877W DSL: Defect: LCDi: retraining

[maurice.walsh]

Hi All,

I've just replaced my 837 with a 877W and I'm having real problems with ATM0 going up and down all the time. With the 837 I have no problems, I've also purchased a new filter and I've disconnected the phone from the line. Today the 877W worked fine until 7pm (I guess when the Exchange got busy), now it stays up for about 10 or 20 seconds.

I've tried different atm operating mode, but none work.

Here's a debug atm events for when the line goes down, I've also attached a number of files with show run, show version, show dsl int atm0 and full debug that may help.

Thanks in advance

Maurice

001788: *Jan 11 04:01:32.310 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up

001789: *Jan 11 04:01:37.474 UTC: ATM0: atmsar_1a_setup_vc, vcinfo = 0x82DBD51C

001790: *Jan 11 04:01:37.474 UTC: ATM0 atmsar_vc_setup: vcd 1

001791: *Jan 11 04:01:37.474 UTC: atmsar_setup_cos(ATM0): vc:1 wred_name:- max_q:0

001792: *Jan 11 04:01:37.474 UTC: ATM0: VC setup successful (vcd = 1)

001793: *Jan 11 04:01:37.474 UTC: ATM0: atmsar_atm_get_stats,vcinfo = 0x0

001794: *Jan 11 04:01:38.014 UTC: ATM0: vcd = 1, safe_start called from periodic

001795: *Jan 11 04:01:38.454 UTC: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up

001796: *Jan 11 04:01:38.454 UTC: %DIALER-6-BIND: Interface Vi2 bound to profile Di0

001797: *Jan 11 04:01:38.454 UTC: atmsar_vc_tx_start(82789F04).

001798: *Jan 11 04:01:38.454 UTC: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x82A98298

001799: *Jan 11 04:01:38.454 UTC: atmsar_transmit_pak_wrapper: deq(82A98298). vcd: 1.atmsar_transmit_pak_wrapper : encap = Data

001800: *Jan 11 04:01:39.014 UTC: ATM0: vcd = 1, safe_start called from periodic

001801: *Jan 11 04:01:40.014 UTC: ATM0: vcd = 1, safe_start called from periodic

001802: *Jan 11 04:01:40.042 UTC: DSL: Defect: LCDi: retraining

001803: *Jan 11 04:01:40.466 UTC: atmsar_vc_tx_start(82789F04).

001804: *Jan 11 04:01:40.466 UTC: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x82D8A4CC

001805: *Jan 11 04:01:40.466 UTC: atmsar_transmit_pak_wrapper: deq(82D8A4CC). vcd: 1.atmsar_transmit_pak_wrapper : encap = Data

001806: *Jan 11 04:01:41.014 UTC: ATM0: vcd = 1, safe_start called from periodic

001807: *Jan 11 04:01:42.014 UTC: ATM0: vcd = 1, safe_start called from periodic

001808: *Jan 11 04:01:42.482 UTC: atmsar_vc_tx_start(82789F04).

001809: *Jan 11 04:01:42.482 UTC: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x822FEC88

001810: *Jan 11 04:01:42.482 UTC: atmsar_transmit_pak_wrapper: deq(822FEC88). vcd: 1.atmsar_transmit_pak_wrapper : encap = Data

001811: *Jan 11 04:01:42.542 UTC: atmsar_atm_lineaction(ATM0): state=0

001812: *Jan 11 04:01:42.542 UTC: ATM0: atmsar_1a_teardown_vc,vcinfo = 0x82DBD51C

001813: *Jan 11 04:01:42.542 UTC: atmsar_1a_teardown_vc(ATM0): vc:1 vpi:0 vci:38

001814: *Jan 11 04:01:42.542 UTC: DSL: SM: [DMTDSL_SHOWTIME -> DMTDSL_RE_OPEN]

001815: *Jan 11 04:01:42.542 UTC: DSL: Send ADSL_CLOSE command.

001816: *Jan 11 04:01:42.542 UTC: DSL(ATM0): Sent command 0x4

001817: *Jan 11 04:01:43.070 UTC: DSL: Received response: 0x25

001818: *Jan 11 04:01:43.074 UTC: DSL: Connection closed

001819: *Jan 11 04:01:43.074 UTC: DSL: SM: [DMTDSL_RE_OPEN -> DMTDSL_DO_OPEN]

001820: *Jan 11 04:01:43.074 UTC: DSL: Send ADSL_OPEN command.

001821: *Jan 11 04:01:43.074 UTC: DSL(ATM0): Using subfunction 0x0

001822: *Jan 11 04:01:43.074 UTC: LOCAL:Max noise margin for power cutoff 31

001823: *Jan 11 04:01:43.074 UTC: DSL(ATM0): Sent extended command 0x3

001824: *Jan 11 04:01:43.542 UTC: Service policy input policy output applied on 0/38

001825: *Jan 11 04:01:43.542 UTC: DBS is not configured on ATM0.1 vc 0/38

001826: *Jan 11 04:01:43.546 UTC: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

001827: *Jan 11 04:01:43.546 UTC: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di0

001828: *Jan 11 04:01:44.542 UTC: %LINK-3-UPDOWN: Interface ATM0, changed state to down

[americain]

Hello

I found these values in your debug.

Capacity Used: 100% 58%

Noise Margin: 13.0 dB 20.0 dB

Attenuation: 41.0 dB 20.5 dB

There are also a lot of CRC errors, due to the bad line.

The capacity used is at 100%, in download, but the noise margins look ok.

The capacity used should be lower than 85% to have a good line.

Check the noise margin and capacity by using the 837 and compare these values.

If I am right this is ADSLoPOTS, I see that the downstream attenuation is 41dB, this is rather high but this can be related to the distance between the router and the DSLAM or it can be an indication of a problem, see also the downstream capacity.

This can also mean that you can't have an ADSL speed of 6M, maybe you can ask your ISP to lower the speed if you can't find an other problem.

Are you sure that your line was ok with the previous router?

HTH

Frederic

[maurice.walsh]

I've put the 837 back on and it's fine.

I've also logged a call with my ISP to see what they say. It is ADSL over POTS and I think I am about 3km from the Exchange, which is a bit too far for 6m, I noticed that the 837 usually has the download at 4 to 5m, but the 877W was saying it was between 4.8 and 6m. I have noticed that since my ISP upgraded my line a few months back that the service is sometimes slower in the evening.

I think that there is something in the 877 that is less forgiving that the 837.

here's the sh dsl int atm0 from the 837

Moz837#show dsl int atm0

ATU-R (DS) ATU-C (US)

Modem Status: Showtime (DMTDSL_SHOWTIME)

DSL Mode: ITU G.992.1 (G.DMT)

ITU STD NUM: 0x01 0x01

Vendor ID: 'ALCB' 'TSTC'

Vendor Specific: 0x0000 0x0000

Vendor Country: 0x00 0xB5

Capacity Used: 99% 65%

Noise Margin: 13.0 dB 16.0 dB

Output Power: 20.0 dBm 11.5 dBm

Attenuation: 41.5 dB 22.5 dB

Defect Status: None None

Last Fail Code: None

Selftest Result: 0x00

Subfunction: 0x15

Interrupts: 646 (1 spurious)

Activations: 1

Init FW: embedded

Operartion FW: embedded

SW Version: 3.9.220

FW Version: 0x1A04

Interleave Fast Interleave Fast

Speed (kbps): 5056 0 448 0

Reed-Solomon EC: 232 0 49 0

CRC Errors: 1 0 0 0

Header Errors: 1 0 0 0

Bit Errors: 0 0

BER Valid sec: 0 0

BER Invalid sec: 0 0

LOM Monitoring : Disabled

DMT Bits Per Bin

00: 0 0 0 0 0 0 0 0 0 4 5 7 7 8 8 9

10: 9 9 9 9 8 8 8 7 8 7 7 6 4 4 0 0

20: 0 0 0 0 0 0 2 2 2 3 4 4 5 5 6 6

30: 7 7 8 8 9 9 9 9 9 A A A A A A A

40: 0 B A 2 B B A A B A A A A A A A

50: A A A 9 A A A A A A A A A A A A

60: A A A A A A A A A 9 A A A A A 7

70: 9 A A A A A A 9 9 9 9 9 9 9 9 9

80: 9 9 9 9 9 9 9 9 8 8 8 6 7 8 8 8

90: 8 8 8 8 8 8 8 8 8 8 8 7 7 7 7 7

A0: 6 5 7 7 8 7 8 7 7 7 7 7 7 6 6 5

B0: 6 6 6 6 6 6 6 7 6 7 6 7 6 7 6 7

C0: 7 7 5 6 6 6 6 6 5 5 5 5 4 4 5 5

D0: 5 5 5 5 5 5 6 6 5 4 5 5 5 4 4 4

E0: 4 4 4 4 4 5 5 5 4 4 4 5 2 4 4 4

F0: 4 4 4 3 2 0 0 0 0 0 0 0 0 0 0 0

Training log buffer capability is not enabled yet.

[americain]

Hello

This can be the result of the 877 having an other impedance than the 837 but the used capacity is still high, so it isn't the router which causes problems.

The variable speed is because ADSL tries to synchronise at a certain speed where it is stable, if there is loss(like in your case) it is possible that is synchronises at a lower speed than the normal ADSL profile or speed.

Maybe you can ask your ISP to downgrade to 5M or 4.5M(I don't know which ADSL profiles are possible with your ISP)

Ciao

[Aaron Harrison]

Hi All!

I'm also having some grief with an 877 (in the UK)... the most progress I've made so far is to go to this URL :

ftp://ftp.cisco.com/pub/access/800

Download the 3.0.10 ADSL firmware. Copy it to flash, and rename to this name exactly:

adsl_alc_20190.bin

This got mine trained up fine - prior to this it appeared to be dead...

Regards

Aaron

Please rate helpful posts...