gsnider
join:2009-06-21
| Packet loss in SA, TX
I'm having some packet loss problems on my line. My ping tests to my default gateway don't drop any packets but go from a steady 20ms ping for a few minutes to 10 or 20 in the 200ms range, then back down. I get anywhere from 2-10% packet loss to my second hop at 63.1 consistently. Here are my test results for the past few days on the line quality test:
»/testhistory/1652895/c0ef6
This was my most recent ping test to 63.1 and line characteristics
Ping statistics for 216.198.63.1:
Packets: Sent = 100, Received = 94, Lost = 6 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 42ms, Average = 20ms
HARDWARE IDENTIFICATION
Manufacturer : [BeWAN/A888-1 ]
Serial Number : [srxl xxxxxxxxxxxxxxxxxxxxxxxxxxxx]
Hardware Identifier : 104AA888
Firmware Revision : PCI-ADW-1-0.4-0.1.0.2
TIME CONNECTED : 00:30:45
Modulation Mode : G.dmt
REMOTE MODEM IDENTIFICATION
Vendor Code : Vendor Country Code : 0
Standard Revision Number : 1
BITRATES (CHANNEL) : FAST INTERLEAVED
Near End (kbps) : 3008 0
Far End (kbps) : 512 0
LINE OPERATIONAL DATA (STREAM) : DOWN UP
Capacity Occupation (%) : 41 54
Noise Margin (dB) : 17.0 21.0
Attenuation (dB) : 28.0 15.5
Output Power (dBm) : 8.0 10.5
PERFORMANCE COUNTERS : FEC CRC HEC
Near End Fast Channel : 0 2 2
Near End Interleaved Channel : 0 0 0
Far End Fast Channel : 0 0 0
Far End Interleaved Channel : 0 0 0
»img265.imageshack.us/i/adsl.jpg/ |
|
Zak_D_H
Premium,VIP
join:2007-01-04
Salt Lake City, UT | Hi Gsnider,
Send me a PM with the account info and I will take a look. |
|
Zak_D_H
Premium,VIP
join:2007-01-04
Salt Lake City, UT | Hi Gsnider,
The line readings are great. I don't see any errors on the line. I am going to go ahead and create a support ticket on this issue as I have seen similar symptoms for other customers today (although non of them were in texas). |
|
gsnider
join:2009-06-21 | it looks like at&t is ramping up the line levels. I'm up to 10dbm downstream and 10.5 upstream and it seems to be improving |
|
gsnider
join:2009-06-21
| AT&T is scheduled to come out and check the line in the morning but I don't think it's the line. I'm running a ping to my 1st hop right now while downloading a file at 300kB/sec and I haven't lost any icmp packets. It looks like there's a problem either between at&t and grandecom or somewhere internal to grandecom. My ping is steady at 180ms but drops down to 45 or so for 1 or 2 pings which leads me to believe there are download packets being dropped at hop 2 or after which is freeing up layer 1 bandwidth for my continuous ping to go a little faster for a moment. Downloading an ubuntu iso at 300k/sec and here are my results from a non fragmented max mtu ping:
ping -n 1000 216.198.50.1 -f -l 1452
Ping statistics for 216.198.50.1:
Packets: Sent = 236, Received = 236, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 236ms, Average = 177ms
A small block of the pings:
Reply from 216.198.50.1: bytes=1452 time=192ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=179ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=188ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=198ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=183ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=183ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=188ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=188ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=236ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=138ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=144ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=156ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=164ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=186ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=193ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=41ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=66ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=83ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=182ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=218ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=188ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=188ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=178ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=190ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=184ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=184ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=186ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=190ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=181ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=182ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=181ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=180ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=182ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=175ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=184ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=184ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=185ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=181ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=181ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=181ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=181ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=172ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=183ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=183ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=176ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=185ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=185ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=186ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=186ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=186ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=186ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=186ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=190ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=180ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=181ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=180ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=180ms TTL=64
Reply from 216.198.50.1: bytes=1452 time=182ms TTL=64
|
|
gsnider
join:2009-06-21
| Well of course AT&T never showed. I ran some ping tests to 216.198.50.1 and 216.198.63.1 from time warner and from the dslreports line quality tool. Here are the results:
216.198.63.1:
»/linequality/nil/2534335
Ping statistics for 216.198.63.1:
Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 391ms, Average = 32ms
216.198.50.1:
»/linequality/nil/2534329
Ping statistics for 216.198.50.1:
Packets: Sent = 1000, Received = 978, Lost = 22 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 379ms, Average = 30ms
Can somebody troubleshoot with Grandecom? |
|
dslx_gm
Premium,VIP
join:2002-12-26
Winnetka, CA
| I have asked our network operations team to take a look. Since the latency is between you and the gateway, it typically indicates a problem on the DSL line itself or on the physical line. Have you tried replacing the phone cable and Ethernet cable that the modem are connected to. Are you connected directly to the DSL modem from the computer when running the test?
Thanks |
|
gsnider
join:2009-06-21
1 edit | I've tried 2 different modems, checked all the wiring in the house, used 2 different phone lines, 2 phone drops, 2 ethernet cables (when using the external modem). As you can see above, the packets are not being dropped at the 1st hop, it's between the 1st and 2nd hop(which indicates a network problem, not a dsl problem), even when being tested by 2 external networks as I showed in my last post.
Edit:
Just to clarify, the ping test in my last post was from my time warner cable connection, so the pings to the 2 ips were coming from external to grandecom's network. The post above that I show the pings to my default gateway from the dsl line with no packet loss even while downloading a large file. |
|
gsnider
join:2009-06-21 | My DSLExtreme ticket has been updated with latest info |
|
gsnider
join:2009-06-21
| It has been 9 days and still no progress has been made on this DSL service. This is quite clearly a layer 3 issue on the IKANO/DSLEXTREME network, yet AT&T has been called out 3 times. It is my understanding that AT&T provides a DSL and an ATM circuit. These are layers 1 and 2. I will restate my problem.
I have 100% connectivity to my first layer 3 hop, 216.198.50.1.
I get anywhere from 2-10% packet loss to my 2nd layer 3 hop, 216.198.63.1
The packet loss between these 2 hops can be verified by running continuous pings to these 2 hops from ANY external IP network.
I would appreciate it if you assigned a network engineer to this problem and not a Tier 2 DSL technician. This is unacceptable. I have done all of the necessary troubleshooting for you and I am still getting the run around.
Ping statistics for 216.198.50.1:
Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 175ms, Average = 47ms
Ping statistics for 216.198.63.1:
Packets: Sent = 500, Received = 464, Lost = 36 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 1226ms, Average = 53ms
OrgName: IKANO Communications Inc.
OrgID: IKAN
Address: 265 East 100 South
Address: Suite 240
City: Salt Lake City
StateProv: UT
PostalCode: 84111
Country: US
NetRange: 216.198.0.0 - 216.198.63.255
CIDR: 216.198.0.0/18
OriginAS: AS6137
NetName: IKANO-1
NetHandle: NET-216-198-0-0-1
Parent: NET-216-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.SISNA.COM
NameServer: NS2.SISNA.COM
Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
RegDate: 1999-02-03
Updated: 2008-01-16
OrgTechHandle: IPADM146-ARIN
OrgTechName: IPADMIN
OrgTechPhone: +1-801-924-0900
OrgTechEmail: ipadmin@ikano.com
|
|
gsnider
join:2009-06-21 | reply to gsnider
is anybody taking a look at this? |
|
dslx_gm
Premium,VIP
join:2002-12-26
Winnetka, CA
| Hi Gary,
I took a look at your ticket and it indicated that the AT&T technician that was dispatched to the location found good sync at the MPOE. I didn't see an indication of them going inside the location. Did they come in and test from the jack?
I took a look at your current line readings and they don't look good. Your upstream margin is extremely low and indicates that there is likely an issue on the line. Typically upstream issue indicate a problem on the far end at the home/location and usually something that isn't filtered properly. The line readings are below for your reference.
Issues on the physical line itself can cause degradation in the line and high ping times to the gateway or dropped packets. Based on your ping to the gateway, it looked like that was what we were seeing here.
We did have our network operations team take a look at the upstream bandwidth but didn't see any issues. I will ask them to take another look.
Do you have access to the MPOE? Can you try to plug in there?
DN STREAM SPEED The line is running at the maximum bit rate of 3008 kbps.
UP STREAM SPEED The line is running at the maximum bit rate of 512 kbps.
DN STREAM S/N The line noise margin is 19.5dB, which is above the target noise margin of 6.0dB.
UP STREAM S/N The line noise margin is 1.5dB, which is below the target noise margin 6.0dB and above the minimum noise margin of 0.0dB.
DN STREAM POWER The line power is 11.5dBm, which is below the maximum of 16.0dBm.
UP STREAM POWER The line power is 12.0dBm, which is below the maximum of 13.0dBm.
DN STREAM LINE CAPACITY The line is running at 38.0% of relative capacity on downstream transmission path.
UP STREAM LINE CAPACITY The line is already running at 100.0% of relative capacity on upstream transmission path.
Thanks
--
George
General Manager
DSL Extreme
Will work for reviews.  |
|
gsnider
join:2009-06-21
| The lines in the house have been tested twice and test fine. Are you looking at the right line? Here are my layer 1 levels
LINE OPERATIONAL DATA (STREAM) : DOWN UP
Capacity Occupation (%) : 41 54
Noise Margin (dB) : 17.5 21.0
Attenuation (dB) : 28.5 15.5
Output Power (dBm) : 8.5 10.5
|
|
dslx_gm
Premium,VIP
join:2002-12-26
Winnetka, CA
| I followed up on your account and the latest notes from our Tech Support team. They indicated that you may have lost dial tone on the phone line and were following up with AT&T by calling 611.
They are scheduled to follow up with you tomorrow.
Thanks
--
George
General Manager
DSL Extreme
Will work for reviews. |
|
gsnider
join:2009-06-21
| Somebody cut through my line outside. It's gonna be a few days for AT&T to come out and run a new one. I am still seeing horrible packet loss to your 216.198.50.1 node from outside of your network. I would like you to escalate this issue and take care of this immediately. If this packet loss issue is not resolved I will be filing a complaint with your parent corporation Ikano regarding the lack of customer support received regardless of the hours of troubleshooting I have done on your behalf.
Here is the most recent packet loss test to 216.198.50.1
»/linequality/2···/2539638 |
|
gsnider
join:2009-06-21
| I've attached a document that may help in troubleshooting. |
|
