dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
6895
share rss forum feed

wchill09

join:2012-10-15
Onondaga, MI

[DSL] drop outs, connection interupted....multiple service calls

Well, here goes....I was ready to pull the plug on Frontier DSL but I recently found this forum and thought I'd give it a try to see if I can get any help with the problem (Since I can't get anywhere with Frontier). We had Frontier DSL installed about a month and a half ago. The lines in the house were questionable so the installer cut the entry line and installed new wiring to where the modem (Netgear 7550) was installed. This is now the only line in the house. The speed of our connection was great but the connection was very unreliable and required powercycling the modem 10+ times per day to bring the connection up. Kept getting "connection was interupted" and/or DNS server errors. Called tech support and they sent a tech out and changed the outdoor phone box on the house as it was corroded. That did nothing. Called again in a few days and they sent out another tech who said it was programming and they were working on it.....? Again, it did nothing. Waited another week or so and called again. Again they sent out a tech and they changed the modem. Frontier (Netgear 7550). Also changed the port I was connected to in the main box down the road. Speed now is unbelievable at 16M down and 700K up....but still it is the same unreliable connection.....Green dsl light stays green and solid, internet light alternates from solid green to flashing green and occasionally red. When I get a connection interupted message or DSL server error the only way I've found to get back online is to powercycle the modem. It then comes back up and all is well for a while....sometimes 5 minutes, sometimes 30 minutes....I've helped the DNS server issue somewhat by changing the settings for the DNS server in the modem. I'm now using public DNS servers at OpenDNS but have also tried the public servers at Google with pretty much same results.....Called again 4 days ago and was given a call ticket# and I would hear something within 24 hours.....I'm still waiting.....starting to think they have given up..... We had a Sprint aircard prior to this and I could probably count on one hand the number of times it was down over the last two years.....Granted it was about 600k down but it was ALWAYS there and reliable.

Any ideas on where I go from here? Is there something else I can change to help the issue or is it all Frontier? Thanks for any help you may be able to offer.



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24

Re: [DSL] drop outs, connection interupted....multiple service c

What are your Transceiver Statistics looking like? When the Internet goes down, what do they look like at that point before you reboot the modem?


wchill09

join:2012-10-15
Onondaga, MI

Click for full size
Here is a screenshot of stats just prior to restarting modem:

Aranarth

join:2011-11-04
Stanwood, MI
Reviews:
·Frontier Communi..
reply to wchill09

Wow that's a lot of FEC errors if it has only been up for 1/2 an hour.
I usually see that many after a week on my line last time I checked.

I would ask to have your max connection speed limited to 17 or 15Mbps down and see if that helps.

You could also ask them to switch you to a different Dslam if they can. Dropping your speed a little bit may allow you to switch to fast path which will give you a better connection over all as well. (Latency wise)

FEC, HEC, and CRC errors types are a little confusing so here is some reading:
»en.wikipedia.org/wiki/Forward_er···rrection
»en.wikipedia.org/wiki/Header_Error_Control
»en.wikipedia.org/wiki/Cyclic_red···cy_check

Basically the high FEC error rate points to a noisy line. Basic troubleshooting you can do:
Do you have filters on every phone jack? sometimes adding a filter even if there is nothing plugged can be helpful.
Does the phone line pass along side a power cable? (crossing is fine laying along side is not)
Does the phone line pass by any large AC motors such as fridge, freezer, or other large type load such as florescent light's ballast, microwave, electric stove or oven etc?
How far away from the NID is your modem? (actual cable length is helpful)

Have they replaced the wires from the network box on the street to your nid or have they been checked that they are in good shape?


wchill09

join:2012-10-15
Onondaga, MI

The only line we have in the house is the new one installed to the dsl modem. The connection was cut where it enters the house and new was installed from there....Because it only went to the modem no filter was installed....

Phone line enters the house about 24" from the power service entrance cable.

Phone line is pretty much a straight shot. Enters the house through basement wall, crosses joist space and enters room with modem. Total inside distance is less than 20 feet....

The distance from the box on the outside of the house to the modem is about 25 feet.

Tech supposedly checked wire condition as that was part of our conversation during the install. He said because wires were good it was going to be an easy install, no digging for a new incoming line....


wchill09

join:2012-10-15
Onondaga, MI

Click for full size
Status update:

Called tech support yesterday and tech came this afternoon. Checked line condition and said it does have noise but that it shouldn't affect the dsl connection. Checked wires from outside box on house to box on pole and also to the main box down the road and said they were OK....He did seem thorough in his testing and was genuinely trying to find a fix....but it wasn't until he saw 150K+ FEC errors (6 hour time frame) in the log that he truly knew what we were experiencing here. It definitely helped having hard copies of the transceiver log to try and show what is going on between modem restarts. What he did do was to back the speed down to where it should have been....7.8M down, 850k up in addition to cleaning up terminal connections both here and down the road. It HAS made quite a bit of improvement in the reliability of my connection. Been on for about 3 hours now and only had to restart once.....FEC errors are at 953. He is supposed to followup tomorrow and if problem persists will change to another port and possibly back the speed down some more..... , I will keep you posted of status and will attach the current transceiver stats:

slopoke

join:2012-05-20
London, OH
reply to Aranarth

Good advice. Needs to make sure modem is plugged in away from heavy loads. Ours used to cycle when the air conditioner started. Plugged into outlet not on busy breaker.
--
Just Me and My Acer. And a bag of chips.


Aranarth

join:2011-11-04
Stanwood, MI
Reviews:
·Frontier Communi..
reply to wchill09

Personally I would get the modem moved so it is as close to the nid as absolutely possible. if you can get a shelf in the basement right where it comes in, split the line, put a plug on each end, use a filter so the modem had a short (6ft or less) phone cable and the from the phone side of the splitter to provide phone service to the rest of the house.

Let me put it to you this way here are my line stats:

Up Time 37:22:13:16 (yep almost 38 DAYS)
Transceiver Information Down Stream Path Up Stream Path
DSL Speed (Kbits/Sec) 3360 847
Margin (dB) 8.7 6.1
Line Attenuation (dB) 49.8 34.2
Transmit Power (dBm) 17.2 11.2
FEC Errors 0 0
HEC Errors 351444 67216
CRC Errors 664393 0

My modem is wired in just like I describe. Once your connection is stable you should see stats like mine.

Note if your connection still isn't stable then the noise on the line is not coming from inside the house. If the phone line (trunk line) passes too close to a power transformer they may have to move it to fix the line noise.


staregazer

join:2006-12-15
Reviews:
·Frontier Communi..

1 edit
reply to wchill09

My internet has been losing connection with the DNS server a lot this past week, getting speeds as slow as 1 MB down now as well during the evening but still getting 17-18 MB down around 2-3 am. They said they would send someone out to look at the modem but they never show up when they say they will and getting tired of dealing with them. Line Margin and Attenuation values look great. Any other issue in the statistics show any issues? I have also connected straight into the outside box and still have the same issues.

Sometimes when I reboot the modem the internet comes back. I rebooted the modem about half an hour ago before posting these stats but the internet was not on at first then came on about ten minutes later.

Statistics -- ADSL1

Mode: ADSL2+
Line Coding: Trellis On
Status: No Defect
Link Power State: L0

Downstream Upstream
SNR Margin (dB): 26.7 16.6
Attenuation (dB): 3.0 2.0
Output Power (dBm): 0.0 11.4
Attainable Rate (Kbps): 25964 1256
Rate (Kbps): 11996 1019
MSGc (number of bytes in overhead channel message): 89 12
B (number of bytes in Mux Data Frame): 254 31
M (number of Mux Data Frames in FEC Data Frame): 1 1
T (Mux Data Frames over sync bytes): 1 4
R (number of check bytes in FEC Data Frame): 0 0
S (ratio of FEC over PMD Data Frame length): 0.6775 0.9961
L (number of bits in PMD Data Frame): 3011 257
D (interleaver depth): 1 1
Delay (msec): 0 0

Super Frames: 44941 40334
Super Frame Errors: 0 0
RS Words: 0 0
RS Correctable Errors: 0 0
RS Uncorrectable Errors: 0 N/A

HEC Errors: 0 0
OCD Errors: 0 0
LCD Errors: 0 0
Total Cells: 20451302 1726544
Data Cells: 116427 1726544
Bit Errors: 0 0

Total ES: 0 0
Total SES: 0 0
Total UAS: 16 16

Statistics -- ADSL2

Mode: Adsl2p, USINP = 0.0, USDELAY = 0 msec, DSINP = 0.0, DSDELAY = 0 msec
Channel: Fast
Status: Showtime

Downstream Upstream
SNR Margin (dB): 25.3 13.3
Attenuation (dB): 5.0 2.0
Output Power (dBm): 0.0 dBm 10.4 dBm
Rate (Kbps): 11996 1147
Super Frames: 46998 44429
Super Frame Errors: 0 0

LPR Errors: 0
HEC Errors: 0
LCD Errors: 0
Total FE ES: 0
Total ES: 0
Total SES: 0

Tracing route to www.google.com [173.194.75.103]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.254.254
2 * * * Request timed out.
3 41 ms 95 ms 248 ms ge--0-0-0---0.car01.chtn.wv.frontiernet.net [74.
42.149.49]
4 91 ms 239 ms 44 ms ae4---0.cor02.chcg.il.frontiernet.net [74.40.1.5
3]
5 * 1689 ms 214 ms ae1---0.cor01.asbn.va.frontiernet.net [74.40.2.1
94]
6 97 ms 240 ms * ae1---0.cbr01.asbn.va.frontiernet.net [74.40.2.1
74]
7 * 49 ms 44 ms 72.14.213.133
8 148 ms 148 ms * 216.239.46.250
9 1016 ms 239 ms * 72.14.236.152
10 * * * Request timed out.
11 85 ms 1434 ms 58 ms 216.239.48.159
12 * * * Request timed out.
13 * * 175 ms ve-in-f103.1e100.net [173.194.75.103]

Trace complete.

I pinged the Charleston server listed on the tracert and it seems to be an issue between my place and there. Pinging to my router gives me 1 ms.

Pinging 74.42.149.49 with 32 bytes of data:
Request timed out.
Reply from 74.42.149.49: bytes=32 time=339ms TTL=62
Reply from 74.42.149.49: bytes=32 time=812ms TTL=62
Reply from 74.42.149.49: bytes=32 time=116ms TTL=62
Reply from 74.42.149.49: bytes=32 time=114ms TTL=62
Reply from 74.42.149.49: bytes=32 time=523ms TTL=62
Reply from 74.42.149.49: bytes=32 time=305ms TTL=62
Reply from 74.42.149.49: bytes=32 time=439ms TTL=62
Request timed out.
Reply from 74.42.149.49: bytes=32 time=15ms TTL=62
Reply from 74.42.149.49: bytes=32 time=1117ms TTL=62
Reply from 74.42.149.49: bytes=32 time=627ms TTL=62
Request timed out.
Reply from 74.42.149.49: bytes=32 time=163ms TTL=62
Reply from 74.42.149.49: bytes=32 time=1351ms TTL=62
Request timed out.
Request timed out.
Reply from 74.42.149.49: bytes=32 time=140ms TTL=62
Reply from 74.42.149.49: bytes=32 time=104ms TTL=62
Reply from 74.42.149.49: bytes=32 time=147ms TTL=62
Reply from 74.42.149.49: bytes=32 time=16ms TTL=62
Reply from 74.42.149.49: bytes=32 time=828ms TTL=62
Reply from 74.42.149.49: bytes=32 time=651ms TTL=62
Reply from 74.42.149.49: bytes=32 time=441ms TTL=62
Reply from 74.42.149.49: bytes=32 time=117ms TTL=62
Reply from 74.42.149.49: bytes=32 time=71ms TTL=62
Request timed out.
Reply from 74.42.149.49: bytes=32 time=44ms TTL=62
Reply from 74.42.149.49: bytes=32 time=1048ms TTL=62
Request timed out.
Reply from 74.42.149.49: bytes=32 time=763ms TTL=62
Reply from 74.42.149.49: bytes=32 time=377ms TTL=62
Reply from 74.42.149.49: bytes=32 time=16ms TTL=62
Reply from 74.42.149.49: bytes=32 time=18ms TTL=62
Reply from 74.42.149.49: bytes=32 time=66ms TTL=62
Reply from 74.42.149.49: bytes=32 time=60ms TTL=62
Reply from 74.42.149.49: bytes=32 time=14ms TTL=62
Request timed out.
Reply from 74.42.149.49: bytes=32 time=283ms TTL=62
Reply from 74.42.149.49: bytes=32 time=323ms TTL=62
Reply from 74.42.149.49: bytes=32 time=65ms TTL=62
Reply from 74.42.149.49: bytes=32 time=191ms TTL=62
Request timed out.
Reply from 74.42.149.49: bytes=32 time=1202ms TTL=62
Reply from 74.42.149.49: bytes=32 time=1054ms TTL=62
Reply from 74.42.149.49: bytes=32 time=118ms TTL=62
Reply from 74.42.149.49: bytes=32 time=90ms TTL=62
Reply from 74.42.149.49: bytes=32 time=28ms TTL=62
Reply from 74.42.149.49: bytes=32 time=114ms TTL=62
Reply from 74.42.149.49: bytes=32 time=112ms TTL=62
Reply from 74.42.149.49: bytes=32 time=490ms TTL=62
Reply from 74.42.149.49: bytes=32 time=403ms TTL=62
Reply from 74.42.149.49: bytes=32 time=66ms TTL=62
Reply from 74.42.149.49: bytes=32 time=259ms TTL=62
Reply from 74.42.149.49: bytes=32 time=767ms TTL=62

Ping statistics for 74.42.149.49:
Packets: Sent = 55, Received = 46, Lost = 9 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 1351ms, Average = 356ms


Action2

join:2010-06-29
Newman, IL
kudos:1
Reviews:
·Frontier Communi..

Were you running those tests during prime time? Bonded DSL puts up extremely high latency numbers when congestion is apparent. The only issue I see is that your upstream ADSL1 is still either out of sync or provisioned wrong. It should normally be 1147 kbps.

I do get minor packet loss when the the connection is under load, but yours does seem a bit high.


wchill09

join:2012-10-15
Onondaga, MI

Click for full size
FINALLY, SOME RESULTS

As the saying goes, if at first you don't succeed, try, try, again.....It may be too early to tell but service call #6 appears to have impacted the problem. The system has been up for 6 hours and only 54 FEC errors. No drops, connection is solid, and I'm finally starting to get a smile on my face.....The tech changed the wires that go from outside box on house to box on telephone pole, even though they checked good. Then tested the line again from box on pole to main box down the road (.9 mile) and made adjustments/changes there. And finally, with the modem stats I have been saving and printing we had good proof of the errors. Since the errors increased exponentially with the speed I was all for backing it WAY down but he was having a difficult time convincing the main office that that was the way to approach a fix.....They finally agreed to drop the speed to 3M (down) and if needed, will drop to 1.5 (down) next week. Thankfully, the system has been up for 6 hours with only 54 FEC errors. GREAT IMPROVEMENT AND NO DROPPED CONNECTIONS! Only time will tell...

wchill09

join:2012-10-15
Onondaga, MI
reply to wchill09

Click for full size
Status update:

Techs have finally solved our high error rates but a problem still persists with drops.....I've used ping plotter to try and get some insight into what is happening so I can accurately describe to support what my issue is. I would certainly appreciate any input you may have on a cause and/or a solution. Above is a screen shot when system is normal:

wchill09

join:2012-10-15
Onondaga, MI
reply to wchill09

Click for full size
Click for full size
Click for full size
Above is a screen shot just when I start to loose the connection followed by when it is totally gone....at this point I can either restart the modem and connection will immediately come up or I can wait 3-4 minutes and connection will be back. The last screen shot is modem stats....where do I go from here?

Aranarth

join:2011-11-04
Stanwood, MI
Reviews:
·Frontier Communi..
reply to wchill09

I would move the modem as close to the NID as previously suggested.
You are still getting fec errors which still shows some noise on the line.

Hopefully getting closer to the nid will help solve the final issue.
(I'm hoping the final noise is coming from inside your house.)


wchill09

join:2012-10-15
Onondaga, MI

said by Aranarth:

I would move the modem as close to the NID as previously suggested.
You are still getting fec errors which still shows some noise on the line.

Hopefully getting closer to the nid will help solve the final issue.
(I'm hoping the final noise is coming from inside your house.)

OK, tomorrow I will move the modem outside and plug into the NID box. I believe I can connect directly there. At the end of the day I'll post modem stats and we can go from there.

Thanks

wchill09

join:2012-10-15
Onondaga, MI
reply to Aranarth

Click for full size
Click for full size
said by Aranarth:

I would move the modem as close to the NID as previously suggested.
You are still getting fec errors which still shows some noise on the line.

Hopefully getting closer to the nid will help solve the final issue.
(I'm hoping the final noise is coming from inside your house.)

I moved the modem outside next to the network box and plugged it directly into the box, then left it for 8 hours. Only one port on the modem was used to connect the garage system to the modem. Screenshots are as above....DSL stats are for the 8 hour time frame. Still appear to be getting FEC errors....right at the box.


Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Reviews:
·Verizon Online DSL
·Frontier Communi..

That many FEC errors during that time is insignificant. If they're increasing at a steady rate or look at something like this:

... then you have problems. That isn't problematic. If the dropouts are still occurring, which they are, have Frontier check their equipment out for any alarms or failures. Something could be bouncing or having issues. It may be with the line card, or it may be with the DSLAM itself, or something further. PPPoE connectivity should not drop, and you should not have a sudden slow-down. ATM Statistics should be displayed by the modem if you want to try to get a copy of those. Under Advanced System Monitoring there should be an ATM Section or monitor that you can view statistics there. If you could provide those during a time when the modem is running good, and when it's running bad, that'd be appreciated.


Aranarth

join:2011-11-04
Stanwood, MI
reply to wchill09

Smith is right, you have just confirmed that whatever the issue is its not inside your home or with your equipment.

Frontier still has a little bit work left to resolve your issues with drop outs etc.



Hank
Searching for a new Frontier
Premium
join:2002-05-21
Burlington, WV
kudos:2
Reviews:
·Frontier Communi..

Concur with Smith - It is Frontiers issues. I have two DSL lines here and they both had the same issues, but the primary had way more drop outs and errors than my secondary. Turned out it was the equipment at both the CO and the remote. So keep pushing them. By the way I suggest that you keep a log of what they tell you they did and when. This is particularly important if you continue to have problems.


COjosh

join:2011-02-21
kudos:1
reply to wchill09

My two cents, for what it's worth-

When I was with ATT working w/ Uverse, we ran into some issues w/ customers being too close to the VRAD/DSLAM called FEXT- Far End Cross-Talk...

Basically the loop didn't have enough distance to properly attenaute which caused a ton of line noise and cross-talk. These issues caused the RG/Modem to bounce and the customer to lose sync on a loop, that by basic copper standards, would be considered perfect.

We "resolved' the issue by adding boxes, in some case as many as 3-4, of IW at the customer prem to help the loop attenaute properly...I left ATT before they came up with a permanent solution...

Granted we were using different tech, VDSL2, but your attenuation and SNR started to make me think..

Are you on ADSL2? Maybe see if they can bump you down to ADSL1..I've seen this sometimes resolve your intermittent sync/FEC problem.

Also, does the problem appear to be cyclical? Like, does it happen the same time everyday, does it happen every 15 minutes, etc? The FEXT issue was horribly regular, you could count on it to be down every 15 to 20 minutes like clockwork. The ADSL2 vs. ADSL1 issue however never has had any real rhyme or reason to it.

Just some ideas..



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Reviews:
·Verizon Online DSL
·Frontier Communi..

I wonder what is causing the drops when on ADSL2+ and I have a feeling I've asked this question a few months ago. It almost sounds like a profile configuration issue if drops are occurring while on an ADSL2+ card but not while on an ADSL card. OP also doesn't seem to be close enough to have Far End interference occur but I'm also not a line tech so I wouldn't know how far out you've seen such issues occur.

Strange. I wonder what the outcome of this issue will be.


COjosh

join:2011-02-21
kudos:1

The FEXT issue was experienced w/ subs generally within 4k feet or so, on VDSL2 mind you, and the ADSL2 problem seems to have been mostly less than 6.5k feet.

As far as why the ADSL2 anomoly, I really have no idea. I HAVE heard, however, that it has to do with how "hot" the SNR comes to the far-end modem. Most subs, on 3Meg, should be provisioned on an ADSL card as opposed to an ADSL2 that can provide faster sync rates and "louder" SNR values...at least that's the way I understand it, I could very well be wrong..

The OP does indeed appear to be further out than that..

Again, a shot in the dark, no more no less..



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24

Good to know. Thanks for the info! Never hurts to take a shot in the dark.


wchill09

join:2012-10-15
Onondaga, MI
reply to COjosh

Click for full size
Click for full size
Click for full size
Click for full size
Just want to say thanks for all of your input. It is appreciated.

Four screen shots, ATM, DSL, and 2 of ADSL , taken when it is working normally. 17 hours runtime.

wchill09

join:2012-10-15
Onondaga, MI

Click for full size
Click for full size
Click for full size
Click for full size
Screen shots of Pingplotter, ATM, DSL, and 1/2 screen of ADSL at point of dropping connection (Other 1/2 on next message). Connection was down 5 minutes then came back up....

wchill09

join:2012-10-15
Onondaga, MI

Click for full size
Click for full size
2nd half of ADSL screen shot when connection was down, and pingplotter when connection was restored 5 minutes later....

COjosh

join:2011-02-21
kudos:1
reply to wchill09

It's not like you're taking a ton of FEC's right before, or even leading up to, when the modem goes down..weird

It also doesn't look like any of the DSL stats fluctuate AT ALL during the period of time these screen shots were taken.

To be honest, I'm stumped...There are a SOME discard packets on the ATM side but nothing too unusual..

I'm of the opinion that this isn't copper trouble at all, at least not currently.

Does the DSL light actually go out/start to flash, or are we dealing with the Internet light going out but DSL staying solid?

From all the info you provided in the screen shots it would seem to be the later..


wchill09

join:2012-10-15
Onondaga, MI

said by COjosh:

It's not like you're taking a ton of FEC's right before, or even leading up to, when the modem goes down..weird

It also doesn't look like any of the DSL stats fluctuate AT ALL during the period of time these screen shots were taken.

To be honest, I'm stumped...There are a SOME discard packets on the ATM side but nothing too unusual..

I'm of the opinion that this isn't copper trouble at all, at least not currently.

Does the DSL light actually go out/start to flash, or are we dealing with the Internet light going out but DSL staying solid?

From all the info you provided in the screen shots it would seem to be the later..

Yes, the DSL light stays solid green but the internet light drops out. Occasionally it will turn red but not always....just goes out. Wait about 5 minutes and it will come back up or power cycle the modem and it will come up immediately.


Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Reviews:
·Verizon Online DSL
·Frontier Communi..

4 edits

Sounds like a key circuit is bouncing and failover is not going smoothly or getting a problem that is resulting in a ton of communication errors. If this is the case, a circuit should not be encountering an issue that often. Anyone nearby you seeing the same issue at all?

Some more food for thought. Before a family relative of mine moved to Cable Internet, they had Verizon DSL service that could operate at no more than 1.5Mbps/384kbps due to their line being 2.7 miles out from the remote. They were fed off of a Catena Remote Terminal with Integrated ADSL DSLAM which was fed by OC-12 fiber and demuxed to T3(or multiple T3s). This is a pretty old remote and had a fair amount of users on it, and it's age might account for the T3 connection. At random, the DSLAM would seem to stop working correctly where it would retrain every single line endlessly for up to a few hours at a time almost as if the unit was rebooting due to a fault. Phone service would continue to work without a single problem. This went on for about a year. After that was fixed, or so they say my relatives started noticing their Internet slowing down towards the night time hours. Towards the last few months of their service with Verizon being active the connection got to the point where it was nearly unusable at night, and PPP sessions would drop. I found out the circuit to the remote my relative was running through had been running at >90% capacity for a good handful of days each month. Their Ping Plotter looked just like yours too.

As on the previous page you posted some horrible ping results, I wonder if this is in fact a connectivity issue back at the DSLAM. If connectivity is having problems you won't lose sync but you will lose all connectivity that must transit back to the Central Office and isn't hosted locally by equipment at the DSL source. I don't know if you'll explicitly see ATM errors when this happens but if this is an IP DSLAM, you won't see that happen anyways due to the conversion from IP --- ATM at the DSLAM itself.


COjosh

join:2011-02-21
kudos:1
reply to wchill09

What Smith mentioned: "a circuit should not be encountering an issue that often. Anyone nearby you seeing the same issue at all?"

I think that's the nail on the head..any of your neighbors having the same problem?

Depending on how the various circuits make it back to the local aggregator and then to the POP, more people than you should be having similar issues. It IS possible that traffic out of your CO may be routed to more places than just one, yours being the circuit more impacted by the problem than the others.

I'd bet that this is a known problem and may be symptomatic of good ol' fashioned congestion...