dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1281
share rss forum feed

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA

Problem with new sb6121 modem

A week ago I bought a sb6121 to replace my sb4200. For a few days it worked perfectly, but since then I've had repeated issues.

The signal power and SNR has always looked fine. However, the last few days there has been an increasing problem with one or more channels showing large numbers of uncorrectable codewords. Sometimes the line speed remains good, but at other times, like this morning, the speed drops to less than 1 Mbps. I've include the log entries since I bought the modem. This morning the speed was good, even though there was still a too-large number of bad codewords on the third channel. However, at about 7:57 I suddenly noticed the speed had dropped to a crawl. I checked the log and found some of the typical notices/errors I've been getting. The modem so far has never rebooted by itself, so any reboots in the log were done by me(although yesterday the utility company shut off the power for a little while. Anyway, this morning the speed remained lousy, with 17+% of the codewords on one channel being uncorrectable. I tried rebooting the modem a couple times, but the speed remains bad and the bad codewords way too high. As I type now, the log is being filled with the same messages over and over(ds partial service fallback, lost mdd timeout).

A couple nights ago I noticed the speed had dropped to a crawl, and the log and signal pages showed simliar stuff, although this time there were only three channels being bonded. I tried resetting the modem's power. When it rebooted the speed was good again, but there was no channel bonding. The next morning it was the same(good speed, no bonding) so I tried another reset/reboot and this time the 4-channels bonding returned(this was yesterda). The rest of the day the speed and bonding was fine, but there were still a fair amount of uncorrectable codewords on one channel(usually the 3rd channel listed).






Time Priority Code Message

Nov 05 2013 08:04:28 6-Notice MDD Recovery following MDD Loss;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 05 2013 08:04:23 5-Warning T202.0 Lost MDD Timeout;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 05 2013 08:04:23 5-Warning DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 05 2013 08:03:34 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Nov 05 2013 07:58:53 6-Notice MDD Recovery following MDD Loss;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 05 2013 07:58:48 5-Warning T202.0 Lost MDD Timeout;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 05 2013 07:58:48 5-Warning DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 05 2013 07:57:39 6-Notice MDD Recovery following MDD Loss;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 05 2013 07:57:02 5-Warning T202.0 Lost MDD Timeout;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 05 2013 07:57:02 5-Warning DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 04 2013 16:06:08 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 04 2013 08:14:31 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Nov 03 2013 16:46:33 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 03 2013 16:46:09 5-Warning T07.0 RCS Partial Service;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 03 2013 16:46:08 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 03 2013 16:14:01 5-Warning T202.0 Lost MDD Timeout;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 03 2013 16:14:01 5-Warning DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 03 2013 13:40:45 4-Error D103.0 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Nov 02 2013 16:49:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Oct 30 2013 14:00:10 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Oct 30 2013 13:21:12 4-Error D103.0 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Oct 30 2013 11:59:44 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from SNMP ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Oct 30 2013 11:48:24 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:76;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Sep 16 2013 19:45:09 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=44:d3:ca:26:e9:a3;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Jun 22 2013 21:56:03 5-Warning T202.0 Lost MDD Timeout;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:30:b8:81:73:f0;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:19 5-Warning T203.0 MDD message timeout;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from SNMP ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Jun 22 2013 21:54:54 5-Warning T202.0 Lost MDD Timeout;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:30:b8:81:73:50;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:32 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:30:b8:81:73:50;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:19 5-Warning T203.0 MDD message timeout;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from SNMP ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Jun 22 2013 21:53:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:17:10:01:f7:2d;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from SNMP ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:17:10:01:f7:2d;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:19 5-Warning T203.0 MDD message timeout;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:66:dd;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;


MediacomChad
Mediacom Social Media Relations Team
Premium,VIP
join:2010-01-20
Gulf Breeze, FL
kudos:117
Thank you for bringing this to my attention. I have looked over the modem and can see a spike in all upstream signals, and the downstream signals are not reporting. There is definitely an issue here. Do you happen to have any splitters connected? If so, can you remove it/them and see if there is any change? If there is not, let me know here and I will be happy to schedule for a service technician to come out and look into this.
--
MediacomChad
Mediacom Social Media Relations Team
»mediacomcable.com/CustomerSupport/

GLIMMER

join:2004-01-17
Fisher, IL
reply to hawkeye_wx
i had this problem and it was a docsis 2.0 filter on the line

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA
reply to MediacomChad
There are two splitters on the line... one where the line enters the house, which sends several lines off to all the rooms, and another in the computer room that sends one line to a tv and the other to the modem.

I just got home and my line speed has returned to normal, the skyrocketing bad codewords have slowed way down, and there have not been any other log entries. Before I try removing the second splitter could you check the line signals one more time?


MediacomChad
Mediacom Social Media Relations Team
Premium,VIP
join:2010-01-20
Gulf Breeze, FL
kudos:117
I am not getting any reports from the modem at this time.

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA

1 edit
Is this very unusual and indicative of something being very wrong? Can I assume you should be receiving reports from the modem that everything is working well? If there is a major issue, would removing one splitter make that much of a difference? I've had good internet service for many years using the old sb4200 modem and the same number of splitters.

k9iua6

join:2004-05-23
Dubuque, IA
kudos:1
reply to GLIMMER
said by GLIMMER:

i had this problem and it was a docsis 2.0 filter on the line

What is a "docsis 2.0 filter"? Never heard of such a thing. A broadcast basic TV filter, yes, but not a DOCSIS filter.


MediacomChad
Mediacom Social Media Relations Team
Premium,VIP
join:2010-01-20
Gulf Breeze, FL
kudos:117
reply to hawkeye_wx
It looks like your modem is reporting in one of our systems, but not in another. It looks like it has been online for just over 5 hours, but signal levels haven't really changed that much. If there is no change in the level of service, I may want to set up a tech visit to check inside out of the house for issues. Would you like for me to set this up?

k9iua6

join:2004-05-23
Dubuque, IA
kudos:1

2 edits
reply to hawkeye_wx
said by hawkeye_wx:

I've had good internet service for many years using the old sb4200 modem and the same number of splitters.

I understand that Docsis 3 modems have a narrower window of good operating parameters. Older DOCSIS protocol modems could tolerate a wider range of power levels. Ideally all four channels are coming into the modem with about the same power level. Although the power level to each of your channels are not too far different from each other, channels 3 and 4 are nonetheless different. Removing the second splitter before the cable modem would raise the power levels to all four channels and get them all closer to the 0 dBmV level, at least as a test.

ADDED: Do you have a TV subscription? If so, then you shouldn't have any filter on your line. But if you don't have a TV subscription or you have Broadcast Basic only, then you likely have a filter on the line. The cutoff of those is about where your 3 and 4th DOCSIS channels currently line up. If so, then the filter is messing with your signals and you might also need a new filter combination put in (what Glimmer was likely referring to). With slower, single-channel HSI users this wouldn't be a problem, as the channels assigned to our modems are typically low enough in frequency to not run into the filter.

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA
reply to hawkeye_wx
k9, I have the family cable plan(extended basic) with the sports tier.

I just removed the second splitter from the line and there is very clear improvement in the signal values. The SNR is now within 1 dB across all channels, the downstream power level has gone from (-2 to -5) down to zero for all channels. The upstream power level has dropped to 39. This is also the first modem reboot in the last couple days in which there was no immediate bad codeword spike. I am also now getting the highest results I've ever had on speedtest(29+ Mbps). MediacomChad, what are you seeing from your end now?




MediacomChad
Mediacom Social Media Relations Team
Premium,VIP
join:2010-01-20
Gulf Breeze, FL
kudos:117
There was a definite signal spike after the splitters were removed. You may want to look at replacing one or both of them. If the issue persists after doing this, let me know.

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA
So Chad, do all the signals to/from my modem look good from Mediacom's end now? If so, and if my internet performance continues to be good with no other problems, then it seems the ideal option would be to keep a second splitter off the modem's line permanently and put another splitter on one of the tv-dedicated lines to run the cable tv line into the computer room. Does that sound right?


MediacomChad
Mediacom Social Media Relations Team
Premium,VIP
join:2010-01-20
Gulf Breeze, FL
kudos:117
Yes that does sound like the best course of action.

k9iua6

join:2004-05-23
Dubuque, IA
kudos:1
reply to hawkeye_wx
I'm glad you have improvement. If your first splitter has an odd-number of output ports (a 3 or 5-way splitter, for instance), you will usually see one of the lines will be marked to have less attenuation than the others. That would be the port you should put the two-way splitter on. If you have a four-way splitter, then you won't have that difference in output lines, and so it won't matter as much other than maybe from differences in length of cable runs.

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA

1 edit
k9, after the line enters my house it passes into a 2-way splitter. One output line now goes directly to the modem. The other output line goes to a 4-way splitter. All those output lines go to the tvs.

k9iua6

join:2004-05-23
Dubuque, IA
kudos:1
said by hawkeye_wx:

k9, after the line enters my house it passes into a 2-way splitter. One output line now goes directly to the modem. The other output line goes to a 4-way splitter. All those output lines go off to the tvs.

That is a good setup then. Each cable leg is equally balanced for the TVs and the cable modem is getting the most direct signal. And I believe how you would want the wiring in place for multi-room DVR sharing in the future.

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA

1 edit
said by k9iua6:

That is a good setup then. Each cable leg is equally balanced for the TVs and the cable modem is getting the most direct signal.

Except there are five tvs so, for now, I have to split the line going to my bedroom and send one output to the tv in the computer room... so each of those two tvs will now receive a weaker signal. I can always get a 5 or 6-way splitter later on if I have to.

k9iua6

join:2004-05-23
Dubuque, IA
kudos:1

1 edit
said by hawkeye_wx:

Except there are five tvs so, for now, I have to split the line going to my bedroom and send one output to the tv in the computer room... so each of those two tvs will now receive a weaker signal. I can always get a 5 or 6-way splitter later on if I have to.

A five- or six-way splitter will give more of your TVs a weaker signal than just the two TVs following the additional 2-way splitter. Each level of splitter drops a signal by about 3.5 dB. A four-way splitter is just 3 two-way splitters in an integrated unit. A five-way splitter adds another two-way to one of the poles, same as your added two-way, although the difference will be in needing all cable runs come all the way back to the five-way splitter. Similar for a six-way splitter, etc. I guess it comes down to how you want to do your cable runs and the level of signal getting to your various TVs and the level of signal loss you can sustain to each before the picture degrades.

MediaCon

join:2013-11-02
Chillicothe, IL
At the pole there are extra slots for each household. Have Mediacom run a new line so you don't get line degradation. Then run 4 way splitter there and go to different rooms.

Nexis

join:2002-04-29
USA
Reviews:
·US Cellular
Actually, there are not "extra slots" for each household. Most places there are enough ports to service the homes that would connect to that pole, and no more.

The proper way to get this figured out would to have a tech stop out and take a look. We can sit and talk about it on the forums all day long, but at the end of the day, getting a tech there to run through the system and see what is going on would be best.

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA
I'm happy with the picture on all my tvs, including the bedroom tv I just added a second splitter to, so I will just go with my current setup.


MediacomChad
Mediacom Social Media Relations Team
Premium,VIP
join:2010-01-20
Gulf Breeze, FL
kudos:117
Good to hear that it is working for you! Let me know if you have any other issues going forward.


Anonymous
Premium
join:2004-06-01
IA
kudos:2
reply to k9iua6
Mediacom used to have a different trap for internet only customers. It's about 5 inches long and it degrades 2 of the 4 channels used for downstream (123MHz and even more 129MHz). The new DOCSIS 3 compatible trap is only about an inch long.

The problem is there are still a lot of them in the field and unless you call in with a problem and have a tech out nobody will upgrade your trap.
--
I speak for myself, not my employer.

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA

1 edit
reply to hawkeye_wx
My sb6121 had been up for about five days since I removed the second splitter from the line. During that time the speed was good, although there were a couple T3 time-outs, as shown below on Nov 8, and one DHCP renew warning. Then, late this afternoon, the speed was still good but I suddenly could not access the modem's web interface(192.168.100.1). It just sat there trying to load, but never did. I could still access other web pages. Then, the modem rebooted itself. After the reboot everything is fine again. I checked the log to see what happened and there is a strange "received response to broadcast maintenance request..." entry. Could MediacomChad, or anyone, explain what happened and if I should be concerned about my line or modem? This goes for the other error/critical log entries as well.

I will add that my uncorrectable codewords were up to about 30,000 on each channel after five days, which seems high(my brother, a comcast user in chicago has zero uncorrectables in the last 45+ days), although percentage-wise that is just a tiny fraction of 1% of the total traffic.

Edit: I just remembered that my modem did reboot itself once for no obvious reason several hours after removing the second splitter. It was then up for 5 days after that reboot. Obviously, a reboot out of nowhere isn't what I was hoping to see at that point or ever.

Nov 11 2013 16:45:03 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out

Nov 08 2013 15:47:50 4-Error D103.0 DHCP RENEW WARNING - Field invalid in response v4 option

Nov 08 2013 05:06:26 3-Critical R02.0 No Ranging Response received - T3 time-out

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA
MediacomChad, can you tell me anything about my last post, like what that "broadcast maintenance request" is about?

Since that happened, my line speed has felt a bit sluggish compared to the snappy feeling it had before. In speedtest my typical ping used to be about 19, but now it is nearly always in the low 30s for the same servers. Also, before my speed would immediately shoot up into the 20s and end at about 28. For the last four days my speed starts in the teens and slowly rises to about 24 or 25 at best. A few tests have been lousy. This morning I decided to reset the modem to see if I could get the previous snappy speed back, but now the modem won't bond channels. I tried resetting several times with no change.

The last couple days I have also had another T3 time-out and another DHCP renew warning in the log, although I don't know if that is significant if you don't lose connection.

Just now I did another couple speedtests using chicago servers and I got 20 and 16 down, whereas I used to get 26-28 pretty much every time.


MediacomChad
Mediacom Social Media Relations Team
Premium,VIP
join:2010-01-20
Gulf Breeze, FL
kudos:117
Hey hawkeye_wx,

Usually with the T3 and T4 timeouts you'll see some sort of signal issue so I checked over your levels and for the most part everything checks out. I do notice that from the evening of 11/8 to the evening of 11/11 the downstream error counts for your area were spiking around 2% which will definitely cause you to see errors on the modem and slower speeds. Since the night of the 11th though this seems to have calmed down significantly to levels that should not cause any more problems. Also over the past 4-5 days it appears that at night usually sometime around 7PM your area is experiencing upstream error counts increasing and again this will show as errors on your modem and may cause the slower type speed results you are seeing. They don't appear to be constant though. Is the issue with the speedtests happening every time now or can you still get proper results?
--
MediacomChad
Mediacom Social Media Relations Team
»mediacomcable.com/CustomerSupport/

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA

2 edits
The several speed tests I just did all had results in the low to mid 20s, although I'm still not getting the consistent 26-29 I was getting before. I did run some tests on a different, faster computer and I did notice the ping was back down to around 20, so there may be something bogging down my main ancient computer that's affecting that. Anyway, for right now I need to figure out the channel bonding issue. I've rebooted my modem several times in the last couple hours, and also did a factory reset, but I'm still not getting any channel bonding. What could the problem be? I remember once during the first week after getting the modem it failed to channel bond after a reboot, and another couple reboots didn't fix it, but then the next morning another reboot did fix it.


MediacomChad
Mediacom Social Media Relations Team
Premium,VIP
join:2010-01-20
Gulf Breeze, FL
kudos:117
Thank you for the information. If you are just seeing the issue on the one PC or it's worse on just one device then further troubleshooting with that equipment would be needed. As for channel bonding, I'm not sure if there is a way to force channel bonding on the 6121 but I do know that the bonding occurs if needed in our system. So if you can pull the proper speeds with just 1 channel bonded then the modem should only bond to the 1 channel. I have heard of these situations before with other customers and normally it's just a matter of time or a reboot and the modem will start bonding to more downstream channels again. I'll look into that a bit further on my end though.
--
MediacomChad
Mediacom Social Media Relations Team
»mediacomcable.com/CustomerSupport/

hawkeye_wx

join:2009-01-07
Cedar Rapids, IA
I just tried another faster wired computer and it is getting good ping(19ms) and good down speed(28+ Mbps), so it seems there may be some background processes slowing down my main computer by stealing the already limited resources. So it seems the line speed is good, but just no channel bonding for some reason. I'll try another modem reboot tomorrow to see if the bonding returns.


MediacomChad
Mediacom Social Media Relations Team
Premium,VIP
join:2010-01-20
Gulf Breeze, FL
kudos:117
When you do the reboot on the modem try this method: Remove power and coax cables from the modem for 1 minute. Screw the coax back in first then restore power. Let me know how that goes.