Comcast XFINITY → Re: SB6120 Firmware Updated (7/19/12)

Just picked this up on my SB6121 in Mountain View, CA today after I did a Reset Factory Defaults + Reboot Modem.

From my own parser / logs:

Jul 29 16:50:00        Firmware: SB612X-1.0.3.3-SCM00-NOSH (Aug 12 2010 13:58:19)
Jul 29 16:50:00    Boot Version: PSPU-Boot(25CLK) 1.0.12.
Jul 29 16:50:00    Modem Uptime: 31 days 16h:20m:43s
Jul 29 16:50:00  Down Channel  2: 717000000 Hz,   0 dBmV power, 37 dB SNR, mods: QAM256
Jul 29 16:50:00  Down Channel  3: 723000000 Hz,   0 dBmV power, 37 dB SNR, mods: QAM256
Jul 29 16:50:00  Down Channel  6: 741000000 Hz,   0 dBmV power, 37 dB SNR, mods: QAM256
Jul 29 16:50:00  Down Channel  7: 747000000 Hz,   0 dBmV power, 36 dB SNR, mods: QAM256
Jul 29 16:50:00    Up Channel  9:  23700000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM
Jul 29 16:50:00    Up Channel  7:  35400000 Hz,  48 dBmV power, 2.560 Msym/sec, mods: [3] QPSK [2] 16QAM
Jul 29 16:50:00    Up Channel  8:  30600000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM
Jul 29 16:50:00 Stats Channel  2: 124394696875 unerrored, 52046 correctable, 625 uncorrectable
Jul 29 16:50:00 Stats Channel  3: 124394697536 unerrored, 51145 correctable, 576 uncorrectable
Jul 29 16:50:00 Stats Channel  6: 124394715110 unerrored, 34111 correctable, 492 uncorrectable
Jul 29 16:50:00 Stats Channel  7: 124394719971 unerrored, 28888 correctable, 531 uncorrectable
Jul 29 16:50:00 --
Jul 29 17:00:00        Firmware: SB_KOMODO-1.0.6.6-SCM00-NOSH (Apr 17 2012 15:09:37)
Jul 29 17:00:00    Boot Version: PSPU-Boot(25CLK) 1.0.12.
Jul 29 17:00:00    Modem Uptime: 0 days 0h:3m:39s
Jul 29 17:00:00  Down Channel  5: 735000000 Hz,   0 dBmV power, 36 dB SNR, mods: QAM256
Jul 29 17:00:00  Down Channel  6: 741000000 Hz,   0 dBmV power, 36 dB SNR, mods: QAM256
Jul 29 17:00:00  Down Channel  7: 747000000 Hz,   0 dBmV power, 36 dB SNR, mods: QAM256
Jul 29 17:00:00  Down Channel  8: 753000000 Hz,   0 dBmV power, 35 dB SNR, mods: QAM256
Jul 29 17:00:00    Up Channel  9:  23700000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM
Jul 29 17:00:00    Up Channel  7:  35400000 Hz,  48 dBmV power, 2.560 Msym/sec, mods: [3] QPSK [2] 16QAM
Jul 29 17:00:00    Up Channel  8:  30600000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM
Jul 29 17:00:00 Stats Channel  5: 8320448 unerrored, 24 correctable, 706 uncorrectable
Jul 29 17:00:00 Stats Channel  6: 8320546 unerrored, 20 correctable, 612 uncorrectable
Jul 29 17:00:00 Stats Channel  7: 8320541 unerrored, 26 correctable, 612 uncorrectable
Jul 29 17:00:00 Stats Channel  8: 8320547 unerrored, 61 correctable, 572 uncorrectable
Jul 29 17:00:00 --
 

Amusingly this firmware still has the bug where after certain reboots/resets, despite being fully 100% online and functional, the Status page still shows:

Cable Modem Status     Offline
 

Another factory reset + reboot will fix that.

Two things I've noticed about the firmware change:

1. The Signal page now has Ranging Status information per-channel on the Upstream channels (my log above doesn't show that; I need to add the proper code to my script). But for example:

Channel ID         9         7         8 
Ranging Status     Success   Success   T4 TimeOut 
 

2. EDIT: Seems the "IPv6 Only" thing I was reporting was just a fluke as a result of the upgrade. It went away (went to "IPv4 Only" which is what I'm used to seeing) once I did a second factory reset + reboot. Wouldn't be the first time I've seen this. Sorry for the noise.

3. There's an "Open Source" menu now listing off all the stuff used to build the firmware.

After a 2nd factory reset + reboot, and me updating my script that pulls stats for my logs, looks good:

Jul 29 17:21:07        Firmware: SB_KOMODO-1.0.6.6-SCM00-NOSH (Apr 17 2012 15:09:37)
Jul 29 17:21:07    Boot Version: PSPU-Boot(25CLK) 1.0.12.
Jul 29 17:21:07    Modem Uptime: 0 days 0h:3m:19s
Jul 29 17:21:07  Down Channel  1: 705000000 Hz,   0 dBmV power, 37 dB SNR, mods: QAM256
Jul 29 17:21:07  Down Channel  2: 717000000 Hz,   0 dBmV power, 36 dB SNR, mods: QAM256
Jul 29 17:21:07  Down Channel  5: 735000000 Hz,   0 dBmV power, 37 dB SNR, mods: QAM256
Jul 29 17:21:07  Down Channel  8: 753000000 Hz,  -1 dBmV power, 36 dB SNR, mods: QAM256
Jul 29 17:21:07    Up Channel  9:  23700000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM, status: Success
Jul 29 17:21:07    Up Channel  7:  35400000 Hz,  48 dBmV power, 2.560 Msym/sec, mods: [3] QPSK [2] 16QAM, status: Success
Jul 29 17:21:07    Up Channel  8:  30600000 Hz,  47 dBmV power, 5.120 Msym/sec, mods: [3] QPSK [3] 64QAM, status: Success
Jul 29 17:21:07 Stats Channel  1: 8510103 unerrored, 14 correctable, 639 uncorrectable
Jul 29 17:21:07 Stats Channel  2: 7878473 unerrored, 4 correctable, 511 uncorrectable
Jul 29 17:21:07 Stats Channel  5: 7878564 unerrored, 1 correctable, 567 uncorrectable
Jul 29 17:21:07 Stats Channel  8: 7878742 unerrored, 1 correctable, 546 uncorrectable
Jul 29 17:21:07 --
 

I had a T4 reboot Sunday around noon. Upon starting, it logged this new error:
Jul 29 2012 11:09:32 5-Warning U103.0 Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired

I had that 'offline' message. I just did a plain reboot, and it connected back normally.

I wish I knew what was going on. Just had another T4 timeout...

So did I...so I rebooted. Everything came back as normal...then five minutes later, back to "not started"/"offline" again on the status page. Also T4 showing up on upstream channel 11 and downstream SnR has been trending around the 35 range for the past week or so (it's usually higher).

Yeah I did notice that whole "offline" thing even though I was still browsing the web just fine. I rebooted for the hack of it and it went back to "operational" status, so I thought nothing of it.