Basic Internet Connectivity And Modem Help

[EG]

The coding is not likely to be "the same".

[donf99]

My error. The old 3.3.1 that Comcast pushed, then rolled back was SBG6580-3.3.1.0-GA-09-058-NOSH.

The version most recently pushed is SBG6580-3.3.1.0-GA-11-070-NOSH.

My settings seem to have survived the update intact. I did notice my primary wireless SSID shows as "admin"' although it is shown correctly at the top of the Wireless configuration page. Odd.

The VPN tab is gone when logging in as admin. However, when logging in as root/motorola, the VPN option is there, with some options missing from the old firmware.

[dbottoms]

I was upgraded to   SBG6580-3.3.1.0-GA-11-070-NOSH   on Wednesday April 11 at 15:36pm 2012 EST.  I've been up and stable for approaching 46 hours straight.  I averaged one reboot approximately every 6-8 hours previously.  Speedtest showing I'm getting the tier I'm paying for also.  Its great so far !  Thank you Motorola and Comcast.

[jstorm001]

Well i never had a problem with my SBG6580 gateway modem but once it awhile i'll reboot it . Last night i rebooted it  & it updated to firmware SBG6580-3.3.1.0-GA-11-070-NOSH didnt get to check it out much settings look the same i guess just fixes bugs had SBG6580-3.1.0.0-GA-07-180-NOSH befor it updated.

[Blultn]

Quick reply after being a reader with the same problem.  Comcast reverted software version to SBG6580-3.1.0.0-GA-07-180-NOSH and all worked normalluy again until two days ago where they pushed SBG6580-3.3.1.0-GA-11-070-NOSH. Declined tech visit option and choose to reset the device to factory setting. Once online, Comcast Blast speeds are back as before. Very surprise.

[reacheks]

Got 3.3 upgrade but received "Critial Error" that required a reset by me.

This was the error message in my Log report:

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out

The system appears to be doing a maintenance request to my modem but my modem is not responding.  I wonder if it is because it is a customer owned modem and the MAC No. may not be registered in the broadcast maintenance database?

Any ideas?  Are any of the other custmer owned modems experiencing the same problem?

To check, you must go to the event log and check the log reports.  I noticed that during the period of the broadcast maintenance check, my computer response bogged down and my VOIP line was intermitent.  Once I did the reset, everything seems to be functiong fine.

EKS

[i-am-nerdburg]

A T4 error just means the modem lost connection for 30 seconds or so and reset the connection. The modem doesn't care who owns it.

[EG]

Yep. Those are RF (Radio Frequency) system based handshake errors.

[reacheks]

So what do you make of these "critical errors"in my log report?

Sun Apr 15 14:13:17 2012    Notice (6)   T4 No Station Maint Timeout - Reinitialize MAC...   Sun Apr 15 14:13:17 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.0;CM-VER=3.0;   Sun Apr 15 14:11:59 2012    Notice (6)   T4 No Station Maint Timeout - Reinitialize MAC...   Sun Apr 15 14:11:59 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.1;CM-VER=3.0;   Sun Apr 15 14:11:07 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.1;CM-VER=3.0;   Sun Apr 15 14:10:54 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.1;CM-VER=3.0;   Sun Apr 15 13:49:47 2012    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.1;CM-VER=3.0;   Sun Apr 15 13:49:47 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.1;CM-VER=3.0;   Sun Apr 15 13:49:22 2012    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=00:25:f2:e6:66:31;CMTS-MAC=00:01:5c:33:74:18;CM-QOS=1.1;CM-VER=3.0;   Time Not Established   Warning (5)   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.0;CM-VER=3.0;   Sun Apr 15 13:48:07 2012    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.0;CM-VER=3.0;   Sun Apr 15 13:47:57 2012    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.0;CM-VER=3.0;   Sun Apr 15 13:47:56 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.0;CM-VER=3.0;   Sun Apr 15 13:46:40 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.0;CM-VER=3.0;   Sun Apr 15 13:45:23 2012    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.1;CM-VER=3.0;   Sun Apr 15 13:44:27 2012    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.1;CM-VER=3.0;   Sun Apr 15 13:06:31 2012    Critical (3)   UCD invalid or channel unusable;CM-MAC=00:25:f2:e6:66:31;CMTS-MAC=XXXX;CM-QOS=1.1;CM-VER=3.0;   Sun Apr 15 12:22:46 2012    Critical (3)   No UCDs Received - Timeout;;CM-MAC=XXXX;CMTS-MAC=XXXX;CM-QOS=1.1;CM-VER=3.0;  ---------------------------------------------------------------------------- The modem has worked good since the upgrade.  I have however noticed some noise in the down stream channels 4 & 5.  When I do a reset, they usually go away.  The SNR & power levels are w/i spec.  It could be a problem w/ DOSIS 3.0 at the substation as my legacy Motorola Surfboard modem w/ router has worked flawlessly.  Is there any chance I might have one or more of the settings wrong?  I am pretty sure that everything is set on the default EXCEPT SIP ALG Enable has been disabled (for my VOIP SipuraSPA box and my DMZ address is set to the IP address for the VOIP device. Other than that, I have enabled the Primary Wireless Network.  Any suggestions are welcomed. EKS P.S. - It could be weather related as we have just ended three days of very cold and rainy storms in our area (No. CA.).  Maybe once things dry out, that RF noise will go away and/or significantly reduce.  I do know that the cable to the street is solid but who knows what it is like under ground to the street box .    T

[i-am-nerdburg]

That's a lot fo errors for a single day. How are your signal levels? http://192.168.100.1

[reacheks]

/duplicate

[Slee_Stack]

Keep deleting my msgs, ill keep posting.

3.3.1 is junk and has made my modem unusable.  constant dropouts.  Fast than nothing.  Can't stream anything for any period of time.

Channels 5 & 6 are low SNR and lots of 'uncorrectables' on 6.

3.1 at least 'worked'.  I could watch a stream.  Now I have to constantly ///oh there it goes again...0...

Gotta love it.

[reacheks]

Yes channel 4 & 5 (especially 5) had some noise level.  I did a reset and all is well. Channel 4 shows zero  0 "correctable" & 0 "non correctible" while channel 5 shows 436  "correctabile" & 0 "non-correctible".

This is way down from the hick-up shown in my log report for Sunday on 13:44 - 14:13 where BOTH Channel 4 & Channel 5 showed over 20K correctibles!  Yes 20,000 corectables (but power dBnV and SNR dB levels were w/i specifications?).

I wonder if somebody at the sub-station hit the cable connection (...he he he).  I really do not think it is a modem issue but rather something happening downstream perhaps with a router interuption, backup signal switch or some other one time back end anomaly.  So far it is a one time event.

I am located in San Jose California.  I suspect this is a one time event but will stayed tuned to see if anything spreads in the syatem.  I will post any other "critical" errors that my log event might record.  Hopefully it is just a recent weather phenomenon as I know that water in the lines can cause such a noise issue,.

I still am puzzeled as to why it is always isolated to channels 4 & 5 (especially channel 5)?

EKS

[glacial]

I have been upgraded to SBG6580-3.3.1.0-GA-11-070-NOSH for 6 days now, and not one single connectivity issue so far. Nothing new recorded in the log since the upgrade. With old firmware, there was at least one connection reset per day (and often more). Also, the log was constantly filled with errors.

This is great, because I was really annoyed at the prospect of having to pay for new hardware.

[nhbragg]

Still waiting on 3.3 here in northern Virginia. Done 2 full resets, one via web gui and the other by using the reset button on the back.  Still running 3.1.

[MidnightCat]

I didn't need to reset my gateway to get the update, so when they roll it out to you, you'll get it then.

To do an updated report, no disconnections yet here, it's very weird that other people are still disconnecting though.

[Slee_Stack]

Had a comcast tech out to visit.

Found rusty connections outside and replaced them.

Channel SNRs have come back up from ~24 to ~34 on 5 & 6.  Still have 300K+ uncorrectables on Channel 6.

Performance is much better, not dropping to zero anymore.

I don't understand how a bad connector would affect only 2 of the 8 downstream channels though.

[reacheks]

Hi Slee-

I found out from a very knowledgable "local" Comcast Service tech that (1) the numbers labled uncorrectables in the SBG6580 log report deal w/ the cable TV side only and are not related to the internet connection. and (2) weather: rain, cold/heat will change your SNR readingS significantly.  In my area (No. CA) we had three days of severe weather that caused new service calls to their Comcast service center 5:1.

I believe the sbg6580 has a very "tight" SNR setting threshold that if exceeded will lose it's handshack connection from the cable service to your modem.  Maybe the firmware update loosened this threshold (to account for weather changes) but still will create a critical log error most times when some of the other legacy equipment (ie motoroloa 5100) will not.

In my case, I may have a marginal cable in the house (30 year old house with original coax cable) and/or street cable ( a flacky under ground cable when wet causes SNR noice) issue.  

It's funny that my SBG6580 recently has had critcal SNR log readings that are time related.  Around 1:00PM I tend to get a lot of drops which end around 3:00PM.  This has occurred the last three days when I was monitoring the line.

I installed my legacy modem (Motorola 5100) w/ DLINK router and the connection is rock solid.  I will use my SBG6580 modem at another propertyI i own serviced by Charter Communications.  I will report any issues that occur but I do not anticipate any (my cable SNR levels s/d be better at this property).

My conclusion is that if your SNR levels are at marginal levels (anytime below 30 d go with one of the modem only harware (legacy) devices and/or get a tech out to check or replace your coax connectors. Old cable may also cause intermittent disconnects and are easy to replace too. The Motorola 5100 (for me) is a rock solid cable modem that works quite well with my old coax cable lines and sometime weather/wet connectors.

The SBG6580 is a very good integrated device but for it to work best it must be hooked into very clean lines with SNR levels well w/i spec.   Newer homes and/or recently wired homes this modem should work fine with the latest firmware upgrade.  I

EKS

[Slee_Stack]

Thx for the info.  My SNR levels just dumped again today on Channels 5 & 6.  Down to 23.  Modem faulted and reset several times, so back to square one.  I think I'm ready to give up on the 6580.  It obviously doesn't work well with ComCast.

[chadsittner]

Sorry to hear some of you are having trouble. When they pushed the 3.3 for the second time I got it about 2 weeks ago. Have had no issues at all since then and the speeds are fantastic.

[rocke86]

Any news on when this will get rolled out to everyone(I'm in the central IL region)?  I'm stuck on SBG6580-3.1.0.0-GA-07-180-NOSH and have been having disconnects for months.  I'm tempted to get a new router but I dropped $150 on this router a year and with my luck as soon as I get a new router the update will be released.  

[i-am-nerdburg]

---

rocke86 wrote:

Any news on when this will get rolled out to everyone(I'm in the central IL region)?  I'm stuck on SBG6580-3.1.0.0-GA-07-180-NOSH and have been having disconnects for months.  I'm tempted to get a new router but I dropped $150 on this router a year and with my luck as soon as I get a new router the update will be released.  

---

I hate to sound like a Comcast rep...but try just unplugging the modem for a few minutes if you haven't already. When the modem reconnects to the Comcast system, it will download the most recent firmware available. Sometimes the modems don't update on their own.

We don't have any official info from Comcast about when or where updates have been deployed.

[mcclenj1]

I've had 3.3 for at least a week now, and I'm still losing internet connection. Really disappointed in Motorola and Comcast over this. Maybe I can get something for my sbg6580 on ebay.

[shlama]

ironicially it seems like my dropping issues started roughly a week ago, maybe as a result of the new firmware. any suggestions? 

[reacheks]

Try a complete power down of the modem and wait at least 3 minutes.  Also check and tighten the coax connector on the modem and/or any other coax connectors you may have on the lines into the house.  Make sure the modem is well ventilated too.

If you have had recent weather issues  your SNR readings may rise which could result  in a handshake "lost connection" event.  In my case, my SNR and dB levels were on the fringe of being in spec.  I got too many lost connections with the SBG6580 during inclimate weather.

I went back to my Motorola 5100 and D-Link router combo.  The line has been rock solid the last four days.  

If in doubt and you have a customer owned modem, you can probably sell it on Ebay.  Then buy the modem only Motorola 5100 and a wireless router (D-Link 825 is what I have) combo.  That will probably work better if your cable lines are marginal (fluctuating SNR and/or dB readings).

EKS

[EG]

---

reacheks wrote:

 If you have had recent weather issues  your SNR readings may rise which could result  in a handshake "lost connection" event.

---

You mean "fall"

[nhbragg]

Still on 3.1 here.  Log shows:

 Thu Apr 26 11:12:44 2012       Notice (6)      TLV-11 - unrecognized OID;CM-MAC=00:23:ee:b7:8d:cb;CMTS-MAC=00:01:5c:22:4a:44;CM-QOS=1.1;CM-VER=3.0;
 Time Not Established      Critical (3)      No Ranging Response received - T3 time-out  
 Mon Apr 23 16:21:27 2012       Critical (3)      Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:23:ee:b7:8d:cb;CMTS-MAC=00:01:5c:22:4a:44;CM-QOS=1.1;CM-VER=3.0;
 Time Not Established      Critical (3)      No Ranging Response received - T3 time-out  
 Time Not Established      Critical (3)      SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:23:ee:b7:8d:cb;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
 Time Not Established      Critical (3)      SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:23:ee:b7:8d:cb;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Very frustrating when all of a sudden my network "hiccups" as the modem resets it's connection.

[Kefkah]

I've been having the same issues here, though the router and service had worked fine when the 3.3.1 firmware update had been in place, then returned when they rolled back the update. I just received the new firmware again last night but now my router has been unable to stay synched up with the comcast servers. It's required me to call in for a manual refresh twice now (The automated refresh failed to refresh the router) and after a short time the connection to the internet drops again, as it goes out of synch with the comcast servers. So far the tech support offered by Comcast's over the phone services has been unable to assist with this, but they're sending a technician over to assist. I was offered the idea of signing up for comcast's signature support service with an extraordinarily high initial fee and high continued payment plan, and it's making me strongly consider switching providers at this point.

[sumsolstice]

I've an SBG6850 with SBG6580-3.3.1.0-GA-11-070-NOSH.

While I see 25Mb/4Mb speeds, I have issues with intermittent disconnects, and large numbers of correctable and uncorrectable errors which makes my (non-Comcast) VOIP phone hard to use.

Last time I had issues - I removed my last splitter from the line and the issue went away for a few months. Now it has returned.

About 9 hours ago, before I went to work, I restarted the modem to clear out the high correctable/uncorrectable error count. I came home to a large # of correctable errors but no uncorrectable errors (nothing much running though).

From what I can tell - the power and signal levels look good. Seeing as how I saw more issues before with the Comcast Docsys 2 modem, and the issue goes away when I reduce the loss in the cable going to it - I find it hard to believe the Motorola SBG6850 is the culprit.

I called Comcast to just talk about it - they said my signal levels were good, but since I owned my modem - not much could be done except for me to go rent one from them. Not a good answer, IMO.

Any thoughts, anyone? I am in the San Jose Area.

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

2

717000000 Hz

7.7 dBmV

36.6 dB

69727

0

2

Locked

QAM256

1

705000000 Hz

8.9 dBmV

37.1 dB

46188

0

3

Locked

QAM256

3

723000000 Hz

8.3 dBmV

36.8 dB

69632

0

4

Locked

QAM256

4

729000000 Hz

8.1 dBmV

36.8 dB

59161

0

5

Locked

QAM256

5

735000000 Hz

8.5 dBmV

36.7 dB

49811

0

6

Locked

QAM256

6

741000000 Hz

7.8 dBmV

36.5 dB

40121

0

7

Locked

QAM256

7

747000000 Hz

6.6 dBmV

35.9 dB

33557

0

8

Locked

QAM256

8

753000000 Hz

6.6 dBmV

36.0 dB

19093

0

Upstream Bonded Channels

Channel

Lock Status

US Channel Type

Channel ID

Symbol Rate

Frequency

Power

1

Locked

ATDMA

10

5120 Ksym/sec

30600000 Hz

44.5 dBmV

2

Locked

TDMA

9

5120 Ksym/sec

35400000 Hz

44.5 dBmV

3

Locked

ATDMA

11

5120 Ksym/sec

23700000 Hz

44.5 dBmV

4

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

Time

Priority

Description

Fri Apr 27 09:25:38 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Fri Apr 27 09:25:35 2012

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Fri Apr 27 09:25:08 2012

Notice (6)

TLV-11 - unrecognized OID;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Time Not Established

Warning (5)

DHCP WARNING - Non-critical field invalid in response ;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.0;CM-VER=3.0;

Fri Apr 27 08:19:47 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Wed Apr 25 02:49:33 2012

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Wed Apr 25 02:47:00 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Sat Apr 21 12:30:11 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Tue Apr 10 07:09:37 2012

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Sun Apr 08 18:43:13 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Sun Apr 08 02:54:16 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Sat Apr 07 18:46:45 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Sat Apr 07 04:52:05 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Fri Apr 06 13:44:42 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Thu Apr 05 22:47:23 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Wed Apr 04 05:29:57 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Tue Apr 03 17:46:57 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Tue Apr 03 10:44:02 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Mon Apr 02 19:52:14 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Mon Apr 02 05:32:45 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Sun Apr 01 12:23:37 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Sat Mar 31 09:42:48 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Fri Mar 30 18:25:25 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Thu Mar 29 11:37:30 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Sat Mar 24 18:39:04 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Fri Mar 23 22:47:01 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Fri Mar 23 11:13:19 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Tue Mar 20 03:36:17 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Fri Mar 16 23:29:05 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Fri Mar 16 08:50:39 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Wed Mar 14 20:39:25 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Wed Mar 14 09:38:55 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Mon Mar 12 11:24:30 2012

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Mon Mar 12 01:41:26 2012

Critical (3)

REG RSP not received;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.1;CM-VER=3.0;

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out

Time Not Established

Critical (3)

No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out

Time Not Established

Critical (3)

No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out

Time Not Established

Critical (3)

No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:01:5c:24:c8:12;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:9e:5f:53:bd:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

                   

[sumsolstice]

My apologies for the long post - didn't realize the formatting would make it so....long

[shlama]

C/P'd from the other thread:

Hi guys!

I spent around a week calling comcast and Motorola about this exact issue. Long story short, I've done a factory reset of the modem and let it do a fresh install of the latest firmware, and no issues since then. Try that and let me know if that works! So far around a day of uptime, no drops. Fingers crossed here.  

[CACoyote]

Since 3.3 FW update:

System Up Time20 days 02h:43m:27s

[dbottoms]

Hi all.  Just reporting I've also enjoyed 20 days uptime so far.  However, I noticed in my system logs on Thursday I received the same unknown error message reported here dozens of times, but, my router did NOT restart.  I noticed the Wireless indicator light on the front of the router was flashing green and orange.  I let the Router go all weekend with nary a blip.  I then toggled the power just to see what was going on and the Wireless light indicator returned to a normal green.  I wonder if there is something to the wireless indicator...   I had a few wireless devices in the house all weekend with no problems so no noticeable disruptions.

[mgraben]

Well, my experience has been the exact opposite.  The latest firmware (version SBG6580-3.3.1.0-GA-11-070-NOSH) has been a disaster.  I not only still have the intermittent drop problem but I also now have a problem with any type of video streaming. 

Streaming video from the Internet causes the router to reboot.  Streaming video from DVRs internal to my LAN also causes reboots.  This last update has some major problems because there's no way it should be causing rebooting just from video streaming between two DVRs at a bit rate of less than 700 KBps.  My old Linksys router had no problem handling this traffic and it only had a 100 Mbps switch built in. 

I disabled WMM just to take that out of the equation but that didn't make any real difference.  Come on Comcast you've had over a year to straighten this out.

[EG]

---

mgraben wrote:

Well, my experience has been the exact opposite.  The latest firmware (version SBG6580-3.3.1.0-GA-11-070-NOSH) has been a disaster.  I not only still have the intermittent drop problem but I also now have a problem with any type of video streaming. 

---

Are the signal stats "in spec" ?

[mgraben]

They appear to be.  Don't see how that could cause reboots while streaming video between DVRs and PCs isolated to the LAN though.

Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables

1 Locked QAM256 2 705000000 Hz -2.1 dBmV 38.1 dB 0 0

2 Locked QAM256 1 699000000 Hz -2.1 dBmV 38.2 dB 0 0

3 Locked QAM256 3 711000000 Hz -2.6 dBmV 37.7 dB 0 0

4 Locked QAM256 4 717000000 Hz -2.9 dBmV 38.1 dB 0 0

5 Locked QAM256 5 723000000 Hz -2.4 dBmV 38.2 dB 0 0

6 Locked QAM256 6 729000000 Hz -2.6 dBmV 38.2 dB 0 0

7 Locked QAM256 7 735000000 Hz -2.3 dBmV 38.4 dB 0 0

8 Locked QAM256 8 741000000 Hz -2.1 dBmV 38.0 dB 0 0

Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power

1 Locked ATDMA 5 5120 Ksym/sec 29400000 Hz 49.7 dBmV

2 Locked TDMA 4 5120 Ksym/sec 22000000 Hz 49.7 dBmV

3 Locked ATDMA 6 5120 Ksym/sec 36200000 Hz 49.7 dBmV

4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

[Jim721]

Your upstream signals are right on the border of to high if it reaches 50 dbmv or higher it can and will cause the modem to reboot.

[EG]

Are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured ?

If there aren't any uneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refreshed them by taking them apart then putting them back together again, then perhaps it's best to book a tech visit to investigate and correct.

As far as the issue with "inter LAN" transfers go have you read this entire thread about the firmware / performance issue/s with this device ?

[mgraben]

So my upstream levels just happen to trigger a reboot nearly every time I try to stream video internally on my LAN?  Even though that requires hardly any access to the WAN side of the network?  Even though they're currently lower than they've been in years and this problem never happened with previous versions of the firmware for this device?

[EG]

What is it that would you like us to say ? Have you tried the *suggestion* yet ?

Ditch the 6580 and go with a separate straight cable modem and a separate high quality router. There is no doubt in my mind that you will be happier..

[Jim721]

It does not matter if your using wan or lan all data still has to come through the modem. As already said that modem you have has a huge history of problems and should be replaced. Keep in mind with your almost out of spec upstream signal any modem may have a problem. Good Luck

[EG]

FWIW, actually, "inter-LAN" transfers will not cross the *cable modem* segment of that device.

[Jim721]

If he is streaming from the web how can it not cross the modem ??

[EG]

See *his* quote here;

"Don't see how that could cause reboots while streaming video between DVRs and PCs isolated to the LAN though"

[Jim721]

Ok EG I gotcha I should have read more carefully.

[mgraben]

As far as splitters leading to the SBG6580, there's just the one after cable enters the house.  It gets its signal as close as possible to the feed from the telephone pole.

As far as reading this thread and any other thread I can find on similar problems via Google, yes I've done that.  And there are several other people reporting similar problems, even a few in this thread.

This is the third generation of Motorola cable modem devices I've owned and for a device on Comcast's aprroved device list it has been extremely problematic.  I would hope that attempting to bring this problem to Comcast's and Motorola's attention would encourage them to spend a little more time and effort before approving a device and let them know that there are still problems with the current firmware.

[EG]

I feel your pain !

[SSubZero]

Ever since the new firmware my event log on the router has been "busy" but any events tend to happen irregularly.  I did have one entry about a failed "software download" over the last couple of days, not sure if they are pushing something.  DO NOT DOWNGRADE ME.

[EG]

---

SSubZero wrote:

I did have one entry about a failed "software download" over the last couple of days, not sure if they are pushing something.  DO NOT DOWNGRADE ME.

---

FWIW, a "software" / firmware push would not have anything to do with a speed tier / rate cap. That is controlled by a configuration / boot file push.

[MDRL]

Just give up! I did a few monthes ago because my husband's business rides on it! Got the Motorola 6121 modem and brought back the router... No issues since! Just have one 6 inch extra piece of equipment on my desk! I am keeping the "email me when someone replies" checked... Just so I know if I can send this 6580 to college with my son!