I live in a neighborhood that is not served by FiOS because it is in Washinton DC - one mile from the vice Presidents House. Go figure. So I have a DSL link and it crashes occasionally - sometimes it runs for a month but some periods it crashes frequently. The most recent period of crashes began about a month ago. I do have a fix - reboot the router - but that gets tedious. The router is always up and available when the link is down so I feel quite comfortable that the problem is the link and not the router. I called support - telephone works OK even when DSL is down - and they gave me the usual spiel about checking my line. It was working fine b/c I rebooted the router so they saw no problems. Since 2 Aug I have been keeping track of the problem and one no day have I not had to reboot. That is, 9 days I had to reboot at least once and on six of those days I had to reboot twice in one day. I reboot whe I see it is down, mornings and evenings generally, but that probably is an artifact of my work schedule. I considered writing a script to ping somewhere every 10 minutes to track when the link goes down to see if there is a pattern to when the local switch reboots their DSL interfaces and leaves me hanging. I've also considered using the neighborhood chatlist to see if any other people are having problems with their Verizon DSL service.
Anyone else have any ideas for getting reliable Verizon DSL service in the nation's captal?
Solved! Go to Correct Answer
You are right - thanks. The line went down again this morning and I checked the transceiver stats before rebooting. The downlink noise margin was 0.-3 (sic) when it usually is around 6. After rebooting it was back to 6.
Thankyou for the help.
Whew, for a while there I thought I'd have a day without a lost connection. The "internet" light doesn't turn red, it goes off when the link is lost. The "DSL" light remains green as does "power" and "E1." "Wireless" also remains green. In other words, the only visible difference between connected and disconnected is that the "internet" light goes out. As seen from my computer, the router also remains fully accessible with no signs that it has suffered an internal malfunction.
Next time it is down I'll go through the system logs to see if they add any useful data although I have little doubt that the problem lies between my Westell 5700 and the local c/o. Looking at the logs now just tells me what happened after I rebooted.
Appreciate the assistance.
The correct path might be System Monitoring -> Advanced Status -> Transciever Stats.
I had hoped to include stats for the transceiver when the link was down but have not had a crash since the morning of the 13th. These are the stats for the transceiver while it is working fine.
Transceiver Revision A2pB020b3.d19d
Vendor ID Code 4D54
Line Mode ADSL_G.dmt
Data Path INTERLEAVED
Transceiver Information Down Stream Path Up Stream Path
DSL Speed (Kbits/Sec) 2944 832
Margin (dB) 6.8 9.0
Line Attenuation (dB) 40.0 25.0
Transmit Power (dBm) 18.8 11.9
This weekend I expect to run a test to compare the logs from a physical line failure to those from a logical line failure. As far as I can read the logs above and the lights, my problem is a logical disconnection rather than a physical one since the DSL link remains up but the internet connection drops. Similarly, the error logs only refer to logical problems rathe than physical problems. Of course, that is where I started, seeing the problem as being high in the OSI stack and on Verizon's end rather than in my modem or DSL path, but I don't usually spend my days troubleshooting modems, so YMMV.