G.INP how to tell with unlocked HG612? High Ping on FTTC

Hi All,

So I had various latency problem with my line in last month. BTOR attended
Today and found "tiny" fault on my line. As it was third time BTOR is attending to reported "fault" on my line he decided to swap wire pair going from green cabinet to man whole outside my house. He then told me he will reset DLM via phone call.

The new line has same speed as it was before I've noticed fault, but now it's stable.
However the latency has significantly increased. I remember back in August 2014
ping to certain BBC IP was around 11ms, yesterday before reporting fault it was already at high 20ms, Today is at 27ms.

In total I've restarted my modem three times Today each time getting different plus.net gw, all with this high latency.

Up till Today the modem I've used was ECI. However when I've noticed latency I've
put on recently purchased HG612 which I've unlocked. The latency remained as high.

Any idea, what's going on and why ping to be so high?

Below are some stats

ThinkBroadband Stats

# xdslcmd profile --show

Modulations:
G.Dmt Enabled
G.lite Enabled
T1.413 Enabled
ADSL2 Enabled
AnnexL Enabled
ADSL2+ Enabled
AnnexM Disabled
VDSL2 Enabled
Phone line pair:
Inner pair
Capability:
bitswap On
sra Off
trellis On
sesdrop Off
CoMinMgn Off
24k On
phyReXmt(Us/Ds) On/On
TpsTc AvPvAa
monitorTone: On
dynamicD: On
dynamicF: Off
SOS: On
Training Margin(Q4 in dB): -1(DEFAULT)
#

# xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14900 Kbps, Downstream rate = 49348 Kbps
Bearer: 0, Upstream rate = 12381 Kbps, Downstream rate = 43463 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): 6.3 6.0
Attn(dB): 19.3 0.0
Pwr(dBm): 12.5 6.5
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 43 47
M: 1 1
T: 64 64
R: 10 16
S: 0.0322 0.1233
L: 13416 4154
D: 1009 261
I: 54 64
N: 54 64
Counters
Bearer 0
OHF: 1104461 289737
OHFErr: 3 0
RS: 282619562 1143094
RSCorr: 11611 1060
RSUnCorr: 8 0

Bearer 0
HEC: 2 0
OCD: 0 0
LCD: 0 0
Total Cells: 190944437 0
Data Cells: 7810820 0
Drop Cells: 0
Bit Errors: 0 0

ES: 2 0
SES: 0 0
UAS: 151 151
AS: 2286

Bearer 0
INP: 3.00 4.00
INPRein: 0.00 0.00
delay: 8 8
PER: 2.06 7.91
OR: 92.80 32.32
AgR: 43556.08 12413.50

Bitswap: 1107/1107 11/11

#






# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14713 Kbps, Downstream rate = 49132 Kbps
Bearer: 0, Upstream rate = 12381 Kbps, Downstream rate = 43463 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): 6.2 5.9
Attn(dB): 19.3 0.0
Pwr(dBm): 12.5 6.5
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 43 47
M: 1 1
T: 64 64
R: 10 16
S: 0.0322 0.1233
L: 13416 4154
D: 1009 261
I: 54 64
N: 54 64
Counters
Bearer 0
OHF: 1120895 294044
OHFErr: 3 0
RS: 286826689 2245685
RSCorr: 11666 1060
RSUnCorr: 8 0

Bearer 0
HEC: 2 0
OCD: 0 0
LCD: 0 0
Total Cells: 193785948 0
Data Cells: 7811349 0
Drop Cells: 0
Bit Errors: 0 0

ES: 2 0
SES: 0 0
UAS: 151 151
AS: 2320

Bearer 0
INP: 3.00 4.00
INPRein: 0.00 0.00
delay: 8 8
PER: 2.06 7.91
OR: 92.80 32.32
AgR: 43556.08 12413.50

Bitswap: 1127/1127 12/12

Total time = 2 hours 15 min 14 sec
FEC: 29696 1626
CRC: 6 0
ES: 2 0
SES: 0 0
UAS: 151 151
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 14 sec
FEC: 25 0
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: 5750 795
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 = 2 hours 15 min 14 sec
FEC: 29696 1626
CRC: 6 0
ES: 2 0
SES: 0 0
UAS: 151 151
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 38 min 39 sec
FEC: 11666 1060
CRC: 3 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
#

# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14780 Kbps, Downstream rate = 49348 Kbps
Bearer: 0, Upstream rate = 12381 Kbps, Downstream rate = 43463 Kbps

Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 14780 kbps 49348 kbps
Actual Aggregate Tx Power: 6.5 dBm 12.5 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 5.2 29.3 45.0 N/A N/A 14.1 37.0 58.9
Signal Attenuation(dB): N/A 28.3 43.9 N/A N/A 19.5 36.7 59.0
SNR Margin(dB): N/A 6.0 5.9 N/A N/A 6.2 6.2 6.3
TX Power(dBm): -128.0 -13.8 6.5 N/A N/A 8.5 8.1 6.4
#
#

If G.INP is enabled you will see references to bearer 1 and also the G.INP values shown in the telnet output will be non-zero.

In my experience it took a couple of days between replacing the OR-supplied ECI modem with an unlocked HG612 before the G.INP was enabled (I think the cabinet itself was enabled for G.INP a week or so earlier). When this happened the latency reduced from ~28ms (with both ECI and HG612) to ~18ms, the line has been synced at 80/20 since then and has been very solid and stable.

Your line doesn't yet have G.INP enabled, and is still under the effects of old-style DLM: a delay of 16ms has been specified (8ms downstream, 8ms upstream)).

It looks like a DLM reset has not been ordered (probable), or your line proved so bad, that DLM re-intervened immediately (possible, but unlikely).

What software version do you have in the HG612? (Easiest seen in the GUI). It should be V100R001C01B030SP08, but many are ...28SP10 which is earlier and not G.INP enabled.

Hi,
I have installed SP08 ( Software version V100R001C01B030SP08 ) so it
should be G.INP enabled.

In reply to a post by RobertoS:

What software version do you have in the HG612? (Easiest seen in the GUI). It should be V100R001C01B030SP08, but many are ...28SP10 which is earlier and not G.INP enabled.

Thanks, I can see now where 8ms is listed ( under delay ).
I guess the engineer made mistake and didn't complete request or it didn't go through.
In either scenario if the line doesn't come back to normal in couple days I will ask plus.net
to report this problem to them.

In reply to a post by WWWombat:

Your line doesn't yet have G.INP enabled, and is still under the effects of old-style DLM: a delay of 16ms has been specified (8ms downstream, 8ms upstream)).

It looks like a DLM reset has not been ordered (probable), or your line proved so bad, that DLM re-intervened immediately (possible, but unlikely).

Just to make sure, can you post the result of this telnet command in sh(ell) please?

xdslcmd info --vendor

Hi,

What are the odds of DLM going back to clean state like the fault was never here?

Also, is there a list of planned G.IMP roll outs ?
Perhaps when they put new equipment in, the DLM would be reset for everyone
connected to that cabinet?

# xdslcmd info --vendor #
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 15949 Kbps, Downstream rate = 48868 Kbps
Bearer: 0, Upstream rate = 13275 Kbps, Downstream rate = 44504 Kbps

ChipSet Vendor Id: BDCM:0xa44f
ChipSet VersionNumber: 0xa44f
ChipSet SerialNumber:

You need a DLM reset for a clean state.

I'm thinking that Openreach have suspended G.Inp activations for the time being, such is the scale of the ECI problem.

The Chipset vendor id is BroaDCoM, so it supports G.Inp properly.

In reply to a post by BatBoy:

You need a DLM reset for a clean state.

I'm thinking that Openreach have suspended G.Inp activations for the time being, such is the scale of the ECI problem.

The Chipset vendor id is BroaDCoM, so it supports G.Inp properly.

I guess my problem was faulty line and not G.INP, it's just coincident that the
roll out was around the same time I've noticed the problem.

However I wouldn't mind it being enabled here, probably would help since I've got Huwai modem.

When plus.net support was dealing with my support query, they've posted various stats.
What is interesting that before the same stats had line "interleaving low", now it says "retransmission". However the delay of 8ms up/down seems to be more inline with interleaving tech.

Test Outcome Pass
Test Outcome Code GTC_FTTC_SERVICE_0003
Description No problem found, OAM test is not currently supported on this line.
Main Fault Location OK
Appointment Required N
NTE Power Status PowerOn
Sync Status In Sync
Downstream Speed 46.9
Upstream Speed 12.6
Profile Name 0.128M-49M Downstream, Retransmission High - 0.128M-17M Upstream, Retransmission Low
Copper Line Test Pass
Bridge Tap Not Detected
Radio Frequency Ingress Not Detected
REIN Not Detected
Cross Talk Not Detected

In reply to a post by BatBoy:

You need a DLM reset for a clean state.

I'm thinking that Openreach have suspended G.Inp activations for the time being, such is the scale of the ECI problem.

The Chipset vendor id is BroaDCoM, so it supports G.Inp properly.

Edited by deleted (Tue 28-Apr-15 22:22:12)