Interface statistics

From Allegro Network Multimeter Manual
Jump to navigation Jump to search

The interface statistics page lists all network ports that are utilized by the Allegro Network Multimeter. To easily focus on the currently used network interfaces, unused interfaces can be hidden via the checkbox to show only active interfaces.

The Interface status column contains generic information about each port.

The Interface ID is a unique number enumerated for all network ports.

The Link pair number covers two ports linked to each other in the bridge mode or mixed bridge/sink mode.

That is, traffic received from one port of the same link pair will be sent to the corresponding port of the same link pair, and vice verse. In sink mode, the link pair number is irrelevant as no traffic is forwarded.

If the packet processing mode Mixed bridge/sink mode has been enabled in the Global settings a drop down menu appears and the packet processing mode for the interface can be chosen. A selection here automatically affects the other interface of the link pair. Single interfaces which are not part of a link pair do not show the drop down menu as they always operate in Sink mode.

The Module Info button opens a dialog that shows SFP-Module information like the vendor name or serial number or metrics like the signal strength or temperature, if available.

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. This selection also has the option disabled to permanently disable the interface and bring the link down.

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 Maximum frame size shows the largest Ethernet frame size that can be received on that interface.

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 Clock synchronization is shown for GNSS/GPS-capable interfaces when the GNSS/GPS time synchronization method is enabled (see Administration). It shows either GNSS/GPS or PPS depending on the clock source of the interface. If 'not locked' is displayed behind the synchronization source this means that the internal DPLL synchronization circuit is not yet fully locked onto the source clock signal. It may take several minutes after activation for the DPLL to lock onto the clock source.

The Clock offset is shown for GNSS/GPS-capable interfaces when the GNSS/GPS time synchronization method is enabled (see Administration). It shows the time offset in nanoseconds at the last synchronization between the interface clock and the DPLL synchronization circuit driven either by GNSS/GPS or PPS.

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.

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.

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.
  • Hardware miss: The packet couldn't be received by the network interface card.
  • Out of packet buffer: There have been problems with allocating memory for the packet.
  • Undersized: The packet was shorter than the minimum size of 64 Bytes and had a valid CRC.
  • Oversized: The packet exceeded the defined 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 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.

TX errors indicates errors when sending to the wire fails for some reason.

  • 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.

Not processed packets were dropped due to overloaded software send queues.

Interface statistics.png

L3 tunnel stats

If the L3 tunnel mode (see Global settings) has been activated for an interface this tab will show a list of the L3 tunnels processed by the system. It shows the source IP address along with the target IP address (see Common table columns - IP) and provides statistics about the amount of traffic transmitted through the tunnel. In case of ERSPAN tunnels the ERSPAN session ID will also be used to differentiate between tunnels in addition to the IP addresses.

WiFi interfaces

If WiFi monitoring interfaces are active a tab named WiFi interfaces is available. This displays statistics for each active WiFi monitoring interface similar to the statistics on the Interfaces tab.