Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: Oldjim on August 17, 2016, 11:39:50 AM
-
After a period of several days where my upstream error seconds were awful in the heat of the day does the resync this morning mean that upstream G.INP has been enabled or just interleaving
-
Yes you have G.INP both upstream & down with a light sprinkling of interleaving (you won't notice it, the levels are extremely low). Huawei cabinet of course.
-
I wondered as it is only listed under downstream
Huawei Cabinet with Billion 8800NL
-
You're running a rather old version of DSLstats. Later versions show the downstream and upstream enablement of G.Inp separately, but the version you're using only shows a single value.
If you show us the contents of Telnet Data --> Connection Stats, that will give a better picture.
-
I assume that you mean this
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 243 244
M: 1 1
T: 0 0
R: 10 10
S: 0.1783 0.7771
L: 11397 2625
D: 8 4
I: 254 255
N: 254 255
Q: 8 4
V: 0 3
RxQueue: 33 15
TxQueue: 11 5
G.INP Framing: 18 18
G.INP lookback: 11 5
RRC bits: 24 24
Also - although probably not directly related my ping has increased
(http://www.thinkbroadband.com/ping/share-thumb/60912b48c9dfebeafccafd43b3a9dd61-17-08-2016.png)
-
That confirms that G.Inp is enabled both up and down, and as Underzone said, your interleaving levels won't noticeably increase latency. I don't know what's causing those big peaks in latency, but your average level is quite low.
-
The big peaks are down to Samknows testing
The increase in ping is a bit odd as it has been at the lower level for ages despite various resyncs not that it bothers me
-
The slight increase in ping could be you reconnected to your ISP via another of their gateways which may be further away or takes longer to process pings...
I used to see this a lot with Plusnet and with one of the gateways on Zen.
-
Well G.INP upstream really works - faster connected speed and no reported CRC errors at all
-
Well G.INP upstream really works - faster connected speed and no reported CRC errors at all
Yes I found it to be great when active, it;s a shame it's never stayed active for long :(
It seems to have a habit or coming into action then dropping back to fast path a couple weeks later, it's happened to me 3 times now, twice in my old home and once here at my new apartment.
Would say I'd like to see it again but I'm using a BTHH5a so not capability for it on Upstream here at the moment.
-
That didn't last long - now removed :(
-
That didn't last long - now removed :(
I know, it sucks don't it.
-
I've just installed a ew Billion 8800NL R2, there as an option in the DSL settings to enable PhyR and then two check boxes next to downstream and upstream...
By default downstream was checked but no upstream so I checked upstream and now overnight G.INP has been activated on my upstream.... I wonder how long it shall remain active :cool:
-
My 8800NL has the same thing so have set it - let us see what happens
-
One thing it did was initiate a resync
-
Evidently you already had G.INP on the upstream without checking the box for upstream PhyR, so it seems doubtful checking that box is going to get G.INP back into use on the upstream. It could have been a coincidence that the DLM decided to enable it for mlmclaren.
-
possibly but let us wait and see
-
Just a reminder that I (at least) am absolutely sure that the PhyR settings on the modem have absolutely nothing whatsoever to do with G.INP.
I experimented a month ago (http://forum.kitz.co.uk/index.php/topic,18102.msg328699.html#msg328699), and unticked the "Downstream PhyR" box the GUI of my 8800NL. Changing the setting caused a resync ... but the link came back up with downstream G.INP running, and it hasn't subsequently gone away.
-
Maybe the PhyR option on the 8800NL applies to ADSL only... Like the SNR tweaking.
-
SNR tweaking depends on how the DSLAM is configured. I expect it would work on VDSL2 if the DSLAM configuration permitted.
PhyR is a bit different. It's a Broadcom specific technology, and would only work with a DSLAM designed with that specific technology. G.Inp is similar but not the same, and I doubt very much if the PhyR controls in the modem would have any effect on G.Inp capability.
-
Resurrecting an old thread
For the last couple of days the upstream error seconds went through the roof - from under 10 per hour to around 200 per hour - presumably due to the high pressure forming.
Then this morning at about 9.00am the system reacted and G.INP is now on the upstream with the speed increasing from about 8,500 to 9,998 kbps and with no error seconds reported
-
Then this morning at about 9.00am the system reacted and G.INP is now on the upstream with the speed increasing from about 8,500 to 9,998 kbps and with no error seconds reported
Excellent news. Thank you for sharing.
-
Now I don't understand how DLM works on upstream
G.INP removed and set to minimum interleaving with speed reduced
Downstream Upstream
Line attenuation (dB): 21.2 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 41777 8374
SNR margin (dB): 6.6 5.0
Power (dBm): 12.6 4.6
Interleave depth: 8 1
INP: 47.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0173 0.0054
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0.36 26.1