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 th e 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) T echnical T raining Department offers training on our most po pular 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
This manual provides information about the commands that are available with all of the NetVanta Series
units.
This manual provides information about the commands that are available with NetVanta 3000 Series units.
For a list of all of the commands available through the CLI, see 61950860L1-35L (All Products).
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 14 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.
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.
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.
LevelAccess by...PromptWith this level you can...
Basicbeginning an AOS session.
Enableentering
Basic command security level
as follows:
>enable
enable
while in the
>•display system information
•perform traceroute and ping
functions
•open a Telnet session
#•manage the startup and running
configurations
•use the debug commands
•enter any o f the configuration modes
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 pr ovided
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
•Obtain syntax help for a specific command by entering the co mmand, 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
form of commands (when available). For example, pressing
following prompt will place the cursor directly after the
#
:
<Ctrl + A>
at the
(config-eth 0/1)#ip address 192.33.55.6
<Ctrl + E>
Jump to the end of the displayed command line. For example, pressing
following prompt will place the cursor directly after the
6
:
<Ctrl + E>
at the
(config-eth 0/1)#ip address 192.33.55.6
<Ctrl + U>
Clears the current displayed command line. The following provides an example of the
<Ctrl + U>
(config-eth 0/1)#ip address 192.33.55.6
feature:
(Press
<Ctrl + U>
here)
(config-eth 0/1)#
auto finishYou need only enter enough letters to identify a command as unique. For example,
entering
configuration parameters for the specified T1 interface. Entering
int t1 1/1
at the Global configuration prompt provides you access to the
Command Reference GuidePerforming Common CLI Functions
Performing Common CLI Functions
The following table contains descriptions of common CLI commands.
CommandDescription
do
no
copy running-config startup-config
show running config
debug
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:
(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.
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 36
do
command used to view the Frame Relay
debug
command to troubleshoot problems you
Enable Mode Command
.
undebug all
To turn off any active debug commands, enter this
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 10
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 10
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 at the end of this
document. 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 16
Common Commands on page 26
Enable Mode Command Set on page 36
Global Configuration Mode Command Set on page 268
Line Interface Command Sets
Line (Console) Interface Config Command Set on page 455
Line (SSH) Interface Config Command Set on page 468
Line (Telnet) Interface Config Command Set on page 476
Physical Interface Command Sets
ADSL Interface Config Command Set on page 485
BRI Interface Configuration Command set on page 489
DDS Interface Configuration Command Set on page 501
DSX-1 Interface Configuration Command Set on page 509
E1 Interface Configuration Command Set on page 519
Ethernet Interface Configuration Command Set on page 536
G.703 Interface Configuration Command set on page 594
Modem Interface Configuration Command Set on page 601
Serial Interface Configuration Command Set on page 606
SHDSL Interface Configuration Command Set on page 615
T1 Interface Configuration Command Set on page 627
Virtual Interface Command Sets
ATM Interface Config Command Set on page 644
ATM Sub-Interface Config Command Set on page 647
Demand Interface Configuration Command Set on page 712
Frame Relay Interface Config Command Set on page 773
Frame Relay Sub-Interface Config Command Set on page 795
HDLC Command Set on page 856
Loopback Interface Configuration Command Set on page 913
PPP Interface Configuration Command Set on page 943
Tunnel Configuration Command Set on page 1015
VPN Parameter Command Sets
CA Profile Configuration Command Set on page 1069
Certificate Configuration Command Set on page 1080
Crypto Map IKE Command Set on page 1084
Crypto Map Manual Command Set on page 1093
IKE Client Command Set on page 1104
IKE Policy Attributes Command Set on page 1108
IKE Policy Command Set on page 1114
Routing Protocol Command Sets
AS Path List Command Set on page 1127
BGP Configuration Command Set on page 1130
BGP Neighbor Configuration Command Set on page 1136
Community List Command Set on page 1152
Router (OSPF) Configuration Command Set on page 1155
Router (RIP) Configuration Command Set on page 1170
Security and Services Command Sets
DHCP Pool Command Set on page 1181
Quality of Service (QoS) Map Commands on page 1199
Radius Group Command Set on page 1205
Route Map Command Set on page 1207
TACACS+ Group Configuration Command Set on page 1217
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 34
All other commands for this command set are described in this section in alphabetical order.
enable on page 17
logout on page 18
ping <address> on page 19
show clock on page 21
show snmp on page 22
show version on page 23
telnet <address> on page 24
traceroute <address> on page 25
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 mo de. Refer to En able Mode Command Set on page 36
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
enable password [md5] <password> on page 323 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 Internet Protocol (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 th e Packet InterNet Groper
program to repeatedly bounce Inter ne t Con tr ol 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 Ho st 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 alphanumeric 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-tri p min /a vg /m ax = 19/2 0. 8/ 25 ms
Use the show clock command to display the sys t em time and date entered using the clock set command.
Refer to the section clock set <time> <day> <month> <year> on page 76 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 a nd
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"
Use the alias command to populate the ifAlias OID (Interface Table MIB of RFC2863) for all physical and
virtual interfaces when using Simple Network Management Protocol (SNMP) management stations.
Syntax Description
<“text”>Describes the interface (for SNMP) using an alphanumeric character string
enclosed in quotation marks (limited to 64 characters).
Default Values
No defaults required for this command.
Applicable Command Modes
Applies to all interface mode command sets.
Applicable Platforms
Applies to all AOS products.
Command History
Release 1.1Command was introduced.
Functional Notes
The ifAlias OID is a member of the ifXEntry object-type (defined in RFC2863) used to provide a
non-volatile, unique name for various interfaces. This name is preserved through power cycles. Enter a
string (using the alias command) which clearly identifies the interface.
Usage Examples
The following example defines a unique character string for the T1 interface:
Use the cross-connect command to create a cross-connect map from a created TDM group on an interface
to a virtual interface.
Changing cross-connect settings could potentially result in service interruption.
Syntax Description
<#>Identifies the cross-connect using a number descriptor or label for (useful in
systems that allow multiple cross-connects).
<from interface>Specifies the interface (physical or virt ual) on one end of the cross-connect. Ente r
cross-connect 1 ? for a list of valid interfaces.
<slot/port>Used when a physical interface is specified in the <from interface> subcommand
(For example: specifying the T1 port of a T1 module would be t1 1/1).
<tdm-group#>Specifies which configured TDM group to use for this cross-connect. This
subcommand only applies to T1 physical interfaces.
<to interface>Specifies the virtual interface on the other end of the cross-connect. Use the ? to
display a list of valid interfaces.
<slot/port>Used when a physical interface is specified in the <to interface> subcommand.
(For example, specifying the primary T1 port of a T1 module would be t1 1/1).
Default Values
By default, there are no configured cross-connects.
Applicable Platforms
Applies to all AOS products
Command History
Release 1.1Command was introduced.
Release 5.1Command was expanded to include the E1 interface.
Functional Notes
Cross-connects provide the mechanism for connecting a configured virtual (layer 2) endpoint with a
physical (layer 1) interface. Supported layer 2 protocols include Frame Relay and point-to-point protocol
(PPP).
The following example creates a Frame Relay endpoint and connects it to the T1 1/1 physical interface:
1. Create the Frame Relay virtual endpoint and set the signaling method:
(config)#
(config-fr 1)#
2. Create the sub-interface and configure the PVC parameters (including DLCI and IP address):
(config-fr 1)#
(config-fr 1.1)#
(config-fr 1.1)#
3. Create the TDM group of 12 DS0s (64K) on the T1 physical interface:
(THIS STEP IS ONLY VALID FOR T1 INTERFACES.)
(config)#
(config-t1 1/1)#
(config-t1 1/1)#
4. Connect the Frame Relay sub-interface with port T1 1/1:
(config)#
interface frame-relay 1
frame-relay lmi-type cisco
interface fr 1.1
frame-relay interface-dlci 17
ip address 168.125.33.252 255.255.255.252
interface t1 1/1
tdm-group 1 timeslots 1-12 speed 64
exit
cross-connect 1 t1 1/1 1 fr 1
Technology Review
Creating an endpoint that uses a layer 2 protocol (such as Frame Relay) is generally a four-step process:
Step 1:
Create the Frame Relay virtual endpoint (using the
method (using the
the applicable Frame Relay timers logging thresholds, encapsulation types, etc. Generally, most Frame Relay
virtual interface parameters should be left at their default state. For example, the following creates a Frame
Relay interface labeled
command). Also included in the Frame Relay virtual endpoint are all
interface frame-relay
ansi
.
command) and set the signaling
Command Reference GuideCommon Commands
Step 2:
Create the sub-interface and configure the PVC parameters. Using the sub-interface, apply access policies to
the interface, create bridging interfaces, configure dial-backup, assign an IP address, and set the PVC data-link
control identifier (DLCI). For example, the following creates a Frame Relay sub-interface labeled
DLCI to
frame-relay interface-dlci 30
ip address 193.44.69.253 255.255.255.252
Step 3: (VALID ONLY FOR T1 INTERFACES)
Specify the group of DS0s used for signaling on the T1 interface by creating a TDM group. Group any number of
contiguous DS0s together to create a data pipe for layer 2 signaling. Also use the
specify the per-DS0 signaling rate on the interface. For example, the following creates a TDM group labeled
tdm-group
command to
9
containing 20 DS0s (each DS0 having a data rate of 56 kbps).
(config)#
(config-t1 1/1)#
(config-t1 1/1)#
interface t1 1/1
tdm-group 9 timeslots 1-20 speed 56
exit
Step 4:
Make the association between the layer 2 endpoint and the physical interface using the
cross-connect
command. Supported layer 2 protocols include Frame Relay and point-to-point protocol (PPP). For example, the
following creates a cross-connect (labeled
(
fr 7
) and the TDM group configured on interface t1 1/1 (
(config)#
cross-connect 5 t1 1/1 9 fr 7
5
) to make an association between the Frame Relay virtual interface
Use the do command to execute any AOS command, regardless of the active configuration mode. It
provides a way to execute commands in other modes without taking the time to exit the current mode and
enter the desired one.
Syntax Description
No subcommands.
Default Values
No defaults required for this command.
Applicable Command Modes
Applies to all mode command sets.
Applicable Platforms
Applies to all AOS products.
Command History
Release 2.1Command was introduced.
Functional Notes
Use the do command to view configurations or interface states after config uration changes are made
without exiting to the Enable mode.
Usage Examples
The following example shows the do command used to view the Frame Relay interface configuration while
currently in the T1 Interface Configuratio n mo d e:
(config)#interface t1 1/1
(config-t1 1/1)#do show interfaces fr 7
fr 7 is ACTIVE
Signaling type is ANSI signaling role is USER
Polling interval is 10 seconds full inquiry interval is 6 polling intervals
Output queue: 0/0 (highest/drops)
0 packets input 0 bytes
0 pkts discarded 0 error pkts 0 unknown protocol pkts
0 packets output 0 bytes
0 tx pkts discarded 0 tx error pkts
Use the exit command to exit the current configuration mode and enter the previous one. For example,
using the exit command in an interface configuration mode will activate the Global Configuration mode.
When using the exit command in the Basic mode, the current session will be terminated.
When exiting the Global Configuration mode, remember to perform a copy
running-config startup-config to save all configuration changes.
Syntax Description
No subcommands.
Default Values
No defaults necessary for this command.
Applicable Command Modes
Applies to all mode command sets.
Applicable Platforms
Applies to all AOS products.
Command History
Release 1.1Command was introduced.
Usage Examples
The following example shows the exit command being executed in the Global Configuration mode:
Use the shutdown command to disable the interface (both physical and virtual) so that no data will be
passed through. Use the no form of this command to turn on the interface and allow it to pass data. By
default, all interfaces are disabled.
Syntax Description
No subcommands.
Default Values
By default, all interfaces are disabled.
Applicable Command Modes
Applies to all interface mode command sets.
Applicable Platforms
Applies to all AOS products.
Command History
Release 1.1Command was introduced.
Usage Examples
The following example administratively disables the modem interface:
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 34
All other commands for this command set are described in this section in alphabetical order.
clear commands begin on page 38
clock auto-correct-dst on page 74
clock no-auto-correct-dst on page 75
clock set <time> <day> <month> <year> on page 76
clock timezone <text> on page 77
configure [memory | network | overwrite-network | terminal] on page 80
copy <source> <destination> on page 81
copy console <filename> on page 82
copy flash <destination> on page 83
copy <filename> interface <interface> <slot/port> on page 84
copy tftp <destination> on page 85
copy xmodem <destination> on page 86
debug commands begin on page 87
dir on page 134
dir [<input> | flash | flash <input>] on page 135
disable on page 136
enable on page 137
erase [<filename> | startup-config] on page 138
events on page 139
exception report generate on page 140
logout on page 141
ping <address> on page 142
reload [cancel | in <delay>] on page 144
show commands begin on page 145
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.
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 autonomous system (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 neighb or, 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 neighb or changes, including cha nges to prefix- list filters, do not take ef fect 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 clear ing is disruptive and causes peer routers to record a route
flap for each route.
The out version of this command provides a soft reset ou t 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.
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 betwe en a MAC address and an IP address that was
offered by the unit to a DHCP client (i.e., most o ften a PC). Clearing a bi nding allows the unit to of fer that IP
address again, should a request be made for on e .
Usage Examples
The following example clears a DHCP server binding for the IP address 125.25.47.4:
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).
ahp Specifies authentication header protocol (AHP).
esp Specifies encapsulating security payload protocol (ESP).
gre Specifies general routing encapsulation protocol (GRE).
icmp Specifies Internet control message protocol (ICMP) protocol.
tcp Specifies transmission control protocol (TCP).
udp Specifies universal datagram protocol (UDP).
<protocol>Specifies protocol ( va lid range: 0 to 255).
<source ip>Specifies the source IP address (format is A.B.C.D).
<source port>Specifies the source port (in hex format AHP, ESP , an d GRE; decimal for all othe r
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 fo rmat 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.
The second half of this command, beginning with the source IP address may be copied and p asted from a
row in the show ip policy-sessions table for easier use.
Usage Examples
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 219 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 connec ted
routes are not cleared by this command.
Syntax Description
**Deletes all destination routes.
<ip address>Specifies the IP address of the destination routes to be deleted.
<subnet mask>Specifies 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 local
loop demarkation point (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 del eted from the data base 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 quality of service (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 tha t 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
interface <interface id>Optional. Specifies a valid interface to clear. Type clear spanning-tree
detected-protocols 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, 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:
clear user [console <user number> | ssh <user number> |
telnet <user number>]
Use the clear user command to detach a user from a given line.
Syntax Description
console <user number> Detaches a specific console user. Valid range is 0 to 1.
ssh <user number>Detaches a specific secure shell (SSH) user. Valid range is 0 to 4.
telnet <user number>Detaches a specific Telnet user. Valid range is 0 to 5.
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 11.1Command was introduced.
Usage Examples
The following example detaches the console 1 user:
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.
Command History
Release 6.1Command was introduced.
Release 11.1Command was expanded to include clock timezone 0.
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 268 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 to copy.
Valid sources include: running-config (current runnin g co nfig ura tio n 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.
Command History
Release 1.1Command was introduced.
Usage Examples
The following example creates a copy of the file myfile.biz (located in FLASH memory) and names it
newfile.biz:
>enable
#copy myfile.biz newfile.biz
The following example creates a backup copy of the startup configuration file (and places in FLASH
memory):
>enable
#copy startup-config backup.bak
The following example copies the current running-configuration file to the startup configuration file located
in NVRAM:
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 ro ot directory):
Use the copy interface command to copy a file to a specified interface.
Syntax Description
<filename>Specifies file name of so urce file to copy.
<interface>Specifies interface to be upgraded.
<slot/port>Specifies slot and port number of interface.
Default Values
No default is 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 8.1Command was introduced.
Usage Examples
The following example upgrades the ADSL interface with the firmware file configfile:
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 atm events command to display events on all ATM ports and all virtual circuits. 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, and 4000 Series units.
Command History
Release 8.1Command was introduced.
Usage Examples
The following example activates ATM event messages:
Use the debug atm oam command to display Op eration, Administration, and Maintenance (OAM) packets
for an ATM virtual circuit descriptor (VCD). Debug messages are displayed (real time) to the terminal (or
Telnet) screen. Use the no form of this command to disable debug messages.
Use the debug atm packet command to activate debug messages associated with packets on ATM ports
and virtual circuits. Debug messages are displayed (real time) to the terminal (or Telnet) screen. Use the no
form of this command to disable the debug messages.
interface atm <port id>Shows packets on a specific ATM port and on all virtual circuits.
vc <VPI/VCI>Shows packets on a specific virtual circuit identified by the virtual path
identifier and virtual channel identifier (VPI/VCI).
vcd <vcd number>Shows packets on specific virtual circuit descriptors (VCD).
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000R, 3000, and 4000 Series units.
Command History
Release 8.1Command was introduced.
Usage Examples
The following example activates debug ATM packet debug messages on ATM port 1:
Use the debug auto-config command to activate debug messages associated auto-config events. 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 11.1Command was introduced.
Usage Examples
The example activates debug messages associated with auto-config events:
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:
Use the debug chat-interfaces command to activate debug messages associated with chat AT command
driven interfaces. 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
<chat interface>Specifies the chat interface to debug in slot/port format.
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 Series units.
Command History
Release 11.1Command was introduced.
Usage Examples
The following example activates debug messages for the chat interface 0/1:
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 public key infrastructure (PKI) 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 data-call command to activate debug messages associated with data call errors and events.
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 11.1Command was introduced.
Usage Examples
The following example activates debug messages associated with data call errors and events:
Use the debug demand-routing command to activate debug messages associated with demand routing
errors and 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 1000R, 3000, 4000, and 5000 Series units.
Command History
Release 11.1Command was introduced.
Usage Examples
The following example activates demand routing error and event messages:
Use the debug dial-backup command to activate debug messages associated with dial-backup 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 1000R, 3000, 4000, and 5000 Series units.
Command History
Release 1.1Command was introduced.
Release 2.1Additional debug messages were implemented for dial-backup operation to
ADTRAN’s IQ and Express Series products.
Functional Notes
The debug dial-backup command activates debug messa ges to aid in th e troub lesho oting of d ial- backup
links.
Usage Examples
The following example activates debug messages for dial-backup operatio n:
Use the debug dialup-interfaces command to generate debug messages used to aid in troubleshooting
problems with all dialup interfaces such as the modem or the BRI cards. 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 1000R, 3000, 4000, and 5000 Series units.
Command History
Release 2.1Command was introduced.
Functional Notes
When enabled, these messages provide status information on incoming calls, dialing and answering
progress, etc. These messages also giv e info r ma tio n on why certain calls are dropped or rejected. It is
beneficial to use this command when troubleshooting dial backup (in addition to the debug dial-backup
command).
Usage Examples
The following example activates the debug messages for dialup interfaces:
Use the debug dynamic-dns command to display debug messages associated with dynamic domain
naming system (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
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, 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: