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 1000 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 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.
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 34
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 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 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 14
Common Commands on page 24
Enable Mode Command Set on page 34
Global Configuration Mode Command Set on page 205
Line Interface Command Sets
Line (Console) Interface Config Command Set on page 344
Line (SSH) Interface Config Command Set on page 357
Line (Telnet) Interface Config Command Set on page 365
Physical Interface Command Sets
Ethernet Interface Configuration Command Set on page 374
Virtual Interface Command Sets
Loopback Interface Configuration Command Set on page 419
Port Channel Interface Config Command Set on page 432
VLAN Configuration Command Set on page 456
VLAN Database Configuration Command Set on page 460
VLAN Interface Config Command Set on page 469
Security and Services Command Sets
DHCP Pool Command Set on page 481
Radius Group Command Set on page 499
TACACS+ Group Configuration Command Set on page 501
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 32
All other commands for this command set are described in this section in alphabetical order.
enable on page 15
logout on page 16
ping <address> on page 17
show clock on page 19
show snmp on page 20
show version on page 21
telnet <address> on page 22
traceroute <address> on page 23
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 34
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 238 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 59 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 32
All other commands for this command set are described in this section in alphabetical order.
clear commands begin on page 36
clock auto-correct-dst on page 57
clock no-auto-correct-dst on page 58
clock set <time> <day> <month> <year> on page 59
clock timezone <text> on page 60
configure [memory | network | overwrite-network | terminal] on page 63
copy <source> <destination> on page 64
copy console <filename> on page 65
copy flash <destination> on page 66
copy tftp <destination> on page 67
copy xmodem <destination> on page 68
debug commands begin on page 69
dir on page 97
dir [<input> | flash | flash <input>] on page 98
disable on page 99
enable on page 100
erase [<filename> | startup-config] on page 101
events on page 102
exception report generate on page 103
logout on page 104
ping <address> on page 105
ping stack-member on page 107
reload [cancel | in <delay>] on page 108
show commands begin on page 109
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):
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:
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
#
clear mac address-table dynamic [address <mac address> |
<interface id>]
Use the clear mac address-table dynamic command to remove dynamic media access control (MAC)
addresses from the MAC address table.
Syntax Description
address
<interface id>
<mac address>
Removes a specific MAC address from the table (format: AA:AA:AA:AA:AA:AA).
Removes the MAC address of a specific interface. T ype clear mac address-t able
dynamic 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, and 1000R Series units.
Command History
Release 5.1Command was introduced.
Usage Examples
The following example removes the dynamic address A0:B1:C2:D3:E4:A1 from the MAC address table:
>enable
#clear mac address-table dynamic add ress A0:B1:C2:D3:E4:A1
The following example removes all dynamic addresses from the MAC address table:
Use the clear port-security command to clear the dynamic or sticky secure media access control (MAC)
addresses associated with an interface. This can be done on a per-address or per-port basis. Variations of
this command include the following:
dynamicClears the dynamic MAC addresses.
stickyClears the sticky secure MAC addresses.
address <address>Clears the information for the specified address.
interface <interface id> Clears the information for the specified interface. Type clear port-security sticky
interface ? or clear port-security dynamic 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, and 1000R Series units.
Command History
Release 8.1Command was introduced.
Usage Examples
The following command clears all dynamic secure MAC addresses associated with the Ethernet interface
0/1:
>enable
#clear port-security dynamic interface eth 0/1
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 205 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 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 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 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 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:
Use the debug gvrp bpdus command to see debug messages showing all GARP VLAN Registration
Protocol (GVRP) configuration messages sent and received on the switch. 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, and 1000R Series units.
Command History
Release 8.1Command was introduced.
Functional Notes
With GVRP enabled on many ports, this command can produce a lot of output. To see these messages
just for individual interfaces, refer to the command
page 74
.
debug gvrp interface <interface> [bpdus | vlans] on
Usage Examples
The following example displays debug messages showing GVRP configuration messages sent and
received on Ethernet interface 0/24:
Use the debug gvrp interface command to see GARP VLAN Registration Protocol (GVRP) debug
messages related to a particular interface. 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
<interface> Activates debug messages for the specified interface. Type debug gvrp
interface ? for a complete list of applicable interfaces.
bpdusDisplays debug messages showing all GVRP configuration messages sent and
received on the interface.
vlansDisplays debug messages showing all GVRP-related VL AN changes occurring on
the interface.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, and 1000R Series units.
Command History
Release 8.1Command was introduced.
Usage Examples
The following example displays debug messages showing GVRP configuration messages sent and
received on Ethernet interface 0/24:
Use the debug gvrp vlans command to see debug messages showing all GARP VLAN Registration
Protocol (GVRP) VLAN changes. 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
<vlan number>Optional. Displays debug message s showing all GVRP-related VLAN changes for
this VLAN only . Range is 1 to 4094.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 300, 1000, and 1000R Series units.
Command History
Release 8.1Command was introduced.
Functional Notes
With GVRP enabled on many ports, this command can produce a lot of output. To see these messages
just for individual interfaces, refer to the command
page 74
.
debug gvrp interface <interface> [bpdus | vlans] on
Usage Examples
The following example displays debug messages showing GVRP-related VLAN changes for VLAN 1:
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:
Use the debug ip dhcp-client command to activate debug messages associated with Dynamic Host
Configuration Protocol (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 Dynamic Host
Configuration Protocol (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 domain naming system
(DNS) 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 domain naming system
(DNS) 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 informatio n 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 HyperText Transfer Protocol
(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 Internet Control Message Protocol (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. 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
send
recv
Optional. Displays only ICMP messages sent by the router.
Optional. Displays only 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. 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 10.1Command was introduced.
Usage Examples
The following sample activates ip mrouting debug messages:
Use the debug ip tcp events command to activate debug messages associated with significant
Transmission Control Protocol (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 st ands 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 udp command to activate debug messages associated with User Datagram Protocol
(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).
Use the debug lldp command to display debug output for all local loop demarkation point (LLDP) receive
and transmit packets. Use the no version of this command to disable it. Debug messages are displayed (real
time) on the terminal (or Telnet) screen. Use the no form of this command to disable the debug messa ges.
Syntax Description
rxShows information about received packets.
txShows information about transmitted packets.
verboseShows detailed debugging information.
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 all possible debug messages associated with LLDP operation:
Use the debug port-auth command to generate debug messages used to aid in troubleshooting problems
during the port authentication process. 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
generalOptional. Displays configuration changes to the port authentication system.
packet bothOptional. Displays packet exchange information in both receive and transmit
directions.
packet rxOptional. Displays packet exchange information in the receive-only direction.
packet txOptional. Displays packet exchange information in the transmit-only direction.
auth-smOptional. Displays AuthPAE-state machine information.
bkendOptional. Displays backend-state machine information.
reauth-smOptional. Displays reauthentication-state machine information.
supp-smOptional. Displays supplicant-state machine information.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 1000, 1000R, 3000, 4000, and 5000 Series units.
Command History
Release 9.1Command was introduced.
Release 10.1New options were introduced.
Usage Examples
The following example activates port authentication debug informatio n on received packets:
>enable
#debug port-auth packet rx
Rcvd EAPOL Start for sess 1 on int eth 0/2
Use the debug port security command to display messages associated with port security. 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, 1000, and 1000R Series units.
Command History
Release 8.1Command was introduced.
Usage Examples
The following example activates port security debug messages:
Use the debug radius command to enable debug messages from the RADIUS subsystem. 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 5.1Command was introduced.
Functional Notes
The debug radius messages show the communication process with the remote RADIUS servers.
Usage Examples
The following is an example output for the debug radius command:
>enable
#debug radius
RADIUS AUTHENTICATION: Sending packet to 172.22.48.1 (1645).
RADIUS AUTHENTICATION: Received response from 172.22.48.1.
Use the debug sntp command to enable debug messages associated with the Simple Network Time
Protocol (SNTP). All SNTP packet exchanges and time decisions are displayed with these debugging
events enabled. 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 sntp command activates debug messages to aid in troubleshooting SNTP protocol issues.
Usage Examples
The following is an example output for the debug sntp command:
>enable
#debug sntp
#config term
(config)#sntp server timeserver.localdomain
2002.12.11 15:06:37 SNTP.CLIENT sent Version 1 SNTP time request to 63.97.45.57
2002.12.11 15:06:37 SNTP.CLIENT received SNTP reply packet from 63.97.45.57
2002.12.11 15:06:37 SNTP.CLIENT setting time to 12-11-2002 15:06:02 UTC
2002.12.11 15:06:37 SNTP.CLIENT waiting for 86400 seconds for the next poll interval
Use the debug spanning-tree bpdu command to display bridge protocol data unit (BPDU) debug
messages. When enabled, a debug message is displayed for each BPDU packet that is transmitted or
received by the unit. 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
receiveDisplays debug messages for BPDU packets received by the unit.
transmitDisplays debug messages for BPDU packets transmitted by the unit.
allDisplays debug messages for BPDU packets that are transmitted and received by
the unit.
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.
Usage Examples
The following example displays debug messages for BPDU packets that are transmitted and received by
the unit:
debug spanning-tree [config | events | general | root]
Use the debug spanning-tree command to enable the display of spanning-tree debug messages. 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
configEnables the display of spanning-tree debug messages when configuration
changes occur.
eventsEnables the display of debug messages when spanning-tree protocol events
occur.
generalEnables the display of general spanning-tree debug messages.
rootEnables the display of debug messages related to the spanning-tree root.
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.
Usage Examples
The following example enables the display of general spanning-tree debug messages:
Use the debug stack command to enable switch-stacking debug messages. 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
SW_APIEnables messages specific to the stack ports.
verboseEnables messages specific to the stack protocol.
Default Values
By default, all debug messages in the AOS are disabled.
Applicable Platforms
This command applies to the NetVanta 1000 and 1000R Series units.
Command History
Release 8.1Command was introduced.
Usage Examples
The following example activates the possible debug stack messages:
Use the debug system command to enable debug messages associated with system events (i.e., login,
logouts, etc.). 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.
Usage Examples
The following example activates debug messages associated with system information:
Use the enable command to enter a password for the Enable mode.
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 10.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 238 for more information.
Usage Examples
The following example enters the Enable Command mode and defines an Enable Command mode
password: