 | Packet Loss - Line or CO Issue? Before contacting VZ |  After contacting VZ |
I've been helping a friend who has Verizon DSL in Springfield, MA. He is on the 3/768 tier, interleaved. Worked fine for years. He's been having lots of packet loss for the past two weeks. I helped him get in touch with Verizon, who did some line tests, and then reduced his provisioning to what looks like around 1.5/384. It didn't correct the issue. They also sent a new modem this week (the Actiontec, was a Westell 7500), but that also didn't help. They want to roll a truck on Monday. I put the line stats below. In ping tests, he has packet loss starting at the gateway hop (the 10.x.x.x hop after the modem)
Could this be a line issue or a CO issue? I'm curious if anyone has any insight. He's not in a FIOS area, so unfortunately he can't move to that platform.
Line stats are in the images attached, both before contacting VZ and after. |
|
|
|
 | May be both. More likely the CO.
Stats look fine here although line degradation due to copper oxidation on the wire can affect stats.
There has been a routing issue noted from the FiOS side of things as well. Some nodes transferring cross America and the world are overloaded, so a lot of speeds have been throttled in an attempt to fix the congestion issue. We know the real answer to that.
Just a warning. The truck tech may advise you to downgrade to the lowest speed package and will claim that will fix everything. Letting you know one of the ridiculous fixes these techs advise. |
|
 | reply to chrisb3127
Thanks for the info! I think it's a CO issue too. They already cut the provisioning in half, so it's obvious a slower speed tier isn't a "fix" like they try to say. I will let my friend know to be nice but firm with them if they suggest anything crazy like that. |
|
 | reply to chrisb3127
Is the packet loss only on wireless? |
|
 | No, it's on both wired and wireless. External pings to the IP also have the same packet loss. |
|
 | reply to chrisb3127
Just an update. Truck roll was today, they replaced the NID and rewired the modem with a fresh wire from the basement termination to the room the modem is in. The stats improved, but the connection still has a lot of packet loss. |
|
 | reply to chrisb3127
Does anyone here have any other suggestions as to what the underlying issue might be? I was thinking it has to be something at the CO, now that the modem and home wiring was all replaced. Is there any way to word it correctly for VZ to verify the circuit the line is on at the actual CO? |
|
 tschmidtPremium,MVM join:2000-11-12 Milford, NH kudos:8 Reviews:
·G4 Communications
·Fairpoint Commun..
·Hollis Hosting
| reply to chrisb3127
Ideally look at low level router stats to see transmission errors. But my guess is since you have reasonable margin the IP errors are not the result of problems with the DSL link itself. Those are normally hidden by ATM transport.
Have you figured out where packet loos is occurring? Try running Traceroute (tracert in windows) to stable sites like this one. See if you can determine which hop they are being dropped. Once you know that if you want you can run a constant ping to that site.
You can also use the line quality test on the tools page, that test line from the other direction.
/tom |
|
 | reply to chrisb3127
I think you answered your own question in your first post. I think that hop is the router at the CO. The noise margins at the slower tier look pretty good and should be stable.
said by chrisb3127:In ping tests, he has packet loss starting at the gateway hop (the 10.x.x.x hop after the modem)
|
|
 | I would call Tier 2 support ,your noise margin is great. Ask tier 2 to change your redback router it is congested .The redback is on their end it is more than likely congested. |
|
 | reply to chrisb3127
Thanks for the info! Presidential Appeals has been handling the case now. They say they don't see any issues on the line, but they offered to move the line to a different circuit at the CO tonight. Hopefully the circuit move will do the trick and resolve it. |
|
 | reply to chrisb3127
Just to update just in case others ever have this issue creep up. They re-created the circuit at the CO level. The issue is resolved, no more packet loss, and I noticed trace routes are a little different (only one Springfield MA hop versus two before the switch).
Only question is -- the account was on 3/768 for a very long time. When the issue started they cut the provisioning to 1.5/384. Based on the stats posted on the first post, do you think it's safe to request the 3/768 plan back? |
|
 | reply to chrisb3127
Last update! Everything is good now. The line automatically had the speed increased without asking. Must be part of that automatic optimizer thing Verizon uses. Everything is rock solid again! The circuit rebuild was all that was needed to resolve the issue. |
|