Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 [2] 3

Author Topic: New cabinet / DSLAM - will local lines be moved?  (Read 2042 times)

Ronski

  • Helpful
  • Kitizen
  • *
  • Posts: 3188
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #15 on: March 15, 2019, 03:45:34 PM »

That's  good to hear, thanks for updating us.

Are you going to upgrade to 80/20?

The interleaving will be removed soon, hopefully in a few days but possibly longer.
Logged
Formerly restrained by ECI and ali,  now surfing along at 390/36  ;D

j0hn

  • Kitizen
  • ****
  • Posts: 2392
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #16 on: March 15, 2019, 03:51:24 PM »

Should switch from Interleaving to ReTx in 2 days.

Glad to hear everything went well.  :congrats: :yay: :clap: :thumbs:
Logged
Plusnet FTTC 80/20 -  ECI now Huawei cab
retx low @ 3dB target SNRM
Zyxel VMG1312-B10A bridged with 1508 MTU + Asus RT-AC68U running Asuswrt-Merlin

Bobsta

  • Member
  • **
  • Posts: 22
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #17 on: March 15, 2019, 04:14:27 PM »

That's  good to hear, thanks for updating us.

Are you going to upgrade to 80/20?

Yes, absolutely. Plusnet's tools currently won't let me order the 80/20 package which they believe is because the cabinet isn't officially open for orders. They're going to keep an eye on things and hopefully in the next week or two when databases are updated I can be bumped up.
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 26201
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #18 on: March 15, 2019, 06:13:18 PM »

There is just one thing that puzzles me . . .

In reply #3 you show two images of the new AIO cabinet.
In reply #11 you mention walking to the new cabinet, as your telephone and broadband services had been disrupted, and showed another image. This latter image does not match either of the two images in reply #3.

  ???
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

Ronski

  • Helpful
  • Kitizen
  • *
  • Posts: 3188
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #19 on: March 15, 2019, 06:40:28 PM »

It does, it's just end on, you can see the same wooden fence in both and also see the same white sign post in both.
Logged
Formerly restrained by ECI and ali,  now surfing along at 390/36  ;D

Bobsta

  • Member
  • **
  • Posts: 22
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #20 on: March 15, 2019, 11:06:21 PM »

It does, it's just end on, you can see the same wooden fence in both and also see the same white sign post in both.

Correct. I agree that the first two pics show the verge looking quite maintained versus the one in post 11... but I can assure you it's definitely the same cab. In fact the OR engineer is down in the trench/pit which you can see the covers for in the second pic (lower right corner).

Maybe this'll help (although I'm sure we've all seen enough green cabinet pics):
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 26201
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #21 on: March 15, 2019, 11:21:54 PM »

Ah, ha. Thank you. The curious kitteh now understands the physical layout.  :)
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

Alucidnation

  • Member
  • **
  • Posts: 58
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #22 on: March 16, 2019, 11:52:35 AM »

How does it show max sync at 82?

I though they were all capped at 80 or 40, package dependant?
Logged

Ronski

  • Helpful
  • Kitizen
  • *
  • Posts: 3188
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #23 on: March 16, 2019, 12:04:03 PM »

The modem shows what it considers to be the maximum attainable speed given no imposed limits, that is the speed he stated. It should be noted that if interleaving is applied then this figure will be incorrect and higher than it should be, it probably also doesn't take into account lower SNR targets, so maximum attainable speed would be higher if the SNR target was lowered.
« Last Edit: March 16, 2019, 12:40:04 PM by Ronski »
Logged
Formerly restrained by ECI and ali,  now surfing along at 390/36  ;D

Alucidnation

  • Member
  • **
  • Posts: 58
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #24 on: March 16, 2019, 12:18:49 PM »

Ah ok, so it is capped at 80 before transmission?
Logged

ejs

  • Kitizen
  • ****
  • Posts: 1939
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #25 on: March 16, 2019, 12:36:48 PM »

The max attainable rate will take into account whatever value the target SNRM is.
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 2392
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #26 on: March 16, 2019, 02:00:43 PM »

Ah ok, so it is capped at 80 before transmission?

All 80/20 lines are capped at 80Mb, even though the max attainable may be 99Mb.
If there wasn't an 80Mb cap then that 99Mb would be roughly where the line would sync.

The max attainable shows what they line would sync at if there was no cap at all, wether it was a 40Mb/55Mb/80Mb cap.

The way Interleaving/INP is applied on FTTC makes the max attainable over estimate.
Logged
Plusnet FTTC 80/20 -  ECI now Huawei cab
retx low @ 3dB target SNRM
Zyxel VMG1312-B10A bridged with 1508 MTU + Asus RT-AC68U running Asuswrt-Merlin

Alex Atkin UK

  • Reg Member
  • ***
  • Posts: 223
    • My Broadband History
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #27 on: March 16, 2019, 09:29:05 PM »

I actually have an interesting comparison having been on Digital Region.

I used to get a max attainable of 130Mbit and actual sync of 99.9Mbit, but once I switched to BT its never been that high.  I suspect something to do with the band plans.

Its quite depressing seeing my line syncing at 76Mbit these days though, my new second line is only hitting 63Mbit. :(

Don't get me wrong, I appreciate that other people have it WAY worse, but its never good to see things going backwards.
Logged
Modems: 2 x VMG3925-B10B V5.13(AAVF.12)C0-jumbo
Router: i5-7200U appliance running pfSense.
ISP: Zen Unlimited Fibre 2 + Plusnet Unlimited Fibre Extra.

Bobsta

  • Member
  • **
  • Posts: 22
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #28 on: March 19, 2019, 05:51:10 PM »

You folks were spot on... after ~36hrs active, at around 1am Sunday the modem resync'd, enabling G.INP and lowering the interleave depth from 1283 to 16 (resulting in my latency halving).

Reported max rates are now 81424 down / 29128 up.

Have ordered Plusnet Fibre Extra (80/20) which should go live overnight, so fingers crossed.  :fingers:
Logged

Bobsta

  • Member
  • **
  • Posts: 22
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #29 on: April 04, 2019, 12:05:33 AM »

Continuing the story... my 80/20 service went live as expected. Initially at:

Code: [Select]
Downstream Upstream
Line attenuation (dB):  9.0 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 71119 19999
SNR margin (dB):        6.2 15.4
Power (dBm):            13.0 -7.2
Interleave depth:        1391 1
INP:                    3.00 0
G.INP:                  Not enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0008 0.0350
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                0 1.28

Then after 48hrs G.INP kicked in and interleaving dropped:

Code: [Select]
Downstream Upstream
Line attenuation (dB):  9.1 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 79999 19999
SNR margin (dB):        6.6 15.7
Power (dBm):            13.1 -7.2
Interleave depth:        8 1
INP:                    52.00 0
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0001 0.0375
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                0 2.17

It's remained sync'd like that for 12 days but I've noticed that my BRAS profile is pretty poor, given my 79999 sync:
Code: [Select]
The current Downstream BRAS rate is: 70.61 Mbps
The current Upstream BRAS rate is: 20 Mbps
... by my maths, that's 88.26%

This is all with a stable downstream SnR of 6.5 dB - but with the dreaded ReTx High.
Here are my Connection Stats and G.INP stats taken earlier today:
Code: [Select]
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 32023 Kbps, Downstream rate = 85064 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79999 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.5 15.6
Attn(dB): 9.1 0.0
Pwr(dBm): 13.1 -7.2
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 162 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0647 0.3781
L: 21128 5374
D: 8 1
I: 171 127
N: 171 254
Q: 8 0
V: 2 0
RxQueue: 136 0
TxQueue: 34 0
G.INP Framing: 18 0
G.INP lookback: 31 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 0
I: 32 0
N: 32 0
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 1722291
OHFErr: 0 513
RS: 1204843304 3148605
RSCorr: 4129 4287
RSUnCorr: 0 0
Bearer 1
OHF: 62051486 0
OHFErr: 0 0
RS: 744617090 0
RSCorr: 22 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 659 0
rtx_c: 561 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 80011 0
errFreeBits: 1215976899 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 3012210997 0
Data Cells: 405054493 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: 10 449
SES: 10 0
UAS: 65 55
AS: 996691

Bearer 0
INP: 52.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80244.76 20063.54

Bearer 1
INP: 4.00 0.00
INPRein: 4.00 0.00
delay: 3 0
PER: 16.06 0.01
OR: 95.62 0.01
AgR: 95.62 0.01

Bitswap: 598693/598693 2819/2820

Total time = 1 days 10 hours 45 min 35 sec
FEC: 39925 7052
CRC: 6241 559
ES: 10 449
SES: 10 0
UAS: 65 55
LOS: 1 0
LOF: 3 0
LOM: 0 0
Latest 15 minutes time = 35 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
Previous 15 minutes time = 15 min 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
Latest 1 day time = 10 hours 45 min 35 sec
FEC: 152 59
CRC: 0 13
ES: 0 13
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 322 170
CRC: 0 24
ES: 0 23
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 11 days 12 hours 51 min 31 sec
FEC: 4129 4287
CRC: 0 513
ES: 0 413
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#

Code: [Select]
Downstream Upstream
General
rtx_tx          674              0               
rtx_c            576              0               
rtx_uc          0                0               
LEFTRS          0                0               
minEFTR          80001            0               
errFreeBits      1226737302      0               
Bearer 0
RxQueue          136              0               
TxQueue          34              0               
G.INP Framing    18              0               
G.INP Lookback  31              0               
RRC Bits        0                24             
Interleave depth 8                1               
INP              52.00            0.00           
INPRein          1.00            0.00           
Delay            0                0               
Bearer 1
Interleave depth 3                0               
INP              4.00            0.00           
INPRein          4.00            0.00           
Delay            3                0       

I've now capped the line at 70000 20000 to try to get ReTx low to kick in. I'm a bit fuzzy on why I wouldn't get ReTx set to low anyway, given the >6dB SNR margin and relatively low error rates. Is someone able to explain that please?

Now it's syncing at 70000 20000 the SNRM is nice and high. I'll post the G.INP stats tomorrow as I know j0hn has been tracking them. Fingers crossed that the 70000 cap is low enough - I may not have been heavy-handed enough, so let's see.

Stats are now:
Code: [Select]
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 31816 Kbps, Downstream rate = 85324 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 69999 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): 9.3 15.2
Attn(dB): 9.0 0.0
Pwr(dBm): 13.0 -7.2
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 138 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0629 0.3781
L: 18697 5374
D: 8 1
I: 147 127
N: 147 254
Q: 8 0
V: 5 0
RxQueue: 140 0
TxQueue: 35 0
G.INP Framing: 18 0
G.INP lookback: 31 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 0
I: 32 0
N: 32 0
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 460862
OHFErr: 0 0
RS: 115799768 2167821
RSCorr: 0 2
RSUnCorr: 0 0
Bearer 1
OHF: 113867 0
OHFErr: 0 0
RS: 1138054 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 810 0
rtx_c: 576 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 70007 0
errFreeBits: 2460334364 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 246175195 0
Data Cells: 848106 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: 10 456
SES: 10 0
UAS: 96 86
AS: 1829

Bearer 0
INP: 52.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 70442.73 20063.54

Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01

Bitswap: 908/908 0/0

Total time = 1 days 14 hours 17 min 5 sec
FEC: 39947 7068
CRC: 6241 566
ES: 10 456
SES: 10 0
UAS: 96 86
LOS: 1 0
LOF: 3 0
LOM: 0 0
Latest 15 minutes time = 2 min 5 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
Previous 15 minutes time = 15 min 0 sec
FEC: 0 2
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 = 14 hours 17 min 5 sec
FEC: 174 75
CRC: 0 20
ES: 0 20
SES: 0 0
UAS: 31 31
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 322 170
CRC: 0 24
ES: 0 23
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 30 min 29 sec
FEC: 0 2
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Logged
Pages: 1 [2] 3