Menu
Reply
  • 18
  • 1
  • 1
cpugenesis
On our wavelength
664 Views
Message 1 of 9
Flag for a moderator

SH3 Internet Connection Drops Packet Loss

Hi Guys,

 

Hope someone is able to help with our connection,

 

Having issue with it being unstable and briefly disconnecting every day.  Noticed it shortly after the SH2AC to SH3 swap.

* Upgraded from SH2AC a few months ago (which had been fine for years)

* Had tech out several weeks ago who confirmed we had full signal, and saw no issues, but swapped the SH3 for a new SH3 (like for like).

 

Issues seem to persist in both router mode and modem mode (connected to a separate router).

 

 

NETGEAR > VM HUB 3  modem mode

 

 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/83febfabef00cb80f3088e557f982e9854...

 

 

 

 

 17.png18th.png19th.png20th.png

 

0 Kudos
Reply
  • 18
  • 1
  • 1
cpugenesis
On our wavelength
656 Views
Message 2 of 9
Flag for a moderator

Re: SH3 Internet Connection Drops Packet Loss

20/10/2018 11:15 stats

 

stats1.pngstats2.pngstats3.png


General Configuration
Network access Allowed
Maximum Number of CPEs 1
Baseline Privacy Enabled
DOCSIS Mode Docsis30
Config file V0dea97109ea7aa00.cm

Primary Downstream Service Flow
SFID 140209
Max Traffic Rate 230000000
Max Traffic Burst 42600
Min Traffic Rate 0

Primary Upstream Service Flow
SFID 140208
Max Traffic Rate 12700000
Max Traffic Burst 16320
Min Traffic Rate 0
Max Concatenated Burst 16320
Scheduling Type BestEffort


Time Priority Description
2018-10-20 10:12:39.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:39.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:39.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:40.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:41.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:42.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:42.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:42.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:46.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:46.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:48.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:48.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:49.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:50.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:51.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:51.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:52.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:52.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:57.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;
2018-10-20 10:12:57.00 Warning! RCS Partial Service;CM-MAC=48::d3*****:13;CMTS-MAC=00:01:*****:5b;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply
  • 11.7K
  • 347
  • 678
Forum Team (Retired) Samantha_L
Forum Team (Retired)
593 Views
Message 3 of 9
Flag for a moderator

Re: SH3 Internet Connection Drops Packet Loss

Hi cpugenesis,

 

Thanks for posting on the community.

 

My apologies you are having an issue with the broadband connection.

 

Looking at your account, the line and hub have come back as fine with no errors. The network segment is running stable and there have been no time-outs reported.

 

With your BQM graph, which I assume is live, is looking much better from today. Has anything changed at all?

 

Regards

Sam


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
  • 18
  • 1
  • 1
cpugenesis
On our wavelength
584 Views
Message 4 of 9
Flag for a moderator

Re: SH3 Internet Connection Drops Packet Loss

Thanks, it is a bit of a weird one - That's right the link is to a live graph, although I do have snapshots of daily graphs.

Looking at the daily graph now we seem to have had 1 drop off at mid day and 1 just after 6pm,  Modem shows 17:20 SYNC Timing Synchronization failure.

 

0 Kudos
Reply
  • 18
  • 1
  • 1
cpugenesis
On our wavelength
567 Views
Message 5 of 9
Flag for a moderator

Re: SH3 Internet Connection Drops Packet Loss

 

More examples and logs

2018-10-24 21:00:47.00 SYNC Timing Synchronization failure - Loss of Sync

2018-10-24 21:08:10.00 SYNC Timing Synchronization failure - Loss of Sync

2018-10-24 21:13:59.00 SYNC Timing Synchronization failure - Loss of Sync

2018-10-24 21:14:10.00 SYNC Timing Synchronization failure - Loss of Sync

2018-10-24 23:56:56.00 No Ranging Response received - T3 time-out

2018-10-25 01:44:32.00 RCS Partial Service;

2018-10-25 02:37:59.00 SYNC Timing Synchronization failure - Loss of Sync

2018-10-25 02:38:00.00 RCS Partial Service

2018-10-25 02:45:54.00 SYNC Timing Synchronization failure - Loss of Sync;

2018-10-25 02:45:54.00 RCS Partial Service

2018-10-25 02:52:33.00 SYNC Timing Synchronization failure - Loss of Sync;

2018-10-25 02:52:33.00 RCS Partial Service;

2018-10-25 03:22:35.00 SYNC Timing Synchronization failure 

2018-10-25 03:22:36.00 RCS Partial Service;

2018-10-25 08:06:17.00 SYNC Timing Synchronization failure - Loss of Sync

2018-10-25 08:06:17.00 RCS Partial Service;

 

 

BBQM Overall.jpg

0 Kudos
Reply
  • 10.87K
  • 406
  • 1.24K
Forum Team (Retired) Nicola_C
Forum Team (Retired)
534 Views
Message 6 of 9
Flag for a moderator
Helpful Answer

Re: SH3 Internet Connection Drops Packet Loss

Hello cpugenesis

Sorry you are still having some loss of sync issues, there was a little bit of intermittent noise in the area however it is difficult to be certain this is the cause. The hub wasn't provisioned correctly on our ladp so I have remedied that, apologies as it caused a reboot. May we see how it goes for the next few days please, kindly keep us updated.

Thank you  

Nicola

Virgin Media Forum Team
  • 18
  • 1
  • 1
cpugenesis
On our wavelength
532 Views
Message 7 of 9
Flag for a moderator

Re: SH3 Internet Connection Drops Packet Loss

Thanks for the help.  I've also been round the house and made sure all connections are nice and tight to avoid any ingress.   I imagine that the extra channels and higher frequencies of DOCSIS 3 are that bit more sensitive to noise.  

Agree - lets see how it goes over the next couple of days.

 

 

  • 18
  • 1
  • 1
cpugenesis
On our wavelength
496 Views
Message 8 of 9
Flag for a moderator

Re: SH3 Internet Connection Drops Packet Loss

Hi guys,

Starting to look a bit better,  Will continue to monitor over the next few days.

 

Friday seemed to stay the same with dropouts throughout the day.

          26FRI.jpg         

Saturday starting to look up,  graph shows 1 dropout at 4am but otherwise okay,

        27SAT.jpg

Sunday we had 2 periods of dropout during the day but otherwise okay.   

         28SUN.jpg

Monday as of 8pm,  so far so good - no issues.

        29MON.jpg

 

 

0 Kudos
Reply
  • 3
  • 0
  • 0
bradley987
Joining in
397 Views
Message 9 of 9
Flag for a moderator

Re: SH3 Internet Connection Drops Packet Loss

Hi, I'm on the same local area network as the original poster cpugenesis.

While the internet was fine for almost a week, the exact same issues have resurfaced over the last 3-4 days.

Last 24 hours 14:00 07/11/2018 - 08/11/2018:

 Packetloss.png

Note: I briefly rebooted the modem once at exactly 13:00.

Network logs show the same swarm of "SYNC Timing Synchronization failure - Loss of Sync" and "RCS Partial Service" errors.

In a one hour period from 13:00 to 14:00 our Downstream channels accumulated – on average – 17,000 Post RS Errors per channel per hour. The highest being 26266 Post RS Errors per hour on channel 23

Any real time services such as: online games/voice communications are impossible to use with them disconnecting every few minutes, logging back in then getting disconnected again.
More casual internet usage is also frustrating, effectively rolling a dice whether a page will load.

Logs:

Downstream Channels.png

Modem Network Logs 08/11/2018

Time Priority Description
2018-11-08 13:12:38.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:38.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:39.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:40.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:40.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:41.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:42.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:42.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:42.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:42.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:46.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:12:48.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:13:20.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:13:20.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:13:20.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:13:20.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:13:51.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:13:51.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:13:57.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-08 13:13:58.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;

Modem Network Logs 05/11/2018

2018-11-05 17:14:27.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:27.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:27.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:53.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:54.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:55.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:55.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:57.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:57.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:59.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:14:59.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:15:01.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:15:01.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:15:02.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:15:02.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:15:03.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:15:03.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:15:04.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:15:04.00 Warning! RCS Partial Service;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2018-11-05 17:15:10.00 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:d3:xx:xx:xx:xx;CMTS-MAC=00:01:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply