System Utility and Clear Commands

This section describes the commands you use to help troubleshoot connectivity issues and to restore various configurations to their factory defaults.

traceroute

Use the traceroute command to discover the routes that packets actually take when traveling to their destination through the network on a hop-by-hop basis. Traceroute continues to provide a synchronous response when initiated from the CLI.

The user may specify the source IP address of the traceroute probes. Recall that traceroute works by sending packets that are expected not to reach their final destination, but instead trigger ICMP error messages back to the source address from each hop along the forward path to the destination. By specifying the source address, the user can determine where along the forward path there is no route back to the source address. Note that this is only useful if the route from source to destination and destination to source is symmetric.) It would be common, for example, to send a traceroute from an edge router to a target higher in the network using a source address from a host subnet on the edge router. This would test reachability from within the network back to hosts attached to the edge router. Alternatively, one might send a traceroute with an address on a loopback interface as a source to test reachability back to the loopback interface address.

In the CLI, the user may specify the source either as an IPv4 address or as a routing interface. When the source is specified as a routing interface, the traceroute is sent using the primary IPv4 address on the source interface. With SNMP, the source must be specified as an address. The source cannot be specified in the web UI.

The software will not accept an incoming packet, such as a traceroute response, that arrives on a routing interface if the packet's destination address is on one of the out-of-band management interfaces (service port or network port). Similarly, the software will not accept a packet that arrives on a management interface if the packet's destination is an address on a routing interface. Thus, it would be futile to send a traceroute on a management interface using a routing interface address as source, or to send a traceroute on a routing interface using a management interface as source. When sending a traceroute on a routing interface, the source must be that routing interface or another routing interface. When sending a traceroute on a management interface, the source must be on that management interface. For this reason, the user cannot specify the source as a management interface or management interface address. When sending a traceroute on a management interface, the user should not specify a source address, but instead let the system select the source address from the outgoing interface.

Default
- count: 3 probes
- interval: 3 seconds
- size: 0 bytes
- port: 33434
- maxTtl: 30 hops
- maxFail: 5 probes
- initTtl: 1 hop
Format: traceroute {<ipaddr|hostname>} [initTtl <initTtl>] [maxTtl <maxTtl>] [maxFail <maxFail>] [interval <interval>] [count <count>] [port <port>] [size <size>] [source {<ip-address|interface>}]
Mode: Privileged EXEC

Using the options described below, you can specify the initial and maximum time-to-live (TTL) in probe packets, the maximum number of failures before termination, the number of probes sent for each TTL, and the size of each probe.

ipaddr/hostname: The <ipaddr>value should be a valid IP address. The <hostname> value should be a valid hostname.
initTtl: Use initTtl to specify the initial time-to-live (TTL), the maximum number of router hops between the local and remote system. Range is 0 to 255.
maxTtl: Use maxTtle to specify the maximum TTL. Range is 1 to 255.
maxFail: Use maxFail to terminate the traceroute after failing to receive a response for this number of consecutive probes. Range is 0 to 255.
interval: Use the optional interval parameter to specify the time between probes, in seconds. If a response is not received within this interval, then traceroute considers that probe a failure (printing *) and sends the next probe. If traceroute does receive a response to a probe within this interval, then it sends the next probe immediately. Range is 1 to 60 seconds.
count: Use the optional count parameter to specify the number of probes to send for each TTL value. Range is 1 to 10 probes.
port: Use the optional port parameter to specify destination UDP port of the probe. This should be an unused port on the remote destination system. Range is 1 to 65535.
size: Use the optional size parameter to specify the size, in bytes, of the payload of the Echo Requests sent. Range is 0 to 65507 bytes.
source: Use the optional source parameter to specify the source IP address or interface for the traceroute.

traceroute ipv6

Use the traceroute command to discover the routes that packets actually take when traveling to their destination through the network on a hop-by-hop basis. The {<ipv6-address> | <hostname>} parameter must be a valid IPv6 address or hostname. The optional <port> parameter is the UDP port used as the destination of packets sent as part of the traceroute. This port should be an unused port on the destination system. The range for <port> is zero (0) to 65535. The default value is 33434.

Default: port: 33434
Format: traceroute ipv6 {<ipv6-address> | <hostname>} [port <port>]
Mode: Privileged EXEC

clear config

This command resets the configuration to the factory defaults without powering off the switch. When you issue this command, a prompt appears to confirm that the reset should proceed. When you enter y, you automatically reset the current configuration on the switch to the default values. It does not reset the switch.

Format: clear config
Mode: Privileged EXEC

clear counters

This command clears the statistics for a specified <unit/slot/port>, for all the ports, or for the entire switch based upon the argument.

Format: clear counters {<unit/slot/port> | all}
Mode: Privileged EXEC

clear igmpsnooping

This command clears the tables managed by the IGMP Snooping function and attempts to delete these entries from the Multicast Forwarding Database.

Format: clear igmpsnooping
Mode: Privileged EXEC

clear pass

This command resets all user passwords to the factory defaults without powering off the switch. You are prompted to confirm that the password reset should proceed.

Format: clear pass
Mode: Privileged EXEC

clear traplog

This command clears the trap log.

Format: clear traplog
Mode: Privileged EXEC

clear vlan

This command resets VLAN configuration parameters to the factory defaults. When the VLAN configuration is reset to the factory defaults, there are some scenarios regarding GVRP and MVRP that happen due to this:

Static VLANs are deleted.
GVRP is restored to the factory default as a result of handling the VLAN RESTORE NOTIFY event. Since GVRP is disabled by default, this means that GVRP should be disabled and all of its dynamic VLANs should be deleted.
MVRP is restored to the factory default as a result of handling the VLAN RESTORE NOTIFY event. Since MVRP is enabled by default, this means that any VLANs already created by MVRP are unaffected. However, for customer platforms where MVRP is disabled by default, then the MVRP behavior should match GVRP. That is, MVRP is disabled and the MVRP VLANs are deleted.

Format: clear vlan
Mode: Privileged EXEC

logout

This command closes the current telnet connection or resets the current serial connection.

NOTE: Save configuration changes before logging out.

Format: logout
Modes:
- Privileged EXEC
- User EXEC

ping

Use this command to determine whether another computer is on the network. Ping provides a synchronous response when initiated from the CLI and Web interfaces.

Default
- The default count is 1.
- The default interval is 3 seconds.
- The default size is 0 bytes
Format: ping {<ipaddress> | <hostname>}[count <count>] [interval <interval>] [size <size>]
Modes:
- Privileged EXEC
- User EXEC

Using the options described below, you can specify the number and size of Echo Requests and the interval between Echo Requests.

count: Use the count parameter to specify the number of ping packets (ICMP Echo requests) that are sent to the destination address specified by the <ip address>field. The range for <count> is 1 to 15 requests.
interval: Use the interval parameter to specify the time between Echo Requests, in seconds. Range is 1 to 60 seconds.
size: Use the size parameter to specify the size, in bytes, of the payload of the Echo Requests sent. Range is 0 to 65507 bytes.

quit

This command closes the current telnet connection or resets the current serial connection. The system asks you whether to save configuration changes before quitting.

Format: quit
Modes:
- Privileged EXEC
- User EXEC

reload

This command resets the switch without powering it off. Reset means that all network connections are terminated and the boot code executes. The switch uses the stored configuration to initialize the switch. You are prompted to confirm that the reset should proceed. The LEDs on the switch indicate a successful reset.

Format: reload
Mode: Privileged EXEC

boot system active/backup [autorestart | autosaveandrestart]

To auto reboot of system while invoking active/backup image

Format: boot system active autorestart To restart the system without saving the unsaved changes (config)
Format: boot system active autosaveandrestart To restart the system after saving unsaved changes (config)
Mode: Privileged EXEC.

copy

The copy command uploads and downloads files to and from the switch. You can also use the copy command to manage the dual images (image1 and image2) on the file system. Upload and download files from a server by using TFTP or Xmodem. SFTP and SCP are available as additional transfer methods if the software package supports secure management.

Format: copy <url>/<source> <destination>
Mode: Privileged EXEC

Replace the <source> and <destination> parameters with the options in Table below. For the <url> source or destination, use one of the following values: {xmodem | tftp://<ipaddr>|<ip6address>/<filepath>/<filename>[noval]| sftp|scp://<username>:<passwd>@<ipaddr|hostname>/<filepath>/<filename>}

The keyword ias-users supports the downloading of the IAS user database file. When the IAS users file is downloaded, the switch IAS user's database is replaced with the users and its attributes available in the downloaded file. In the command copy url ias-users, for url one of the following is used for IAS users file:

{ { tftp://<ipaddr | hostname> | <ipv6address | hostname> /<filepath>/<filename> } | { sftp | scp:// <username>:<passwd>@<ipaddr|hostname>/<filepath>/<filename>}

NOTE: The maximum length for the file path is 160 characters, and the maximum length for the file name is 31 characters

For TFTP, SFTP and SCP, the <ipaddr/hostname> parameter is the IP address or host name of the server, <filepath> is the path to the file, and <username> is the name of the file you want to upload or download. For SFTP and SCP, the <username> parameter is the username for logging into the remote server via SSH. <passwd> string is added for SFTP and SCP.

NOTE: <ip6address> is also a valid parameter for routing packages that support IPv6

Table below describes copy Parameters.

Copy Parameters

Source	Destination	Description
nvram:backup-config	nvram:startup-config	Copies the backup configuration to the startup configuration.
nvram:clibanner	<url>	Copies the CLI banner to a server.
nvram:errorlog	<url>	Copies the error log file to a server.
nvram:tejos.cfg	<url>	Uploads the binary config file to a server.
nvram:log	<url>	Copies the log file to a server.
nvram:script <scriptname>	<url>	Copies a specified configuration script file to a server.
nvram:startup-config	<url>	Copies the startup configuration to a server.
nvram:traplog	<url>	Copies the trap log file to a server.
system:running-config	nvram:startup-config	Saves the running configuration to nvram
<url>	nvram:clibanner	Downloads the CLI banner to the system.
<url>	nvram:tejos.cfg	Downloads the binary config file to the system.
<url>	nvram:script<destfilename>	Downloads a configuration script file to the system. During the download of a configuration script, the copy command validates the script. In case of any error, the command lists all the lines at the end of the validation process and prompts you to confirm before copying the script file.
<url>	nvram:script <destfilename> noval	When you use this option, the copy command will not validate the downloaded script file.
<url>	nvram:sshkey-dsa	Downloads an SSH key file. For more information, see Secure Shell Commands.
<url>	nvram:sshkey-rsa1	Downloads an SSH key file.
<url>	nvram:sshkey-rsa2	Downloads an SSH key file.
<url>	nvram:sslpem-dhweak	Downloads an HTTP secure-server certificate.
<url>	nvram:sslpemdhstrong	Downloads an HTTP secure-server certificate.
<url>	nvram:sslpem-root	Downloads an HTTP secure-server certificate.For more information, see Secure Shell Commands.
<url>	nvram:sslpem-server	Downloads an HTTP secure-server certificate.
<url>	nvram:startup-config	Downloads the startup configuration file to the system.
<url>	nvram:system-image	Downloads a code image to the system.
<url>	kernel	Downloads kernel file by xmodem, ymodem, zmodem, sftp, scp or tftp to the system.
<url>	ias-users	Downloads an IAS users database file to the system. When the IAS users file is downloaded, the switch IAS user’s database is replaced with the users and their attributes available in the downloaded file.
<url>	{active \| backup}	Download an image from the remote server to either image. In a stacking environment, the downloaded image is distributed to the stack nodes.
{active \| backup}	<url>	Upload either image to the remote server.
active	backup	Copy the active image to the backup image.
backup	active	Copy the backup image to the active image.
{active \| backup}	{active \| backup} unit://<unit>/{active \| backup}	Copy an image from the management node to a given node in a Stack. Use the unit parameter to specify the node to which the image should be copied.
{active \| backup}	unit://*/{active \| backup}	Copy an image from the management node to all of the nodes in a Stack.

Copy <url>

As part of URL “password ” string is added for scp and sftp instead of separate user entry.

Format: scp://<user>:<passwd>@<ipaddr|hostname>/<path>/<filename>
sftp://<user>:<passwd>@<ipaddr|hostname>/<path>/<filename>
Mode: Privileged EXEC