>>> It doesn't bloody work !!!!!!!!!
If this is true and from Erics case (and several others in the past) then it doesnt always appear to work as it should.
Asking the ISP to permanently set the depth of interleaving makes sense and should hopefully resolve the issue.
I could be wrong, but I think the minimum figures that can be set are 2 for the upstream and 4 for the downstream. (or at least they used to be).
Unfortunately Kitz, it is true.
There is urban myth amongst engineers and our colleagues at BTw, that a group have been set up to try and give the EU the quickest speeds possible. We believe it to be in India. Truth or otherwise, I and many other engineers find ourselves attending lots of BB faults that have been ticking along just fine for years, and have suddenly started mis-behaving.
On-site diagnostics usually finds that there is nothing wrong with the EU's MPF (Metallic Path Facility), or anything else for that matter. It is generally down to parameter changes being implemented. A simple 'SNR reset' automatically puts the DS and US back to 'Fast Path' and as I've said, the theory is that DLM will change this to 'Interleaved Path' as stabilisation occurs. I can only speak as I find, but 70% of the time, the DS will have reverted to 'Interleaved Path', but the US will remain on 'Fast Path'. On a long'ish line I can see the US errors incrementing at a rapid rate, thus forceing a profile change or a retrain.
The other really annoying thing 'The fabled group' employ, is inputting a 'Banded Profile' via 'Element Manager' on DLM. Prior to receiving WHOOSH access (see Tech Chat thread for more info on this), without contacting BTw we would have no idea that a BP had been implemented !! So in the early days of this ridiculous idea, we would have the EU raising a fault reporting, 'No synch'. Along we go and yes, there would be no synch with our HHT's at the EU's. A subsequent PQT would show a healthy MPF, so off to the Exchange you'd go. Once there the HHT would synchronise, so off to the PCP you'd go. It would indeed synchronise at this point. Hmmm, I would then test the D-side once again for faults and find none, so off to the top of the DP you'd go. Here there would be no synch, so you're left faulting the UG network. The very first time this happened, myself and a colleague had synch in one JUF4, and just 30mtrs away, no synch in that particular JUF4 !! We even swapped pairs between the 2 boxes, but to no avail.
The BP had been set to (cant remember exactly) lets say, 4-8Meg. Therefore the circuit would only work within those parameters. We had roughly 4Meg in the first JUF4, but the added attenuation meant it wasn't achievable 30mtrs down the road. A full day spent on that and all it needed was the BP removing and putting back to 160Kbps-24Meg. This is what
ALL FS Profiles should be set to in my opinion.
Sorry for harping on, but it makes my blood boil when folk start messing around with a perfect working circuit Just for further clarification, everything discussed above only takes place on 21CN circuits, not 'Fixed' or 20CN.
