inactive
369
edits
FAQ: Difference between revisions
→System behavior
| Line 125: | Line 125: | ||
storage. | storage. | ||
== System | == System behaviour == | ||
==== Where does the Allegro Network Multimeter display L1 issues like bad CRC frames? ==== | ==== Where does the Allegro Network Multimeter display L1 issues like bad CRC frames? ==== | ||
| Line 131: | Line 131: | ||
Issues like these are accounted for the Monitoring interface on which the issue was encountered and the respective | Issues like these are accounted for the Monitoring interface on which the issue was encountered and the respective | ||
statistics are available on the '''Interface stats''' page in the '''Errors''' column. For an explanation of the error | statistics are available on the '''Interface stats''' page in the '''Errors''' column. For an explanation of the error | ||
counters, | counters, refer to the [[Interface_statistics|Interface statistics]] manual page. | ||
==== What happens in case of a system overload? ==== | ==== What happens in the case of a system overload? ==== | ||
In case of a system overload, a prominent warning is displayed at the top of the user interface for a few seconds | In the case of a system overload, a prominent warning is displayed at the top of the user interface for a few seconds | ||
and | and this warning and the time when the error occurred can be reviewed on the '''Info''' -> '''Status''' page. As long as there are | ||
still notifications on the '''Info''' -> '''Status''' page, this is indicated by | still notifications on the '''Info''' -> '''Status''' page, this is indicated by coloured icons at the top of the user interface. | ||
If a system overload occurs and not all packets can be analyzed, these packets are accounted at the Monitoring | If a system overload occurs and not all packets can be analyzed, these packets are accounted at the Monitoring | ||
interface on which they were received. The counter can be found on the '''Interface stats''' page in the '''Errors''' column | interface on which they were received. The counter can be found on the '''Interface stats''' page in the '''Errors''' column | ||
under the '''Not processed''' section and | under the '''Not processed''' section and titled '''due to overload'''. | ||
When the Allegro Network Multimeter is operating in | When the Allegro Network Multimeter is operating in Bridge mode and packets cannot be processed due to a system | ||
overload, a software bypass will ensure that these packets are still forwarded to the adjacent Monitoring interface. | overload, a software bypass will ensure that these packets are still forwarded to the adjacent Monitoring interface. | ||
| Line 149: | Line 149: | ||
In this case, the Allegro Network Multimeter will start freeing up memory by removing historic statistical data which | In this case, the Allegro Network Multimeter will start freeing up memory by removing historic statistical data which | ||
lies before a certain point in time. This | lies before a certain point in time. This cut-off time is constantly adjusted to provide the best possible use of the | ||
available memory. For how far back-in-time historical statistics are currently available, can be reviewed on the | available memory. For how far back-in-time historical statistics are currently available, can be reviewed on the | ||
'''Info''' -> '''System Info''' page. | '''Info''' -> '''System Info''' page. | ||
| Line 157: | Line 157: | ||
If the system does not provide a sufficient look back-in-time with the given traffic, it may help to deactivate certain | If the system does not provide a sufficient look back-in-time with the given traffic, it may help to deactivate certain | ||
features that provide very detailed information but also consume a large amount of memory. Features that typically | features that provide very detailed information but also consume a large amount of memory. Features that typically | ||
fit into this category are | fit into this category are different settings of the '''IP statistics'''. These settings can be accessed by navigating to | ||
'''IP''' -> '''IP Statistics''' and clicking the '''Settings''' button at the top of the page. Especially turning off the | '''IP''' -> '''IP Statistics''' and clicking the '''Settings''' button at the top of the page. Especially turning off the | ||
'''Store connection information for every IP''' and '''Store traffic history graph for IP peers''' settings can help saving | '''Store connection information for every IP''' and '''Store traffic history graph for IP peers''' settings can help saving | ||
| Line 172: | Line 172: | ||
stored on the attached hard disk drive. This data is not lost after the | stored on the attached hard disk drive. This data is not lost after the | ||
processing is stopped. It is possible to reanalyze the packet ringbuffer, but | processing is stopped. It is possible to reanalyze the packet ringbuffer, but | ||
this will interrupt the '''live''' mode, so no new packets will be processed. | this will interrupt the '''live''' mode, so no new packets will be processed when this is in operation. | ||
== Allegro hardware == | == Allegro hardware == | ||