jeffb666
join:2005-02-15
La Grange Park, IL
| Tracking down problems.
I have had people complain of timeouts and not being able to connect to a webserver of mine.
Also I noticed problems on my end as well browsing.
I have had to reboot the router on occasion.
I have had problems getting to www.ebay.com yet signin.ebay.com works.. not sure if this is related.
I have complains of people having the connection issue when there is higher traffic coming in.. yet in the slower times it seams ok.
The router (briteport 8120) is showing:
Line Mode G.dmt
Line State Show Time
DS Speed 3008 Kbps
US Speed 768 Kbps
DS Latency Interleave
US Latency Interleave
Trellis Coding Enabled
Loss of Signal 0
Line Attenuation 55 dB
Loss of Frame 0
Down Noise Margin 17 dB
Down CRC Error 228
Up Noise Margin 9 dB
Up CRC Error 8
Line Up Count 1
Error Second 176 seconds
Line Up Time 0:21:39:31
System Up Time 0:21:39:59
Any help is appriciated.
Thanks,
Jeff |
|
leibold
Premium,MVM
join:2002-07-09
Sunnyvale, CA
clubs: 
| A line attenuation of 55dB is on the high side and either indicates a long distance from the CO (which you can't do anything about, except moving) or a line problem. If the attenuation is noticeably lower when the modem is plugged directly into your NID test port than you need to fix your inside wiring.
Your down noise margin of 17dB is great, but the up noise margin of only 9dB is rather low (still ok, but not good).
The strange thing is that it is normally the other way around with the down noise margin being lower. This could be an indication that there is an RF disturbance effecting the upstream frequencies. Those are difficult to diagnose and depending on whether the disturbance is within your own home or somewhere along the line may not be fixable either.
You are already on an interleave profile which provides more reliability (at the expense of increased latency) and the fact that there are CRC errors justifies this (you would only want to be on fast-path if your line is completely error-free).
The error second counter should give the number of seconds that the connection was down because of errors (that could mean one downtime of 176 seconds or 176 times down for 1 second, but most likely something in between). An error log might hint at the cause, but often doesn't help much to pinpoint the exact source.
Using a ping plotter (or the DSLR/BBR line monitoring service) may help in determining whether there is a specific pattern (certain times of day) to the disturbances.
--
Got some spare cpu cycles ? Join Team Helix or Team Starfire! |
|
jeffb666
join:2005-02-15
La Grange Park, IL
| I also have an SBC Line as well..
Let me try and remember how to get the same information from it to try and compaire since the CO would be the same distance.
As far as a ping plotter (or the DSLR/BBR line monitoring service) do you have a recommendation?
Oh and also..
Thanks for helping me with this..
Jeff |
|
