I have to say I'm a wee bit disappointed in the fact that how this has turned out. I was going to post myself the other night about harsh comments, but in the end I bit my tongue and decided it's about time I start taking a back seat as communication for me is difficult and some days I find it hard to get across the point I am trying to make. Part of it could be the pain meds I'm on and the other part FM. I shall be going AWOL within the next few days anyhow as I'm due an operation which will leave me a bit incapacitated for a wee while and its why I'm so busy this week as I try to do what I can before I go in hospital so I've not had much time to spend on the forum. I have tried speech to text but found it doesn't always work well on forums for the posts I tend to make.
That leads on to what happened last night, I was aware of g3uiss's situation which is why I was trying to help and see if I could see anything, or at least any pointers that could assist if he did have to call out an engineer.
The line is performing below the MGAL, it used to be fine until he had problems with water in the DP. Although I didn't know until very recently g3uiss is fairly local to me on a neighbouring exchange and I know there is no RF in this area. Bear in mind also that his VDSL line does not exhibit those same blank tones either. I still maintain I've not seen anything like that before in 15+ years of reading stats, so I feel it is right to point it out.
Whilst I agree it may be a red herring to the overall problem - something is causing those blank tones and its interesting that hlog with the Zyxel modem is fine as is QLN... so what later causes no bit load? Am I not supposed to comment on something abnormal?
The line is quite obviously banded, you also have to consider what caused DLM to take interest in the line so quickly after a line reset. There's several indicators that it was MBTR rather than MBTE.
- Err Secs within MBTE limit
- Why banded but not interleaved. WBC DLM should opt for INP (Interleaving) if it was through Error rates.
- The presence of LOS and quite a lot of LOFs.
Whilst I appreciate that LOFs may not always cause a full resync it marks a period of short period time when the line is unavailable. There's a subtle difference between resync and retrain. Just about every technical document I checked classed LOFs as critical requiring either resync or retain. Whilst I note what ejs said about "not a resync as we know it". I think that bearing in mind knowing that DLM was highly likely to be taking action through MBTR figures rather than MBTE.
OK so I sidetracked a wee bit with the mention of RDI's but TBH I still think it was a valid point to make. What if DLM is ignoring the RDI markers (which indicate that the LOF was caused by something other than and SEF causing the LOF). It ignores Dying Gasp messages and still counts LPRs as a retrain, so I feel I was quite justified to wonder if there was the possibility it could be doing similar with LOF's that strictly speacking should be ignored because they have an RDI marker. I still feel justified in bringing up the topic because it may well explain why several other lines in the past have attracted DLM intervention when the resync count wasn't quite reaching the full total. It is definitely something to ponder over so therefore I make no excuse for raising it.
I repeat no matter what technical journal you look at, they all class the following as not just error states, but critical and the causes for loss of sync
- LOF (There should be an RDI marker if not caused by SEF - ie DLM initiated type resync at DSLAM)
- LOL
- LOS
- LPR (This is usually EU disconect of modem - and we know for counts this and ignores the dying gasp signal)
Anyhow back to g3uiss's problem. I feel that he should go ahead with the OR visit. Something is constantly causing DLM to take an interest and further cripple his speeds. It doesnt do that for nothing and its why I said I was not too happy with the LOF count.
What is causing the LOF's is another matter. I find it curious the Zyxel marked those tones during the sync process and whilst its not what is causing DLM to freak out, it still leaves the possibility that there is something causing retrains. Thus I feel it would be beneficial to mention to the engineer that DLM probably banded the line due to MBTR (retrains) rather than MBTE (Errors).
Finally whilst the Zyxel wasn't on very long, it does look like the error rate was slightly less during that period. The SNRM is also higher which means he should get a better sync speed with it if wasnt for the fact the line wasn't banded. I feel it may be beneficial at some point to run the Zyxel for a longer period to get a better picture. However not now as an engineer is coming on Friday so let him see it in its current state with the HG612
I'm in no hurry to get the VMG1312 back. I currently have a VMG8324 on my line and when I get chance I have a VMG8924 to put on and VDSL for me is off the radar for a while. My own line has just dropped below MGAL, but atm I have other things on which mean that now is not best time for logging faults with PN if I'm not going to be here or in a position to be swapping out modems myself.
What may be beneficial that if after the Openreach visit, the VMG1312-B10D does perform better on your line purchase of a B10A variant may well eke out more from your connection.
OK I'm done - hitting send typo's and all.