Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

No Ranging Response received T3 timeout

oliveiraandre
Joining in

on ‎01-07-2022 16:06

Hi community,

I've been having issues with my internet dropping every single day since it has been setup in home, can anyone in Virgin Media help, please?

Below the network logs I got from my router.

Network Log

Time Priority Description
Wed 29/06/2022 22:46:033SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:036CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; 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;
Wed 29/06/2022 22:46:043SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:056CM-STATUS message sent. Event Type Code: 4; Chan ID: 27; 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;
Wed 29/06/2022 22:46:073SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:086CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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;
Wed 29/06/2022 22:46:093SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:116CM-STATUS message sent. Event Type Code: 5; Chan ID: 23; 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;
Wed 29/06/2022 22:46:133SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:136CM-STATUS message sent. Event Type Code: 5; Chan ID: 11; 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;
Wed 29/06/2022 22:46:155Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:156CM-STATUS message sent. Event Type Code: 5; Chan ID: 30; 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;
Wed 29/06/2022 22:46:173SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:176CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; 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;
Wed 29/06/2022 22:46:193SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:206CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; 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;
Wed 29/06/2022 22:46:293SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:296CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:323SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:326CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; 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;
Wed 29/06/2022 22:46:333Received 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.1;
Wed 29/06/2022 22:46:333SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:333Received 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.1;
Wed 29/06/2022 22:46:346CM-STATUS message sent. Event Type Code: 5; Chan ID: 30; 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;
Wed 29/06/2022 22:46:405Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:46:406CM-STATUS message sent. Event Type Code: 4; Chan ID: 27; 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;
Wed 29/06/2022 22:47:285MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:51:016CM-STATUS message sent. Event Type Code: 5; Chan ID: 29; 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;
Wed 29/06/2022 22:58:305Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/06/2022 22:58:316CM-STATUS message sent. Event Type Code: 5; Chan ID: 29; 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;
Thu 30/06/2022 08:19:383No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 30/06/2022 12:42:543SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 30/06/2022 12:42:566CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; 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;
Thu 30/06/2022 12:42:583No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 30/06/2022 12:43:046CM-STATUS message sent. Event Type Code: 2; Chan ID: 1; 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;
Thu 30/06/2022 12:44:363SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 30/06/2022 12:44:376CM-STATUS message sent. Event Type Code: 5; Chan ID: 30; 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;
Thu 30/06/2022 12:44:393SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 30/06/2022 12:44:416CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; 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;
Thu 30/06/2022 12:44:425Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 30/06/2022 12:44:423No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 30/06/2022 12:44:436CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; 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;
Thu 30/06/2022 18:11:323No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 30/06/2022 18:14:206CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 03:58:133No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 06:14:036CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; 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;

 

Thanks in advance 

0 Kudos
4 REPLIES 4

oliveiraandre
Joining in

on ‎01-07-2022 16:07

3.0 Downstream channels

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

30730000000-5.340.4QAM25630
15268000000-3.940.9QAM25615
25690000000-4.440.4QAM25625
32746000000-4.540.4QAM25632
13252000000-4.140.4QAM25613
14260000000-440.4QAM25614
16276000000-3.840.9QAM25616
18292000000-3.240.9QAM25618
20308000000-3.440.4QAM25620
24506000000-4.140.4QAM25624
5182000000-3.640.4QAM2565
6190000000-3.840.9QAM2566
7198000000-3.940.4QAM2567
8206000000-440.9QAM2568
9214000000-4.140.4QAM2569
10222000000-440.9QAM25610
11230000000-4.140.4QAM25611
12238000000-3.940.4QAM25612
17284000000-3.740.4QAM25617
19300000000-3.340.4QAM25619
22490000000-4.340.4QAM25622
23498000000-3.940.4QAM25623
27706000000-440.4QAM25627
28714000000-4.639QAM25628
29722000000-4.940.4QAM25629
26698000000-4.240.9QAM25626
31738000000-5.539QAM25631
1150000000-2.840.9QAM2561
2158000000-340.4QAM2562
3166000000-3.240.9QAM2563
4174000000-3.440.4QAM2564
21482000000-3.840.4QAM25621



3.0 Downstream channels

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

30Locked40.36628700
15Locked40.94620900
25Locked40.36628700
32Locked40.36628700
13Locked40.3662871620
14Locked40.36628700
16Locked40.94620900
18Locked40.94620900
20Locked40.36628700
24Locked40.36628700
5Locked40.36628700
6Locked40.94620900
7Locked40.36628700
8Locked40.94620900
9Locked40.36628700
10Locked40.94620900
11Locked40.36628700
12Locked40.3662871110
17Locked40.36628700
19Locked40.36628700
22Locked40.36628700
23Locked40.36628700
27Locked40.36628700
28Locked38.98326100
29Locked40.36628700
26Locked40.94620900
31Locked38.98326100
1Locked40.94620900
2Locked40.36628700
3Locked40.94620900
4Locked40.36628700
21Locked40.36628700



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33564K1080QAM4096631


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33Locked42-4.74790673386
0 Kudos

Tudor
Very Insightful Person
Very Insightful Person
In response to oliveiraandre

‎01-07-2022 16:57 - edited ‎01-07-2022 16:58

We need the upstream figures as well, they are just as important. 

Also check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level.


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2
0 Kudos

oliveiraandre
Joining in
In response to Tudor

on ‎02-07-2022 09:20

Hi Tudor,

Thanks for replying. I thought I had added the upstream also.

 

3.0 Upstream channels

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

13280000047.85120 KSym/sec64QAM2
26020000050.35120 KSym/sec64QAM6
353600000495120 KSym/sec64QAM5
44600000048.35120 KSym/sec64QAM4
539400000495120 KSym/sec64QAM3



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0030
2US_TYPE_STDMA0010
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
5US_TYPE_STDMA0010

 

 

Many thanks

0 Kudos

David_Bn
Forum Team
Forum Team
In response to oliveiraandre

on ‎04-07-2022 11:44

Good Morning @oliveiraandre, thanks for your post on our Community Forums, and a very warm welcome to you!

Sorry to hear of the issues with the connection since installation, the power levels look a little on the high side.

Check out the purple envelope in the top right hand corner for a private message from me, and I'll be able to look into this further.

Kindest regards,

David_Bn

0 Kudos
Top