Hi,
Has anybody an idea how to realize if the hop count to an Node changes?br
br,
Oli
I submitted this as a feature request, as the TTL is not currently being collected as part of the ICMP echo-reply stats.I'm not sure if this is going to be added or not in future versions.
It should be quite easy to add another column to the DB called TTL and collect this data along with the ICMP response time.
Then I could alert anytime the TTL changed and start a script to traceroute to the node to see what the new L3 path is.
Bump -
Here is an example of the TTL that is included with the Windows ping command:
c:\>ping yahoo.ca
Pinging yahoo.ca [68.180.206.184] with 32 bytes of data:
Reply from 68.180.206.184: bytes=32 time=116ms TTL=49
Reply from 68.180.206.184: bytes=32 time=105ms TTL=48
Reply from 68.180.206.184: bytes=32 time=110ms TTL=48
c:\>tracert yahoo.ca
Tracing route to yahoo.ca [68.18
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms
2 <1 ms <1 ms <1 ms
3 17 ms 17 ms 17 ms
4 19 ms 18 ms 18 ms
5 19 ms 18 ms 18 ms
6 19 ms 19 ms 19 ms
7 19 ms 19 ms 19 ms
8 38 ms 44 ms 38 ms
9 * * *
10 121 ms 120 ms 119 ms
11 148 ms 112 ms 119 ms
12 105 ms 104 ms 114 ms
13 116 ms 110 ms 105 ms
Trace complete.
____________________________________________________
c:\>ping google.ca
Pinging google.ca [173.194.79.94] with 32 bytes of data:
Reply from 173.194.79.94: bytes=32 time=76ms TTL=44
Reply from 173.194.79.94: bytes=32 time=75ms TTL=44
Ping statistics for 173.194.79.94:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 76ms, Average = 75ms
c:\>tracert google.ca
Tracing route to google.ca [173.
3 21 ms 20 ms 20 ms
4 21 ms 20 ms 20 ms
5 21 ms 20 ms 21 ms
6 22 ms 33 ms 22 ms
7 21 ms 21 ms 21 ms
8 52 ms 53 ms 53 ms
9 62 ms 62 ms 62 ms
10 51 ms 51 ms 51 ms
11 51 ms 52 ms 51 ms
12 64 ms 64 ms 64 ms
13 72 ms 80 ms 78 ms
14 74 ms 73 ms 74 ms
15 85 ms 95 ms 78 ms
16 83 ms 90 ms 86 ms
17 * * *
18 75 ms 75 ms 76 ms
