Print

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

[myriad]

Having been on infinity for over a year on fastpath I was moved to interleaved a couple of months ago after I removed some internal wiring (so I probably caused some noise on the line at the time or made a few too many disconnections in a row) but it hasn't recovered to fastpath.

At the time I was using a Netgear D6400, but recently I decided to swap back to the HH5 in the vague hope this may help with DLM, the HH5 always syncs lower than the Netgear. Of course I was then hit by a power cut but two weeks after that there had been no disconnections and then the HH5 rebooted seemingly due to remote command, something called OpenRG. So I decided to swap back to the Netgear thinking that maybe there is some remote process that would prevent long stable periods on the HH5 anyway and try to monitor the stats using the Netgear.

Thing is I have no idea how to read the stats as good or bad, I have errors but I don't know if they are normal or abnormal in number. So below is a paste of the telnet data so far, if someone could help me understand if there is anything I can do to get back on fastpath then that would be great.

Now with webstats under user myriad if it helps.

adslctl info --stats
adslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 7473 Kbps, Downstream rate = 46418 Kbps
Bearer: 0, Upstream rate = 7473 Kbps, Downstream rate = 38933 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.3
Attn(dB):        25.7            0.0
Pwr(dBm):        11.4            4.3

                        VDSL2 framing
                        Bearer 0
MSGc:           18              26
B:              51              223
M:              1               1
T:              64              42
R:              12              0
S:              0.0425          0.9522
L:              12048           1882
D:              761             1
I:              64              112
N:              64              224

                        Counters
                        Bearer 0
OHF:            95744899                977095
OHFErr:         2935            607
RS:             3035764731              2769910
RSCorr:         6349326         0
RSUnCorr:       182303          0

                        Bearer 0
HEC:            44315           0
OCD:            41              0
LCD:            41              0
Total Cells:    2393279328              0
Data Cells:     1440553872              0
Drop Cells:     0
Bit Errors:     0               0

ES:             712             553
SES:            0               3
UAS:            27              27
AS:             261427

                        Bearer 0
INP:            3.00            0.00
INPRein:        0.00            0.00
delay:          8               0
PER:            2.73            10.03
OR:             70.31           25.50
AgR:            39003.64        7498.70

Bitswap:        123281/123281           517/520

Total time = 3 days 37 min 34 sec
FEC:            6349326         0
CRC:            2935            607
ES:             712             553
SES:            0               3
UAS:            27              27
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Latest 15 minutes time = 7 min 34 sec
FEC:            4550            0
CRC:            0               3
ES:             0               2
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Previous 15 minutes time = 15 min 0 sec
FEC:            20239           0
CRC:            17              0
ES:             5               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           N/A
Latest 1 day time = 37 min 34 sec
FEC:            45198           0
CRC:            20              5
ES:             6               4
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Previous 1 day time = 24 hours 0 sec
FEC:            2379308         0
CRC:            1049            162
ES:             279             152
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Since Link time = 3 days 37 min 5 sec
FEC:            6349326         0
CRC:            2935            607
ES:             712             553
SES:            0               3
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
#

[NewtronStar]

Thing is I have no idea how to read the stats as good or bad, I have errors but I don't know if they are normal or abnormal in number..

This looks like a ECI cabinet without any G.INP to hand there is rumor this will be enable again 1st quarter of 2017, are you connected to Huawei or ECI cabinet ?

If you look at Total time = 3 days 37 min 34 sec
FEC:            6349326         0
CRC:            2935            607
ES:             712             553
notice the ES: counts of 712 thats the total for 3 days if you divide that by 3 to get 1 day (24 hours) = 237 errored seconds that is quite high for an Interleaved line imagine what it would look like on fastpath way above the DLM  threshold of 2880 or 1440 depending on which ISP is in use

SNR (dB):        6.1             6.3
SNR Signal to noise ratio is showing a good target of 6dB so that's fine

D:              761             1
This is your interleaving depth DS & US and DS is Interleaved US is Fastpath

You ask how to get back to fastpath you will need to get those errored seconds down to less than 20 per day (24 hours)

[myriad]

I don't know what I am on, I thought I was on Huawei based on the type of cabinets I see around but I don't know for sure, is there something I can do to find out?

My SNR for DS has dropped a little now, min 5.7, at 5.9 currently, but those errored seconds are pretty consistent even when I was above 6 earlier.

So what is the likely cause of high errored seconds and what can I do about reducing them? Should I be noticing noise on the phone line or something?

[skyeci]

http://www.kitz.co.uk/adsl/cabinet-lookup.htm#fttc_cab_info

[NewtronStar]

Should I be noticing noise on the phone line or something?

And did you find any noise on phone line with a preferred cored phone ? and 2 out of 10 users will say yes to phone line noise if it has become that bad then the broadband will be significantly effected by big changes in SNRM and frequent lose of DSL signal with random changes of sync & attainable sync when phone rings or when making a call

[burakkucat]

I don't know what I am on, I thought I was on Huawei based on the type of cabinets I see around but I don't know for sure, is there something I can do to find out?

The output from an adslctl info --vendor command line, when connected either by telnet or by ssh into the Netgear device should output some useful information.

If there is a BDCM string present, it will be a cabinet equipped with either a Huawei SmartAX MA5616 or a Huawei SmartAX MA5603T DSLAM.
If there is a IFTN string present, it will be a cabinet equipped with an ECI Hi-FOCuS M41 DSLAM.

P.s. Welcome to the Kitz forum. 

[tbailey2]

I don't know what I am on, I thought I was on Huawei based on the type of cabinets I see around but I don't know for sure, is there something I can do to find out?

My SNR for DS has dropped a little now, min 5.7, at 5.9 currently, but those errored seconds are pretty consistent even when I was above 6 earlier.

So what is the likely cause of high errored seconds and what can I do about reducing them? Should I be noticing noise on the phone line or something?

Your cab is shown on MDWS (under the SNRM data on the top status bar) after your first hourly tone file uploads and you are on a Huawei ...

[myriad]

As expected I am on Huawei equipment:

ChipSet Vendor Id:      BDCM:0xa48c
ChipSet VersionNumber:  0xa48c
ChipSet SerialNumber:

My town shows all cabs as being Huawei too. Doesn't that mean G.INP would/should be available?

I only have a crappy phone at the moment as I just never have a phone plugged in, I'll get a BT phone and do some testing to see if I can reproduce bad results with it ringing or on a call.

[myriad]

I am just looking at the bt wholesale checker and it seems the VDSL range has changed since last month. Clean range used to be 39.8 - 29 and is now showing 35.2 - 27.4 and I am currently synced at 38993 with a max showing of 46425. Any chance that reducing my sync speed could help with my ES?

[NewtronStar]

Wonder why your line with D6400 is not picking up G.INP as it should > Kitz info

Compatible Modem/Routers known to work with G.INP:
Netgear D6400 - Now seems to be working.

[burakkucat]

Wonder why your line with D6400 is not picking up G.INP as it should

I wonder if the Netgear device has been updated to use the latest available firmware? 

[myriad]

Firmware is V1.0.0.52 so I don't know why I haven't got G.INP, my understanding is that this could reduce ping compared to interleaving?

[Sheepie]

I had DLM reset 8 days ago due to GEA migration, and it still has not activated G.INP.  (was active before DLM reset and Zen confirm they have it as enabled)

Lots of interleaving applied, more each day, sync down nearly 50% of what it was with no sign of why (no ES or loss of sync).

Zen said the only reason they can think of is that the DLM is not enabling G.INP because of some underlying fault that will need to be fixed first. Nothing they can do but raise a fault with BT and possible changes if the fault is my end of the master socket ;(

[forceware]

I cap my line, it greatly reduces my es, I stay on fastpath for ages now. Here's a useful link http://forum.kitz.co.uk/index.php/topic,16427.0.html

[Sheepie]

but you would have thought that G.INP should be the first thing that the DLM applies on G.INP enabled cabs since that will work much better than interleave and delay. I used to speed cap my connection to reduce ES before I had G.INP enabled some 18 months ago, once G.INP got enabled I never had a single ES (and no latency overhead!)

Seems to be a few people with G.INP enabled lines where G.INP is not being activated or de-activated recently (at least 4 people on MDWS), maybe something wider going on (by BT)......