Changes to DLM Incoming

Forums › New Zealand Broadband › Changes to DLM Incoming - ADSL & VDSL

1 | ... | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | ... | 44

18 posts

Geek
+1 received by user: 1

Reply # 1827536 23-Jul-2017 12:14

@hio77:

Thank you for the quick response. I can probably arrange for someone to get the stats for each line from our modems - may take a day or so. (I like your graphing and stat collection - may be I should aim to set that up for myself!)

RE the electrical spike issue, I'm not sure if that was measured or postulated. (this may have been from 18 months to 2 years ago when we were looking at reasons for the instability issues on Line 2, hence my reference to possible lateral line issues). FYI, both lines are in the same cable 'bundle' - the demarc is about 300 from the exchange. I think the cable bundle is a direct bury under the footpath of the main street.

I'm not sure what espm means? (I did know the techs who installed the lines and helped maintain it. This helped because after raising a fault thru the ISP, we could discuss issues. Unfortunately, they have either retired or moved on. However, I did talk directly to the new tech the other day. Unfortunately, the tech's authority to troubleshoot seems to end with plugging the line in at the port, so any potential card issues seem to lie with Assure [speculation on my part as I'm not sure about how things work within Chorus, nor am I sure about the architecture within the exchange] ). FYI. I knew of someone else with a VDSL line from the same exchange with similar line-drop issues - after months of trouble shooting it turned out to be an intermittent loose screw in a Chorus junction box and a crook port at the ISP's server's end

Jase2985

8214 posts

Uber Geek
+1 received by user: 2783

Lifetime subscriber

Reply # 1827573 23-Jul-2017 13:14

its a shame your device isnt reporting errors correctly

what device is it?

anatokidave

18 posts

Geek
+1 received by user: 1

Reply # 1827607 23-Jul-2017 15:43

@Jase2985:

The most recent line stats were taken using a Draytek Vigor DV-130. Because it's a single port modem, I unplugged it from the router and plugged it directly into my lappy. It would not have been passing any data when I looked at line status.

On reflection, I could have used the 2750 instead, as it has multiple ports and I have configured a separate port through which I can manage the modem. (ie I can look at the line status thru this modem while its connected to the router)

Jase2985

8214 posts

Uber Geek
+1 received by user: 2783

Lifetime subscriber

Reply # 1827613 23-Jul-2017 16:14

One person supports this post

@anatokidave it doesnt need to pass data, the errors displayed are from the last time the modem synced. so its highly unlikely that any line would have an error count of zero. if its been up for a few hours there should be something there

i think i recall there being new firmware for it too which may or may not help

hio77

'That VDSL Cat'
9702 posts

Uber Geek
+1 received by user: 2253

Trusted

Spark

Subscriber

Reply # 1827981 23-Jul-2017 22:05

i'd get your hands on some clear details first.

in terms of my monitoring stack, i run a ELK stack with a "beats" built for my particular modems (although it should work with any broadcom based modem I simply have not built support for that as of yet)

I really do need to cleanup my repo before i can start posting it here - some of it is a little slapped together since GO is kinda weird..

in terms of techs, your right.. field techs can only do so much, just as assure techs can... and then you get outside plant techs... What a pain for faults that change hands tbh.

it is rare that they can do it all as such.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

anatokidave

18 posts

Geek
+1 received by user: 1

Reply # 1831579 26-Jul-2017 12:52

@Jase2985: yes, I recorded the line stats immediately after upgrading the firmware. Thanks for pointing this out; next time, I'll check the status before I make any changes.

@hio77: OK, some progress since the weekend:

On Monday, the ISP reported there had been almost a dozen line drops over the weekend on the 'bad' line (Line1), and none on Line 2. They also informed me that:

"- the line profile (of the slower line) was changed from 8b to 17a so it used more of the available spectrum. This hasn't fixed the underlying DSL issue.
Within each line profile Chorus has the ability to change and tweak it a lot more, however we do not have that kind of visibility and sadly Chorus do not provide us with that level of detail in their fault notes, even when requested. Sync wise we currently see the faster line at - 61160 / 8904 (61Mbps / 8.9Mbps) - while the slower line shows as - 50904 / 10560 (50Mbps / 10Mbps). Chorus records show both lines as " Service Stability: STABLE ", however there are clearly quite a lot of DSL drops on one of the lines, do we don't trust this. - "

After further follow up from the ISP, Chorus then changed the port on Line 1

Today I have received the following info:

" - Following up with Chorus they note no more than 1-2 DSL drops in a 24 hour period and they have asked we give it a week to allow DLM to complete as they seem confident it will be okay. The 50/10 connection appears to be stable on 17a while the 61/8.9 connection appears to be stable on 8b. - "

I still don't understand why there is a slower speed on the 17a profile when compared with the 8b on the other line. Anyway, I'll put that to one side for a while as I need line stability so I'll cross fingers and hope the line remains stable.

Only have to wait for four years until fibre becomes available ....

hio77

'That VDSL Cat'
9702 posts

Uber Geek
+1 received by user: 2253

Trusted

Spark

Subscriber

Reply # 1831581 26-Jul-2017 13:01

17a has a lower maximum power level, If you line can't make use of the further specturm this will result in a drop in power on paper.

Generally chorus actually do a good job at pulling alike results even on distant lines, i suspect they are somewhat pushing the limit a tad on those though...

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

Jarsky

135 posts

Master Geek
+1 received by user: 41

Reply # 1834470 31-Jul-2017 17:24

One person supports this post

@anatokidave:

The DLM changes over the past few weeks have resulted in the speed of one of my lines decreasing from 52 Mbps to below 40 Mbps, while another line increased from 47 Mbps to 61Mbps. What's up with this? It seems it's a continuation of VDSL2 issues I have had over the last 18 months - (long) explanation follows.

I have a post here where i've had similar issues which appear related to their ddDLM changes : https://www.geekzone.co.nz/forums.asp?forumid=39&topicid=215582

The thread is a bit messy because it first started as throughput - my line sync was fine even through modem reboots/changes, however throughput was down as low as 8Mbit.

The throughput issues stopped but then after some DSLAM outages for I guess maintenance, the sync dropped significantly.

I've just today had a loop fixed on my line, but that has existed since June 2016 when a tech was digging the cable outside.

It still doesn't explain the sudden drop of my speed from 68Mbit with the *damaged line* down to 35Mbit.

The main thing I have noticed though, is that SNR has gone from my previous 8-9dB up to 12dB when I experienced the speed drop.

I also use a Draytek DV130 - but I have also tried another VDSL modem as well with the same results. I also tried updating the DV130 firmware with no change either.

Be interesting to see if my line can resync at 70Mbit now i have a 93Mbit attainable....

Jarsky

135 posts

Master Geek
+1 received by user: 41

Reply # 1839290 4-Aug-2017 17:36

One person supports this post

Jarsky:

Be interesting to see if my line can resync at 70Mbit now i have a 93Mbit attainable....

And the line appears to have settled today - can't complain about that really for an Ikanos card.

> vdsl status
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 70012000 bps US Actual Rate : 24360000 bps
DS Attainable Rate :113931392 bps US Attainable Rate : 24616000 bps
DS Path Mode : Interleave US Path Mode : Interleave
DS Interleave Depth : 0 US Interleave Depth : 0
NE Current Attenuation : 11 dB Cur SNR Margin : 15 dB
DS actual PSD : -3. 0 dB US actual PSD : 14. 5 dB
NE CRC Count : 0 FE CRC Count : 0
NE ES Count : 0 FE ES Count : 0
Xdsl Reset Times : 0 Xdsl Link Times : 10
ITU Version[0] : b5004946 ITU Version[1] : 544e0000
VDSL Firmware Version : 05-04-08-00-00-06
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 0 dB Far SNR Margin : 11 dB
CO ITU Version[0] : b500494b CO ITU Version[1] : 4e530001
DSLAM CHIPSET VENDOR : < IKNS >

hio77

'That VDSL Cat'
9702 posts

Uber Geek
+1 received by user: 2253

Trusted

Spark

Subscriber

Reply # 1839295 4-Aug-2017 17:52

One person supports this post

Jarsky:

And the line appears to have settled today - can't complain about that really for an Ikanos card.

Yep not bad...

if i get a chance this evening i'll post up my lines, hitting 36mbit so about 21/1.1 and 18/1.2 on my side.... Quite happy now that ddDLM has calmed down.

Following this new found stability, I'm keen to see what i'll be getting once i finally finish the migration of both my lines (Last tests were 36/6 per line roadside)

might be able to break 70mbit once both are up :D

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

freakngeek

324 posts

Ultimate Geek
+1 received by user: 83

Reply # 1839424 5-Aug-2017 08:58

One person supports this post

Woohoo, got a ddDLM resync last night, Interleave depth dropped from 900+ to a much more manageable 160 = nice boost in actual DL speed

---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 75366000 bps US Actual Rate : 24564000 bps
DS Attainable Rate : 75060472 bps US Attainable Rate : 24563000 bps
DS Path Mode : Interleave US Path Mode : Fast
DS Interleave Depth : 158 US Interleave Depth : 8
NE Current Attenuation : 21 dB Cur SNR Margin : 6 dB
DS actual PSD : 9. 0 dB US actual PSD : 14. 2 dB
NE CRC Count : 0 FE CRC Count : 960
NE ES Count : 0 FE ES Count : 732
Xdsl Reset Times : 0 Xdsl Link Times : 4
ITU Version[0] : b5004946 ITU Version[1] : 544e0000
VDSL Firmware Version : 05-07-06-0D-01-07 [with Vectoring support]
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 31 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004244 CO ITU Version[1] : 434db1ad
DSLAM CHIPSET VENDOR : < BDCM >

sbiddle

27581 posts

Uber Geek
+1 received by user: 7045

Moderator

Trusted

Biddle Corp

Lifetime subscriber

Reply # 1839463 5-Aug-2017 10:24

I installed a VDSL2 connection this week that sync and delivers 100Mbps - a speedtest was limited to 94Mbps due to the VDSL2 modem in use only having a 100Mbps port.

Upstream is currently sitting at 38Mbps so it's going to be interesting to observe this in coming weeks to see how much closer to 50Mbps it can get.

hio77

'That VDSL Cat'
9702 posts

Uber Geek
+1 received by user: 2253

Trusted

Spark

Subscriber

Reply # 1839464 5-Aug-2017 10:26

sbiddle:
I installed a VDSL2 connection this week that sync and delivers 100Mbps - a speedtest was limited to 94Mbps due to the VDSL2 modem in use only having a 100Mbps port.

Upstream is currently sitting at 38Mbps so it's going to be interesting to observe this in coming weeks to see how much closer to 50Mbps it can get.

I've noticed the upstream at that rate can be heavily modem dependant.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

Jarsky

135 posts

Master Geek
+1 received by user: 41

Reply # 1839473 5-Aug-2017 11:08

freakngeek:

Woohoo, got a ddDLM resync last night, Interleave depth dropped from 900+ to a much more manageable 160 = nice boost in actual DL speed

---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 75366000 bps US Actual Rate : 24564000 bps
DS Attainable Rate : 75060472 bps US Attainable Rate : 24563000 bps
DS Path Mode : Interleave US Path Mode : Fast
DS Interleave Depth : 158 US Interleave Depth : 8
NE Current Attenuation : 21 dB Cur SNR Margin : 6 dB
DS actual PSD : 9. 0 dB US actual PSD : 14. 2 dB
NE CRC Count : 0 FE CRC Count : 960
NE ES Count : 0 FE ES Count : 732
Xdsl Reset Times : 0 Xdsl Link Times : 4
ITU Version[0] : b5004946 ITU Version[1] : 544e0000
VDSL Firmware Version : 05-07-06-0D-01-07 [with Vectoring support]
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 31 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004244 CO ITU Version[1] : 434db1ad
DSLAM CHIPSET VENDOR : < BDCM >

I wonder if your rate will stay constant with that FEC count

I noticed that we're on different VDSL firmware as well - that you're running one of the G.Vectoring ones. When I ran the "NZ & AU recommended" G.Vector one it dropped my speed significantly

freakngeek

324 posts

Ultimate Geek
+1 received by user: 83

Reply # 1839489 5-Aug-2017 12:05

One person supports this post

Jarsky:

I wonder if your rate will stay constant with that FEC count

I noticed that we're on different VDSL firmware as well - that you're running one of the G.Vectoring ones. When I ran the "NZ & AU recommended" G.Vector one it dropped my speed significantly

The Error rate data it seems to have kept from before the resync, does this after a reboot and Factory reset also
Only keeps upload data, DL gets reset every resync
Before the resync last night the FEC count on DL was over 9million, doesn't seem to affect the ddDLM sync any, probably due to the errors being corrected on the fly

Also never had a Saturday morning resync either, always Tuesday and Thursday mornings

I use FW MDM4 at the moment, seems most stable, MDM8 can give higher upload but also more CRC's
STD FW is rubbish as error reporting doesn't work.

1 | ... | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | ... | 44