Virgin Media Community

[sfsd334]

Hi,

I've noticed errors showing in the network log for the SH3 router. I've carried out the standard steps to try to resolve the issue.
I've pasted the log below. I've read other posts by people on this forum with the same issue and staff saying there is nothing wrong with their line from the tests they've done. There doesn't seem to be an explanation of why these errors are occuring.

Can you explain why I'm getting the below errors? I did have my VM cox cable moved higher up the wall a few weeks back so not sure if it has anything to do with that?

Cable Modem Status
Item Status Comments
Acquired Downstream Channel (Hz)
259000000
Locked
Ranged Upstream Channel (Hz)
39400000
Locked
Provisioning State
Online

Network Log
Time Priority Description
07/05/2022 14:27:59 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2022 21:57:31 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/05/2022 08:16:49 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/05/2022 02:21:52 notice SW download Successful - Via NMS
04/05/2022 02:19:40 notice SW Download INIT - Via NMS
02/05/2022 21:28:0 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 17:30:47 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/05/2022 04:28:18 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 06:10:41 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/04/2022 16:47:7 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/04/2022 15:50:58 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/04/2022 21:35:30 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/04/2022 03:50:58 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/04/2022 05:35:0 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/04/2022 15:50:58 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/04/2022 05:12:31 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/04/2022 03:50:58 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/04/2022 02:31:11 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/04/2022 15:50:58 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 18:38:23 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[gitty]

Sometimes they occur, because a request packet gets lost in transit. Other times a ranging request from the modem could be dropped by the CMTS, because it is busy doing something else. The few you have don't indicate a problem.

[jem101 · Accepted solution]

The ranging request and ranging response cycle happens every 30 seconds or so - it doesn't log all of the successful ones, just the occasional missed response. As @gitty rightly says, getting one of these every few days is really quite normal and isn't a problem.

[sfsd334]

Thanks for both your replies.