cancel
Showing results for 
Search instead for 
Did you mean: 

Noisey line - SNR

mellatron
On our wavelength

Have got a noisey line since Virgin did some area work to "fix" local issues. Getting lots of SYNC Timing Synchronization failure - Loss of Sync errors in the hub network logs as well as T3 timeouts. Latency issues mean working from home is impossable.

Had an engingeer out due to lots of connection drop outs who reported the SNR issues to the Network Team but have heard nothing back regarding a repair. Same engineer told me our local area was over subscribed and the street cabinets were a mess.

One of my neighbours was told by a contractor the street cable needed replacing, no one seems to know what is going on. Can anyone help?

ownstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13310000007.642QAM 25625
21390000008.441QAM 2561
31470000008.341QAM 2562
41550000008.341QAM 2563
51630000008.341QAM 2564
61710000008.341QAM 2565
71790000008.441QAM 2566
81870000008.641QAM 2567
91950000008.441QAM 2568
102030000008.341QAM 2569
112110000008.341QAM 25610
122190000008.141QAM 25611
132270000007.941QAM 25612
142350000007.941QAM 25613
152430000007.641QAM 25614
162510000007.641QAM 25615
172590000007.541QAM 25616
182670000007.641QAM 25617
192750000007.741QAM 25618
202830000007.741QAM 25619
212910000007.641QAM 25620
222990000007.641QAM 25621
233070000007.741QAM 25622
243150000007.642QAM 25623
253230000007.742QAM 25624
263390000007.341QAM 25626
273470000007.341QAM 25627
283550000007.441QAM 25628
293630000007.542QAM 25629
303710000007.642QAM 25630
313790000007.842QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4280
2Locked4190
3Locked41140
4Locked41100
5Locked41180
6Locked4190
7Locked41110
8Locked4140
9Locked41120
10Locked4180
11Locked4190
12Locked4160
13Locked4140
14Locked41110
15Locked41130
16Locked41150
17Locked4160
18Locked41120
19Locked41130
20Locked41130
21Locked41100
22Locked4180
23Locked4180
24Locked42150
25Locked42150
26Locked41160
27Locked41140
28Locked41100
29Locked4230
30Locked42120
31Locked42150

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000044.55120QAM 641
14310000043.55120QAM 642
23660000042.55120QAM 643
33010000042.35120QAM 644
42360000041.55120QAM 645

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA00180
4ATDMA0000

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file
Allowed
1
Enabled
3.1
,.iyewrkldJKDHSUBsgvca698

Network Log

Time Priority Description
28-09-2023 13:33:03criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-09-2023 13:32:35noticeCM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-09-2023 13:29:00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-09-2023 13:28:39noticeCM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-09-2023 02:00:03criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-09-2023 01:59:56errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:33:04criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:32:56warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:32:03criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:31:56warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:18:07criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:17:56warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:17:00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:16:56warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:05:17criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:05:00critical16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:05:00criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:05:00criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:04:02criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:03:40criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:02:02criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:01:40warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:01:20criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:01:04criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 03:00:40warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 02:48:25criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-09-2023 13:59:51errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-09-2023 14:04:17warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-09-2023 14:04:17noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-09-2023 13:54:14noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-09-2023 13:54:14warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
20-09-2023 21:46:48warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

My Broadband Ping - New Hub 5

3 REPLIES 3

Client62
Legend

Line does not exhibit the obvious signs of an SNR issue.

Interesting, thanks.The dropouts are getting less frequent, I just wish Virgin would communicate with their customers so we know what's going on. That seems a strech when the different departments can't talk to each other though.

Hi mellatron,

Thank you for your post. I'm so sorry to hear you've been having a lot of trouble with your broadband recently.

Your BQM graph looks very good and stable, no sign of bad latency or packet loss, however looking at this end, a lot of your broadband downstream levels are out of spec, so I'll need to arrange for another engineer to take a look.

I'll pop over a private message now so I can help further.

 

Beth