Contributor

Error Spikes, not sure what's wrong.

I have been pretty religiously checking the modem interface pages since the new modem and Maxx rollout, and I'm noticing some pretty bad error spikes.  Here are some samples.    I noticed it while running with a splitter on for the extra Tx loss, so I removed the splitter but am still getting loads of errors.

 

 

 

 

 

 

 

 

 

 

You can see by the times that they're going up at a pretty steady rate.  And finally, the event log.

 

 

Time Priority Description

Time Not EstablishedWarning (5)ToD request sent - No Response received;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedNotice (6)TLV-11 - unrecognized OID;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedWarning (5)ToD request sent - No Response received;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedError (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedError (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedWarning (5)ToD request sent - No Response received;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.0;CM-VER=3.0;
Time Not EstablishedNotice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Wed May 18 14:24:26 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Wed May 18 14:24:22 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 14:24:22 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 14:24:18 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 14:24:18 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 14:24:08 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 14:24:08 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 14:23:57 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:41:50 2016Critical (3)No Ranging Response received - T3 time-out
Wed May 18 02:41:41 2016Critical (3)TFTP Request Retries exceeded, CM unable to register
Wed May 18 02:41:41 2016Critical (3)TFTP failed - Request sent - No Response;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.0;CM-VER=3.0;
Wed May 18 02:40:55 2016Critical (3)No Ranging Response received - T3 time-out
Wed May 18 02:37:52 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Wed May 18 02:37:48 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:37:48 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:37:44 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:37:44 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:37:40 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:37:40 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:37:39 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:37:38 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:37:33 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Wed May 18 02:37:26 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Tue May 17 00:11:52 2016Critical (3)No Ranging Response received - T3 time-out
Mon May 16 22:18:26 2016Critical (3)No Ranging Response received - T3 time-out
Mon May 16 22:16:22 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Mon May 16 22:16:19 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:16:19 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:16:01 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:16:00 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:15:59 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:15:59 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:15:47 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:15:47 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:15:46 2016Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:15:46 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:15:40 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 22:15:34 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.1;CM-VER=3.0;
Mon May 16 21:21:43 2016Critical (3)No Ranging Response received - T3 time-out
Mon May 16 21:10:40 2016Critical (3)No Ranging Response received - T3 time-out
Mon May 16 20:19:37 2016Critical (3)No Ranging Response received - T3 time-out
Mon May 16 20:19:23 2016Critical (3)No Ranging Response received - T3 time-out
Mon May 16 20:19:16 2016Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.0;CM-VER=3.0;
Mon May 16 20:19:07 2016Critical (3)TFTP Request Retries exceeded, CM unable to register
Mon May 16 20:19:07 2016Critical (3)TFTP failed - Request sent - No Response;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:01:5c:77:64:47;CM-QOS=1.0;CM-VER=3.0;
Mon May 16 20:18:21 2016Critical (3)No Ranging Response received - T3 time-out
Mon May 16 02:40:22 2016Critical (3)No Ranging Response received - T3 time-out
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:ec:aa:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

 

 

What could be the issue here, TWC?

 

7 REPLIES 7
Lead Moderator

Re: Error Spikes, not sure what's wrong.

I would suggest contacting us directly to get a technician visit scheduled.

 

We can be reached directly at TWC_ForumsHelp  Please do include your 

account number, verification of your service address, and best contact number. 

 

Regards,
Julia R.
TWC-Social Media Customer Care
Moderator - TWC Community Forums

Highlighted
Expert

Re: Error Spikes, not sure what's wrong.

I don't think there's been a problem since wed per the log

 

Corrected/ uncorrecteds are increasing but not at an alarming rate, good luck getting twc to reduce them

 

 

Contributor

Re: Error Spikes, not sure what's wrong.

I read on another thread at some point that uncorrecteds should never be higher than correcteds.  I'm wondering if the spikes just happen no matter what, because I've already had two techs out and if there was some real issue, I would think they would have caught it.  Unless, they just don't like rerunning drop lines, or changing fixtures.  That's if it's even an issue on my premises.  I don't remember seeing them that high, before they put the filter on at the tap.  However, I had been resetting the modem a lot, because I was playing around with a couple different routers.

Expert

Re: Error Spikes, not sure what's wrong.

My modem/routers are on a ups however the outside plant loses power, every time it does, i get 500-600 uncorrecteds

Here's what I have on 31 days of up time

Downstream Bonding Channel Value
Channel ID10 11 12 
Frequency681000000 Hz 687000000 Hz 693000000 Hz 699000000 Hz 705000000 Hz 711000000 Hz 717000000 Hz 723000000 Hz 
Signal to Noise Ratio35 dB 35 dB 35 dB 35 dB 36 dB 36 dB 36 dB 36 dB 
Downstream ModulationQAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
-2 dBmV  -3 dBmV  -3 dBmV  -2 dBmV  -2 dBmV  -2 dBmV  -1 dBmV  -1 dBmV  

 

Upstream Bonding Channel Value
Channel ID34 33 35 36 
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID8495 8495 8495 8495 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level46 dBmV 44 dBmV 47 dBmV 48 dBmV 
Upstream Modulation[3] QPSK
[3] 16QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[3] 16QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID10 11 12 
Total Unerrored Codewords124269875455 124269881719 124269879558 124269881892 124269841619 124269833075 124269883182 124269877976 
Total Correctable Codewords5691 5437 5805 6935 5803 5338 6033 6795 
Total Uncorrectable Codewords22463 20890 24366 24986 22529 23470 22881 23296 

 

 


 

 

Status | Signal | Addresses | Configuration | Logs | Open Source | Help

 

Contributor

Re: Error Spikes, not sure what's wrong.

Seems to be what's happening here too.  

 

this time, just a slight jump in correcteds, uncorrecteds look the same.

 

ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1LockedQAM2561591000000 Hz5.7 dBmV42.4 dB19083983
2LockedQAM2562597000000 Hz6.1 dBmV42.4 dB20274313
3LockedQAM2563603000000 Hz6.2 dBmV42.4 dB20064721
4LockedQAM2564609000000 Hz6.1 dBmV42.0 dB21544908
5LockedQAM2565615000000 Hz6.3 dBmV41.8 dB21084204
6LockedQAM2566621000000 Hz6.5 dBmV41.8 dB21374351
7LockedQAM2567627000000 Hz6.4 dBmV41.5 dB23944413
8LockedQAM2568633000000 Hz6.4 dBmV41.4 dB21004397
9LockedQAM2569639000000 Hz6.4 dBmV41.5 dB24034516
10LockedQAM25610645000000 Hz6.6 dBmV41.7 dB20634221
11LockedQAM25611651000000 Hz6.7 dBmV41.7 dB21104348
12LockedQAM25612657000000 Hz6.9 dBmV41.2 dB21654191
13LockedQAM25613663000000 Hz6.7 dBmV41.5 dB22404525
14LockedQAM25614669000000 Hz6.8 dBmV41.6 dB21564484
15LockedQAM25615675000000 Hz7.1 dBmV41.8 dB20264397
16LockedQAM25616681000000 Hz6.9 dBmV41.9 dB21684361

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA115120 Ksym/sec30600000 Hz39.0 dBmV
2LockedTDMA92560 Ksym/sec19400000 Hz37.0 dBmV
3LockedATDMA105120 Ksym/sec24200000 Hz38.3 dBmV
4LockedATDMA122560 Ksym/sec37000000 Hz40.0 dBmV


 

Current System Time: Mon May 23 20:16:10 2016

 

Expert

Re: Error Spikes, not sure what's wrong.

I think the 6141 I have limits the unerrored byte totals to 12 digits....

 

 

Correcteds aren't bad in low number increases a day, they are renegotiated bytes between your modem and the CMTS, but if the retry also fails parity check, it now becomes uncorrected and your computer has to renegotiate all the way back to the server you were getting the bytes from for a resend and that drives up ping time and screws up gaming as that can take 300ms

 

Contributor

Re: Error Spikes, not sure what's wrong.

Thanks for the layman's explanation.  I've been wondering about what those particular stats actually meant.