dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
15
share rss forum feed

catnapped

join:2010-11-22
Elizabethtown, PA
reply to Mike Wolf

Re: [Connectivity] New SB6120/6121 Firmware Released

It is something of concern that there's a T4 that stays on top of the log and keeps changing its time on a refresh of the log page? Seems to update the time mark every 30 seconds. Don't remember if I was seeing that before 1.0.6.6 showed up.


koitsu
Premium,MVM
join:2002-07-16
Mountain View, CA
kudos:23
said by catnapped:

It is something of concern that there's a T4 that stays on top of the log and keeps changing its time on a refresh of the log page? Seems to update the time mark every 30 seconds. Don't remember if I was seeing that before 1.0.6.6 showed up.

Repeated issues of the exact same type/error simply update the timestamp of the top row log entry, rather than continually prepend additional rows.

What you describe indicates continual T4 timeouts, not occasional. Occasional T4 timeouts are acceptable. Constant, non-stop T4s are not. What you describe is indicative of a different problem and is not firmware related. Please start another thread or engage folks in the Comcast Direct forum for assistance; something at the head-end needs to be investigated.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.

andyross
Premium,MVM
join:2003-05-04
Schaumburg, IL
reply to catnapped
said by catnapped:

It is something of concern that there's a T4 that stays on top of the log and keeps changing its time on a refresh of the log page? Seems to update the time mark every 30 seconds. Don't remember if I was seeing that before 1.0.6.6 showed up.

If you look at your signals, one of your upstream channels is probably listed as 'T4 Timeout'. That means it cannot connect on that one. Sometimes, rebooting will get it to connect. If you signals are marginal, it may occur again.


tshirt
Premium
join:2004-07-11
Snohomish, WA
kudos:5
reply to catnapped
T4's are often associated with upstream noise, so you could call in and ask what your upstream SNR is like.

andyross
Premium,MVM
join:2003-05-04
Schaumburg, IL
One of the interesting things is that, when people have posted issues on 3-channel upstream bonding with a T4'd channel, it's always the middle channel, even if it's not the middle frequency.


koitsu
Premium,MVM
join:2002-07-16
Mountain View, CA
kudos:23
said by andyross:

One of the interesting things is that, when people have posted issues on 3-channel upstream bonding with a T4'd channel, it's always the middle channel, even if it's not the middle frequency.

I cannot confirm this. Proof from my cable modem polling script logs, with firmware 1.0.6.6, are below.

Apologies for the syntax changes in the log too (I removed the modulation type sometime in late August to make things easier to read):

Sep 09 08:56:00   Up Channel  9:  23700000 Hz,  51 dBmV power, 5.120 Msym/sec, status: T4 TimeOut
Sep 09 08:58:00   Up Channel  9:  23700000 Hz,  51 dBmV power, 5.120 Msym/sec, status: T4 TimeOut
Aug 22 12:20:01   Up Channel  8:  30600000 Hz,  50 dBmV power, 5.120 Msym/sec, status: T4 TimeOut
Aug 22 12:20:01   Up Channel  9:  23700000 Hz,  50 dBmV power, 5.120 Msym/sec, status: T4 TimeOut
Aug 21 04:35:00   Up Channel  7:  35400000 Hz,  50 dBmV power, 2.560 Msym/sec, status: T4 TimeOut
Aug 21 04:35:00   Up Channel  9:  23700000 Hz,  49 dBmV power, 5.120 Msym/sec, status: T4 TimeOut
Aug 17 13:30:00    Up Channel  9:  23700000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM, status: T4 TimeOut
Aug 17 13:50:00    Up Channel  9:  23700000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM, status: T4 TimeOut
 

Let's pick August 17th as a test subject:

Aug 17 13:30:00        Firmware: SB_KOMODO-1.0.6.6-SCM00-NOSH (Apr 17 2012 15:09:37)
Aug 17 13:30:00    Boot Version: PSPU-Boot(25CLK) 1.0.12.
Aug 17 13:30:00     H/W Version: 5.0
Aug 17 13:30:00    Modem Uptime: 0 days 0h:2m:57s
Aug 17 13:30:00  Down Channel  3: 723000000 Hz,   1 dBmV power, 37 dB SNR, mods: QAM256
Aug 17 13:30:00  Down Channel  5: 735000000 Hz,   2 dBmV power, 36 dB SNR, mods: QAM256
Aug 17 13:30:00  Down Channel  7: 747000000 Hz,   1 dBmV power, 35 dB SNR, mods: QAM256
Aug 17 13:30:00  Down Channel  8: 753000000 Hz,   1 dBmV power, 35 dB SNR, mods: QAM256
Aug 17 13:30:00    Up Channel  8:  30600000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM, status: Success
Aug 17 13:30:00    Up Channel  7:  35400000 Hz,  48 dBmV power, 2.560 Msym/sec, mods: [3] QPSK [2] 16QAM, status: Success
Aug 17 13:30:00    Up Channel  9:  23700000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM, status: T4 TimeOut
Aug 17 13:30:00 Stats Channel  3: 5604427 unerrored, 44 correctable, 607 uncorrectable
Aug 17 13:30:00 Stats Channel  5: 5604430 unerrored, 11 correctable, 637 uncorrectable
Aug 17 13:30:00 Stats Channel  7: 5604344 unerrored, 13 correctable, 727 uncorrectable
Aug 17 13:30:00 Stats Channel  8: 5604424 unerrored, 21 correctable, 639 uncorrectable
 

The order you see these channels in is the order they're shown in the actual "Signal" web page interface (from left to right).

--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.

catnapped

join:2010-11-22
Elizabethtown, PA
reply to andyross
said by andyross:

If you look at your signals, one of your upstream channels is probably listed as 'T4 Timeout'. That means it cannot connect on that one. Sometimes, rebooting will get it to connect. If you signals are marginal, it may occur again.

Yep...middle channel/middle (upload) frequency that had the T4. Rebooted and got rid of it, but we'll see how long it lasts....