dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
12

djrobx
Premium Member
join:2000-05-31
Reno, NV

djrobx to mpgstuff

Premium Member

to mpgstuff

Re: [TWC] Cable Modem Resets

it seems to happen the most between the hours of 2-9PM, but that's also more likely the time a user would be on and notice something so I wouldn't suggest its time bound.

Channel change requests happen because the CMTS is trying to balance the load. This activity is most likely to happen during peak hours.

If not fixed, the problems will likely stop once TWC figures out how to get the upstreams bonded, removing the need for channel changes on bonded modems.
mpgstuff
join:2003-07-07
Kenosha, WI

mpgstuff

Member

Thanks for the response. I will see what the technician says tomorrow. I'm not sure what he/she will want to look at inside the house (or outside for that matter). Inside, nothing has changed in the 10 years we've had the service. I looked at the coax and splitters and everything is tight and "appears" fine inside.
I can show them the cable modem logs and the new cable modem, the is about it for inside.

As a side note, I noticed in the SB6141 logs that my most recent entry (a few posts up) was timestamped Dec 22 2012 06:47:48. Now when I look at it, it is the same error message (T3 Time-out) but the time-stamp is Dec 22 2012 10:18:52 and the 06:47:48 entry is no longer there. Does the SB6141 do some sort of in-place log replacement/consolidation?

motorola870
join:2008-12-07
Arlington, TX

1 edit

motorola870 to djrobx

Member

to djrobx
not necessarily going to stop load balancing I had my modem reset the other night and it took the primary downstream for 783MHz to 807MHz which is channel 5 all while still bonding 6 downstreams and 4 upstreams!

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File
Security Enabled BPI+

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 5 807000000 Hz -5.9 dBmV 35.4 dB 1857 0
2 Locked QAM256 1 783000000 Hz -4.3 dBmV 37.2 dB 145 0
3 Locked QAM256 2 789000000 Hz -4.5 dBmV 37.0 dB 200 0
4 Locked QAM256 3 795000000 Hz -5.1 dBmV 36.1 dB 522 0
5 Locked QAM256 4 801000000 Hz -5.1 dBmV 36.2 dB 705 0
6 Locked QAM256 6 813000000 Hz -5.5 dBmV 36.2 dB 1011 29
7 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
8 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked TDMA and ATDMA 10 2560 Ksym/sec 33000000 Hz 42.0 dBmV
2 Locked TDMA and ATDMA 9 2560 Ksym/sec 36500000 Hz 42.0 dBmV
3 Locked TDMA and ATDMA 11 2560 Ksym/sec 29500000 Hz 42.0 dBmV
4 Locked TDMA and ATDMA 12 2560 Ksym/sec 24500000 Hz 42.0 dBmV

I would think that the correctables should be expected in my area as TWC is using the same bands as wireless providers do so there could be a small amount of noise getting in from the node to my house I believe this set up is better than having my downstreams in the 99MHz to 123MHz like some areas do in Ohio on TWC.

I am actually surprised that have 4 upstreams with QAM64 as when QAM64 first rolled out at the beginning of 2011 in my area I was struggling to keep QAM64 on two of the 4 upstreams and sometimes 3 of them as my modem would keep alternating. Right now these basically are equivalent to two QAM64 6.4MHz wide channels on the downstream I have a feeling that we will have them respaced in early 2013 to maximize the upstream capacity and two of them will go 3.2MHz wide QAM16 and the other two will go 6.4MHz wide QAM64.