1,775
edits
Settings: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
* Bridge mode: In bridge mode, all received packets will be transmitted again on the corresponding mutual port so that the device can be placed in-line between any network component. The device will be transparent and will not modify the traffic in any way. The additional latency will be typically around or less than 1 millisecond. | * Bridge mode: In bridge mode, all received packets will be transmitted again on the corresponding mutual port so that the device can be placed in-line between any network component. The device will be transparent and will not modify the traffic in any way. The additional latency will be typically around or less than 1 millisecond. | ||
* Sink mode: In sink mode, packets are only received and not forwarded. This operation mode allows for installation at a mirror port of a switch or when using a network tap to access the network traffic. | * Sink mode: In sink mode, packets are only received and not forwarded. This operation mode allows for installation at a mirror port of a switch or when using a network tap to access the network traffic. | ||
The packet processing mode can be changed during run-time. | The packet processing mode can be changed during run-time. | ||
| Line 46: | Line 47: | ||
* Reduce graph resolution of old data by up to: The resolution of older graph data is automatically reduced to save memory and to allow a longer view into the traffic history. This option allows to change this behavior. With a reduction factor of 1/1 no reduction is done at all which means the selected graph resolution is available for the complete time. | * Reduce graph resolution of old data by up to: The resolution of older graph data is automatically reduced to save memory and to allow a longer view into the traffic history. This option allows to change this behavior. With a reduction factor of 1/1 no reduction is done at all which means the selected graph resolution is available for the complete time. | ||
This of course reduces the time period to see historical data. You can also choose to increase the reduction factor to be able to store more data for a longer time. | :This of course reduces the time period to see historical data. You can also choose to increase the reduction factor to be able to store more data for a longer time. The time printed in parentheses represents the worst-case graph resolution based on the chosen resolution and reduction factor. | ||
The time printed in parentheses represents the worst-case graph resolution based on the chosen resolution and reduction factor. | |||
Note: Regardless of these settings, the graph values are always converted to represent a value per second (when applicable). For example, the packets per second for IP addresses will always be a value literally per second even if the resolution is larger or smaller than one second. The shown value is scaled to match this view. Especially with sub-second resolution this might be misleading. | Note: Regardless of these settings, the graph values are always converted to represent a value per second (when applicable). For example, the packets per second for IP addresses will always be a value literally per second even if the resolution is larger or smaller than one second. The shown value is scaled to match this view. Especially with sub-second resolution this might be misleading. | ||
For instance, if there is a network element sending one packet per second and the resolution is set to 100 millisecond, the value might be shown as 10 packets per second as each sample point is scaled to represent an value per second. For a detailed investigation it is recommended to select a specific time interval since the total packet counters shown in all statistics are unscaled and represent the actual values. | For instance, if there is a network element sending one packet per second and the resolution is set to 100 millisecond, the value might be shown as 10 packets per second as each sample point is scaled to represent an value per second. For a detailed investigation it is recommended to select a specific time interval since the total packet counters shown in all statistics are unscaled and represent the actual values. | ||
Performance implications: | |||
The performance degradation and memory usage depends on the actual network traffic and is not exactly predictable. Here are some examples for reference on a Multimeter 1000 series with different configuration values (under ideal test conditions): | Performance implications: The performance degradation and memory usage depends on the actual network traffic and is not exactly predictable. | ||
Here are some examples for reference on a Multimeter 1000 series with different configuration values (under ideal test conditions): | |||
* 1 second resolution, 1/1 reduction factor: 90% of default performance | * 1 second resolution, 1/1 reduction factor: 90% of default performance | ||