Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ColinS]

I don't quite know how to interpret this graph, but I'm only guessing it checks for latency and packet loss?

Yes.

Something I would like to know, how can get the Modem stats to be across my network, my HG533 TalKTalk router is at 192.168.1.1, so can I change anything around to make this possible?

The modem IP is settable to anything you like via the modem settings tab using the settings editor in the Scripts folder of HG612 stats.  You'd need to change the modem itself, via Basic/Lan/Lan Host settings, to the same value first though. Or you could (possibly) change your TT router's address.

[jid]

The modem IP is settable to anything you like via the modem settings tab using the settings editor in the Scripts folder of HG612 stats.  You'd need to change the modem itself, via Basic/Lan/Lan Host settings, to the same value first though. Or you could (possibly) change your TT router's address.

Only problem I've come across is when connected to LAN2, I've no internet connection? Do I need to set this up somewhere? 

[jid]

Bit loading in those low frequencies seems to have miraculously changed?? 

[ColinS]

Only problem I've come across is when connected to LAN2, I've no internet connection? Do I need to set this up somewhere? 

I'm not entirely sure what you mean?  Could you describe your set-up a bit more, with specific reference to which ports on which device are connected, and their respective IP addresses.
[Edit], if you meant that when you connect the router to Lan2 instead of Lan1, it doesn't work, this is as intended.  Connect the router to Lan1 as it is the only port bound to the PTM WAN connection (VDSL2) in the router by default. Lan2 is to allow you to connect to the router itself to collect the stats.

BTW, it's also occurred to me that perhaps the settings you are seeing (i.e. the values of Interleaving, INP and delay) have been set by TT in order to ensure the line is capable of withstanding noise without it affecting your IPTV.  In other words they're there to prevent that, not necessarily because it has happened.  But I have no idea how TT approach this, or whether these values have changed at all over time for you.

[ColinS]

Bit loading in those low frequencies seems to have miraculously changed?? 

Well, they can and do vary dynamically, but not normally as dramatically as this.  Has there been a resync?  Check your stats again, or the resync.log in the Ongoing stats directory. [Edit] Or possibly the bandwidth reservation has ceased?

[jid]

I'm not entirely sure what you mean?  Could you describe your set-up a bit more, with specific reference to which ports on which device are connected, and their respective IP addresses.
[Edit], if you meant that when you connect the router to Lan2 instead of Lan1, it doesn't work, this is as intended.  Connect the router to Lan1 as it is the only port bound to the PTM WAN connection (VDSL2) in the router by default. Lan2 is to allow you to connect to the router itself to collect the stats.

I found this yes, bound both LAN1 and LAN2 to the WAN and then lost access to the admin pages, so had to perform a long reset 

What I have is router to LAN1, then from the router LAN to Computer, then Homeplug to access point to extend WiFi. What I want is to be able to "see" the modem through my router (192.168.1.1), say by having the modem at 192.168.1.222 for example, is this something that is possible?

Therefore I've had to obviously reboot, however nothings changed anywhere, everything is as is before.

Maybe your theory on TalkTalk applying certain parameters to the line to be the case, although I thought the FTTC product is controlled by Openreach, and not the ISPs themselves?

Bit loading in those low frequencies seems to have miraculously changed?? 

Well, they can and do vary dynamically, but not normally as dramatically as this.  Has there been a resync?  Check your stats again, or the resync.log in the Ongoing stats directory. [Edit] Or possibly the bandwidth reservation has ceased?

They've gone back to how they were without the state of a few minutes, obviously a dynamic variation in the bit loading values as you say, no resyncs.

[burakkucat]

I would be interesting in seeing the latest version of the line_stats-P montage.

Looking at the earlier montage (reply no. 4, above), we can see quite definite (upward) spikes in the QLN graph (between tones 200 - 300, approximately) which correspond with the quite definite (downward) spikes in the SNR graph.

I wonder if there is some transmitter, local to Jamie's area, that was active when the data for the first montage was collected (1343 hours) and was inactive when the subsequent data was collected (1807 hours)?

[jid]

Attached is the latest line_stats-P after resync, and the one from 18:07 when the bit loading was normal

[ColinS]

What I have is router to LAN1, then from the router LAN to Computer, then Homeplug to access point to extend WiFi. What I want is to be able to "see" the modem through my router (192.168.1.1), say by having the modem at 192.168.1.222 for example, is this something that is possible?

Yes, assuming you have enough LAN ports on your router (or can get a mini-ethernet switch) .  Plug the router WAN connection into the modem LAN1 (like I assume you already do).  Plug your PC into the router LAN port 2 (like you currently do). Plug LAN port 3 on the router to LAN port 2 on the modem.  Adjust the modem's address as described above & reflect that in HG612's settings.  You can test this by telneting into the modem on its new address.

[ColinS]

Jamie,

for B*Kat & me, would you please use the settings editor for hg612, and 'Run Graphpd' specifying 1 d. This will create a new subdirectory in the Ongoing stats dir.  Look in there for the line_stats-FULL_MONTY file it here for us all. Thanks.

[jid]

Jamie,

for B*Kat & me, would you please use the settings editor for hg612, and 'Run Graphpd' specifying 1 d. This will create a new subdirectory in the Ongoing stats dir.  Look in there for the line_stats-FULL_MONTY file it here for us all. Thanks.

I'll get this to you tomorrow, I've only now properly set up the modem on my LAN - so I will run the main desktop all day tomorrow and this will hopefully get the information gathered, currently if I run it all the graphs are blank

[jid]

This may give the answer

To what Jamie?  It's not actually known whether or not these three so-called 'profiles' are made available to ISPs, but if they were, then what you assume may be right - but it wouldn't explain why your bit loadings change as much as they appear to do.

Answer to the high error correction that seems to be in place

Attached is a 2 Hour full monty image From what I can spot, there's spikes of FEC errors appearing, and at the same time Interleaving is correcting errors.

[burakkucat]

Further stats attached in case they work out the interleaving figure's strangeness!

Do you still have the raw data which produced the 1343 hours montage, Jamie? If yes, would you be willing to share that data with an inquisitive b*cat, please?

I would like to take a close look at the precise frequencies of those spikes in the 200 - 300 tone region. 

[Chrysalis]

yeah the line is interleaved but I am baffled as to why as your line should be in cruise mode.

run this in telnet to show error stats.

xdslcmd info --stats

Can I ask what "cruise mode" is?

Here we go:

Code: [Select]

xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max:    Upstream rate = 32734 Kbps, Downstream rate = 95680 Kbps
Path:   0, Upstream rate = 1999 Kbps, Downstream rate = 39999 Kbps

Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        17.4            31.0
Attn(dB):        0.0             0.0
Pwr(dBm):        12.7            5.2
                        VDSL2 framing
                        Path 0
B:              29              31
M:              1               2
T:              64              36
R:              16              16
S:              0.0239          0.9922
L:              15425           645
D:              2177            1
I:              46              80
N:              46              80
                        Counters
                        Path 0
OHF:            8442381         1207611
OHFErr:         0               0
RS:             2701561494              778467
RSCorr:         3559            0
RSUnCorr:       0               0

                        Path 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    1244018448              0
Data Cells:     18553515                0
Drop Cells:     0
Bit Errors:     0               0

ES:             0               0
SES:            0               0
UAS:            18              18
AS:             16176

                        Path 0
INP:            9.00            0.00
PER:            1.90            13.39
delay:          13.00           0.00
OR:             83.83           57.33

Bitswap:        134             109

Total time = 4 hours 29 min 54 sec
FEC:            3559            0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            18              18
LOS:            0               0
LOF:            0               0
Latest 15 minutes time = 14 min 54 sec
FEC:            0               0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            2               0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Latest 1 day time = 4 hours 29 min 54 sec
FEC:            3559            0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            18              18
LOS:            0               0
LOF:            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
Since Link time = 4 hours 29 min 35 sec
FEC:            3559            0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
#

cruise mode is me just using a figure of speech it isnt a specific dsl mode, so I mean the line should be trundling along very merrily as it has very high snr margin.

you have an uptime of only 4 hours, either you seem to be powering it down (or resetting it) a lot or the line is dropping out, also your FEC is high for 4 hours uptime, even if you had a 6db snrm that would be high but on a 17db thats just crazy.

Something somewhere is injecting noise/interference onto your line, it could be local or it may not be.

[jid]

Do you still have the raw data which produced the 1343 hours montage, Jamie? If yes, would you be willing to share that data with an inquisitive b*cat, please?

I would like to take a close look at the precise frequencies of those spikes in the 200 - 300 tone region. 

I should do B*cat, could you tell me where I could find it?

you have an uptime of only 4 hours, either you seem to be powering it down (or resetting it) a lot or the line is dropping out, also your FEC is high for 4 hours uptime, even if you had a 6db snrm that would be high but on a 17db thats just crazy.

Something somewhere is injecting noise/interference onto your line, it could be local or it may not be.

The uptime was short purely because I had swapped over from the ECI to Huawei modem, it had not dropped out or had it been reset. Since having Fibre, I've never witnessed a resync thats effected my service (although they may well have being going on in the wee hours of the night).

I do have a noisy line from ADSL2+ days, the cause was never found internally, I've a substation or two near me, so all possible causes

As you can see, FEC errors do continue to be a problem:

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max:    Upstream rate = 32734 Kbps, Downstream rate = 95776 Kbps
Path:   0, Upstream rate = 1999 Kbps, Downstream rate = 39999 Kbps

Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        17.4            31.0
Attn(dB):        0.0             0.0
Pwr(dBm):        12.6            5.1
                        VDSL2 framing
                        Path 0
B:              29              31
M:              1               2
T:              64              36
R:              16              16
S:              0.0239          0.9922
L:              15425           645
D:              2177            1
I:              46              80
N:              46              80
                        Counters
                        Path 0
OHF:            29798869                504636
OHFErr:         0               0
RS:             945703038               2500614
RSCorr:         14775           0
RSUnCorr:       0               0

                        Path 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    96014413                0
Data Cells:     21175229                0
Drop Cells:     0
Bit Errors:     0               0

ES:             0               0
SES:            0               0
UAS:            18              18
AS:             57091

                        Path 0
INP:            9.00            0.00
PER:            1.90            13.39
delay:          13.00           0.00
OR:             83.83           57.33

Bitswap:        515             1891

Total time = 15 hours 51 min 49 sec
FEC:            14775           0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            18              18
LOS:            0               0
LOF:            0               0
Latest 15 minutes time = 6 min 49 sec
FEC:            18              0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            22              0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Latest 1 day time = 15 hours 51 min 49 sec
FEC:            14775           0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            18              18
LOS:            0               0
LOF:            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
Since Link time = 15 hours 51 min 31 sec
FEC:            14775           0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0