Pingplotter number of times to trace5/11/2023 In other cases it's necessary to use formal procedures to force their hand. If you're in a fixed term contract and wish to leave, then sometimes VM admit there's a problem without difficulty and let customers go without penalty. If the problem is not officially recognised, then staff will see no fault reference, and can only tell you that they see no over-utilisation report, and because over-utilisation doesn't usually affect power levels or SNR they'll probably telling you that all hub status data looks good, because it does.Īppreciate that's downbeat, but if the latest tech visit doesn't find a fix and the BQM remains the same, then your only options are to tolerate the service or leave. What this means is that there's always a lag of months between over-utilisation developing and being recognised, and then there's usually many months before it will be fixed (in some cases it seems they conclude it isn't economic to fix at all). The measures used and the threshold values are not disclosed. For it to be classified officially as over-utilisation, the problem needs referring to the networks team, they then monitor the situation for a few weeks/couple of months, and decide whether there are any capacity problems, and whether they go over whatever threshold is in use internally. ![]() ![]() There are occaisionally faults that create a similar looking BQM and are not over-utilisation, but they are fairly rare. BQM does look to me like over-utilisation but I suspect at what (for VM) is too low a threshold for them to recognise officially.
0 Comments
Leave a Reply. |