Probably looking at @Hio77, but keen to hear others thoughts.
Chucked a new VDSL connection for a custom, on a POTS line, filter installed.
Stats (from Chorus side) look like this:
DIAGNOSIS PARAMETERS
ACTUAL BITRATE
DOWNSTREAM 113.279 Mb/s
UPSTREAM 29.999 Mb/s
ACTUAL PSD
DOWNSTREAM -56.2 dBm/Hz
UPSTREAM -65.0 dBm/Hz
USER TRAFFIC
DOWNSTREAM Detected
UPSTREAM Detected
ATTAINABLE BITRATE
DOWNSTREAM 113.635 Mb/s
UPSTREAM 36.513 Mb/s
ATTENUATION
DOWNSTREAM 11.9 dB
UPSTREAM 14.8 dB
NOISE MARGIN
DOWNSTREAM 6.1 dB
UPSTREAM 9.9 dB
OUTPUT POWER
DOWNSTREAM 14.5 dBm
UPSTREAM 1.9 dBm
RELATIVE CAPACITY OCCUPATION
DOWNSTREAM 99.0 %
UPSTREAM 85.0 %
LOOP ATTENUATION
DOWNSTREAM 11.9 dB
UPSTREAM 14.8 dB
LINE OPERATIONAL INFO
ESTIMATED ELT DISTANCE 343
LAST STATUS CHANGED 1548120309962
LINE STATUS up
SERVICE STABILITY UNSTABLE
LINE CONFIGURATION
CPE TYPE Unknown
DSL TYPE non.shdsl.opermode vdsl2.g9932.profile.17a, line.type.pots
LINE ID
USER LABEL Unknown
SPECTRUM PROFILE NAME EUBAV-VDSL2-1
SERVICE PROFILE NAME EUBAV-I-FSFS
SERVICE TEMPLATE NAME VDSL2-I-V-ddDLM
So it's rocking it hard on a 17a profile at 110Mbps down, but is "unstable" in Chorus' words and also from our own monitoring via SNMP. I've requested we pull it back to a 9b profile, but wondering if there is a better option. Obviously could just simply be a bad line, so no amount of profile changing will help. But from experience, what do people reckon?
Edit: dam, tables didn't come out properly lol