Cisco ADSL connection problem

Our main router at one of our site was having problems with dropping
the ADSL connection on a regular basis so I got onto BT and they ran
some tests on the line a said that there was some unkown interferance
on the line causing the connection to drop. Around the time of them
testing the line the connection totally dropped and has not been
connected since. BT came to site and and found that there was a "loose
connection in the master socket" and it was damp too - which must have
been causing the interferance. They connected their modem and
everything was working fine.
We plugged our router back in and nothing! Ive done some investigation
and run some commands on the router and it seems the router is unable
to see the ADSL on the line - see below.
Can anyone make any suggestions of anything to try? Could there be a
problem with the router now?
#show dsl int atm0
Alcatel 20190 chipset information
Line has not yet been activated. No information available.
DSL: Training log buffer capability is not enabled
#show int atm0
ATM0 is initializing, line protocol is down
Hardware is MPC ATMSAR (with Alcatel ADSL Module)
MTU 4470 bytes, sub MTU 4470, BW 4608 Kbit, DLY 80 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5 AAL2, PVC mode
10 maximum active VCs, 1024 VCs per VP, 0 current VCCs
VC Auto Creation Disabled.
VC idle disconnect time: 300 seconds
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops:
Queueing strategy: Per VC Queueing
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
#debug atm events
000873: *May 7 11:05:34.194 PCTime: DSL(ATM0): Received 1 timer
events during wait
000874: *
May 7 11:05:36.694 PCTime: DSL(ATM0): Received 2 timer
events during wait
000875: *May 7 11:05:39.194 PCTime: DSL(ATM0): Received 3 timer
events during wait
000876: *
May 7 11:05:41.694 PCTime: DSL(ATM0): Received 4 timer
events during wait
000877: *May 7 11:05:44.194 PCTime: DSL: No response from init_AMR-
000878: *
May 7 11:05:44.194 PCTime: DSL: Unexpected response 0x0 to
000879: *May 7 11:05:44.194 PCTime: DSL: SM: [DMTDSL_DLOAD_1 ->
000880: *
May 7 11:05:44.266 PCTime: DSL: SM: [DMTDSL_INIT ->
000881: *May 7 11:05:44.266 PCTime: DSL: Downloading init_AMR-
R-2.5.042_no_bist.binretry=0, reg=0x1
retry=1, reg=0x1
retry=2, reg=0x1
000882: *
May 7 11:05:44.290 PCTime: DSL: Could not send command 0x12
after 3 retries
000883: *May 7 11:05:44.290 PCTime: send command fails!!!
000884: *
May 7 11:05:44.290 PCTime: DSL: Could not download init_AMR-
Reply to
Jon Bev
Loading thread data ...
Hi John,
I have seen this 101 times on BT connections. Normally ends up being a problem with the line, however, all you can do is the normal checks. In no particular order:
1) Do you get dial tone when plugging an analogue phone in to the splitter (micro-filter) following the BT engineers visit 2) Have you changed the splitter - try at least 1 x other 3) Have you changed the RJ11 cable - rare to find these are faulty but I have had it a couple of times 4) Ask the carrier to do a whoosh test on the line to double check what the BT engineer told you 5) Try a second router / WIC card in your existing router if you have one
Appears to be no DSL on the line so I would swap the filter and cable and try this command again
Normally this goes all the way upto 0x26 and then gives you 'showtime' assuming all is OK. When you resolve the issue and get a CD light on on the router you will see this on the above debug.
Reply to
I have had some issues with 877 in the UK not working on DSL.
Manually setting the dsl operating mode seemed to help as did upgrading the IOS software.
Cisco have free downloads for patched DSL software for 877 if you fancied trying that.
Reply to
Bod43 Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.