1,775
edits
Interface statistics: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
The Speed setting offers a possibility to change the speed of the port. | The Speed setting offers a possibility to change the speed of the port. | ||
A selection of all possible settings is presented. The default selection is auto for the highest possible speed. | A selection of all possible settings is presented. The default selection is '''auto''' for the highest possible speed. | ||
The Speed indicates whether a network cable is connected and which link speed has been negotiated. | The Speed indicates whether a network cable is connected and which link speed has been negotiated. | ||
The Duplex status shows whether the link is operated in full-duplex or half-duplex mode. | The Duplex status shows whether the link is operated in '''full-duplex''' or '''half-duplex''' mode. | ||
In case the Allegro Network Multimeter operates in bridge mode and two mutual interfaces do not have the | In case the Allegro Network Multimeter operates in bridge mode and two mutual interfaces do not have the same link speed and duplex, a warning will be shown below the Duplex status for both interfaces. | ||
The Current receive/transmit utilization summarizes the traffic received and sent by the network port. The value is calculated by the number of bytes received and sent in relation to full-duplex link speed. | The Current receive/transmit utilization summarizes the traffic received and sent by the network port. | ||
The value is calculated by the number of bytes received and sent in relation to full-duplex link speed. | |||
A PCAP buttons allows capturing all traffic for that network port. | A PCAP buttons allows capturing all traffic for that network port. | ||
Next to the Interface status there are three graphs for the number of processed packets, the number of processed bytes, and possible error counters. | Next to the Interface status there are three graphs for the number of processed packets, the number of processed bytes, and possible error counters. | ||
Both packets and bytes statistics show past values in the graph and the current total values and the current rate during the last second, separately for receiving (yellow down arrow) and sending side (blue up arrow). | Both packets and bytes statistics show past values in the graph and the current total values and the current rate during the last second, separately for receiving ('''yellow''' down arrow) and sending side ('''blue''' up arrow). | ||
The error values list all possible packet processing errors. Depending on the network interface card´s capabilities, slightly different counters are shown. | The error values list all possible packet processing errors. Depending on the network interface card´s capabilities, slightly different counters are shown. | ||
'''RX errors apply to received packets. Following errors are counted:''' | '''RX errors apply to '''received''' packets. Following errors are counted:''' | ||
* Malformed packets: The packet was corrupt. This is a general receive error counter and more detailed counters will be reported below. | * Malformed packets: The packet was corrupt. This is a general receive error counter and more detailed counters will be reported below. | ||
* Hardware miss: The packet couldn't be received by the network interface card. | * Hardware miss: The packet couldn't be received by the network interface card. | ||
| Line 37: | Line 39: | ||
* Under or oversized: The packet was either too small or it exceeded MTU. | * Under or oversized: The packet was either too small or it exceeded MTU. | ||
* Bad CRC: Frame check sequence of layer 2 was broken. | * Bad CRC: Frame check sequence of layer 2 was broken. | ||
* Bad fragmentation: The packet | * Bad fragmentation: The packet was shorter than the minimum size of 64 Bytes and had a bad CRC. | ||
* Jabber: The packet was longer than the MTU and had a bad CRC. | * Jabber: The packet was longer than the MTU and had a bad CRC. | ||
'''TX errors indicates errors when sending to the wire fails for some reason.''' | '''TX errors indicates errors when '''sending''' to the wire fails for some reason.''' | ||
* Unable to forward: This is a generic error counter. | * Unable to forward: This is a generic error counter. | ||
* Dropped due to missing capacity: The packet could not be sent as the link capacity was too small. | * Dropped due to missing capacity: The packet could not be sent as the link capacity was too small. | ||