Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: kitz on October 17, 2014, 07:34:16 AM
-
hmmm.. yesterday I was on the way to a class so couldnt stop, but I noticed that there was a guy working on one of the ECI cabs on the dock road.
Weird thing is I dunno who was working on the cab because there was no BT van.. it was a white estate type car but with white panels (not glass) and I couldnt see any livery on it. The cab was wide open and I got a quick glimpse of the dslam and line cards as I drove past.
I notice this morning that at 4:18 I lost sync (PTM) and it was off for just under an hour, so it looks like someone was working on my cab during the wee small hours.
I cant see anything too much different with my stats... but my upstream SNRm is now a bit weird.. cant recall seeing it like that since my HR fault was fixed.
----
Edited by admin
Topic split from here (http://forum.kitz.co.uk/index.php?topic=14555.0) as now it needs its own thread.
-
hmmm.. yesterday I was on the way to a class so couldnt stop, but I noticed that there was a guy working on one of the ECI cabs on the dock road.
Weird thing is I dunno who was working on the cab because there was no BT van.. it was a white estate type car but with white panels (not glass) and I couldnt see any livery on it. The cab was wide open and I got a quick glimpse of the dslam and line cards as I drove past.
I notice this morning that at 4:18 I lost sync (PTM) and it was off for just under an hour, so it looks like someone was working on my cab during the wee small hours.
I cant see anything too much different with my stats... but my upstream SNRm is now a bit weird.. cant recall seeing it like that since my HR fault was fixed.
Sounds a bit like what Chrysalis described happening in his third post. They must be doing upgrades then, but to what end I guess nobody yet knows. It can only be assumed that it's related to supporting vectoring in the future.
-
kitz mine wasnt down for an hour, was more like about 5 minutes. The guys working on mine did have an openreach van.
-
hmmmm.. I just had a thought - for the past month or so, Ive been seeing some carp speeds. Because it co-incided with the problems with BNGs I at first thought it was a Plusnet issue.
However, Plusnet assured me that there was no bandwidth capacity issue on their pipes.. This is the response I got
As far as we're aware there's no congestion issues on our network, we put additional bandwidth in for iOS8 above and beyond what was needed so the network has plenty of spare bandwidth right now. Checking through the monitoring there's no packet loss or any interfaces that are maxed out anywhere on the network.
Looking at the quality reports I can see some packet loss showing on your SVLAN back to the exchange, it's up to 5% last night, that could easily be the cause of a drop to 30Mbps (graph attached for yesterday).
Over the past few weeks things have deteriorated further and each evening I routinely see speeds of circa 20Mbps. Ive not been monitoring it though as 1) I didnt see the point in getting stressed about something that BT would hopefully fix in their own time 2) I could still do most things I wanted to do as my upstream wasnt affected and there was sufficient bandwidth to stream, which is where the vast amount most of my download usage is.
However... if it is backhaul capacity.. I dont see any reason why they should need to switch off the DSLAM for an hour.. unless its to hook up newly blown fibre. In general if new capacity is installed it should be more of a software configuration.. as the SVLAN is the equivalent of an old VP.
Chrys havent you too been seeing some capacity issues at peak? Has that been sorted now?
I guess I shall find out tonight if my speeds have increased so we can rule that out or not
---------
Warning - while you were typing a new reply has been posted. You may wish to review your post.
-
kitz mine wasnt down for an hour, was more like about 5 minutes. The guys working on mine did have an openreach van.
Oh okies - no idea who was working on mine at 4.30am - I was in bed.
The guy working on the cab on the dock road (not mine) was there at about 9am so could be unrelated. Just thought the unmarked van was weird.. and its also not often that you see the actual FTTC cab open.
-
for me plusnet performance seems to have been fixed. I have not tested the last few nights as I have been busy but the nights before that was ok.
I have been deliberately not using the BGN's tho because (a) ipv6 and (b) they keep crashing.
-
kitz mine wasnt down for an hour, was more like about 5 minutes. The guys working on mine did have an openreach van.
Oh okies - no idea who was working on mine at 4.30am - I was in bed.
The guy working on the cab on the dock road (not mine) was there at about 9am so could be unrelated. Just thought the unmarked van was weird.. and its also not often that you see the actual FTTC cab open.
doesnt mean it wasnt related tho, e.g. they could have been reapplying ties one at a time, and I just got lucky mine was one of the first ones, or maybe they had complications on yours, however I would expect them to do maintenance at night not in the day time.
-
The guy working on the cab on the dock road (not mine) was there at about 9am so could be unrelated. Just thought the unmarked van was weird.. and its also not often that you see the actual FTTC cab open.
Van or small hatchback car? If the latter it could well have been someone from Telent, as I seem to recall that only their larger vehicles are actually marked.
Adjustments (physical or configurational) to the FTTC cabinet MSAN will only be carried out by either Beattie Operate or Telent technicians.
-
............... or ECI in-house engineers. :)
Only last year I chaperoned one of these guys on my patch to change out the MK3 VTUC cards that had been installed, as they weren't compatible with the DSLAM software and causing multiple outage issues. The card-switch process (Back to VTUC MK2), literally was a 5 minute process, but of course meant all EU's connected to that particular card losing service for that period.
As an aside, he had un-liveried estate car.
-
Ah, interesting. Thank you. :)
-
:)
-
Mr Telent commissioning a "small" ECI equipped cabinet, somewhere in the Surrey countryside . . .
-
kitz I see you getting US snrm issues as well now. This started since the cab work?
-
by the way ran a speedtest as I remembered. still ok
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww.thinkbroadband.com%2Fspeedtest%2Fbutton%2F14135745826499273088.png&hash=11be9fada2c59f5ab368f9caa5a9b488e84e35c0) (http://www.thinkbroadband.com/speedtest/results.html?id=14135745826499273088)
-
The guy working on the cab on the dock road (not mine) was there at about 9am so could be unrelated. Just thought the unmarked van was weird.. and its also not often that you see the actual FTTC cab open.
Van or small hatchback car? If the latter it could well have been someone from Telent, as I seem to recall that only their larger vehicles are actually marked.
Adjustments (physical or configurational) to the FTTC cabinet MSAN will only be carried out by either Beattie Operate or Telent technicians.
Large white hatchback - estate type. Not a proper van. Only got a fleeting glimpse as I was driving past and I was looking at the cab mostly.
-
kitz I see you getting US snrm issues as well now. This started since the cab work?
Yeah... I just noticed myslef - my upstream has gone crazy since whatever they did last night. ???
Its normally very stable
-
Who thinks the DLM is going to hammer me?
:'( :'( :'(
-
E-yuck! :tongue:
That has got to be a fault! :o
-
Oh... and the capacity issues now seem to have gone!!!!!!
Bit bumpy - but for the past few weeks come evenings Ive been down to at low as 20Mbps. It could be that everyone is out on a Friday evening.. or that they have added more capacity.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww.thinkbroadband.com%2Fspeedtest%2Fbutton%2F141358037137632941919.png&hash=48abdd024693e045e62088cd7e2a8346218a1d01) (http://www.thinkbroadband.com/speedtest/results.html?id=141358037137632941919)
-
Who thinks the DLM is going to hammer me?
:'( :'( :'(
99.7% sure you will escape the dreaded hands of the DLM as the errored seconds is only affecting the upstream if it was the other way round yes I would say you would end up being interleaved with a reduction of the DS sync speed for a few days.
As for the :-\ 3% you will know in the wee small hours if your DLM has taken effect on your line.
-
I notice Ive lost sync a couple of times this evening - so I guess I will have to see if it notices that too :(
-
I notice Ive lost sync a couple of times this evening - so I guess I will have to see if it notices that too :(
remember you are aloud 20 lost sync's in a 24 hour period it's just how close together they are within a 15 minute period that does the damage ;)
-
they were :/
.... and Im not sure I believe the 20 figure - plenty on here seen it happen at much less. I think maxdsl had the DLM kick in after 5... and yes I saw his RADIUS report from PN which would appear to confirm this :(
-
they were :/
.... and Im not sure I believe the 20 figure - plenty on here seen it happen at much less. I think maxdsl had the DLM kick in after 5... and yes I saw his RADIUS report from PN which would appear to confirm this :(
Looking at MDS you had lost 2 sync's within 15 minutes this evening and one at 5am, you should be ok ;)
-
your ES looks ok for DLM (based on graph just over 2000ES a guess) but thats assuming the US has same threshold as DS. I am curious if those errors were service affecting tho.
Kitz I am pretty confident now its ES not CRC, when I left my sync on 79987 for the afternoon barrage of noise, I had 17k crc in a 2 hour period and DLM left me alone, the ES was 500.
-
@kitz Since the downstream looks much the same as usual I would guess that it should not be a line fault but either the DSLAM or the modem. Mostly probably the DSLAM, but I would first swap the modem since that is easy and, if the problem remains the same, it should enable you to be more firm in reporting a fault.
-
The DLM got me and at 5:45 has applied Interleaving and INP.
I'll swap routers in a bit.
@les. Just as an aside my line fault last year only affected my upstream - and eventually voice.
-
Thanks for the aside, I was assuming that as both up and down occur over the same two wires that would be hard to achieve. I think voice can be different as it effectively needs a good DC path with no possibility of working via capacitance coupling.
-
Ive seen quite a few HR type faults were just the upstream is affected and downstream is ok.
When mine got really bad, I could still sync at the 80Mbps and my downstream SNRm would be relatively flat.. but my upstream could only manage a sync in the region of 10Mbps and my upstream SNR was spikey as hell. :/
-
The DLM got me and at 5:45 has applied Interleaving and INP.
Until you can get those US errors under control the DLM is not going to return you back to fastpath and it's a case of monitoring your stats to see if you line fix's itself over the next days or call or use your ISP forums if things have not changed.
It will be interesting to see if those US errored second counts rise again in the evening time.
-
I know. :(
Interleaving has increased my latency by about 7ms.. but done absolutley nothing to arrest the CRCs... which is still the same/slightly worse than yesterday.
I guess we shall see what happens this evening.
-
yeah you was under the 2880/day on that graph, but the errors continued on so I think you got over 2880.
You got some stats from your modem on hourly rate?
Also not sure if the hg612 will save you, if there is a fault or interference any modem will get errors.
-
interesting is that interleaving with the lower snrm seems to be no better than your higher snrm on fast path. Both seem to have equal effect of error mitigation.
My line is also still having US snrm dips but isnt causing errors.
-
interesting is that interleaving with the lower snrm seems to be no better than your higher snrm on fast path. Both seem to have equal effect of error mitigation.
Yep.. I noticed that and said that the application of Interleaving has done nothing to stop the errors.
Put the HG612 back on - that makes no difference either. Still seeing the upstream SNRm spiking and also similar error rates - in fact if anything there is wider variance between the upstream SNRm band with the HG612 and its done a mean spike down to 1dB... so its not the Zyxel.
-
Thinking... if there was a capacity issue.. and you know how I said the other day that if they were just lighting more bandwidth, then normally its just a software config.
However... if it is backhaul capacity.. I dont see any reason why they should need to switch off the DSLAM for an hour.. unless its to hook up newly blown fibre. In general if new capacity is installed it should be more of a software configuration.. as the SVLAN is the equivalent of an old VP.
So what if it was to hook up new fibre.. wouldnt they have to do some rejigging in the DSLAM ie move some lines about so that the new capacity is shared?? So what if Ive been moved on to another port on a different line card - which is duff
I dunno what they do.
Looks like Im going to have to raise a fault.. which is going to be a PITA.. because I know damn well what BT Openreach will say. Theres nowt wrong with your line your syncing at 80 Mbps.. whats the problem? :'(
-
kitz you can check if its specific tones with the problem? on the billion tones can be turned off.
So buy a 8800nl, turn the bad tones off and get your fast path back maybe? :)
I would report the fault, I suspect you will get some crappy engineers initially who will walk after seeing 80/20 and the JDSU passes, then plusnet will end up escalating it before someone with the head on right turns up and fixes it.
But I got a feeling you may get a HR fault showing up on the JDSU,
I know engineers can request a DLM reset before they turn up as my last one did it, as he said DLM can mask problems (which he is correct on) but in your case DLM is failing to mask it.
-
kitz you can check if its specific tones with the problem?
Hard to say where its occurring. U1 and U2 is spiking 5-6 dB.
I would report the fault,
I was going to do so last night, but the PN fault reporting was undergoing maintenance. I shall do in a mo.
DLM can mask problems (which he is correct on) but in your case DLM is failing to mask it.
The DLM kicked in again this morning. It adjusted interleaving depth and has rate limited me to 17Mbps.
Yet again this has done nothing to arrest the error rate which continue exactly the same as before.
-
I lost sync this morning, alerted by tony's system when I checked my email :( After the event DS attainable was shuffling about.
-
The rate limiting is good in my opinion, thats harder for engineers to ignore. They may still babble on about it been a a "up to" service but your line spec should be an easy 20 up.
-
The rate limiting is good in my opinion, thats harder for engineers to ignore.
Yes thats true. Im also waiting to see what tomorrow brings. Any action applied by the DLM so far hasnt made any difference to the amount of errors Im seeing, so Im not sure if its finished with me yet.
If you think the SNRm graph looks spikey, thats nothing to what I see on the SNRm per band - thats real pretty - not ::)
I wonder if the SNRm bands is something that could perhaps be something for Tony to think about if he wants to develop things further.
My CRCs arent any better. Swapping to the HG612 made no difference and in fact Ive put the Zyxel back on, because
1) the line performed slightly better with the Zyxel
2) Two less Ethernet leads dangling across the desk, 1 less power socket in use and 1 less piece of hardware.
I dont seem to be able to view ErrSecs on mydslstats for 3 days. It shows my downstream.. but not any of my upstream. Can you see them.
From looking at DSLstats they dont appear to be any better either.
-
It only seems possible to see your upstream errsecs on mydslwebstats for 24 hours and less. For longer times the scales seem adjusted but nothing shows.
-
Another day.. another DLM.
Interleave depth 325 to 355,
INP 3 to 3.5
Banding 17000 and now capped at 14994
.. and still the errors keep a coming.
What I noticed is that yesterdays banding gave me a SNRm of apprx 9dB and todays banding gives me an SNRm of 12dB
-
kitz please keep us updated with ES counters as well.
-
mydslweb stats show other oddities that I had not noticed. Your upsrteam CRC per minute counts seem to be 0,24,46 or 70 almost all the time ??? --I wonder why other numbers don't see to happen.
I also wonder what upstream error rate will make the DLM happy. Your latest reduction in upstream speed suggests that the previous 24 hours did not make it happy and your latest 24 hours look like more than 60/hour but less than 120/hour. Maybe if it now stays less than 60/hour it will not intervene further.
The most interesting thing will be to find out the cause and correction, but I guess just correcting the fault is your priority!!
-
It only seems possible to see your upstream errsecs on mydslwebstats for 24 hours and less. For longer times the scales seem adjusted but nothing shows.
There seems to be a bug in the Column Charts where if the errors exceed a certain value and count, the bars just don't display, especially Upstream. For the moment, and I know everyone is used to viewing bars for ES, the charts for now display as Line Charts like all the other ones but at least all the values are now visible for the longer periods - even if they do look like a map of the Pyrenees at times
-
mydslweb stats show other oddities that I had not noticed. Your upstream CRC per minute counts seem to be 0,24,46 or 70 almost all the time ??? --I wonder why other numbers don't seem to happen.
Well other numbers do happen but you are not seeing them due to lack of pixels to plot them on for the viewing period/vs pixels available. It does appear strange I admit but looking at the raw database figures, they do tend to be around those values but they are +/- in the detail. If you zoom in to a level that shows individual minutes then you can see there are differences as shown in the zoomed attachment graph.
But there is a definite grouping around the values you mention from the actual uploaded values (US_OHFErr_delta currently as noted elsewhere and used as per BE1's recommendation). Also attached some of the the raw DB figures against time.
-
looking at kitz's US errored second counts on MWS it seems fine now since 13:00 hope thats the start of line going back to normal :fingers:
-
Your upsrteam CRC per minute counts seem to be 0,24,46 or 70 almost all the time
If you could see my upstream SNRm then its not too surprising why the errors follow that pattern. It doesnt show up anything in the combined SNRm, but as I mentioned a few posts back, my upstream SNRm per band paints a pretty picture and far more insight of whats going on. The 3 bands have separated and its like the blade of a saw swinging 1dB either way.
If you think the SNRm graph looks spikey, thats nothing to what I see on the SNRm per band - thats real pretty - not ::)
I wonder if the SNRm bands is something that could perhaps be something for Tony to think about if he wants to develop things further.
Its what Id equate to consistent static noise.. then every so often theres a burst spike.. and its only the larger spikes that are showing up on MDWS.
Looks like somethings changed today and its a lot more stable. Not had chance to look properly yet whats been going on.. and I need to look on the PC really but it appears like Ive had no errors for a large part of the day.
-
But there is a definite grouping around the values you mention from the actual uploaded values (US_OHFErr_delta currently as noted elsewhere and used as per BE1's recommendation). Also attached some of the the raw DB figures against time.
Yep I agree it does, but if you could see my upstream SNRm broken down into bands it would become clear that its also following the same pattern. Take for eg U1 it was swinging between something like 10db - 12db in a jagged saw edge pattern. I cant do a screen cap atm, but I think you can see the saw blade pattern starting to form from an attachment in one of my earlier posts.
-
If you think the SNRm graph looks spikey, thats nothing to what I see on the SNRm per band - thats real pretty - not ::)
I wonder if the SNRm bands is something that could perhaps be something for Tony to think about if he wants to develop things further.
Done :) I haven't double-checked the displayed data against the Database but looking at yours, since it appears to represent a Magnitude 9 on a Seismometer I guess it's correct :o
The entries are at the top of the list under the normal SNRM entry. Hit Update if you don't see them at first on a pane or F5 to get all panes at once.
SNRM
SNRM/Band DS
SNRM/Band US
-
I am also on an ECI cab and with no speed capping my upstream snrm's are always about 6db at sync, with my varying crosstalk the power adjusts to ensure this at sync.
With speed capping if I cap the upstream below 17mb/s the upsream snrm's are always about 9db- The power increases to achieve this -- maybe in an effort to do better.
Variations have always been much as yours is now.
I have never understood why your upstream power and snrm magnitude behaviour is so different. Even when my line first started and the downstream attainable was 108 the upstream was held done by a very low upstream power.. It makes me wonder if all ECI DSLAMs are the same or have the same settings
-
If you think the SNRm graph looks spikey, thats nothing to what I see on the SNRm per band - thats real pretty - not ::)
I wonder if the SNRm bands is something that could perhaps be something for Tony to think about if he wants to develop things further.
Done :) I haven't double-checked the displayed data against the Database but looking at yours, since it appears to represent a Magnitude 9 on a Seismometer I guess it's correct :o
The entries are at the top of the list under the normal SNRM entry. Hit Update if you don't see them at first on a pane or F5 to get all panes at once.
SNRM
SNRM/Band DS
SNRM/Band US
Thanks - thats brilliant.
That particular graph isnt as bad though as the day before.. I couldn't do a screen grab last night as I wasnt at the PC and I hadn't even checked out properly what the line had been doing as I'd been out and busy trying to re-arrange things so I was free on Wed if a BT engineer needs to come.. and I'd typed out the line behaviour from memory.
Yesterday the line was a lot better no CRCs/Err secs and although U0 is still jagged.. previously all 3 bands were behaving erratically. Something changed yesterday and the line is now pretty stable.
Whether the added INP has affected that or not Ive no idea, but I dont think that would account for U1 and U2 loosing their jaggedness.
What is strange is that today the separate bands look in much better shape than they have been for the past 5 days.. yet for the first time the combined SNRM graph for this morning is more bumpy than it has been since this started. ???
--
Edited to add graph
-
I am also on an ECI cab and with no speed capping my upstream snrm's are always about 6db at sync, with my varying crosstalk the power adjusts to ensure this at sync.
With speed capping if I cap the upstream below 17mb/s the upsream snrm's are always about 9db- The power increases to achieve this -- maybe in an effort to do better.
Variations have always been much as yours is now.
I have never understood why your upstream power and snrm magnitude behaviour is so different. Even when my line first started and the downstream attainable was 108 the upstream was held done by a very low upstream power.. It makes me wonder if all ECI DSLAMs are the same or have the same settings
I should imagine they do have different settings. Ive noticed that my PSD mask doesnt always follow the same shape as others. Note how on my D1 bitloading I dont get as much PCB at around tone 255.
Im very close to the exchange which I can see from my window [well I could, but in summer a neighbours tree in full leaf has grown taller and mostly obscures it atm]. Its already known that BT had 4 possibly 5 different PSD masks depending upon distance from the exchange for adsl2. So theres bound to be different profiles on the FTTC dslams. These will probably have to take into account not just distance from the exchange but also distance from the cab.
-
That particular graph isnt as bad though as the day before.. I couldn't do a screen grab last night as I wasnt at the PC and I hadn't even checked out properly what the line had been doing as I'd been out and busy trying to re-arrange things so I was free on Wed if a BT engineer needs to come.. and I'd typed out the line behaviour from memory.
You probably know but if not, you can get any graph for any single day by going to the Range date option (rather than current) and then select both days the same. Attached is the 19th for instance. Along with some -ve spikes....
-
In spite of DLM variations I will be very interested in how your line goes from now on and whether there is a fixable fault. For the last 24 hours all Your SNRM wobbles and spikes are quite similar to those on my line. To be more similar you will need to get odd ES/SES/CRC spikes on top of your fairly low background of errors. My background is about 5 Es per hour if you remove the 10-20 or so minutes each day with spikes that can contribute most of the days error count.
-
Thanks tony I was aware of that handy feature. :) It was because I was looking at DSLstats anyhow that I grabbed a copy of that.
For the last 24 hours all Your SNRM wobbles and spikes are quite similar to those on my line.
Yeah since the Errors stopped it is very wobbly and not its usual behaviour. Its currently wavering on a downward trend.
It is very strange that the wobbles in the total SNRm only started to show when the vast majority of the errors stopped. For now the individual bands seem much healthier, yet the overall SNRm isnt. Im not sure how much behaviour is being masked by DLM intervention.
-
Ive just been advised that an engineer visit isnt deemed necessary. Instead BT have raised an exchange task "to check a number of issues related to your circuit". The next update from BT is due after 48 hours.
-
Ive just been advised that an engineer visit isnt deemed necessary. Instead BT have raised an exchange task "to check a number of issues related to your circuit". The next update from BT is due after 48 hours.
If I was in exactly your situation (knowing, as I do, the precise "lay of the land" of Maison Kitz, the PCP through which your line is connected, its fibre twin cabinet and the telephone exchange) I would have replied to that message to say "I'll be waiting outside the main door of the telephone exchange at 0900 hours, precisely, ready to accompany your technician whilst (s)he investigates the issues with my circuit." ;)
-
I may take a stroll to replenish food supplies at some point ;). but its not my intention to hover outside a cab for most of the day. ;D Although Im in sight of the exchange.. the cab isnt.
-
I may take a stroll to replenish food supplies at some point ;). but its not my intention to hover outside a cab for most of the day. ;D Although Im in sight of the exchange.. the cab isnt.
Just to let you know your back on US fastpath and US sync is rising again :)
-
Yep something happened on Wed and all the errors abruptly stopped generating. So I guess they tweaked something. They still have a task outstanding though which means atm my ISP cant even see what speed Im syncing at.
I noticed that it seems to be going in the right direction though this time :) Ive had a DLM change practically every day for a week now.
-
Just a note on this - my line seems to be in limbo atm, as BT still have an 'open fault' that they havent responded to.. and my ISP cant perform any tests nor even see what speed Im syncing at. They cant even perform a whoosh or check the BT RADIUS. So are chasing with BT.
BT were supposed to do something on Wednesday - which they obviously did because all the errors suddenly ceased, but Im assuming the line is possibly in limbo whilst they monitor it. Either that or someones forgotten to close off the fault and not add any notes.
DLM changed again this morning though and has removed all banding, interleaving and INP.
----
btw as an aside... has anyone else ever seen the DLM do its changes at times between 10 and 11 am? I thought they were supposed to happen overnight.
-
btw as an aside... has anyone else ever seen the DLM do its changes at times between 10 and 11 am? I thought they were supposed to happen overnight.
According to all the reliable reports that I have read, the "window of DLM change" appears to be between 0200 and 0600 hours. The latter end of that window tends to predominate.
-
Thank you for that confirmation b cat. I thought that was supposed to be the case.
I was at a bit surprised at 2 changes now occurring between 10 and 11am, which I've not seen anyone else reporting before.
-
My last DLM change occurred at 7:40am a few days ago, so sometimes it can be a little later than the usual expected time range.
-
Perhaps the "window" has been (is being) deliberately moved to a later time period? :-\
-
I believe between 02:00 & 06:00 are the usual times, but I have seen what appear to be DLM resyncs occur at other times (both earlier & later).
This is the timing of my most recent 'DLM' resync:-
08/10/2014 00:45 - RESYNC detected (DS 22399 Kbps, US 4295 Kbps), AS = 37, Retrain Reason: 1
The resync must have occured during the previous minute as the AS value = 37 at the time the data was harvested at a few seconds past 00:45
FWIW, 8 DS LOF & 1 LOS delta values were reported following the resync.
-
Thanks, I just thought 09:47 and 10:47 was a little late in the day to be doing DLM changes :D
-----
PS should also say that the congestion of 20-30Mbps speeds I had been seeing each evening for the previous month, immediately cleared on the day that BT did whatever they did at the exchange.. and Im back to full speeds again.. so IMHO they were messing with something to do with my SVLAN...
and as a 2nd thought.. I saw BT laying some new blown fibre down the main road.. I should look up the date that was cause I sent a message to someone else about it... but at a guess it would be appx 6wks ago.