Basic Internet Connectivity And Modem Help

[dryachovsky]

The modem worked fine until this morning. Now it constantly reboots.

The signal data:

Downstream Bonding Channel Value Channel ID 226  Frequency 699000000 Hz  Signal to Noise Ratio 38 dB  Downstream Modulation QAM256  Power Level The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading 7 dBmV  Upstream Bonding Channel Value Channel ID 3  Frequency 30400000 Hz  Ranging Service ID n/a  Symbol Rate 5.120 Msym/sec  Power Level 57 dBmV  Upstream Modulation [3] QPSK
[3] 64QAM
  Ranging Status Continue Signal Stats (Codewords) Bonding Channel Value Channel ID 226  Total Unerrored Codewords 1119146  Total Correctable Codewords 0  Total Uncorrectable Codewords 660 

The log says:

Time Priority Code Message Jan 01 1970 00:31:46 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:31:35 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:31:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:31:04 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:30:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:30:20 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:29:57 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:29:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:29:24 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:59 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:39 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:21 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:01 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:45 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:24 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:01 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:39 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:27 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:00 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:25:37 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:77:31:fb;CMTS-MAC=00:14:f1:e8:86:c6;CM-QOS=1.1;CM-VER=3.0; 

The signal strength seems to be high. I rent the appartment - is there a way for me to fix that without re-wiring the building?  

[EG]

This is typical in multiple dwellings. Perhaps you should book a tech ?

[dryachovsky]

Will do. Thanks.

[andyross]

A bit messy post, but it looks like your downstream is +7, but your upstream is 57? That almost seems as if there is an RF amp in-line, but it's not broadband compatible and is restricting the upstream signal.

As mentioned, have Comcast come out and see if they can check it. You wouldn't remember what your signals were before this recent problem?

[dryachovsky]

It used to be ~0 dBmV downstream and ~40 dBmV upstream

[andyross]

That STRONGLY suggests an RF amp has been added that is not broadband compatible. Broadband compatible means it splits the signals by frequency and will allow the lower frequencies that are used for upstream to go around the amp. A non-compatible amp means it has to fight to go backwards through the amp circuitry.

Not knowing how your location is wired, somebody may have complained about a weak signal is 'stealing' yours and bought and installed a cheap amp.

As mentioned, get Comcast out to take a look. Going from 0/40 to 7/57 is a giant clue. A bad ground can sometimes affect the low frequencies used for upstream, but wouldn't make your downstream stronger!

[jdchurchill]

my sb6121 is also constantly rebooting.  when i called comcast to get the hardware added, the tech took my mac id, and as we were on the phone the thing just kept running through the same cycle: receive light blinks then goes solid green, send light blinks then goes solid green, online light blinks then goes solid green, then receive and send blink green for perhaps a minute or two then solid blue and it shuts off. this happened perhaps 5-10 times while i was on the phone and the tech suggested the modem didn't work.  but at some point my phone cut out and i lost the tech.

after reading up on some of the forums i have tried connecting directly to the cable that comes into my apt to no avail.  i have tried hitting the "restore default settings" button in the configuration dialog at 192.168.100.1  i have tried run>cmd>ipconfig/release  ipconfig/renew.  none of these things have done the trick.  downstream power levels i have seen -7 to 0dBmV, upstream power levels 36-44dBmV.  i keep getting this in the log:   

Jun 09 2012 13:17:36 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb6121_silver_c01.cm

Jun 09 2012 13:17:29 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from shell 

i would appreciate any suggestions anyone could give me.

[jdchurchill]

also why does it always default to new years day 1970?

[EG]

---

jdchurchill wrote:

also why does it always default to new years day 1970?

---

That's what modem's display for the time when for whatever the reason they can not talk to the T.O.D. (time of day) server to retrive the correct time. This is typically caused by RF signal / connection quality issues.

[andyross]

It's the 'day 0' time for the operating system it runs. The modem does not have it's own clock chip, so it sets it's internal clock by accessing a time server once a connection is established. I don't think it updates after that, as my 6120 tends to run a bit slow and loses about 1 sec/day.

[jdchurchill]

ok so we got the time thing sussed; does anyone have any advice to give me about how to get the modem to work?

[andyross]

It seems as if it cannot complete the software configuration download? Maybe it's not properly configured by Comcast and it's trying to pull the wrong file. Call have make certain they have the correct modem model listed. The 6121 may require a different file than the 6120.

[jdchurchill]

perhaps i didn't paste in enough of the log data.  here is another copy&paste from data i have

Jun 09 2012 13:05:37 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb6121_silver_c01.cm Jun 09 2012 13:05:31 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot from shell ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jun 09 2012 13:04:30 6-Notice E112.0 SW download Successful - Via Config file

i guess what perplexes me is that it states 'download successful' but perhaps you are correct that it's the wrong thing.

[andyross]

Remember that the log is in reverse order. It says successful at 13:04. Then as you work up, it loads the config file (which is the correct 6121), then says SW Download INIT, then ends.

[EG]

Are there more entries ? The 13:05 entry actually shows that the software / firmware download is being reinitiated via the config file after the device re-boots. The config file always comes first, then a software loading gets performed via the config file.

[jdchurchill]

yes there are more entries, so here is all the data i collected the other day:

Jun 09 2012 13:17:36 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb6121_silver_c01.cm

Jun 09 2012 13:17:29 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from shell ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jun 09 2012 13:16:29 6-Notice E112.0 SW download Successful - Via Config file

Jun 09 2012 13:14:36 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb6121_silver_c01.cm

Jun 09 2012 13:14:29 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from shell ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jun 09 2012 13:13:28 6-Notice E112.0 SW download Successful - Via Config file

Jun 09 2012 13:11:36 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb6121_silver_c01.cm

Jun 09 2012 13:11:29 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from shell ;CM-MAC=MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jun 09 2012 13:10:29 6-Notice E112.0 SW download Successful - Via Config file

Jun 09 2012 13:08:37 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb6121_silver_c01.cm

Jun 09 2012 13:08:29 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from shell ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jun 09 2012 13:07:29 6-Notice E112.0 SW download Successful - Via Config file

Jun 09 2012 13:05:37 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb6121_silver_c01.cm

Jun 09 2012 13:05:31 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot from shell ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Jun 09 2012 13:04:30 6-Notice E112.0 SW download Successful - Via Config file

it appears to me that it turns on, records a warning mimo event, downloads the config file and reboots.  i do not understand why after it successfully downloads the config file it then reboots.  this don't make sense to me

[jdchurchill]

bumping this thread

just looking for some replies

thx dudes