Menu
Reply
Highlighted
  • 6
  • 0
  • 0
S-M-W
Joining in
166 Views
Message 1 of 11
Flag for a moderator

Area 12 (B31) lost connection more than 7 times today

I tried logging this via the connect app on 8/8/2019 and then via the message function on the website but still haven't had a response.

I had my origial (very old) hub replaced at Xmas because of connection problems; I then had the hub3 replaced again a couple of months ago and the connection is now worse than ever.

The hub has rebooted more than 6 times today, the modem log is full of errors and the power levels are all over the place i.e they are completly different every time the modem reboots so there's no point in me posting them.

Due to the high number of errors and the "Virgin Media" connect app appearing to go offline at the same time I'm assuming there's a fault in the cab and that its not just my connection?

This is making the connection unusable again. I'm assuming VM staff can see my connection details so I removed the MAC before posting the error log.

14/08/2019 17:20:7criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 17:22:23criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 17:23:10criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 17:23:19criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 17:23:19criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:ae;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 17:24:1criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 17:24:1criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:ae;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 17:24:41criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 17:24:41criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 18:14:53Warning!RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 18:22:5criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 18:22:5Warning!RCS Partial Service;CM-MAC=4;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 18:22:10Warning!Lost MDD Timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 18:22:28criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:ae;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 19:01:40criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 19:01:40Warning!RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 19:01:59criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 19:04:14criticalReceived 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;
14/08/2019 19:05:7criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 19:13:38Warning!RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;

 

0 Kudos
Reply
  • 11.47K
  • 761
  • 3.33K
Superuser
Superuser
156 Views
Message 2 of 11
Flag for a moderator

Re: Area 12 (B31) lost connection more than 7 times today

Yes Ive read your original post- just thought Id point that out. Before asking you...

Can you post your power levels?

 

 


0 Kudos
Reply
  • 6
  • 0
  • 0
S-M-W
Joining in
152 Views
Message 3 of 11
Flag for a moderator

Re: Area 12 (B31) lost connection more than 7 times today

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 323000000 -0.5 38 256 qam 24
2 139000000 -0.5 40 256 qam 1
3 147000000 -0.5 38 256 qam 2
4 155000000 -0.2 38 256 qam 3
5 163000000 -0.5 40 256 qam 4
6 171000000 -0.5 38 256 qam 5
7 179000000 -0.5 38 256 qam 6
8 187000000 -0.2 38 256 qam 7
9 195000000 -0.5 38 256 qam 8
10 203000000 -0.9 38 256 qam 9
11 211000000 -0.7 38 256 qam 10
12 219000000 -0.2 38 256 qam 11
13 227000000 -0.7 38 256 qam 12
14 235000000 -1.2 38 256 qam 13
15 243000000 -1.2 38 256 qam 14
16 251000000 -0.7 38 256 qam 15
17 259000000 -1 38 256 qam 16
18 267000000 -1.2 38 256 qam 17
19 275000000 -0.9 38 256 qam 18
20 283000000 -0.5 40 256 qam 19
21 291000000 -0.7 38 256 qam 20
22 299000000 -1 38 256 qam 21
23 307000000 -0.9 38 256 qam 22
24 315000000 -0.4 40 256 qam 23


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 666 1847
2 Locked 40.3 17077 227
3 Locked 38.6 609 169
4 Locked 38.9 3262 350
5 Locked 40.9 15102 532
6 Locked 38.9 448 568
7 Locked 38.9 29797 338
8 Locked 38.9 4613 26
9 Locked 38.9 245 24
10 Locked 38.9 269 60
11 Locked 38.9 245 26
12 Locked 38.6 210 25
13 Locked 38.9 248 27
14 Locked 38.6 317 27
15 Locked 38.9 308 24
16 Locked 38.9 324 37
17 Locked 38.9 386 19
18 Locked 38.9 339 27
19 Locked 38.9 350 30
20 Locked 40.3 384 46
21 Locked 38.6 374 22
22 Locked 38.9 408 26
23 Locked 38.9 449 29
24 Locked 40.3 394 20

 

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 46199854 5 5120 64 qam 3
2 39400021 5 5120 64 qam 4
3 53700017 5.1 5120 64 qam 2
4 60299974 5.1 5120 64 qam 1


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

 

 

They've changed from +2 to -11 over the last few days so I dont know how long they will stay where they are at now!

 

 

0 Kudos
Reply
  • 11.47K
  • 761
  • 3.33K
Superuser
Superuser
147 Views
Message 4 of 11
Flag for a moderator

Re: Area 12 (B31) lost connection more than 7 times today


@S-M-W wrote:

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 323000000 -0.5 38 256 qam 24
2 139000000 -0.5 40 256 qam 1
3 147000000 -0.5 38 256 qam 2
4 155000000 -0.2 38 256 qam 3
5 163000000 -0.5 40 256 qam 4
6 171000000 -0.5 38 256 qam 5
7 179000000 -0.5 38 256 qam 6
8 187000000 -0.2 38 256 qam 7
9 195000000 -0.5 38 256 qam 8
10 203000000 -0.9 38 256 qam 9
11 211000000 -0.7 38 256 qam 10
12 219000000 -0.2 38 256 qam 11
13 227000000 -0.7 38 256 qam 12
14 235000000 -1.2 38 256 qam 13
15 243000000 -1.2 38 256 qam 14
16 251000000 -0.7 38 256 qam 15
17 259000000 -1 38 256 qam 16
18 267000000 -1.2 38 256 qam 17
19 275000000 -0.9 38 256 qam 18
20 283000000 -0.5 40 256 qam 19
21 291000000 -0.7 38 256 qam 20
22 299000000 -1 38 256 qam 21
23 307000000 -0.9 38 256 qam 22
24 315000000 -0.4 40 256 qam 23


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 666 1847
2 Locked 40.3 17077 227
3 Locked 38.6 609 169
4 Locked 38.9 3262 350
5 Locked 40.9 15102 532
6 Locked 38.9 448 568
7 Locked 38.9 29797 338
8 Locked 38.9 4613 26
9 Locked 38.9 245 24
10 Locked 38.9 269 60
11 Locked 38.9 245 26
12 Locked 38.6 210 25
13 Locked 38.9 248 27
14 Locked 38.6 317 27
15 Locked 38.9 308 24
16 Locked 38.9 324 37
17 Locked 38.9 386 19
18 Locked 38.9 339 27
19 Locked 38.9 350 30
20 Locked 40.3 384 46
21 Locked 38.6 374 22
22 Locked 38.9 408 26
23 Locked 38.9 449 29
24 Locked 40.3 394 20

 

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 46199854 5 5120 64 qam 3
2 39400021 5 5120 64 qam 4
3 53700017 5.1 5120 64 qam 2
4 60299974 5.1 5120 64 qam 1


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

 

 

They've changed from +2 to -11 over the last few days so I dont know how long they will stay where they are at now!

 

 



@S-M-W wrote:

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 323000000 -0.5 38 256 qam 24
2 139000000 -0.5 40 256 qam 1
3 147000000 -0.5 38 256 qam 2
4 155000000 -0.2 38 256 qam 3
5 163000000 -0.5 40 256 qam 4
6 171000000 -0.5 38 256 qam 5
7 179000000 -0.5 38 256 qam 6
8 187000000 -0.2 38 256 qam 7
9 195000000 -0.5 38 256 qam 8
10 203000000 -0.9 38 256 qam 9
11 211000000 -0.7 38 256 qam 10
12 219000000 -0.2 38 256 qam 11
13 227000000 -0.7 38 256 qam 12
14 235000000 -1.2 38 256 qam 13
15 243000000 -1.2 38 256 qam 14
16 251000000 -0.7 38 256 qam 15
17 259000000 -1 38 256 qam 16
18 267000000 -1.2 38 256 qam 17
19 275000000 -0.9 38 256 qam 18
20 283000000 -0.5 40 256 qam 19
21 291000000 -0.7 38 256 qam 20
22 299000000 -1 38 256 qam 21
23 307000000 -0.9 38 256 qam 22
24 315000000 -0.4 40 256 qam 23


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 666 1847
2 Locked 40.3 17077 227
3 Locked 38.6 609 169
4 Locked 38.9 3262 350
5 Locked 40.9 15102 532
6 Locked 38.9 448 568
7 Locked 38.9 29797 338
8 Locked 38.9 4613 26
9 Locked 38.9 245 24
10 Locked 38.9 269 60
11 Locked 38.9 245 26
12 Locked 38.6 210 25
13 Locked 38.9 248 27
14 Locked 38.6 317 27
15 Locked 38.9 308 24
16 Locked 38.9 324 37
17 Locked 38.9 386 19
18 Locked 38.9 339 27
19 Locked 38.9 350 30
20 Locked 40.3 384 46
21 Locked 38.6 374 22
22 Locked 38.9 408 26
23 Locked 38.9 449 29
24 Locked 40.3 394 20

 

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 46199854 5 5120 64 qam 3
2 39400021 5 5120 64 qam 4
3 53700017 5.1 5120 64 qam 2
4 60299974 5.1 5120 64 qam 1


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

 

 

They've changed from +2 to -11 over the last few days so I dont know how long they will stay where they are at now!

 

 


Doesn't matter , upstream's WAAAYYY out. Downstream is pants too.

@ModTeam 

Can someone get a check your side and book an engineer if required?

 


  • 6
  • 0
  • 0
S-M-W
Joining in
144 Views
Message 5 of 11
Flag for a moderator

Re: Area 12 (B31) lost connection more than 7 times today

Actually looking at an earlier screen grab from 2019-08-09 19:23 it was -14.4 !

 

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 323000000 -9 35 256 qam 24
2 139000000 -14.4 28 256 qam 1
3 147000000 -13.9 28 256 qam 2
4 155000000 -13.4 29 256 qam 3
5 163000000 -13.4 29 256 qam 4
6 171000000 -12.9 30 256 qam 5
7 179000000 -12.7 30 256 qam 6
8 187000000 -12.2 30 256 qam 7
9 195000000 -12 31 256 qam 8
10 203000000 -12.2 31 256 qam 9
11 211000000 -11.7 31 256 qam 10
12 219000000 -11.2 32 256 qam 11
13 227000000 -11.4 32 256 qam 12
14 235000000 -11.5 32 256 qam 13
15 243000000 -11.4 32 256 qam 14
16 251000000 -10.7 32 256 qam 15
17 259000000 -10.7 33 256 qam 16
18 267000000 -10.7 33 256 qam 17
19 275000000 -10.2 33 256 qam 18
20 283000000 -9.7 34 256 qam 19
21 291000000 -9.7 34 256 qam 20
22 299000000 -10 34 256 qam 21
23 307000000 -9.5 34 256 qam 22
24 315000000 -9 35 256 qam 23


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 35.5 43270 208
2 Locked 28.4 49133338 46492
3 Locked 28.9 38222203 32450
4 Locked 29.4 23853085 19721
5 Locked 29.8 17020982 15866
6 Locked 30 13301297 6207
7 Locked 30.3 9044014 10073
8 Locked 30.7 5964828 6069
9 Locked 31 3976800 722
10 Locked 31.3 2412325 390
11 Locked 31.6 1400085 242
12 Locked 32 752515 164
13 Locked 32.2 651579 187
14 Locked 32.5 407357 165
15 Locked 32.6 277983 158
16 Locked 32.9 213526 143
17 Locked 33.1 182795 156
18 Locked 33.8 127935 169
19 Locked 33.9 105942 65
20 Locked 34.4 84924 147
21 Locked 34.4 72588 137
22 Locked 34.3 71697 144
23 Locked 34.9 63553 138
24 Locked 35 53112 124


Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 46200061 5.1 5120 64 qam 3


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0

0 Kudos
Reply
  • 11.47K
  • 761
  • 3.33K
Superuser
Superuser
139 Views
Message 6 of 11
Flag for a moderator

Re: Area 12 (B31) lost connection more than 7 times today

winnergif.jpg

Congratulations, you have won the "most horribly out of spec power levels so bad your HUB should be crying in a corner and refuse to work" medal of the week

Staff should contact you to arrange an engineer. Come back and let us know how it goes....

 


  • 6
  • 0
  • 0
S-M-W
Joining in
115 Views
Message 7 of 11
Flag for a moderator

Re: Area 12 (B31) lost connection more than 7 times today

I'm guessing VM have poked my router remotely because it's now stuck ranging and I've lost all internet access. I've switched the router off for a few minutes and managed to connect a tablet using the VM connect app but the signal is dreadful. Hopefully they will send an engineer to look at the cab and contact me if they need access to the router again...

I did read on another thread that there's a firmware bug so routers are showing the wrong upload power levels maybe VM could update my firmware so it's on the newer version?

0 Kudos
Reply
  • 989
  • 46
  • 59
Forum Team
Forum Team
85 Views
Message 8 of 11
Flag for a moderator

Re: Area 12 (B31) lost connection more than 7 times today

Good Morning S-M-W

 

Thanks for your post on our Community Forums and a very warm welcome to you!

 

This doesn't look good does it!? Lets get this sorted for you asap!

 

Please check out the purple envelope in the top right hand corner of the screen for a PM from me

 

Kindest regards

 

David_Bn

0 Kudos
Reply
  • 6
  • 0
  • 0
S-M-W
Joining in
24 Views
Message 9 of 11
Flag for a moderator

Re: Area 12 (B31) lost connection more than 7 times today

 

@ModTeam

 

Engineer visited on Saturday he tested the signal in the flat and said it was fine; he then replaced a splitter in the box on the outside wall which was rusty on the back (incoming cable shared with flat above mine); he also replaced the cable between the outside box and the inside box and removed the isolator from the inside box which he said was very old (apparantly can degrade over time but protects from high voltages so probably should have been replaced not just removed). The Modem came back online after he scanned the barcode on the router.

I asked him if there could be a fault on the incoming cable or in the flat above mine which uses the same cable and he said his test would have showed if there was.

Engineer did all he could to help and it was working okay when he left; he even left his mobile number in case it started playing up again which was a nice gesture. Unfortunately it worked for less than a day then the router started rebooting again and my mobile is on the fritz so I haven't been able to call him and ask him to come back. It went down for quite a long time then when it came back on for a while I signed up for the broadband monitoring service.

I don't know anyone that would be happy with a connection like this either:
1. the modem which was replaced during the previous visit is faulty
2. theres an intermittent fault on the cable from your cab (engineer said cable was okay)
3. theres an intermittent fault in the cab

https://www.thinkbroadband.com/broadband/monitoring/quality/share/bb107e349ed40c01279828a9ea3b4fca73...

 

This mornings network log:
19/08/2019 07:37:49 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 07:37:50 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 07:37:50 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 07:37:56 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 07:38:36 critical 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;
19/08/2019 07:54:58 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:07:44 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:07:44 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:07:45 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:07:50 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:08:42 critical 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;
19/08/2019 08:28:34 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:33:49 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:33:49 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:33:49 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:33:54 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:34:40 critical 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;
19/08/2019 08:35:18 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 08:37:18 critical 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;
19/08/2019 08:37:53 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Last nights network log:
18/08/2019 21:27:45 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 21:41:41 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 21:41:42 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 21:41:42 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 21:41:47 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 21:42:25 critical 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;
18/08/2019 21:57:10 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:12:7 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:12:8 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:12:8 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:12:8 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:12:8 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:12:13 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:12:49 critical 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;
18/08/2019 22:27:41 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:43:23 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:43:23 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:43:24 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:43:27 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 22:44:7 critical 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;

Connection info from this morning when it was working:
Item Status Comments
Acquired Downstream Channel (Hz) 299000000 Locked
Ranged Upstream Channel (Hz) 32600007 Locked
Provisioning State Online

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 299000000 3.9 40 256 qam 21
2 139000000 4 40 256 qam 1
3 147000000 4 40 256 qam 2
4 155000000 4.3 40 256 qam 3
5 163000000 4 40 256 qam 4
6 171000000 4 40 256 qam 5
7 179000000 4 40 256 qam 6
8 187000000 4.3 40 256 qam 7
9 195000000 4.1 40 256 qam 8
10 203000000 3.7 40 256 qam 9
11 211000000 3.9 40 256 qam 10
12 219000000 4.1 40 256 qam 11
13 227000000 4 40 256 qam 12
14 235000000 3.5 40 256 qam 13
15 243000000 3.2 40 256 qam 14
16 251000000 3.7 40 256 qam 15
17 259000000 3.7 40 256 qam 16
18 267000000 3.5 40 256 qam 17
19 275000000 3.7 40 256 qam 18
20 283000000 3.5 40 256 qam 19
21 291000000 3.7 40 256 qam 20
22 307000000 3.5 40 256 qam 22
23 315000000 3.7 40 256 qam 23
24 323000000 3.9 40 256 qam 24


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.9 453 0
2 Locked 40.3 9 0
3 Locked 40.3 7 0
4 Locked 40.9 7 0
5 Locked 40.9 14 0
6 Locked 40.9 7 0
7 Locked 40.3 16 0
8 Locked 40.9 21 0
9 Locked 40.9 19 0
10 Locked 40.3 26 0
11 Locked 40.3 48 0
12 Locked 40.9 42 0
13 Locked 40.9 75 0
14 Locked 40.3 111 0
15 Locked 40.9 125 0
16 Locked 40.9 129 0
17 Locked 40.9 191 0
18 Locked 40.9 194 0
19 Locked 40.3 250 0
20 Locked 40.3 311 0
21 Locked 40.3 341 0
22 Locked 40.9 528 0
23 Locked 40.9 529 0
24 Locked 40.3 581 0


Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 32600007 4.45 5120 64 qam 5
2 39400007 4.5 5120 64 qam 4
3 46199996 4.55 5120 64 qam 3
4 53699991 4.65 5120 64 qam 2


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

 

0 Kudos
Reply
  • 11.47K
  • 761
  • 3.33K
Superuser
Superuser
18 Views
Message 10 of 11
Flag for a moderator

Re: Area 12 (B31) lost connection more than 7 times today

Well, on the plus side engineer has done his/her job as the power levels are now in spec, which is reflected in post RS errors being fine.

Obviously you can see the minus side...

I wonder have you stumbled on the issue? Maybe upstairs is letting noise into the network?

We can only diagnose so much from metrics, but looking at yours I would say either option 3 or noise ingress- but TBF to the engineer, the tests they ran at the time may not have picked either up as the issue looks to be intermittent.

@ModTeam  can someone arrange a follow-up visit or some tests your side?

@S-M-W  DO you know the upstairs flat people well  enough to find out if they have/had VM?