Observer

Uncorrected errors

My mom's connection has been misbehaving lately. I found what appears to be a great number of uncorrected errors in the modem log pasted below.  Any suggestions?

 

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 13693.00 MHz0.88 dBmV36.84 dB256QAM16096716492113115791
Downstream 212639.00 MHz1.10 dBmV36.39 dB256QAM4475450727174515193
Downstream 311645.00 MHz1.43 dBmV34.48 dB256QAM4446991573140415698
Downstream 410651.00 MHz1.40 dBmV36.61 dB256QAM4428526078125115776
Downstream 59657.00 MHz0.86 dBmV37.09 dB256QAM463726322114297237
Downstream 68663.00 MHz1.04 dBmV37.09 dB256QAM445805495014767206
Downstream 77669.00 MHz1.15 dBmV37.36 dB256QAM439840104912947229
Downstream 86675.00 MHz0.92 dBmV37.36 dB256QAM481939895311437447
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 13423.30 MHz51.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 23318.50 MHz----------------
Upstream 33530.60 MHz51.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 43637.00 MHz----------------

 

 Status
System Uptime:57 d: 19 h: 42 m
Computers Detected:staticCPE(1), dynamicCPE(1)
CM Status:Telephony-Reg Complete
Time and Date:Sun 2016-05-15 04:52:35

 

 Interface Parameters
Interface NameProvisionedStateSpeed (Mbps)MAC address
LAN Port 1EnabledDown-----E8:3E:FCSmiley Very Happy7:44:71
LAN Port 2EnabledDown-----E8:3E:FCSmiley Very Happy7:44:71
LAN Port 3EnabledDown-----E8:3E:FCSmiley Very Happy7:44:71
LAN Port 4EnabledDown-----E8:3E:FCSmiley Very Happy7:44:71
CABLEEnabledUp-----E8:3E:FCSmiley Very Happy7:44:72
MTAPassWithWarningsUp-----E8:3E:FCSmiley Very Happy7:44:73
4 REPLIES 4
Observer

Re: Uncorrected errors

And here is the Event Log:

 

 DOCSIS(CM) Events

 

Date TimeEvent IDEvent LevelDescription
5/13/2016 17:32820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/13/2016 17:33820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/13/2016 23:45820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/13/2016 23:46820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/13/2016 23:46820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/13/2016 23:46820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 0:17820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 0:17820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 4:01820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 4:01820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 4:01820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 4:01820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 4:01820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 4:02820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 17:26820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/14/2016 17:26820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/15/2016 1:00820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/15/2016 1:00820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/15/2016 1:44820002003No Ranging Response received - T3 time-out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
5/15/2016 1:44820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:3e:fc:d7:44:72;CMTS-MAC=00:01:5c:6d:c4:62;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: Uncorrected errors

looks like too manyy splitters or open ports, bad/loose cables or chewed up line

if everything is tight call TWC out. This cannot be fixed over the phone, needs a tech out

 Upstream is out of range on 2 channels and there's noise and broadcast tv ingress on the downstream channels

 

Observer

Re: Uncorrected errors

Thank you very much

Valued Contributor

Re: Uncorrected errors

I get worried about my uncorrectables then I see these threads...