Print

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

[tommy45]

Last night for some reason unknown my connection lost sync, and looking at the TBBQM it was for a longer time than the normal DLM resync
And looking at another MDWS user who i know has a connection in the same town as me and different cab, they too had a loss at the same time their TBBQM confirms this, there is also another connection showing a loss at the same time,
So could the reason be due to OR updating the firmware in cabinets, as a network issue wouldn't cause a loss of sync, and my error rates lately have been well within the params, So i would like to know why I have had some sync stolen ?

[ejs]

The cabinet firmware version (or vendor-specific bytes) is visible in the output of xdslctl info --vendor, so you might be able to see when it changes.

[tommy45]

The cabinet firmware version (or vendor-specific bytes) is visible in the output of xdslctl info --vendor, so you might be able to see when it changes.

Well nothing seems to have changed, no logical reason  for it

[burakkucat]

Perhaps there was a need to work "upstream" of the cabinet DSLAM, i.e. at the OLT at the fibre head-end exchange, and a remote re-start of the DSLAMs was found to be necessary.

[tommy45]

Perhaps there was a need to work "upstream" of the cabinet DSLAM, i.e. at the OLT at the fibre head-end exchange, and a remote re-start of the DSLAMs was found to be necessary.

Maybe, But if they knew it would likely cause downtime, they usually give notice in advance to ISP's, and checking my Area code there's nothing listed,

[burakkucat]

. . . if they knew it would likely cause downtime, they usually give notice in advance to ISP's, . . .

Indeed, yes.

I suggest that no downtime was expected but some subsequent event ultimately made a remote DSLAM restart a necessity.