Technical data

Switching and Routing

The display contains additional sections of statistics. However, the additional statistics apply to Layer 4 – 7

switching, not to IP forwarding.

Clearing IP Traffic Statistics

To clear the IP traffic statistics displayed by the show ip traffic command, enter the following command:

ServerIron# clear ip traffic

Syntax: clear ip traffic

IP Interfaces and Multinetting

Beginning with Release 8.0.00, the ServerIron Chassis devices support Layer 3 features, including the following:

• Multiple IP interfaces in the same or different sub-nets

• Support for multiple sub-net addresses on the same physical port or a single sub-net address on multiple

physical ports

• Route-only support

NOTE: When switch trunk is configured and the servers are all remote servers 1 hop away from the ServerIron,

Layer 3 switch trunking does not work. The ServerIron does not perform load balancing on the trunk ports. The

expected behavior is trunking should be based on destination IP only.

The Layer 3 features include support for configuring multiple IP interfaces in the same or different IP sub-nets on

the ServerIron.

• Without Layer 3 – When you use the ServerIron as a Layer 2 and Layer 4 – 7 switch, you can configure one IP

interface on the device. The address is used as the management interface for the device. To multi-net the

device, you must configure source IP addresses for the sub-nets that are in addition to the sub-net containing

the device’s management IP address.

• With Layer 3 – When you use the ServerIron as a Layer 2/3 and Layer 4 – 7 switch, you can configure

separate IP sub-net interfaces on individual ports. In addition, you can associate the same sub-net interface

with all the ports in a port-based VLAN by configuring a virtual routing interface on the VLAN, then assigning

an IP address to the virtual routing interface.

fragmented The total number of IP packets fragmented by this device to

accommodate the MTU of this device or of another device.

reassembled The total number of fragmented IP packets that this device re-

assembled.

bad header The number of IP packets dropped by the device due to a bad packet

header.

no route The number of packets dropped by the device because there was no

route.

unknown proto The number of packets dropped by the device because the value in

the Protocol field of the packet header is unrecognized by this device.

no buffer This information is used by Brocade customer support.

other errors The number of packets that this device dropped due to error types

other than the types listed above.

Table 2.6: CLI Display of IP Forwarding Traffic Statistics (Continued)

This Field... Displays...