PE's will drop ICMP packets if their too busy handling other traffic.
Thought if the desitnation machine is configured to respond on ICMP, you can
very well troubleshoot using traces.
For this, you can best use a program called (win)MTR, Linux users mostly
have this pre-installed, windows users can download the windows version
from: http://winmtr.sourceforge.net
With this tool you can messure packetloss, and other routings issues.
if the last hop (destination IP) doesnt show any packetloss, the line is
having no issues (if you messure packetloss in the middle, but not in the
end, its simply PE's dropping ICMP requests directly aimed at them).
If you messure extreem high pings, you can pretty much see in the MTR trace
were exactly this starts off, and hand over the traces to your ISP so they
can either change their routing, or contact the 3rd party having the issues.
Cheers,
Saint K.
----- Original Message -----
From: "Edward Luna" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, January 24, 2007 3:17 PM
Subject: RE: [hlds] [OT]Savvis Metwork
I wouldn't put too much faith in trace routes for troubleshooting lag
issues. Not that it can't be an indicator mind you, but I'm pretty sure a
trace route is a low priority item for routers.
-----Original Message-----
From: J. Laws - Hi-Definition Gaming [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 23, 2007 11:25 PM
To: [email protected]
Subject: RE: [hlds] [OT]Savvis Metwork
Or you could stop using a Playskool network and have a return path along
the
lines of this:
traceroute to 4.69.132.210 (4.69.132.210), 30 hops max, 46 byte packets
1 border6.fe6-21.globalcon-4.chg.pnap.net (69.25.252.125) 0.358 ms
0.313
ms 0.370 ms
2 core3.te6-1-bbnet1.chg.pnap.net (64.94.32.3) 0.345 ms 0.328 ms *
3 128.242.186.173 (128.242.186.173) 0.452 ms 0.477 ms 0.394 ms
4 xe-0-1-0.r21.chcgil09.us.bb.gin.ntt.net (129.250.3.13) 0.553 ms 0.544
ms *
5 as-1.r02.chcgil09.us.bb.gin.ntt.net (129.250.2.245) 0.484 ms 0.470 ms
0.449 ms
6 ge-0.level3.chcgil09.us.bb.gin.ntt.net (129.250.9.18) 153.725 ms
182.374 ms 2.128 ms
7 ae-32-52.ebr2.Chicago1.Level3.net (4.68.101.62) 5.594 ms 0.881 ms
ae-32-54.ebr2.Chicago1.Level3.net (4.68.101.126) 14.570 ms
8 ae-5-5.car1.Cincinnati1.Level3.net (4.69.132.205) 7.398 ms * 7.495 ms
9 ae-11-11.car2.Cincinnati1.Level3.net (4.69.132.210) 7.344 ms * 7.255
ms
-----Original Message-----
From: Gary Stanley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 23, 2007 10:54 PM
To: [email protected]; [email protected]
Subject: RE: [hlds] [OT]Savvis Metwork
Looks like level3 is having a fit, might be return path issue.
traceroute to 74.130.80.1 (74.130.80.1), 64 hops max, 40 byte packets
1 ge0-1-1000M.ar1.ChicagoEquinix.velocity-servers.net
(66.225.194.1) 0.615 ms 0.577 ms 0.604 ms
2 unknown.ord.scnet.net (205.234.205.17) 0.480 ms 0.357 ms 10.103 ms
3 po4.ar1.ord1.us.scnet.net (216.246.50.2) 0.480 ms 0.597 ms 0.482 ms
4 tge9-3-10G.ar1.ord1.us.scnet.net (216.246.50.154) 16.101 ms 0.361 ms
0.362 ms
5 level3-02172-chi-bb1.telia.net (213.248.84.54) 34.956 ms 34.284 ms
ge-6-6.car3.Chicago1.Level3.net (209.0.227.73) 33.685 ms
6 ae-32-54.ebr2.Chicago1.Level3.net (4.68.101.126) 46.185 ms
ae-32-56.ebr2.Chicago1.Level3.net (4.68.101.190) 34.848 ms
ae-31-53.ebr1.Chicago1.Level3.net (4.68.101.94) 37.889 ms
7 ae-5-5.car1.Cincinnati1.Level3.net (4.69.132.205) 42.658 ms 41.722
ms
41.709 ms
8 ae-5-5.car1.Cincinnati1.Level3.net (4.69.132.205) 40.833 ms
ae-11-11.car2.Cincinnati1.Level3.net (4.69.132.210) 42.729 ms 41.804
ms
9 INSIGHT-MID.car2.Cincinnati1.Level3.net (63.210.248.18) 43.828 ms
44.579 ms
ae-11-11.car2.Cincinnati1.Level3.net (4.69.132.210) 41.586 ms 10
74.128.8.121 (74.128.8.121) 54.463 ms 53.532 ms 53.445 ms
At 10:28 PM 1/23/2007, Scott Pettit wrote:
Your first hop is lagging - sort your own connection out first.
-Scott
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Munra -hlds
Sent: Wednesday, 24 January 2007 4:04 p.m.
To: [email protected]
Subject: [hlds] [OT]Savvis Metwork
As any one notice or had anyone Complain about lag when hopping though
the Savvis Network?? OR any other network on the East Coast?
1 <1 ms <1 ms <1 ms 192.168.1.1
2 158 ms 13 ms 79 ms 74-130-80-1.dhcp.insightbb.com
[74.130.80.1]
3 43 ms 25 ms 15 ms 74-128-22-97.dhcp.insightbb.com
[74.128.22.97]
4 75 ms 7 ms 44 ms 74.128.8.97
5 31 ms 32 ms 46 ms sl-gw25-atl-10-0.sprintlink.net
[144.232.212.249
]
6 25 ms 21 ms 53 ms sl-bb21-atl-5-0.sprintlink.net
[144.232.22.13]
7 57 ms 21 ms 41 ms 144.232.8.182
8 107 ms 111 ms 118 ms dcr2-so-0-2-0.Atlanta.savvis.net
[208.172.65.246
]
9 72 ms 42 ms 48 ms dcr1-as0-0.Atlanta.savvis.net
[204.70.192.41]
10 40 ms 133 ms 40 ms bcs1-so-2-0-0.Washington.savvis.net
[204.70.192.
54]
11 161 ms 158 ms 83 ms ber2-pos-7-0-0.Chicago.savvis.net
[208.175.10.25
4]
12 70 ms 53 ms 185 ms ber2-tenge-3-1.chicagoequinix.savvis.net
[204.70
.196.26]
13 100 ms 69 ms 98 ms 208.173.176.214
14 103 ms 194 ms 111 ms po1-4G.ar1.ord1.us.scnet.net
[64.202.110.62]
15 94 ms 116 ms 155 ms po1-4G.ar1.ord1.us.scnet.net
[64.202.110.62]
16 126 ms 140 ms 171 ms ge0-1.aggr201.ord1.us.scnet.net
[216.246.94.6]
17 181 ms 121 ms 110 ms unknown.ord.scnet.net [20x.xx.249.xx]
Trace complete.
The server in this Trace is in equinux data center in chicago
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
