Couple days we got a storm that was pretty bad. Others lost power, but we only got a few brown outs. Cox was down for a couple of days, which is fine in my book. Things break, need time to fix them. The problem started this morning, when looking at my signal levels I noticed the "Ranging Status" for upstream channel 3 said "failed, tries exce.." but the wording was cut off. It stayed this way for only a few seconds, and went back to the normal "Success". Other then that, signal levels are great. I started doing some tests, and noticed a slower than normal upload speed. Anywhere from 0.9Mbps to 3.2Mbs, when my normal is 5-6Mbps on Preferred.This was hardwired direct from laptop to modem. I noticed escalating T3 errors in my log. Signal levels in screenshot.
I called Cox and they see my Tx SNR was "in the green" but I couldn't confidently confirm that. That said they saw packet loss going to my modem. I scheduled a Technician and wondering what he might find. But where it got weird is when I noticed my modem status page. EVen though I am online and everything is fine (except for slow upload) my Cable modem status says I am offline. I did a normal power cycle, then a factory reset into a power cycle. The page doesn't change during the boot. Anyone see anything like that? Firmware glitch? Electrical damage?
Equipment: Motorola SB6141
Asus RT-N66U
Direct RG6 quad shield from modem, with a 10db pad, to outlet, outside to housebox with a single grounding block then straight to the tap.
Update:
UNO ticket opened 8/9 and problem looks to be fixed by PM of 8/10, so kudos to the South County maintenance team. Modem is still giving a false negative for the status, but that will be fixed when I soon upgrade to the SB6183. Firmware still seems to have a few kinks. Resolved.
Update 2:
UNO ticket still open and escalated. Oddity of not showing status fixed by having the modem powered down for 5+ min while I moved it to a new outlet. Now the status shows normal and internet connection is fine, levels good (even better) but Cox says they can't see the modem on their end. Maybe upstream packet loss causing problem with snmp? Maybe hardware malfunction still present. Still some very minor latency and performance loss on the upload, but well with reason and UNO ticket is still open so I am not worried.
Update 3:
Problem returned with a vengeance. Offline for a couple minuets, then modem in D2 only mode. 3rd channel was kicking out t3's leading into t4's. Directly connected to the modem, I was getting up to 14% packet loss to the first hop (CMTS?) and latency from 7ms to 100+ms with average of around 54ms. I noticed my upstream levels were moving from 42db to 54db without me changing anything. Called and re-escalated to tier 2, UNO ticket is still open in Data Ops queue. Tier 2 is esclating to field supervisor for ETR on UNO and general plan of action.
↧