cancel
Showing results for 
Search instead for 
Did you mean: 

Misbehaving line - GEA line test request

FIXED
flanzm
Pro
Posts: 251
Thanks: 107
Fixes: 15
Registered: ‎20-04-2016

Misbehaving line - GEA line test request

Hi there,

 

For a long while now I've had an intermittent HR fault on the E side of my line which results in an occasional noisy line but didn't affect FTTC. Normally I could sync for 100's of days continuously without an issue.  At the start of March by SNR margin was even dropped to 4db and it has been fine for a few weeks.

 

On Saturday the voice service went completely dead for 10 mins and then come back - the FTTC service resynced and came back with a 5db downstream margin.  I assume as a DLM response to the outage.

Since Saturday though I've had a couple more resyncs and now G.INP has been applied on the upstream which is worrying.  Weirdly I can't hear any audible noise any more but from looking at the stats below something is definitely going on.

 

Please can you guys take a look at my line as I can't figure out what is likely to be going wrong here.

 

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 29014 Kbps, Downstream rate = 68864 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 69346 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.1 11.7
Attn(dB): 15.1 0.0
Pwr(dBm): 12.6 6.8

Total time = 1 days 14 hours 37 min 22 sec
FEC: 5122301 137814
CRC: 1662 19272
ES: 38 17731
SES: 31 0
UAS: 241 211
LOS: 3 0
LOF: 25 0
LOM: 0 0
Latest 15 minutes time = 7 min 22 sec
FEC: 33 7
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 59 19
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 14 hours 37 min 22 sec
FEC: 4466 1032
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 7358 764
CRC: 555 255
ES: 10 248
SES: 10 0
UAS: 36 26
LOS: 1 0
LOF: 9 0
LOM: 0 0
Since Link time = 14 hours 40 min 41 sec
FEC: 4482 1035
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#

5 REPLIES 5
Mav
Moderator
Moderator
Posts: 22,371
Thanks: 4,725
Fixes: 514
Registered: ‎06-04-2007

Re: Misbehaving line - GEA line test request

Moderator's note by Mike (Mav)

A duplicate post has been released from the Spam Filter and then removed.

Forum Moderator and Customer
Courage is resistance to fear, mastery of fear, not absence of fear - Mark Twain
He who feared he would not succeed sat still

flanzm
Pro
Posts: 251
Thanks: 107
Fixes: 15
Registered: ‎20-04-2016

Re: Misbehaving line - GEA line test request

Just for info it's resynced again this morning with thousands of FEC's on the upstream - there must be a fault on this line surely ?

ejs
Aspiring Hero
Posts: 5,442
Thanks: 631
Fixes: 25
Registered: ‎10-06-2010

Re: Misbehaving line - GEA line test request

Considering that the vast majority of the VDSL2 upstream frequencies are well away from the voice range, having G.INP on the upstream shouldn't really be any different to having G.INP on the downstream? As in, it doesn't necessarily imply that your line must have some terrible fault. Considering the upstream SNRM is fairly high due to the line achieving the maximum rate with plenty to spare, you'd perhaps expect the error rate to be lower, which I'm guessing it is now that both up and down have G.INP.

Thousands of FECs is a negligible number.

flanzm
Pro
Posts: 251
Thanks: 107
Fixes: 15
Registered: ‎20-04-2016

Re: Misbehaving line - GEA line test request

Thanks.  Just checked again and it appears that the resync was to reduce the downstream SNR margin back to 4db.

I think you're right.  It looks like DLM is trying stuff out on my line to decide what is best.  The reason I suspected it was a fault is previously I've had 150+ days of continuous sync.  Like I say maybe I'm just going through a period where DLM is doing it's stuff.

Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Misbehaving line - GEA line test request

Fix
 
Test Outcome Pass
Test Outcome Code GTC_FTTC_SERVICE_0001
Description GEA service test completed and no fault found but unable to check for customer equipment connected to modem.
Main Fault Location OK
Sync Status In Sync
Downstream Speed 72.6 Mbps
Upstream Speed 20.0 Mbps
Appointment Required N
Fault Report Advised N
NTE Power Status PowerOn
Voice Line Test Result Pass
Bridge Tap Not Detected
Radio Frequency Ingress Not Detected
Repetitive Electrical Impulse Noise Not Detected
Cross Talk Not Detected
Estimated Line Length In Metres 405.9
Upstream Rate Assessment Very Good
Downstream Rate Assessment Very Good
Interference Pattern Regular Interference Observed Daily
Service Impact No Impact Observed
Interference Duration Longest Occurrence ; 00:00 to 23:45
Interference Location Unknown
Home Wiring Problem Not Detected
Downstream Policing Discard Rate 0.0
Customer Traffic Level Upstream and Downstream Traffic Detected
Technology VDSL
Profile Name 0.128M-80M Downstream, Retransmission Low - 0.128M-20M Upstream, Error Protection Off
Time Stamp 2017-03-25T15:00:00
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.