FTTC IP profile update question

Hi all

I've noticed a extra gain in sync speed ever since the target downstream SNR has been set to 3db. So I am now syncing at: 66635 Kbps from 53999 Kbps. My BRAS IP profile is set to 61.05 Mbps ... this feels awfully low IMO, but what does the IP profile increment up in? And how often would I see the changes come into effect? Is there some information I can refer to regarding the IP profile on FTTC lines?

TIA!

Where you getting the iP Profile from? If Plusnet they might be behind the times

It should be near-instantaneous, setting to sync x 0.9679, or sync x 0.9669 if G.INP is active. But see MrSaffron's post, as if you are looking at the Plusnet Current line speed (which will be a fraction lower), that could easily get stuck.

In reply to a post by MrSaffron:

Where you getting the iP Profile from? If Plusnet they might be behind the times

I'm getting my IP Profile information from this link

Most lines with a 3dB snrm target are on the retransmission high profile.
This has an IP profile around 91-92%

If you have access to detailed line stats you can tell of you are on retransmission low or high.

Bearer 0
INP-Rein 0 = retransmission low
INP-Rein 1 = retransmission high

Edited by j0hn83 (Thu 08-Feb-18 00:03:49)

In reply to a post by j0hn83:

Most lines with a 3dB snrm target are on the retransmission high profile.
This has an IP profile around 91-92%

If you have access to detailed line stats you can tell of you are on retransmission low or high.

Bearer 0
INP-Rein 0 = retransmission low
INP-Rein 1 = retransmission high

# xdslcmd info --show
xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 18158 Kbps, Downstream rate = 66060 Kbps
Bearer: 0, Upstream rate = 18158 Kbps, Downstream rate = 66635 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 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): 3.3 6.0
Attn(dB): 16.6 0.0
Pwr(dBm): 14.0 7.1
VDSL2 framing
Bearer 0
MSGc: -6 22
B: 243 239
M: 1 1
T: 0 64
R: 10 14
S: 0.1166 0.4205
L: 17427 4832
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 75 0
TxQueue: 15 0
G.INP Framing: 18 0
G.INP lookback: 15 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 1861663
OHFErr: 0 86
RS: 1574458088 151920
RSCorr: 14232 9310
RSUnCorr: 0 0
Bearer 1
OHF: 2868544 0
OHFErr: 0 0
RS: 28684825 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 54049 0
rtx_c: 87 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 66622 0
errFreeBits: 46814693 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1609341581 0
Data Cells: 24633005 0
Drop Cells: 0
Bit Errors: 0 0

Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0

ES: 0 54
SES: 0 1
UAS: 27 27
AS: 46077

Bearer 0
INP: 55.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 6.75
OR: 0.01 33.16
AgR: 66703.03 18191.61

Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01

Bitswap: 10583/10583 3962/3962

So according to the above it says INPRein: 1.00 for the downstream ... so looks like I am on a retransmission high ... would you say this is correct or am I interpreting this wrong?

Yes, that would explain why the IP profile is set at that percentage of the sync speed.

Just curious, when did you run the BRAS IP profile check, as for weeks I've not been able to get a result for our BTW number.

Edited by deleted (Thu 08-Feb-18 12:44:18)

Yes you are on retransmission high, so an IP profile between 91-92% is correct.

Yes, you are reading it right. Sorry, I forgot about the "special case" when the sync-time margin has been set to 3dB and G.INP is active. I have the same problem.

Normally the BT Wholesale IP Profile is set as I said. But in this case it isn't. On AAISP I can see my radius log, but unfortunately only for a few days back. What I see on a re-sync is that the connection speed reported by BT Wholesale to AAISP is considerably lower than the actual sync my modem/router reports. When on a 6dB margin they are identical.

My IP Profile is calculated as I said above (96.69% of sync) based on that lower figure.

Whether the figure is incorrectly passed from Openreach to BTW, or BTW reduce it for some reason before calculating the IP Profile, I have no idea. I gave up bothering AAISP about it, as despite a few emails between us they refuse to accept this is happening.

Though that exchange was a while ago. Maybe they have found it is common by now, but life's too short.

It's idiotic that OR lower the margin to give a higher sync, but it doesn't translate into a commensurate increase in IP Profile.

Edited by RobertoS (Thu 08-Feb-18 13:10:23)

I get my IP Profile from mouselike.
https://windows.mouselike.org/be/index.asp?DoAction=...

Mouselike just runs a BT Wholesale speed test on your line and reports the IP Profile to you. I discovered that years ago, when having used it BTW made me wait (IIRC) ten minutes (it used be be longer) before letting me.

Edited by RobertoS (Thu 08-Feb-18 13:13:35)

Hmmmm. This is interesting. I know it can happen (and why) on third-party speed tests, but don't recall it on the BT Wholesale one.

Download speed achieved during the test was - 70.8 Mbps
For your connection, the acceptable range of speeds is 40 Mbps-69.67 Mbps .
Additional Information:
IP Profile for your line is - 69.67 Mbps

Upload speed achieved during the test was - 11.29Mbps
Additional Information:
Upstream Rate IP profile on your line is - 20 Mbps

Speed > IP Profile. Though I did earlier see an oddity in another AAISP log when checking how far back the part of the Radius Log report I can see went. My current sync is in my sig by the way.

This is what I get:

Looks like BT refused to test, possibly because a speed test or BRAS check has been run recently which prevents this tool from working. Try again in a few hours.
Debug: BT no BRAS info

Edited by deleted (Thu 08-Feb-18 13:54:31)

In reply to a post by WilliamGrimsley:

This is what I get:

Looks like BT refused to test, possibly because a speed test or BRAS check has been run recently which prevents this tool from working. Try again in a few hours.
Debug: BT no BRAS info

When i used to be on BTW Backhaul with Zen the IP profile stopped working many months before they put me on TTW backhaul , And following a Fault with the DSLAM port (lift and shift) they following a DLM reset had changed the DLM Policy from SPEED to stable As it had put me on a G.INP re trans High profile for some reason, maybe tt's default

Thats a 4 year old thread you've just resurrected !

I get the same result as BTw checker never work on my G.fast.

But my isp told me that all ip profile will never work on TalkTalkBusiness backhaul ADSL, ADSL2, FTTC & G.fast.

These only work on BTw backhaul ADSL, ADSL2, FTTC & G.fast.

I do believe the ip profile are set below:

IP Profile are 9369% from sync rate 330 = 309 (downstream only) for G.fast (throughput speed 305) BTw Backhaul Profile (low G.INP retransmission Bearer 0 INPRein = 0.00)
IP Profile are 9369% from sync rate 160 = 149 (downstream only) for G.fast (throughput speed 145) BTw Backhaul Profile (low G.INP retransmission Bearer 0 INPRein = 0.00)
IP Profile are 8869% from sync rate 330 = 292 (downstream only) for G.fast (throughput speed 288) BTw Backhaul Profile (high G.INP retransmission Bearer 0 INPRein = 10.00)
IP Profile are 8869% from sync rate 160 = 141 (downstream only) for G.fast (throughput speed 137) BTw Backhaul Profile (high G.INP retransmission Bearer 0 INPRein = 10.00)
IP Profile are 9669% from sync rate 80 = 77 (downstream only) for VDSL (throughput speed 73) BTw Backhaul Profile (low G.INP retransmission Bearer 0 INPRein = 0.00)
IP Profile are 9669% from sync rate 40 = 38 (downstream only) for VDSL (throughput speed 34) BTw Backhual Profile (low G.INP retransmission Bearer 0 INPRein = 0.00)
IP Profile are 9169% from sync rate 80 = 73 (downstream only) for VDSL (throughput speed 69) BTw Backhual Profile (high G.INP retransmission Bearer 0 INPRein = 1.00)
IP Profile are 9169% from sync rate 40 = 36 (downstream only) for VDSL (throughput speed 32) BTw Backhual Profile (high G.INP retransmission Bearer 0 INPRein = 1.00)

Edited by adslmax (Sun 13-Feb-22 10:09:24)

The "IP profile" is something applied by the end ISP on their BRAS, not by the backhaul provider, so that makes no difference.

It is also not the same thing as the line stats that you reported, which are the bit rate on the copper which runs between the cabinet and your property. You certainly cannot view the BRAS profile directly.

However, the ISP does aim to set the BRAS profile at a speed around or just below the line rate; that's to stop the DSLAM being overwhelmed by incoming packets faster than it can send down the copper line (and throwing them away).

In order to learn the line rate, the DSLAM adds some attributes in the PPPoE or DHCP requests that it forwards upstream. Then at the ISP end these get picked up, typically turned into RADIUS attributes, and the RADIUS server selects an IP profile in its RADIUS response.

At least, that's how I understand it works. I'm sure CarlIT will correct me if I'm wrong.

At the moment my ISP Keith agree with me to set the line speed profile at 110% instead of 98% because we both agree that G.fast use SRA and FRA as the speed of sync rate kept changing every half an hour all day as the IP Profile kept changing every 30 minutes but the ISP can't updated to match BRAS IP Profile as it normally updated every 24 - 48 hours.

My current sync now at 244011 - BRAS IP Profile = 228613 ISP IP Profile at 110% = 251474 = throughput speed = 224613 - this throughput speed will stay at all times unless I did soft PPPoE disconnection or a change from DLM force resync.

Edited by adslmax (Sun 13-Feb-22 10:14:27)

In reply to a post by jchamier:

Thats a 4 year old thread you've just resurrected !

Considering the member why are you surprised