how-to block ads
|
mooosenix
join:2004-01-09
Milwaukee, WI
1 edit | Re: [TWC] Throttling in Milwaukee? said by funchords  :said by alexfalkenberg :
I'm tired of the BS of my cable modem constantly rebooting... I responded on his blog with the following...Alex, Your modem is rebooting. That nearly eliminates purposeful ISP throttling as a cause as many DOCSIS modems cannot be rebooted from the headend. This is why most ISPs tell you to reboot your router when a network upgrade happens so that it can phone home and download and apply its new config file. Mine is not rebooting.
The modem "config" page is still accessable, and all the lights are still on with the activity light happily blinking away. However, any outbound traffic will fail to
reach its destination.
In addition, there are no new logs on the modem config page after this happens. If the modem would have rebooted, it would have some logs about the startup process, right?
Sometimes the connection will restore itself after ~30 seconds or so by itself without a reboot. However, most of the time I have to manually restart the modem.
Just for kicks, I'll probably have my modem swapped out in hope that's the problem, but I doubt it. | |
|  
MacLeech
The one and only
Premium
join:2001-07-14
SoCal
3 edits | Re: [TWC] Throttling in Milwaukee? said by mooosenix :The modem "config" page is still accessable, and all the lights are still on with the activity light happily blinking away. However, any outbound traffic will fail to reach its destination. How are the modem signal levels during all of this?
Are they stable or does the SNR or Tx level fluctuate more than 1-2 dB?
Is there packet loss during this time?
Can you ping your gateway IP during these times?
Can you ping 192.168.100.1 during these times?
Can you ping 127.0.0.1 during these times?
.
It sounds like a return signal issue from the symptoms listed so far, possibly caused by noise, CPD, transient hum modulation, or return signal reflections... none of which phone support or the techs field techs assigned to service calls can see very well, if at all. Maintenance/line techs can see some or all of it depending on the training and/or tools they have access to. The return issues can cause intermittent upstream interruptions without causing the modem to reset. | |
| | 
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC | Re: [TWC] Throttling in Milwaukee? What is CPD? | |
| | |
MacLeech
The one and only
Premium
join:2001-07-14
SoCal
4 edits | Re: [TWC] Throttling in Milwaukee? said by funchords :What is CPD? CPD = common path distortion. It's caused when forward signals are "reflected" back onto the return path. It's more common on the coax distribution system where the forward signals are high (20 dBmV or higher) and the return attenuation is low.
It causes the return noise floor to jump up quite a bit (some times more than 20 dB). It kills the upstream SNR and causes "codeword" errors on the upstream. It usually affects every modem on the upstream CMTS port, but can be VERY intermittent and difficult to track down because it often disappears for hours or days due to being disturbed during the troubleshooting process.
If CPD is strong enough, it'll knock modems offline, if it's not it could just slow things down and cause "hiccups" occasionally because of the upstream errors.
It has a lot of possible causes: corrosion of distribution equipment, loose connectors, bad termination, faulty amplifiers, kinked cable, customer wiring issues, etc.... I've seen alot of it first hand.
This may interest you:
»cable.doit.wisc.edu/cpd/cpd2.v2.html
[edit]Posted better link. | |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
 ·Verizon Online DSL
 ·Skype
| said by mooosenix :Mine is not rebooting. The modem "config" page is still accessable, and all the lights are still on with the activity light happily blinking away.... ...no new logs on the modem config page Agreed, your modem is not rebooting.
said by mooosenix :Sometimes the connection will restore itself after ~30 seconds or so by itself without a reboot. The next time this happens, do not manually restart the modem. Instead, check your system logs or router's logs for a message indicating some kind of a DHCP event. (Restarting the modem would force such an event, which is why I'd like you to avoid it.)
said by mooosenix :Just for kicks, I'll probably have my modem swapped out in hope that's the problem, but I doubt it. Despite the lack of log entries, the modem is still in play as a possible cause for your issue. I would think that if a modem was requiring a signal, that too would be logged. Swapping it would be a quick way to rule in or rule out a major player in making a successful connection.
My gut tells me it's your computer or your router, and not your modem and not ISP throttling.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
"We don't throttle any traffic," -Charlie Douglas, Comcast spokesman, on this report. | |
| | | |
|
