![]() |
Re: [Merged] Manchester Issues
Sorry I see no loss, or high pings to speak of to the last hop on the trace. If you have nothing better to do on December 21st than run endless traceroutes to try and find issues that's your prerogative. I do :)
As has been mentioned to me you may not be conversant with these technologies. So... Tracing route to pear.nildram.net [195.149.20.145] over a maximum of 30 hops: 1 10 ms 1 ms 1 ms 192.168.11.1 << This is router setting up Network Address Translation table entry and new Stateful Packet Inspection firewall ruleset entry. 2 7 ms 6 ms 7 ms 172.17.0.1 3 7 ms 7 ms 7 ms gr1-stbc-rtr1.homechoice.co.uk [81.1.112.62] 4 11 ms 7 ms 10 ms 81-1-67-48.homechoice.co.uk [81.1.67.48] 5 7 ms 8 ms 8 ms 81-1-67-16.homechoice.co.uk [81.1.67.16] 6 8 ms 7 ms 7 ms 195.50.117.113 7 111 ms 8 ms 7 ms so-1-3-0.gar2.London1.Level3.net [212.113.3.29] << This is the Level 3 router giving CPU priority to its' rpd (route processor daemon) process, as it's a Juniper (indicated by its' DNS and the so-1-3-0 bit specifically) rather than icmpd its' Internet Control Message Protocol daemon. These are both low priority however ICMP is subterranean. 8 14 ms 8 ms 12 ms unknown.Level3.net [212.187.131.156] 9 9 ms 8 ms 8 ms telia-level3-ge.London1.Level3.net [4.68.111.182] 10 8 ms 8 ms 8 ms ldn-bb1-pos0-3-0.telia.net [213.248.74.5] 11 8 ms 8 ms 8 ms ldn-b3-pos6-0.telia.net [213.248.65.238] 12 8 ms 8 ms 8 ms pipex-110586-ldn-b3.c.telia.net [213.248.100.30] 13 9 ms 8 ms 8 ms lon1-9.nildram.net [84.12.224.14] 14 9 ms 8 ms 8 ms pear.nildram.net [195.149.20.145] << end of the trace, a web server which responds in a timely fashion to the queries, however if I were to continue tracing it it would probably respond late every so often or not at all simply because its' getting too many pings and is preserving resources as an anti-denial of service measure. ---------- Post added at 17:25 ---------- Previous post was at 17:11 ---------- [QUOTE=Bill C]2 15 ms 10 ms 8 ms 16 ms 8 ms 25 ms 58 ms 9 ms 12 ms 6 ms 8 ms 24 ms 17 ms 21 ms 54 ms 14 ms [10.15.16.1] Cisco uBR 7246VXR 3 7 ms 8 ms 9 ms 57 ms 5 ms 11 ms 27 ms 25 ms 7 ms 7 ms 6 ms 5 ms 9 ms 6 ms 23 ms 6 ms bagu-t2cam1-a-v121.inet.ntl.com [80.5.162.85]Cisco 4 16 ms 8 ms 12 ms 9 ms 7 ms 9 ms 42 ms 38 ms 10 ms 19 ms 7 ms 8 ms 7 ms 7 ms 39 ms 18 ms bagu-t2core-a-ge-wan63.inet.ntl.com [80.5.161.17]Cisco 5 6 ms 8 ms 7 ms 7 ms 9 ms 19 ms 59 ms 27 ms 6 ms 7 ms 9 ms 8 ms 8 ms 7 ms 12 ms 9 ms man-bb-a-so-100-0.inet.ntl.com [62.253.188.25]Juniper 6 8 ms 34 ms 9 ms 7 ms 17 ms 15 ms 28 ms 24 ms 9 ms 93 ms 24 ms 8 ms 8 ms 10 ms 31 ms 29 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]Juniper 7 12 ms 15 ms 27 ms 20 ms 15 ms 14 ms 56 ms 20 ms 12 ms 17 ms 40 ms 14 ms 16 ms 26 ms 13 ms 56 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]Juniper 8 51 ms 46 ms 39 ms 19 ms 32 ms 20 ms 89 ms 227 ms 25 ms 20 ms 13 ms 13 ms 12 ms 14 ms 46 ms 25 ms win-dc-a-v902.inet.ntl.com [62.253.187.222]Busy Cisco, VLAN not real interface 9 16 ms 15 ms 14 ms 13 ms 12 ms 17 ms 58 ms 221 ms 20 ms 14 ms 21 ms 18 ms 14 ms 14 ms 64 ms 49 ms www.ntlworld.com [212.250.162.47]Load balanced web cluster, not a 'real' device but collection of them |
Re: [Merged] Manchester Issues
If the information is not of use to you am sorry its just i have not even been able to ping to local ubr at times.
The time get on it is like someone has put a proxy in the system . Pages not loading unresponsive connection . Then its ok am lost again we had similar problems earlier this year remember you and Bill saying local issue. That was sorted by adjustment of the network levels Could it be similar Target Name: spc1-roch1-6-0-gw.bagu.broadband.ntl.com IP: 81.100.143.1 Date/Time: 21/12/2005 18:05:15 2 318 ms 7 ms * 10 ms * 6 ms 6 ms 10 ms 6 ms 7 ms 221 ms 6 ms 7 ms 8 ms 6 ms 307 ms 123 ms 9 ms 290 ms * 7 ms 193 ms 9 ms 14 ms 14 ms * 7 ms 9 ms 6 ms 143 ms spc1-roch1-6-0-gw.bagu.broadband.ntl.com [81.100.143.1] I have been dead happy up till now see the ping to the ubr from yesterday 138ms could that be a levels problem Come on guys these are the results |
Re: [Merged] Manchester Issues
Quote:
If they can see a problems as well then they should send out a Network Tech. :) My and Igs point is that the trace routes you have posted dont show any problems apart from 1 ot 2 slow routers. ??? |
Re: [Merged] Manchester Issues
Quote:
recently its bobbins Target Name: spc1-roch1-6-0-gw.bagu.broadband.ntl.com IP: 81.100.143.1 Date/Time: 21/12/2005 18:10:07 2 306 ms * 127 ms 11 ms 154 ms 6 ms 8 ms 173 ms 96 ms 6 ms 12 ms 267 ms 6 ms 6 ms 6 ms 6 ms 223 ms 46 ms 6 ms 7 ms 6 ms 9 ms 220 ms 58 ms 185 ms 6 ms 7 ms 6 ms 121 ms 7 ms spc1-roch1-6-0-gw.bagu.broadband.ntl.com [81.100.143.1] I was after your and igs advice on this |
Re: [Merged] Manchester Issues
Quote:
This is more like it. the last lot did not show anything was wrong. This does. Get on the phone :) you have a local issue by the look of these |
Re: [Merged] Manchester Issues
Thanks bill just managed to get on again to the site.
I have reported it but its india dealing with it |
Re: [Merged] Manchester Issues
Quote:
I leave NTL on Friday :hyper: |
Re: [Merged] Manchester Issues
thenegineer your trace's are just about the best I have seen from an ntl connection, how are you getting more then 3 latency figures to show on each hop?
|
Re: [Merged] Manchester Issues
Quote:
Nice to see someone else see's that as well :) |
Re: [Merged] Manchester Issues
Quote:
Target Name: www.ntlworld.com IP: 212.250.162.47 Date/Time: 22/12/2005 07:10:11 2 76 ms 6 ms 90 ms 173 ms 353 ms 8 ms 9 ms 89 ms 148 ms * 6 ms 77 ms 392 ms 60 ms 6 ms 107 ms 48 ms 5 ms 8 ms 5 ms 5 ms 7 ms 6 ms 5 ms 6 ms 6 ms 6 ms 6 ms 6 ms 5 ms [10.23.48.1] 3 223 ms 7 ms 92 ms 310 ms 323 ms 12 ms 7 ms 60 ms 120 ms * 8 ms 74 ms 363 ms 31 ms 7 ms 78 ms 19 ms 6 ms 7 ms 7 ms 71 ms 7 ms 8 ms 7 ms 7 ms 6 ms 7 ms 7 ms 7 ms 10 ms oldh-t2cam1-b-v115.inet.ntl.com [80.5.164.189] 4 205 ms 7 ms 32 ms 281 ms 424 ms 6 ms 8 ms 172 ms 90 ms * 7 ms 85 ms 408 ms 12 ms 9 ms 55 ms 8 ms 10 ms 8 ms 8 ms 8 ms 8 ms 9 ms 7 ms 8 ms 16 ms 8 ms 8 ms 8 ms 7 ms [213.104.242.205] 5 176 ms 91 ms 13 ms 252 ms 396 ms 7 ms 7 ms 143 ms 61 ms * 8 ms 56 ms 379 ms 7 ms 8 ms 26 ms 7 ms 10 ms 9 ms 7 ms 7 ms 8 ms 16 ms 7 ms 8 ms 7 ms 8 ms 78 ms 8 ms 9 ms [213.105.242.245] 6 212 ms 13 ms 14 ms 236 ms 371 ms 13 ms 21 ms 117 ms 48 ms * 14 ms 31 ms 354 ms 15 ms 14 ms 15 ms 16 ms 13 ms 12 ms 13 ms 13 ms 25 ms 13 ms 64 ms 16 ms 15 ms 12 ms 14 ms 13 ms 13 ms [62.253.185.138] 7 198 ms 13 ms 152 ms 322 ms 341 ms 14 ms 13 ms * 15 ms * 12 ms 12 ms 334 ms 13 ms 13 ms 16 ms 13 ms 13 ms 14 ms 14 ms 13 ms 13 ms 14 ms 13 ms 14 ms 12 ms 13 ms 15 ms 13 ms 13 ms [62.253.187.222] 8 168 ms 13 ms 123 ms 297 ms 432 ms 13 ms 14 ms 62 ms 174 ms * 13 ms 107 ms 304 ms 13 ms 14 ms 14 ms 15 ms 19 ms 15 ms 13 ms 13 ms 14 ms 13 ms 14 ms 13 ms 22 ms 13 ms 13 ms 13 ms 14 ms www.ntlworld.com [212.250.162.47] this is to the UBR Target Name: spc1-roch1-6-0-gw.bagu.broadband.ntl.com IP: 81.100.143.1 Date/Time: 22/12/2005 07:14:45 2 * * * * 9 ms 195 ms * 6 ms 181 ms * 6 ms 38 ms 449 ms 5 ms 6 ms 441 ms 412 ms 6 ms 232 ms * 7 ms 81 ms 6 ms 89 ms 67 ms 62 ms 205 ms 6 ms 186 ms 177 ms spc1-roch1-6-0-gw.bagu.broadband.ntl.com [81.100.143.1] And now the problem it then goes back to normal for a few minutes Target Name: www.ntlworld.com IP: 212.250.162.47 Date/Time: 22/12/2005 07:22:26 2 6 ms 6 ms 13 ms 6 ms 9 ms 6 ms 6 ms 7 ms 8 ms 5 ms 6 ms 6 ms 5 ms 6 ms 6 ms 7 ms 10 ms 8 ms 6 ms 6 ms 7 ms [10.23.48.1] 3 6 ms 6 ms 7 ms 6 ms 7 ms 6 ms 14 ms 7 ms 20 ms 12 ms 7 ms 6 ms 7 ms 17 ms 6 ms 8 ms 6 ms 7 ms 12 ms 6 ms 7 ms oldh-t2cam1-b-v115.inet.ntl.com [80.5.164.189] 4 8 ms 8 ms 8 ms 7 ms 7 ms 14 ms 8 ms 7 ms 7 ms 7 ms 7 ms 7 ms 7 ms 7 ms 7 ms 7 ms 8 ms 7 ms 7 ms 7 ms 7 ms manc-t3core-1b-ge-111-0.inet.ntl.com [213.104.242.205] 5 10 ms 8 ms 82 ms 10 ms 7 ms 8 ms 11 ms 75 ms 8 ms 7 ms 7 ms 9 ms 8 ms 7 ms 7 ms 11 ms 7 ms 8 ms 7 ms 7 ms 8 ms man-bb-b-so-400-0.inet.ntl.com [213.105.242.245] 6 13 ms * 12 ms 14 ms 13 ms 12 ms 14 ms 28 ms 14 ms 13 ms 13 ms 13 ms 12 ms 14 ms 13 ms 13 ms 13 ms 13 ms 14 ms 13 ms 18 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138] 7 14 ms 12 ms 14 ms 13 ms 14 ms 14 ms 14 ms 14 ms 13 ms 44 ms 16 ms 41 ms 13 ms 12 ms 13 ms 13 ms 12 ms 14 ms 13 ms 13 ms 13 ms [62.253.187.222] 8 15 ms 14 ms 13 ms 14 ms 13 ms 15 ms 14 ms 13 ms 14 ms 14 ms 13 ms 13 ms 13 ms 14 ms 13 ms 13 ms 14 ms 13 ms 13 ms 14 ms 12 ms www.ntlworld.com [212.250.162.47] Do not know if this might help checked STB Menu error 896 on stream 554750 |
Re: [Merged] Manchester Issues
Well as if by magic someone has sorted something out either loose connection oversubbed UBR or something
Target Name: www.ntlworld.com IP: 212.250.162.47 Date/Time: 22/12/2005 14:10:25 to 22/12/2005 14:12:02 Hop Sent Err PL% Min Max Avg Host Name / [IP] 1 16 0 0.0 0 8 0 [192.168.123.254] 2 16 0 0.0 5 18 9 [10.23.48.1] 3 16 0 0.0 6 33 10 oldh-t2cam1-b-v115.inet.ntl.com [80.5.164.189] 4 16 0 0.0 6 17 9 manc-t3core-1b-ge-111-0.inet.ntl.com [213.104.242.205] 5 16 0 0.0 7 18 11 cpc3-swan1-3-0-cust245.swan.cable.ntl.com [213.105.242.245] 6 16 0 0.0 14 25 16 win-bb-a-so-300-0.inet.ntl.com [62.253.185.138] 7 16 0 0.0 14 55 19 win-dc-a-v902.inet.ntl.com [62.253.187.222] 8 16 0 0.0 13 25 17 www.ntlworld.com [212.250.162.47] Target Name: spc1-roch1-6-0-gw.bagu.broadband.ntl.com IP: 81.100.143.1 Date/Time: 22/12/2005 14:15:22 to 22/12/2005 14:17:28 Hop Sent Err PL% Min Max Avg Host Name / [IP] 2 26 1 3.8 5 12 7 spc1-roch1-6-0-gw.bagu.broadband.ntl.com [81.100.143.1] got a new version of ping plotter note loss |
Re: [Merged] Manchester Issues
Quote:
You are scaring me with this obsession with ping plotter and indeed your ongoing obsession with your connection, but nonetheless if the loss on your report doesn't show on other hops there's no issue. |
Re: [Merged] Manchester Issues
Quote:
I was told a few months ago that NTL have a few network local issues in this area. Somnething to do with weather datastreams and balancing So told to check the connection with ping plotter to local UBR. As its that bit thats liable to be the problem the route to UBR. Thanks for checking UBR ign appreciated. Suppose it will not improve much more improved with Pace2000 then improved with Samsung box. |
Re: [Merged] Manchester Issues
Ok my ubr is fine as confirmed by bbking so check this trace from ping plotter, please dont have a cardiac arrest th'engineer.
Target Name: www.ntlworld.com IP: 212.250.162.47 Date/Time: 23/12/2005 19:51:17 to 23/12/2005 19:51:44 1 9 ms 8 ms 49 ms 45 ms 19 ms 23 ms 9 ms 8 ms 60 ms 33 ms UBR [10.8.143.254] 2 9 ms 24 ms 22 ms 29 ms 21 ms 9 ms 12 ms 12 ms 19 ms 15 ms leic-t2cam1-a-ge914.inet.ntl.com [82.3.35.149] 3 12 ms 38 ms 9 ms 10 ms 11 ms 32 ms 9 ms 20 ms 10 ms 11 ms leic-t2core-a-ge-220-0.inet.ntl.com [82.3.33.10] 4 19 ms 25 ms 20 ms 39 ms 15 ms 9 ms 48 ms 17 ms 12 ms 11 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110] 5 23 ms 19 ms 21 ms 23 ms 20 ms 18 ms 44 ms 16 ms 20 ms 18 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238] 6 25 ms 17 ms 21 ms 29 ms 117 ms 52 ms 15 ms 50 ms 43 ms 16 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78] 7 19 ms 26 ms 23 ms 16 ms 71 ms 15 ms 47 ms 20 ms 69 ms 59 ms win-bb-b-so-500-0.inet.ntl.com [62.253.185.202] 8 27 ms 21 ms 57 ms 19 ms 43 ms 71 ms 24 ms 17 ms 26 ms 16 ms win-dc-b-v902.inet.ntl.com [62.253.187.226] 9 38 ms 22 ms 33 ms 15 ms 20 ms 34 ms 52 ms 33 ms 58 ms 39 ms www.ntlworld.com [212.250.162.47] Ping statistics for www.ntlworld.com Packets: Sent = 10, Received = 10, Lost = 0 (0.0%) Round Trip Times: Minimum = 15ms, Maximum = 58ms, Average = 34ms so as you can see your traceroutes's are exceptionally good. |
Re: [Merged] Manchester Issues
Has anyone in Manchester got 10mbps yet, i was told they were performing hardware updates and they would only guarantee 3mb up until this date which to be fair they have.
Although it is now the 24th and still on 3mbs. :( |
| All times are GMT +1. The time now is 09:13. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum