Cisco 857 dropping atm interface O2

[tjbradford]

I have a Cisco 857 that keeps dropping the atm interface

Cisco#sh dsl int atm 0
ATM0
Alcatel 20190 chipset information
ATU-R (DS) ATU-C (US)
Modem Status: Showtime (DMTDSL_SHOWTIME)
DSL Mode: ITU G.992.5 (ADSL2+) Annex A
ITU STD NUM: 0x03 0x2
Chip Vendor ID: 'STMI' 'BDCM'
Chip Vendor Specific: 0x0000 0x918F
Chip Vendor Country: 0x0F 0xB5
Modem Vendor ID: 'CSCO' ' '
Modem Vendor Specific: 0x0000 0x0000
Modem Vendor Country: 0xB5 0x00
Serial Number Near: FCZ104142D8
Serial Number Far:
Modem Version Near: 12.4(6)T5
Modem Version Far:
Capacity Used: 68% 99%
Noise Margin: 6.5 dB 9.0 dB
Output Power: 19.0 dBm 12.0 dBm
Attenuation: 32.0 dB 16.0 dB
Defect Status: None None
Last Fail Code: None
Watchdog Counter: 0x49
Watchdog Resets: 0
Selftest Result: 0x00
Subfunction: 0x00
Interrupts: 92635 (0 spurious)
PHY Access Err: 0
Activations: 83
LED Status: ON
LED On Time: 100
LED Off Time: 100
Init FW: init_AMR_4.0.018.bin
Operation FW: AMR-E-4.0.018.bin
FW Version: 4.0.18

DS Channel1 DS Channel0 US Channel1 US Channel0
Speed (kbps): 0 8192 0 1108
Cells: 0 170423 0 3489034
Reed-Solomon EC: 0 2405 0 0
CRC Errors: 0 0 0 0
Header Errors: 0 0 0 0
Total BER: 0E-0 0E-0
Leakage Avarage BER: 0E-0 0E-0
Interleave Delay: 0 7 0 0

LOM Monitoring : Disabled


DMT Bits Per Bin
000: 0 0 0 0 0 0 0 6 9 B B C C D D D
010: C D D D D D D D D D D C C B A A
020: 0 2 2 4 4 5 6 7 7 8 9 9 A A 9 9
030: A A B A B B B B B B B B B B B A
040: A B B B B B A B 2 A A B B A A A
050: A A A B A A A A A B A A A A A A
060: A A A A A A A 9 A 9 A A 9 9 9 9
070: 9 A 9 9 9 A 9 9 9 A 9 9 9 9 9 9
080: 9 A 9 9 9 9 9 9 9 9 8 8 4 8 8 8
090: 5 8 9 8 9 7 5 6 7 8 8 7 5 4 5 5
0A0: 2 0 4 7 7 5 8 8 8 7 8 8 7 4 6 8
0B0: 7 7 6 5 5 7 8 8 8 8 8 8 8 8 8 8
0C0: 8 8 8 8 8 8 8 8 7 8 8 8 8 8 8 7
0D0: 7 8 7 5 7 8 7 7 7 6 2 0 2 5 6 7
0E0: 7 7 7 8 7 7 8 7 7 7 6 7 8 8 7 7
0F0: 7 7 8 7 0 8 8 7 8 8 7 7 5 5 7 7
100: 8 8 8 6 8 7 8 8 7 7 7 5 2 0 2 5
110: 5 7 7 7 7 5 5 7 7 7 4 7 7 7 7 7
120: 5 6 5 4 0 2 4 5 6 7 7 7 7 7 7 7
130: 8 7 7 4 7 7 7 7 7 7 7 6 6 5 3 0
140: 2 5 7 7 7 7 7 6 5 7 7 7 6 7 7 7
150: 7 6 3 6 7 7 7 7 7 6 7 7 7 7 7 7
160: 6 5 6 6 6 6 5 0 5 5 5 5 6 6 6 5
170: 5 5 5 4 4 5 5 5 5 5 3 5 5 5 5 5
180: 5 5 5 5 4 4 5 5 4 2 3 4 4 4 4 4
190: 4 4 4 4 4 4 4 4 4 0 3 4 3 4 3 3
1A0: 3 3 3 2 3 2 2 2 2 0 2 2 2 2 2 2
1B0: 2 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0
1C0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1D0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1E0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1F0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

DSL: Training log buffer capability is not enabled
Cisco#

as you can see i have tried upgrading the firmware
Operation FW: AMR-E-4.0.018.bin
FW Version: 4.0.18

but with no joy , bit unsure what else todo i have enabled logging on the interface and got the following


?*Jul 8 22:40:00.176: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 8 22:40:02.176: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 8 22:40:03.176: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down

sometimes it then reconnects other times i have to issue a shut noshut,

any ideas ?

 

[burtsbees]

Looks like an issue with the provider.

/

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!

 

[ChrisUK1978]

TJBradford,

I have been having exactly the same problem since October 28 @ 19:55. I am speaking directly with the MD of BE Broadband, and the head of customer services and attempting to convince them they have interoperability problems.

I am getting approximately 14 minutes service followed by 4 minutes downtime, its beyond a joke.

Can you PM me your details so I can send you some email addresses at BE / O2 that you can write to so we can pool our efforts?

Many thanks,
Chris.

 

[tjbradford]

cant find the pm button anywhere !

but yes i'm up for some testing


below is what i have started logging on my box

interface ATM0
mac-address ****.****.****.****
no ip address
ip virtual-reassembly
logging event atm pvc state
logging event atm pvc autoppp
logging event subif-link-status
no atm ilmi-keepalive
dsl operating-mode auto
!
interface ATM0.1 point-to-point
description ADSL2+ o2broadband
ip address dhcp
ip access-group Inbound in
ip access-group Outbound out
ip nat outside
ip virtual-reassembly
no snmp trap link-status
atm route-bridged ip
pvc 0/101
oam-pvc manage
encapsulation aal5snap



output of show log

*Jul 12 17:26:43.230: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 17:26:44.230: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 17:27:21.162: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 17:27:21.438: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 17:27:22.438: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 17:54:58.857: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 17:54:58.857: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 17:55:00.857: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 17:55:01.857: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 17:55:41.437: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 17:55:42.437: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 17:55:42.465: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 18:00:19.833: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 18:00:19.833: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 18:00:21.833: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 18:00:22.833: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 18:01:01.021: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 18:01:01.437: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 18:01:02.437: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 18:04:03.353: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 18:04:03.353: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 18:04:05.353: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 18:04:06.353: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 18:04:39.961: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 18:04:41.445: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 18:04:42.445: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 18:08:06.205: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 18:08:06.205: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 18:08:08.205: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 18:08:09.205: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 18:08:41.445: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 18:08:42.445: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 18:08:48.673: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 18:13:23.909: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 18:13:23.909: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 18:13:25.909: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 18:13:26.909: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 18:14:01.445: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 18:14:02.445: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 18:14:07.089: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 18:40:49.149: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 18:40:49.149: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 18:40:51.149: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 18:40:52.149: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 18:41:21.457: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 18:41:22.457: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 18:41:28.933: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 18:45:09.357: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 18:45:09.357: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 18:45:11.357: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 18:45:12.357: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 18:45:51.457: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 18:45:52.457: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 18:45:57.457: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 18:47:37.817: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 18:47:37.817: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 18:47:39.817: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 18:47:40.817: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 18:48:11.457: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 18:48:12.457: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 18:48:16.649: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 18:54:33.309: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 18:54:33.309: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 18:54:35.309: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 18:54:36.309: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 18:55:11.473: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 18:55:12.473: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 18:55:14.585: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 19:24:55.221: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 19:24:55.221: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 19:24:57.221: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 19:24:58.221: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 19:25:31.473: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 19:25:32.473: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 19:25:36.357: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 12 20:57:25.949: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 12 20:57:25.949: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 12 20:57:27.949: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 12 20:57:28.949: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 12 20:58:21.489: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 12 20:58:22.489: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 12 20:58:29.081: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 13 04:13:49.799: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 13 04:13:49.799: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 13 04:13:51.799: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 13 04:13:52.799: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 13 04:14:31.603: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 13 04:14:32.603: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 13 04:14:33.611: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 13 05:25:32.767: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 13 05:25:32.767: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 13 05:25:34.767: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 13 05:25:35.775: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 13 05:26:11.627: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 13 05:26:12.627: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 13 05:26:13.167: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 13 05:48:40.335: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 13 05:48:40.335: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 13 05:48:42.335: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 13 05:48:43.335: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 13 05:49:41.626: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 13 05:49:42.626: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 13 05:49:46.382: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 13 06:28:43.590: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 13 06:28:43.590: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 13 06:28:45.590: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 13 06:28:46.590: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 13 06:29:21.634: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 13 06:29:22.634: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 13 06:29:24.506: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 13 06:47:13.854: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 13 06:47:13.854: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 13 06:47:15.854: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 13 06:47:16.854: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 13 06:47:51.634: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 13 06:47:52.634: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 13 06:47:59.622: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 13 07:08:21.530: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 13 07:08:21.530: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 13 07:08:23.530: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 13 07:08:24.530: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 13 07:09:01.646: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 13 07:09:02.646: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 13 07:09:03.514: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Jul 13 07:45:41.850: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
*Jul 13 07:45:41.850: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
*Jul 13 07:45:43.850: %LINK-3-UPDOWN: Interface ATM0, changed state to down
*Jul 13 07:45:44.850: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
*Jul 13 07:46:21.650: %LINK-3-UPDOWN: Interface ATM0, changed state to up
*Jul 13 07:46:22.650: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Jul 13 07:46:22.758: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state

 

[tjbradford]

ok so i note the clock is wrong whoops

 

[ChrisUK1978]

TJBradford,

Is you drop me a message at chris.bailes (at) myrealbox.com we will see if we cannot co-ordinate the effort.

I am away from tomorrow, but will hopefully put you in touch with Louise before then.

All best,
Chris Bailes

 

[tjbradford]

mailed you, the 02 bband is at home which i am at work currently, I have a spare 857 to try although i'm sure this isn't the issue.

I wonder if it's BT playing a part in this as the equipment that the adsl goes back to in the exchange is still BT's i beleive, the reason i say this is due to someone else i know saying that they are experiencing the same issue and there with uk online.

there also cisco although 837 no a 57

 

[imbadatthis]

im on the other side of the world and i had similar issue.
whats the output of your

debug atm events

that will give you better idea, it should say where the problem lies.

also if they complain too much (like my 5th tech that showed up with a new modem did) , take them to your NID/demark (where your inside wire meets ISP wire) and plug it there and tell them to go stick it where the sun don't shine.

for me it turned out there is water in the lines, and im SOL. so im on coax now, making my 857w completely useless......

 

[tjbradford]

managed to grab the debug as per imbadatthis's request

.Dec 26 16:40:29.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:30.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:31.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:31.628: ATM0 DSL: Defect: LOM
.Dec 26 16:40:32.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:33.096: ATM0:atmsar_oam_enqueue_vc,pak = 0x820401EC
.Dec 26 16:40:33.096: atmsar_vc_tx_start(81C38D98).
.Dec 26 16:40:33.096: atmsar_transmit_pak_wrapper: deq(820401EC). vcd: 1.
.Dec 26 16:40:33.096: atmsar_transmit_pak_wrapper : encap = Raw
.Dec 26 16:40:33.112: atmsar_raw_rcv: pak->if_input = 0x81C3A05C,
pak->if_input->hwptr = 0x81C38D98 encap = 0x0
.Dec 26 16:40:33.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:34.128: ATM0 DSL: Defect: LOM
.Dec 26 16:40:34.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:35.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:36.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:36.628: ATM0 DSL: Defect: LOM
.Dec 26 16:40:37.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:38.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:39.128: ATM0 DSL: Defect: LOM
.Dec 26 16:40:39.128: DSL: Defect: LOS LOF LCDi: retraining
.Dec 26 16:40:39.128: DSL: Received response: 0x41
.Dec 26 16:40:39.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:40.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:41.384: ATM0: vcd = 1, safe_start called from periodic
.Dec 26 16:40:41.628: atmsar_atm_lineaction(ATM0): state=0
.Dec 26 16:40:41.628: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to SHUTTING_DOWN.
.Dec 26 16:40:41.628: ATM0: atmsar_1a_teardown_vc,vcinfo = 0x81ABF0C8
.Dec 26 16:40:41.628: atmsar_1a_teardown_vc(ATM0): vc:1 vpi:0 vci:101
.Dec 26 16:40:41.628: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to NOT_IN_SERVICE.
.Dec 26 16:40:41.628: DSL: SM: [DMTDSL_SHOWTIME -> DMTDSL_RE_OPEN]
.Dec 26 16:40:41.628: DSL: Send ADSL_CLOSE command.
.Dec 26 16:40:41.628: DSL(ATM0): Sent command 0x4
.Dec 26 16:40:42.156: DSL: Received response: 0x25
.Dec 26 16:40:42.156: DSL: Connection closed
.Dec 26 16:40:42.156: DSL: SM: [DMTDSL_RE_OPEN -> DMTDSL_DO_OPEN]
.Dec 26 16:40:42.156: DSL: Send ADSL_OPEN command.
.Dec 26 16:40:42.156: DSL(ATM0): Using subfunction 0x0
.Dec 26 16:40:42.156: LOCAL:Max noise margin for power cutoff 31
.Dec 26 16:40:42.156: DSL(ATM0): Sent command 0x3
.Dec 26 16:40:42.368: ATM0: atmsar_vc_dlcx
.Dec 26 16:40:43.628: %LINK-3-UPDOWN: Interface ATM0, changed state to down
.Dec 26 16:40:43.628: atmsar_atm_lineaction(ATM0): state=0
.Dec 26 16:40:44.628: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
.Dec 26 16:40:44.656: DSL(ATM0): 1: Modem state = 0x9
.Dec 26 16:40:47.156: DSL(ATM0): 2: Modem state = 0x10
.Dec 26 16:40:49.656: DSL(ATM0): 3: Modem state = 0x10
.Dec 26 16:40:52.156: DSL(ATM0): 4: Modem state = 0x10
.Dec 26 16:40:54.224: DSL: Received response: 0x24
.Dec 26 16:40:54.224: DSL: Showtime!
.Dec 26 16:40:54.224: DSL(ATM0): Sent command 0x11
.Dec 26 16:40:54.228: DSL: Received response: 0x61
.Dec 26 16:40:54.228: DSL: Read firmware revision 0x0000
.Dec 26 16:40:54.328: DSL(ATM0): Sent command 0x31
.Dec 26 16:40:54.328: DSL: Received response: 0x12
.Dec 26 16:40:54.328: DSL(ATM0): operation mode 0x0002
.Dec 26 16:40:54.428: DSL(ATM0): Sent command 0x33
.Dec 26 16:40:54.428: DSL: Received response: 0x16
.Dec 26 16:40:54.428: DSL(ATM0): Far End ITU Country Code 0xB5
.Dec 26 16:40:54.428: DSL: Far End ITU Vendor ID BDCM
.Dec 26 16:40:54.428: DSL: Far End ITU Vendor ID Specific 0x918F
.Dec 26 16:40:54.428: DSL: Far End ITU Vendor STD Number 0x0002
.Dec 26 16:40:54.528: DSL(ATM0): Sent command 0x32
.Dec 26 16:40:54.528: DSL: Received response: 0x14
.Dec 26 16:40:54.528: DSL(ATM0): Near End ITU Country Code 0x00
.Dec 26 16:40:54.528: DSL: Near End ITU Vendor ID ALCB
.Dec 26 16:40:54.528: DSL: Near End ITU Vendor ID Specific 0x0000
.Dec 26 16:40:54.528: DSL: Near End ITU Vendor STD Number 0x0002
.Dec 26 16:40:54.528: ATM0 atmsar_update_us_bandwidth(): upstream bw =928 Kbps
.Dec 26 16:40:54.528: DSL: SM: [DMTDSL_DO_OPEN -> DMTDSL_SHOWTIME]no debug all
All possible debugging has been turned off
Cisco#
.Dec 26 16:41:02.368: ATM0: atmsar_vc_dlcx
.Dec 26 16:41:02.368: (ATM0)1a_enable: delay activation of vcd=1, vc=0x81ABF0C8
.Dec 26 16:41:02.368: atmsar enable ATM0

.Dec 26 16:41:02.368: ATM0: atmsar_bringup_interface: Interface and atm_db flags are UP
.Dec 26 16:41:04.368: %LINK-3-UPDOWN: Interface ATM0, changed state to up
.Dec 26 16:41:05.368: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
.Dec 26 16:41:07.720: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
Cisco#no debug all
All possible debugging has been turned off
Cisco#

unsure on pulling this apart tho

 

[tjbradford]

interestingly i have updated my ios Cisco IOS Software, C850 Software (C850-ADVSECURITYK9-M), Version 12.4(15)T11, RELEASE SOFTWARE (fc2)


seems to have worked so far !

*Dec 26 18:45:40.535: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
*Dec 26 18:45:46.020: %ATM-6-PVC_STATE_CHANGE: ATM(ATM0.1): PVC(VCD=1, VPI=0, VCI=101) state changed to UP.
*Dec 26 18:47:52.625: %SYS-5-CONFIG_I: Configured from console by console

time that this log was taken is 21:40 so far so good !

i forced the dsl operating mode to adsl2+ on the atm 0 interface

 

[tjbradford]

i believe my above tweaking has resolved the issues i get one sync at around 430am each day other than that there is no resync's for the rest of the day !

please try this out anyone with resync issues and let me know how you get on i would be very intrested to hear

thanks