Page 701 / 757 Scroll up to view Page 696 - 700
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
697
97
TRACE ROUTE COMMANDS
The Trace Route commands in the Command Line Interface (CLI) are listed (along with the appropriate parameters) in
the following table.
Command
Parameters
traceroute
[<ipaddr> | <domain_name 255>] {ttl <value 1-60> | port <value 30000-64900> |
timeout <sec 1-65535> | probe <value 1-9>}
traceroute6
<ipv6addr> {ttl <value 1-60> | port <value 30000-64900> | timeout <sec 1-
65535> | probe <value 1-9>}
Each command is listed, in detail, in the following sections.
traceroute
Purpose
This command is used to trace the routed path between the switch and a destination end
station.
Syntax
traceroute [<ipaddr> | <domain_name 255>] {ttl <value 1-60> | port <value 30000-
64900> | timeout <sec 1-65535> | probe <value 1-9>}
Description
To track the route of an IP packet, traceroute launches UDP probe packets with a small TTL
(time to live) and then listens for an ICMP "time exceeded" reply from a gateway. Probes start
with a TTL of one and increase by one until either an ICMP "port unreachable" is returned,
indicating that the packet reached the host, or the maximum number of hops is exceeded. At
each TTL setting, one probe packet is launched (the number can be changed by specifying
the parameter “probe”) and traceroute prints a line showing the round trip time and the
address of the gateway of each probe, or time out of each probe. If there is no response
within the 5 seconds timeout interval, an asterisk (*) is printed for that probe.
Parameters
ipaddr
- IP address of the destination end station.
<domain_name 255>
- The domain name of the destination end station.
ttl <value 1-60>
- The time to live value of the trace route request. This is the maximum
number of routers that a trace route packet can cross, while seeking the network path
between two devices. The range for the TTL is 1 to 60 hops.
port <value 30000–64900>
- Specify the destination UDP port number. The UDP port range
is from 30000 to 64900.
timeout <sec 1-65535>
- Define the timeout period while waiting for a response from the
remote device. A value of 1 to 65535 seconds can be specified. The default is 5 seconds.
probe <value 1-9>
- Specify the number of probe packets for each TTL. The default is 1.
Note:
The probe will be terminated once the destination is reached.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To trace the routed path between the switch and 10.48.74.121:
Page 702 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
698
DGS-3627:admin# traceroute 10.48.74.121 probe 3
Command: traceroute 10.48.74.121 probe 3
<10 ms
10.12.73.254
<10 ms
10.12.73.254
<10 ms
10.12.73.254
<10 ms
10.19.68.1
<10 ms
10.19.68.1
*
Request timed out.
<10 ms
10.48.74.121
Trace complete.
DGS-3627:admin#
To trace the routed path between the switch and intra.example.com:
DGS-3627:admin# traceroute intra.example.com timeout 10
Command: traceroute intra.example.com timeout 10
<10 ms
10.12.73.254
<10 ms
10.19.68.1
<10 ms
intra.example.com [10.48.74.100]
Trace complete.
DGS-3627:admin#
traceroute6
Purpose
This command is used to trace the IPv6 routed path between the switch and a destination
end station.
Syntax
traceroute6 <ipv6addr> {ttl <value 1-60> | port <value 30000-64900> | timeout <sec 1-
65535> | probe <value 1-9>}
Description
To track the route of an IPv6 packet, traceroute6 launches UDP probe packets with a small
TTL (time to live) and then listens for an ICMP "time exceeded" reply from a gateway. Probes
start with a TTL of one and increase by one until either an ICMP "port unreachable" is
returned, indicating that the packet reached the host, or the maximum number of hops is
exceeded. At each TTL setting, one probe are launched (the number can be changed by
specifying the parameter “probe”) and traceroute prints a line showing the round trip time and
the address of the gateway of each probe, or time out of each probe. If there is no response
within the 5 seconds timeout interval, an asterisk (*) is printed for that probe.
Parameters
ipv6addr
- IPv6 address of the destination end station.
ttl <value 1-60>
- The time to live value of the trace route request. This is the maximum
number of routers that a trace route v6 packet can cross, while seeking the network path
between two devices. The range for the TTL is 1 to 60 hops.
port <value 30000-64900>
- Specify the destination UDP port number. The UDP port range is
from 30000 to 64900.
timeout <sec 1-65535>
- Define the timeout period while waiting for a response from the
remote device. A value of 1 to 65535 seconds can be specified. The default is 5 seconds.
probe <value 1-9>
- Specify the number of probe packets for each hop. The default is 1.
Note:
The probe will be terminated once the destination is reached.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To trace the IPv6 routed path between the switch and 3000::1:
Page 703 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
699
DGS-3627:admin# traceroute6 3000::1 probe 3
Command: traceroute6 3000::1 probe 3
<10 ms
1345:142::11
<10 ms
1345:142::11
<10 ms
1345:142::11
<10 ms
2011:14::100
<10 ms
2011:14::100
*
Request timed out.
<10 ms
3000::1
Trace complete.
DGS-3627:admin#
To trace the IPv6 routed path between the switch and 1210:100::11 with port 40000:
DGS-3627:admin# traceroute6 1210:100::11 port 40000
Command: traceroute6 1210:100::11 port 40000
<10 ms
3100::25
<10 ms
4130::100
<10 ms
1210:100::11
Trace complete.
DGS-3627:admin#
Page 704 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
700
98
TRAFFIC CONTROL COMMANDS
On a computer network, packets such as Multicast packets and Broadcast packets continually flood the network as
normal procedure. At times, this traffic may increase do to a malicious endstation on the network or a malfunctioning
device, such as a faulty network card. Thus, switch throughput problems will arise and consequently affect the overall
performance of the switch network. To help rectify this packet storm, the Switch will monitor and control the situation.
The packet storm is monitored to determine if too many packets are flooding the network, based on the threshold level
provided by the user. Once a packet storm has been detected, the Switch will drop packets coming into the Switch until
the storm has subsided. This method can be utilized by selecting the Drop option of the Action field in the window below.
The Switch will also scan and monitor packets coming into the Switch by monitoring the Switch’s chip counter. This
method is only viable for Broadcast and Multicast storms because the chip only has counters for these two types of
packets. Once a storm has been detected (that is, once the packet threshold set below has been exceeded), the Switch
will shutdown the port to all incoming traffic with the exception of STP BPDU packets, for a time period specified using the
CountDown field. If this field times out and the packet storm continues, the port will be placed in a Shutdown Forever
mode which will produce a warning message to be sent to the Trap Receiver. Once in Shutdown Forever mode, the only
method of recovering this port is to manually recoup it using the
Port Configuration
window in the
Administration
folder
and selecting the disabled port and returning it to an Enabled status. To utilize this method of Storm Control, choose the
Shutdown option of the Action field in the window below.
There are two modes used for packet storm control on the Switch, Drop mode and Shutdown mode. Drop mode is
hardware-based (chip-based) and Shutdown mode is a function of software. The two modes are incompatible with each
other, therefore it is necessary to determine which method is best suited to the network environment where it is used.
The Drop mode storm control function is used to configure three chip-based hardware tables for state and a single
threshold value (threshold value is the same for all three tables). If the threshold value is exceeded on a port, the Switch
will drop all packets on the port. In Drop mode, some parameters such as “time interval” and “count down,” as well as the
CLI command, “config traffic control auto_recover_time” are software-based functions and therefore not applicable for
Drop mode traffic control.
Drop mode
Shutdown mode is a software-based storm control function. When shutdown mode is used, the state of the hardware
tables used for Drop mode are set to disable. Shutdown mode does not support DLF storm control. All configurations
except the port state are saved in the software table. The CPU receives the port state from the counter table (updated at
2 second intervals). If a counter is exceeded on a port, the CPU is shutdown. All packets, except BPDU packets, on the
port are dropped. If the port remains in shutdown status for a configurable period (the count down value), the port enters
shutdown forever status. The port link is down and remains disabled until either the configurable recover timer is timed
out or the CLI command “config ports [ <portlist> | all ] state enable" is manually entered.
Shutdown mode
Page 705 / 757
xStack
®
DGS-3600 Series Layer 3 Gigabit Ethernet Managed Switch CLI Manual
701
The Traffic Control commands in the Command Line Interface (CLI) are listed (along with the appropriate parameters) in
the following table.
Command
Parameters
config traffic control
[<portlist> | all] {broadcast [enable| disable] | multicast [enable | disable] | [dlf |
unicast ] [enable | disable] | action [ drop | shutdown ] | threshold <value 0-
255000 > | countdown
[ <min 0> | <min 3-30> | disable] | time_interval <sec 5-
600>}
config traffic trap
[ none | storm_occurred | storm_cleared | both ]
show traffic control
{<portlist>}
config traffic control
auto_recover_time
[<min 0> | <min 1-65535>]
config traffic control_recover
[<portlist> | all]
Each command is listed, in detail, in the following sections.
config traffic control
Purpose
Used to configure broadcast/multicast packet storm control. Shutdown mode is provided to
monitor the traffic rate in addition to the storm control drop mode. If traffic rate is too high, this
port will be shut down.
Syntax
config traffic control [<portlist> | all] {broadcast [enable| disable] | multicast [enable |
disable] | [dlf | unicast ] [enable | disable] | action [ drop | shutdown ] | threshold
<value 0-255000 > | countdown [<min 0> | <min 3-30> | disable] | time_interval <sec 5-
600>}
Description
The config traffic control command configures broadcast/multicast/DLF storm control.
Parameters
portlist
- Used to specify a range of ports to be configured.
broadcast
- Enable or disable broadcast storm control.
multicast
- Enable or disable multicast storm control.
dlf
- Enable or disable unknown packet storm control. ( Supported for drop mode only)
action
- One of the two options for action are specified for storm control, shutdown of drop
mode. Shutdown mode is a function of software, drop mode is implemented by the chip. If
shutdown mode is specified, it is necessary to configure values for the
back_off and
time_interval parameters.
threshold
- The upper threshold, at which point the specified storm control is triggered. The
<value>is the number of broadcast/multicast packets per second received by the switch that
will trigger the storm traffic control measure. The threshold is expressed as PPS (packets per
second) and must be an unsigned integer.
time_interval
- The sampling interval of received packet counts. The possible value will be 5-
600 seconds. The parameter is not applicable if “drop” (mode) is specified for the “action”
parameter.
countdown
- Timer for shutdown mode. If a port enters the shutdown Rx state and this timer
runs out, port will be shutdown forever. The parameter is not applicable if “drop” (mode) is
specified for the “action” parameter. Default is 0 minutes. 0 disables the forever state,
meaning that the port will not enter the shut down forever state.
disable
- Countdown is disable, the port directly shutdown when the switch detects storm.
Restrictions
Only Administrator and Operator-level users can issue this command.
Example usage:
To configure the parameters so that the traffic control status is enabled on ports 1-12:

Rate

4.5 / 5 based on 2 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top