Menu
Reply
  • 6
  • 0
  • 0
harrylesanto
Joining in
354 Views
Message 1 of 6
Flag for a moderator

Constant daily disconnects

I've been having dropouts similar to what I've seen in other posts but wanted to make my own for visibility, they occur a good 10 or so times a day at fairly random intervals for a couple of minutes in each instance, been going on for weeks now. We had a hub replacement, followed by an engineer visit (changed the attenuator) then another engineer (same again, removed the previous attenuator) and now whenever I call they tell me they can't see any problem. I had one operator try to convince me it was because I was using a long ethernet cable (20m... it's hardly a seafloor cable), despite the fact that all my wired and WiFi devices disconnect at the same time, then I had another operator tell me they were going to send something to my hub within the next 24 hours that should stabilise the connection, whether he was just lying to get me off the phone or whether he really did that and it just hasn't worked I don't know but that was over 24 hours ago now so I gave it the time I was told to and it's had no effect whatsoever.

 

I'll post my logs below in case they're helpful at all. I really don't want to leave VM as we get a much faster connection than we would on a copper line, I'm on 350 where we'd get max 80 on the any of the other providers that're on the openreach network, but at least then I'd potentially have a stable line (I work for Openreach so I'd even be able to fix my own faults that way)...

12/05/2019 13:58:51Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 13:58:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 13:58:56Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 13:59:15criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 13:59:19criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 13:59:32Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 13:59:39criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:02:38Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:02:51criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:03:57Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:04:3criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:04:6Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:04:10criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:04:33criticalReceived 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;
12/05/2019 14:05:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:05:33criticalReceived 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;
12/05/2019 14:42:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:42:33criticalReceived 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;
12/05/2019 14:42:46Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2019 14:43:3criticalReceived 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;
0 Kudos
Reply
  • 6
  • 0
  • 0
harrylesanto
Joining in
353 Views
Message 2 of 6
Flag for a moderator

Re: Constant daily disconnects

I'll also post power levels here because someone's sure to ask.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1323000000540256 qam24
22030000004.840256 qam9
32110000004.538256 qam10
42190000004.440256 qam11
52270000004.340256 qam12
62350000004.540256 qam13
72430000004.540256 qam14
82510000004.540256 qam15
92590000004.540256 qam16
102670000004.640256 qam17
112750000004.640256 qam18
12283000000540256 qam19
13291000000540256 qam20
142990000005.140256 qam21
153070000005.140256 qam22
163150000005.340256 qam23
174270000005.140256 qam25
184350000005.140256 qam26
194430000005.340256 qam27
204510000005.340256 qam28
214590000005.340256 qam29
224670000005.140256 qam30
234750000004.840256 qam31
244830000004.640256 qam32



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked40.361272257
2Locked40.9136363897
3Locked38.9128484007
4Locked40.3146833591
5Locked40.3458346484
6Locked40.3280063836
7Locked40.3109303191
8Locked40.996862754
9Locked40.988002969
10Locked40.376602716
11Locked40.372822573
12Locked40.363642899
13Locked40.363252839
14Locked40.363592662
15Locked40.358122684
16Locked40.358772208
17Locked40.940281356
18Locked40.341851283
19Locked40.342171418
20Locked40.341041240
21Locked40.340561252
22Locked40.339321045
23Locked40.337041264
24Locked40.336381061

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1258000004.5512064 qam4
2462000004.625512064 qam1
3326000004.575512064 qam3



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
0 Kudos
Reply
Highlighted
  • 26
  • 0
  • 2
marting24
Tuning in
328 Views
Message 3 of 6
Flag for a moderator

Re: Constant daily disconnects

same problem here, 3 hubs and 4 engineer visits, no answer.

0 Kudos
Reply
  • 979
  • 46
  • 87
Forum Team (Retired) Tom_S
Forum Team (Retired)
272 Views
Message 4 of 6
Flag for a moderator

Re: Constant daily disconnects

Hi harrylesanto,

 

Having a look at your readings I'd like to send you a PM to discuss this further.

 

Thanks,

Tom_S

0 Kudos
Reply
  • 4
  • 0
  • 0
BATCH007
Joining in
262 Views
Message 5 of 6
Flag for a moderator

Re: Constant daily disconnects

did yours start when you got the new tivo box?

0 Kudos
Reply
  • 6
  • 0
  • 0
harrylesanto
Joining in
242 Views
Message 6 of 6
Flag for a moderator

Re: Constant daily disconnects

An engineer came yesterday and showed us that one of our downstream frequencies looked bad and replacing our isolator seemed to bring it into line, however overnight it's had more of the same, I don't have any TV box so I'm afraid it's nothing to do with that BATCH007.

16/05/2019 05:17:2criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:17:2Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:17:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:17:30Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:17:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:17:54Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:17:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:17:54criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:17:54Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:18:18criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:18:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:18:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 05:19:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 06:04:59criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 06:05:10Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 06:05:10criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 06:05:34Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 06:05:34criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 06:05:58Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2019 06:05:58criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply