Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: N0STIE on June 18, 2015, 02:47:13 AM
-
Hi there!
I am new on kitz.co.uk
Just wondering if my line is still interleaved or already on fastpath? Getting about 20-23ms to uk hosts such as multiplay.co.uk, google.co.uk, kelly.co.uk etc
I can't post any stats as I am using locked ECI modem combined with HH5 Type B, although my line doesn't below to the shortest out there, about 700m from the ECI cabinet. Getting rock solid Infinity 1 speed (39/8)
Btw. why is my early hop same as other hops - 20ms? I can't post any other trace routes if needed.
C:\Users\Admin>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.244.20]
over a maximum 30 hops:
1 <1 ms <1 ms <1 ms BTHUB5 [192.168.1.254]
2 * * * Request timed out.
3 * 19 ms 19 ms 31.55.185.193
4 20 ms 20 ms 19 ms 31.55.185.212
5 20 ms 19 ms 20 ms 195.99.127.130
6 20 ms 19 ms 19 ms vhsaccess2-pos1-0.faraday.fixed.bt.net [195.99.127.9]
7 20 ms 19 ms 20 ms 195.99.127.23
8 24 ms 19 ms 19 ms 194.74.65.42
9 * * * Request timed out.
10 * * * Request timed out.
11 20 ms 20 ms 20 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12 21 ms 20 ms 21 ms 132.185.255.149
13 20 ms 20 ms 20 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]
Trace complete.
Cheers!
-
Hi N0STIE, I was talking about you earlier when you thought you were monitoring your stats using MDWS here - http://forum.kitz.co.uk/index.php/topic,14361.msg290131.html#msg290131
-
I think your ping shows you are on an interleaved connection. My fastpath ping is about half of what you're seeing.
The reason why all your hops are around the same ping is that your ping is mostly due to the first hop which is the remote gateway, the entrance to your ISP. All the other hops are probably less than the first hop and so have no effect.
If you really want to know the parameters for your line, you will need a modem capable of displaying them to you. An unlocked Huawei HG612 v3B is ideal for this.
The Huawei HG612 can be monitored 24*7 using DSLstats or HG612-modem-stats. These apps can also upload the data to MyDslWebStats so you can see them and compare them and discuss them with others, instead of looking at Guest stats which actually belong to tbailey2.
-
Where abouts in the UK are you? People in the North AND on BT are seeing those kinds of pings on fastpath, I believe.
-
It depends on how BT route people, and location of the ISP data centre they route the connection to, The same can and does apply with LLU providers
Ukonline fast path = 7-8ms to 1st hop but 13ms base latency
Be unlimited = 20ms base latency
BEwholesale 26ms base latency
Plusnet 11-13ms base latency
Zen 7ms 1st hop Manchester data centre 13ms base latency to some uk based destinations, due to Zen's peering some are less than 13ms
All from same connection on fast path/G.inp and I'm in the north west
-
I am in Liverpool @boost
I can't believe my connection is on fastpath with that kind of ping!
-
If you're with BT, it's a very real possibility, unfortunately.
-
It depends on how BT route people, and location of the ISP data centre they route the connection to, The same can and does apply with LLU providers
Ukonline fast path = 7-8ms to 1st hop but 13ms base latency
Be unlimited = 20ms base latency
BEwholesale 26ms base latency
Plusnet 11-13ms base latency
Zen 7ms 1st hop Manchester data centre 13ms base latency to some uk based destinations, due to Zen's peering some are less than 13ms
All from same connection on fast path/G.inp and I'm in the north west
Plusnet was awesome for latency when I had FTTC with them. 9ms first hop, 10ms end to end and 12/13 ping in game.
UK Online sounds very interesting? :)
-
UKonline, BE unlimited and BE wholesale don't exist.
-
UKonline, BE unlimited and BE wholesale don't exist.
Yes they sadly no are no longer , the reason for the low latency to the 1st hop with Ukonline was down to that first hop being the LLU kit in my exchange, it wasn't consistent as it would fluctuate a little but always under the 13ms
But the 7ms to zen's data centre in Manchester is a consistent almost flat line 6-7ms (1st hop) i have monitored it over a long period of time ,as i did with all previous connections
-
I can remember that my 2 first hopes had different IP when I was doing trace routes, something like 2xx.... and it was about 15-16ms but the final ping was much higher like 30ish ms to bbc.co.uk, now the IPs are different starting at 3x... and the first hops ms are pretty much the same as the final ones.
-
It will be down to the route it takes to their data centre in London, but you should be able to get a ping of around 13ms
but that is BT consumer for you,
-
So are you assuming I may be on fastpath with that kind of mad route from BT side? Well since I bought my ECI modem which happened 8 days ago, after 2 days of using it my ping decreased from 28-30ms to 20-22ms to bbc.co.uk. My line is stable at the moment. I think I am going to wait another week or two to see what will happen. Perhaps it will decrease another 8ms. Let's hope!
Believe me or not I have used to join some UK's teamspeaks to see what pings people are getting, like 80% of them get 6-10ms less than me. Mine is 20-25ms. I play a lot online FPS games so latency is very important for me.
-
The only way you can be sure is to use a modem that tells you if you're on fastpath or interleaved path.
Usually that means using either an unlocked BT modem or a 3rd party modem that tells you by default.
-
Well at the moment my connection and stuff is fine, waiting for G.INP to be enable on my DSLAM then will worry what next! Probably buying HG612 3B if g.inp will affect my connection.
-
I dont know why but latency with BT does seem to be higher than with most other ISPs.
Im not certain.... but Im quite sure their habit of redirecting custom DNS and barefruit wont be helping. For some reason it doesn't seem to be too unusual these days to see latency of 18ms even on FastPath :/
The hops with circa 20ms will all be to London. The 2nd hop which times out is likely to be the bRAS which has ICMP disabled. As this is likely to be nearer your home town, then if it did respond, it would likely be much lower.
Im also in the NW, but with latency to london of circa 11ms via Plusnet.
-
Just moved to BT Infinity 1 and I'm getting 6ms to the first hop in BT's network, 13ms to bbc.co.uk. Fastpath, of course...
I'm not using the HH5 and I'm not using BT's DNS servers (nor am I being redirected to them).
-
MikeZ, no one uses BT's DNS, I am using google's DNS but I think it doesn't affect pings in any way.
How far are you from a FTTC cabinet? Are you getting full speed of Infinity 1? Where about in the UK are you? Can you post trace route to bbc.co.uk?
Cheers.
-
Distance to the cab shouldn't really make much difference, because we are talking meters rather than miles.
6-7 ms to first hop (bRAS) is about what I'd expect for a fast path connection.
From bRAS to London obviously depends upon geographic location.
ISP gateway to the BBC should only add on another 1ms as most ISP's will have direct peering with the Beeb.
-
yeah, but for example me getting 20ms on 1st hop actually tells I can't be on fastpath.
-
Can't see what your first hop on the BTnetwork is as it looks like your particular bRAS is configured to ignore ICMP - (some of them are)
2 * * * Request timed out.
This is likely where you will have entered the CORE network
The mention of faraday (http://www.kitz.co.uk/adsl/21cn_nodes.htm#core_nodes) at hop 6 - is an indication of where you exit off the CORE, but looks like you are bouncing around several routers at this particular point. The fact they are all 19/20ms indicates those routers are all in close proximity, probably in the same co-lo (http://www.kitz.co.uk/adsl/equip3.htm#colo).
-
MikeZ, no one uses BT's DNS, I am using google's DNS but I think it doesn't affect pings in any way.
How far are you from a FTTC cabinet? Are you getting full speed of Infinity 1? Where about in the UK are you? Can you post trace route to bbc.co.uk?
Cheers.
No, DNS isn't particularly relevant as far as pings and traceroutes go. You can see my stats on MDWS (MikeZ) - I'm getting the full speed for 40/10. I'm in Northamptonshire.
traceroute to bbc.co.uk (212.58.244.20), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.300 ms 0.275 ms 0.272 ms
2 * * *
3 * * *
4 217.41.217.45 (217.41.217.45) 6.210 ms 6.259 ms 6.259 ms
5 212.140.235.74 (212.140.235.74) 9.694 ms 10.160 ms 10.179 ms
6 31.55.164.221 (31.55.164.221) 9.614 ms 9.353 ms 9.315 ms
7 31.55.164.109 (31.55.164.109) 9.987 ms 8.901 ms 8.870 ms
8 109.159.248.207 (109.159.248.207) 8.790 ms 8.390 ms 8.399 ms
9 core2-te0-3-0-2.ealing.ukcore.bt.net (109.159.248.148) 14.985 ms 15.022 ms 14.748 ms
10 peer2-xe4-0-1.telehouse.ukcore.bt.net (109.159.252.39) 12.832 ms 13.112 ms 12.921 ms
11 194.74.65.42 (194.74.65.42) 12.820 ms 12.863 ms 12.850 ms
12 * * *
13 * * *
14 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 13.322 ms 12.796 ms 13.487 ms
15 132.185.255.149 (132.185.255.149) 14.114 ms 13.864 ms 13.877 ms
16 fmt-vip71.telhc.bbc.co.uk (212.58.244.20) 13.500 ms 13.331 ms 13.894 ms
-
I was getting about 14-16ms on the 3 first hopes a few weeks ago but my final ping was 29ms, IP range was 2xx same as yours. No idea why it changed.
-
Can you ask your ISP to perform a GEA Service Test on your line. This will give you your line profile so that you will know for sure.
My ISP did one for me a couple of days ago and they look like this.
They may not provide the image - but they should be able to tell you the results of the Profile Name
-
MikeZ, no one uses BT's DNS, I am using google's DNS but I think it doesn't affect pings in any way.
How far are you from a FTTC cabinet? Are you getting full speed of Infinity 1? Where about in the UK are you? Can you post trace route to bbc.co.uk?
Cheers.
No, DNS isn't particularly relevant as far as pings and traceroutes go. You can see my stats on MDWS (MikeZ) - I'm getting the full speed for 40/10. I'm in Northamptonshire.
traceroute to bbc.co.uk (212.58.244.20), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.300 ms 0.275 ms 0.272 ms
2 * * *
3 * * *
4 217.41.217.45 (217.41.217.45) 6.210 ms 6.259 ms 6.259 ms
5 212.140.235.74 (212.140.235.74) 9.694 ms 10.160 ms 10.179 ms
6 31.55.164.221 (31.55.164.221) 9.614 ms 9.353 ms 9.315 ms
7 31.55.164.109 (31.55.164.109) 9.987 ms 8.901 ms 8.870 ms
8 109.159.248.207 (109.159.248.207) 8.790 ms 8.390 ms 8.399 ms
9 core2-te0-3-0-2.ealing.ukcore.bt.net (109.159.248.148) 14.985 ms 15.022 ms 14.748 ms
10 peer2-xe4-0-1.telehouse.ukcore.bt.net (109.159.252.39) 12.832 ms 13.112 ms 12.921 ms
11 194.74.65.42 (194.74.65.42) 12.820 ms 12.863 ms 12.850 ms
12 * * *
13 * * *
14 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 13.322 ms 12.796 ms 13.487 ms
15 132.185.255.149 (132.185.255.149) 14.114 ms 13.864 ms 13.877 ms
16 fmt-vip71.telhc.bbc.co.uk (212.58.244.20) 13.500 ms 13.331 ms 13.894 ms
6ms is impressive. The lowest I've seen so far.
Shame your ISP doubles it!
What length do you reckon your copper tail is? What's attenuation reported as? :)
-
That's a great latency, I wish I had 13ms!
I am thinking of getting HG612 3B, is it good idea? My DLSAM is ECI. I would love to see my line stats and that confusing interleaving!
-
6ms is impressive. The lowest I've seen so far.
Shame your ISP doubles it!
What length do you reckon your copper tail is? What's attenuation reported as? :)
That isn't the ISP doubling it. Hop 4 will be at the bRAS location and before any core routing. Liverpool doesnt have a core node (http://www.kitz.co.uk/adsl/21cn_nodes.htm), so most likely that will be somewhere like Manchester. As mentioned in my earlier post 6-7ms is typical to bRAS, its also not unusual to see several hops at the bRAS before it enters the core.
Hop 9 is exiting the core at Ealing.
Most BTw based ISPs except BTretail use L2TP tunnelling so that you never see any of the BTwholesale routing. Many years ago I did some trials for Plusnet's RIN network where they didnt use L2TP and I could see clearly from that I went through Manchester. There used to be another way you could view your routing (http://www.kitz.co.uk/adsl/RAS.htm), but Im not sure if it works on 21CN - I havent tried it.
I find hop 5 quite interesting though and how things increase by 3ms - yet both hop4 and hop5 resolve to T-MAN (Metropolitan Access Node) but Ive no idea what a T-MAN is - searching throws up something to do with clusters & IPv6 and yet when I look at the next hop after it resolves to BT-UKIP-IPV4. If someone has more info on that please do enlighten :) Im not sure if those particular routers in that cluster could even have low priority to ICMP as note how hop 8 has lower latency, which is typical of prioritising ICMP.
-
Just tried to tracert the IP that appears in my tracert, unfortunately none of these IP is routable or pingable - many timeouts. Just found that these first hop IPs are very similar to my BT DNS. What do you think about this?
Strange how the trace route changes. I have seen kind of IPs on the first hops you posted starting at 2xx. then it suddenly changed to 3x.
-
That's a great latency, I wish I had 13ms!
I am thinking of getting HG612 3B, is it good idea? My DLSAM is ECI. I would love to see my line stats and that confusing interleaving!
Unfortunately BT's core routing adds a few ms - my previous ISP gave me 8 or 9ms to bbc.co.uk.
If you want to upload your stats to MDWS then you'll need something like the HG612. I'm using one with an ECI cab and it's fine at the moment. Will be interesting to see what happens if/when G.INP is enabled...
-
I find hop 5 quite interesting though and how things increase by 3ms - yet both hop4 and hop5 resolve to T-MAN (Metropolitan Access Node) but Ive no idea what a T-MAN is - searching throws up something to do with clusters & IPv6 and yet when I look at the next hop after it resolves to BT-UKIP-IPV4. If someone has more info on that please do enlighten :) Im not sure if those particular routers in that cluster could even have low priority to ICMP as note how hop 8 has lower latency, which is typical of prioritising ICMP.
I'd rather they gave low priority to ICMP rather than dropping UDP, which some of them seem to be doing. Since switching to Infinity I've noticed that NTP has become less reliable. Using tshark I can see that many requests just don't get a reply at peak times. Early in the morning, every request receives a reply.
-
6ms is impressive. The lowest I've seen so far.
Shame your ISP doubles it!
What length do you reckon your copper tail is? What's attenuation reported as? :)
That isn't the ISP doubling it. Hop 4 will be at the bRAS location and before any core routing. Liverpool doesnt have a core node (http://www.kitz.co.uk/adsl/21cn_nodes.htm), so most likely that will be somewhere like Manchester. As mentioned in my earlier post 6-7ms is typical to bRAS, its also not unusual to see several hops at the bRAS before it enters the core.
Hop 9 is exiting the core at Ealing.
Most BTw based ISPs except BTretail use L2TP tunnelling so that you never see any of the BTwholesale routing. Many years ago I did some trials for Plusnet's RIN network where they didnt use L2TP and I could see clearly from that I went through Manchester. There used to be another way you could view your routing (http://www.kitz.co.uk/adsl/RAS.htm), but Im not sure if it works on 21CN - I havent tried it.
I find hop 5 quite interesting though and how things increase by 3ms - yet both hop4 and hop5 resolve to T-MAN (Metropolitan Access Node) but Ive no idea what a T-MAN is - searching throws up something to do with clusters & IPv6 and yet when I look at the next hop after it resolves to BT-UKIP-IPV4. If someone has more info on that please do enlighten :) Im not sure if those particular routers in that cluster could even have low priority to ICMP as note how hop 8 has lower latency, which is typical of prioritising ICMP.
If the access technology yields 6ms, everything thereafter (excluding the native fibre propagation delay, 1ms?) is simply inefficiency.
6ms to 13ms is sloppy design/aged hardware/misconfiguration.
The end :P
-
If you want to upload your stats to MDWS then you'll need something like the HG612.
A caveat for N0STIE. The prices of the HG612 have become silly money recently on Ebay. Before you purchase please read this thread (http://forum.kitz.co.uk/index.php/topic,15340.0.html) and avoid certain sellers who are charging extortionate prices. It may be far more economical to purchase a decent combined unit.
If you want help on this please do ask.
-
I'd rather they gave low priority to ICMP rather than dropping UDP, which some of them seem to be doing. Since switching to Infinity I've noticed that NTP has become less reliable. Using tshark I can see that many requests just don't get a reply at peak times. Early in the morning, every request receives a reply.
I totally agree, and I suspect that is what they are doing for those routers reporting 8-9 ms. It makes the network more efficient by prioritising. :)
-
If the access technology yields 6ms, everything thereafter (excluding the native fibre propagation delay, 1ms?) is simply inefficiency.
6ms to 13ms is sloppy design/aged hardware/misconfiguration.
The end :P
But its not that. 6ms is only the time taken to the bRAS - ie Manchester. The additional 6ms on top of that bringing it up to 12ms is all the way to London.
When you break that tracert down to its most simplistic form it interprets as
6ms - EU Premises <-> RAS - Enter the CORE Network at Manchester
12ms - EU Premises <-> London - Exit the CORE at Ealing London.
13ms - EU Premises <-> BBC - extra 1ms to get from Core exit point to the BBC server.
-
A caveat for N0STIE. The prices of the HG612 have become silly money recently on Ebay. Before you purchase please read this thread (http://forum.kitz.co.uk/index.php/topic,15340.0.html) and avoid certain sellers who are charging extortionate prices. It may be far more economical to purchase a decent combined unit.
If you want help on this please do ask.
Thanks kitz for this link, very useful! Just purchased one HG612 3B for £25.00 unfortunately locked one. I hope this is not that complicated to unlock it. Which firmware should I use to get the best out of it?
-
. . . Just purchased one HG612 3B for £25.00 unfortunately locked one. I hope this is not that complicated to unlock it. Which firmware should I use to get the best out of it?
Please have a read of the initial posting of this thread (http://forum.kitz.co.uk/index.php?topic=14262.0) and take note of the added information coloured red. You should also download a copy of Asbokid's unlocking guide (https://huaweihg612hacking.files.wordpress.com/2011/11/hg612_unlock_instructions_v1-3.pdf), make a hard-copy print out and carefully read it before attempting to unlock your HG612.
-
Hey bruakkucat,
I will read it carefully before unlocking! Do you suggest turning off BT Agent and how to do it?
-
Do you suggest turning off BT Agent and how to do it?
I don't recommend it but if you really want to do so, the simplest method is to remove the "channel" by which it communicates with Beattie Bellman's HQ. ;) Once you have the HG612 unlocked, just ask and one of us will explain what change should be made to the configuration.
-
Yes I definietely will. Thanks for help and explanation burakkucat! I will post back in a few days once I get my modem and unlock it.
-
If the access technology yields 6ms, everything thereafter (excluding the native fibre propagation delay, 1ms?) is simply inefficiency.
6ms to 13ms is sloppy design/aged hardware/misconfiguration.
The end :P
But its not that. 6ms is only the time taken to the bRAS - ie Manchester. The additional 6ms on top of that bringing it up to 12ms is all the way to London.
When you break that tracert down to its most simplistic form it interprets as
6ms - EU Premises <-> RAS - Enter the CORE Network at Manchester
12ms - EU Premises <-> London - Exit the CORE at Ealing London.
13ms - EU Premises <-> BBC - extra 1ms to get from Core exit point to the BBC server.
This is where my complete inability to do anything maths related fails me :P
-
I would love to see fastpath at some point. Unfortunately I have never seen it on VDSL. I had VDSL with Zen on my last property and was always interleaved even though the BT engineer stated I had a very good clean line along with full sync.
Now in my new property, I believe the line may be noisier but still not too bad a sync at 75/20. No sign of fastpath here either. Best pings I get are 25ms to bbc from NE Scotland.
-
What ISP/modem? :)
-
I'm still with Zen and using the HG612. I did use a Netgear D6400 for 8days. Currently back in the HG612.
-
I've no idea if it would help or hinder in general but have you looked at the maxDataRate command for the HG612?
You could potentially lower your synch which may allow for a more favourable latency profile? :)
-
I've never even heard if the Max data rate command to be honest.
-
One of my scribblings shows the following:
xdslcmd configure --trellis on --bitswap on --sesdrop on --sra on --phyReXmt 0x3 --i24k on --maxDataRate 40000 20000 60000
xdslcmd configure1 --maxDataRate 40960 20480 61440
Your HG needs to be running the latest firmware before the maxdatarate syntax becomes valid.
--maxDataRate <desired downstream synch> <desired upstream synch> <the total of the former two>
-
Hmm. Looks a bit out of my depth. I've been in touch with Zen and this is the response I got from them:
I have checked the profile for this circuit and "fastpath" is not enabled. Fast path is another term for interleaving which is applied if a line starts to error. However on FTTC lines it can never be turned totally off by advising the stability option. the Dynamic Line Management will always have the option to enable interleaving if its required.
Currently this circuit is not running with any profile restrictions, it has also been stable so would not expect it to be enabled unless it gets into trouble
-
Fast path is another term for interleaving which is applied if a line starts to error.
The above line is utter hog-wash! :-X
Are you absolutely sure that is what was typed? Could some words have been inadvertently omitted? :-\
-
Fast path is another term for interleaving which is applied if a line starts to error.
Oh dear. :(
I have checked the profile for this circuit and "fastpath" is not enabled.
Fast path is never mentioned in the FTTC profile anyhow. It should either say something like Error Protection or Interleaving.
Since he claims to have looked at your profile may be an idea if you could ask what that is, as we may be able to interpret.
-
Hi there, sorry for the delay.
I'm half way around the world at the moment so totally back to front with UK time.
I just copied and pasted their response from the email I received but deleted my name. When I read it, it made no sense to me. I did respond but have not heard back from them at all.
I'll maybe get a ticket raised. He said I had no DLM restrictions but I have a feeling I'm banded. Looking at my stats it shows Max attainable as approx 80,500 but my actual sync speed is 74,002. Basically bang on. Maybe that is right but just looks strange to me.
-
Looking at my stats it shows Max attainable as approx 80,500 but my actual sync speed is 74,002. Basically bang on. Maybe that is right but just looks strange to me.
If the line is interleaved, then the max attainable does go a bit skewy and show a higher figure than what would be obtainable if the line wasnt interleaved.
We dont know exactly why this would be, but my guess is something to do with RS overheads. In other words if the line is interleaved and has Error Correction applied, then sync connection speed has to be lowered because of the redundancy overheads.
-
Well that makes a lot of sense. Thanks for explaining!
It is certainly interleaved. G.inp was also applied at the end of march.
I can post a full stats when I get to my work computer but it seems interleaved is set at 16 down and 8 up. g.inp shows 49 down and 47 up I believe. I'm not too worried about getting fastpath, just interested on how it works.
I guess as g.inp remains in place, there must be some sort of noise on the line.
-
Ok, Here is a full list of stats I pulled from a Netgear D6400 when I had it connected for 8 days. I'm back on the HG612 now though.
DSLAM/MSAN type: BDCM:0xa485 / v0xa485
Modem/router firmware: AnnexA version - A2pv6F039j.d25d
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime:
Resyncs: 0 (since 31 May 2015 12:58:02)
Downstream Upstream
Line attenuation (dB): 17.5 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 74000 20000
SNR margin (dB): 7.5 9.7
Power (dBm): 13.6 7.5
Interleave depth: 16 8
INP: 49.00 47.00
G.INP: Enabled
RSCorr/RS (%): 0.0221 7.0520
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
adslctl info --stats
adslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 26040 Kbps, Downstream rate = 80441 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 74000 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): 7.5 9.7
Attn(dB): 17.5 0.0
Pwr(dBm): 13.6 7.5
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 174 97
M: 1 1
T: 0 0
R: 8 8
S: 0.0752 0.1554
L: 19456 5457
D: 16 8
I: 183 106
N: 183 106
Q: 16 8
V: 3 2
RxQueue: 42 39
TxQueue: 14 13
G.INP Framing: 18 18
G.INP lookback: 14 13
RRC bits: 24 24
Bearer 1
MSGc: 154 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 6.4000 16.0000
L: 40 16
D: 3 1
I: 32 32
N: 32 32
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 0
OHFErr: 2 13
RS: 2515510368 2428593
RSCorr: 554115 61355
RSUnCorr: 0 0
Bearer 1
OHF: 43355392 533362
OHFErr: 0 0
RS: 433553307 2301221
RSCorr: 2129 299
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 388043 5110
rtx_c: 19178 17972
rtx_uc: 2 73044
G.INP Counters
LEFTRS: 456 84
minEFTR: 74006 19997
errFreeBits: 785859680 1521542996
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 317187817 0
Data Cells: 325251717 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: 2 3
SES: 0 0
UAS: 31 31
AS: 696400
Bearer 0
INP: 49.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 74132.27 20102.08
Bearer 1
INP: 4.50 4.00
INPRein: 4.50 4.00
delay: 3 0
PER: 16.06 16.06
OR: 79.68 31.87
AgR: 79.68 31.87
Bitswap: 85324/85329 9058/9063
Total time = 8 days 1 hours 27 min 11 sec
FEC: 554115 61355
CRC: 2 13
ES: 2 3
SES: 0 0
UAS: 31 31
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 12 min 11 sec
FEC: 65 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: 84 16
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 = 1 hours 27 min 11 sec
FEC: 1515 92
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 62119 2103
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 8 days 1 hours 26 min 39 sec
FEC: 554115 61355
CRC: 2 13
ES: 2 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
#
-
Mitchy_me can you please PM me the ref and name from the Zen Rep please.
The information is incorrect and I want to make sure this is put straight.
Kindest Regards,
-
Mitchy_me can you please PM me the ref and name from the Zen Rep please.
The information is incorrect and I want to make sure this is put straight.
Kindest Regards,
Azzaka,
I've sent you my correspondence with the Zen team member via PM. I've also attached my initial question so you can see what I have asked prior to what I was told. Thanks.
-
Not too sure if this makes a difference but the InpREIN on the bearer 0 and bearer 1 are very different.
Bearer 0
INP: 49.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 74132.27 20102.08
Bearer 1
INP: 4.50 4.00
INPRein: 4.50 4.00
delay: 3 0
PER: 16.06 16.06
OR: 79.68 31.87
AgR: 79.68 31.87
Here is a trace route to BBC. I live in NE Scotland.
Tracing route to bbc.co.uk [212.58.246.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 19 ms 18 ms 18 ms losubs.subs.dsl2.wh-man.zen.net.uk [62.3.87.147]
3 19 ms 19 ms 18 ms ae1-114.cr1.wh-man.zen.net.uk [62.3.87.169]
4 25 ms 42 ms 32 ms ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
5 25 ms 25 ms 25 ms ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41]
6 27 ms 26 ms 25 ms 82.71.254.134
7 * * * Request timed out.
8 27 ms 26 ms 26 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
9 27 ms 26 ms 27 ms 132.185.255.165
10 26 ms 26 ms 26 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]
Trace complete.
-
Thanks Mitchy.
I know the person in question and will make sure the correct information is given in the future. If you have any further issues please PM directly and I will do what I can to help. If I am not around, let Kitz know and she will contact me.
All the best,
Azz
-
Thanks Mitchy.
I know the person in question and will make sure the correct information is given in the future. If you have any further issues please PM directly and I will do what I can to help. If I am not around, let Kitz know and she will contact me.
All the best,
Azz
Hi Azz,
Thank you very much. Very kind of you. I'll maybe PM you one little question.
-
Mitchy_me can you please PM me the ref and name from the Zen Rep please.
The information is incorrect and I want to make sure this is put straight.
Kindest Regards,
*checks how much Zen Internets is per month*
-
Huh?
-
Not too sure if this makes a difference but the InpREIN on the bearer 0 and bearer 1 are very different.
Bearer 0
INP: 49.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 74132.27 20102.08
Bearer 1
INP: 4.50 4.00
INPRein: 4.50 4.00
delay: 3 0
PER: 16.06 16.06
OR: 79.68 31.87
AgR: 79.68 31.87
Bearer 1 is a low bandwidth channel that only contains control information passing between the modems. DLM chooses better protection for that data, doesn't want re-transmission, and is willing to put up with the overheads. Bearer 0 still carries all your data - and that is protected by re-transmission.
The configuration that DLM has chosen for bearer 0 on your line is as close to minimal as possible, and that demonstrates the problem with (simplistically) referring to a path as fastpath or interleaved.
In the modern setup, *every* line is interleaved, and none are fastpath (and that would be strictly true even if D=1). However, where the pre-G.INP interleaved configuration would have a minimum delay of 8ms, the smallest G.INP versions of interleaving have delays of around 0.2ms. Multiply the interleaving depth by the interleaver block size for both cases, and you can see the difference.
Presumably BT's tests have shown that this minimal level of interleaving+FEC helps reduce superficial re-transmissions that would come without it, reducing the jitter that would come from retransmission.
-
Presumably BT's tests have shown that this minimal level of interleaving+FEC helps
the HH5A to function.
-
Ok the HG612 3B has arrived although I have a problem with it.
I have unlocked it using this guide http://www.kitz.co.uk/routers/hg612unlock.htm and firmware B030SP08 webgui but I can't connection to the internet via LAN2 on my PC, LAN1 works fine but without dsl stats. When I connect my HH5 Type B via LAN1 wifi also works, just LAN2 won't let me connect to the internet. Based on the lights it appears to be connected. I have access to web gui @ 192.168.1.1 via LAN2 but there are not any stats beside sync and max sync attainable and no internet connection too.
What do I do?
-
Ok the HG612 3B has arrived although I have a problem with it.
I have unlocked it using this guide http://www.kitz.co.uk/routers/hg612unlock.htm and firmware B030SP08 webgui but I can't connection to the internet via LAN2 on my PC, LAN1 works fine but without dsl stats. When I connect my HH5 Type B via LAN1 wifi also works, just LAN2 won't let me connect to the internet. Based on the lights it appears to be connected. I have access to web gui @ 192.168.1.1 via LAN2 but there are not any stats beside sync and max sync attainable and no internet connection too.
What do I do?
LAN2 does not have internet connectivity by design, it's for stats only. Plug LAN1 into your HH5 ethernet WAN port, and LAN2 into one of the LAN ports on the HH5.
-
What about my PC ethernet cable? I would like to have internet connection and web gui /telnet stats at the same time.
-
your PC plugs into another LAN port on the HH5.
-
won't work, just connected as you said, no connection. Only works when I connect LAN1 on the HG612 to my PC but no line stats.
-
Here you go -
Ethernet connection from LAN 1 on HG612 to WAN port on HH5 - this gives you your internet connection via HH5.
EThernet cable from LAN 2 on HG612 to spare LAN port on HH5- this gives DSL Stats connectivity to HG612 from anywhere on your network.
Ethernet cable from any other spare LAN port on HH5 to a PC/Laptop of your choice - wired internet connection.
I think the above works assuming you haven't changed any standard IP addresses - 192.168.1.1 for the HG612, 192.168.1.254 for HH5 (?). Seems to work OK for me.
Picture attached (hopefully)
-
Yeah all cables connected exactly as on the picture attached, still no connection on my PC, wifi works fine on laptop tho. Can't even acces 192.168.1.1 now, the IPs in NIC are 192.168.1.100 as IPv4 and 255.255.255.0 as subnet mask.
-
Bearer 1 is a low bandwidth channel that only contains control information passing between the modems. DLM chooses better protection for that data, doesn't want re-transmission, and is willing to put up with the overheads. Bearer 0 still carries all your data - and that is protected by re-transmission.
The configuration that DLM has chosen for bearer 0 on your line is as close to minimal as possible, and that demonstrates the problem with (simplistically) referring to a path as fastpath or interleaved.
In the modern setup, *every* line is interleaved, and none are fastpath (and that would be strictly true even if D=1). However, where the pre-G.INP interleaved configuration would have a minimum delay of 8ms, the smallest G.INP versions of interleaving have delays of around 0.2ms. Multiply the interleaving depth by the interleaver block size for both cases, and you can see the difference.
Presumably BT's tests have shown that this minimal level of interleaving+FEC helps reduce superficial re-transmissions that would come without it, reducing the jitter that would come from retransmission.
Thanks for the detailed description. That makes a lot more sense to me.
A different Zen support member came back to me yesterday stating the following about my line.
Synch Speeds:
Downstream: 73.9mbps
Upstream: 20.0mbps
Profile: 0.128M-74M Downstream, Retransmission Low - 0.128M-20M Upstream, Retransmission Low
The DSLAM is reporting your circuit is using a different type of protection known as G.INP / Retransmission, this is essentially that whenever an error is detected on the circuit this will be corrected on demand & in real-time; any other time the circuit is not erroring, then it's literally like interleaving is turned off.
It may simply be that your modem is reporting that the connection is being interleaved when in reality G.INP is actually in play.
I'm happy enough with my line as it is solid and gaming is fine. I was just more interested to learn more about it and trying to understand G.INP a bit better.
-
Have you set the settings in the HH5 to use WAN?
When I have been checking stats, I have one cable from LAN1 on HG612 to Wan port on my Asus router.
Second cable from LAn 2 on HG612 to LAN1 on the Asus. This allows me to view stats on my main PC. I could never get HG612 stats to work so just used DSLstats.
-
Ok rebooted my PC and it seems its working now LOL.
Having access to 192.168.1.1 and to 192.168.1.254 (HH5)
But I didnt have to set up PPPoE connection on my PC why is that? The connection normally goes HH5->PC via ethernet. The modem didnt change anything to be honest. Latency is basically the same, bandwith as well.
How can I access stats via telnet?
-
But I didnt have to set up PPPoE connection on my PC why is that?
Because the HH5 manages the PPP session.
How can I access stats via telnet?
From your web-browser:
- Entering 192.168.1.254 into the address bar will take you to the GUI of the HH5
- Entering 192.168.1.1 into the address bar will take you to the GUI of the HG612
From your computer's command line telnet 192.168.1.1 will connect you to the HG612's command line interface. Login to the HG612 with admin, password admin and then, at the ATP> prompt, enter sh. At the busybox shell prompt, enter xdslcmd --help.
-
When I type xdslcmd --help I am getting this:
Welcome Visiting Huawei Home Gateway
Copyright by Huawei Technologies Co., Ltd.
Login:admin
Password:
ATP>sh
BusyBox v1.9.1 (2014-01-21 16:44:38 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# xdslcmd --help
Usage: xdslcmd start [--up] <configure command options>
xdslcmd stop
xdslcmd connection [--up] [--down] [--loopback] [--reverb]
[--medley] [--noretrain] [--L3] [--diagmode] [--L0]
[--tones <r1-r2,r3-r4,...>] [--normal] [--freezeReverb] [--freezeMedl
ey]
xdslcmd configure/configure1 [--mod <a|d|l|t|2|p|e|m|M3|M5|v>] [--lpair <
(i)nner|(o)uter>]
[--trellis <on|off>] [--snr <snrQ4>] [--bitswap <on|off>] [--sesdrop
<on|off>]
[--sra <on|off>] [--CoMinMgn <on|off>] [--i24k <on|off>] [--phyReXmt
<0xBitMap-UsDs>]
[--Ginp <0xBitMap-UsDs>] [--TpsTc <0xBitMap-AvPvAaPa>] [--monitorTone
<on|off>]
[--profile <0x00 - 0xFF>|<"8a |8b |8c |8d |12a |12b |17a |30a">] [--u
s0 <on|off>]
[--dynamicD <on|off>] [--dynamicF <on|off>] [--SOS <on|off>] [--maxDa
taRate <maxDsDataRateKbps maxUsDataRateKbps maxAggrDataRateKbps>]
[--forceJ43 <on|off>] [--toggleJ43B43 <on|off>]
xdslcmd bert [--start <#seconds>] [--stop] [--show]
xdslcmd afelb [--time <sec>] [--tones] [--signal <1/2/8>]
xdslcmd qlnmntr [--time <sec>] [--freq <msec>]
xdslcmd inm [--start <INMIATO> <INMIATS><INMCC><INM_INPEQ_MODE><INM_INPEQ
_FORMAT>] [--show]
xdslcmd snrclamp [--shape <shapeId>] [--bpshape [bpIndex-bpLevel,]]
xdslcmd nlnm [--show ] [--setThld <Thld_Num_Tones>]
xdslcmd diag [--logstart <nBytes>] [--logpause] [--logstop] [--loguntilbu
fferfull <nBytes>] [--loguntilretrain <nBytes>] [--dumpBuf <sizeKb>]
xdslcmd info [--state] [--show] [--stats] [--SNR] [--QLN] [--Hlog] [--Hli
n] [--HlinS] [--Bits]
[--pbParams] [--linediag] [--linediag1] [--reset] [--vendor] [--cfg]
xdslcmd profile [--show] [--save] [--restore]
xdslcmd --version
xdslcmd --help
#
#
-
just woke up and checked my latency if something changed and shocked at the same time. DLM has kick in and added massive amount of interleaving to my line and destroyed my line - ping to bbc.co.uk went up to 35ms from 21ms and upload speed dropped from 8mbps to 6mbps. You can check my stats on mydslwebstats.co.uk nickname: N0STIE
I think I am gonna swap it back to eci/r as this is unnacceptable.
Attached a picture aswell.
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 6056 Kbps, Downstream rate = 49740 Kbps
Bearer: 0, Upstream rate = 6928 Kbps, Downstream rate = 42833 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.1 6.0
Attn(dB): 22.2 0.0
Pwr(dBm): 12.6 5.8
VDSL2 framing
Bearer 0
MSGc: 18 33
B: 63 80
M: 1 1
T: 64 58
R: 16 16
S: 0.0475 0.3716
L: 13464 2088
D: 1137 87
I: 80 97
N: 80 97
Counters
Bearer 0
OHF: 4238272 600654
OHFErr: 0 0
RS: 813665662 1409258
RSCorr: 34172 3
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 799048578 0
Data Cells: 1451085 0
Drop Cells: 0
Bit Errors: 0 0
ES: 31 3
SES: 11 0
UAS: 91 80
AS: 9709
Bearer 0
INP: 5.00 2.50
INPRein: 0.00 0.00
delay: 13 8
PER: 2.29 16.22
OR: 83.82 19.22
AgR: 42917.15 6947.21
Bitswap: 4627/4627 0/0
Total time = 9 hours 59 min 40 sec
FEC: 235711 24
CRC: 3898 4
ES: 31 3
SES: 11 0
UAS: 91 80
LOS: 1 0
LOF: 6 0
LOM: 0 0
Latest 15 minutes time = 14 min 40 sec
FEC: 3285 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: 3629 0
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 = 9 hours 59 min 40 sec
FEC: 235711 24
CRC: 3898 4
ES: 31 3
SES: 11 0
UAS: 91 80
LOS: 1 0
LOF: 6 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 = 2 hours 41 min 49 sec
FEC: 34172 3
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Stats recorded 25 jun 2015 09:00:01
DSLAM/MSAN type: IFTN:0xb204 / v0xb204
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 2 hours 44 min 49 sec
Resyncs: 0 (since 25 jun 2015 08:51:47)
Downstream Upstream
Line attenuation (dB): 22,2 0,0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 42833 6928
SNR margin (dB): 6,0 6,0
Power (dBm): 12,6 5,8
Interleave depth: 1137 87
INP: 5,00 2,50
G.INP: Not enabled
RSCorr/RS (%): 0,0041 0,0001
RSUnCorr/RS (%): 0,0000 0,0000
ES/hour: 2,73 0,12
-
just woke up and checked my latency if something changed and shocked at the same time. DLM has kick in and added massive amount of interleaving to my line and destroyed my line - ping to bbc.co.uk went up to 35ms from 21ms and upload speed dropped from 8mbps to 6mbps. You can check my stats on mydslwebstats.co.uk nickname: N0STIE
I think I am gonna swap it back to eci/r as this is unnacceptable.
If you've been power-cycling/disconnecting/reconnecting the HG612 a lot then that will have contributed. Switching back to the ECI won't make any difference now. Just leave things to settle (HG612 permanently connected and powered on). It may take up to a few weeks for DLM to move the rate again.
-
If you've been power-cycling/disconnecting/reconnecting the HG612 a lot then that will have contributed. Switching back to the ECI won't make any difference now. Just leave things to settle (HG612 permanently connected and powered on). It may take up to a few weeks for DLM to move the rate again.
and at least you will know, whereas with the ECI you'll never know.
-
Yeah, I think I will leave it connected 24/7 for few weeks, what if my HH5 drops? Interleaving depth of 1127 down and 97 up + 13/8 delay is massive isnt it? When can I expect first reduction of latency which is very important for me as I usually play online games such as CS:GO where latency is a key.
-
Yeah, I think I will leave it connected 24/7 for few weeks, what if my HH5 drops? Interleaving depth of 1127 down and 97 up + 13/8 delay is massive isnt it? When can I expect first reduction of latency which is very important for me as I usually play online games such as CS:GO where latency is a key.
It doesn't matter if the HH5 drops - that will just restart the PPP session. You need to make sure the HG612 doesn't disconnect or restart, if you can help it, as that's what's maintaining sync.
I had similar interleaving to you - it took 15 days for US interleaving to be removed and then a further 4 weeks (I think) before DS was removed.
-
4 weeks? seems like long holiday coming up :)
-
Most of my 'penalties' from DLM have been removed in a number of days. Check again in 3 days or so but keep the HG612 connected and powered up.
-
A different Zen support member came back to me yesterday stating the following about my line.
The DSLAM is reporting your circuit is using a different type of protection known as G.INP / Retransmission, this is essentially that whenever an error is detected on the circuit this will be corrected on demand & in real-time; any other time the circuit is not erroring, then it's literally like interleaving is turned off.
It may simply be that your modem is reporting that the connection is being interleaved when in reality G.INP is actually in play.
He's mostly correct.
I think the best thing to remember is that all of these error-protection mechanisms can be turned on and off independently - so can be used together if necessary. Unfortunately, this requires a nuanced explanation, but support staff aren't always well versed in grasping the full breadth of complexity involved.
In your case, G.INP retransmission is the predominant protection, with very small levels of FEC and interleaving protection added. Interleaving isn't quite turned off, but it can be considered to be turned down to a great extent.
-
Interleaving depth of 1127 down and 97 up + 13/8 delay is massive isnt it?
The delays are indeed massive - a surprise to see such a value upstream too.
What DLM is looking for now is stability. Once that returns, things can improve quickly.
I went through a bad patch with our house power tripping. It took less than a day, with a lot of outages, to cause DLM to intervene heavily. However, once I stopped the trips (and fitted a UPS), things were back to normal within 4 days.
-
He's mostly correct.
I think the best thing to remember is that all of these error-protection mechanisms can be turned on and off independently - so can be used together if necessary. Unfortunately, this requires a nuanced explanation, but support staff aren't always well versed in grasping the full breadth of complexity involved.
In your case, G.INP retransmission is the predominant protection, with very small levels of FEC and interleaving protection added. Interleaving isn't quite turned off, but it can be considered to be turned down to a great extent.
Thanks for your input WWWombat. I am happy with the way my line performs. I was just more curious as to how it all worked and it is starting to look a bit complex. I've never had any issues with gaming or anything like that. I most likely would not notice a drop of 10ms or so anyway. The main thing it is stable and has no adverse effects on my experience.
-
My connection just resynced, here are the results, 13ms to bbc.co.uk. I hope it will stay like that forever. Oh completely forgot about todays downgrade to Infinity 1. May it affect my latency once again?
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 8338 Kbps, Downstream rate = 47608 Kbps
Bearer: 0, Upstream rate = 8069 Kbps, Downstream rate = 39973 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): 10.0 6.2
Attn(dB): 22.3 0.0
Pwr(dBm): 12.6 5.8
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 239 238
M: 1 1
T: 64 27
R: 0 16
S: 0.1911 0.9418
L: 10048 2166
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 1125023 271660
OHFErr: 157 0
RS: 0 1780222
RSCorr: 0 0
RSUnCorr: 0 0
Bearer 0
HEC: 454 0
OCD: 20 0
LCD: 20 0
Total Cells: 265208358 0
Data Cells: 9199996 0
Drop Cells: 0
Bit Errors: 0 0
ES: 58 0
SES: 11 0
UAS: 58 48
AS: 3454
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 3.06 12.76
OR: 62.55 20.05
AgR: 40035.61 8088.77
Bitswap: 2645/2645 0/0
Total time = 14 hours 25 min 54 sec
FEC: 0 0
CRC: 157 0
ES: 58 0
SES: 11 0
UAS: 58 48
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 10 min 54 sec
FEC: 0 0
CRC: 22 0
ES: 13 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: 0 0
CRC: 7 0
ES: 6 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 14 hours 25 min 54 sec
FEC: 0 0
CRC: 157 0
ES: 58 0
SES: 11 0
UAS: 58 48
LOS: 1 0
LOF: 9 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 = 57 min 33 sec
FEC: 0 0
CRC: 157 0
ES: 32 0
SES: 1 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
I still waiting for DLM to change my line interleave depth from 16:8 to 16:1 as I notice many used to be on 16:8 and now on 16:1 but mine still on 16:8 for 25 days!
-
Is that due to the G.inp adjustments that users have been put on 16:1? Maybe it hasnt rolled out to you yet? Last time I checked I was still on 16:8. It doesn't make any difference anyway after seeing stats from another user.
-
Anyone can confirm what my stats are like? May DLM do something with my line? Average ES/h about 20 while daylight and 35-40 in the evenings.
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 8223 Kbps, Downstream rate = 47220 Kbps
Bearer: 0, Upstream rate = 8069 Kbps, Downstream rate = 39973 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): 9.8 6.0
Attn(dB): 22.3 0.0
Pwr(dBm): 12.6 5.8
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 239 238
M: 1 1
T: 64 27
R: 0 16
S: 0.1911 0.9418
L: 10048 2166
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 77582679 255704
OHFErr: 4251 5
RS: 0 2026189
RSCorr: 0 75
RSUnCorr: 0 0
Bearer 0
HEC: 9628 0
OCD: 495 0
LCD: 495 0
Total Cells: 1110293821 0
Data Cells: 241347497 0
Drop Cells: 0
Bit Errors: 0 0
ES: 1574 5
SES: 19 0
UAS: 58 48
AS: 238132
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 3.06 12.76
OR: 62.55 20.05
AgR: 40035.61 8088.77
Bitswap: 132878/132884 13/13
Total time = 1 days 7 hours 37 min 12 sec
FEC: 0 75
CRC: 4251 5
ES: 1574 5
SES: 19 0
UAS: 58 48
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 7 min 12 sec
FEC: 0 0
CRC: 2 0
ES: 2 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: 0 0
CRC: 4 0
ES: 4 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 7 hours 37 min 12 sec
FEC: 0 6
CRC: 299 1
ES: 133 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 24
CRC: 1465 2
ES: 596 2
SES: 3 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 2 days 18 hours 8 min 51 sec
FEC: 0 75
CRC: 4251 5
ES: 1548 5
SES: 9 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
You appear to be on fastpath, I don't think there's anything more for DLM to give?
Have you disabled QOS on the HG612? It's in Advanced on the webgui. That should maximise your upstream.
-
Just disabled it now, havent noticed any change in upstream level. Whats retrain reason: 1? I am afraid that my line may be unable to handle fastpath and move me back to interleaving. Are my errors normal or too high?
-
Have you checked the trafiic lights on your MDWS page?
This post explains Retrain Reason 1 http://forum.kitz.co.uk/index.php/topic,12504.msg236045.html#msg236045
-
First light is green then the middle on and the bottom are orange on the first traffic light, rest is green.
-
This is the thread about the traffic lights http://forum.kitz.co.uk/index.php/topic,15623.msg290968.html#msg290968
-
thanks @Dray, useful stuff
Anyone knows why my DL SNR margin is about 10dB instead of 6dB that always used to be.
-
The higher DL SNR margin are better because you will gained more attainable line rate on your line.
-
I think you said you moved from Infinity 2 to Infinity 1 so your connection is now capped to 40/10.
-
Yeah, but this happened 1-2 days before they capped my speed.
@adslmax, my attainable line rate is around 48mbps, it used to be over 50mpbs with SNR margin of 6.0dB
-
Can you post screenshot of your DSLStats please
As mine stats here: Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 11.5 15.9
Attenuation (dB) 11.6 0.0
Output Power (dBm) 12.4 -0.1
Attainable Rate (Kbps) 102567 35253
Rate (Kbps) 79999 20000
-
I think this is what you're asking for.
Stats recorded 29 jun 2015 01:22:42
DSLAM/MSAN type: IFTN:0xb204 / v0xb204
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 3 days 41 min 51 sec
Resyncs: 0 (since 28 jun 2015 12:45:38)
Downstream Upstream
Line attenuation (dB): 22,3 0,0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 39973 8069
SNR margin (dB): 10,1 6,2
Power (dBm): 12,6 5,8
Interleave depth: 1 1
INP: 0 0
G.INP: Not enabled
RSCorr/RS (%): N/A 0,0025
RSUnCorr/RS (%): N/A 0,0000
ES/hour: 24,2 0,08
-
Yeah, but this happened 1-2 days before they capped my speed.
Looking at your SNRM graph on MDWS it happened on June 26, when your modem last resynced.
-
I think it happened when I was swapping the modems between ECI and HG612 3B
-
That must be a guess as your stats weren't available on your ECI.
-
@adslmax, my attainable line rate is around 48mbps, it used to be over 50mpbs with SNR margin of 6.0dB
Bit strange to reduce attainable line rate from 50Mbps @ 6dB SNR to 48Mbps with 10dB SNR (possible due to crosstalk etc)
-
Attainable reduces when interleaving is removed.
-
@Dray, I could see the stats on HH5 helpdesk I think it was something about 52-54mbps.
On the MDWS page the lights are now orange on the first traffic light? Is it good or?
-
No, green is good but amber is BAD
-
so most likely DLM may do something? I remember I was getting weird lag spikes every 30secs few days ago.
-
Yeah, DLM may do something I guess. Should be better now though than it was before and you'll be able to see what's going on now you can see all the stats.
-
Is interleaving depth the same as delay? I mean can I have interleaving depth of for example 1000 and delay of 0 on both dl/up? I assume delay is the thing that increases latency? 8 delay means 8ms added to latency?
-
It's not that simple. see http://www.kitz.co.uk/adsl/linestats_errors.htm
-
This site doesn't give me any idea unfortunately :(
-
I just notice my SNR reduced and Line attainable rate today :(
Yesterday:
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 11.5 15.9
Attenuation (dB) 11.6 0.0
Output Power (dBm) 12.4 -0.1
Attainable Rate (Kbps) 102567 35253
Rate (Kbps) 79999 20000
Today:
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 8.2 14.2
Attenuation (dB) 11.6 0.0
Output Power (dBm) 12.4 0.1
Attainable Rate (Kbps) 91182 32751
Rate (Kbps) 79999 20000
-
@adslmax
This is what I said before, seems like lower SNRM gives you more attainable rate but you are getting full speed for your package so it doesn't matter I guess.
-
Looks like noise increased so attainable reduced
-
My connection just resynced and it applied interleaving of 849 for downstream which gives me 8ms delay unfortunately. Is there any posibility that it will remove it after a week or so? Why is my downstream rate 39998 instead of 39999kbps and upstream did not reach 9999kbps? (if stupid question I apologise)
Have I been on banded profile or did it just give me max attainable speed for infinity 1?
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 8290 Kbps, Downstream rate = 48828 Kbps
Bearer: 0, Upstream rate = 8061 Kbps, Downstream rate = 39998 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.4 6.1
Attn(dB): 22.3 0.0
Pwr(dBm): 12.6 5.8
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 47 238
M: 1 1
T: 64 27
R: 14 16
S: 0.0382 0.9427
L: 12992 2164
D: 849 1
I: 62 255
N: 62 255
Counters
Bearer 0
OHF: 585835 112954
OHFErr: 4 0
RS: 149870316 1802563
RSCorr: 13170 0
RSUnCorr: 63 0
Bearer 0
HEC: 10 0
OCD: 0 0
LCD: 0 0
Total Cells: 110427005 0
Data Cells: 2478095 0
Drop Cells: 0
Bit Errors: 0 0
ES: 5756 28
SES: 54 0
UAS: 93 72
AS: 1438
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.45 12.77
OR: 78.27 20.03
AgR: 40076.74 8081.31
Bitswap: 1058/1058 1/1
Total time = 1 days 15 hours 39 min 6 sec
FEC: 540950 253
CRC: 4208 0
ES: 5756 28
SES: 54 0
UAS: 93 72
LOS: 2 0
LOF: 18 0
LOM: 0 0
Latest 15 minutes time = 9 min 6 sec
FEC: 7899 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: 5271 0
CRC: 4 0
ES: 1 0
SES: 0 0
UAS: 6 6
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 15 hours 39 min 6 sec
FEC: 13170 0
CRC: 4 0
ES: 346 9
SES: 12 0
UAS: 35 24
LOS: 1 0
LOF: 9 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 0
CRC: 0 0
ES: 2514 6
SES: 17 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 23 min 57 sec
FEC: 13170 0
CRC: 4 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
No, green is good but amber is BAD
Green is good
Amber is OK
Red is bad
If you are wanting DLM to reduce the profile you have to stay green. If its amber then DLM takes no action one way or other.
-
Hi kitz,
Was waiting for you to answer to be honest!
My MDWS lights are all green at the moment but one changed to amber at the bottom of first traffic light for few hours then it changed back to green and now stays green. How long aprox do I have to wait for DLM to take an action?
I don't understand the timings for example 2400 secs (36 ES) for DL and 28800 (3 ES). My stats have been uploading to MDWS constantly so take a look if you can (nick: N0STIE)
Lets say my ping is 22ms to bbc.co.uk at the moment and 8ms delay due to interleaving made my ping 22ms so I assume if DLM removes my interleaving my lowest possible ping can be 14ms to bbc.co.uk with interleaving depth of 1 1 and there is no way to lower it? Is it due to ISP routing? I have seen many people with ping around 10ms to bbc.co.uk.
Thanks!
-
Anyone can tell me if the errors are acceptable? And when can I expect DLM to remove the delay? It's been nearly 7 days with interleaving applied.
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 8462 Kbps, Downstream rate = 48828 Kbps
Bearer: 0, Upstream rate = 8061 Kbps, Downstream rate = 39998 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.4 6.2
Attn(dB): 22.3 0.0
Pwr(dBm): 12.6 5.8
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 47 238
M: 1 1
T: 64 27
R: 14 16
S: 0.0382 0.9427
L: 12992 2164
D: 849 1
I: 62 255
N: 62 255
Counters
Bearer 0
OHF: 238767337 1200071
OHFErr: 904 42
RS: 994792868 2606190
RSCorr: 4351984 396
RSUnCorr: 59069 0
Bearer 0
HEC: 14354 0
OCD: 463 0
LCD: 463 0
Total Cells: 2064413553 0
Data Cells: 988658859 0
Drop Cells: 0
Bit Errors: 0 0
ES: 5962 62
SES: 54 0
UAS: 93 72
AS: 585694
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.45 12.77
OR: 78.27 20.03
AgR: 40076.74 8081.31
Bitswap: 339288/339306 43/45
Total time = 1 days 9 hours 56 min 42 sec
FEC: 4879764 649
CRC: 5108 42
ES: 5962 62
SES: 54 0
UAS: 93 72
LOS: 2 0
LOF: 18 0
LOM: 0 0
Latest 15 minutes time = 11 min 42 sec
FEC: 16804 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: 4503 0
CRC: 3 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 9 hours 56 min 42 sec
FEC: 86865 11
CRC: 3 1
ES: 1 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 421388 59
CRC: 53 12
ES: 16 11
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 6 days 18 hours 41 min 33 sec
FEC: 4351984 396
CRC: 904 42
ES: 207 34
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
Well, your 'traffic lights' are all green, which is good. It can take weeks for DLM to do anything, though (around 5 or 6 weeks in my case to remove interleaving), so you just need to be patient.
-
But its not that. 6ms is only the time taken to the bRAS - ie Manchester. The additional 6ms on top of that bringing it up to 12ms is all the way to London.
When you break that tracert down to its most simplistic form it interprets as
6ms - EU Premises <-> RAS - Enter the CORE Network at Manchester
12ms - EU Premises <-> London - Exit the CORE at Ealing London.
13ms - EU Premises <-> BBC - extra 1ms to get from Core exit point to the BBC server.
Following a short downtime in the early hours (PPP down, but no resync), I'm now seeing this:
traceroute to bbc.co.uk (212.58.244.20), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.226 ms 0.198 ms 0.196 ms
2 * * *
3 * * 31.55.186.133 (31.55.186.133) 8.260 ms
4 31.55.186.132 (31.55.186.132) 8.496 ms 8.950 ms 8.966 ms
5 core3-hu0-1-0-1.faraday.ukcore.bt.net (195.99.127.34) 10.504 ms 10.542 ms 10.542 ms
6 peer2-et-1-1-0.telehouse.ukcore.bt.net (213.121.193.163) 8.467 ms 8.005 ms 8.172 ms
7 194.74.65.42 (194.74.65.42) 8.864 ms 7.593 ms 7.427 ms
8 * * *
9 * * *
10 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 7.842 ms 7.850 ms 8.287 ms
11 132.185.255.149 (132.185.255.149) 8.382 ms 8.386 ms 8.552 ms
12 fmt-vip71.telhc.bbc.co.uk (212.58.244.20) 7.755 ms 7.590 ms 7.836 ms
Let's hope it stays this way!
-
Here is a comparison of mine on Zen.
Tracing route to bbc.co.uk [212.58.244.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 19 ms 21 ms 18 ms losubs.subs.dsl2.wh-man.zen.net.uk [62.3.87.147]
3 19 ms 18 ms 18 ms ae1-114.cr1.wh-man.zen.net.uk [62.3.87.169]
4 33 ms 26 ms 45 ms ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
5 25 ms 27 ms 24 ms ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41]
6 25 ms 25 ms 25 ms 82.71.254.134
7 * * * Request timed out.
8 * * * Request timed out.
9 25 ms 25 ms 25 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 26 ms 26 ms 26 ms 132.185.255.149
11 28 ms 25 ms 25 ms fmt-vip72.telhc.bbc.co.uk [212.58.244.18]
Trace complete.
-
@MikeZ
Cheers for answer! What if the lights change to amber or I will have a power cut?
-
@MikeZ
Cheers for answer! What if the lights change to amber or I will have a power cut?
My understanding is that amber means that DLM won't take any action either way - things will stay the same. One power cut shouldn't cause any problems - it's when you have a number of resyncs within a certain time frame.
The best thing to do is leave the modem connected 24 hours a day and, if you do need to power it off for any reason, leave it 30 minutes before powering back on again. Rebooting the router connected to the modem won't cause any DLM issues.
-
Yeah I am keeping it powered on as long as I can! Its been nearly 8 days now. I am hoping for DLM to remove this *bleep* interleaving of my line. I am getting only ~20 ES per day and not even 1 SES so I guess it is enough for DLM to remove it. With fast path on I was getting nearly 500 ES per day and 30 per hour although I haven't noticed any unstability on my line such as packet loss or sync loss so I think that DLM is no needed for some lines. (I was on fast path around 7 days just after I swapped the modems then it suddenly resynced and added 849 depth of interleaving and 8ms delay).
-
I just noticed that my UP SNRM has increased to 6.8dB from about 6.0-6.2dB just straight after my neighbours got installed virgin media this morning. This increased my attainable to over 9000 kbps. May that virgins installation cause that or maybe DLM sees something?
Any comments/suggestions appreciated.
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 9051 Kbps, Downstream rate = 48956 Kbps
Bearer: 0, Upstream rate = 8061 Kbps, Downstream rate = 39998 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.5 6.8
Attn(dB): 22.3 0.0
Pwr(dBm): 12.6 5.8
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 47 238
M: 1 1
T: 64 27
R: 14 16
S: 0.0382 0.9427
L: 12992 2164
D: 849 1
I: 62 255
N: 62 255
Counters
Bearer 0
OHF: 550431833 630830
OHFErr: 1897 82
RS: 3471492512 3720411
RSCorr: 8568744 779
RSUnCorr: 102246 0
Bearer 0
HEC: 24642 0
OCD: 847 0
LCD: 847 0
Total Cells: 692099758 0
Data Cells: 2287757208 0
Drop Cells: 0
Bit Errors: 0 0
ES: 6209 102
SES: 54 0
UAS: 93 72
AS: 1350203
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.45 12.77
OR: 78.27 20.03
AgR: 40076.74 8081.31
Bitswap: 786146/786189 113/117
Total time = 1 days 6 hours 18 min 31 sec
FEC: 9096524 1032
CRC: 6101 82
ES: 6209 102
SES: 54 0
UAS: 93 72
LOS: 2 0
LOF: 18 0
LOM: 0 0
Latest 15 minutes time = 3 min 31 sec
FEC: 162 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: 2643 2
CRC: 4 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 6 hours 18 min 31 sec
FEC: 73725 12
CRC: 8 1
ES: 2 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 406494 34
CRC: 61 5
ES: 21 5
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 15 days 15 hours 3 min 23 sec
FEC: 8568744 779
CRC: 1897 82
ES: 454 74
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
I thought this site is to get help from people they actually know stuff about networking. I feel like I am being ignored.
-
What do you want to know?
SNRM varies all the time depending on the noise level. It's only important when you resync as the modem aims for a target of 6 and sets the sync speed to achieve that.
If the SRNM falls a lot below the target, then the modem may resync on it's own.
-
I want to know if I can force DLM to force without delay/higher up speed anyhow? Its been over 17 days of uptime and still no respone from DLM.
-
No, you can't do that. The only circumstance in which a direct intervention can be made is a full line reset, and this can only be done after a line fault has been fixed.
-
Are you on Infinity 1 or Infinity 2?
-
I think I've mentioned before that it took around 6 weeks before interleaving was removed from mine. You just have to be patient :)
-
I am on Infinity 1 capped at 39998
@MikeZ 6 weeks? I thought it will be removing interleaving depth slowly like resyncing say every week and removing some of the depth and delay at the same time. What if DLM removes the interleaving and delay but after few days there will be high number of ES? May DLM put me back onto interleaving again?
-
I am on Infinity 1 capped at 39998
@MikeZ 6 weeks? I thought it will be removing interleaving depth slowly like resyncing say every week and removing some of the depth and delay at the same time. What if DLM removes the interleaving and delay but after few days there will be high number of ES? May DLM put me back onto interleaving again?
Yes - it removed US interleaving first (May 7th) then DS on June 2nd.
And, yes, if you start getting enough errors then DLM will intervene again.
-
What causes high numbers of ES on fastpath? Lack of INP which shows 0.00 on both US and DS? MikeZ I have noticed on MDWS that you are getting the same number of ES on fastpath than I being interleaved and delayed.
-
I am on Infinity 1 capped at 39998
Which modem are you using, which firmware/software versions is it using & are you connected to a Huawei cabinet?
If it's a Huawei cabinet, you may see G.INP applied in due course.
That should replace DS interleaving with a more efficient G.INP type of downstream error connection.
Upstream is currently on the equivalent to fastpath (interleaving depth = 1), but it does appear that a return to US G.INP error correction is now being rolled out again for users connected to Huawei cabinets (if it is needed).
-
I am using unlocked modem Huawei HG612 3B. Monitoring stats using DSLstats v5.5. I am on ECI cabinet with no G.INP enabled.
Product type: EchoLife HG612
Device ID: F4559C-21530315408K1B079638
Hardware version: VER.B
Software version: V100R001C01B030SP08
Firmware version: A2pv6C038m.d24j
Batch number: BC1P6.030.A2pv6C038m.d24j
-
Not ignored - Sorry just not around a lot due to family illnesses.. and with it being holidays time some others arent always around but theres normally a good bunch of people who do try and help answer.
Noise causes ES, so all you can do is check your internal wiring and monitor SNRm to see if you can see any patterns.
Mike may have the same E/S as you, but you may both be amber or green (I havent checked MDWS). If you want the DLM to relent then you have to stay green for 'x' period of time. 'x' depends on previous history of the line. First time you get interleaved it can be forgiving and remove it again in a couple of days, but if it removes it and then has to put it back on then next time you have to wait twice as long for it to be removed, and then if it goes back on again it takes even longer again before it will remove it the next time.
-
Well cheers kitz for reply.
The SNRM pattern I have noticed is that DS Margin always drops to 6.3-6.1dB at peak times (7pm-10pm) then it comes back to 6.6-6.7dB after peak times then during the night (1am till the morning it is even higher like 6.8-6.9dB. During the day its always 6.6-6.7dB (now 6.7dB).
US margin basically stays the same about 7dB now (used to be around 6.0-6.2dB) - as I mentioned in my previous posts it suddenly increased to 7dB and stayed like that same as DS margin. This increased my attainable speed so I assume its good.
I am getting only 20-40 ES per day. The lights on MDWS are all green for like 2 weeks now? maybe longer
My internal wiring is fine. Well line history, there was the line reset some time ago due to line fault when my SNR was dropping to 4.5dB every few days on HH5 in result my speed was 0.50mb and I was getting huge packet loss. And since the reset I am trying to keep my line stable without any disconnections. It has been 28 days now since HG612 connected.
Stats from now:
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 9307 Kbps, Downstream rate = 49344 Kbps
Bearer: 0, Upstream rate = 8061 Kbps, Downstream rate = 39998 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.7 7.0
Attn(dB): 22.3 0.0
Pwr(dBm): 12.6 5.9
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 47 238
M: 1 1
T: 64 27
R: 14 16
S: 0.0382 0.9427
L: 12992 2164
D: 849 1
I: 62 255
N: 62 255
Counters
Bearer 0
OHF: 722351201 810484
OHFErr: 2330 110
RS: 238210311 2060397
RSCorr: 11285385 995
RSUnCorr: 118429 0
Bearer 0
HEC: 28491 0
OCD: 981 0
LCD: 981 0
Total Cells: 3038803382 0
Data Cells: 3071127090 0
Drop Cells: 0
Bit Errors: 0 0
ES: 6350 128
SES: 54 0
UAS: 93 72
AS: 1771919
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.45 12.77
OR: 78.27 20.03
AgR: 40076.74 8081.31
Bitswap: 1039231/1039288 165/171
Total time = 1 days 3 hours 27 min 7 sec
FEC: 11813165 1248
CRC: 6534 110
ES: 6350 128
SES: 54 0
UAS: 93 72
LOS: 2 0
LOF: 18 0
LOM: 0 0
Latest 15 minutes time = 12 min 7 sec
FEC: 1391 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: 1933 1
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 = 3 hours 27 min 7 sec
FEC: 20230 3
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 516386 78
CRC: 109 13
ES: 33 11
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 20 days 12 hours 11 min 59 sec
FEC: 11285385 995
CRC: 2330 110
ES: 595 100
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Cheers!
-
What does your Hlog and QLN look like?
-
See attachment. No idea what QLN is and where to find it.
edit:
just found the QLN
-
See attachment. No idea what QLN is and where to find it.
edit:
just found the QLN
I'm getting slightly higher ES than you, enough to make the 'stable' traffic light amber. They've increased this week - probably because the schools are out :) I do have a significantly higher attainable rate, though, so plenty of headroom to play with, SNRM-wise...
-
Yeah just checked your MDWS stats, I thought they were much lower than now. Anyway you are on fastpath with 0.00 INP so your ES are higher then. I was getting around 30 ES/hour on fastpath then there was a burst which gave me 1161 ES - no idea why... then my MDWS lights became red and after that DLM applied high depth of interleaving till now.
-
Can anyone tell me why the errors @ 192.168.1.1 are different from DSLstats v5.5? I am a bit confused which are real ones and if they are acceptable.
Full stats from now from DSLstats over 30 days of hg612 3b powered on since purchased and 22 days since resync which added interleaving to my line.
By the way how do I monitor stats 24/7 like some people do. Do they have their PCs powered on all the time? As soon as I go to bed it aint monitoring over DSLstats.
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 9500 Kbps, Downstream rate = 49732 Kbps
Bearer: 0, Upstream rate = 8061 Kbps, Downstream rate = 39998 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.9 7.2
Attn(dB): 22.3 0.0
Pwr(dBm): 12.6 5.9
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 47 238
M: 1 1
T: 64 27
R: 14 16
S: 0.0382 0.9427
L: 12992 2164
D: 849 1
I: 62 255
N: 62 255
Counters
Bearer 0
OHF: 809963218 559441
OHFErr: 2531 131
RS: 1192050324 3389930
RSCorr: 12495686 1122
RSUnCorr: 126871 0
Bearer 0
HEC: 30469 0
OCD: 1058 0
LCD: 1058 0
Total Cells: 2376171381 0
Data Cells: 3558781703 0
Drop Cells: 0
Bit Errors: 0 0
ES: 6400 149
SES: 54 0
UAS: 93 72
AS: 1986830
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.45 12.77
OR: 78.27 20.03
AgR: 40076.74 8081.31
Bitswap: 1171032/1171097 192/199
Total time = 1 days 15 hours 8 min 58 sec
FEC: 13023466 1375
CRC: 6735 131
ES: 6400 149
SES: 54 0
UAS: 93 72
LOS: 2 0
LOF: 18 0
LOM: 0 0
Latest 15 minutes time = 8 min 58 sec
FEC: 460 1
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: 1968 0
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 = 15 hours 8 min 58 sec
FEC: 355530 31
CRC: 39 3
ES: 10 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 440116 34
CRC: 83 6
ES: 19 6
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 22 days 23 hours 53 min 49 sec
FEC: 12495686 1122
CRC: 2531 131
ES: 645 121
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
[attachment deleted by admin]
-
The error values reported in the HG612 GUI are mixed up, and should be ignored. The values obtained by telnet, which DSLstats and HG612_Modem_Stats use, are the correct ones.
You've got about 28 ES per day downstream, which is quite low.
The only way to monitor the stats 24/7 is to have a computer running 24/7. The low power option is to use a Raspberry Pi for this.
-
Looking at my stats it shows Max attainable as approx 80,500 but my actual sync speed is 74,002. Basically bang on. Maybe that is right but just looks strange to me.
If the line is interleaved, then the max attainable does go a bit skewy and show a higher figure than what would be obtainable if the line wasnt interleaved.
We dont know exactly why this would be, but my guess is something to do with RS overheads. In other words if the line is interleaved and has Error Correction applied, then sync connection speed has to be lowered because of the redundancy overheads.
Looks like you were correct on the max attainable being a bit iffy with interleaving applied.
This is the stats from the D6400 and HG612.
Last initialization procedure status: 0
Max: Upstream rate = 26040 Kbps, Downstream rate = 80441 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 74000 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): 7.5 9.7
Attn(dB): 17.5 0.0
Pwr(dBm): 13.6 7.5
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 174 97
M: 1 1
T: 0 0
R: 8 8
S: 0.0752 0.1554
L: 19456 5457
D: 16 8
I: 183 106
N: 183 106
Q: 16 8
V: 3 2
I since purchased a D7000 and noticed that G.INP 2 was also done so that took G.INP off the upstream. After 3 days use, It appears my interleaving depth was halved from 16 down to 8. This has never happened on any other modem on this line.
Max: Upstream rate = 16438 Kbps, Downstream rate = 73653 Kbps
Bearer: 0, Upstream rate = 16438 Kbps, Downstream rate = 72064 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): 6.1 5.9
Attn(dB): 17.2 0.0
Pwr(dBm): 13.6 7.6
VDSL2 framing
Bearer 0
MSGc: -6 22
B: 243 237
M: 1 1
T: 0 64
R: 10 16
S: 0.1078 0.4607
L: 18847 4411
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
This now appears more true to what my line can actually take instead of over inflated although now my BT checker for my line stats max should be just shy of 79/20 compared to previous of 73/20. I take that with a pinch of salt though.
I wonder if this modem could possibly reduce the interleave level again. As I said, This is the first time I've ever seen anything lower than 16 on the DS side.
-
Can anyone answer a question I have?
Theoretically speaking, If you maintained a clean line etc, Can G.INP be removed from the line?
-
I believe that it is possible. :-\
-
OK thanks, I done a fair bit of reading through the night and it appears I should want to keep it :-)
-
hi guys,
I think it is finally time to post something here! :)
Its been over 5 weeks now since last resync and over 6 weeks since modem has been powered on with minimal amount of errors and DLM hasn't done anything yet so sad about it. Is there any way to recycly mode or force it to resync by DLM?
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 8841 Kbps, Downstream rate = 48956 Kbps
Bearer: 0, Upstream rate = 8061 Kbps, Downstream rate = 39998 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.5 6.5
Attn(dB): 22.3 0.0
Pwr(dBm): 12.6 5.8
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 47 238
M: 1 1
T: 64 27
R: 14 16
S: 0.0382 0.9427
L: 12992 2164
D: 849 1
I: 62 255
N: 62 255
Counters
Bearer 0
OHF: 1333628307 1304217
OHFErr: 3678 201
RS: 2106326803 3396369
RSCorr: 19799986 1756
RSUnCorr: 166578 0
Bearer 0
HEC: 38993 0
OCD: 1396 0
LCD: 1396 0
Total Cells: 2317828225 0
Data Cells: 3541018293 0
Drop Cells: 0
Bit Errors: 0 0
ES: 6772 217
SES: 54 0
UAS: 93 72
AS: 3271375
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.45 12.77
OR: 78.27 20.03
AgR: 40076.74 8081.31
Bitswap: 1932396/1932520 368/381
Total time = 1 days 11 hours 58 min 3 sec
FEC: 20327766 2009
CRC: 7882 201
ES: 6772 217
SES: 54 0
UAS: 93 72
LOS: 2 0
LOF: 18 0
LOM: 0 0
Latest 15 minutes time = 13 min 3 sec
FEC: 20674 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: 7110 0
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 = 11 hours 58 min 3 sec
FEC: 227212 30
CRC: 22 4
ES: 9 4
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 522237 41
CRC: 108 2
ES: 29 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 37 days 20 hours 42 min 53 sec
FEC: 19799986 1756
CRC: 3678 201
ES: 1017 189
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
That 39998 sync makes me think your line might be banded...
-
What does it mean? Is it good or bad to be banded? I am on infinity 1 so its the max speed I can get I guess.
-
Sorry! I thought you were talking about the sync speed. Doh.
Regarding the interleaving, I think a single restart may help but don't do this until some others have confirmed :)
-
I've seen people report months of uptime until the DLM relented and put them back on fastpath. One user on the BT forum eventually got fastpath after a year but he did not say if he had previous issues or high noise on the line.
If you have had issues, You could be waiting longer than you already have. I would just leave it and check on a weekly basis.
-
@AlecR
Yep I am talking about sync speed actually :)
Which is 39998 instead of 39999 or 40000 no idea why. My line should handle easily full Infinity 1 speed as I was getting over 45mbps before on Infinity 2. Its been very long time since it resynced and added massive ammount of interleaving to my line + I am getting very low ES :)
@michty_me
Its been over 5 weeks now. Every day there is almost the same number of ES about 20-30. They appear usually at the evening and late night. No ES throughout the day tho. So I don't think there is a noise on the line. Connection is perfectly stable.
I had issues with down SNRM dropping below 6dB few months ago for some reason but it has been fixed now + there was DLM reset after that so there is no negative DLM history of my line I guess. Am I right?
-
You could perhaps report a fault and get the visiting OR engineer to reset the DLM?
I recall Plusnet sending out engineers for this specific purpose. In fact, I believe they've not even been required to attend the EU's premises :)
-
Yep I reported broadband fault, the engineer turned up and fixed the problem and reseted DLM at the same time I believe.
-
Then I suspect what will have happened is the DLM detected a high amount of errors in the first 24 hour period and so put interleaving on the circuit.
With the error counts seemingly very low now, I would think the DLM (once reset) would leave interleaving off.
Unless of course, DLM also takes into account FEC counts (which we are still unsure about). If that were true, perhaps because yours are quite high, DLM will be more reluctant to remove interleaving?
-
Interleaving was off for first week after swapping modems between ECI and HG612, the ES were still acceptable (about 20 per hour) but what has happened was the burst of ES (1161 in just an hour) then on the next day DLM put interleaving on till now. The FECs are around 500.000 a day, is it high isn't it?
-
My understanding is the higher your interleaving then usually you will see higher FEC's and lower CRC errors.
-
Ok, so I just had a power outage for a few minutes (no idea what happened exactly) IT WASN'T DLM RESYNC! then it came back and I have noticed that it f.... up my connection by far. Interleaving depth is now 1283 and the SNRM dropped a bit as well. Haven't noticed any changes in ping tho. The speeds are almost the same (a little drop of upload speed) and the upstream attainable dropped a bit although downstream stayed the same.
By the way after it came back I immediately unplugged the DSL cable the powered off the modem, waited about 30 mins then powered it on and plugged DSL cable back.
What can I do with this now?
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 8610 Kbps, Downstream rate = 49628 Kbps
Bearer: 0, Upstream rate = 8423 Kbps, Downstream rate = 39994 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.4 6.1
Attn(dB): 22.3 0.0
Pwr(dBm): 12.6 6.2
VDSL2 framing
Bearer 0
MSGc: 18 28
B: 31 238
M: 1 1
T: 64 30
R: 10 16
S: 0.0255 0.9023
L: 13200 2261
D: 1283 1
I: 42 255
N: 42 255
Counters
Bearer 0
OHF: 436572 79157
OHFErr: 2 0
RS: 167488592 453196
RSCorr: 9963 0
RSUnCorr: 4 0
Bearer 0
HEC: 1 0
OCD: 0 0
LCD: 0 0
Total Cells: 82286137 0
Data Cells: 3994918 0
Drop Cells: 0
Bit Errors: 0 0
ES: 1 0
SES: 0 0
UAS: 194 194
AS: 1072
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.45 13.58
OR: 78.26 20.01
AgR: 40072.04 8443.55
Bitswap: 796/796 0/0
Total time = 21 min 6 sec
FEC: 9963 0
CRC: 2 0
ES: 1 0
SES: 0 0
UAS: 194 194
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 6 min 6 sec
FEC: 4226 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: 5737 0
CRC: 2 0
ES: 1 0
SES: 0 0
UAS: 194 194
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 21 min 6 sec
FEC: 9963 0
CRC: 2 0
ES: 1 0
SES: 0 0
UAS: 194 194
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 = 17 min 51 sec
FEC: 9963 0
CRC: 2 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
What are you wanting to do? Are you waiting to be put back onto "fastpath"? Or what is your main concern?
-
Yeah, the main concern is to be permamently on fastpath if possible.
-
Not much you can do really apart from to make your end as free from noise as possible. I removed all extensions in my house as they weren't used anyway. If that is all done then it is just a case of suck it and see. You may never get fastpath ping times like myself. The best I have seen is 24ms on VDSL.
-
I got 8ms on VDSL when I has G.INP. That's on TalkTalk.
-
I'm on g.inp with interleaved depth of 8/1. Must just be my location or the routing. The best I've seen is 24ms.
-
@mitchy_me
What extensions do you mean?
-
Just telephone extensions throughout the house.
I only have the master socket in the hall now with no internal extension sockets connected.
-
I don't even have telephone extension connection to the SSFP infinity. Just the RJ-11 cable to the HG612.
-
As far as I can see that last resync hasnt had any change in DLM profile
Youre still on @ lowest level
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
It should eventually remove it if your E/Secs remain low.
-
@kitz
It wasn't resync, it was power outage that happened last night. The only positive thing is that I gained 0.5mbps of upload speed.
It counted over 46 days of constant uptime but no resync then power outage happened.
-
I don't even have telephone extension connection to the SSFP infinity. Just the RJ-11 cable to the HG612.
You have probably done everything you can your end. I don't think you can do anything else other than wait and hope that it will return.
-
I've just had a re-sync myself with no idea of what it has changed. At present I can't really see my stats as I'm away from home. Only benefit I can see is that I've gained 1Mb d/s and maybe 0.5mb upstream.
-
I was checking a neighbor's computer for issues and noticed his SNR was high yet his sync was low. Anyway, I returned home to find my own connection has gone to hell too. Normally I get 25Mb down with an SNR of 8. Now I have this...
Any ideas what's going on? I did however noticed that interleaving has dropped from 4 to 2 now and INP has changed from 51 to 48 as well. Are they likely just messing with the exchange?
-
You have a very high snrm which seems unusual. Maybe it resynced when there was bad interference about. I would be inclined to turn the modem off for 30 mins and then see if you get the same when you power back on.
-
Powered off for a few minutes and turned it back on, it's back to normal now. 25Mb with INP of 51, SNR 8.9. Weird.
-
I don't suppose someone could take a look at my graphs in MDWS under Michty. See if you can see anything obvious that would prevent me from dropping to the next interleaving level of 1. As far as I can tell, All looks good.
-
Hello everyone!
I just noticed my modem get resynced at 4am and moved me to fast path but ES are massive, about 200 over 24h period. So I don't think I may stay on fastpath, my line is just too bad to be on fastpath I assume.
-
200 ES in 24 hours isn't massive, it's well below the thresholds for action by DLM.
-
I thought it will stay like that, but it is now 444 ES over 19 hours and still counting. What for DLM put me on fastpath if my line can't handle it. I pressume I will be back to interleaved in a couple of days.
-
Have a look at your MyDSLWebStats data. At the top left there are some little traffic lights, which give an indication of the likelihood of DLM intervention. Hover the mouse over each one to get a description of what they represent. If you're on a Speed profile (quite probable) then you're currently all green, so no danger of DLM intervention.
-
All of them all amber for downstream, and ES still counting :(
-
Amber is OK. It means that DLM won't intervene either way (either more intervention or less). Green means that DLM may eventually move in the direction of less intervention. Read about it here: http://www.kitz.co.uk/adsl/DLM.htm#DLM_categorising_the_line
-
I know that, but they are going to be red in a couple of hours, because the errors are still counting.
-
I had a reset at around 4:00am, my stats looked good no ES zero CRC and still my interleave went from 8\4 to 8\8. How's that happen then, surely I should be heading towards fastpath?
-
No idea, if you are getting 0 ES/0 CRC after resync your interleaving depth should be lower or removed.
To be honest this is so annoying and stupid, only UK has these connection problems with stupid profiles that increase or decrease latency just because you restarted your modem. This is just hilarious. Other countries do not have that problem, they just get stable line with 1 steady ping that won't change even if you restart your modem multiple times. You should be allowed to restart your modem many times as you want without any consequences/changes to connection. But here I live in fear that random or even not modem reset will cause my line to increase latency. Like I reset my modem lets say 3 times now my latency will automatically increase by another 20ms, pretty much stupid.
That DLM software is a joke. Paying £40.00 for connection that is stable but that latency changes because of stupid errors are just unneeded. I don't know if it is just BT/Plusnet or all ISPs in UK that do this.
I am not here to complain, just saying the truth. I have no idea how UK is top 10 in internet connection speed ranking.
-
To be fair 8/8 is pretty low, i'm just surprised its there at all with stats such as I have. II don't have an A1 line, and G.inp has made a massive improvement, I guess there must be something that's triggering a response from the DLM, I'd just like to know what.
-
if these interleave depth doesn't change/increase your delay in miliseconds you should not worry about. I would rather have interleave depth of 500/500 and 0ms delay than 8/8 and some delay added.
-
Delay says 0/0 so no need to worry then.
-
Pretty much yes, you have lowest latency your line can handle, nothing to worry about unless you have any speed issues or unstable line.
-
Its there to stabilise a line. You are probably well aware of that. It saves OR getting called out every hour if someones line has crapped out. I've never been fastpath on VDSL2 and it hasn't mattered one jot. I would never notice 8ms of ping time. Not one person would at this low ping rates. I guess we both have rubbish lines and that is what we are destined for now mate. Certainly doesn't harm my gaming scores anyway.
-
Of course it is designed to stabilise the line, BUT why at the expense of ping? 8ms is just theoretically but in reality it is even more. Now I can notice much lower ping than before with delay of 8ms and game is smoother especially when I am playing on servers located in Sweden or any other country that is far away. It gives me 40ms now to them and before over 50ms. For example currently with fastpath enabled I am getting about 18-20ms in game called CS:GO to one specific server located in London that I have always been playing on and before with interleave I was getting about 30-32ms so it is not 8ms unless I can't count :P
-
Its there to stabilise a line. You are probably well aware of that. It saves OR getting called out every hour if someones line has crapped out. I've never been fastpath on VDSL2 and it hasn't mattered one jot. I would never notice 8ms of ping time. Not one person would at this low ping rates. I guess we both have rubbish lines and that is what we are destined for now mate. Certainly doesn't harm my gaming scores anyway.
My line is pretty stable if not perfect, if you look at my stats they are nearly all flat, no major variations except when it rains, then the upstream SNR drops from its normal 10-11 to as low as 7, but it does not appear to generate any major problems.
The only thing that's annoying me is the FEC count which I know is caused by the Central Heating. I've stuck filters & supressors all over the place and although I've reduced them, I cannot get rid of them completey.... and I'm not getting a new boiler just to get rid of the few hundred FEC's I get when the CH kicks in. :)
-
That must be the same as my stats then. There is barely any fluctuation at all, Very minimal errors but it remains interleaved. No idea why, Maybe a stuck profile. Who knows.
@Nostie, I get what you are saying. I used to game on American servers all the time for CS:S. Pings were always around 120-140ms. I didn't notice much difference. I must have been good at it :P
-
@mitchy_me
There is actually a huge difference, even between 20ms and 50ms in FPS games. I used to get pings such as 90ms to american servers, it was New Yorks one if I am correct. But it was right after BT installation, was getting 8ms to bbc.co.uk - good times I can say.
I would even pay more than 40 quid/month if BT leave me on fast path permanently with latency 10ms or below. Well 22ms is not that massive so I can't complain but 14ms much better though. 8ms is just the dream.
-
Old topic but I agree with N0STIE's post here. I had no ES on Downstream for several days and DLM increased my interleaving level from 8 to 16...
-
I highly doubt an interleaving level of 8 to 16 would have made any difference.
I went the opposite way after a year (16 down to 8) and it made absolutely no difference at all.