Browser

update mdd timeout

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 113591.00 MHz9.80 dBmV40.37 dB256QAM4724269300
Downstream 29567.00 MHz10.30 dBmV40.37 dB256QAM3656323600
Downstream 310573.00 MHz10.20 dBmV40.37 dB256QAM3614040500
Downstream 411579.00 MHz9.90 dBmV40.37 dB256QAM3731813600
Downstream 519627.00 MHz9.00 dBmV40.37 dB256QAM3914701300
Downstream 620633.00 MHz9.00 dBmV40.37 dB256QAM4058307000
Downstream 721639.00 MHz8.70 dBmV40.37 dB256QAM4243216500
Downstream 824657.00 MHz8.40 dBmV40.37 dB256QAM4112893500
Downstream 925663.00 MHz8.50 dBmV40.37 dB256QAM4455846300
Downstream 1026669.00 MHz8.60 dBmV40.37 dB256QAM4018757000
Downstream 1127675.00 MHz8.50 dBmV40.37 dB256QAM4498159000
Downstream 1228681.00 MHz8.40 dBmV40.37 dB256QAM4016131000
Downstream 1329687.00 MHz8.10 dBmV40.95 dB256QAM4008381400
Downstream 1430693.00 MHz8.00 dBmV40.37 dB256QAM4366120600
Downstream 1531699.00 MHz8.10 dBmV40.37 dB256QAM4292408600
Downstream 1632705.00 MHz8.00 dBmV40.95 dB256QAM4106312300
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 16037.00 MHz45.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 25930.60 MHz44.50 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 35823.30 MHz42.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 45718.50 MHz41.75 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

Date TimeEvent IDEvent LevelDescription
9/8/2017 0:08840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 0:08840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 0:08840202005Lost MDD Timeout;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 0:08820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 2:17840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 6:57820002003No Ranging Response received - T3 time-out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 16:21840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 16:21840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 16:21840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 16:21840202005Lost MDD Timeout;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/8/2017 16:22820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 3:57840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 3:57840202005Lost MDD Timeout;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 3:57840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 3:57840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 3:57840202005Lost MDD Timeout;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 3:57820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 4:18840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 18:29820002003No Ranging Response received - T3 time-out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 19:51840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
3 REPLIES
Expert

Re: update mdd timeout

You have serious ingress from broadcast tv, something is corroded or loose or there's open/ too many splitter ports. Real problem is the Partial Service due to the interference.

 

Highlighted
Browser

Re: update mdd timeout

i did what you told me

 

9/9/2017 4:18840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 18:29820002003No Ranging Response received - T3 time-out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 19:51840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 22:22820002003No Ranging Response received - T3 time-out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 22:22840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/9/2017 22:22840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:03820002003No Ranging Response received - T3 time-out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840202005Lost MDD Timeout;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:04840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:05820002003No Ranging Response received - T3 time-out;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
9/10/2017 1:14840007005RCS Partial Service;CM-MAC=10:56:11:f9:d9:69;CMTS-MAC=00:01:5c:67:ce:71;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: update mdd timeout

are the correctables/ uncorrectables still increasing? If so, It's outside somewhere and TWC/ Spectrum needs to replace outside connectors/ grounding block for a start.