Tracert's to ntp.plus.net
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Tracert's to ntp.plus.net
Tracert's to ntp.plus.net
25-05-2013 7:06 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I'm currently on a different Gateway and get the following -
>ping ntp.plus.net
Pinging ntp.plus.net [212.159.6.10] with 32 bytes of data:
Ping statistics for 212.159.6.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>tracert ntp.plus.net
Tracing route to ntp.plus.net [212.159.6.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 34 ms 35 ms 50 ms lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 35 ms 34 ms 34 ms link5-central10.ptw-gw01.plus.net [84.93.248.40]
4 34 ms 41 ms 33 ms 56.core.plus.net [212.159.1.56]
5 34 ms 33 ms 33 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 34 ms 34 ms 34 ms vl55.ptn-lb02.plus.net [212.159.2.125]
7 34 ms 33 ms 34 ms cdns02.plus.net [212.159.6.10]
Trace complete.
>tracert 212.159.6.10
Tracing route to cdns02.plus.net [212.159.6.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 34 ms 40 ms 34 ms lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 35 ms 35 ms 40 ms link5-central10.ptw-gw01.plus.net [84.93.248.40]
4 67 ms 34 ms 38 ms 56.core.plus.net [212.159.1.56]
5 34 ms 34 ms 34 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 35 ms 34 ms 34 ms vl55.ptn-lb02.plus.net [212.159.2.125]
7 34 ms 34 ms 34 ms cdns02.plus.net [212.159.6.10]
Trace complete.
>tracert 212.159.6.9
Tracing route to cdns01.plus.net [212.159.6.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 34 ms 35 ms 38 ms lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 35 ms 34 ms 35 ms link3-central10.ptw-gw01.plus.net [84.93.248.36]
4 34 ms 34 ms 33 ms 56.core.plus.net [212.159.1.56]
5 34 ms 34 ms 34 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 34 ms 34 ms 35 ms vl55.ptn-lb02.plus.net [212.159.2.125]
7 34 ms 34 ms 34 ms cdns01.plus.net [212.159.6.9]
Trace complete.
>tracert 212.159.13.50
Tracing route to cdns02.plus.net [212.159.13.50]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 45 ms 37 ms 38 ms lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 34 ms 34 ms 34 ms link5-central10.ptw-gw01.plus.net [84.93.248.40]
4 34 ms 34 ms 34 ms 56.core.plus.net [212.159.1.56]
5 34 ms 35 ms 34 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 34 ms 34 ms 34 ms vl55.ptn-lb02.plus.net [212.159.2.125]
7 34 ms 33 ms 46 ms cdns02.plus.net [212.159.13.50]
Trace complete.
>tracert 212.159.13.49
Tracing route to cdns01.plus.net [212.159.13.49]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 42 ms 97 ms 45 ms lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 34 ms 34 ms 34 ms link11-central10.ptw-gw01.plus.net [84.93.248.52]
4 34 ms 34 ms 34 ms 56.core.plus.net [212.159.1.56]
5 34 ms 34 ms 33 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 104 ms 33 ms 34 ms vl55.ptn-lb02.plus.net [212.159.2.125]
7 33 ms 34 ms 34 ms cdns01.plus.net [212.159.13.49]
Trace complete.
All the above were done yesterday. I couldn't recall if pings or tracerts to ntp.plus.net always went to the same cdns server just for hours (which it certainly does) or days or until I change Gateway. Well all the above are the same today (no Gateway change yet).
You'll note that all the routes are identical apart from hop 3, should this happen, is this right/correct?
What happens if any of the Routers in hops 4, 5, & 6 fail - No DNS it would seem
An issue about common subnets and paths was mentioned here -
http://community.plus.net/forum/index.php/topic,110965.msg951189.html#msg951189
but there was no Plusnet response to these specific points.
We'll see what some Gateway hopping yields.
Re: Tracert's to ntp.plus.net
25-05-2013 7:32 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Just for reference:
[tt]traceroute -I 212.159.6.9
traceroute to 212.159.6.9 (212.159.6.9), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 3.229 ms 3.317 ms 3.886 ms
2 lo0-central10.ptw-ag01.plus.net (195.166.128.195) 20.823 ms 22.395 ms 24.848 ms
3 link7-central10.ptw-gw01.plus.net (84.93.248.12) 24.609 ms 26.380 ms 28.375 ms
4 xe-0-2-0.ptw-cr01.plus.net (212.159.1.16) 28.595 ms 29.913 ms 30.518 ms
5 te9-4.ptn-gw01.plus.net (195.166.129.33) 32.195 ms 33.153 ms 34.570 ms
6 vl55.ptn-lb02.plus.net (212.159.2.125) 35.637 ms 35.935 ms 35.977 ms
7 cdns01.plus.net (212.159.6.9) 36.060 ms 19.763 ms 19.994 ms
traceroute -I 212.159.13.49
traceroute to 212.159.13.49 (212.159.13.49), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 3.065 ms 5.367 ms 5.573 ms
2 lo0-central10.ptw-ag01.plus.net (195.166.128.195) 21.744 ms 23.298 ms 25.353 ms
3 link7-central10.ptw-gw01.plus.net (84.93.248.12) 26.014 ms 26.974 ms 27.706 ms
4 xe-0-2-0.ptw-cr01.plus.net (212.159.1.16) 28.439 ms 30.749 ms 30.956 ms
5 te9-4.ptn-gw01.plus.net (195.166.129.33) 32.476 ms 33.566 ms 34.687 ms
6 vl55.ptn-lb02.plus.net (212.159.2.125) 47.099 ms 44.525 ms 44.945 ms
7 cdns01.plus.net (212.159.13.49) 45.013 ms 29.016 ms 30.375 ms
traceroute -I 212.159.6.10
traceroute to 212.159.6.10 (212.159.6.10), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.841 ms 4.368 ms 5.825 ms
2 lo0-central10.ptw-ag01.plus.net (195.166.128.195) 116.710 ms 117.145 ms 119.568 ms
3 link3-central10.ptw-gw01.plus.net (84.93.248.4) 26.033 ms 27.616 ms 28.471 ms
4 xe-0-2-0.ptw-cr01.plus.net (212.159.1.16) 29.683 ms 30.280 ms 37.702 ms
5 te9-4.ptn-gw01.plus.net (195.166.129.33) 32.968 ms 34.436 ms 37.107 ms
6 vl55.ptn-lb02.plus.net (212.159.2.125) 59.976 ms 58.795 ms 57.644 ms
7 cdns02.plus.net (212.159.6.10) 40.814 ms 26.834 ms 27.494 ms
traceroute -I 212.159.13.50
traceroute to 212.159.13.50 (212.159.13.50), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 2.982 ms 3.043 ms 3.210 ms
2 lo0-central10.ptw-ag01.plus.net (195.166.128.195) 21.514 ms 22.583 ms 24.385 ms
3 link3-central10.ptw-gw01.plus.net (84.93.248.4) 25.128 ms 26.045 ms 27.580 ms
4 xe-0-2-0.ptw-cr01.plus.net (212.159.1.16) 28.035 ms 29.719 ms 30.318 ms
5 te9-4.ptn-gw01.plus.net (195.166.129.33) 32.113 ms 32.570 ms 34.183 ms
6 vl55.ptn-lb02.plus.net (212.159.2.125) 36.167 ms 33.732 ms 34.449 ms
7 cdns02.plus.net (212.159.13.50) 35.837 ms 18.475 ms 19.221 ms
[/tt]
Re: Tracert's to ntp.plus.net
25-05-2013 7:40 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
pcl-ag03
>ping ntp.plus.net
Pinging ntp.plus.net [212.159.6.10] with 32 bytes of data:
Reply from 212.159.6.10: bytes=32 time=18ms TTL=250
Reply from 212.159.6.10: bytes=32 time=18ms TTL=250
Reply from 212.159.6.10: bytes=32 time=18ms TTL=250
Reply from 212.159.6.10: bytes=32 time=18ms TTL=250
Ping statistics for 212.159.6.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 18ms, Average = 18ms
>tracert ntp.plus.net
Tracing route to ntp.plus.net [212.159.13.49]
over a maximum of 30 hops:
1 55 ms 99 ms 99 ms 192.168.0.254
2 35 ms 20 ms 27 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 17 ms 17 ms 17 ms link9-central10.pcl-gw01.plus.net [84.93.249.80]
4 17 ms 17 ms 17 ms xe-1-2-0.pcl-cr01.plus.net [212.159.1.4]
5 17 ms 17 ms 17 ms po2.pcl-gw01.plus.net [195.166.129.41]
6 18 ms 18 ms 17 ms vl63.pcl-lb02.plus.net [212.159.2.253]
7 18 ms 20 ms 17 ms cdns01.plus.net [212.159.13.49]
Trace complete.
>tracert 212.159.6.10
Tracing route to cdns02.plus.net [212.159.6.10]
over a maximum of 30 hops:
1 55 ms 99 ms 99 ms 192.168.0.254
2 18 ms 17 ms 17 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 18 ms 17 ms 17 ms link7-central10.pcl-gw01.plus.net [84.93.249.76]
4 17 ms 16 ms 17 ms xe-1-2-0.pcl-cr01.plus.net [212.159.1.4]
5 17 ms 18 ms 17 ms po2.pcl-gw01.plus.net [195.166.129.41]
6 18 ms 18 ms 18 ms vl63.pcl-lb02.plus.net [212.159.2.253]
7 18 ms 17 ms 17 ms cdns02.plus.net [212.159.6.10]
Trace complete.
>tracert 212.159.6.9
Tracing route to cdns01.plus.net [212.159.6.9]
over a maximum of 30 hops:
1 30 ms 98 ms 99 ms 192.168.0.254
2 20 ms 27 ms 20 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 17 ms 17 ms 18 ms link9-central10.pcl-gw01.plus.net [84.93.249.80]
4 17 ms 17 ms 17 ms xe-1-2-0.pcl-cr01.plus.net [212.159.1.4]
5 17 ms 17 ms 17 ms po2.pcl-gw01.plus.net [195.166.129.41]
6 31 ms 17 ms 17 ms vl63.pcl-lb02.plus.net [212.159.2.253]
7 22 ms 18 ms 19 ms cdns01.plus.net [212.159.6.9]
Trace complete.
>tracert 212.159.13.50
Tracing route to cdns02.plus.net [212.159.13.50]
over a maximum of 30 hops:
1 69 ms 99 ms 99 ms 192.168.0.254
2 18 ms 19 ms 19 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 17 ms 18 ms 17 ms link7-central10.pcl-gw01.plus.net [84.93.249.76]
4 17 ms 17 ms 17 ms xe-1-2-0.pcl-cr01.plus.net [212.159.1.4]
5 18 ms 17 ms 17 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 18 ms 18 ms 18 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
7 18 ms 18 ms 18 ms vl55.ptn-lb02.plus.net [212.159.2.125]
8 17 ms 18 ms 17 ms cdns02.plus.net [212.159.13.50]
Trace complete.
>tracert 212.159.13.49
Tracing route to cdns01.plus.net [212.159.13.49]
over a maximum of 30 hops:
1 85 ms 99 ms 99 ms 192.168.0.254
2 18 ms 21 ms 71 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 18 ms 17 ms 17 ms link9-central10.pcl-gw01.plus.net [84.93.249.80]
4 19 ms 17 ms 17 ms xe-1-2-0.pcl-cr01.plus.net [212.159.1.4]
5 17 ms 17 ms 17 ms po2.pcl-gw01.plus.net [195.166.129.41]
6 18 ms 18 ms 19 ms vl63.pcl-lb02.plus.net [212.159.2.253]
7 20 ms 18 ms 18 ms cdns01.plus.net [212.159.13.49]
Re: Tracert's to ntp.plus.net
25-05-2013 8:02 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Now there is interesting, your tracert 212.159.13.50 has an extra hop with hop 5 onwards being different from the others.
@ejs
Ha, tracert to ntp.plus.net using the same cdns IP possibly due to DNS caching - had just twigged that possibility myself having just sat in front of another computer and it's using a different one from the other computer (no Gateway change yet). Will investigate a bit further.
Re: Tracert's to ntp.plus.net
25-05-2013 8:06 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
ok i'll get me coat..
Re: Tracert's to ntp.plus.net
25-05-2013 8:25 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Flushing the DNS Cache sorted the cdns IP address point, it became random if flushed each time, however no change to the hops on the current gateway.
Re: Tracert's to ntp.plus.net
27-05-2013 7:45 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
[tt]# traceroute -I 212.159.6.9
traceroute to 212.159.6.9 (212.159.6.9), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 2.322 ms 3.701 ms 4.224 ms
2 lo0-central10.pcl-ag01.plus.net (195.166.128.182) 70.621 ms 72.046 ms 73.454 ms
3 link3-central10.pcl-gw01.plus.net (84.93.249.4) 25.333 ms 27.163 ms 29.365 ms
4 192.core.access.plus.net (212.159.0.192) 29.866 ms 31.208 ms 31.958 ms
5 po2.pcl-gw01.plus.net (195.166.129.41) 33.389 ms 35.334 ms 36.468 ms
6 vl63.pcl-lb02.plus.net (212.159.2.253) 38.246 ms 37.404 ms 37.946 ms
7 cdns01.plus.net (212.159.6.9) 39.272 ms 20.705 ms 19.840 ms
# traceroute -I 212.159.13.49
traceroute to 212.159.13.49 (212.159.13.49), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 3.232 ms 3.390 ms 3.772 ms
2 lo0-central10.pcl-ag01.plus.net (195.166.128.182) 21.594 ms 27.208 ms 29.895 ms
3 link9-central10.pcl-gw01.plus.net (84.93.249.16) 26.454 ms 29.701 ms 30.548 ms
4 192.core.access.plus.net (212.159.0.192) 31.076 ms 31.949 ms 33.133 ms
5 po2.pcl-gw01.plus.net (195.166.129.41) 35.902 ms 36.241 ms 37.921 ms
6 vl63.pcl-lb02.plus.net (212.159.2.253) 39.764 ms 38.800 ms 40.101 ms
7 cdns01.plus.net (212.159.13.49) 40.602 ms 24.615 ms 20.535 ms
# traceroute -I 212.159.6.10
traceroute to 212.159.6.10 (212.159.6.10), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 3.324 ms 3.568 ms 3.796 ms
2 lo0-central10.pcl-ag01.plus.net (195.166.128.182) 22.418 ms 24.159 ms 24.774 ms
3 link5-central10.pcl-gw01.plus.net (84.93.249.8 ) 25.623 ms 27.614 ms 28.287 ms
4 192.core.access.plus.net (212.159.0.192) 29.861 ms 31.448 ms 32.229 ms
5 po2.pcl-gw01.plus.net (195.166.129.41) 34.716 ms 35.720 ms 37.351 ms
6 vl63.pcl-lb02.plus.net (212.159.2.253) 39.732 ms 37.356 ms 38.130 ms
7 cdns02.plus.net (212.159.6.10) 39.540 ms 24.461 ms 25.614 ms
# traceroute -I 212.159.13.50
traceroute to 212.159.13.50 (212.159.13.50), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 3.055 ms 3.219 ms 3.767 ms
2 lo0-central10.pcl-ag01.plus.net (195.166.128.182) 22.528 ms 24.070 ms 24.646 ms
3 link5-central10.pcl-gw01.plus.net (84.93.249.8 ) 26.944 ms 27.330 ms 28.293 ms
4 192.core.access.plus.net (212.159.0.192) 29.837 ms 31.722 ms 32.275 ms
5 ae1.ptw-cr01.plus.net (195.166.129.0) 34.382 ms 36.757 ms 37.402 ms
6 te9-4.ptn-gw01.plus.net (195.166.129.33) 38.734 ms 35.979 ms 37.505 ms
7 vl55.ptn-lb02.plus.net (212.159.2.125) 38.859 ms 21.151 ms 22.491 ms
8 cdns02.plus.net (212.159.13.50) 23.271 ms 22.188 ms 22.908 ms
[/tt]
Re: Tracert's to ntp.plus.net
27-05-2013 8:00 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: Anotherone
You'll note that all the routes are identical apart from hop 3, should this happen, is this right/correct?
What happens if any of the Routers in hops 4, 5, & 6 fail - No DNS it would seem
An issue about common subnets and paths was mentioned here -
http://community.plus.net/forum/index.php/topic,110965.msg951189.html#msg951189
but there was no Plusnet response to these specific points.
We'll see what some Gateway hopping yields.
In answer to your question about hop 3, yes thats fine and expected. In summery you have 12 links to pick from and route hashing will just send you off down one of them. All the other hops are resilient in one format or another and will be routed around.
In regards to the DNS servers. We have them (cluster) located in two sites, both responding to the same VIP ranges so in theory you should just go to the cloest one, if one site goes away the same VIP will just work at the other site.
Hopefully that helps a little, if I've missed the point in some way or there is an issue I'm sure the DC guys will pick it up and/or get it logged internally.
Re: Tracert's to ntp.plus.net
28-05-2013 7:24 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Can you explain how this "resilience" is supposed to work. In the tracert's I've posted from ptw-ag02, hops 4.5.& 6 are identical.
The question is "What happens if any of the Routers in hops 4, 5, & 6 fail" as those routes to each of the cdns servers is identical.
Re: Tracert's to ntp.plus.net
28-05-2013 8:10 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
>tracert 212.159.13.49
Tracing route to cdns01.plus.net [212.159.13.49]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 35 ms 40 ms 35 ms lo0-central10.pcl-ag01.plus.net [195.166.128.182]
3 34 ms 33 ms 34 ms link9-central10.pcl-gw01.plus.net [84.93.249.16]
4 34 ms 33 ms 33 ms 192.core.access.plus.net [212.159.0.192]
5 34 ms 33 ms 33 ms po2.pcl-gw01.plus.net [195.166.129.41]
6 34 ms 34 ms 34 ms vl63.pcl-lb02.plus.net [212.159.2.253]
7 33 ms 33 ms 34 ms cdns01.plus.net [212.159.13.49]
Trace complete.
>tracert 212.159.13.50
Tracing route to cdns02.plus.net [212.159.13.50]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 40 ms 36 ms 34 ms lo0-central10.pcl-ag01.plus.net [195.166.128.182]
3 34 ms 34 ms 33 ms link1-central10.pcl-gw01.plus.net [84.93.249.0]
4 34 ms 34 ms 33 ms 192.core.access.plus.net [212.159.0.192]
5 33 ms 34 ms 34 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 34 ms 33 ms 33 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
7 34 ms 34 ms 33 ms vl55.ptn-lb02.plus.net [212.159.2.125]
8 34 ms 34 ms 33 ms cdns02.plus.net [212.159.13.50]
Trace complete.
>tracert 212.159.6.9
Tracing route to cdns01.plus.net [212.159.6.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 37 ms 40 ms 34 ms lo0-central10.pcl-ag01.plus.net [195.166.128.182]
3 34 ms 33 ms 33 ms link9-central10.pcl-gw01.plus.net [84.93.249.16]
4 34 ms 34 ms 32 ms 192.core.access.plus.net [212.159.0.192]
5 34 ms 34 ms 33 ms po2.pcl-gw01.plus.net [195.166.129.41]
6 34 ms 34 ms 34 ms vl63.pcl-lb02.plus.net [212.159.2.253]
7 34 ms 34 ms 34 ms cdns01.plus.net [212.159.6.9]
Trace complete.
>tracert 212.159.6.10
Tracing route to cdns02.plus.net [212.159.6.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 35 ms 34 ms 34 ms lo0-central10.pcl-ag01.plus.net [195.166.128.182]
3 34 ms 34 ms 34 ms link1-central10.pcl-gw01.plus.net [84.93.249.0]
4 108 ms 33 ms 36 ms 192.core.access.plus.net [212.159.0.192]
5 34 ms 33 ms 33 ms po2.pcl-gw01.plus.net [195.166.129.41]
6 34 ms 33 ms 34 ms vl63.pcl-lb02.plus.net [212.159.2.253]
7 34 ms 33 ms 34 ms cdns02.plus.net [212.159.6.10]
Trace complete.
Hmm, interesting, hops 4, 5, & 6 are the same except for cdns02.plus.net [212.159.13.50] where after hop 4 it's different, with an extra hop!!
I notice the same in ejs's last post also pcl-ag01.
Re: Tracert's to ntp.plus.net
28-05-2013 10:28 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
>tracert 212.159.13.49
Tracing route to cdns01.plus.net [212.159.13.49]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 40 ms 43 ms 38 ms lo0-central10.ptw-ag04.plus.net [195.166.128.194]
3 37 ms 37 ms 37 ms link7-central10.ptw-gw01.plus.net [84.93.248.108]
4 37 ms 47 ms 39 ms xe-10-0-0.ptw-cr01.plus.net [212.159.1.40]
5 37 ms 37 ms 37 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 37 ms 37 ms 36 ms vl55.ptn-lb02.plus.net [212.159.2.125]
7 37 ms 37 ms 37 ms cdns01.plus.net [212.159.13.49]
Trace complete.
>tracert 212.159.13.50
Tracing route to cdns02.plus.net [212.159.13.50]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 38 ms 37 ms 40 ms lo0-central10.ptw-ag04.plus.net [195.166.128.194]
3 38 ms 37 ms 37 ms link1-central10.ptw-gw01.plus.net [84.93.248.96]
4 36 ms 37 ms 37 ms xe-10-0-0.ptw-cr01.plus.net [212.159.1.40]
5 38 ms 37 ms 37 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 37 ms 37 ms 36 ms vl55.ptn-lb02.plus.net [212.159.2.125]
7 37 ms 37 ms 37 ms cdns02.plus.net [212.159.13.50]
Trace complete.
>tracert 212.159.6.9
Tracing route to cdns01.plus.net [212.159.6.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 67 ms 39 ms 47 ms lo0-central10.ptw-ag04.plus.net [195.166.128.194]
3 37 ms 37 ms 50 ms link7-central10.ptw-gw01.plus.net [84.93.248.108]
4 37 ms 40 ms 36 ms xe-10-0-0.ptw-cr01.plus.net [212.159.1.40]
5 37 ms 37 ms 37 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 37 ms 37 ms 37 ms vl55.ptn-lb02.plus.net [212.159.2.125]
7 36 ms 37 ms 36 ms cdns01.plus.net [212.159.6.9]
Trace complete.
>tracert 212.159.6.10
Tracing route to cdns02.plus.net [212.159.6.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 37 ms 38 ms 41 ms lo0-central10.ptw-ag04.plus.net [195.166.128.194]
3 37 ms 36 ms 37 ms link1-central10.ptw-gw01.plus.net [84.93.248.96]
4 37 ms 37 ms 36 ms xe-10-0-0.ptw-cr01.plus.net [212.159.1.40]
5 37 ms 36 ms 37 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 38 ms 37 ms 37 ms vl55.ptn-lb02.plus.net [212.159.2.125]
7 37 ms 37 ms 37 ms cdns02.plus.net [212.159.6.10]
Trace complete.
Hops 4 to 6 identical to all. As my normal DNS servers are set to 212.159.6.9 & 10 automatically, it seems to me if any other those 3 Routers fail to respond, I get a failed DNS lookup!
Re: Tracert's to ntp.plus.net
28-05-2013 11:30 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: paulmh5 In regards to the DNS servers. We have them (cluster) located in two sites, both responding to the same VIP ranges so in theory you should just go to the cloest one, if one site goes away the same VIP will just work at the other site.
Paul,
Is the point you are trying to make here, is that the IP addresses we see in trace routes to PN services are virtual, not the real addresses of the servers? Therefore if a real server / route is not available, the network will redirect the virtual IP to a different physical server delivering the same service?
Cheers,
Kevin
In another browser tab, login into the Plusnet user portal BEFORE clicking the fault & ticket links
Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.
If this post helped, please click the Thumbs Up and if it fixed your issue, please click the This fixed my problem green button below.
Re: Tracert's to ntp.plus.net
28-05-2013 12:06 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
But that does not explain what happens if for example xe-10-0-0.ptw-cr01.plus.net in the tracert in my previous post fails/fails to respond!
Re: Tracert's to ntp.plus.net
28-05-2013 12:32 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Agreed! This does not look clear to us outsiders. Many 'alternate' PN network services appear to have the same connectivity route within their network, thus (at least superficially) the failure in one step of the common route will cause connectivity to the prime and alternate services to fail.
It would be most useful to learn / know how the primary / secondary services are indeed resilient to a failure in what appears to be common (shared) routes.
Terminology in this area does confuse me, but would I be correct in saying arguably any service behind a load balancer is virtualised? One is not addressing the machine delivering the service, but something which will select 1 out of N instances of the service, each of which must have its own unique IP address.
Kevin
In another browser tab, login into the Plusnet user portal BEFORE clicking the fault & ticket links
Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.
If this post helped, please click the Thumbs Up and if it fixed your issue, please click the This fixed my problem green button below.
Re: Tracert's to ntp.plus.net
28-05-2013 1:09 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: townman
Quote from: paulmh5 In regards to the DNS servers. We have them (cluster) located in two sites, both responding to the same VIP ranges so in theory you should just go to the cloest one, if one site goes away the same VIP will just work at the other site.
Paul,
Is the point you are trying to make here, is that the IP addresses we see in trace routes to PN services are virtual, not the real addresses of the servers?
I'm not Paul but yes, the IP's you see in traceroutes are not those of the physical caching DNS servers themselves. They are virtual IP's. The physical caching servers themselves are clustered across two sites for resiliency. I think BGP or something similar is used to route you to the closest cluster which is the basis for the question jelv asked here.
I could be wrong but last I knew there were four physical boxes in each cluster (each with their own IP that you'll not see in traceroutes).
Quote from: Anotherone But that does not explain what happens if for example xe-10-0-0.ptw-cr01.plus.net in the tracert in my previous post fails/fails to respond!
That's a core router (Juniper MX kit I think). The rDNS of that hop represents one of multiple interfaces on the device itself. There will be redundancy within the unit itself e.g. multiple line cards as well as there being another physical unit i.e. ptw-cr02. I don't know a huge amount about our core network but I do know there's sufficient resiliency should a network interface unexpectedly fall over.
I'm going to bow out now before I get out of my depth, however if this thread is a question of whether or not we've sufficient network redundancy then I don't think people have anything to worry about
Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page