Participant

Help with previous post on connectivity.

[ Edited ]

It will not let me continue or reply on my original post. So trying with a new one. Posted link below to it.

http://forums.timewarnercable.com/t5/Connectivity/Help-and-advice-with-repeated-loss-of-connectivity...

As per intermittent  issues on that post, I have another tech visit (suppose to be a senior tech this time that knows stuff) scheduled for tomorrow and am still in need of assistance for issue occuring for about a month now. Trying to get it fixed, owner owned modem and router, so I'm assuming you will understand exactly why I now have new ones. Per phone calls to Spectrum/TWC my area had 2 reported outages over the weekend, I wondered if they were working on something on their end because when new modem first hooked up it had the same issues as the old one with lost mdd timeout errors and rcs partial service errors, but is better now and although issues have improved some I still had a disconnect that corresponded with a RCS partial service event in logs. on 7/9. 

In attempts to get rid of anything to blame on my end, I have also run a temp new cable directly from the outside cable to a new two way splitter, one out to tv, one out to cable box., and checked all connections.

Wondering if I'm still having issues with the number of correctable and uncorrectables.

Do you all see anything below that I need to address with the tech tomorrow? And thank you for your assistance.

New modem, has been up for 2 days

Arris SB6190, version 9.1.93N, provisioned correctly by Spectrum/TWC according to them.

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

 

 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM24807.00 MHz1.20 dBmV40.37 dB6895229
2Locked256QAM9717.00 MHz2.00 dBmV40.37 dB1226120222
3Locked256QAM10723.00 MHz1.80 dBmV40.95 dB1277216161
4Locked256QAM11729.00 MHz1.90 dBmV40.37 dB1378518839
5Locked256QAM12735.00 MHz2.00 dBmV38.98 dB2141715759
6Locked256QAM13741.00 MHz1.90 dBmV38.98 dB2230715564
7Locked256QAM14747.00 MHz1.40 dBmV38.98 dB3042012011
8Locked256QAM15753.00 MHz1.40 dBmV38.98 dB264579782
9Locked256QAM16759.00 MHz0.80 dBmV40.37 dB212838781
10Locked256QAM17765.00 MHz1.40 dBmV38.98 dB171184464
11Locked256QAM18771.00 MHz1.50 dBmV40.37 dB145343272
12Locked256QAM19777.00 MHz1.50 dBmV38.98 dB1905632951
13Locked256QAM20783.00 MHz1.30 dBmV38.98 dB2853121441
14Locked256QAM21789.00 MHz1.00 dBmV38.61 dB275132040
15Locked256QAM22795.00 MHz0.40 dBmV38.98 dB26248662
16Locked256QAM23801.00 MHz0.90 dBmV38.98 dB13913369

 

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA265120 kSym/s24.20 MHz48.50 dBmV
2LockedATDMA282560 kSym/s37.00 MHz47.50 dBmV
3LockedATDMA275120 kSym/s30.60 MHz47.75 dBmV
4LockedTDMA252560 kSym/s19.40 MHz48.00 dBmV



 

Current System Time: Mon Jul 10 11:09:32 2017

Sat Jul 08 06:35:15 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 09 05:54:42 20173No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 09 13:44:34 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
5 REPLIES
Highlighted
Expert

Re: Help with previous post on connectivity.

[ Edited ]

those numbers are really bad, problem is outside somewhere....

you are having serious ingress issues from your and others 4G LTE phone handsets, the carriers cell sites and LMR radio/data systems. Something is corroded, loose or chewed up.

 

 

Participant

Re: Help with previous post on connectivity.

[ Edited ]

Tech out found some issues representing problems with noise at the pole. Said everything to house is new and no issues, and that the issue is definately on Spectrum/TWC side, escalating the issue.

Another tech same day, looking for problems on lines. The next two days I have noticed them working on lines here and there close to the house service out for short periods of time but I am still having some of the same issues.

Will keep posted as I do not think this has yet been resolved, just giving them some time to work on it.

 

Expert

.Re: Help with previous post on connectivity.

[ Edited ]

copy and paste the new sgnal level page, let's see what they changed9i

Participant

Re: .Re: Help with previous post on connectivity.

Modem up for 2 days and 6 hours.

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

 

 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM24807.00 MHz0.60 dBmV38.61 dB267322344
2Locked256QAM9717.00 MHz1.50 dBmV38.98 dB211826268
3Locked256QAM10723.00 MHz1.60 dBmV38.98 dB192723007
4Locked256QAM11729.00 MHz1.30 dBmV38.98 dB209824136
5Locked256QAM12735.00 MHz1.10 dBmV38.61 dB208726354
6Locked256QAM13741.00 MHz0.90 dBmV38.61 dB223415817
7Locked256QAM14747.00 MHz0.40 dBmV38.61 dB228726313
8Locked256QAM15753.00 MHz0.50 dBmV38.98 dB199218666
9Locked256QAM16759.00 MHz0.50 dBmV38.98 dB297117972
10Locked256QAM17765.00 MHz0.80 dBmV38.98 dB226819148
11Locked256QAM18771.00 MHz0.80 dBmV38.61 dB202216797
12Locked256QAM19777.00 MHz0.60 dBmV38.98 dB30692185551
13Locked256QAM20783.00 MHz0.10 dBmV38.61 dB67730351926
14Locked256QAM21789.00 MHz-0.20 dBmV38.61 dB243221045
15Locked256QAM22795.00 MHz-0.30 dBmV38.61 dB320619873
16Locked256QAM23801.00 MHz0.10 dBmV38.98 dB250018098

 

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA265120 kSym/s24.20 MHz47.25 dBmV
2LockedATDMA282560 kSym/s37.00 MHz45.75 dBmV
3LockedATDMA275120 kSym/s30.60 MHz46.25 dBmV
4LockedTDMA252560 kSym/s19.40 MHz47.00 dBmV



 

Current System Time: Thu Jul 13 21:13:02 2017

Time Priority Description

Wed Jul 12 15:00:44 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:00:44 20173SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:00:49 20175Lost MDD Timeout;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:00:55 20173Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:19:29 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:19:29 20173SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:19:29 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:19:29 20173SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:19:40 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:19:40 20173SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:19:40 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:19:40 20173SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:23:51 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:23:51 20173SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:23:51 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:23:51 20173SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:23:56 20175Lost MDD Timeout;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 12 15:24:05 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 13 02:36:55 20173No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 13 08:30:29 20175RCS Partial Service;CM-MAC=5c:e3:0e:3d:27:93;CMTS-MAC=00:01:5c:8f:40:55;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: .Re: Help with previous post on connectivity.

[ Edited ]

It's way worst, you should never have more uncorrecteds than correcteds. Those are totally failed packets and hold up the next packet for the ping and reply time all the way back to the originating server

 Signal levels look the same though, they haven't tweaked any amplifiers to/from the fiber.

 the s/n is 1.5 dB worst, supposedly not enough to make a difference. Wonder if it's a lot hotter or colder than the previous readings.....