60
edits
Generic troubleshooting processes: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Remco.derooy (talk | contribs) |
No edit summary |
||
| Line 3: | Line 3: | ||
Every now and then we get asked, what a (generic) troubleshooting approach/workflow with an Allegro Network Multimeter would look like. | Every now and then we get asked, what a (generic) troubleshooting approach/workflow with an Allegro Network Multimeter would look like. | ||
And, rightfully so, because the endless possibilities of an Allegro might be overwhelming for some. | And, rightfully so, because the endless possibilities of an Allegro Network Multimeter might be overwhelming for some. | ||
In this tutorial, we’ll go into several topics that might be of interest to you -the user- while working with an Allegro Network Multimeter. | In this tutorial, we’ll go into several topics that might be of interest to you -the user- while working with an Allegro Network Multimeter. | ||
| Line 128: | Line 128: | ||
=== <u>Burst Analysis</u> === | === <u>Burst Analysis</u> === | ||
The first graph on | The first graph on Allegro Network Multimeter’s predefined quality dashboard, represents “Burst Analysis”. | ||
Because the Allegro Network Multimeter supports data measurement intervals (sampling rates), as detailed as 1 ms, you can identify instances where a Link is 100% saturated, for very short fractions of time. | Because the Allegro Network Multimeter supports data measurement intervals (sampling rates), as detailed as 1 ms, you can identify instances where a Link is 100% saturated, for very short fractions of time. | ||