Use this Knowledge Script to collect traceroute data for a specified source and target location on demand, or at regularly scheduled intervals.
Networks-RT
The default interval for this script is Every 4 hours.
Set the following parameters as needed:
|
Description |
How to Set It |
|
Collect data? |
Select Yes to collect traceroute data. By default, data is collected. |
|
Event when traceroute fails? |
Select Yes to raise events. By default, events are enabled. |
|
Event when total latency exceeds threshold? |
Select Yes to raise events. The default is n. |
|
Select the traceroute target locations |
Specify an AppManager ResponseTime for Networks node, some other AppManager node, an IP address, or a URL. The maximum length is 64 characters. NOTE:The source location is the computer where the script is run. Click the Browse [...] button to display the Select a View dialog box. Highlight a view from the list and click Next to open the Select Desired Computer(s) dialog box. The view determines which computers are available for selection. Select one or more endpoint computers. Click Finish. Or specify multiple targets separated by commas in the text input field. The script validates whether at least one of the target locations is different from the source location where the script is run. |
|
Maximum number of hops |
Specify an integer, 1-30. Set the maximum number of hops allowed in the traceroute. The default is 30. |
|
Total latency threshold (sec) |
Set the threshold for the total latency in seconds. The default is 1.000 seconds. The latency threshold must not be blank if the Event when total latency exceeds threshold? parameter is enabled. |
|
Traceroute failed event severity |
Set the event severity, from 1 to 40, to indicate the importance of the event. The default is 15. |
|
Threshold event severity |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 25. |
This script can be used to collect baseline traceroute data between a specified source and target location. This is particularly useful if you have also selected the Action_Traceroute or Action_TracerouteNetworks-RT script as an action associated with a separate Knowledge Script. If you are collecting exception traceroutes by means of an action traceroute script, the baseline data collected by the Networks-RT_Traceroute script may be used as a comparison with the exception data. However, for comparison of baseline and exception data, you must run the Networks-RT_Traceroute script against the same source and target location as the Knowledge Scripts that might generate exception traceroutes.
In addition to comparing the Networks-RT_Traceroute data against exception data, the baseline data may also be viewed on its own. You may run the Report_TracerouteProfile script to generate a report that summarizes the accumulated traceroute data for a given source and target location thus far.