Dell PowerConnect FCS624S Web Management Interface User Guide - Page 55

Monitoring RMON statistics

Page 55 highlights

Monitoring RMON statistics 3 Packets: Broadcast Packets: Multicast CRC Alignment Errors Size Packets: Under Size Packets: Over Fragments Jabbers Collisions The total number of good packets received that were directed to the broadcast address. This number does not include multicast packets. The total number of good packets received that were directed to a multicast address. This number does not include packets directed to the broadcast address. 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. 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. 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. 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 be incremented, 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. 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. The best estimate of the total number of collisions on this Ethernet segment. Monitoring RMON statistics RMON statistics provides count information on multicast and broadcast packets. This information includes total packets sent, undersized and oversized packets, CRC alignment errors, jabbers, collisions, fragments, and dropped events for each port on the system. RMON statistics collection is activated automatically during system startup, and requires no configuration. PowerConnect B-Series FCX Web Management Interface User Guide 45 53-1002268-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152

PowerConnect B-Series FCX Web Management Interface User Guide
45
53-1002268-01
Monitoring RMON statistics
3
Monitoring RMON statistics
RMON statistics provides count information on multicast and broadcast packets. This information
includes total packets sent, undersized and oversized packets, CRC alignment errors, jabbers,
collisions, fragments, and dropped events for each port on the system. RMON statistics collection
is activated automatically during system startup, and requires no configuration.
Packets: Broadcast
The total number of good packets received that were directed to the broadcast
address.
This number does not include multicast packets.
Packets: Multicast
The total number of good packets received that were directed to a multicast address.
This number does not include packets directed to the broadcast address.
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.
Size Packets: Under
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.
Size Packets: Over
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.
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 be incremented, 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.
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.