Amer Networks SS2GD8I - Manual (Page 29)

23
Rx 64 Bytes: Number of 64-byte frames in both good and bad packets received.
Rx 65-127 Bytes: Number of 65 - 126-byte frames in both good and bad packets received.
Rx 128-255 Bytes: Number of 127 - 255-byte frames in both good and bad packets received.
Rx 256-511 Bytes: Number of 256 - 511-byte frames in both good and bad packets received.
Rx 512-1023 Bytes: Number of 512 - 1023-byte frames in both good and bad packets received.
Rx 1024-Bytes: Number of 1024 - max_length-byte frames in both good and bad packets received.
Tx 64 Bytes: Number of 64-byte frames in both good and bad packets transmitted.
Tx 65-127 Bytes: Number of 65 - 126-byte frames in both good and bad packets transmitted.
Tx 128-255 Bytes: Number of 127 - 255-byte frames in both good and bad packets transmitted.
Tx 256-511 Bytes: Number of 256 - 511-byte frames in both good and bad packets transmitted.
Tx 512-1023 Bytes: Number of 512 - 1023-byte frames in both good and bad packets transmitted.
Tx 1024-Bytes: Number of 1024 - max_length-byte frames in both good and bad packets transmitted.
Rx CRC/Alignment: Number of Alignment errors and CRC error packets received.
Rx Undersize: Number of short frames (<64 Bytes) with valid CRC received.
Rx Oversize: Number of long frames (according to max_length register) with valid CRC received.
Rx Fragments: Number of short frames (< 64 bytes) with invalid CRC received.
Rx Jabber: Number of long frames (according tomax_length register) with invalid CRC received.
Rx Drops: Frames dropped due to lack of receiving buffer space.
Rx Errors: Number of the error packets received.
Tx Collisions: Number of collisions experienced while transmitting frames.
Tx Drops: Number of frames dropped due to excessive collision, late collision, or frame aging.
Tx FIFO Drops: Number of frames dropped due to the lack of transmitting buffer space.
3.3 Mirror
The Mirror page (Figure 3-13) allows you to configure port mirroring on the switch. Port mirroring allows
you to duplicate all of the traffic going to one or more ports on to your monitoring port. This is typically
used for diagnosing and troubleshooting problems on the network. For example, if port 1 is the monitoring
port, and ports 2 and 3 are monitored ports, then all traffic going to ports 2 and 3 will be copied to port 1.
Note: When using port mirroring, you should avoid setting a port to be a monitoring port
and an aggregated port at the same time to avoid conflicts.