Print

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

[nfxcr3w]

So good news today interleave went down from 983 to 8 on the downstream and G.INP has been applied and my 6ms ping has come back also speed has increased from 56mb to 63mb how long till i get my speed back now since DLM seems to be working. Here are the stats do they look fine?

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   1
Last initialization procedure status:   0
Max:   Upstream rate = 23603 Kbps, Downstream rate = 67752 Kbps
Bearer:   0, Upstream rate = 20000 Kbps, Downstream rate = 68329 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.2       7.8
Attn(dB):    12.5       0.0
Pwr(dBm):    12.4      -1.7
         VDSL2 framing
         Bearer 0
MSGc:      -6      20
B:      243      239
M:      1      1
T:      0      64
R:      10      0
S:      0.1137      0.3819
L:      17870      5028
D:      8      1
I:      254      120
N:      254      240
Q:      8      0
V:      0      0
RxQueue:      56      0
TxQueue:      14      0
G.INP Framing:      18      0
G.INP lookback:      14      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      2171609
OHFErr:      0      24
RS:      464844472      1534704
RSCorr:      85      0
RSUnCorr:   0      0
         Bearer 1
OHF:      825960      0
OHFErr:      0      0
RS:      8258988      0
RSCorr:      0      0
RSUnCorr:   0      0

         Retransmit Counters
rtx_tx:      149515      0
rtx_c:      1      0
rtx_uc:      0      0

         G.INP Counters
LEFTRS:      0      0
minEFTR:   68307      0
errFreeBits:   13824420      0

         Bearer 0
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   1743263667      0
Data Cells:   5809235      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:      13      299
SES:      10      0
UAS:      64      54
AS:      13267

         Bearer 0
INP:      50.00      0.00
INPRein:   0.00      0.00
delay:      0      0
PER:      0.00      6.13
OR:      0.01      33.91
AgR:      68398.64   20033.74

         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:   2032/2032      20/20

Total time = 1 days 16 hours 4 min 38 sec
FEC:      22347      0
CRC:      5845      473
ES:      13      299
SES:      10      0
UAS:      64      54
LOS:      1      0
LOF:      9      0
LOM:      0      0
Latest 15 minutes time = 4 min 38 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:      6      0
CRC:      0      1
ES:      0      1
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 16 hours 4 min 38 sec
FEC:      1723      0
CRC:      5827      142
ES:      10      116
SES:      10      0
UAS:      36      26
LOS:      1      0
LOF:      9      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      20624      0
CRC:      18      331
ES:      3      183
SES:      0      0
UAS:      28      28
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 3 hours 41 min 7 sec
FEC:      85      0
CRC:      0      24
ES:      0      22
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
#

[tubaman]

Good news that G.INP has kicked in quite quickly.
To get more speed now you need to wait for DLM to drop the DS SNR from 6dB to hopefully 3dB if your line can support it.  This'll happen in 1dB steps over a number of days.
Be patient and it should get there.
 

[nfxcr3w]

Good news that G.INP has kicked in quite quickly.
To get more speed now you need to wait for DLM to drop the DS SNR from 6dB to hopefully 3dB if your line can support it.  This'll happen in 1dB steps over a number of days.
Be patient and it should get there.
 

Thank you I've seen my SNR drop on the downstream with my previous ISP to 2.2 SNR is that good? it took almost a year to drop down that low. It was stable on that low of a SNR

[dee.jay]

2.2 is a bit too low, 3dB is where it's at.

[nfxcr3w]

2.2 is a bit too low, 3dB is where it's at.

Thank you do you know what causes it to drop too low?

[tubaman]

Thank you do you know what causes it to drop too low?

It should have synced at 3dB but may then have dropped over time - or it may have been the time of day you looked at it as it does vary a bit throughout the day.
As long as it is stable with low errors then DLM should leave it alone.
 

[dee.jay]

Yes mine recently dropped to 2.5 and it was stable, but has since returned to 3 by itself.

[j0hn]

Thank you do you know what causes it to drop too low?

The target SNRM is 3, 4, 5 or 6dB.

Broadcom modems tend to sync with a slightly higher SNRM at 3.3, 4.3, 5.3 or 6.3dB.

Although your target SNRM may have been 3dB, the actual SNRM can go up and down after sync is achieved as noise comes and goes on the line.
The target is never below 3dB though.

DLM moves the target SNRM in 1dB steps.
It requires G.INP to be active to go below a 6dB target.

Now that G.INP is active hopefully the DLM will start to lower your target SNRM down towards 3dB.
It usually drops to 5dB around 48 hours after G.INP is enabled, and 4dB after another 48 hours, etc.

Stability is key so best not to fiddle if you want back to 3dB.

[nfxcr3w]

It should have synced at 3dB but may then have dropped over time - or it may have been the time of day you looked at it as it does vary a bit throughout the day.
As long as it is stable with low errors then DLM should leave it alone.
 

Thanks DLM is been good to me now i remember it was a bit harsh in the passed.

[nfxcr3w]

Yes mine recently dropped to 2.5 and it was stable, but has since returned to 3 by itself.

Nice i think the longer you leave it alone the more forgiving the DLM is on the SNR 

[nfxcr3w]

The target SNRM is 3, 4, 5 or 6dB.

Broadcom modems tend to sync with a slightly higher SNRM at 3.3, 4.3, 5.3 or 6.3dB.

Although your target SNRM may have been 3dB, the actual SNRM can go up and down after sync is achieved as noise comes and goes on the line.
The target is never below 3dB though.

DLM moves the target SNRM in 1dB steps.
It requires G.INP to be active to go below a 6dB target.

Now that G.INP is active hopefully the DLM will start to lower your target SNRM down towards 3dB.
It usually drops to 5dB around 48 hours after G.INP is enabled, and 4dB after another 48 hours, etc.

Stability is key so best not to fiddle if you want back to 3dB.

Thank you J0hn, I have a question about the Huawei Chipset I've noticed that the Broadcom DSLAM SW version got updated last year from BDCM:0xa48c (164.140) / v0xa48c to BDCM:0xc014 (192.20) / v0xc014 any reason for the change? Since i feel im the only one with this updated version.

[j0hn]

Has your cabinet had an extension added?

My DSLAM firmware updated when the Huawei 288 > 384 expansion was added.
I believe it may be reporting line card version which changes with a larger line card.

Though I haven't seen the version you report before now.

[nfxcr3w]

Has your cabinet had an extension added?

My DSLAM firmware updated when the Huawei 288 > 384 expansion was added.
I believe it may be reporting line card version which changes with a larger line card.

Though I haven't seen the version you report before now.

Yes it has I've seen the extension on the side of the cabinet which it never had before. Is this line card added for extra connections?

[j0hn]

Basically yes.
They swap out the current line cards for ones with more ports.
Swapping 32 port line cards for 64 port cards on the smaller cabinets or on the large Huawei cabinets it's swapping 48 port cards for 64 port cards.

The smaller Huawei cabinets have evolved through 24 > 32 > 48 and more recently 64 port line cards.

I believe the larger Huawei cabinets started with 48 ports.

Capacity upgrades are only done when necessary.

[nfxcr3w]

Basically yes.
They swap out the current line cards for ones with more ports.
Swapping 32 port line cards for 64 port cards on the smaller cabinets or on the large Huawei cabinets it's swapping 48 port cards for 64 port cards.

The smaller Huawei cabinets have evolved through 24 > 32 > 48 and more recently 64 port line cards.

I believe the larger Huawei cabinets started with 48 ports.

Capacity upgrades are only done when necessary.

Thanks J0hn for the explanation I think the Capacity needed to be upgraded since the last time i was with bt about a year ago around Christmas time it slowed down from 75mb all the way to 11mb BTW changed my SVLAN so many times that it didn't make a blind bit of difference till they gave up with me so it must of been a Capacity problem at the Huawei cabinet?