11 RMON support

 

 

 

TABLE 55

Export configuration and statistics (Continued)

 

 

 

 

 

Parameter

 

Definition

 

 

 

 

CRC alignment errors

The total number of packets received that were from 64 – 1518 octets long, but had

 

 

 

either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a

 

 

 

non-integral number of octets (Alignment Error).

 

 

 

The packet length does not include framing bits but does include FCS octets.

 

 

 

 

Undersize pkts

The total number of packets received that were less than 64 octets long and were

 

 

 

otherwise well formed.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

 

 

Fragments

 

The total number of packets received that were less than 64 octets long and had either

 

 

 

a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a

 

 

 

non-integral number of octets (Alignment Error).

 

 

 

It is normal for this counter to increment, since it counts both runts (which are normal

 

 

 

occurrences due to collisions) and noise hits.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

 

Oversize packets

The total number of packets received that were longer than 1518 octets and were

 

 

 

otherwise well formed.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

NOTE: 48GC modules do not support count information on oversized packets and

 

 

 

report 0.

 

 

 

 

 

Jabbers

 

The total number of packets received that were longer than 1518 octets and had either

 

 

 

a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a

 

 

 

non-integral number of octets (Alignment Error).

 

 

 

NOTE: This definition of jabber is different from the definition in IEEE-802.3 section

 

 

 

8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define

 

 

 

jabber as the condition where any packet exceeds 20 ms. The allowed range to

 

 

 

detect jabber is between 20 ms and 150 ms.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

NOTE: 48GC modules do not support count information on jabbers and report 0.

 

 

 

 

 

Collisions

 

The best estimate of the total number of collisions on this Ethernet segment.

 

 

 

 

64 octets pkts

The total number of packets received that were 64 octets long.

 

 

 

This number includes bad packets.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

 

65 to 127 octets pkts

The total number of packets received that were 65 – 127 octets long.

 

 

 

This number includes bad packets.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

 

128 to 255 octets pkts

The total number of packets received that were 128 – 255 octets long.

 

 

 

This number includes bad packets.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

 

256 to 511 octets pkts

The total number of packets received that were 256 – 511 octets long.

 

 

 

This number includes bad packets.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

 

512 to 1023 octets pkts

The total number of packets received that were 512 – 1023 octets long.

 

 

 

This number includes bad packets.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

 

1024 to 1518 octets

The total number of packets received that were 1024 – 1518 octets long.

 

pkts

 

This number includes bad packets.

 

 

 

This number does not include framing bits but does include FCS octets.

 

 

 

 

252

Brocade ICX 6650 Administration Guide

 

53-1002600-01

Page 270
Image 270
Brocade Communications Systems 6650 manual Rmon support Export configuration and statistics, Parameter Definition