I had a second tech out at the start of the week taking a look into my situation over here. He did the usual signal test but as I was explaining the issue he said "interference" and said he was going to go grab some tools off his truck. He came back in and tested my line and found power on it. He traced it to my outside storage unit where an unknown cable was being fed into a splitter that was rather dated (probably installed some 15+ years ago at this location). I had the tech bypass the splitter as I wasn't using the cable in my bedroom and have no intention to use it during the next 6 months that I'll be here.
The internet worked fine for a few hours after that discovery but again started to have issues as the evening rolled on. I let most of the week go by to see how many times I would get T3 time-out issues so I could report back asking for further assistance. Today I jumped on my modem to see what the event log had to say and found the following:
| Time | Priority | Description |
| Apr 09 2018 17:15:07 | Warning (5) | Lost MDD Timeout |
| Apr 09 2018 17:15:07 | Warning (5) | Lost MDD Timeout |
| Apr 09 2018 17:15:07 | Warning (5) | Lost MDD Timeout |
| Apr 09 2018 17:15:07 | Warning (5) | Lost MDD Timeout |
| Apr 09 2018 17:15:07 | Warning (5) | Lost MDD Timeout |
| Apr 09 2018 17:15:07 | Warning (5) | Lost MDD Timeout |
| Apr 09 2018 17:15:07 | Warning (5) | Lost MDD Timeout |
| Apr 09 2018 17:15:07 | Warning (5) | Lost MDD Timeout |
| Apr 09 2018 17:15:44 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| Apr 09 2018 17:27:12 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Apr 09 2018 17:27:12 | Notice (6) | TLV-11 - unrecognized OID |
| Apr 09 2018 17:34:59 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Apr 09 2018 17:34:59 | Notice (6) | TLV-11 - unrecognized OID |
| Apr 10 2018 08:07:13 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 07:53:00 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 11 2018 07:53:00 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 07:53:40 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 11 2018 07:53:40 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 07:54:04 | Critical (3) | Ranging Request Retries exhausted |
| Apr 11 2018 07:54:04 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted |
| Apr 11 2018 07:54:24 | Critical (3) | Ranging Request Retries exhausted |
| Apr 11 2018 07:54:24 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted |
| Apr 11 2018 07:55:00 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 11 2018 07:55:00 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 07:56:20 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 11 2018 07:56:20 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 07:57:40 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 11 2018 07:57:40 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 07:59:19 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 11 2018 07:59:20 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 08:00:59 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 11 2018 08:01:00 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 08:09:20 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 11 2018 08:09:20 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 08:09:58 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 11 2018 08:09:59 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 11 2018 19:19:05 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Apr 11 2018 19:19:05 | Notice (6) | TLV-11 - unrecognized OID |
| Apr 11 2018 19:26:26 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Apr 11 2018 19:26:26 | Notice (6) | TLV-11 - unrecognized OID |
| Apr 11 2018 19:39:23 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Apr 11 2018 19:39:23 | Notice (6) | TLV-11 - unrecognized OID |
| Apr 11 2018 23:10:39 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 12 2018 16:58:33 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 12 2018 16:58:33 | Critical (3) | No Ranging Response received - T3 time-out |
| Apr 12 2018 16:58:53 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Apr 12 2018 16:58:53 | Critical (3) | No Ranging Response received - T3 time-out |
It's not showing now but at the time of the T3 time-out today around 5 pm my dBmV for upstream channels was pushing 51 again.
Here is an updated look at my downstream and upstream channels:
| Downstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
| Upstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Since the issue seems to persist (granted not as heavily as it was when I had power running on my coaxial for who-knows-what reason) I would like to ask if there is any further insight you could provide. If this is a chip issue as was stated by UnhappyCustomer1 is there nothing I can do while waiting for the patch on the issue? Also I cannot explain how the cable gets from the street to my particular apartment though I am right next to the street/cable lines and lines are usually run underground here, not 100% sure that's the case here but I think it is. Assuming the only splitter in my apartment was the one in the storage unit I no longer go through any splitters.
Please send us an email with your full address to cox.help@cox.com so we can help resolve this issue on you behalf.
Thanks,
Allan - Cox Support Forums Moderator.
I have submitted a confirmation email with my address. I'm not sure what else can be done at this point but I'll be completely honest. After $110 in technician charges I'm not very thrilled that the issue still persists and I'm not eager for another charge like that just to possibly face the same results.
During my first call I decided to get the complete care as I wasn't certain how bad this issue was going to be and figured it would be worth it. I see that I was still charged the full price on the second tech and would like to ask if the complete care doesn't cover anything until I've made my payment this month? If it's not going to help at all and I'll still be charged like that then you might as well remove it from my account as it's not what I thought it would be.
