North Tonawanda, NY
·Verizon Online DSL
|reply to jamesonnorth |
Re: [DSL] Extreme Slow downs Frontier 12/2
I can attest to what Hank is talking about. I can't chime into the sync rate being affected by congestion, unless it's the DSLAM being told to set lines to certain speeds under certain conditions. That, or if there is a lot of crosstalk in a trunk because of a high volume of connections running in there. I can chime into the disconnects being caused by congestion though. If there is a technical reason as to why the sync rate drops from congestion (bandwidth, not something noise related or exceeding the limit of customers a remote should have active) I'd love to hear it!
Verizon has a bunch of older remotes from Catena in this area which are connected back to the Central Office using T3 lines, delivered over Fiber. Many of these older remotes are somewhat rural and have gone unupgraded for quite a while and have needed to take on additional loads, such as brand new neighborhoods springing up or heavier loads. One of my relatives who used to have DSL with them and has since moved to Cable Internet used to have this issue. For over a year and a half, every day or two, sometimes several times a day their Internet connection would go into a constant re-synchronization for up to several hours. The modem would train, immediately drop the connection before it could start to establish PPPoE connectivity, and then start the whole process over. It was an issue with the entire remote, and every line would drop as a result. I believe it was due to an issue with the remote's Integrated DSLAM that caused it to reboot since that is how it behaved. Even when Verizon did fix that issue, or when it ironed itself out the remote suffered from heavy congestion at night for years. Speed tests would be around 50kbps download, 100kbps upload on a 1.5Mbps/384kbps circuit, PPPoE connections would drop, and latency when idle would be in the hundreds. The circuit on the remote was found to be running beyond 92% capacity, often a step or two from 100% for about 15 days out of the month. No one gave a glance at the remote and instead the solution was to keep sending modems. No idea how it's running to this day. Hopefully it gave up and died or got hit by a snow plow or from lightning so it'd get some much needed attention.
The irony of the above situation as well: The remote sits 1000 feet away in a farm field from a location that is served by Verizon FiOS, in another county and from another CO.
That irony is the sad truth in the broadband world. 100 people served by two or three 45mbps lines, and 1000 feet away there's capacity for hundreds of megabits probably with less than 40% utilization.
I'm pretty sure my CO has an OC3 or higher, and I bet the remotes are in a similar situation to your area. Luckily I'm not on a remote or I'd really be screwed. I guess living in a rural area I'm lucky to get 6mbps. It's not 1000 feet away, but there is at least one if not more of at least 1gbit line of dark fiber line running about 3 miles away. If Frontier cared to expand my area, they could have 25mbps VDSL for half the cost of Comcast and drive them out. Unfortunately I doubt that will happen until 50mbps is the norm for Comcast.--
CompTIA Net+ Network Administrator - I know networks!
Professional Photographer - www.jnphoto.biz - Weddings and Senior Photos
Nice and comfy with Frontier DSL: I can help with your issues!
North Tonawanda, NY
·Verizon Online DSL
I should say, in the case of this remote it was one T3 line per DSLAM. The T3 was sent over OC12 Fiber. I don't know how many DSLAMs were available in that remote but things got pretty bad. It's not like the Litespan I feed out of for Verizon which has OC3 fiber directly going to it (it's old, too) or Frontier's Adtran DSLAM in the remote which I would presume has at least an OC3, the remote itself probably having an OC12 back to the CO with their higher VDSL2 speeds now being available to me.