Trouble with 212.159.8.110?
Quote from: Anotherone The problem is they should not be different which is why I would not call them "usual"
The gateways are in buildings in different parts of London and there's routing from each back to Sheffield with a link between the two London buildings - of course there's a high chance that the routing may be different!
Edit: Too add to that the targets are in different datacentres, one is in peh and one in ptp.
Everything should be replicated in different datacentres so that if anything drastic happens at one it all keeps running (albeit with probably reduced performance).
Looking at the trace routes the first goes pcl -> ptw -> ptn -> peh.
The second goes pcl -> ptp so of course it has fewer hops.
I'm on a ptw gateway and you can see the routing for me goes the other way:
If you gateway hop on to a ptn gateway you'd see something different again.
Looking at the trace routes the first goes pcl -> ptw -> ptn -> peh.
The second goes pcl -> ptp so of course it has fewer hops.
I'm on a ptw gateway and you can see the routing for me goes the other way:
C:\Users\John>tracert 212.159.8.110
Tracing route to community.plus.net [212.159.8.110]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms tg582 [192.168.1.254]
2 21 ms 20 ms 21 ms lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 21 ms 21 ms 21 ms link-a-central10.ptw-gw01.plus.net [212.159.2.148]
4 21 ms 20 ms 20 ms xe-0-2-0.ptw-cr01.plus.net [212.159.0.248]
5 28 ms 27 ms 22 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 39 ms 31 ms 30 ms gi5-1.peh-cr02.plus.net [84.93.232.61]
7 38 ms 33 ms 33 ms po5.peh-cr01.plus.net [84.93.232.16]
8 39 ms 29 ms 30 ms vlan2657.peh-elb01.plus.net [84.93.232.44]
9 30 ms 54 ms 32 ms community.plus.net [212.159.8.110]
Trace complete.
C:\Users\John>tracert 212.159.9.110
Tracing route to community.plus.net [212.159.9.110]
over a maximum of 30 hops:
1 <1 ms 2 ms 1 ms tg582 [192.168.1.254]
2 23 ms 21 ms 23 ms lo0-central10.ptw-ag02.plus.net [195.166.128.196]
3 21 ms 20 ms 21 ms link-a-central10.ptw-gw01.plus.net [212.159.2.148]
4 20 ms 21 ms 24 ms xe-0-2-0.ptw-cr01.plus.net [212.159.0.248]
5 27 ms 21 ms 21 ms ae1.pcl-cr01.plus.net [195.166.129.1]
6 21 ms 21 ms 21 ms po2.pcl-gw01.plus.net [195.166.129.41]
7 28 ms 29 ms 27 ms gi5-8.ptp-cr01.plus.net [84.93.224.48]
8 29 ms 28 ms 27 ms vlan2657.ptp-elb01.plus.net [84.93.224.36]
9 28 ms 28 ms 30 ms community.plus.net [212.159.9.110]
If you gateway hop on to a ptn gateway you'd see something different again.
I realised that after I posted the rather daft comment. I suppose I should untangle my brain and get a cup of coffee - caffeine deficiency has set in 
Having said that, I'm not convinced that this doesn't have a bearing on some of the issues being seen - if you follow all the negatives!
I can do traceroutes to each of the ntp servers and they are all the same number of hops. They are in different data centres. How does that come about?
Having said that, I'm not convinced that this doesn't have a bearing on some of the issues being seen - if you follow all the negatives!
I can do traceroutes to each of the ntp servers and they are all the same number of hops. They are in different data centres. How does that come about?
Because each of the data centres with gateways has it's own set of DNS servers with the same set of IP addresses.
You may be right - ptn and ptw might share in which case the routing from ptn and ptw gateways would show a difference.
All four IPs are definitely present in both ptw and pcl - you'll see the traceroute doesn't leave ptn/ptw or pcl depending upon where you are connected.
All four IPs are definitely present in both ptw and pcl - you'll see the traceroute doesn't leave ptn/ptw or pcl depending upon where you are connected.