Any brand names and product names included in this manual are trademarks, registered trademarks,
service marks, or trade names of their respective holders.
To the Holder of this Manual
The contents of this manual are current as of the date of publication. ADTRAN reserves the right to change
the contents without prior notice.
In no event will ADTRAN be liable for any special, incidental, or consequential damages or for
commercial losses even if ADTRAN has been advised thereof as a result of issue of this publication.
Software Licensing Agreement
Each ADTRAN product contains a single license for ADTRAN supplied software. Pursuant to the
Licensing Agreement, you may: (a) use the software on the purchased ADTRAN device only and (b) keep
a copy of the software for backup purposes. This Agreement covers all software installed on the system as
well as any software available on the ADTRAN website. In addition, certain ADTRAN systems may
contain additional conditions for obtaining software upgrades.
Conventions
Notes provide additional useful information.
Cautions signify information that could prevent service interruption or damage to the
equipment.
Warnings provide information that could prevent endangerment to human life.
ADTRAN will repair and return this product within the warranty period if it does not meet its published
specifications or fails while in service. Warranty information can be found at www.adtran.com
. (Click on
Warranty and Repair Information under Support.)
Product Registration
Registering your product helps ensure complete customer satisfaction. Please take time to register your
products on line at www.adtran.com
. Click Service/Support and then on Product Registration under
Support.
Product Support Information
A return material authorization (RMA) is required prior to returning equipment to ADTRAN. For service,
RMA requests, training, or more information, use the contact information given below.
Repair and Return
If you determine that a repair is needed, please contact our Customer and Product Service (CaPS)
department to have an RMA number issued. CaPS should also be contacted to obtain information
regarding equipment currently in house or possible fees associated with repair.
CaPS Department(256) 963-8722
Identify the RMA number clearly on the package (below the address), and return to the following address:
ADTRAN Customer and Product Service
901 Explorer Blvd. (East Tower)
Huntsville, Alabama 35806
Your reseller should serve as the first point of contact for support. If additional pre-sales support is needed,
the ADTRAN Support website provides a variety of support services such as a searchable knowledge base,
latest product documentation, application briefs, case studies, and a link to submit a question to an
Applications Engineer. All of this, and more, is available at:
http://support.adtran.com
When needed, further pre-sales assistance is available by calling our Applications Engineering
Department.
Applications Engineering(800) 615-1176
Post-Sales Support
Your reseller should serve as the first point of contact for support. If additional support is needed, the
ADTRAN Support website provides a variety of support services such as a searchable knowledge base,
updated firmware releases, latest product documentation, service request ticket generation and
trouble-shooting tools. All of this, and more, is available at:
http://support.adtran.com
When needed, further post-sales assistance is available by calling our Technical Support Center. Please
have your unit serial number available when you call.
Technical Support(888) 4ADTRAN
International Technical Support 1-256-963-8716
Installation and Maintenance Support
The ADTRAN Custom Extended Services (ACES) program offers multiple types and levels of installation
and maintenance services which allow you to choose the kind of assistance you need. This support is
available at:
The Enterprise Network (EN) Technical Training Department offers training on our most popular products.
These courses include overviews on product features and functions while covering applications of
ADTRAN's product lines. ADTRAN provides a variety of training options, including customized training
and courses taught at our facilities or at your site. For more information about training, please contact your
Territory Manager or the Enterprise Training Coordinator.
Training Phone(800) 615-1176, ext. 7500
Training Fax(256) 963-6700
Training Emailtraining@adtran.com
Export Statement
An Export License is required if an ADTRAN product is sold to a Government Entity outside of the EU+8
(Austria, Australia, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary,
Ireland, Italy, Japan, Luxembourg, Netherlands, New Zealand, Norway, Poland, Portugal, Spain, Sweden,
Switzerland and the United Kingdom). This requirement is per DOC/BIS ruling G030477 issued 6/6/03.
This product also requires that the Exporter of Record file a semi-annual report with the BXA detailing the
information per EAR 740.17(5)(e)(2).
DOC - Department of Commerce
BIS - Bureau of Industry and Security
BXA - Bureau of Export Administration
If you are new to the ADTRAN Operating System’s (AOS) Command Line Interface (CLI), take a few
moments to review the information provided in the section which follows (CLI Introduction).
If you are already familiar with the CLI and you need information on a specific command or group of
commands, proceed to Command Descriptions on page 13 of this guide.
CLI INTRODUCTION
This portion of the Command Reference Guide is designed to introduce you to the basic concepts and
strategies associated with using the AOS CLI.
Accessing the CLI from your PC
All products using the AOS are initially accessed by connecting a VT100 terminal (or terminal emulator)
CONSOLE port located on the rear panel of the unit using a standard DB-9 (male) to DB-9 (female)
to the
serial cable. Configure the VT100 terminal or terminal emulation software to the following settings:
•9600 baud
•8 data bits
•No parity
•1 stop bit
•No flow control
For more details on connecting to your unit, refer to the Quick Configuration Guides and
Quick Start Guides located on the ADTRAN OS Documentation CD provided with your
unit.
Understanding Command Security Levels
The ADTRAN CLI has two command security levels — Basic and Enable. Both levels support a specific
set of commands. For example, all interface configuration commands are accessible only through the
Enable security level. The following table contains a brief description of each level.
To prevent unauthorized users from accessing the configuration functions of your AOS
product, immediately install an Enable-level password. Refer to the Quick Configuration
Guides and Quick Start Guides located on the ADTRAN OS Documentation CD provided
with your unit for more information on configuring a password.
Understanding Configuration Modes
The ADTRAN CLI has four configuration modes to organize the configuration commands – Global, Line,
Router, and Interface. Each configuration mode supports a set of commands specific to the configurable
parameters for the mode. For example, all Frame Relay configuration commands are accessible only
through the interface configuration mode (for the virtual Frame Relay interface). The following table
contains a brief description of each level.
ModeAccess by...Sample Prompt With this mode you
can...
Globalentering
command security level prompt.
For example:
>enable
#config term
Linespecifying a line (console or Telnet)
while at the Global Configuration mode
prompt.
For example:
>enable
#config term
(config)#line console 0
Routerentering
while at the Global Configuration mode
prompt.
For example:
>enable
#config term
(config)#
•Obtain syntax help for a specific command by entering the command, a space, and
then a question mark (?). The ADTRAN CLI displays the range of values and a brief
description of the next parameter expected for that particular command. For
example:
(config-eth 0/1)#mtu ?
<64-1500> - MTU (bytes)
Jump to the beginning of the displayed command line. This shortcut is helpful when using
the
no
following prompt will place the cursor directly after the
(config-eth 0/1)#ip address 192.33.55.6
ip d?
form of commands (when available). For example, pressing
entering
configuration parameters for the specified T1 interface. Entering
work as well, but is not necessary.
feature:
int t1 1/1
(Press
at the Global configuration prompt provides you access to the
6
:
<Ctrl + U>
here)
interface t1 1/1
<Ctrl + E>
at the
would
Performing Common CLI Functions
The following table contains descriptions of common CLI commands.
CommandDescription
do
The do command provides a way to execute commands in
other command sets without taking the time to exit the
current and enter the desired one. The following example
shows the
interface configuration while currently in the T1 interface
command set:
do
command used to view the Frame Relay
(config)#interface t1 1/1
(config-t1 1/1)#do show interfaces fr 7
To undo an issued command or to disable a feature, enter
no
before the command.
For example:
no shutdown t1 1/1
When you are ready to save the changes made to the
configuration, enter this command. This copies your
changes to the unit’s nonvolatile random access memory
(NVRAM). Once the save is complete, the changes are
retained even if the unit is shut down or suffers a power
outage.
Displays the current configuration.
Command Reference GuidePerforming Common CLI Functions
CommandDescription
debug
undebug all
Use the
may be experiencing on your network. These commands
provide additional information to help you better interpret
possible problems. For information on specific debug
commands, refer to the section
Set on page 24
To turn off any active debug commands, enter this
command.
debug
command to troubleshoot problems you
Enable Mode Command
.
The overhead associated with the debug command takes up a large portion of your AOS
product’s resources and at times can halt other processes. It is best to only use the debug
command during times when the network resources are in low demand (non-peak hours,
weekends, etc.).
The following table lists and defines some of the more common error messages given in the CLI.
MessageHelpful Hints
%Ambiguous command
%Unrecognized Command
%Invalid or incomplete
command
%Invalid input detected at “^"
marker
The command may not be valid in the current command mode, or you may
not have entered enough correct characters for the command to be
?
recognized. Try using the
CLI Shortcuts on page 9
The command may not be valid in the current command mode, or you may
not have entered all of the pertinent information required to make the
command valid. Try using the
Using CLI Shortcuts on page 9
The error in command entry is located where the caret (^) mark appears.
Enter a question mark at the prompt. The system will display a list of
applicable commands or will give syntax information for the entry.
This portion of the guide provides a detailed listing of all available commands for the ADTRAN OS CLI
(organized by command set). Each command listing contains pertinent information including the default
value, a description of all sub-command parameters, functional notes for using the command, and a brief
technology review. To search for a particular command alphabetically, use the Index. To
search for information on a group of commands within a particular command set, use the linked references
given below:
Basic Mode Command Set on page 14
Enable Mode Command Set on page 24
Global Configuration Mode Command Set on page 257
DHCP Pool Command Set on page 448
HDLC Command Set on page 466
IKE Policy Attributes Command Set on page 554
IKE Client Command Set on page 519
Crypto Map IKE Command Set on page 523
Radius Group Command Set on page 532
CA Profile Configuration Command Set on page 534
Certificate Configuration Command Set on page 545
Ethernet Interface Configuration Command Set on page 549
T1 Interface Configuration Command Set on page 604
DSX-1 Interface Configuration Command Set on page 633
FXS Interface Configuration Command Set on page 618
FDL Interface Configuration Command Set on page 628
Frame Relay Interface Config Command Set on page 643
Frame Relay Sub-Interface Config Command Set on page 663
BGP Configuration Command Set on page 708
BGP Neighbor Configuration Command Set on page 714
Tunnel Configuration Command Set on page 730
PPP Interface Configuration Command Set on page 768
Loopback Interface Configuration Command Set on page 821
Line (Console) Interface Config Command Set on page 851
Line (Telnet) Interface Config Command Set on page 862
Router (RIP) Configuration Command Set on page 869
Router (OSPF) Configuration Command Set on page 878
Quality of Service (QoS) Map Commands on page 892
Voice User Command Set on page 898
AS Path List Command Set on page 928
Codec List Command Set on page 931
Community List Command Set on page 935
Voice Trunk Group Command Set on page 938
Voice Trunk SIP Command Set on page 943
Voice Trunk T1 Wink Command Set on page 952
Voice CoS Command Set on page 967
Voice Ring Group Command Set on page 994
To activate the Basic mode, simply log in to the unit. After connecting the unit to a VT100 terminal (or
terminal emulator) and activating a terminal session, the following prompt displays:
>
The following command is common to multiple command sets and is covered in a centralized section of
this guide. For more information, refer to the section listed below:
exit on page 1014
All other commands for this command set are described in this section in alphabetical order.
Use the enable command (at the Basic Command mode prompt) to enter the Enable Command mode. Use
the disable command to exit the Enable Command mode. Refer to Enable Mode Command Set on page 24
for more information.
Syntax Description
No subcommands.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 1.1Command was introduced.
Functional Notes
The Enable Command mode provides access to operating and configuration parameters and should be
password protected to prevent unauthorized use. Use the enable password command (found in the
Global Configuration mode) to specify an Enable Command mode password. If the password is set,
access to the Enable Commands (and all other “privileged” commands) is only granted when the correct
password is entered. Refer to
crypto ca authenticate <name> on page 275 for more information.
Usage Examples
The following example enters the Enable Command mode and defines an Enable Command mode
password:
Use the ping command (at the Basic Command mode prompt) to verify IP network connectivity.
Syntax Description
<address>Specifies the IP address of the system to ping. Entering the ping command with
no specified address prompts the user with parameters for a more detailed ping
configuration. Refer to Functional Notes (below) for more information.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 1.1Command was introduced.Command was introduced.
Functional Notes
The ping command helps diagnose basic IP network connectivity using the Packet InterNet Groper
program to repeatedly bounce Internet Control Message Protocol (ICMP) Echo_Request packets off a
system (using a specified IP address). The AOS allows executing a standard ping request to a specified IP
address or provides a set of prompts to configure a more specific ping configuration.
The following is a list of output messages from the ping command:
!Success
-Destination Host Unreachable
$Invalid Host Address
XTTL Expired in Transit
? Unknown Host
*Request Timed Out
The following is a list of available extended ping fields with descriptions:
Target IP addressSpecifies the IP address of the system to ping.
Repeat CountSpecifies the number of ping packets to send to the system
(valid range: 1 to 1,000,000).
Datagram SizeSpecifies the size (in bytes) of the ping packet (valid range: 1 to 1448).
Timeout in SecondsSpecifies the timeout period after which a ping is considered unsuccessful
(valid range: 1 to 5 seconds).
Extended CommandsSpecifies whether additional commands are desired for more ping
configuration parameters.
Source Address (or interface) Specifies the IP address to use as the source address in the ECHO_REQ
packets.
Data PatternSpecifies an alphanumerical string to use (the ASCII equivalent) as the data
pattern in the ECHO_REQ packets.
Sweep Range of SizesVaries the sizes of the ECHO_REQ packets transmitted.
Sweep Min SizeSpecifies the minimum size of the ECHO_REQ packet
(valid range: 0 to 1448).
Sweep Max SizeSpecifies the maximum size of the ECHO_REQ packet
(valid range: Sweep Min Size to 1448).
Sweep IntervalSpecifies the interval used to determine packet size when performing the
sweep (valid range: 1 to 1448).
Verbose OutputSpecifies an extended results output.
Usage Examples
The following is an example of a successful ping command:
>ping
Target IP address:192.168.0.30
Repeat count[1-1000000]:5
Datagram Size [1-1000000]:100
Timeout in seconds [1-5]:2
Extended Commands? [y or n]:n
Type CTRL+C to abort.
Legend: '!' = Success '?' = Unknown host '$' = Invalid host address
'*' = Request timed out '-' = Destination host unreachable
'x' = TTL expired in transit
Pinging 192.168.0.30 with 100 bytes of data:
!!!!!
Success rate is 100 percent (5/5) round-trip min/avg/max = 19/20.8/25 ms
Use the show clock command to display the system time and date entered using the clock set command.
Refer to the section clock set <time> <day> <month> <year> on page 60 for more information.
Syntax Description
No subcommands.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 1.1Command was introduced.
Usage Examples
The following example displays the current time and data from the system clock:
Use the show snmp command to display the system Simple Network Management Protocol (SNMP)
parameters and current status of SNMP communications.
Syntax Description
No subcommands.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 1.1Command was introduced.
Usage Examples
The following is an example output using the show snmp command for a system with SNMP disabled and
the default chassis and contact parameters:
>show snmp
Chassis: Chassis ID
Contact: Customer Service
0 Rx SNMP packets
0 Bad community names
0 Bad community uses
0 Bad versions
0 Silent drops
0 Proxy drops
0 ASN parse errors
Use the show version command to display the current AOS version information.
Syntax Description
No subcommands.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 1.1Command was introduced.
Usage Examples
The following is a sample show version output:
>show version
AOS version 06.01.00
Checksum: 1F0D5243 built on Fri Nov 08 13:12:06 2002
Upgrade key: de76efcfeb4c8eeb6901188475dd0917
Boot ROM version 03.00.18
Checksum: 7A3D built on: Fri Nov 08 13:12:25 2002
Copyright (c) 1999-2002 ADTRAN Inc.
Serial number C14C6308
UNIT_2 uptime is 0 days 4 hours 59 minutes 43 seconds
System returned to ROM by Warm Start
Current system image file is "030018adv.biz"
Boot system image file is "030018adv.biz"
To activate the Enable mode, enter the enable command at the Basic mode prompt. (If an enable password
has been configured, a password prompt will display.) For example:
>enable
Password: XXXXXXX
#
The following command is common to multiple command sets and is covered in a centralized section of
this guide. For more information, refer to the section listed below:
exit on page 1014
All other commands for this command set are described in this section in alphabetical order.
Use the clear crypto ipsec sa command to clear existing IPSec security associations (SAs), including
active ones.
Variations of this command include the following:
clear crypto ipsec sa
clear crypto ipsec sa entry <ip address> ah <SPI>
clear crypto ipsec sa entry <ip address> esp <SPI>
clear crypto ipsec sa map <map name>
clear crypto ipsec sa peer <ip address>
Syntax Description
entry
<ip address>
ah
<SPI>
esp
<SPI>
map
<map name>
peer
<ip address>
Clears only the SAs related to a certain destination IP address.
Clears only a portion of the SAs by specifying the authentication header (AH)
protocol and a security parameter index (SPI). You can determine the correct SPI
value using the show crypto ipsec sa command.
Clears only a portion of the SAs by specifying the encapsulating security payload
(ESP) protocol and an SPI. You can determine the correct SPI value using the
show crypto ipsec sa command.
Clears only the SAs associated with the crypto map name given.
Clears only the SAs associated with the far-end peer IP address given.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Use the clear ip dhcp-server binding command to clear Dynamic Host Configuration Protocol (DHCP)
server binding entries from the database.
Syntax Description
*Clears all automatic binding entries.
<ip address>Clears a specific binding entry. Enter the source IP address (format is A.B.C.D).
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 10.1Command was introduced.
Functional Notes
A DHCP server binding represents an association between a MAC address and an IP address that was
offered by the unit to a DHCP client (i.e., most often a PC). Clearing a binding allows the unit to offer that
IP address again, should a request be made for one.
Usage Examples
The following example clears a DHCP server binding for the IP address 125.25.47.4:
The clear dump-core command clears diagnostic information appended to the output of the show version
command. This information results from an unexpected unit reboot.
Syntax Description
No subcommands.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 6.1Command was introduced.
Usage Examples
The following example clears the entire database of IKE SAs (including the active associations):
clear ip bgp [* | <as-number> | <ip address>] [in | out | soft]
Use the clear ip bgp command to clear BGP neighbors as specified.
Syntax Description
*Clears all BGP neighbors.
<as-number>Clears all BGP neighbors with the specified AS number. Range is 1 to 65,535.
<ip address>Clears the BGP neighbor with the specified IP address.
inCauses a “soft” reset inbound with a neighbor, reprocessing routes advertised by
that neighbor.
outCauses a “soft” reset outbound with a neighbor, re-sending advertised routes to
that neighbor.
softCauses a “soft” reset both inbound and outbound.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Command History
Release 8.1Command was introduced.
Functional Notes
The clear ip bgp command must be issued to re-initialize the BGP process between the peers matching
the given arguments. Most neighbor changes, including changes to prefix-list filters, do not take effect until
the clear command is issued. A hard reset clears the TCP connection with the specified peers, which
results in clearing the table. This method of clearing is disruptive and causes peer routers to record a route
flap for each route.
The out version of this command provides a soft reset out to occur by causing all routes to be re-sent to
the specified peer(s). TCP connections are not torn down, so this method is less disruptive. Output
filters/policies are re-applied before sending the update.
The in version of this command provides a soft reset in to occur by allowing the router to receive an
updated table from a peer without tearing down the TCP connection. This method is less disruptive and
does not count as a route flap. Currently, all of the peer's routes are stored permanently, even if they are
filtered by a prefix list. The command causes the peer's routes to be reprocessed with any new
parameters.
clear ip igmp group [<group-address> | <interface>]
Use the clear ip igmp group command to clear entries from the Internet Group Management Protocol
(IGMP) tables. If no address or interface is specified, all non-static IGMP groups are cleared with this
command.
Syntax Description
<group-address>
<interface>
Optional. Specifies the multicast IP address of the multicast group.
Optional. Designates the display of parameters for a specific interface (in the format
type slot/port). For example:
eth 0/1
.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 3000, 4000, and 5000 and Total Access 900 Series
units.
Command History
Release 7.1Command was introduced.
Release 9.1Command was expanded to include HDSL and tunnel interfaces.
Usage Examples
The following example shows output for the show igmp groups command before and after a
clear ip igmp group command is issued. This example clears the IGMP entry that was registered
dynamically by a host. Interfaces that are statically joined are not cleared:
#show ip igmp groups
IGMP Connected Group Membership
Group Address
Interface
Uptime
Expires
Last Reporter
Use the clear ip policy-sessions command to clear policy class sessions. You may clear all the sessions or
a specific session. Use the show ip policy-sessions command to view a current session listing. The
following lists the complete syntax for the clear ip policy-sessions commands:
clear ip policy-sessions
clear ip policy-sessions <classname> [ahp | esp | gre | icmp | tcp | udp | <protocol>] <source ip>
<source port><dest ip><dest port>
clear ip policy-sessions <classname> [ahp | esp | gre | icmp | tcp | udp | <protocol>] <source ip>
<classname>Alphanumeric descriptor for identifying the configured access policy (access
policy descriptors are not case-sensitive).
<protocol>Specifies protocol (valid range: 0-255).
<source ip>Specifies the source IP address (format is A.B.C.D).
<source port>Specifies the source port (in hex format for ahp, esp, and gre; decimal for all other
protocols).
<dest ip>Specifies the destination IP address (format is A.B.C.D).
<dest port>Specifies the destination port (in hex format for ahp, esp, and gre; decimal for all
other protocols).
[destination | source] For NAT sessions, this specifies whether to select a NAT source or NAT
destination session.
<nat ip>For NAT sessions, this specifies the NAT IP address (format is A.B.C.D).
<nat port>For NAT sessions, this specifies the NAT port (in hex format for ahp, esp, and gre;
decimal for all other protocols).
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 2.1Command was introduced.
Functional Notes
The second half of this command, beginning with the source IP address may be copied and pasted from a
row in the show ip policy-sessions table for easier use.
The following example clears the Telnet association (TCP port 23) for policy class "pclass1" with source IP
address 192.22.71.50 and destination 192.22.71.130:
>enable
#clear ip policy-sessions pclass1 tcp 192.22.71.50 23 192.22.71.130 23
Use the clear ip prefix-list command to clear the IP prefix list hit count shown in the show ip prefix-list
detail command output. Refer to show ip prefix-list [detail | summary] <listname> on page 183 for more
information.
Syntax Description
<listname>Specifies hit count statistics of the IP prefix list to clear.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Command History
Release 8.1Command was introduced.
Usage Examples
The following example clears the hit count statistics for prefix list test:
Use the clear ip route command to remove all learned routes from the IP route table. Static and connected
routes are not cleared by this command.
Syntax Description
*Delete all destination routes.
<ip address>Specify the IP address of the destination routes to be deleted.
<subnet mask>Specify the subnet mask of the destination routes to be deleted
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Command History
Release 1.1Command was introduced.
Usage Examples
The following example removes all learned routes from the route table:
Use the clear lldp neighbors command to remove all neighbors from this unit’s database. As new LLDP
packets are received, the database will contain information about neighbors included in those frames.
Syntax Description
No subcommands.
Default Values
There are no default settings for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 8.1Command was introduced.
Functional Notes
This command generates output indicating the names of any neighbors deleted from the database and the
name of the interface on which the neighbor was learned.
Usage Examples
The following example clears LLDP neighbor Switch_1 from the Ethernet interface 0/7:
>enable
#clear lldp neighbors
LLDP: Deleted neighbor “Switch_1” on interface eth 0/7
#
Use the clear qos map command to clear the statistics for all defined QoS maps or to view detailed
information for maps meeting user-configured specifications.
<map name>Specifies the name of a defined QoS map.
<sequence number>Specifies one of the map’s defined sequence numbers.
<interface>Specifies an interface for which to clear QoS map statistics (for just that interface).
Type
clear qos map interface ?
for a complete list of applicable interfaces.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Use the clear spanning-tree detected-protocols command to restart the protocol migration process.
Syntax Description
interfaceOptional. Specifies
<interface id>Optional. Specifies
detected-protocols interface
the
ethernet, gigabit ethernet
a valid interface ID. Type
? for a complete list of applicable interfaces.
, or
port channel
clear spanning-tree
interface.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 3000, 4000, and 5000 and Total Access 900
Series units.
Command History
Release 5.1Command was introduced.
Functional Notes
The switch has the ability to operate using the rapid spanning-tree protocol or the legacy 802.1D version of
spanning-tree. When a BPDU (bridge protocol data unit) of the legacy version is detected on an interface,
the switch automatically regresses to using the 802.1D spanning-tree protocol for that interface. Issue the
clear spanning-tree detected-protocols command to return to rapid spanning-tree operation.
Usage Examples
The following example re-initiates the protocol migration process on Ethernet interface 0/3:
The clock auto-correct-dst command allows the automatic one-hour correction for Daylight Saving Time
(DST). Use the clock no-auto-correct-dst command to disable this feature.
Syntax Description
No subcommands.
Default Values
By default this command is enabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 6.1Command was introduced.
Usage Examples
The following example allows for automatic DST correction:
The clock no-auto-correct-dst command allows you to override the automatic one-hour correction for
Daylight Saving Time (DST).
Syntax Description
No subcommands.
Default Values
No default value is necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 6.1Command was introduced.
Functional Notes
Many time zones include an automatic one-hour correction for daylight saving time at the appropriate time.
You may override it at your location using this command.
Usage Examples
The following example overrides the one-hour offset for DST:
Use the clock set command to configure the system software clock. For the command to be valid, all fields
must be entered. Refer to the Usage Example below for an example.
Syntax Description
<time>Sets the time (in 24-hour format) of the system software clock in the format
HH:MM:SS (hours:minutes:seconds).
<day>Sets the current day of the month (valid range: 1 to 31).
<month>Sets the current month (valid range: January to December). You need only enter
enough characters to make the entry unique. This entry is not case-sensitive.
<year>Sets the current year (valid range: 2000 to 2100).
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 1.1Command was introduced.
Usage Examples
The following example sets the system software clock for 3:42 pm, August 22 2004:
The clock timezone command sets the unit’s internal clock to the timezone of your choice. This setting is
based on the difference in time (in hours) between Greenwich Mean Time (GMT) or Central Standard
Time (CST) and the timezone for which you are setting up the unit. Use the no form of this command to
disable this feature.
Syntax Description
Subcommands are specified in the Functional Notes section for this command.
Default Values
No default value is necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Use the configure command to enter the Global Configuration mode or to configure the system from
memory. Refer to Global Configuration Mode Command Set on page 257 for more information.
Syntax Description
memoryConfigures the active system with the commands located in the default
configuration file stored in NVRAM.
networkConfigures the system from a TFTP network host.
overwrite-networkOverwrites NVRAM memory from a TFTP network host.
terminalEnters the Global Configuration mode.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 1.1Command was introduced.
Usage Examples
The following example enters the Global Configuration mode from the Enable mode:
Use the copy command to copy any file from a specified source to a specified destination.
Syntax Description
<source>Specifies the current location of the file.
Valid sources include: running-config (current running configuration file),
startup-config (configuration file located in NVRAM), or a filename (located in
FLASH memory).
<destination>Specifies the destination of the copied file.
Valid destinations include: running-config (current running configuration file),
startup-config (configuration file located in NVRAM), or a filename (located in
FLASH memory).
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Use the copy console command to copy the console’s input to a text file. To end copying to the text file,
type <
Ctrl+D>. The file will be saved in the AOS root directory.
Syntax Description
<filename>Specifies destination file for console input.
Default Values
No default is necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 8.1Command was introduced.
Functional Notes
The copy console command works much like a line editor. Prior to pressing <Enter>, changes can be
made to the text on the line. Changes can be made using <Delete> and <Backspace> keys. The text can
be traversed using the arrow keys, <Ctrl+A> (to go to the beginning of a line), and <Ctrl+E> (to go to the
end of a line). To end copying to the text file, type <Ctrl+D>. The file will be saved in the AOS root
directory. Use the dir command to see a list of files in the root directory.
Usage Examples
The following example copies the console input into the file config (located in the AOS root directory):
Use the copy tftp command to copy a file located on a network Trivial File Transfer Protocol (TFTP)
server to a specified destination.
Syntax Description
<destination>Specifies the destination of the file copied from the TFTP server.
Valid destinations include: flash (FLASH memory), startup-config (the
configuration file stored in NVRAM), or running-config (the current running
configuration file).
After entering copy tftp and specifying a destination, the AOS prompts for
the following information:
Address of remote host:IP address of the TFTP server.
Source filename:Name of the file to copy from the TFTP server.
Destination filename:Specifies the filename to use when storing the copied file to FLASH
memory. (Valid only for the copy tftp flash command.)
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 1.1Command was introduced.
Usage Examples
The following example copies myfile.biz from the TFTP server (10.200.2.4) to flash memory and labels it
newfile.biz:
>enable
#copy tftp flash
Address of remote host?10.200.2.4
Source filename myfile.biz
Destination filename newfile.biz
Initiating TFTP transfer...
Received 45647 bytes.
Transfer Complete!
#
Use the copy xmodem command to copy a file (using the XMODEM protocol) to a specified destination.
XMODEM capability is provided in terminal emulation software such as HyperTerminal™.
Syntax Description
<destination>Specifies the destination of the copied file.
Valid destinations include: flash (FLASH memory), startup-config (the
configuration file stored in NVRAM), or running-config (the current running
configuration file).
After entering copy xmodem and specifying a destination, the AOS prompts for
the following information:
Destination filename:Specifies the filename to use when storing the copied file to FLASH memory.
(Valid only for the copy flash command.)
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 1.1Command was introduced.
Usage Examples
The following example copies a .biz file to flash memory and labels it newfile.biz:
>enable
#copy xmodem flash
Destination filename newfile.biz
Begin the Xmodem transfer now...
Press CTRL+X twice to cancel
CCCCCC
The AOS is now ready to accept the file on the CONSOLE port (using the XMODEM protocol). The next
step in the process may differ depending on the type of terminal emulation software you are using. For
HyperTerminal, you will now select Transfer > Send File and browse to the file you wish to copy. Once the
transfer is complete, information similar to the following is displayed:
Use the debug aaa command to activate debug messages associated with authentication from the AAA
subsystem. Debug messages are displayed (real-time) on the terminal (or Telnet) screen. Use the no form
of this command to disable the debug messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 5.1Command was introduced.
Functional Notes
The debug aaa events include connection notices, login attempts, and session tracking.
Usage Examples
The following is sample output for this command:
>enable
#debug aaa
AAA: New Session on portal 'TELNET 0 (172.22.12.60:4867)'.
AAA: No list mapped to 'TELNET 0'. Using 'default'.
AAA: Attempting authentication (username/password).
AAA: RADIUS authentication failed.
AAA: Authentication failed.
AAA: Closing Session on portal 'TELNET 0 (172.22.12.60:4867)'.
Use the debug access-list command to activate debug messages (for a specified list) associated with access
list operation. Debug messages are displayed (real-time) on the terminal (or Telnet) screen. Use the no
form of this command to disable the debug messages.
Syntax Description
<listname>Specifies a configured access list.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Command History
Release 2.1Command was introduced.
Functional Notes
The debug access-list command provides debug messages to aid in troubleshooting access list issues.
Usage Examples
The following example activates debug messages for the access list labeled MatchAll:
Use the debug arp command to activate debug messages associated with IP ARP transactions. Debug
messages are displayed (real-time) on the terminal (or Telnet) screen. Use the no form of this command to
disable the debug messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300 and Total Access 900 Series units.
Command History
Release 9.3Command was introduced.
Usage Examples
The following example activates debug messages associated with ARP transactions:
Use the debug bridge command to display messages associated with bridge events. Debug messages are
displayed (real-time) to the terminal (or Telnet) screen. Use the no form of this command to disable debug
messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 3000, 4000, and 5000 and Total Access 900 Series
units.
Command History
Release 8.1Command was introduced.
Usage Examples
The following example activates bridge debug messages:
debug crypto [ike | ike negotiation | ike client authentication |
ike client configuration | ipsec | pki]
Use the debug crypto command to activate debug messages associated with IKE and IPSec functions.
Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the no form of this
command to disable the debug messages.
Syntax Description
ike Displays all IKE debug messages.
ike negotiationDisplays only IKE key management debug messages (e.g., handshaking).
ike client authenticationDisplays IKE client authentication messages as they occur.
ike client configurationDisplays mode-config exchanges as they take place over the IKE SA. It is
enabled independently from the ike negotiation debug described
previously.
ipsecDisplays all IPSec debug messages.
pkiDisplays all PKI (public key infrastructure) debug messages.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Command History
Release 4.1Command was introduced.
Release 6.1Debug pki command introduced.
Usage Examples
The following example activates the IPSec debug messages:
Use the debug dynamic-dns command to display debug messages associated with dynamic DNS. Debug
messages are displayed (real-time) to the terminal (or Telnet) screen. Use the no form of this command to
disable the debug messages.
Syntax Description
verboseTurns on verbose messaging.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 8.1Command was introduced.
Usage Examples
The following example activates dynamic DNS debug messages:
Use the debug firewall command to activate debug messages associated with the AOS firewall operation.
Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the no form of this
command to disable the debug messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Command History
Release 2.1Command was introduced.
Functional Notes
The debug firewall command activates debug messages to provide real-time information about the AOS
stateful inspection firewall operation.
Usage Examples
The following example activates the debug messages for the AOS stateful inspection firewall:
Use the debug firewall alg sip command to activate debug messages associated with Session Initiation
Protocol (SIP) information with AOS firewall operation. Debug messages are displayed (real-time) on the
terminal (or Telnet) screen. Use the no form of this command to disable the debug messages.
Syntax Description
verboseEnables detailed debug messages.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300 and Total Access 900 Series units.
Command History
Release 9.3Command was introduced.
Usage Examples
The following example activates debug messages associated with SIP information with AOS firewall
operation:
Use the debug frame-relay command to activate debug messages associated with the Frame Relay
operation. Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the no form of
this command to disable the debug messages.
Syntax Description
eventsActivates debug messages for generic Frame Relay events (such as Frame Relay
interface state).
llc2Activates debug messages for the logical link control layer.
lmiActivates debug messages for the local management interface (such as DLCI
status signaling state, etc.).
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 1000R, 3000, 4000, and 5000 and Total Access 900 Series units.
Command History
Release 1.1Command was introduced.
Functional Notes
The debug frame-relay command activates debug messages to aid in the troubleshooting of Frame Relay
links.
Usage Examples
The following example activates all possible debug messages associated with Frame Relay operation:
Use the debug frame-relay multilink command to activate debug messages associated with Frame Relay
multilink operation. Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the
no form of this command to disable the debug messages.
Syntax Description
<interface>Optional. Activates debug messages for the specified interface. Type debug
frame-relay multilink ? for a complete list of applicable interfaces.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 1000R, 3000, 4000, and 5000 and Total Access 900 Series units.
Command History
Release 9.1Command was introduced.
Usage Examples
The following example activates debug messages associated with multilink operation for all Frame Relay
interfaces:
Use the debug hdlc command to activate debug messages associated with the HDLC interface. Debug
messages are displayed (real-time) to the terminal (or Telnet) screen. Use the no form of this command to
disable the debug messages.
Syntax Description
errorsEnables protocol error and statistic messages.
verboseEnables detailed debug messages.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the 1000R, 3000, 4000, and 5000 and Total Access 900 Series units.
Command History
Release 9.1Command was introduced.
Usage Examples
The following example activates detailed debug messages associated with the HDLC interface:
Use the debug interface command to activate debug messages associated with the specified interface.
Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the no form of this
command to disable the debug messages.
Syntax Description
<interface>Activates debug messages for the specified interface. Type debug interface ? for
a complete list of applicable interfaces.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 3.1Command was introduced.
Release 6.1Command was expanded to include T1 and FXS interfaces.
Release 7.1Command was expanded to include FXO interface.
Release 9.1Command was expanded to include tunnel interface.
Functional Notes
The debug interface command activates debug messages to aid in the troubleshooting of physical
interfaces.
Usage Examples
The following example activates all possible debug messages associated with the Ethernet port:
debug ip bgp [events | in | out | keepalives | updates | updates quiet]
Use the debug ip bgp command to activate debug messages associated with IP BGP. Debug messages are
displayed (real-time) on the terminal (or Telnet) screen. Use the no form of this command to disable the
debug messages.
Syntax Description
eventsDisplays significant BGP events such as a neighbor state change.
in/outDisplays the same information as debug ip bgp, but limits messages to the
specified direction (in or out).
keepalivesDisplays BGP keepalive packets.
updatesDisplays detailed information on BGP updates for all neighbors.
updates quietDisplays summary information about BGP neighbor updates. (Note: updates
quiet displays a one-line summary of what update displays in 104 lines.)
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Command History
Release 8.1Command was introduced.
Functional Notes
If no arguments are given, the debug ip bgp command displays general BGP events such as
sent/received message summaries, route processing actions, and results. Keepalive packets are not
debugged with this command.
Usage Examples
The following example enables debug messages on general outbound BGP messages and events:
>enable
#debug ip bgp out
#07:42:39: BGP OUT 10.15.240.1[2]: Transmitting msg, type=UPDATE (2), len=142
Use the debug ip dhcp-client command to activate debug messages associated with DHCP client
operation in the AOS. Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the
no form of this command to disable the debug messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 2.1Command was introduced.
Functional Notes
The debug ip dhcp-client command activates debug messages to provide information on DHCP client
activity in the AOS. The AOS DHCP client capability allows interfaces to dynamically obtain an IP address
from a network DHCP server.
Usage Examples
The following example activates debug messages associated with DHCP client activity:
Use the debug ip dhcp-server command to activate debug messages associated with DHCP server
operation in the AOS. Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the
no form of this command to disable the debug messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 2.1Command was introduced.
Functional Notes
The debug ip dhcp-server command activates debug messages to provide information on DHCP server
activity in the AOS. The AOS DHCP server capability allows the AOS to dynamically assign IP addresses
to hosts on the network.
Usage Examples
The following example activates debug messages associated with DHCP server activity:
Use the debug ip dns-client command to activate debug messages associated with DNS (domain naming
system) client operation in the AOS. Debug messages are displayed (real-time) to the terminal (or Telnet)
screen. Use the no form of this command to disable the debug messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 3.1Command was introduced.
Functional Notes
The debug ip dns-client command activates debug messages to provide information on DNS client
activity in the AOS. The IP DNS capability allows for DNS-based host translation (name-to-address).
Usage Examples
The following example activates debug messages associated with DNS client activity:
Use the debug ip dns-proxy command to activate debug messages associated with DNS (domain naming
system) proxy operation in the AOS. Debug messages are displayed (real-time) to the terminal (or Telnet)
screen. Use the no form of this command to disable the debug messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 3.1Command was introduced.
Functional Notes
The debug ip dns-proxy command activates debug messages to provide information on DNS proxy
activity in the AOS. The IP DNS capability allows for DNS-based host translation (name-to-address).
Usage Examples
The following example activates debug messages associated with DNS proxy activity:
Use the debug ip http command to activate debug messages associated with HTTP operation in the AOS.
Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the no form of this
command to disable the debug messages.
Syntax Description
verboseActivates detailed debug messages for HTTP operation.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, and 2000 and Total Access 900 Series units.
Command History
Release 6.1Command was introduced.
Usage Examples
The following example activates debug messages associated with HTTP activity:
Use the debug ip icmp command to show all ICMP messages as they come into the router or are
originated by the router. If an optional keyword (send or recv) is not used, all results are displayed. Use the
no form of this command to disable the debug messages.
Syntax Description
send
recv
Optional. Keyword which allows you to only display ICMP messages sent by the
router.
Optional. Keyword which allows you to only display ICMP messages received by the
router.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 3.1Command was introduced.
Usage Examples
The following example activates the debug ip icmp send and receive messages for the AOS:
>enable
#debug ip icmp
ICMP SEND: From (0.0.0.0) to (172.22.14.229) Type=8 Code=0 Length=72 Details:echo request
ICMP RECV: From (172.22.14.229) to (10.100.23.19) Type=0 Code=0 Length=72 Details:echo reply
ICMP SEND: From (0.0.0.0) to (172.22.14.229) Type=8 Code=0 Length=72 Details:echo request
ICMP RECV: From (172.22.14.229) to (10.100.23.19) Type=0 Code=0 Length=72 Details:echo reply
ICMP RECV: From (172.22.255.200) to (10.100.23.19) Type=11 Code=0 Length=36 Details:TTL equals 0
during transit
ICMP RECV: From (172.22.14.229) to (10.100.23.19) Type=3 Code=3 Length=36 Details:port
unreachable
ICMP RECV: From (172.22.14.229) to (10.100.23.19) Type=3 Code=3 Length=36 Details:port
Use the debug ip mrouting command to activate debug messages associated with multicast table routing
events. Use the no form of this command to disable the debug messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and Total Access
900 Series units.
Command History
Release 10.1Command was introduced.
Usage Examples
The following sample activates ip mrouting debug messages:
Use the debug ip ospf command to activate debug messages associated with OSPF routing operations.
Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the no form of this
command to disable the debug messages.
Use the debug ip rip command to activate debug messages associated with Routing Information Protocol
(RIP) operation in the AOS. Debug messages are displayed (real-time) to the terminal (or Telnet) screen.
Use the no form of this command to disable the debug messages.
Syntax Description
eventsOptional.
Displays only RIP protocol events.
Default Values
No default value necessary for this command.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 2000, 3000, 4000, and 5000 and Total Access 900
Series units.
Command History
Release 1.1Command was introduced.
Functional Notes
The debug ip rip command activates debug messages to provide information on Routing Information
Protocol (RIP) activity in the AOS. RIP allows hosts and routers on a network to exchange information
about routes.
Usage Examples
The following example activates debug messages associated with RIP activity:
Use the debug ip tcp events command to activate debug messages associated with significant TCP events
such as state changes, retransmissions, session aborts, etc., in the AOS. Debug messages are displayed
(real-time) to the terminal (or Telnet) screen. Use the no form of this command to disable the debug
messages.
These debug events are logged for packets that are sent or received from the router.
Forwarded TCP packets are not included.
Syntax Description
eventsOptional.
Displays only TCP protocol events.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 4.1Command was introduced.
Functional Notes
In the debug ip tcp events information, TCB stands for TCP task control block. The numbers which
sometimes appear next to TCB (e.g., TCB5 in the following example) represent the TCP session number.
This allows you to differentiate debug messages for multiple TCP sessions.
Use the debug ip tcp md5 command to activate debug messages that detail the results of each incoming
TCP packet’s MD5 authentication with an internal route in the AOS. Debug messages are displayed
(real-time) to the terminal (or Telnet) screen. Use the no form of this command to disable the debug
messages.
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 3000, 4000, and 5000 and Total Access 900 Series
units.
Command History
Release 9.1Command was introduced.
Functional Notes
Debug messages will only be generated for TCP ports that have MD5 authentication enabled.
Usage Examples
The following example activates debug messages associated with incoming TCP packet’s MD5 authentication:
Use the debug ip udp command to activate debug messages associated with UDP send and receive events
in the AOS. Debug messages are displayed (real-time) to the terminal (or Telnet) screen. Use the no form
of this command to disable the debug messages.
These debug events are logged for packets that are sent or received from the router.
Forwarded UDP packets are not included.
The overhead associated with this command takes up a large portion of your router’s
resources and at times can halt other router processes. It is best to only use the command
during times when the network resources are in low demand (non-peak hours, weekends,
etc.).
Syntax Description
No subcommands.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, 1000R, 2000, 3000, 4000, and 5000 and
Total Access 900 Series units.
Command History
Release 4.1Command was introduced.
Functional Notes
In the debug ip udp information, the message no listener means that there is no service listening on this
UDP port (i.e., the data is discarded).