Spectator

Was hoping to get some advice.

I was going through my modem's log on Sunday and started to notice abnormal amounts of correctable and uncorrectables. So I started to look at the event log and saw I started to receive RCS Partial Service throughout the day and has been continuing since then. I hadn't happened to encounter any issues myself, but I usually only get that error along with the SYNC timing synchronization failure when they are working in the area or going to need to do so. I did a reboot yesterday to get some fresh numbers. There seems to be some periods where there isn't an issuse at all, but oddly enough when I use the internet for anyhing the correcatbles and uncorrectable seems to be stable, but when idle they run rampant Figured I'd give it a few days since I'm not going to be around the house much. Any advice on what I should do if it doesn't change would be appreciated.

 

RF Parameters

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 116645.00 MHz-4.40 dBmV40.37 dB256QAM6045781461195212681
Downstream 22561.00 MHz-3.60 dBmV40.37 dB256QAM955117131455328409
Downstream 33567.00 MHz-3.60 dBmV40.95 dB256QAM974545051387723680
Downstream 44573.00 MHz-4.00 dBmV40.37 dB256QAM1007140171423624173
Downstream 55579.00 MHz-4.10 dBmV40.37 dB256QAM954306961421123527
Downstream 66585.00 MHz-3.90 dBmV40.37 dB256QAM934531201346920236
Downstream 77591.00 MHz-3.90 dBmV40.37 dB256QAM951840781243114313
Downstream 88597.00 MHz-3.90 dBmV40.95 dB256QAM985381041241012703
Downstream 99603.00 MHz-4.20 dBmV40.95 dB256QAM94234583119079698
Downstream 1010609.00 MHz-4.30 dBmV40.37 dB256QAM97907665113828362
Downstream 1111615.00 MHz-4.60 dBmV40.95 dB256QAM96002065114908705
Downstream 1212621.00 MHz-4.20 dBmV40.95 dB256QAM94413569110748557
Downstream 1313627.00 MHz-4.30 dBmV40.37 dB256QAM95324856110077613
Downstream 1414633.00 MHz-4.30 dBmV40.37 dB256QAM961525341123911404
Downstream 1515639.00 MHz-4.30 dBmV40.37 dB256QAM953674981134210562
Downstream 161555.00 MHz-3.40 dBmV40.95 dB256QAM946000781524834413
Downstream 1717651.00 MHz-4.50 dBmV40.37 dB256QAM1032931691093711849
Downstream 1818657.00 MHz-4.40 dBmV40.37 dB256QAM1020776911137712186
Downstream 1919663.00 MHz-4.20 dBmV40.37 dB256QAM104212020102649533
Downstream 2020669.00 MHz-4.40 dBmV40.95 dB256QAM993989819915

8529

 

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1330.60 MHz46.50 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 2437.00 MHz45.75 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 3119.40 MHz46.75 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM
Upstream 4224.20 MHz45.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM

 

DOCSIS(CM) Events

 

Date TimeEvent IDEvent LevelDescription
3/18/2018 3:08820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/18/2018 11:19840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/18/2018 13:13820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/18/2018 16:46840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/18/2018 18:01820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/18/2018 18:23840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/18/2018 22:37840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/18/2018 22:46840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/19/2018 2:53820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/19/2018 12:33840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/19/2018 17:19730402003TLV-11 - Illegal Set operation failed;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/19/2018 17:32840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/19/2018 18:33820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/19/2018 18:46840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/20/2018 5:52820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/20/2018 6:30840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/20/2018 7:54820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/20/2018 8:21840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/20/2018 8:46820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/20/2018 8:52840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
7 REPLIES 7
Trusted Helper

Re: Was hoping to get some advice.

My view,

 

If you are not noticing an Internet speed decrease or drop in signals regularly, I wouldn't worry about the numbers too much.  Same would be true with slight fluctuations.  Can you do online what you need to do reliably and fast concerning your Internet connection?  That's the main issue.

 

If you are noticing consistent slowdowns or loss of Internet signals on a regular basis, contact Spectrum for a signal and drop line test.  If you do that, what's most important is to try not to reset your cable boxes, modems, or routers for at least six hours prior to your service appointment.  Equipment resets reset the signal error codes and the tech needs to see those.

 

Do you own your own modem/router or rent one from Spectrum?  How long have you had your modem/router?

 

Satch

 

 

Spectator

Re: Was hoping to get some advice.

Since i noticed the log on Sunday I haven't experienced any sort of issues during the time I used it.  I tend to check my modem's info every few days and just shocked at the numbers at the time.  Usually in a month I would get maybe 100 correctables only. The log was from a reboot 17 hours before the post and since then it's been rather clam in increments compared to the last two days where it would  fluctuate like crazy during the early to mid afternoon.

 

Also as a side note I can't be fore certain, but I think I've gain 4 more downstream channels then I had. Pretty sure I was always 16x4, It's one of those things I can never figure out if thier working in the ara or not by calling them up. I remember when they did something with the line and I had only two upsteam channels for a few days and they said it was perfectly fine on their end for about 4 days.

 

I'll keep that in mind in case  I start having issues.

 

I rent one from them it's a Arris TM1602 about two weeks short of a year having it.

 

 

Lead Moderator

Re: Was hoping to get some advice.

If you do find that the problem has been resolved please come back to the forums

and mark this solved.

 

Hope you are having a great day! 

 

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

Highlighted
Proven Sharer

Re: Was hoping to get some advice.

The RCS Partial Service message means that your modem lost signal on one or more of the downlink channels that it is programmed to receive.  Since your local system recently added four new channels this may resolve the reported error.  If you do see the RCS Partial Service message again, please get in touch with Julia_R, who is monitoring your case. 

Spectator

Re: Was hoping to get some advice.

@Julia_R

 

It's been all over the place all week. On Tuesday when I made the post I saw bucket truck working in the area after two hours of seeing it The problems seems to have gone away till Friday where it got really bad all day. That even after midnight it seemed to have been fixed until Sunday's early hours.  It's been the worst today. Saw another bucket truck one block down last night, but they didn't seem to do anything. I've called Spectrum a few times to see if there was any outage, but that doesn't seem to the case and they couldn't let me know if they was any working being done in the area.

 

At this rate it may be best when I have an opportunity to call them up and schedule an appointment for a tech.

 

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 116645.00 MHz-5.80 dBmV40.37 dB256QAM55858057192424855649
Downstream 22561.00 MHz-4.80 dBmV40.37 dB256QAM96502348732527100477
Downstream 33567.00 MHz-4.80 dBmV40.37 dB256QAM95530073134958112341
Downstream 44573.00 MHz-5.20 dBmV38.98 dB256QAM95006774132899101640
Downstream 55579.00 MHz-5.40 dBmV40.37 dB256QAM94756201133216101293
Downstream 66585.00 MHz-5.10 dBmV40.37 dB256QAM9270568833041581930
Downstream 77591.00 MHz-5.10 dBmV40.95 dB256QAM9655997342687164275
Downstream 88597.00 MHz-5.10 dBmV40.37 dB256QAM9774881402620859645
Downstream 99603.00 MHz-5.30 dBmV40.37 dB256QAM9489369102397742280
Downstream 1010609.00 MHz-5.50 dBmV40.37 dB256QAM9591912762374140643
Downstream 1111615.00 MHz-5.80 dBmV38.98 dB256QAM9567221622414344463
Downstream 1212621.00 MHz-5.40 dBmV40.37 dB256QAM9655106902208940337
Downstream 1313627.00 MHz-5.60 dBmV38.98 dB256QAM9543521512229636198
Downstream 1414633.00 MHz-5.60 dBmV38.98 dB256QAM9674512892357745196
Downstream 1515639.00 MHz-5.70 dBmV38.98 dB256QAM9421462372465748443
Downstream 161555.00 MHz-4.60 dBmV40.95 dB256QAM97094299433963106200
Downstream 1717651.00 MHz-5.90 dBmV38.98 dB256QAM10874582322366150622
Downstream 1818657.00 MHz-5.80 dBmV38.98 dB256QAM11456471252441449003
Downstream 1919663.00 MHz-5.50 dBmV38.98 dB256QAM11691392702268855711
Downstream 2020669.00 MHz-5.40 dBmV40.37 dB256QAM11348233742236244902
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1330.60 MHz47.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 2437.00 MHz47.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 3119.40 MHz47.25 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM
Upstream 4224.20 MHz47.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM

 

Date TimeEvent IDEvent LevelDescription
3/24/2018 4:39820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 2:36840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 3:30820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 3:42840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 7:35820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 10:15840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 11:06820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 12:18840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 12:39840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 12:47840005003SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 13:07820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 13:19840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 13:37820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 13:38840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 14:08820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 14:29840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 15:20820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 15:20840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 15:55820002003No Ranging Response received - T3 time-out;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
3/25/2018 16:56840007005RCS Partial Service;CM-MAC=a8:11:fc:49:30:ef;CMTS-MAC=00:17:10:8b:8e:06;CM-QOS=1.1;CM-VER=3.0;
Proven Sharer

Re: Was hoping to get some advice.


@javiowrote:

How would I go about contacting her? Or is this post enough?

 

It's been all over the place all week. On Tuesday when I made the post I saw bucket truck working in the area after two hours of seeing it The problems seems to have gone away till Friday where it got really bad all day. That even after midnight it seemed to have been fixed until Sunday's early hours.  It's been the worst today. Saw another bucket truck one block down last night, but they didn't seem to do anything. I've called Spectrum a few times to see if there was any outage, but that doesn't seem to the case and they couldn't let me know if they was any working being done in the area.

 

At this rate it may be best when I have an opportunity to call them up and schedule an appointment for a tech.


Just put @Julia_R in the body of your reply message and she will be alerted.  Also I suggest you again paste in the signal levels page so she can compare to your previous complaint.

Lead Moderator

Re: Was hoping to get some advice.

Hi again!

 

Looking at those logs we need to get someone out to further investigate.

 

We should not be seeing these errors. You can contact us directly to 

schedule an appointment.  

 

Forums_Help

 

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