Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[daveesh1]

Can somebody have a look at my QLN Graph on MDWS (Daveesh1) as it has changed. Looks like it is when I had a Re-sync with firmware upgrade on ECI cabs. Is this now going to be my normal haven't noticed any other issues speed as it was. Will this be ok or do I need a Re-sync

[burakkucat]

It's all fuzzy! Yuck.

My advice would be to power off the modem, disconnect the cable linking it to the filter and to leave the circuit in that state overnight. By giving the DSLAM's line card port sufficient time to "relax" may help alleviate the problem.

[daveesh1]

Will give that a try. If it is the same in the morning when instilled back into life any ideas

[burakkucat]

None, at the moment. Let's see how it looks -- er -- later today. 

[daveesh1]

Well been off all night just powered backup and QLN Graph is still the same. Any ideas

[burakkucat]

I've just been to take a look at the QLN plot. As you have mentioned, it's just the same as before. 

Assuming that your Billion 8800NL has not developed a fault (to be absolutely sure, the only way would be to temporarily use a different device) and that the DSLAM's line-card port has not developed a fault, then we are left considering what might be the cause of that excessive "fuzz" across a wide spectrum? Having typed that, I look at the QLN plot once again and revise my question to ask what could cause that excessive "fuzz" across all DS bands (& not the US bands)? 

Looking at the DLM "traffic lights" on MDWS for your circuit, we see that there is an amber caution for the DS. There is something just not right about the DS segment for your VDSL2 service but I can't see it. 

Perhaps others may be able to input some suggestions, please?

[tickmike]

Can somebody have a look at my QLN Graph on MDWS (Daveesh1) .

For the people who do not go on mdws can you attach your graphs below.

[licquorice]

Haven't got an answer, but mine is like it after a village power cut earlier in the week.

[daveesh1]

Thanks burakkucat. Well this has only happened since the Firmware change on my ECI cabinet which was 4th Feb since there my ES errors have been far less, but since the re-sync this morning they have gone back to values seen before the firmware change. Here is a pdf of the graph

[burakkucat]

Having read licquorice's post, I wonder if there are other people seeing a similar effect in their QLN plots?

If so, then perhaps looking for something in common that has changed may help us understand what is occurring.

In daveesh1's case the point to note is his circuit is connected to an ECI cabinet and that when the line-card's port is interrogated by the CPE, it returns a new "fingerprint".

[licquorice]

I'm connected to an Huawei cabinet.

[burakkucat]

I'm connected to an Huawei cabinet.

Thank you for that information. I should have checked first. 

[licquorice]

Interestingly, since the power cut, my attainable downstream has increased from c 45M to c 51M and upstream from 9.4M to 16M (capped on Infinity 1 so speeds are academic). The last power cut resulted in a temporary increase in speed, presumably due to early sync up before crosstalk disturbers kicked in,  but  soon resulted in a resync and lower speeds. This time the increase has remained with no subsequent resync.

[roseway]

Your experience and the QLN graph are quite similar to mine. Do remember that QLN is only recorded at the time of sync, and if this happened immediately after a power cut it's not too surprising that the conditions were unusual at the time.

[daveesh1]

The first one was after the upgrade on the cabinet so you could say yes for that one, but the resync I did was a controlled one so would of thought if it was due to power cut then it would of come back normal.