Last message from OR engineer….

Hi. SFP has been replaced - all connections cleaned - hopefully it will work as it should and errors will disappear.

So far BQM looks clean since his message.

Edited by SamBGB (Sat 16-Aug-25 09:16:57)

Looks like this resolved the issue no longer seeing packets dropped.

In reply to a post by Pheasant:

In reply to a post by SamBGB:

The Openreach engineer has attended and feels everything in the property looks good, however he did mention there where BIP errors and said that it could be a faulty or loose SPF connector at the exchange (there has been a batch of them recently apparently) so he is going to go ahead and re-seat or change it or something.

...will be bit errors rather than BIP errors.

If it was in the exchange at the OLT, then it would also be affecting all other customers on that PON - though it may not be reported / checked.

No, he meant BIP. Bit Interleaved Parity. They will of course produce bit errors but BIPs are what count up when there's an issue with the optical section.

Everyday is a school day as they say 😀

It must be nearly 30 years since I last used a BERT in anger, during a gap in study / leave whilst working in the datacentres of Reuters.

In reply to a post by SamBGB:

Last message from OR engineer….

Hi. SFP has been replaced - all connections cleaned - hopefully it will work as it should and errors will disappear.

So this replacement is not in your equipment, but presumably somewhere at the other end of the fibre?

Thats correct.

The notes on the job:
Issue caused by wear and tear on the connector port at the AGG-Node; resolved by cleaning the port.

In reply to a post by SamBGB:

Thats correct.

The notes on the job:
Issue caused by wear and tear on the connector port at the AGG-Node; resolved by cleaning the port.

Earlier in the thread you said

The Openreach engineer has attended and feels everything in the property looks good, however he did mention there where BIP errors and said that it could be a faulty or loose SPF connector at the exchange (there has been a batch of them recently apparently) so he is going to go ahead and re-seat or change it or something.

But, as a rule, the agg node will be out on the highways and byways somewhere, not in the exchange. I wonder where the truth actually lay ?
It would be fairly unusual for the common or garden engineer to be ferreting about in either the agg node or the head end.

Glad it got sorted though, and thank you for updating the thread.

It’s a very inconsistent explanation. At one point there was talk of an SFP problem in the exchange. OK fair enough, must be rare but not impossible.

Then it transpires that something was amiss at the aggregation node. Except there are no connectors (or any actives) to be loose, dirty or faulty there, just splicing…weird. The engineer that attends your house isn’t going to re-splicing anything at an AgNode or playing about with actives on the OLTs. The latter usually takes more than a few days or more to get booked in etc.

At least the OP is sorted, but the explanation is v. opaque.

Edited by Pheasant (Mon 18-Aug-25 14:38:25)

In reply to a post by Pheasant:

It’s a very inconsistent explanation. At one point there was talk of an SFP problem in the exchange. OK fair enough, must be rare but not impossible.

Then it transpires that something was amiss at the aggregation node. Except there are no connectors (or any actives) to be loose, dirty or faulty there, just splicing…weird. The engineer that attends your house isn’t going to re-splicing anything at an AgNode or playing about with actives on the OLTs. The latter usually takes more than a few days or more to get booked in etc.

At least the OP is sorted, but the explanation is v. opaque.

Send three and fourpence, we are going to a dance.

In reply to a post by rippedcotton:

In reply to a post by Pheasant:

It’s a very inconsistent explanation. At one point there was talk of an SFP problem in the exchange. OK fair enough, must be rare but not impossible.

Then it transpires that something was amiss at the aggregation node. Except there are no connectors (or any actives) to be loose, dirty or faulty there, just splicing…weird. The engineer that attends your house isn’t going to re-splicing anything at an AgNode or playing about with actives on the OLTs. The latter usually takes more than a few days or more to get booked in etc.

At least the OP is sorted, but the explanation is v. opaque.

Send three and fourpence, we are going to a dance.

What did you mishear Brian ?