Maintenance Help

Configuration

The switch stores its configuration in a number of text files in CLI format. The files are either virtual (RAM-based) or stored in flash on the switch.

The available files are:

running-config: A virtual file that represents the currently active configuration on the switch. This file is volatile.
startup-config: The startup configuration for the switch, read at boot time. If this file doesn't exist at boot time, the switch will start up in default configuration.
default-config: A read-only file with vendor-specific configuration. This file is read when the system is restored to default settings.
Up to other files, typically used for configuration backups or alternative configurations.

Save startup-config

This copies running-config to startup-config, thereby ensuring that the currently active configuration will be used at the next reboot.

It is possible to download any of the files on the switch to the web browser. Select the file and click .
Download of running-config may take a little while to complete, as the file must be prepared for download.

Upload

It is possible to upload a file from the web browser to all the files on the switch, except default-config which is read-only.
Select the file to upload, select the destination file on the target, then click .

If the destination is running-config, the file will be applied to the switch configuration. This can be done in two ways:

Replace mode: The current configuration is fully replaced with the configuration in the uploaded file.
Merge mode: The uploaded file is merged into running-config.

If the flash file system is full (i.e. contains default-config and other files, usually including startup-config), it is not possible to create new files. Instead an existing file must be overwritten or another file must be deleted.

Activate

It is possible to activate any of the configuration files present on the switch, except for running-config which represents the currently active configuration.
Select the file to activate and click . This will initiate the process of completely replacing the existing configuration with that of the selected file.

Delete

It is possible to delete any of the writable files stored in flash, including startup-config. If this is done and the switch is rebooted without a prior Save operation, this effectively resets the switch to default configuration.

Diagnostics Help

Ping

This page allows you to issue ICMP PING packets to troubleshoot IP connectivity issues.

After you press , ICMP packets are transmitted, and the sequence number and round trip time are displayed upon reception of a reply. The amount of data received inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes more than the requested data space(the ICMP header). The page refreshes automatically until responses to all packets are received, or until a timeout occurs.

PING server 10.10.132.20, 56 bytes of data.
64 bytes from 10.10.132.20: icmp_seq=0, time=10ms
64 bytes from 10.10.132.20: icmp_seq=1, time=10ms
64 bytes from 10.10.132.20: icmp_seq=2, time=10ms
64 bytes from 10.10.132.20: icmp_seq=3, time=10ms
64 bytes from 10.10.132.20: icmp_seq=4, time=10ms
Sent 5 packets, received 5 OK, 0 bad

Link OAM MIB Retrieval

This page allows you to retrieve the local or remote OAM MIB variable data on a particular port. Select the appropriate radio button and enter the port number of the switch to retrieve the content of interest. Click on to retrieve the content. Click on to retrieve another content of interest.

Ping6

This page allows you to issue ICMPv6 PING packets to troubleshoot IPv6 connectivity issues.

After you press , ICMPv6 packets are transmitted, and the sequence number and round trip time are displayed upon reception of a reply. The page refreshes automatically until responses to all packets are received, or until a timeout occurs.

PING6 server ff02::2, 56 bytes of data.
64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=0, time=10ms
64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=0, time=10ms
64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=1, time=10ms
64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=1, time=10ms
64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=2, time=10ms
64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=2, time=10ms
64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=3, time=10ms
64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=3, time=10ms
64 bytes from fe80::219:5bff:fe2f:b47: icmp_seq=4, time=10ms
64 bytes from fe80::215:58ff:feed:69dd: icmp_seq=4, time=10ms
Sent 5 packets, received 10 OK, 0 bad

You can configure the following properties of the issued ICMP packets:

IP Address: The destination IP Address.
Ping Length: The payload size of the ICMP packet. Values range from 2 bytes to 1452 bytes.
Ping Count: The count of the ICMP packet. Values range from 1 time to 60 times.
Ping Interval: The interval of the ICMP packet. Values range from 1 second to 30 seconds.
Egress Interface (Only for IPv6): The VLAN ID (VID) of the specific egress IPv6 interface which ICMP packet goes.
The given VID ranges from 1 to 4095 and will be effective only when the corresponding IPv6 interface is valid.
When the egress interface is not given, PING6 finds the best match interface for destination.
Do not specify egress interface for loopback address.
Do specify egress interface for link-local or multicast address.

Traceroute

This page allows you to issue ICMP, TCP, or UDP packets to diagnose network connectivity issues.

After you press , Traceroute sends packets with gradually increasing TTL value, starting with TTL value of 1. The first router receives the packet, decrements the TTL value and drops the packet because it then has TTL value zero. The router sends an ICMP Time Exceeded message back to the source. The next set of packets are given a TTL value of 2, so the first router forwards the packets, but the second router drops them and replies with ICMP Time Exceeded. Proceeding in this way, traceroute uses the returned ICMP Time Exceeded messages to build a list of routers that packets traverse, until the destination is reached and returns an ICMP Echo Reply message.

traceroute to 202.39.253.11 (202.39.253.11), 30 hops max, 40 byte packets
1 192.168.10.254 ae-2-3508.edge4.Atlanta2.Level3.net. (192.168.10.254) 10 ms 10 ms 10 ms
2 59-125-13-254.HINET-IP.hinet.net. (59.125.13.254) 20 ms 20 ms 20 ms
3 h146.s228.ts.hinet.net. (168.95.228.146) 20 ms 10 ms 20 ms
4 tchn-3011.hinet.net. (220.128.16.194) 20 ms TCHN-3112.hinet.net. (220.128.17.142) 20 ms tchn-3011.hinet.net. (220.128.16.202) 20 ms
5 TPDT-3012.hinet.net. (220.128.17.6) 20 ms TPDT-3011.hinet.net. (220.128.16.10) 20 ms TPDT-3012.hinet.net. (220.128.17.6) 40 ms
6 CHCH-3112.hinet.net. (220.128.2.13) 20 ms tchn-3011.hinet.net. (220.128.1.9) 10 ms CHCH-3112.hinet.net. (220.128.2.13) 30 ms
7 211.22.41.237 CHCH-3112.hinet.net. (211.22.41.237) 20 ms 30 ms 30 ms
8 202-39-253-11.HINET-IP.hinet.net. (202.39.253.11) 10 ms 10 ms

You can configure the following properties:

Protocol: The protocol(ICMP, UDP, TCP) packets to send.
IP Address: The destination IP Address.
Wait Time: Set the time (in seconds) to wait for a response to a probe (default 5.0 sec). Values range from 1 to 60. The payload size of the ICMP packet. Values range from 2 bytes to 1452 bytes.
Max TTL: Specifies the maximum number of hops (max time-to-live value) traceroute will probe. Values range from 1 to 255. The default is 30.
Probe Count: Sets the number of probe packets per hop. Values range from 1 to 10. The default is 3.

Buttons

: Click to start transmitting ICMP packets.

: Click to re-start diagnostics with PING.