Menu
Reply
Highlighted
  • 57
  • 1
  • 2
On our wavelength
155 Views
Message 1 of 6
Flag for a moderator

Network logs

I’ve got an engineer booked to sort my low level upstream levels but I have noticed I’ve got a lot of errors and my logs aren’t to cracky either. Could power levels be the cause?

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

1331000000-1.538256 qam25
2203000000-1.238256 qam9
3211000000-1.238256 qam10
4219000000-1.238256 qam11
5227000000-1.238256 qam12
6235000000-1.238256 qam13
7243000000-1.438256 qam14
8251000000-1.438256 qam15
9259000000-1.538256 qam16
10267000000-1.538256 qam17
11275000000-1.738256 qam18
12283000000-1.738256 qam19
13291000000-1.938256 qam20
14299000000-1.738256 qam21
15307000000-1.738256 qam22
16315000000-1.738256 qam23
17323000000-1.538256 qam24
18339000000-1.438256 qam26
19347000000-1.238256 qam27
20355000000-1.238256 qam28
21363000000-1.238256 qam29
22371000000-138256 qam30
23379000000-1.238256 qam31
24387000000-1.238256 qam32



Downstream bonded channels

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

1Locked38.911553005
2Locked38.9270
3Locked38.9120
4Locked38.6130
5Locked38.9160
6Locked38.9120
7Locked38.9160
8Locked38.690
9Locked38.680
10Locked38.9220
11Locked38.9130
12Locked38.9100
13Locked38.6100
14Locked38.9140
15Locked38.9150
16Locked38.9130
17Locked38.9150
18Locked38.6110
19Locked38.9260
20Locked38.9250
21Locked38.9230
22Locked38.9110
23Locked38.9110
24Locked38.970
0 Kudos
Reply
Highlighted
  • 57
  • 1
  • 2
On our wavelength
151 Views
Message 2 of 6
Flag for a moderator

Re: Network logs

Network Log

Time Priority Description

12/08/2020 14:05:45criticalReceived 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/08/2020 14:04:0Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:56criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:55Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:55criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:44Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:44criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:44Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:40criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:40Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:40criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:03:39Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:02:47Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:02:43Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:02:42criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:02:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:02:42criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:02:41Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:02:41criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 12:29:37Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Highlighted
  • 9.28K
  • 721
  • 1.21K
Alessandro Volta
144 Views
Message 3 of 6
Flag for a moderator

Re: Network logs

Can you post your Upstream stats please.

Then

Can you set up a Broadband Quality Monitor (BQM) at thinkbroadband.com - this will give you an insight into what is happening with the signal at the other side of the Hub, it will take a few hours to get any kind of trend showing although you can post the link straight away.

Post a link to your BQM on here.

Instructions for posting BQM Link

Under your BQM graph are two links in red.

Click the lower link (Share Live Graph) then click generate.

Copy the text in the Direct Link box, beware, there may be more text than you can see.

On here click the Link icon (2 links chain to the left of the camera icon)

 In the URL box paste the link you copied and then click OK - you can post the link straight away.

***********************************************************************************************************************************

Mike Robinson
Aircraft Engineer & Computer Based Training and Learning Designer for many of the world's Military Arms.


My Broadband Ping - 26_Aug_2020
If you think my post has helped please give Gary Dexter a Kudos
because he collects them like a young lad collects conkers.
0 Kudos
Reply
Highlighted
  • 57
  • 1
  • 2
On our wavelength
134 Views
Message 4 of 6
Flag for a moderator

Re: Network logs

Upstream bonded channels

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

1537002703.25512064 qam2
2394002073.25512064 qam4
3462002463.25512064 qam3
4603002413.25512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
Highlighted
  • 57
  • 1
  • 2
On our wavelength
132 Views
Message 5 of 6
Flag for a moderator

Re: Network logs

0 Kudos
Reply
Highlighted
  • 3.98K
  • 670
  • 1.6K
Very Insightful Person
Very Insightful Person
121 Views
Message 6 of 6
Flag for a moderator
Helpful Answer

Re: Network logs

All those counted errors and network log messages are caused by the hub losing communication with VM's local network gear, and that's almost certainly because your upstream power levels are too low.  Other than the drop outs, your BQM looks very good.  Let the technician fix the power levels, and it should all be resolved.  A bit more explanation here in a reply I made earlier to somebody with a related issue.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply