Skip to main content
bdub's profile
bdub

New Contributor

 • 

3 Messages

Sunday, June 23rd, 2013 9:59 PM

Closed

Not getting 50 MBps????

Hi,

  Seen a few posts on here where a Tiffany R was able to resolve the same issue I'm having in a matter of seconds. I'm hopeful, her, or someone else from Cox reading this forum can assist. Bought a brand new SB6141 yesterday. Upgraded...or was suppose to have upgraded...from Preferred to Premium Internet this morning. 

Download speeds are just the same...25-30 MBps, as what I had before. I do see a slight change in the upload speeds, but I have to believe there is something missing that isn't allowing me to get to 50 MBps or at least close? Called a tech twice and all I'm told is signals look great, we do a speed test directly connected to the modem, turn of antivirus, etc...nothing changes. I have no splitters, running direct in to the wall. I used speedtest.net and Cox's own speed test....Omaha Market selected...nothing changed.  

Last conversation said I have 1DS and 4US channels. Seems a bit off isn't it? I have 8x4 on my modem signal page. I've seen a few fixes related to changing a code on the billing side that supported the correct 3.0 modem, another change was done to re-provisioning something so the additional bonding channels were recognized, etc...

Why do people on this forum know these quick and easy changes, but when you call in no one can make these quick fixes while your on the phone?

Tiffany R. if your out there, please help!! I am getting frustrated, I am paying more but not getting more....other then being told a technician can come out and we may charge you $70 for coming out. Not sure what that's all about.

Can anyone help please???

Thanks!

Discussions

 • 

Updated 

12 years ago

3.5K

3

0

0

bdub

New Contributor

 • 

3 Messages

12 years ago

I also just read where my modem may need a firmware update? I don't see one in my log since yesterday. Not sure if that helps? All of the resets are from time on the phone with techs.

Jun 23 2013 16:27:34 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jun 23 2013 16:27:34 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 23 2013 15:52:10 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jun 23 2013 15:52:10 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 23 2013 15:46:51 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jun 23 2013 15:46:51 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot from SNMP ;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jun 23 2013 15:45:31 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jun 23 2013 15:45:31 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jun 23 2013 13:53:02 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jun 23 2013 13:53:02 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:26 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot from SNMP ;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 22 2013 14:41:54 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jun 22 2013 14:41:54 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=dc:45:17:a2:75:9e;CMTS-MAC=c4:71:fe:76:cb:a1;CM-QOS=1.1;CM-VER=3.0;

0

0

KipK

Valued Contributor II

 • 

606 Messages

12 years ago

bdub said:
I also just read where my modem may need a firmware update? I don't see one in my log since yesterday. Not sure if that helps? All of the resets are from time on the phone with techs.

A firmware update shouldn't be strictly necessary, but it won't hurt and will happen eventually, so I did that  anyway. 

However, the problem was that you had the Premier code for DOCSIS 2, and needed the Premier code for DOCSIS 3. I'm sorry to say that we still see this from time to time.

You should be all set now. Let us know how it goes.

0

0

bdub

New Contributor

 • 

3 Messages

12 years ago

Really appreciate the quick response. I had a feeling that it was something rather simple on the back end. Ran a speed test and got 63 down and 12 up so thank you very much. I'll let you know if those speeds aren't reflected in the coming days.

Regards,

0

0

Related Content

Loading...

Recent Discussions

View More

Loading...