High Upstream Power Levels

[Osram]

Hi, my upstream power levels are going up again all four channels are currently at 55.3 to 56.3 which I believe should not be above 51, Downstream ranges from 8.2 to 3.8, the hub 5 is fitted wive a 16 decibel attentuator as fitted by the last of many tech visits, each of them tried various values of attenuators. My undertanding is that  higher levels of attenuation lower Downstream levels but increase Upstream levels and vice versa? The high power levels seem to cause many recorded fault and ultimaly a modem self reboot, then the saga starts again, this happens every couple of weeks.

Is it still possable to get a tech to move my conection to a lower power tap in the local box? Or are there there any other remidies?

[Tudor]

You still need a technician’s visit to sort it out. The type of attenuator normally used by VM is a forward path attenuator that only affects the downstream level. I think your problem lies in the cabinet. 

[Osram]

Thanks for your comments, I'm hoping a Forum Team member will pick up on this and arrange a tech visit.

[Martin_N]

Hi Osram,

Thank you for your post. I'm very sorry to hear about the issue you've had with your broadband service. 

I am happy to take a look into this to see what is needed to resolve this. 

I will private message you now to confirm your details. 

^Martin

[Omadawn]

Out of idle curiosity, how far away are you from the street cabinet, the figures you have posted and the fact that they have slapped a 16 dB attenuator on but some of the downstream channels are at 8 dBmV would indicate that you are quite close.

Anyhow, you have an upstream issue and this is more than likely a bad joint somewhere between you and said street cabinet. This needs to be found and rectified and then stop messing about with forward path attenuators and connect you to a more suitable tap in the cabinet.

Of course that means getting a tech visit by someone who actually does understand how this stuff works, but that’s another issue!

[Osram]

Hi Omadawn

Nice to hear from someone who is on the ball, you are correct, according to Google earth I am 67 meters from the local box. And your view of their techs is equaly accurate, see one of my previous posts that was never fixed but quickly forgotten :-https://community.virginmedia.com/t5/Networking-and-WiFi/Hub-5-Time-sync/m-p/5334851#M547026 Thanks.

[Osram]

PS

With such a short run of cable you would think it would not be that hard to find a fault? 

[Osram]

PPS

PPS There are only 2-3 other Virgin home connections btween me and the box.

[Osram]

PPPS (how many of these are allowed?)

Part of my current log :-

17-07-2023 20:13:49  critical  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

17-07-2023 20:11:51  critical  Received 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;

17-07-2023 19:43:54  critical  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

17-07-2023 19:43:41  critical  Received 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;

17-07-2023 19:37:50  critical  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

17-07-2023 19:35:57  critical  Received 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;

17-07-2023 19:33:20  critical  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

17-07-2023 19:33:16  critical  Received 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;

17-07-2023 19:31:46  critical  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

17-07-2023 19:22:46  critical  Received 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;

17-07-2023 19:21:59  critical  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

17-07-2023 19:18:13  critical  Received 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;

17-07-2023 19:17:42  critical  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

17-07-2023 19:15:51  critical  Received 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;

17-07-2023 19:14:13  critical  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

17-07-2023 19:08:46  critical  Received 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;

17-07-2023 19:08:13  critical  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

17-07-2023 19:01:38  critical  Received 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;