Menu
Reply
  • 2
  • 0
  • 0
pnjman
Joining in
80 Views
Message 1 of 4
Flag for a moderator

Frequent internet dropouts.

I've had 100mb broadband for 3 weeks, first 2 weeks connection rock solid, since then connection has frequently gone down for many hours at a time.

Here are my router logs

Cable Modem Status
Item Status Comments
Acquired Downstream Channel(Hz)
323000000
Locked
Ranged Upstream Channel(Hz)
37600000
Locked
Provisioning State
Online

 

Downstream bonded channels
Channel Frequency(Hz) Power
(dBmV) SNR
(dB) Modulation Channel ID
1 323000000 12 36.3 256 qam 12
2 315000000 9.5 33.8 256 qam 11
3 307000000 9.4 34.3 256 qam 10
4 299000000 11.5 36.6 256 qam 9
5 235000000 12.9 37.6 256 qam 1
6 283000000 10.5 35.5 256 qam 7
7 275000000 12.3 37.6 256 qam 6
8 267000000 12.3 37.6 256 qam 5
9 259000000 12.4 37.6 256 qam 4
10 251000000 11.8 37.6 256 qam 3
11 243000000 11.9 37.3 256 qam 2
12 291000000 9.5 33.9 256 qam 8

 

Upstream bonded channels
Channel ID Frequency(Hz) Mode Power
(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)
4 37600000 ATDMA 39.8 64 qam 6400000 5120
6 24400000 ATDMA 39.8 64 qam 6400000 5120
5 31000000 ATDMA 39.8 64 qam 6400000 5120

 

Operational Configuration
General Configuration Value
Network access
Enabled
Maximum Number of CPEs
1
Baseline Privacy
Enabled
Docsis Mode
Docsis30
Config file
cxv9873254k;fg87dsf
Primary Downstream Service Flow
SFID 6295
Max Traffic Rate 110100000
Primary Upstream Service Flow
SFID 6306
Max Traffic Rate 6400000

 

Network Log
Date And Time Error Number Event Description
2016-12-05 09:48:16.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:48:16.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:48:56.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:48:57.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:04.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:07.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:20.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:20.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:24.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:24.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:26.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:26.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:29.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:30.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:49.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:49:52.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 09:57:38.00 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 19:20:50.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 19:42:54.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2016-12-05 19:58:24.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply
  • 8.99K
  • 756
  • 1.88K
Superuser
Superuser
74 Views
Message 2 of 4
Flag for a moderator

Re: Frequent internet dropouts.

Your downstream power levels are too high and need to be adjusted. The logs are also showing your downstream is in distress.

You will need to contact VM for resolution, either by waiting here about a week until a VM Forum Team Member picks up the thread, or give them a call on 150 from a VM line or 0345 454 1111 for a quicker response.

0 Kudos
Reply
  • 2
  • 0
  • 0
pnjman
Joining in
71 Views
Message 3 of 4
Flag for a moderator

Re: Frequent internet dropouts.

Thanks for the reply. Better get on the phone.

0 Kudos
Reply
  • 9.96K
  • 291
  • 624
Forum Team
Forum Team
49 Views
Message 4 of 4
Flag for a moderator

Re: Frequent internet dropouts.

Hello pnjman,

 

Thanks for posting and a big welcome to the community Smiley Very Happy

 

Sorry to see that you're having trouble with your connection.

 

I can get this sorted for you. Let's arrange for an engineer to visit.

 

I'll send you the appointment info via PM (purple envelope, top right).

 

Catch you soon,

Take care.

Heather_J

Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply