on 11-06-2023 11:38
ourselves and the neybours are getting a lot of LoS NRRR
any reason and resolution for this please?
Time Priority Description
11/06/2023 10:30:13 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2023 10:30:12 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2023 09:22:25 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2023 15:37:45 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2023 12:17:47 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2023 12:17:47 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2023 12:17:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2023 12:17:42 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2023 09:14:4 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2023 09:03:39 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2023 05:29:39 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2023 05:29:39 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2023 21:16:9 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2023 19:17:41 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Answered! Go to Answer
on 15-06-2023 21:02
actioned. please note, this is a issue for multple addresses. we are aware of 1 problem, the pit by us , the tap box has water damage to 2 ports. but due to noise/interference will also need checking to its input and back to source.
on 15-06-2023 21:02
on 16-06-2023 13:18
on 18-06-2023 14:58
Thank you for providing your BQM @ne
You can post a live link to your BQM that we can see and check everyday without needing to post a new image each day.
If you still need further support on this, I can see that my colleague is supporting you via private message. Please respond to their questions and they'll be able to support further in investigating this for you.
on 18-06-2023 15:27
on 18-06-2023 16:21
on 14-07-2023 19:47
hi, had tech visit last Saturday, confirmed my findings and noise on the tab board in pit. said it will be passed to networks to visit on mon/tue. but no1 has been yet. can you see where they have got to please, and see tonight's grab of qos. ive has faster dialup connections.
on 16-07-2023 14:54
Hi ne, thanks for the message, The network teams are independent. The teams will access the network and they if needed make the changes.
Can you let us know if anything change after the weekend and continue to monitor the connection with the BQM ^Chris.
on 24-04-2024 12:39
hi, issue has returned, was supposed to have been passed to networks as signal into the tap box was very noisy too.
on 26-04-2024 17:58
Thank you for that information ne. We are happy to take a further look into this.
I will private message you now to confirm your details.
^Martin