Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: DANNYG on August 24, 2021, 02:39:25 PM
-
If you dont mind could you please take a look and let me know any info.
Many thanks.
BusyBox v1.9.1 (2014-01-21 16:44:38 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 30397 Kbps, Downstream rate = 75588 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 60000 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): 10.9 12.5
Attn(dB): 12.6 0.0
Pwr(dBm): 13.0 0.9
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 178 97
M: 1 1
T: 0 0
R: 10 8
S: 0.0950 0.1554
L: 15922 5457
D: 16 8
I: 189 106
N: 189 106
Q: 16 8
V: 2 2
RxQueue: 33 39
TxQueue: 11 13
G.INP Framing: 18 18
G.INP lookback: 11 13
RRC bits: 24 24
Bearer 1
MSGc: 122 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 8.0000 16.0000
L: 32 16
D: 1 1
I: 32 32
N: 32 32
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 0
OHFErr: 0 0
RS: 583674896 1588784
RSCorr: 117 40
RSUnCorr: 0 0
Bearer 1
OHF: 866116 869442
OHFErr: 0 0
RS: 6928435 3477768
RSCorr: 0 1
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 8089946 5
rtx_c: 5 89508
rtx_uc: 0 2811676
G.INP Counters
LEFTRS: 0 627
minEFTR: 59987 19991
errFreeBits: 12729484 1360055542
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1605176801 0
Data Cells: 592286527 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: 0 0
SES: 0 0
UAS: 71 71
AS: 13913
Bearer 0
INP: 48.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 60083.56 20102.08
Bearer 1
INP: 2.00 4.00
INPRein: 2.00 4.00
delay: 0 0
PER: 16.06 16.06
OR: 63.75 31.87
AgR: 63.75 31.87
Bitswap: 3703/3703 0/0
Total time = 3 hours 53 min 4 sec
FEC: 117 40
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 71 71
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 8 min 4 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: 27 7
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 = 3 hours 53 min 4 sec
FEC: 117 40
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 71 71
LOS: 0 0
LOF: 0 0
LOM: 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
LOM: 0 0
Since Link time = 3 hours 51 min 51 sec
FEC: 117 40
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Connection to host lost.
C:\Users\brigh>
[Moderator edited to wrap the statistics with [code][/code] tags.]
-
The line has been banded (capped) by the DLM at 60Mb.
If it wasn't for the cap you would get around 75Mb sync.
You would need your ISP to try arrange a DLM reset to get the cap removed but I can tell your right now that is very very unlikely to happen with Talktalk.
Banding is usually applied by the DLM due to too many resyncs in a short time period.
Sometimes it's the consequence of a genuine line fault resulting in repeated disconnections.
Quite often it self inflicted, the result of swapping modems or turning the modem on and off when diagnosing issues, or turning the properties power on and off when doing works.
Apart from that the line looks a nice clean short line.
-
With the banding removed and G.INP reducing the SNRM in steps to 3dB target value you should be able to get full 80Mbps sync on the line. :)
I have 79,999Mbps sync with a higher attenuation than your line.
-
Thank you for your reply's guys :)
-
The line has been banded (capped) by the DLM at 60Mb.
If it wasn't for the cap you would get around 75Mb sync.
You would need your ISP to try arrange a DLM reset to get the cap removed but I can tell your right now that is very very unlikely to happen with Talktalk.
Banding is usually applied by the DLM due to too many resyncs in a short time period.
Sometimes it's the consequence of a genuine line fault resulting in repeated disconnections.
Quite often it self inflicted, the result of swapping modems or turning the modem on and off when diagnosing issues, or turning the properties power on and off when doing works.
Apart from that the line looks a nice clean short line.
After a little while on the phone to TT the customer service agent was very nice help full and polite im sure she did the best she could however i dont think the reduced speeds was fixed i will be doing a line test tomorrow.
Again thank you for your help.
-
It needs an Openreach DLM reset to remove the banding, and unless the speed you're getting is lower than they guaranteed it's unlikely they'll do it as it costs them money.
-
Open reach DLM this would be from a service engineer?
-
Your ISP should submit a request to Openreach for a DLM reset, (if they know anything about banding ???). There is no engineer involved it is done remotely.
-
aww ok i get you now.
many thanks.
-
since i last posted ive been having some issues would you mind to take a look please.
# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 20268 Kbps, Downstream rate = 23656 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 25808 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): 7.1 6.0
Attn(dB): 33.8 0.0
Pwr(dBm): 12.9 6.6
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 227 244
M: 1 1
T: 0 0
R: 16 10
S: 0.2810 0.3885
L: 6947 5251
D: 4 4
I: 244 255
N: 244 255
Q: 4 4
V: 0 3
RxQueue: 60 30
TxQueue: 15 10
G.INP Framing: 18 18
G.INP lookback: 15 10
RRC bits: 24 24
Bearer 1
MSGc: 90 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 10.6667 16.0000
L: 24 16
D: 1 1
I: 32 32
N: 32 32
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 0
OHFErr: 60 1
RS: 696392772 3115347
RSCorr: 1911428 1807377
RSUnCorr: 0 0
Bearer 1
OHF: 3057494 972162
OHFErr: 9 8
RS: 18344592 3687321
RSCorr: 107 302
RSUnCorr: 9 0
Retransmit Counters
rtx_tx: 8125853 66195
rtx_c: 2843 91579
rtx_uc: 55611 2872296
G.INP Counters
LEFTRS: 77 866
minEFTR: 25805 19997
errFreeBits: 56406727 1424635159
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2437333945 0
Data Cells: 297605984 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: 30 239
SES: 29 0
UAS: 103 76
AS: 49110
Bearer 0
INP: 49.00 45.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 25864.80 20101.79
Bearer 1
INP: 2.50 4.00
INPRein: 2.50 4.00
delay: 0 0
PER: 16.06 16.06
OR: 47.81 31.87
AgR: 47.81 31.87
Bitswap: 38182/38182 10665/10678
Total time = 1 days 4 min 14 sec
FEC: 4059011 4394870
CRC: 1524 323
ES: 30 239
SES: 29 0
UAS: 103 76
LOS: 3 0
LOF: 23 0
LOM: 12 0
Latest 15 minutes time = 4 min 14 sec
FEC: 324 41684
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: 1882 207334
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 = 4 min 14 sec
FEC: 324 41684
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 4058687 4353186
CRC: 1524 323
ES: 30 239
SES: 29 0
UAS: 103 76
LOS: 3 0
LOF: 23 0
LOM: 12 0
Since Link time = 13 hours 38 min 29 sec
FEC: 1911428 1807377
CRC: 60 1
ES: 2 1
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
# xdslcmd info --stats
[Moderator edited to wrap the statistics with [code][/code] tags.]
-
What issues ?
-
im suppose to be on 65down and 20 currently getting like 19down 15 up
-
That's very odd to get the full US rate but only 26Mbps sync on the DS. Have you changed anything before this happened (junction box perhaps)?
:)
-
No i changed nothing they said there is a fault on the line and will be out to fix it.
No need to be home.
I just wondered if you could see anything.
I was going to change the junction box but this happend.
-
weird thing is i dont even have landline telephone working.
-
Your attenuation has gone right up, that’s the result of the fault. I think it’s just waiting for a response on the external fault.
-
weird thing is i dont even have landline telephone working.
This means that one wire from the copper pair is either loose from a joint or physically broken somewhere, internet can work on a single wire (but probably will drop down as in your case) but dial tone would never.
-
This means that one wire from the copper pair is either loose from a joint or physically broken somewhere, internet can work on a single wire (but probably will drop down as in your case) but dial tone would never.
That clears it up thank you.
-
weird thing is i dont even have landline telephone working.
That accounts for the odd behaviour of the Internet connection, exactly as mofa2020 has described. (In Openreach speak, you have a "one leg dis".)
-
They fixed it today also my speeds seem to be up and down a bit around 50/15 :)so i guess its best to leave it all well enough alone no modem resets let the DLM do its thing?
Many thanks.
-
Yep, The gods of DLM must be so mad with the line fault so a step up in speed means the reason for being angry is gone and now only time can bring calmness again "so I guess its best to leave it all well enough alone no modem resets let the DLM do its thing" ;)
-
Would the OR engineer not have initiated a DLM reset for you anyway? As a matter of course?
-
Would the OR engineer not have initiated a DLM reset for you anyway? As a matter of course?
He/She should have but it can take a week or 2 for the DLM to optimize a line connected to a Huawei cabinet.