Menu
Reply
Joining in
  • 11
  • 0
  • 0
Registered: ‎16-02-2017
Message 1 of 13 (332 Views)

Connection unstable, dozens of times every single day

Ever since Virgin managed to set up my connection, I've been experiencing an embarrassing amount of disconnections every day.

This is what happens: all of a sudden, the SuperHub 3 shuts off, then flashes the green led, wireless and wps lights turn on and then off and eventually, in a couple of minutes, I'm back online.

This is just an excerpt of what I'm suffering right now:

2017-03-13 15:13:56.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:15:45.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:16:02.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:17:06.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:17:23.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:26:29.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:26:58.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:27:52.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:28:15.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:28:35.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:29:23.0082000400Received 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;
2017-03-13 15:30:01.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:32:40.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:32:43.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:32:50.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:32:51.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:32:51.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:34:08.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:34:28.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:34:52.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:35:07.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:37:21.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:37:23.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:42:08.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:44:57.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:45:46.0082000400Received 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;
2017-03-13 15:46:22.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-13 15:49:11.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;


While this is the log I've saved over the weekend.
Unfortunately the router only stores a bunch of lines, so this is what I saved when I remembered to do so:

2017-03-11 20:05:0582000400Received 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;
2017-03-11 20:08:1984000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-11 20:35:4283010300Service Delete Response rejected - Invalid Transaction;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-11 20:51:3784020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-11 20:55:0583010200Service Change Response rejected - Invalid transaction ID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-11 21:17:3267040400DCC-ACK rejected authentication failure;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-11 21:18:5183020200Service Add Ack rejected - Invalid transaction ID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 0:54:0382000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 8:54:0284000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 9:32:2282000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 9:33:1082000400Received 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;
2017-03-12 9:33:5682000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 9:36:1384000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 9:37:0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 9:37:4282000400Received 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;
2017-03-12 9:38:3682000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 9:46:3984000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 9:49:1482000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 9:50:0282000400Received 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;
2017-03-12 9:51:0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 10:44:1484000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 10:47:4484000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 10:48:1484000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 10:49:2682000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 10:50:1482000400Received 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;
2017-03-12 10:51:0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 11:03:1682000400Received 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;
2017-03-12 11:04:0882000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 11:11:5984000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 11:13:2784000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 11:13:3484000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 11:13:3982000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 11:13:3984000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 11:13:4082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 11:14:2782000400Received 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;
2017-03-12 11:15:3382000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 11:50:1784000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 12:20:4682000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 12:21:3582000400Received 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;
2017-03-12 12:22:1982000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 13:28:2084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 13:29:0282000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 13:29:5082000400Received 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;
2017-03-12 13:30:4282000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 13:31:5168000100DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 13:31:5582000400Received 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;
2017-03-12 13:32:2982000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 13:38:1484000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 13:38:2182000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-03-12 13:39:2582000400Received 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;
2017-03-12 13:40:1882000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;


Now, what the hell am I supposed to do?
This does not even come close to a decent service, let alone one I'm supposed to pay at the end of each month.

Reply
0 Kudos
Knows their stuff
  • 1.07K
  • 78
  • 203
Registered: ‎15-03-2012
Message 2 of 13 (314 Views)

Re: Connection unstable, dozens of times every single day

It will take around a week for a member of Virgin staff to reach this message, so may be worth giving 150 a call.

It may help to post your power levels here as well.

And a BQM http://www.thinkbroadband.com/ping should give some useful info, although you'll have to disable the hubs firewall for it to work properly.

Reply
0 Kudos
Joining in
  • 11
  • 0
  • 0
Registered: ‎16-02-2017
Message 3 of 13 (307 Views)

Re: Connection unstable, dozens of times every single day

I'm gonna give that tool a try later, thanks.

As for calling them: well I don't have a Virgin phone line, and last month I've pretty much used up all my monthly mobile minutes with Virgin call centre to obtain an engineer visit to finally get me up and running. I'd rather not doing that again.

And also I'm not a native English speaker, and since the live chat has never worked for me once, I'm much more comfortable asking for support here instead.
Reply
0 Kudos
Joining in
  • 11
  • 0
  • 0
Registered: ‎16-02-2017
Message 4 of 13 (250 Views)

Re: Connection unstable, dozens of times every single day

[ Edited ]

Here you go, this are the BQM graphs starting on 14/03 at around 10.30 until now: 

My Broadband Ping - Virgin Cable

My Broadband Ping - Virgin Cable

It's clear there's something going on - except during late night, which is not that ideal.

Regarding the power levels, this is what I found in my router dashboard:

Downstream bonded channels

ChannelFrequency(Hz)Power(dBmV)SNR(dB)ModulationChannel ID
1298750000338.9256 qam17
23227500003.538.9256 qam20
33147500003.738.6256 qam19
4306750000338.9256 qam18
52907500002.938.9256 qam16
62827500002.538.9256 qam15
72747500002.938.6256 qam14
82667500002.738.9256 qam13
92587500002.438.6256 qam12
102507500003.238.9256 qam11
112427500002.938.6256 qam10
122347500002.438.9256 qam9
132267500002.538.9256 qam8
142187500002.438.9256 qam7
152107500002.738.6256 qam6
16202750000338.6256 qam5
17194750000338.6256 qam4
18186750000338.9256 qam3
191787500003.238.6256 qam2
201707500003.238.6256 qam

 

Upstream bonded channels

Channel IDFrequency(Hz)ModePower(dBmV)ModulationChannel Bandwidth(Hz)Symbol Rate (ksps)
835800000ATDMA46.564 qam64000005120
745800000ATDMA46.564 qam64000005120


Now, yesterday I called them because it was so insufferable.
The support person told me there's nothing wrong in my area and sent me a new modem that should arrive tomorrow.

Fact is: I don't think there's anything wrong with my current modem as, judging by the BQM graphs, it's clearly capable to work without issues for long periods.

Reply
0 Kudos
Joining in
  • 11
  • 0
  • 0
Registered: ‎16-02-2017
Message 5 of 13 (260 Views)

Re: Connection unstable, dozens of times every single day

Here you go with two BQM graphs, one starting from 14/03 at around 10.30, the other is live.

My Broadband Ping - Virgin Cable

My Broadband Ping - Virgin Cable

Now, there's clearly something going on here, except during late night, which is not really acceptable at all.

Here's my power levels as shown in the router dashboard:

Downstream bonded channels
ChannelFrequency(Hz)Power
(dBmV)
SNR
(dB)
ModulationChannel ID
1298750000338.9256 qam17
23227500003.538.9256 qam20
33147500003.738.6256 qam19
4306750000338.9256 qam18
52907500002.938.9256 qam16
62827500002.538.9256 qam15
72747500002.938.6256 qam14
82667500002.738.9256 qam13
92587500002.438.6256 qam12
102507500003.238.9256 qam11
112427500002.938.6256 qam10
122347500002.438.9256 qam9
132267500002.538.9256 qam8
142187500002.438.9256 qam7
152107500002.738.6256 qam6
16202750000338.6256 qam5
17194750000338.6256 qam4
18186750000338.9256 qam3
191787500003.238.6256 qam2
201707500003.238.6256 qam1

 

Upstream bonded channels
Channel IDFrequency(Hz)ModePower
(dBmV)
ModulationChannel Bandwidth(Hz)Symbol Rate (ksps)
835800000ATDMA46.564 qam64000005120
745800000ATDMA46.564 qam64000005120

 

Yesterday, when the situation was utterly unsufferable, I called and the support person told me there's nothing wrong going on in my area, assumed my modem was faulty and sent me a new one which should arrive tomorrow.

Fact is: I don't think it's a modem problem, considering it's capable of working with no issues for so many hours while I'm sleeping.

Reply
0 Kudos
Forum Team
  • 9.02K
  • 253
  • 540
Registered: ‎07-04-2015
Message 6 of 13 (236 Views)

Re: Connection unstable, dozens of times every single day

Hi Copons,

 

Thanks for taking the time to post on the community.

 

My apologies you are experiencing intermittent broadband connection. I can imagine how annoying this must be.

 

Looking at your connection, the line and hub have come back as fine with no time-outs reported.

 

Has there been any further disconnections, since you activated the new router?

 

I'm guessing from the Live BQM graph, that this has not been set up with the new router? If you are getting the same issue, can you post your network log for me please?

 

Hope to hear from you soon

Sam


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


Reply
0 Kudos
Joining in
  • 11
  • 0
  • 0
Registered: ‎16-02-2017
Message 7 of 13 (225 Views)

Re: Connection unstable, dozens of times every single day

Hi Sam,
the new router is definitely a huge improvement.
Not perfect though. I'm still experiencing a couple of daily disconnections (on average, and according to the BQM graph).
I'll keep it monitored for another week or so, but for now it's still annoying but liveable.
Reply
0 Kudos
Forum Team
  • 9.02K
  • 253
  • 540
Registered: ‎07-04-2015
Message 8 of 13 (213 Views)

Re: Connection unstable, dozens of times every single day

Morning Copons,

 

Thanks for getting back to me.

 

I'm glad you have noticed an improvement with the connection, that is good.

 

If you would like me to take a look at the disconnections, post the network log and BQM graph for me please. Otherwise monitor the connection and fingers crossed all will be ok.

 

Take care

Sam


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


Reply
0 Kudos
Joining in
  • 11
  • 0
  • 0
Registered: ‎16-02-2017
Message 9 of 13 (198 Views)

Re: Connection unstable, dozens of times every single day

[ Edited ]

Hi Samantha,

I'm reopening this thread as, after a couple of good enough weeks, the situation regressed to a quite bad state.

I'm having more than a couple of daily disconnections, with plenty of minor dropped packages here and there throughout the day.

 

Here you go with a bunch of BQM graphs for some (meaning: there are other bad days, but good days as well) of the worst offender days:

Right now:My Broadband Ping - Virgin Cable (2nd)

09/05/2017:My Broadband Ping - Virgin Cable (2nd)

06/05/2017:My Broadband Ping - Virgin Cable (2nd)

30/04/2017:My Broadband Ping - Virgin Cable (2nd)

29/04/2017:My Broadband Ping - Virgin Cable (2nd)

23/04/2017:My Broadband Ping - Virgin Cable (2nd)

Notice that there's no obvious pattern. It's nothing related to the day of the week, or the time, or even the usage (most of these graphs comes from days we were abroad!).

And here it is the network log (I'd say the times are offset by 1 hour compared to the BQM graphs):

2017-05-10 10:38:56.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 10:39:04.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 10:39:27.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 10:39:28.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 10:39:29.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 10:39:29.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 10:39:40.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 10:39:43.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 10:39:45.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 10:40:04.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 12:49:30.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 16:33:02.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 16:33:12.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 16:33:38.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 16:34:18.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 16:34:21.0082000300Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 16:34:22.0082000600Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 16:34:25.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-05-10 16:34:52.0082000400Received 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;
2017-05-10 16:36:03.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Reply
0 Kudos
Joining in
  • 11
  • 0
  • 0
Registered: ‎16-02-2017
Message 10 of 13 (177 Views)

Re: Connection unstable, dozens of times every single day

This is ridiculous.

My Broadband Ping - Virgin Cable (2nd)

Reply
0 Kudos