also just pulled this too:

# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 2
Max: Upstream rate = 25621 Kbps, Downstream rate = 66588 Kbps
Path: 0, Upstream rate = 19999 Kbps, Downstream rate = 56570 Kbps

Discovery Phase (Initial) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3971)
Medley Phase (Final) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3971)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 25621 kbps 66588 kbps
Actual Aggregate Tx Power: 7.1 dBm 13.6 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 3.8 22.1 33.7 N/A 11.1 27.4 43.2

Signal Attenuation(dB): 3.8 21.1 32.7 N/A 11.1 27.4 43.2

SNR Margin(dB): 6.6 6.5 6.6 N/A 6.1 6.1 6.1

TX Power(dBm): -2.2 -21.1 6.5 N/A 10.8 7.9 6.9

#

Thanks

Edited by deleted (Fri 20-Mar-15 18:15:46)

That's interesting -RetrainReasonNegativeMargin 2

In reply to a post by BatBoy:

That's interesting -RetrainReasonNegativeMargin 2

Is that what reason 2 is?

and does that mean the SNR dropped from 6 to below 0?

I think so

In reply to a post by BatBoy:

The post I replied to, obviously.

Duh...

What part of it indicates a fault? There are quite a few components, if you read the post carefully.

But I'll answer anyway... Any of those components can happen without a fault. DLM intervention. Turning FEC on. Turning interleaving on. Dropping Sync speeds. Over-estimated attainable speeds. Every single one can be business-as-usual.

In reply to a post by mlmclaren:

So you agree that some of the settings on the connection need changing or resetting, as you said, interleaving has been set on both downstream and upstream with a delay of 8 (I saw in modem stats)

DLM works by monitoring the rate of errors on your line (most specifically the ES counter); when it intervenes, it does so by setting the INP and delay parameters.

So, while you say that "some of the settings need changing or resetting", doing so *alone* is pointless. You would go back to having lots of errors - and DLM would re-intervene 2 days later.

What you need to do is figure out what was causing the errors, and eliminate that.

However, because DLM has now intervened, the errors will now mostly appear as FECs. To see when those events are happening, you need to run some monitoring software, and use the graphs to work out when the noise happens. Is it all day long? Is it when the heating turns on? etc.

I do agree that DLM has intervened heavily, and further than the norm. It is worth investigating.

and if I'm right, your saying that if their is any fault it is on upstream and not downstream..

DLM intervention is separate - and has happened on both. It suggests your line is receiving interference both up- and down-stream.

Here is my modem stats before the issues!

http://tinypic.com/r/2zz7ur8/8

Yup, they're OK. Ignore the error counts on the GUI, as it gets them mixed up. The text values are better - and the monitoring software uses those.

I think the negative margin indicates a fault rather than normal behaviour.

I don't see any negative margin. Or the line you quoted "That's interesting -RetrainReasonNegativeMargin 2" [puzzled]

Edited by RobertoS (Fri 20-Mar-15 19:02:52)

Just updated my modem firmware info here have noticed slight increase as mentioned in the link.