dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
2665
asiatrails
asiatrails
join:2014-09-06

1 edit

asiatrails

Member

[OK] Poor Service in Owasso

I am very frustrated with Cox for the last two months service has been intermittent, failed, or just slow. I have called tech support and Wow, what a difference from a year ago.

A year ago I had no problems in getting the system installed, the tech ran new cable from the modem direct to the backyard box, everything was great, speed tests on multiple locations was excellent, got what I paid for.

A couple of months later, my modem failed and I had to replace it on a Saturday night. Tech support were able to get it talking to the world very quickly. Moved my tier of service up to Cox Premier to get better Netflix, all was good.

About eight months ago the speed started to go erratic and I had a tech come out, found a lot of corrosion in the terminal box, green tube like thing in the back yard, tech replaced the splitter and said he would put in a ticket to have it replaced.

Never replaced, signal degrades or goes down when it rains, called Cox and was asked if the tech was a contractor or one of their employees - No frigging idea he had a Cox shirt on and was driving a Cox van. This was the first crack in the good impression.

Internet kept getting worse, then got better when the premier upgrade to 100 down 10 up was rolled out, then it went to crap again. Just ran a speed test on Ookla and got 0.7 up and 1.14 down, tried other test sites just as bad, see comment about Ookla under speed test.

About a month ago, I had a long discussion with tech support and they said they would send someone out to check things out. Got a call from the tech, on the wrong day, to say he could not find the address. WTF, there are things called maps, Google earth, or GPS that shows the city, subdivision, street, and even the house. Called tech support ticket was closed by the tech as no fault found.

Yesterday evening, no internet, called tech support and was told that they could send someone next Wednesday, lots of apologies, can see the problem, its on their side, basically you are stuck until it either starts working or our sainted tech appears on Wednesday. basically "It sucks to be You" was the impression I got. At the end of the conversation I was told that it would be "escalated" and I should get a call from a senior tech tomorrow. It's now afternoon, I have stayed in all morning and no call yet.

This is no way to treat a customer and expect them to stay when options arrive.

Motorola Surfboard DOCIS 3
Netgear N900
Cox Premier 100/10
My speed test with Ookla consistently shows 0.7 up and 1.14 down, Garbage!!!. I used other sites but was told by the tech that Ookla is the "Only Recognized by Cox and is The Best Global Test Site" Wow Fantastic.
No splitters wired by cox directly to the termination point in the back yard
No tweaked (ยป/tweaks) or twerks
Connected bot ways wired and wireless
• have you tested speeds bypassing router - Yes no change
• are other services such as phone or tv affected - Yes Netflix etc. is useless?
Will not post MAC address on open forum but here's the error file from the modem

Sep 20 2014 22:16:31 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 22:16:31 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;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=b0:77:ac:8e:dc:ab;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:27:45 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:27:45 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;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=b0:77:ac:8e:dc:ab;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:07:47 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:07:22 5-Warning T202.0 Lost MDD Timeout;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:07:22 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:07:22 5-Warning T202.0 Lost MDD Timeout;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:07:22 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:06:41 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:06:34 5-Warning T202.0 Lost MDD Timeout;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:06:34 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:05:45 5-Warning T07.0 RCS Partial Service;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:05:44 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:05:44 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 19:03:45 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;

Hard Harry7
join:2010-10-19
Narragansett, RI

Hard Harry7

Member

Looks like a possible downstream issue from just looking at the T4 and the partial service fall back. Thats basically your modem falling back to DOCSIS 2.0 tech. Can you post your signal levels?
asiatrails
asiatrails
join:2014-09-06

asiatrails

Member

Click for full size
Well it's 8:30 PM here and no call or contact from Cox, I guess the words of the customer service guy fell on deaf ears.

Thanks for your interest and I like the Tom Waits song as well.

Signal levels attached, they are all over the place.

Here are the latest error files:

Sep 21 2014 19:58:51 5-Warning T202.0 Lost MDD Timeout;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 21 2014 19:58:51 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 22:16:31 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 22:16:31 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;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=b0:77:ac:8e:dc:ab;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Hard Harry7
join:2010-10-19
Narragansett, RI

Hard Harry7

Member

Yea, as I thought, your DS SNR levels are low. Should be 36 or above. Channel ID 120 is at DS SNR 33, which is probably causing your modem to drop the channel and try to reconnect, causing the T4 your seeing.

Whats the cabling like from street to modem? You said "the tech ran new cable from the modem direct to the backyard box" What backyard box? Do you mean a pedestal like this?

»davewhitmore.net/images/ ··· stal.jpg

If so, the problem is either at that box, or more likely the underground wiring. Which explains why the Techs aren't really seeing the problem, since digging up a underground tap and relaying it is expensive. Is a above ground drop possible?
asiatrails
asiatrails
join:2014-09-06

asiatrails

Member

Yes the box looks like that but more corroded. My connection has a filter on it like the top left in your picture. My neighbors use AT&T so no comparison possible.

The tech ran a new line underground from this box to the wall of the house, put a new interface box there and then ran a line directly to the modem. So one splice in the line.

By the saints of the HOA (and city code) all cables in the subdivision are underground.

Hard Harry7
join:2010-10-19
Narragansett, RI

1 edit

Hard Harry7

Member

said by asiatrails:

The tech ran a new line underground from this box to the wall of the house

Then the problem must run from that box to the street or where ever the main line comes from, or the pedestal itself. And if the line goes under someones driveway or sidewalk, and you have a strict HOA, then I can see why this issue may have gone unresolved for a while. All this is just speculation though. Your problem is that 33 DS SNR, I bet my hat on it.
bchandler02
join:2011-07-08
Oklahoma City, OK

bchandler02 to asiatrails

Member

to asiatrails
You need to get thru to some management within Cox. I had similar problems as you - stable for years, then about a year of hell, and now that they finally fixed it right, stable as can be again. Maybe get CoxTech1 here to help you our, or call and raise hell with the local office. Demand a few supervisors, etc.

Worst case, try an exec email carpet bomb to all of the Cox executives. That's ultimately what I had to do but once I got their attention, I had it and the issues got fixed and fixed right.

It sucks that you have to go through stuff like this just to get them to fix it, but I guess that's life these days.

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA
Nokia BGW320-505

1 edit

odog to asiatrails

Premium Member

to asiatrails
said by asiatrails:

Well it's 8:30 PM here and no call or contact from Cox, I guess the words of the customer service guy fell on deaf ears.

Thanks for your interest and I like the Tom Waits song as well.

Signal levels attached, they are all over the place.

Here are the latest error files:

You only have 7 channels.... you should have 8. You're missing channel 114 aka 843MHz, due to it being so "bad" the modem can't use it. Make sure all the cables are tight, with no loose connectors, or unterminated splitters. Pay close attention that you don't have a cell phone near the modem. Particularly if the cell phone is at the fringe of the tower range and has low signal.
asiatrails
asiatrails
join:2014-09-06

1 edit

asiatrails

Member

Click for full size
Click for full size
Click for full size
Click for full size
Thanks Odog, I thought I was missing something. Everything is tight, no cell phones near the router or modem. I believe the fault is outside, here are the Ookla pings for Tulsa, upload is good, download is horrible.

I just waited on hold for Cox for 12 minutes "all !!!!!! are helping other customers" gave up in disgust.

And just to cap things here is todays error log and channel data.

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA

odog

Premium Member

Check that all the cables are tight, and that there are no loose connectors on any of the devices connected to cable. Also make sure that you're using good quality shielded cable.

Do you happen to have an AT&T/Tmobile cell phone?
asiatrails
asiatrails
join:2014-09-06

1 edit

asiatrails

Member

Yes I do, interesting question. Tried with the phones turned off, no difference.

It is now 8:30 pm on Tuesday, still no call from Cox support, so much for the promised call on Sunday.

Here is the event report log update:

Sep 23 2014 17:45:38 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 23 2014 17:45:38 5-Warning T202.0 Lost MDD Timeout;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 23 2014 17:45:38 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 23 2014 17:44:01 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 22 2014 13:13:14 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 22 2014 13:12:43 5-Warning T202.0 Lost MDD Timeout;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 22 2014 13:12:43 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 21 2014 19:58:51 5-Warning T202.0 Lost MDD Timeout;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 21 2014 19:58:51 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 22:16:31 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 20 2014 22:16:31 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;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=b0:77:ac:8e:dc:ab;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA

odog to asiatrails

Premium Member

to asiatrails
you would have to turn the phones off, and then likely reboot the modem to get it to bond all 8 again.

If it then does bond 8, you have very leaky cable and the cellular signal is interfering with the cable signal.
asiatrails
asiatrails
join:2014-09-06

1 edit

asiatrails

Member

Interesting thought, I rebooted the modem about an hour ago and got all the channels back. A couple of error messages since then, lets see how it holds out. Just ping checked with Ookla, still the same should be 100 down, getting 47 at best, up is OK at 11, contract is for 10.

Sep 24 2014 19:11:45 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 24 2014 19:11:45 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;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=b0:77:ac:8e:dc:ab;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA
Nokia BGW320-505

odog

Premium Member

said by asiatrails:

Interesting thought, I rebooted the modem about an hour ago and got all the channels back. A couple of error messages since then, lets see how it holds out. Just ping checked with Ookla, still the same should be 100 down, getting 47 at best, up is OK at 11, contract is for 10.

How are you connected to the modem? A gigabit ethernet router, and wired gigabit ethernet to the router?
odog

odog to asiatrails

Premium Member

to asiatrails
You find something?

I'm seeing 37.9dB SNR on 843MHz now
asiatrails
asiatrails
join:2014-09-06

1 edit

asiatrails

Member

Click for full size
Click for full size
Found nothing wrong, it was there after the reboot, but now it's gone again. Just wasted another 10 minutes of my life on hold

Sep 25 2014 14:54:26 5-Warning T202.0 Lost MDD Timeout;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 25 2014 14:54:26 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 25 2014 14:53:46 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 25 2014 14:41:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 25 2014 14:26:04 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 25 2014 11:42:48 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 24 2014 19:39:48 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 24 2014 19:39:48 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:23 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot from GUI/Configuration page ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA

odog to asiatrails

Premium Member

to asiatrails
I would book a trouble call. If you/we can't find the problem, that is about the only thing we can do.
asiatrails
asiatrails
join:2014-09-06

asiatrails

Member

I want to believe that Cox intends to live up to the promised performance, this might be promising, I just found this in the log today, looks like some kind of software update. I will let it settle in before trying a speed test or rebooting the modem to see if it stays. I have no idea what an "unrecognized OID" is.

Sep 26 2014 08:57:50 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 26 2014 08:57:50 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 26 2014 08:56:56 6-Notice N/A Cable Modem Reboot from Software upgrade ;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;
Sep 26 2014 08:56:55 6-Notice E111.0 SW download Successful - Via NMS
Sep 26 2014 08:55:44 6-Notice E101.0 SW Download INIT - Via NMS
Sep 25 2014 14:54:26 5-Warning T202.0 Lost MDD Timeout;CM-MAC=b0:77:ac:8e:dc:ab;CMTS-MAC=00:14:f1:eb:32:9f;CM-QOS=1.1;CM-VER=3.0;

Anonguy
@68.106.20.x

Anonguy

Anon

The TLV-11 - unrecognized OID message simply indicates that the configuration file contains different vendor (or multiple vendor) information in it.

Cable modem configuration files have multiple vendor-specific TLV-11, commonly called miscellaneous OIDs. They tell each brand of equipment how to do specific things for only that vendor. Since the config has multiple brands in it, all modems will report that error. They don't report that error when they see their native vendor info, but will report it during digestion of a config with other VSIF OID in it.

You may see the above notice in your cable modem's log files every time the modem registers it gets the configuration file. It should not affect the cm operation in any way.

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA

odog to asiatrails

Premium Member

to asiatrails
Yes, I upgraded your software.

The modem appeared to go back into 8 bonding mode after the firmware/reboot. I still think you have an ingress issue causing 843MHz to become unusable.
asiatrails
asiatrails
join:2014-09-06

asiatrails to Anonguy

Member

to Anonguy
Thanks, a bit of online checking confirms this, this is not the droid I am looking for.
asiatrails

asiatrails to odog

Member

to odog
I think so but I have seen a lot of Cox vans around here this week so I am almost optimistic that they have found some type of common error. Still no call from them though.
asiatrails

asiatrails to odog

Member

to odog
So far so good, getting 90 down and 12 up. Waiting for the rain to see if things go bad again. Here are the latest Ookla results. No new modem error messages.
asiatrails

asiatrails

Member

Well it's been a while since I updated this post, thanks to odog the service seems "mostly stable".

Channels 114 & 113 keep swapping positions on the router table and I get a T4 fail reboot about every 10 to 15 days.

On Ookla, the speed is close to or better than contracted and the family are not complaining, which is good, other testers do not show such good results.

So, overall, it's not perfect, right now, it works fast enough most of the time for what we need, that said, the overall infrastructure needs to be updated.

I did pull a 9600 baud modem out of the garage, locked it down to 2400 baud and put it in my youngest son's computer, once he got onto the internet, he stopped complaining about the cable speed very quickly.

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA

odog

Premium Member

All the speeds appear to be 90-100? I can't really see them due to the picture being so small.

If you can try using the speedtest.cox.com, those are logged and I can actually see the test history.
asiatrails
asiatrails
join:2014-09-06

asiatrails

Member

Click for full size
Thanks odog, I will use that link for future checks, why do the support guys always say we recognize no one as worthy but the sainted Ookla?

have waited patiently for Cox to fix the problems; as with most things it got better then drifted down to rubbish. I called Cox a few times recently and the first tier service is either good or rubbish, finally got a good one today and service is sort of working.

Here is a snapshot of the modem log since noon today, this is not the service I am paying for.

asiatrails

asiatrails

Member

Click for full size
And here is a speed test from cox.com, I suppose half is better than none.
asiatrails

asiatrails

Member

Click for full size
And now we get

MarkRH
Premium Member
join:2005-02-08
Edmond, OK
ARRIS BGW210-700
ARRIS TM3402
Asus RT-AC68

MarkRH to asiatrails

Premium Member

to asiatrails
Interesting. I go to speedtest.cox.com and it asks for a username and password in which my Cox account username/password does not work.

I try to run the speedtest via internet tools (same area that bandwidth usage is) and the test always fails with a latency test error.

Hrmm.. should probably start my own thread.. oops.
asiatrails
asiatrails
join:2014-09-06

asiatrails

Member

Click for full size
and here are the bonding values