G.INP Retransmission question

Hi all

Does anyone know what criteria is usually needed for a G.INP High Retransmission line to go back down to a G.INP Low Retransmission state?

TIA

The DLM will do it on it own - it will take up to few weeks to get retransmission low. Nothing ISP or you can do anything about it.

My G.fast was on high retransmission for 9 days before went back to low. My past FTTC take 4 days to get it back to low.

In reply to a post by Bobby_Valentino:

Hi all

Does anyone know what criteria is usually needed for a G.INP High Retransmission line to go back down to a G.INP Low Retransmission state?

TIA

No idea what the criteria is. Personally I think the FEC numbers play a part.

If you cap your downstream sync speed for a few days the DLM will move you to Retx Low, increasing throughput. You can then remove the cap and it will stay on Retx Low.

The DLM seems to prefer Retx High, particularly on Broadcom chipsets if the SNRM target has been lowered from 6dB.
A sync speed cap gives it a nudge to Retx Low.

If you tell me your current downstream sync speed I'll suggest a cap that will work. The lower the cap the more likely it will work, and sometimes quicker too.

This has been discussed extensively on the kitz forum. I've only seen the cap not work on 1 occasion. That was a line with Vectoring and the user was very stubborn in refusing to increase the cap sufficiently.
There's probably 30-40+ examples of it working.

Edited by j0hn83 (Fri 11-Feb-22 16:17:40)

In reply to a post by j0hn83:

In reply to a post by Bobby_Valentino:

Hi all

Does anyone know what criteria is usually needed for a G.INP High Retransmission line to go back down to a G.INP Low Retransmission state?

TIA

No idea what the criteria is. Personally I think the FEC numbers play a part.

If you cap your downstream sync speed for a few days the DLM will move you to Retx Low, increasing throughput. You can then remove the cap and it will stay on Retx Low.

The DLM seems to prefer Retx High, particularly on Broadcom chipsets if the SNRM target has been lowered from 6dB.
A sync speed cap gives it a nudge to Retx Low.

If you tell me your current downstream sync speed I'll suggest a cap that will work. The lower the cap the more likely it will work, and sometimes quicker too.

This has been discussed extensively on the kitz forum. I've only seen the cap not work on 1 occasion. That was a line with Vectoring and the user was very stubborn in refusing to increase the cap sufficiently.
There's probably 30-40+ examples of it working.

Interesting this is possible!

My sync speed is: 68218 Kbps

Also what tool do you use to cap the sync speed?

You issue a command.
I recommend a 40Mb cap for a few days. That should do the trick.

The command for a 40 down 20 up cap is...

xdslcmd configure --maxDataRate 40000 20000 100000

Please post back if/when it works.

Edited by j0hn83 (Fri 11-Feb-22 17:25:18)

In reply to a post by j0hn83:

You issue a command.
I recommend a 40Mb cap for a few days. That should do the trick.

The command for a 40 down 20 up cap is...

xdslcmd configure --maxDataRate 40000 20000 100000

Please post back if/when it works.

Ah sweet, thanks for this!

Does this work on G.fast? If it become G.INP Retransmission High again?

In reply to a post by adslmax:

Does this work on G.fast? If it become G.INP Retransmission High again?

Try it and see. I've never tinkered with G.Farce.

I've no idea how it will work as G.Fast has SRA. Having a static sync speed isn't the norm.

Edited by j0hn83 (Sat 12-Feb-22 13:29:47)