History (rmon group 2) – Brocade TurboIron 24X Series Configuration Guide User Manual

Page 274

Advertising
background image

240

Brocade TurboIron 24X Series Configuration Guide

53-1003053-01

RMON support

History (RMON group 2)

All active ports by default will generate two history control data entries per active Layer 2 Switch
port or Layer 3 Switch interface. An active port is defined as one with a link up. If the link goes
down the two entries are automatically deleted.

Two history entries are generated for each device:

A sampling of statistics every 30 seconds

A sampling of statistics every 30 minutes

The history data can be accessed and displayed using any of the popular RMON applications

A sample RMON history command and its syntax is shown below.

TurboIron(config)#rmon history 1 interface 1 buckets 10 interval 10 owner nyc02

Syntax: rmon history <entry-number> interface <portnum> buckets <number> interval

<sampling-interval> owner <text-string>

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.

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.

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
pkts

The total number of packets received that were 1024 – 1518 octets long.
This number includes bad packets.
This number does not include framing bits but does include FCS octets.

TABLE 49

Export configuration and statistics (Continued)

This line...

Displays...

Advertising