As I thought might happen, G.INP is back... seems to be less invasive than last time though...
Stats recorded 03 Apr 2016 09:28:21
DSLAM/MSAN type: IFTN:0xb204 / v0xb204
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 1 hours 37 min 5 sec
Resyncs: 1 (since 02 Apr 2016 21:11:17)
Downstream Upstream
Line attenuation (dB): 11.4 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 51185 20000
SNR margin (dB): 6.4 6.2
Power (dBm): 13.6 -1.7
Interleave depth: 1 1
INP: 48.00 0
G.INP: Enabled Not enabled
RSCorr/RS (%): 0.0000 0.0033
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0.62 1.66
Downstream Upstream
General
rtx_tx 25 0
rtx_c 6 0
rtx_uc 0 0
LEFTRS 0 0
minEFTR 51174 0
errFreeBits 4734471 0
Bearer 0
RxQueue 87 0
TxQueue 29 0
G.INP Framing 18 0
G.INP Lookback 29 0
RRC Bits 0 24
Interleave depth 1 1
INP 48.00 0.00
INPRein 0.00 0.00
Delay 0 0
Bearer 1
Interleave depth 1 0
INP 2.00 0.00
INPRein 2.00 0.00
Delay 0 0
Oddly, last time it was showing as being active, the INP figure was 0, wheras this time it is (correctly, I believe) showing as 48.00. There also appears to be no negative impact on the performance, unlike a couple of days ago.
How come your downstream is so low with that attenuation? mine is at 16.8 dbi and I get the full 80mbps and an attainable of just under 90mbps



Pages in this thread:
Print Thread
