Cisco 837 ADSL Dropping intermitantly 1

[DorsetBunny]

Hi Folks.

I have a Cisco 837 and a BT ADSL line. With the standard BT Homehub all is well (apart from it's config is locked down )

So I config'd my cisco to run and its up and good (for a while). Problem is it occasionally drops the DSL connection. (more often when the connection is stressed e.g. MW2).

I am running IOS 12.3(2)XE4 and its a 64/12MB version. I have done some debug output for you although I suspect its a line issue and as such little I can do as BT say the line is ok.



show dsl interface atm 0
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 0x0400
Vendor Country: 0x00 0xB5
Capacity Used: 100% 60%
Noise Margin: 6.5 dB 18.0 dB
Output Power: 20.0 dBm 12.0 dBm
Attenuation: 37.0 dB 21.0 dB
Defect Status: None None
Last Fail Code: Protocol error
Selftest Result: 0x00
Subfunction: 0x15
Interrupts: 689 (1 spurious)
Activations: 7
Init FW: embedded
Operartion FW: embedded
SW Version: 3.9.220
FW Version: 0x1A04

Interleave Fast Interleave Fast
Speed (kbps): 0 5600 0 448
Reed-Solomon EC: 0 0 0 0
CRC Errors: 0 1 0 0
Header Errors: 0 1 0 0
Bit Errors: 0 0
BER Valid sec: 0 0
BER Invalid sec: 0 0

the atm events are logged as follows;

Feb 12 00:12:58 10.10.10.1 120: Feb 12 00:12:04.703: DSL: Defect: LOS LOF LCDf LOM: retraining
Feb 12 00:12:58 10.10.10.1 121: Feb 12 00:12:04.703: DSL: Received response: 0x41
Feb 12 00:12:58 10.10.10.1 122: Feb 12 00:12:04.967: Resetting ATM0
Feb 12 00:12:58 10.10.10.1 123: Feb 12 00:12:06.107: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Feb 12 00:12:59 10.10.10.1 124: Feb 12 00:12:06.111: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Feb 12 00:12:59 10.10.10.1 125: Feb 12 00:12:06.715: %LINK-3-UPDOWN: Interface ATM0, changed state to down
Feb 12 00:12:59 10.10.10.1 126: Feb 12 00:12:07.107: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Feb 12 00:13:00 10.10.10.1 127: Feb 12 00:12:07.211: DSL: SM: [DMTDSL_SHOWTIME -> DMTDSL_RE_OPEN]
Feb 12 00:13:00 10.10.10.1 128: Feb 12 00:12:07.211: DSL: Send ADSL_CLOSE command.
Feb 12 00:13:00 10.10.10.1 129: Feb 12 00:12:07.211: DSL: Sent command 0x4
Feb 12 00:13:00 10.10.10.1 130: Feb 12 00:12:07.715: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
Feb 12 00:13:01 10.10.10.1 131: Feb 12 00:12:07.735: DSL: Received response: 0x25
Feb 12 00:13:01 10.10.10.1 132: Feb 12 00:12:07.735: DSL: Connection closed
Feb 12 00:13:01 10.10.10.1 133: Feb 12 00:12:07.743: DSL: SM: [DMTDSL_RE_OPEN -> DMTDSL_DO_OPEN]
Feb 12 00:13:01 10.10.10.1 134: Feb 12 00:12:07.743: DSL: Trying to bring up DSL line using Embedded firmware version : 3.9.220
Feb 12 00:13:01 10.10.10.1 135: Feb 12 00:12:07.743: DSL: Send ADSL_OPEN command.
Feb 12 00:13:01 10.10.10.1 136: Feb 12 00:12:07.743: DSL: Using subfunction 0x15
Feb 12 00:13:01 10.10.10.1 137: Feb 12 00:12:07.743: DSL: Using subfunction 0x15
Feb 12 00:13:01 10.10.10.1 138: Feb 12 00:12:07.743: LOCAL:Max noise margin for power cutoff 31
Feb 12 00:13:01 10.10.10.1 139: Feb 12 00:12:07.747: DSL: Sent command 0x3
Feb 12 00:13:03 10.10.10.1 140: Feb 12 00:12:10.247: DSL: 1: Modem state = 0x8
Feb 12 00:13:06 10.10.10.1 141: Feb 12 00:12:12.747: DSL: 2: Modem state = 0x10
Feb 12 00:13:08 10.10.10.1 142: Feb 12 00:12:15.247: DSL: 3: Modem state = 0x10
Feb 12 00:13:11 10.10.10.1 143: Feb 12 00:12:17.747: DSL: 4: Modem state = 0x10
Feb 12 00:13:11 10.10.10.1 144: Feb 12 00:12:19.611: DSL: Received response: 0x24
Feb 12 00:13:11 10.10.10.1 145: Feb 12 00:12:19.611: DSL: DSL line trained using Embedded firmware version : 3.9.220
Feb 12 00:13:11 10.10.10.1 146: Feb 12 00:12:19.611: DSL: Showtime!
Feb 12 00:13:11 10.10.10.1 147: Feb 12 00:12:19.611: DSL: Sent command 0x11
Feb 12 00:13:11 10.10.10.1 148: Feb 12 00:12:19.615: DSL: Received response: 0x61
Feb 12 00:13:11 10.10.10.1 149: Feb 12 00:12:19.619: DSL: Read firmware revision 0x1A04
Feb 12 00:13:11 10.10.10.1 150: Feb 12 00:12:19.619: DSL: Sent command 0x31
Feb 12 00:13:11 10.10.10.1 151: Feb 12 00:12:19.623: DSL: Received response: 0x12
Feb 12 00:13:11 10.10.10.1 152: Feb 12 00:12:19.623: DSL: operation mode 0x0002
Feb 12 00:13:11 10.10.10.1 153: Feb 12 00:12:19.623: DSL: Sent command 0x33
Feb 12 00:13:11 10.10.10.1 154: Feb 12 00:12:19.627: DSL: Received response: 0x16
Feb 12 00:13:11 10.10.10.1 155: Feb 12 00:12:19.627: DSL: Far End ITU Country Code 0xB5
Feb 12 00:13:11 10.10.10.1 156: Feb 12 00:12:19.627: DSL: Far End ITU Vendor ID TSTC
Feb 12 00:13:12 10.10.10.1 157: Feb 12 00:12:19.627: DSL: Far End ITU Vendor ID Specific 0x0400
Feb 12 00:13:13 10.10.10.1 158: Feb 12 00:12:19.631: DSL: Far End ITU Vendor STD Number 0x0001
Feb 12 00:13:13 10.10.10.1 159: Feb 12 00:12:19.631: DSL: Sent command 0x32
Feb 12 00:13:13 10.10.10.1 160: Feb 12 00:12:19.643: DSL: Received response: 0x14
Feb 12 00:13:13 10.10.10.1 161: Feb 12 00:12:19.643: DSL: Near End ITU Country Code 0x00
Feb 12 00:13:13 10.10.10.1 162: Feb 12 00:12:19.643: DSL: Near End ITU Vendor ID ALCB
Feb 12 00:13:13 10.10.10.1 163: Feb 12 00:12:19.643: DSL: Near End ITU Vendor ID Specific 0x0000
Feb 12 00:13:13 10.10.10.1 164: Feb 12 00:12:19.643: DSL: Near End ITU Vendor STD Number 0x0001
Feb 12 00:13:13 10.10.10.1 165: Feb 12 00:12:19.643: DSL: SM: [DMTDSL_DO_OPEN -> DMTDSL_SHOWTIME]
Feb 12 00:13:13 10.10.10.1 166: Feb 12 00:12:20.439: Resetting ATM0
Feb 12 00:13:13 10.10.10.1 167: Feb 12 00:12:21.611: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Feb 12 00:13:14 10.10.10.1 168: Feb 12 00:12:21.611: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
Feb 12 00:13:15 10.10.10.1 169: Feb 12 00:12:22.179: %LINK-3-UPDOWN: Interface ATM0, changed state to up
Feb 12 00:13:15 10.10.10.1 170: Feb 12 00:12:23.179: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
Feb 12 00:13:22 10.10.10.1 171: Feb 12 00:12:28.927: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up

I am using a high quality filter and cat52 (rj11) from wall to router in the engineers socket (with no other devices/extensions connected).

Are my suspicions correct and does anyone have experience in solving this type of issue (would asking BT to replace the cable from the junction to my wall socket help perhaps?)

Thanks in advance and hi btw

Rachel

 

[burtsbees]

Look at where your outside phone line comes into the junction box---this looks to be a line issue to me as well.

That cable that I am talking about---I had an issue like this---a tech came out and tested the line, found the freq to be too low---the line at the junction box outside was corroded.

/

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!

 

[DorsetBunny]

Thanks - I never thought there would be anything I could look at on the line. Anything else I can do (my tool set is limited to a voltmeter) - Guess if I had a line tester I could see it?

I'll take a look at that box.

Otherwise I guess its a call to my telecoms company (currently BT, but will be virgin as of Tuesday due to my wanting to speak to techies in my own country that I don't have to spell stuff to)

Rachel

 

[imbadatthis]

my experience on this side of the pond was that the tech blamed everything and anything he could on the Inside wiring (where the teleco's responsibility ends)

your best bet is to put a jack at the demark, and plug your router in there.
see if it synchs . if it does, then issue is your inside wiring, if it doesn't, at least you have proven its outside issue before you call BT ...

installing jacks are easy, its only pair 3 and 4 you need to connect for DSL ...

hope this helps a bit in trouble shooting.

cheers.

 

[DorsetBunny]

problem 'seems' to be resolved (still have 6db SNR during busy times, and sometimes gets to 8 off-peak)

I have a lovely XTE-2005 faceplate and cat5 cable with RJ11's to the router. No other devices/extensions are physically connected to the line.

I also had to add dsl noise-margin 3 to the atm int.