Trace Route monitors
Trace Route monitor tracks the response time and total number of hops to reach a particular IP address. Trace Route monitor sends ICMP echo packets to the destination host and uses the TTL field in the IP header.
This monitor must run with root privileges since it uses raw socket for sending ping requests. This monitor does not work if the monitored device is protected by a firewall that does not support ICMP.
Monitored attributes for Trace Route monitors
The following table lists the monitored attributes of a Trace Route monitor.
Attribute | Description |
|---|---|
Availability (%) | Percentage availability of the monitored resource. If able to connect to the target IP and transfer data, then availability is 100%; otherwise it is 0%. |
DNS Lookup Time (ms) | Time taken for the input DNS name to be resolved into an IP address. Value of this attribute will be NO RESPONSE if the name lookup failed. The value is 0 if an IP address is input for the target device. |
Max Hop Time (ms) | Maximum of all the average time in hop. For example, if it takes 17 hops to reach the destination, and for each hop there were 3 pings, then for each hop you have the Max Time, Min Time, and Avg. Time.
Then the Max Hop Time is the maximum average of the hop time for all 17 hops. Max Hop Time = of all the hops, the maximum avgerage time to reach the hop |
Round Trip Time (ms) | Average time taken to reach destination. For example, consider the Trace Route of www.cisco.com, using 4 pings for each hop. If the destination is reached in 3 pings, and the time taken by the 3 pings for this destination are 500ms, 550ms, and 525ms, then the Round Trip Time is (500 + 550 + 525)/3 = 525ms. Round Trip Time = (sum of the Round Trip Time for the destination)/ number of responses |
Total No Of Hops (#) | Number of hops to reach destination. |
Configuration information for Trace Route monitors
The following table describes the information required during configuration of the Trace Route monitor.
Configuration information | Description |
|---|---|
Input fields on the Configuration tab | |
Instance Name | Specify a name for the monitor instance. This is displayed on folders, graphs, lists, etc. If you do not specify a name here, the monitor instance will be created with the name "Target Device = <input value of Target Device>". |
Tag | Specify a tag value to search or group the objects. You can enter multiple name-value pairs, text, or include both (name-value pair and text). This gives you the option to group objects in different forms. Click the + icon to select a default tag class. The Enter Tag Details screen opens. Select Tag Class from the drop-down list and enter a tag value. Click Add to append tag class and value. Click Finish.
|
Source Agent | Select the name or IP address of the BMC ProactiveNet server or BMC ProactiveNet agent to host the new monitor instance. |
Target Device | Specify the DNS name/IP address of the target machine. BMC ProactiveNet recommends that the target IP and the IP address of the device where the monitor is being created be the same. If domain name is specified here, then DNS lookup is done during each poll. Restart DNS client on Windows agent, if you change the IP address of the device (Domain name of which you had specified here to create the monitor instance). |
Control tab | |
No Of Hops | Specify the maximum number of hops that can be taken to reach the destination. Default is 30. |
Collect Data | Select/clear check box to enable/disable data collection for the monitored component. By default, data collection is enabled (check box selected). |
Statistics Poll Interval | Specify the time interval between two consecutive statistical data polls. Default is 5 minutes. |
Statistics Poll Timeout | Specify the time-out period for each poll of statistical data. If no data is available at the end of this interval, the system records Zero availability and proceeds with the next scheduled poll. Default is 30 seconds. |
Group tab | |
Group Membership | This enables you to add a device and its monitors to one or more groups. Optionally, you may associate the device with a group. A group is used to logically organize the devices and monitors by department, geographic area, or service. Assigning a device to a group also enables the system administrator to restrict or allow access to certain devices. To associate the device with a group, select the group name here. |
Additional configuration and setup issues
The following table presents details about Additional configuration and setup issues for the Trace Route monitor.
Issue | Details |
|---|---|
Monitor configuration | No additional configuration requirements for this monitor. Maintain the default configuration of BMC ProactiveNet. |
External setup | No external setup requirements for this monitor. |
External dependencies | No external dependencies for this monitor. |
BMC ProactiveNet agent dependencies | BMC ProactiveNet agent installation on the monitored host is not mandatory. Monitor instance can be created on any BMC ProactiveNet agent. |
Trace Route monitor thresholds
Attribute | Severity | Duration (min) | Flag | Default Threshold | Outside Baseline | Baseline Type |
|---|---|---|---|---|---|---|
Availability | Critical | 0 | Below | 100 | N | ALL |
Round Trip Time | Minor | 15 | Above | 180000 | Y | ALL |