Configuration Guide User guide

526 FastIron Configuration Guide
53-1002494-02
Basic system management
Clearing statistics
You can clear statistics for many parameters using the clear command.
To determine the available clear commands for the system, enter the clear command at the
Privileged EXEC level of the CLI.
Brocade#clear ?
Syntax: clear <option>
You also can enter “clear” at the command prompt, then press the TAB key.
Traffic counters for outbound traffic
You can configure traffic counters (also called transmit counters) that enable the Brocade device to
count the following packet types on a port or port region:
broadcast packets
multicast packets
unicast packets
dropped packets due to congestion and egress filtering
Depending on the parameters specified with the traffic counter configuration, traffic counters
record the number of outbound packets from any combination of the following sources:
a specific port or all ports in a specific port region
a specific VLAN or all VLANs
a specific 802.1p priority queue or all priority queues
Traffic counters configuration notes
Consider the following rules when configuring traffic counters for outbound traffic.
This feature is supported on FastIron X Series devices only.
This feature is supported in the Layer 2, base Layer 3, and full Layer 3 codes.
This feature applies to physical ports only, including 10 Gbps Ethernet ports and trunk ports. It
does not apply to virtual interfaces.
Once the enhanced traffic counters are read using the show transmit-counter values
command, the counters are cleared (reset to zero).
For each port region, you can enable a maximum of two traffic counters, regardless of whether
traffic counters are enabled on individual ports or on all ports in the port region.
Traffic counters increase for bridged filtered outbound traffic when any of the following
conditions occur:
The port is disabled or the link is down.
The port or port region does not belong to the VLAN specified in the transmit counter
configuration.
A Layer 2 protocol (e.g., spanning tree) has the port in a Blocked state.
The source port needs to be suppressed for multi-target packets.
The priority queue specified in the traffic counter is not allowed for some other reason.