Netgear GS752TP GS728TP/GS728TPP/GS752TP Software Administration Manual - Page 214

Total Packets Received with MAC Errors, Packets Received 128-255 Octets

Page 214 highlights

GS752TP, GS728TP, and GS728TPP Gigabit Smart Switches • Packets Received 128-255 Octets. The total number of packets (including bad packets) received that were 128 through 255 octets in length inclusive (excluding framing bits but including FCS octets). • Packets Received 256-511 Octets. The total number of packets (including bad packets) received that were 256 through 511 octets in length inclusive (excluding framing bits but including FCS octets). • Packets Received 512-1023 Octets. The total number of packets (including bad packets) received that were 512 through 1023 octets in length inclusive (excluding framing bits but including FCS octets). • Packets Received > 1024 Octets. The total number of packets received that were in excess of 1024 octets (excluding framing bits, but including FCS octets) and were otherwise well formed. • Total Packets Received Without Errors. The total number of packets received that were without errors. • Unicast Packets Received. The number of subnetwork-unicast packets delivered to a higher-layer protocol. • Multicast Packets Received. 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. • Broadcast Packets Received. The total number of good packets received that were directed to the broadcast address. This does not include multicast packets. • Total Packets Received with MAC Errors. The total number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. • Jabbers Received. The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad frame check sequence (FCS) with an integral number of octets (FCS error) or a bad FCS with a nonintegral number of octets (alignment error). 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 20-150 ms. • Fragments Received. The total number of packets received that were less than 64 octets in length with ERROR CRC (excluding framing bits but including FCS octets). • Undersize Received. The total number of packets received that were less than 64 octets in length with GOOD CRC (excluding framing bits but including FCS octets). • Alignment Errors. The total number of packets received that had a length (excluding framing bits, but including FCS octets) of from 64 through 1518 octets, inclusive, but had a bad frame check sequence (FCS) with a nonintegral number of octets. • Rx FCS Errors. The total number of packets received that had a length (excluding framing bits, but including FCS octets) of 64 through 1518 octets, inclusive, but had a bad Frame Check Sequence (FCS) with an integral number of octets • Overruns. The total number of frames discarded as this port was overloaded with incoming packets, and was not able to keep up with the inflow. Monitoring the System 214

  • 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
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275

Monitoring the System
214
GS752TP, GS728TP, and GS728TPP Gigabit Smart Switches
Packets Received 128-255 Octets
. The total number of packets (including bad
packets) received that were 128 through 255 octets in length inclusive (excluding
framing bits but including FCS octets).
Packets Received 256-511 Octets
. The total number of packets (including bad
packets) received that were 256 through 511 octets in length inclusive (excluding
framing bits but including FCS octets).
Packets Received 512-1023 Octets
. The total number of packets (including bad
packets) received that were 512 through 1023 octets in length inclusive (excluding
framing bits but including FCS octets).
Packets Received > 1024 Octets
. The total number of packets received that were in
excess of 1024 octets (excluding framing bits, but including FCS octets) and were
otherwise well formed.
Total Packets Received Without Errors
. The total number of packets received that
were without errors.
Unicast Packets Received
. The number of subnetwork-unicast packets delivered to
a higher-layer protocol.
Multicast Packets Received.
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.
Broadcast Packets Received
. The total number of good packets received that were
directed to the broadcast address. This does not include multicast packets.
Total Packets Received with MAC Errors
. The total number of inbound packets that
contained errors preventing them from being deliverable to a higher-layer protocol.
Jabbers Received
. The total number of packets received that were longer than 1518
octets (excluding framing bits, but including FCS octets), and had either a bad frame
check sequence (FCS) with an integral number of octets (FCS error) or a bad FCS
with a nonintegral number of octets (alignment error). 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 20–150 ms.
Fragments Received
. The total number of packets received that were less than 64
octets in length with ERROR CRC (excluding framing bits but including FCS octets).
Undersize Received
. The total number of packets received that were less than 64
octets in length with GOOD CRC (excluding framing bits but including FCS octets).
Alignment Errors
. The total number of packets received that had a length (excluding
framing bits, but including FCS octets) of from 64 through 1518 octets, inclusive, but
had a bad frame check sequence (FCS) with a nonintegral number of octets.
Rx FCS Errors
. The total number of packets received that had a length (excluding
framing bits, but including FCS octets) of 64 through 1518 octets, inclusive, but had a
bad Frame Check Sequence (FCS) with an integral number of octets
Overruns
. The total number of frames discarded as this port was overloaded with
incoming packets, and was not able to keep up with the inflow.