Menu
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
243 Views
Message 1 of 11
Flag for a moderator

No Ranging Response received

I keep getting these errors so either cabinet issues or capacity issues as router replaced, external tests by VM show no issues but dropouts are becoming annoying. Hub used as modem as have XR300 router.

The list endless.

Time Priority Description

16/11/2020 15:07:16Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/11/2020 14:11:56criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/11/2020 14:11:28criticalREG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/11/2020 14:11:28ErrorT6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/11/2020 14:11:28criticalRegistration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/11/2020 14:11:28criticalRegistration RSP rejected message syntax error;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/11/2020 14:11:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/11/2020 14:10:47criticalREG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/11/2020 14:10:47ErrorT6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 

0 Kudos
Reply
Highlighted
  • 1.43K
  • 202
  • 672
Very Insightful Person
Very Insightful Person
217 Views
Message 2 of 11
Flag for a moderator

Re: No Ranging Response received

These are upstream issues and almost certainly a cable fault (bad joint, damaged coax cable) somewhere between the Hub and the street cabinet - check all the connections you can get to and make sure they are nice and finger-tight with  no obvious sign of damage (don't forget the ones in the omnibox outside on the wall where the cable comes in). If no luck then you will need an engineer visit.

0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
193 Views
Message 3 of 11
Flag for a moderator

Re: No Ranging Response received

All connections checked, internal cables haven't been disturbed in years, my guess is external as VM in the street a couple of weeks ago and neighbours card swapped out.

Cabinet at top of street is not weather proof as open.

last issues resolved with lift and shift.

Could be water ingress as power levels seem to drop in wet weather.

this is more than likely VM cabinet end as cables don't just fail and there's been a lot of VM activity in my area.

0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
191 Views
Message 4 of 11
Flag for a moderator

Re: No Ranging Response received

also discussed these issues with VM and was told no issues found, which clearly isn't the case as it is so intermittent.

Every issue i have ever had with VM has been cabinet based!! never seen an engineer and that's in like 20 years of being with them.
0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
186 Views
Message 5 of 11
Flag for a moderator

Re: No Ranging Response received

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

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.6 279 0
2 Locked 37.6 9507088 639843
3 Locked 38.9 283328 216959
4 Locked 38.9 2178438 335562
5 Locked 38.9 9414259 1202155
6 Locked 38.9 76343 178999
7 Locked 38.6 8861727 2003261
8 Locked 38.6 3635090 113441
9 Locked 38.6 124 11
10 Locked 38.6 108 12
11 Locked 38.9 107 0
12 Locked 38.6 101 0
13 Locked 38.6 101 0
14 Locked 38.6 108 0
15 Locked 38.9 118 0
16 Locked 38.6 134 0
17 Locked 38.9 134 0
18 Locked 38.6 117 1
19 Locked 38.9 96 0
20 Locked 38.6 103 0
21 Locked 38.6 225 0
22 Locked 38.9 95 0
23 Locked 38.6 77 0
24 Locked 38.9 90 0
0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
118 Views
Message 6 of 11
Flag for a moderator

Re: No Ranging Response received

Worse today and impacting son working at home with school work.

Clearly an external cabinet issue that needs sorting urgently, how can this be diagnosed NFF when its failing daily?

18/11/2020 15:19:11 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:07:23 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:06:51 critical REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:06:51 Error T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:06:51 critical Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:06:51 critical Registration RSP rejected message syntax error;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:06:37 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:06:5 critical REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:06:5 Error T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:06:5 critical Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:06:5 critical Registration RSP rejected message syntax error;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:05:51 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:05:19 critical REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:05:19 Error T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:05:19 critical Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:05:19 critical Registration RSP rejected message syntax error;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:05:3 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:04:30 critical REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:04:30 Error T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/11/2020 14:04:30 critical Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
79 Views
Message 7 of 11
Flag for a moderator

Re: No Ranging Response received

Another poor day, VM please sort this out.

19/11/2020 13:34:52 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:11:1 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:09:44 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:09:24 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:04:25 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:03:43 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:03:26 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:02:7 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:01:42 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:00:55 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:00:29 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:00:28 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:00:4 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 10:00:4 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 09:59:39 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 09:54:59 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/11/2020 09:52:0 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Highlighted
  • 12.15K
  • 943
  • 1.56K
Alessandro Volta
68 Views
Message 8 of 11
Flag for a moderator

Re: No Ranging Response received

This will need an engineer to put right.

You can either call in (08:00 is the best time) or wait on here for a few days (6 to 7 days average) until one of the VM Forum Staff comes along.

If you wait on here Do Not bump the thread it will put it further down the VM 'to do list'.

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

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

My Broadband Ping - Mike Robbo
0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
57 Views
Message 9 of 11
Flag for a moderator

Re: No Ranging Response received

This is definitely an external cabinet issue. This is happening on a daily basis, when it works it works well and can't complain and all tests PASS OK. 

I can wait no issue rather than hang on a phone, already complained and told NFF as tests PASSED OK!!

Thanks.

0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Joining in
54 Views
Message 10 of 11
Flag for a moderator

Re: No Ranging Response received

20/11/2020 16:13:16 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

todays issue
0 Kudos
Reply