Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Delirium on October 08, 2007, 07:09:05 PM
-
I'm getting consistent packet loss between ATT and attens when ping plotting to HTC. This only occurs during prime time...
Target Name: N/A
IP: 206.16.60.38
Date/Time: 10/8/2007 8:07:43 PM to 10/8/2007 8:07:52 PM
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.0.1]
2 10 ms 9 ms 9 ms 9 ms 9 ms 10 ms 9 ms 9 ms 10 ms 10 ms adsl-76-239-47-254.dsl.mrdnct.sbcglobal.net [76.239.47.254]
3 9 ms 9 ms 10 ms 9 ms 10 ms 9 ms 9 ms 9 ms 9 ms 10 ms dist2-vlan50.mrdnct.sbcglobal.net [66.159.184.195]
4 9 ms 10 ms 9 ms 10 ms 9 ms 9 ms 9 ms 9 ms 9 ms 10 ms bb2-10g2-0.mrdnct.sbcglobal.net [151.164.92.153]
5 19 ms 19 ms 19 ms 19 ms 19 ms 19 ms 19 ms 20 ms 18 ms 58 ms ex2-p4-1.eqabva.sbcglobal.net [151.164.95.103]
6 20 ms 20 ms 19 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 19 ms [12.122.79.73]
7 57 ms 58 ms 57 ms 57 ms 57 ms 57 ms 57 ms 57 ms 57 ms 57 ms tbr1.wswdc.ip.att.net [12.122.113.6]
8 53 ms 53 ms 52 ms 53 ms 52 ms 52 ms 52 ms 52 ms 53 ms 53 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
9 * * 54 ms 54 ms 54 ms 54 ms 54 ms 54 ms 54 ms 54 ms tbr2.dlstx.ip.att.net [12.122.10.90]
10 53 ms 52 ms 52 ms 52 ms 52 ms 52 ms 52 ms 52 ms 52 ms * br2.dlstx.ip.att.net [12.123.16.213]
11 53 ms 53 ms 53 ms 53 ms 53 ms 52 ms 53 ms 52 ms 53 ms 53 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
12 51 ms 50 ms 51 ms 51 ms 50 ms 51 ms 50 ms 51 ms 50 ms * mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
13 53 ms 53 ms 53 ms 52 ms 53 ms 53 ms 53 ms 53 ms 53 ms 53 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 52ms, Maximum = 53ms, Average = 52ms
-
Target Name: N/A
IP: 206.16.60.38
Date/Time: 10/8/2007 8:11:46 PM to 10/8/2007 8:11:55 PM
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.0.1]
2 10 ms 9 ms 9 ms 9 ms 10 ms 9 ms 10 ms 10 ms 9 ms 10 ms adsl-76-239-47-254.dsl.mrdnct.sbcglobal.net [76.239.47.254]
3 9 ms 9 ms 9 ms 10 ms 10 ms 9 ms 10 ms 9 ms 10 ms 9 ms dist2-vlan50.mrdnct.sbcglobal.net [66.159.184.195]
4 10 ms 9 ms 9 ms 10 ms 9 ms 9 ms 9 ms 9 ms 9 ms 38 ms bb2-10g2-0.mrdnct.sbcglobal.net [151.164.92.153]
5 18 ms 19 ms 20 ms 19 ms 19 ms 19 ms 19 ms 19 ms 19 ms 19 ms ex2-p4-1.eqabva.sbcglobal.net [151.164.95.103]
6 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms [12.122.79.73]
7 58 ms 57 ms 57 ms 77 ms 71 ms 58 ms 57 ms 57 ms 57 ms 57 ms tbr1.wswdc.ip.att.net [12.122.113.6]
8 52 ms 52 ms 52 ms 52 ms 52 ms 52 ms 52 ms 52 ms 52 ms 52 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
9 54 ms 54 ms 54 ms 54 ms 54 ms 54 ms 53 ms 54 ms 54 ms 54 ms tbr2.dlstx.ip.att.net [12.122.10.90]
10 52 ms 52 ms 53 ms 52 ms 52 ms 52 ms 53 ms 52 ms 66 ms 53 ms br2.dlstx.ip.att.net [12.123.16.213]
11 53 ms 53 ms 53 ms 53 ms 53 ms 53 ms 53 ms 53 ms 53 ms 53 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
12 * 50 ms * * * 51 ms 51 ms 51 ms 50 ms 51 ms mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
13 53 ms 53 ms 54 ms 53 ms 53 ms 53 ms 53 ms 53 ms 53 ms 54 ms [206.16.60.38]
Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 53ms, Maximum = 54ms, Average = 53ms
-
Well, I'm going to have to say you have nothing to worry about.
Routers tend to make ICMP replies a low priority on the todo list.
Durring peak times when a router is really pushing traffic it doesn't want to have to worry about ICMP info since it's not really data.
Normally if a router is in trouble due to saturated bandwidth, high proccess load on the line card ... You will see packet loss on that hop and every hop after it, including to it's destination. Which these plots do not show.
Now this could be intermittant but you would need to run this test a lot longer, say no less than 10 mins, but I would recomend 30 mins to 1 hour.
Then you would have to get a decent amount of no replies to consider it a bad route.