New BB FEC errors
- Thread starter thenewoc
- Start date
Connection has been up for almost the last 4 days so how do these look now?
Uptime: 3 days, 17:54:00
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 988 / 7,146
Data Transferred (Sent/Received) [GB/GB]: 1.40 / 25.48
Output Power (Up/Down) [dBm]: 12.7 / 0.0
Line Attenuation (Up/Down) [dB]: 23.8 / 43.0
SN Margin (Up/Down) [dB]: 12.3 / 12.7
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 734 / 0
FEC Errors (Up/Down): 0 / 966,800,851
CRC Errors (Up/Down): 31 / 1,369
HEC Errors (Up/Down): 26 / 8,711
Uptime: 3 days, 17:54:00
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 988 / 7,146
Data Transferred (Sent/Received) [GB/GB]: 1.40 / 25.48
Output Power (Up/Down) [dBm]: 12.7 / 0.0
Line Attenuation (Up/Down) [dB]: 23.8 / 43.0
SN Margin (Up/Down) [dB]: 12.3 / 12.7
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 734 / 0
FEC Errors (Up/Down): 0 / 966,800,851
CRC Errors (Up/Down): 31 / 1,369
HEC Errors (Up/Down): 26 / 8,711
- Joined
- 9 Apr 2012
- Posts
- 13,166
Openreach go to the green FTTC cabinet and move your line (pair) over to a different port on the DSLAM. It eliminates the DSLAM as the issue.
If that doesn't help you can push until you eventually get a pair change (which may or may not make a difference).
If it's still happening after a pair change is done, it's probably REIN and the REIN team can get involved.
Went back to the twitter support team and got the closed fault rejected, got to go back in 48hours for BT wholesales response.
- Joined
- 9 Apr 2012
- Posts
- 13,166
Don't let them take the easy option. Tell them you want a lift and shift and a pair change.
Yeah there's another engineer coming today, his notes are told to check for rain interference or something, lol.
Been back to BT so many times now that a specific support person has taken control of my ticket. Lets see what happens.
Been back to BT so many times now that a specific support person has taken control of my ticket. Lets see what happens.
- Joined
- 9 Apr 2012
- Posts
- 13,166
Just persevere. Eventually you'll get a good OR engineer
I'd try and get a D-side change done and then REIN can be investigated if that doesn't help.
I'd try and get a D-side change done and then REIN can be investigated if that doesn't help.
- Joined
- 9 Apr 2012
- Posts
- 13,166
Something just occured to me, what modem are you using?
HG612 unlocked. Cab matches vendor.
- Joined
- 9 Apr 2012
- Posts
- 13,166
Can you make a new thread mate? I feel like we've hijacked the OP's thread here.
- Joined
- 9 Apr 2012
- Posts
- 13,166
OP, what modem are you using?
The OPs issue is NOT likely to be a HR fault IMO. A HR fault will result (interleaved or not) in a far greater decrease in speed. His prior speed before any issues was 9Mb it is not about 7.5Mb that is a 1.5Mb loss (which would equate to the line now being interleaved).
A HR fault will also not necessarily show itself as noise on the phone line either. It is more likely to be seen as the connection having issues remaining connected when the phone is off the hook, in use or the receiver is placed back down. Those are the only time the SERIOUS voltage will change with a HR fault at the user end.
His post with 6 and 41 Million FEC and just under 8 hours of up time http://forums.overclockers.co.uk/showpost.php?p=28322398&postcount=12 is where he has resynced the line MULTIPLE times during a training period and INP has not been reapplied properly. Entirely normal to happen on an ADSL line if you keep resyncing it. INP values are calculated on a ratio of errors against uptime, keep restarting the connection and it has conflicting data on what the value should be. Resulting in a line which is still interleaved but with no INP to base the interleave calculation from.
Half his issues is he keeps resetting/restarting his connection, obviously in a vain and hopeless attempt in thinking suddenly he is going to get his 1.5Mb extra back. Though to be honest even if he didnt i doubt DLM will be able to sort things out, his line is just poor. Even before it had 'issues' http://forums.overclockers.co.uk/showpost.php?p=28315810&postcount=3 it was suffereing from LOF and LOS, which is far worse a problem than any errors.
His issue is more likely a Earth contact fault. Either in his property (old star based wiring which needs a refresh is an often culprit) or outside at cabinet or exchange. If the OP has a newer style faceplate the first thing he should be doing is trying the test socket. IF speed goes back up using that then he knows its likely poor cable termination his end.
If it is outside of his property (FAR MORE LIKELY IF BROADBAND IS THE ONLY ISSUE THE OP HAS AND PHONE WORKS FINE) its at the exchange and the reason its happened is because when he migrated the connection from SKY (LLU based) back to BT, BT in their infinite wisdom doing the lift and shift from LLU back to BT wholesale gear have decided to connect to an old bunch of pairs which have not been used in years. Probably corroded as hell and the lazy engineer couldnt be bothered to go get the emery paper before crimping him off. SOMETHING i hated when working for them and having to go fix other lazy individuals so called "work".
Calling BT and asking them to test the line (assuming you do not speak to another lazy idiot) should identify the fault. The OP can also try https://www.bt.com/faults which SOMETIMES will pick up line faults and even identify where the fault is.
A HR fault will also not necessarily show itself as noise on the phone line either. It is more likely to be seen as the connection having issues remaining connected when the phone is off the hook, in use or the receiver is placed back down. Those are the only time the SERIOUS voltage will change with a HR fault at the user end.
His post with 6 and 41 Million FEC and just under 8 hours of up time http://forums.overclockers.co.uk/showpost.php?p=28322398&postcount=12 is where he has resynced the line MULTIPLE times during a training period and INP has not been reapplied properly. Entirely normal to happen on an ADSL line if you keep resyncing it. INP values are calculated on a ratio of errors against uptime, keep restarting the connection and it has conflicting data on what the value should be. Resulting in a line which is still interleaved but with no INP to base the interleave calculation from.
Half his issues is he keeps resetting/restarting his connection, obviously in a vain and hopeless attempt in thinking suddenly he is going to get his 1.5Mb extra back. Though to be honest even if he didnt i doubt DLM will be able to sort things out, his line is just poor. Even before it had 'issues' http://forums.overclockers.co.uk/showpost.php?p=28315810&postcount=3 it was suffereing from LOF and LOS, which is far worse a problem than any errors.
His issue is more likely a Earth contact fault. Either in his property (old star based wiring which needs a refresh is an often culprit) or outside at cabinet or exchange. If the OP has a newer style faceplate the first thing he should be doing is trying the test socket. IF speed goes back up using that then he knows its likely poor cable termination his end.
If it is outside of his property (FAR MORE LIKELY IF BROADBAND IS THE ONLY ISSUE THE OP HAS AND PHONE WORKS FINE) its at the exchange and the reason its happened is because when he migrated the connection from SKY (LLU based) back to BT, BT in their infinite wisdom doing the lift and shift from LLU back to BT wholesale gear have decided to connect to an old bunch of pairs which have not been used in years. Probably corroded as hell and the lazy engineer couldnt be bothered to go get the emery paper before crimping him off. SOMETHING i hated when working for them and having to go fix other lazy individuals so called "work".
Calling BT and asking them to test the line (assuming you do not speak to another lazy idiot) should identify the fault. The OP can also try https://www.bt.com/faults which SOMETIMES will pick up line faults and even identify where the fault is.
Well, engineer showed up today and found bugger all.
I explained to him when and how they happened and he basically said "Because they happen at night and my tests are fine during the day there is nothing we can really do since we can't check it at that time."
God dammit. Where's my G.INP.
Thats REIN if it is only happening at specific times of the day or night and unless its inside your home (example happens when central heating comes on or off) then the chances of BT finding the issue outside is slim to none. Use to happen to me dead on 8pm each evening. Was where my old exchange was on an estate and at 8pm some textiles place would start up all their electrical crap for the night shift. Nothing could be done about it.
Pushing until you get a FULL pair change (IE you end up using a different bunch of wires all the way from pole back to exchange) SHOULD ONLY be a last gasp try. Doing that can result in you ending up with an even worse connection than before
Well, new engineer came.
Much better bloke, knew all the technical crap and we spoke about all of it.
He didn't find anything specifically, nor did diagnostics find anything on the last 72 hours. However, he did change the pair and reset the profile for me, just in case.
Gave me his phone number and told me how to listen for REIN, AM radio at 612 and when the errors spike, take it out and listen on the outside where the line comes in. If I hear a low rumbling noise, give him a call and he'll come back (at night even) and take a look himself.
So hopefully I'll find something, and if not, it's another issue and no idea where to go from there. Demand BT turn on G.INP at my cabinet immediately.
- Joined
- 9 Apr 2012
- Posts
- 13,166
Sounds like my visit today, Tephnos!
Pair change and lift and shift done here too
Pair change and lift and shift done here too
Well, he didn't swap my wires out, just lift and shifted them.
Of course, it hasn't fixed my REIN, as I can see from the stats, so no doubt it'll come back worse (not so bad today). bitsNbobs sounds like a former engineer, so he is probably right in that if I can't find anything internal causing it, I'm probably screwed as a new line wouldn't do anything and could make it potentially worse.
Maybe I should hammer on at BT to get G.INP on the cab to fix it that way.
Of course, it hasn't fixed my REIN, as I can see from the stats, so no doubt it'll come back worse (not so bad today). bitsNbobs sounds like a former engineer, so he is probably right in that if I can't find anything internal causing it, I'm probably screwed as a new line wouldn't do anything and could make it potentially worse.
Maybe I should hammer on at BT to get G.INP on the cab to fix it that way.
- Joined
- 9 Apr 2012
- Posts
- 13,166
Like I say, it really depends on the engineer you get.
If you have enough (like I have), you'll eventually get one who will listen to you and do something even if the tests pass.
The most stunning thing about OR is how they all the time say that their tests passed, so there's no issue. If there was no issue, why would I have called you out...
If you have enough (like I have), you'll eventually get one who will listen to you and do something even if the tests pass.
The most stunning thing about OR is how they all the time say that their tests passed, so there's no issue. If there was no issue, why would I have called you out...
- Joined
- 9 Apr 2012
- Posts
- 13,166
Okay yes that is true but what I mean is, I wouldn't have raised a fault if their was no issue.