Broadband Related > ADSL Issues

An ADSL2+ CIrcuit, Deliberately Restricted as ADSL2.

(1/6) > >>

burakkucat:
I wonder if the more analytical of our members would be able to interpret the following statistics, harvested from a ZyXEL VMG1312-B10A that is acting as the CPE on a long metallic pathway, and is configured to operate only in ADSL2 (ITU-T G.992.3) mode. In particular, do the error counts hint at any possible problem?  :-\

 > xdslctl info --show
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    8000
Last initialization procedure status:   0
Max:    Upstream rate = 417 Kbps, Downstream rate = 3428 Kbps
Bearer: 0, Upstream rate = 445 Kbps, Downstream rate = 3082 Kbps

Link Power State:       L0
Mode:                   ADSL2 Annex A
TPS-TC:                 ATM Mode(0x0)
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        3.1             5.8
Attn(dB):        64.0            40.3
Pwr(dBm):        18.2            12.4

                        ADSL2 framing
                        Bearer 0
MSGc:           52              14
B:              35              46
M:              4               1
T:              3               1
R:              12              12
S:              1.4717          3.3007
L:              848             143
D:              2               8

                        Counters
                        Bearer 0
SF:             64333918                789747
SFErr:          1539            42
RS:             2798525458              999616
RSCorr:         84573           8888395
RSUnCorr:       3343            0

ReXmt:          54454           0
ReXmtCorr:      51851           0
ReXmtUnCorr:    3462            0

                        Bearer 0
HEC:            3953            39
OCD:            9               0
LCD:            9               0
Total Cells:    3238169092              1089949025
Data Cells:     360612088               43423312
Drop Cells:     0
Bit Errors:     188262          3954

ES:             227             40
SES:            9               0
UAS:            180             180
AS:             1036442

                        Bearer 0
INP:            26.00           2.50
INPRein:        0.00            0.00
delay:          8               7
PER:            16.00           16.50
OR:             28.99           9.69
AgR:            3097.23 453.88

Bitswap:        259493/261876           38946/38946

boozy:
Hi B*Cat

1st Question - how long is the uptime?

You look as if you are having error bursts with 4% of Errored Seconds being SES... so I'm betting the problem is short lived and repetitive - have you got a ES graph?

I'm having experiments with two lines one of which has an SNR of 3 and the other of 11.  There's a surprisingly similar pattern on both lines despite the SNR difference. Your interference may be similar if the uptime is low (and have the same low chance of sussing it out if it is similar :().

j0hn:
Is that your line B*cat?
The presence of PhyR caught my eye.

burakkucat:
Thank you, both, for your comments.  :)

No, those harvested statistics do not relate to my circuit . . . but were "pushed under the door of The Cattery" early yesterday morning, with a note asking about the error counts. The only comment I could make was that without details of the relevant time-frame, etc, not a lot could be deduced.

RealAleMadrid:
The AS figure (Available seconds) indicates an up time of almost exactly 12 days.  :)

Navigation

[0] Message Index

[#] Next page