Community Forum

Non-Stop RCS Partial Service/Lost MDD Timeout Errors

Highlighted
New Poster

Non-Stop RCS Partial Service/Lost MDD Timeout Errors

I'm getting to the end of my rope with the tech service support I have so far received. I have intermittent service drops and modem resets. After being told the issue was my previous Arris SB6141, I went out and bought a new Arris SB6190. Still having the same issues. So I called back to then try and schedule a service tech. After a couple of hours of holding, explaining, re-explaining, and being patient I finally had a service ticket open. So this morning the tech showed up and he replaced some connectors, reinstalled a ground wire, and replaced the jack in the wall. After that my internet was even slower! I was getting 3mb down and .5mb up. He then told me that another ticket was created and said I might hear something in a week. So after a couple more hard resets, I was able to get my internet speeds back to normal. But this evening, another modem reset. This is unacceptable, I am a fulltime student and desperately need the internet to perform all of my online classes.  

 

Wed Oct 28 20:40:58 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:41:15 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:41:16 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:42:07 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:42:12 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:42:18 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:42:37 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:42:47 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:42:49 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:43:17 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:43:18 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:44:06 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:44:07 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:44:29 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:44:43 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:45:20 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:45:20 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:45:31 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:45:31 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Wed Oct 28 20:45:58 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;

 

What is the most frustrating is, I do know enough to look into the error logs for both my modem and my router. Looking through these specifically on the modem, I can see that every 15 seconds I am receiving RCS Partial Service/Lost MDD Timeout errors. So I obviously brought this up to everyone I have spoken to and it has blatantly ignored.  Prior to today, I was also regularly receiving TLV-11, T3 Timeout, and T4 Timeout errors as well. 

 

 

 

 

 

Highlighted
New Poster

Re: Non-Stop RCS Partial Service/Lost MDD Timeout Errors

 

ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM16531.00 MHz-12.10 dBmV36.61 dB822112100995
2Locked256QAM4453.00 MHz-13.10 dBmV35.60 dB1066268605402
3Locked256QAM5459.00 MHz-12.10 dBmV37.64 dB865777104406
4Locked256QAM6465.00 MHz-11.80 dBmV37.64 dB997783175325
5Locked256QAM7471.00 MHz-11.40 dBmV36.61 dB66911680244
6Not Locked----8477.00 MHz----------------
7Not Locked----9483.00 MHz----------------
8Locked256QAM10489.00 MHz-10.30 dBmV37.36 dB48373568324
9Locked256QAM11495.00 MHz-9.60 dBmV38.61 dB82921872185
10Locked256QAM12507.00 MHz-9.50 dBmV37.36 dB27047150404
11Locked256QAM13513.00 MHz-10.70 dBmV37.36 dB40318855693
12Locked256QAM14519.00 MHz-10.10 dBmV37.64 dB41852053841
13Locked256QAM15525.00 MHz-10.20 dBmV37.64 dB50337160060
14Locked256QAM17537.00 MHz-13.80 dBmV36.39 dB1103762136556
15Locked256QAM18543.00 MHz-12.30 dBmV36.61 dB1012331177950
16Locked256QAM19549.00 MHz-8.90 dBmV37.64 dB756066107764
17Not Locked----20555.00 MHz----------------
18Locked256QAM21561.00 MHz-9.60 dBmV35.08 dB45849548911
19Locked256QAM22567.00 MHz-10.70 dBmV35.60 dB26971136096
20Locked256QAM23573.00 MHz-10.40 dBmV29.44 dB34616401609328
21Not Locked----24579.00 MHz----------------
22Not Locked----25585.00 MHz----------------
23Not Locked----26591.00 MHz----------------
24Locked256QAM27597.00 MHz-13.90 dBmV28.75 dB174271904625745
25Not Locked----28603.00 MHz----------------
26Locked256QAM29609.00 MHz-10.80 dBmV30.00 dB1275547338
27Locked256QAM30615.00 MHz-10.60 dBmV38.20 dB613115251
28Locked256QAM31621.00 MHz-11.50 dBmV36.60 dB1209647432
29Locked256QAM32627.00 MHz-11.60 dBmV35.50 dB47756918200
30Locked256QAM33633.00 MHz-13.50 dBmV33.00 dB12587814202
31Locked256QAM34639.00 MHz-17.50 dBmV33.10 dB12224821762
32Locked256QAM35645.00 MHz-16.70 dBmV34.30 dB11689010023
Highlighted
Expert

Re: Non-Stop RCS Partial Service/Lost MDD Timeout Errors

The downstream power is too low / out of spec. Please also post the upstream power level numbers.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
New Poster

Re: Non-Stop RCS Partial Service/Lost MDD Timeout Errors

 

ProcedureStatusComment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK 
SecurityEnabledBPI+
DOCSIS Network Access EnabledAllowed 

 

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM16531.00 MHz4.00 dBmV38.98 dB36379581568249
2Locked256QAM4453.00 MHz3.40 dBmV40.37 dB41120643067024
3Locked256QAM5459.00 MHz3.50 dBmV38.98 dB38088281517841
4Locked256QAM6465.00 MHz3.70 dBmV38.98 dB38206381900246
5Locked256QAM7471.00 MHz3.90 dBmV38.98 dB33963571193014
6Locked256QAM8477.00 MHz3.90 dBmV31.62 dB512750262589994
7Locked256QAM9483.00 MHz3.90 dBmV35.60 dB52047366261740
8Locked256QAM10489.00 MHz3.80 dBmV38.61 dB3058317884565
9Locked256QAM11495.00 MHz3.90 dBmV38.98 dB37639701315077
10Locked256QAM12507.00 MHz4.20 dBmV40.37 dB2392524674993
11Locked256QAM13513.00 MHz4.10 dBmV38.98 dB2753346859527
12Locked256QAM14519.00 MHz4.20 dBmV40.37 dB2805962842205
13Locked256QAM15525.00 MHz3.90 dBmV40.37 dB3054687955548
14Locked256QAM17537.00 MHz3.30 dBmV38.61 dB41706572084076
15Locked256QAM18543.00 MHz2.30 dBmV38.98 dB39463932026362
16Locked256QAM19549.00 MHz2.90 dBmV38.61 dB34419951232956
17Locked256QAM20555.00 MHz3.20 dBmV34.93 dB17782028341260080
18Locked256QAM21561.00 MHz2.50 dBmV37.64 dB2697505614214
19Locked256QAM22567.00 MHz3.10 dBmV38.61 dB2316766606702
20Locked256QAM23573.00 MHz3.30 dBmV36.39 dB64656143832708
21Locked256QAM24579.00 MHz2.60 dBmV35.60 dB118940492164620
22Locked256QAM25585.00 MHz3.20 dBmV33.49 dB6627293408743
23Locked256QAM26591.00 MHz2.50 dBmV33.83 dB9429084117242897
24Locked256QAM27597.00 MHz0.70 dBmV36.39 dB215388639081350
25Locked256QAM28603.00 MHz1.60 dBmV35.70 dB7033462274067
26Locked256QAM29609.00 MHz1.90 dBmV35.90 dB216258144364
27Locked256QAM30615.00 MHz0.50 dBmV39.20 dB15017817142
28Locked256QAM31621.00 MHz1.40 dBmV38.60 dB25962520509
29Locked256QAM32627.00 MHz1.90 dBmV38.60 dB83262352014
30Locked256QAM33633.00 MHz1.20 dBmV38.60 dB41728084979
31Locked256QAM34639.00 MHz1.70 dBmV38.60 dB30528193519
32Locked256QAM35645.00 MHz1.10 dBmV38.20 dB38879568757

 

Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA255120 kSym/s36.50 MHz38.75 dBmV
2LockedATDMA285120 kSym/s17.30 MHz39.50 dBmV
3LockedATDMA275120 kSym/s23.70 MHz39.00 dBmV
4LockedATDMA265120 kSym/s30.10 MHz39.75 dBmV
Highlighted
New Poster

Re: Non-Stop RCS Partial Service/Lost MDD Timeout Errors

 

 

Time Priority Description

Thu Oct 29 01:25:59 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:26:03 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:26:09 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:26:11 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:26:33 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:26:33 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:26:45 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:26:46 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:27:49 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:28:09 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:41:55 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:43:26 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:44:21 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:44:36 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:44:59 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 01:49:41 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 11:25:53 20203No Ranging Response received - T3 time-out;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 17:05:52 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 17:06:55 20205RCS Partial Service;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;
Thu Oct 29 17:06:58 20205Lost MDD Timeout;CM-MAC=40:4c:77:00:12:a9;CMTS-MAC=00:01:5c:63:c6:55;CM-QOS=1.1;CM-VER=3.0;