547
edits
Virtual Link Group functionality: Difference between revisions
Virtual Link Group functionality (view source)
Revision as of 07:43, 29 September 2023
, 29 September 2023→Detail of traffic analysis
mNo edit summary |
|||
| Line 1: | Line 1: | ||
The Allegro Network Multimeter allows for defining up to '''100''' so called Virtual Link Groups to logically separate traffic for easier analysis. | The Allegro Network Multimeter allows for defining up to '''100''' so called Virtual Link Groups (VLG) to logically separate traffic for easier analysis. | ||
__TOC__ | __TOC__ | ||
== Usage == | |||
All statistics data for each Virtual Link Group (VLG) are strictly separated. Once at least one VLG is defined, a drop-down menu appears at the top menu bar allowing to select which VLG should be chosen for the displayed statistics. | |||
Packet capture also takes the VLG into account so when capturing a specific IP for example, the system only returns packets for that IP in the currently selected VLG. Expert capture filters still allows to use multiple VLG filter for a single capture or disable the VLG filter at all (by not using the 'group' filter). | |||
Statistics for a VLG can also be reset independently from other VLGs (since firmware version 4.2). The drop-down menu contains an eraser-like button to reset the measurement statistics for that VLG. Currently this reset feature is limited to some measurement modules only (IP). | |||
== Configuration == | == Configuration == | ||
| Line 52: | Line 59: | ||
All statistics in the Allegro Network Multimeter will show information related to the selected group only. Interface graphs, total traffic graph on the dashboard and the burst analysis module will, however, show global information and ignore the group selection. | All statistics in the Allegro Network Multimeter will show information related to the selected group only. Interface graphs, total traffic graph on the dashboard and the burst analysis module will, however, show global information and ignore the group selection. | ||
== Traffic color settings == | === Traffic color settings === | ||
A group can be configured so that all traffic counters are displayed in a utilization color. | A group can be configured so that all traffic counters are displayed in a utilization color. | ||
| Line 74: | Line 81: | ||
|} | |} | ||
== Detail of traffic analysis == | === Detail of traffic analysis === | ||
Each virtual link group can limit the detail of traffic analysis to a specific network layer. Reducing the detail will improve overall performance and increase the history time. In contrast to the [[Global settings]] for the detail of traffic analysis, this option still allows for some groups to show more detailed information while for other only limited data is available. | Each virtual link group can limit the detail of traffic analysis to a specific network layer. Reducing the detail will improve overall performance and increase the history time. In contrast to the [[Global settings]] for the detail of traffic analysis, this option still allows for some groups to show more detailed information while for other only limited data is available. | ||
'''NOTE:''' The configuration can be changed during runtime, but it is recommended to do a processing restart so statistics for already running connections are not mixed between different groups and processing modes. | '''NOTE:''' The configuration can be changed during runtime, but it is recommended to do a processing restart so statistics for already running connections are not mixed between different groups and processing modes. | ||
[[File:Virtual Link Group functionality processing mode.png|none | [[File:Virtual Link Group functionality processing mode.png|none|Virtual Link Group functionality processing mode|thumb|545x545px]] | ||
=== Statistics timeout === | |||
Since firmware 4.2, the age of the measurement statistics can be configured individually for each Virtual Link Group separately. | |||
The configuration dialog allows to enter an arbitrary duration for which the data should be stored. The value can be in plain seconds, or with d/h/m suffixes also in days (d), hours (h), or minutes (m). | |||
The global timeout is used if no value is entered (or zero). Data can also not be older than the global timeout. | |||