Re: HiHave you solved this ?We

kamaradialbertog · ‎07-30-2011

I own a Cisco 887 and every 3-4 days but abolutely random internet goes down. I can't understand if it is a WAN or internal router problem. Sometimes the problem solves on its own, sometimes a reload is needed.

I can post you the following logs:

000038: Jul 27 09:35:06.911 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

000039: Jul 27 09:35:07.963 PCTime: %LINK-3-UPDOWN: Interface ATM0, changed state to down

000040: Jul 27 09:35:08.963 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down

000041: Jul 27 09:35:49.315 PCTime: %LINK-3-UPDOWN: Interface ATM0, changed state to up

000042: Jul 27 09:35:50.315 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up

000043: Jul 27 09:35:56.303 PCTime: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up

000044: Jul 27 09:35:56.303 PCTime: %DIALER-6-BIND: Interface Vi2 bound to profile Di0

000045: Jul 27 09:36:02.071 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up

000046: Jul 29 04:16:44.604 PCTime: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

000047: Jul 29 04:16:44.604 PCTime: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di0

000048: Jul 29 04:16:44.612 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

000049: Jul 29 04:16:45.628 PCTime: %LINK-3-UPDOWN: Interface ATM0, changed state to down

000050: Jul 29 04:16:46.628 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down

000051: Jul 29 04:17:28.436 PCTime: %LINK-3-UPDOWN: Interface ATM0, changed state to up

000052: Jul 29 04:17:29.436 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up

000053: Jul 29 04:17:33.956 PCTime: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up

000054: Jul 29 04:17:33.956 PCTime: %DIALER-6-BIND: Interface Vi2 bound to profile Di0

000055: Jul 29 04:17:39.416 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up

000056: Jul 29 13:49:16.818 PCTime: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

000057: Jul 29 13:49:16.818 PCTime: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di0

000058: Jul 29 13:49:16.826 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

000059: Jul 29 13:49:17.898 PCTime: %LINK-3-UPDOWN: Interface ATM0, changed state to down

000060: Jul 29 13:49:18.898 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down

000061: Jul 29 13:49:53.750 PCTime: %LINK-3-UPDOWN: Interface ATM0, changed state to up

000062: Jul 29 13:49:54.750 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up

000063: Jul 29 13:49:59.002 PCTime: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up

000064: Jul 29 13:49:59.002 PCTime: %DIALER-6-BIND: Interface Vi2 bound to profile Di0

000065: Jul 29 13:50:04.710 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up

000066: Jul 30 03:41:05.451 PCTime: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

000067: Jul 30 03:41:05.451 PCTime: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di0

000068: Jul 30 03:41:05.459 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

000069: Jul 30 03:41:06.463 PCTime: %LINK-3-UPDOWN: Interface ATM0, changed state to down

000070: Jul 30 03:41:07.463 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down

000071: Jul 30 03:41:50.383 PCTime: %LINK-3-UPDOWN: Interface ATM0, changed state to up

000072: Jul 30 03:41:51.383 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up

000073: Jul 30 03:41:52.023 PCTime: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up

000074: Jul 30 03:41:52.023 PCTime: %DIALER-6-BIND: Interface Vi2 bound to profile Di0

000075: Jul 30 03:41:57.507 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up

000076: Jul 30 14:47:42.972 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

This last one is the kind of error that sometimes never solves on its own and I have to force a reload as the line never goes back.

The following is my show version:

Cisco IOS Software, C880 Software (C880DATA-UNIVERSALK9-M), Version 15.1(4)M1, RELEASE SOFTWARE (fc1)

Technical Support:

http://www.cisco.com/techsupport

Compiled Wed 15-Jun-11 00:49 by prod_rel_team

ROM: System Bootstrap, Version 12.4(22r)YB5, RELEASE SOFTWARE (fc1)

vvg-rtr-254 uptime is 10 minutes

System returned to ROM by reload at 14:50:24 PCTime Sat Jul 30 2011

System restarted at 14:51:11 PCTime Sat Jul 30 2011

System image file is "flash:c880data-universalk9-mz.151-4.M1.bin"

Last reload type: Normal Reload

Last reload reason: Reload Command

[…]

Cisco 887 (MPC8300) processor (revision 1.0) with 236544K/25600K bytes of memory.

Processor board ID FCZ1411C24F

4 FastEthernet interfaces

1 ISDN Basic Rate interface

1 ATM interface

1 Virtual Private Network (VPN) Module

256K bytes of non-volatile configuration memory.

126000K bytes of ATA CompactFlash (Read/Write)

License Info:

License UDI:

-------------------------------------------------

Device# PID SN

-------------------------------------------------

*0 CISCO887-SEC-K9 xxxxxxxxxxxxxxxx

License Information for 'c880-data'

License Level: advipservices Type: Permanent

Next reboot license Level: advipservices

Configuration register is 0x2102

and this is my configuration:

Current configuration : 7870 bytes

!

! No configuration change since last restart

version 15.1

no service pad

service tcp-keepalives-in

service tcp-keepalives-out

service timestamps debug datetime msec localtime show-timezone

service timestamps log datetime msec localtime show-timezone

service password-encryption

service internal

service sequence-numbers

!

hostname vvg-rtr-254

!

boot-start-marker

boot-end-marker

!

security authentication failure rate 3 log

security passwords min-length 6

logging buffered 40960

logging rate-limit 100 except warnings

no logging console

no logging monitor

!

aaa new-model

!

aaa authentication login local_authen local

aaa authorization exec local_author local

!

aaa session-id common

!

memory-size iomem 10

clock timezone PCTime 1 0

clock summer-time PCTime date Mar 30 2003 2:00 Oct 26 2003 3:00

crypto pki token default removal timeout 0

!

crypto pki trustpoint TP-self-signed-796254749

enrollment selfsigned

subject-name cn=IOS-Self-Signed-Certificate-796254749

revocation-check none

!

crypto pki certificate chain TP-self-signed-796254749

certificate self-signed 01

[…]

quit

no ip source-route

!

ip cef

no ip bootp server

ip domain name kamara.eu

ip name-server 8.8.8.8

ip name-server 8.8.4.4

ip inspect WAAS flush-timeout 10

no ipv6 cef

!

multilink bundle-name authenticated

license udi pid CISCO887-SEC-K9 sn xxxxxxxxxxx

license boot module c880-data level advipservices

license agent notify

http://192.168.103.37:9710/clm/servlet/HttpListenServlet

dummy dummy 2.0

!

username Administrator privilege 15 secret 5 Xxxxxxxxxxxxxxxxxxxxxxxxxx

!

ip tcp synwait-time 10

no ip ftp passive

ip ssh time-out 60

ip ssh authentication-retries 2

!

class-map match-any CCP-Transactional-1

match protocol citrix

match protocol finger

match protocol notes

match protocol novadigm

match protocol pcanywhere

match protocol sap

match protocol secure-telnet

match protocol sqlnet

match protocol sqlserver

match protocol ssh

match protocol telnet

match protocol xwindows

class-map match-any CCP-Voice-1

match protocol rtp audio

class-map match-any CCP-Routing-1

match protocol eigrp

match protocol rip

match protocol rsvp

class-map match-any CCP-Signaling-1

match protocol h323

match protocol rtcp

match protocol sip

class-map match-any CCP-Management-1

match protocol dhcp

match protocol dns

match protocol imap

match protocol kerberos

match protocol ldap

match protocol secure-imap

match protocol secure-ldap

match protocol snmp

match protocol socks

match protocol syslog

!

policy-map CCP-QoS-Policy-1

class CCP-Voice-1

set dscp ef

priority percent 33

class CCP-Signaling-1

set dscp cs3

bandwidth percent 5

class CCP-Routing-1

set dscp cs6

bandwidth percent 5

class CCP-Management-1

set dscp cs2

bandwidth percent 5

class CCP-Transactional-1

set dscp af21

bandwidth percent 5

class class-default

fair-queue

!

crypto isakmp keepalive 1800 periodic

!

crypto ipsec security-association lifetime kilobytes 4096000

!

interface Null0

no ip unreachables

!

interface BRI0

no ip address

no ip redirects

no ip unreachables

no ip proxy-arp

ip flow ingress

encapsulation hdlc

shutdown

isdn termination multidrop

!

interface ATM0

no ip address

no ip redirects

no ip unreachables

no ip proxy-arp

ip flow ingress

no atm ilmi-keepalive

dsl lom 30

dsl noise-margin -1

dsl gain-setting tx-offset 3

dsl gain-setting rx-offset 3

dsl bitswap both

!

interface ATM0.1 point-to-point

no ip redirects

no ip unreachables

no ip proxy-arp

ip flow ingress

pvc 8/35

encapsulation aal5mux ppp dialer

dialer pool-member 1

!

interface FastEthernet0

no ip address

!

interface FastEthernet1

no ip address

!

interface FastEthernet2

no ip address

!

interface FastEthernet3

no ip address

!

interface Vlan1

description $FW_INSIDE$

ip address 192.168.103.254 255.255.255.0

no ip redirects

no ip unreachables

no ip proxy-arp

ip flow ingress

ip nat inside

ip virtual-reassembly in

!

interface Dialer0

description $FW_OUTSIDE$

ip address negotiated

no ip redirects

no ip unreachables

no ip proxy-arp

ip nbar protocol-discovery

ip flow ingress

ip flow egress

ip nat outside

ip virtual-reassembly in

encapsulation ppp

ip tcp header-compression

dialer pool 1

dialer-group 1

ppp authentication chap pap callin

ppp chap hostname xxxxxxxxx

ppp chap password 7 xxxxxxxxxxxx

ppp pap sent-username xxxxxxxxxxxxxxxx password 7 xxxxxxxxxxxxxxxxxxxxx

!

ip forward-protocol nd

ip http server

ip http access-class 1

ip http authentication local

ip http secure-server

!

ip flow-top-talkers

top 25

sort-by bytes

!

ip nat inside source static udp 192.168.103.12 12803 interface Dialer0 12803

ip nat inside source static udp 192.168.103.12 12802 interface Dialer0 12802

ip nat inside source static udp 192.168.103.12 12801 interface Dialer0 12801

ip nat inside source static udp 192.168.103.12 12800 interface Dialer0 12800

ip nat inside source static udp 192.168.103.12 12506 interface Dialer0 12506

ip nat inside source static tcp 192.168.103.37 37200 interface Dialer0 37200

ip nat inside source static tcp 192.168.103.28 28200 interface Dialer0 28200

ip nat inside source static udp 192.168.103.37 37881 interface Dialer0 37881

ip nat inside source static tcp 192.168.103.37 37881 interface Dialer0 37881

ip nat inside source static udp 192.168.103.28 28881 interface Dialer0 28881

ip nat inside source static tcp 192.168.103.28 28881 interface Dialer0 28881

ip nat inside source static udp 192.168.103.37 37672 interface Dialer0 37672

ip nat inside source static tcp 192.168.103.37 37662 interface Dialer0 37662

ip nat inside source list 101 interface Dialer0 overload

ip route 0.0.0.0 0.0.0.0 Dialer0

!

logging trap debugging

access-list 1 remark HTTP Access-class list

access-list 1 remark CCP_ACL Category=1

access-list 1 permit 192.168.103.0 0.0.0.255

access-list 1 deny any

access-list 101 remark ACL libera

access-list 101 remark CCP_ACL Category=1

access-list 101 permit ip any any

dialer-list 1 protocol ip permit

no cdp run

!

control-plane

!

line con 0

login authentication local_authen

transport output telnet

line aux 0

login authentication local_authen

transport output telnet

line vty 0 4

authorization exec local_author

login authentication local_authen

transport input telnet ssh

!

scheduler interval 500

event manager applet ATMFIX

event syslog occurs 3 pattern "No retrain. sleep 20 seconds"

action 1.0 syslog msg "Rebooting to recover from no retrain problem."

action 2.0 reload

!

end

The dsl interface tells:

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' 'GSPN'

Chip Vendor Specific: 0x0000 0x0010

Chip Vendor Country: 0x0F 0xFF

Modem Vendor ID: 'CSCO' ' '

Modem Vendor Specific: 0x0000 0x0000

Modem Vendor Country: 0xB5 0x00

Serial Number Near: FCZ1411C24 887-SEC- 15.1

Serial Number Far: Chip ID: C196 (3) capability-enabled

DFE BOM: DFE3.0 Annex A (1)

Capacity Used: 100% 92%

Noise Margin: 6.0 dB 9.0 dB

Output Power: 20.0 dBm 12.5 dBm

Attenuation: 37.0 dB 15.0 dB

FEC ES Errors: 18 2443

ES Errors: 1 245

SES Errors: 0 1

LOSES Errors: 0 1

UES Errors: 107 0

Defect Status: None None

Last Fail Code: None

Watchdog Counter: 0x6B

Watchdog Resets: 0

Selftest Result: 0x00

Subfunction: 0x00

Interrupts: 11748 (0 spurious)

PHY Access Err: 0

Activations: 1

LED Status: ON

LED On Time: 100

LED Off Time: 100

Init FW: init_AMR_5.0.005.bin

Operation FW: AMR-E-5.0.005.bin

FW Source: external

FW Version: 5.0.5

DS Channel1 DS Channel0 US Channel1 US Channel0

Speed (kbps): 0 14086 0 1053

DS User cells: 0 171531586

US User & Idle cells: 0 21868336

Reed-Solomon EC: 0 0 0 190272

CRC Errors: 0 449 0 449

Header Errors: 0 376 0 9920

Total BER: 0E-0 33280E-0

Leakage Average BER: 0E-0 33280E-0

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

Bitswap: enabled enabled

LOM Monitoring : Enabled

LOM watch configured for 30 times

LOM appeared continuously for 0 times

DMT Bits Per Bin

Not able to get complete DMT bin information.Retry "show dsl" after few seconds.

DSL: Training log buffer capability is not enabled

This router is 30km from my home and it's very unconfortable have to go there to manually reboot the device when it's not correctly operating with the dsl line!

I need an advice from you, thanks

johnlloyd_13 · ‎07-30-2011

Hi,

Your DSL line has a high attenuation and errors on it. Need to rectify this with your SP.

Sent from Cisco Technical Support iPhone App

kamaradialbertog · ‎07-30-2011

If so, why does not LOM report it and why doesn't the router retrain the line, thus hanging in a no way out state?

johnlloyd_13 · ‎07-30-2011

Hi,

I haven't used the LOM feature, so hopefully someone here in this forum can further advise. But based from personal experience, I've seen attenuation goes high as 40+ dB and SP field tech was able to improve it to as low as 1.0 dB and rarely got any disconnections afterwards.

Sent from Cisco Technical Support iPhone App

kamaradialbertog · ‎07-31-2011

I appreciate your good will but I think my problems need some more investigating from a more expert guy

The line attenuation is exactly what I can expect from the line distance from the ISP.

jimw25 · ‎08-01-2011

Hello

I have installed two Cisco 887 routers recently and BOTH have the same sort of problem as yours... will work fine for a while and then just drop repeatedly, sometimes coming back up on their own, other times needing to be rebooted or cable pulled or sometimes just issuing a 'shut' then 'no shut' on the ATM0 interface....

The Virtual Access interface is the part that comes up once PPP has done it's negotiation and the router is happy. I have seen authentication failures to cause Virtual Access interface to be in an 'up' 'down' state. Anyway, if the ATM interface which is the physical interface goes down, it will pull the Virtual Access interface down with it

000039: Jul 27 09:35:07.963 PCTime: %LINK-3-UPDOWN: Interface ATM0, changed state to down

000040: Jul 27 09:35:08.963 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down

If the ATM interface is going down, this normally indicates a layer 1 issue

Try 'debug atm events' command whilst the interface is down, if it returns a 'modem state' of 0x8 this means it could not establish a connection and has not heard back from the CO. Basically it does not see an incoming signal from the exchange kit. This indicates an ISP issue, although getting them to admit there is one whilst the line is actually up is a whole different story! (make sure you have changed all your filters and made sure there is no internal wiring connected to the master socket or they may charge blah blah blah...!)

When the interface comes back online the debug output will show 'modem state=0x10' followed by "showtime!" as it connects successfully!

Please let me know if you have any luck with this problem. I have spoken with my ISP (same one for both routers) who, funnily enough, cannot find a problem. I have also tried updating the firmware on the Alcatel modem inside the router which didn't help and have also asked my suppliers tech support if they know of any outstanding bugs or issues with these routers and they say there are none!

Many thanks

Jim Westhead CCNP

kamaradialbertog · ‎08-02-2011

Your analysis has been more than exhaustive and clear, thank you!

If the problem is on every 887 out there, some Cisco guy should come here and tell us the truth.

Could you please post here your versions, config and ATM status? I'd be glad to see if there are some similarities or differences from mine.

I have problems with virutal interface, not with ATM. Is the number of every Virtual Interface associated to something of particular?

P.S: I have tried the "debug ATM events" command and the output is a simple "ATM events debugging is on". How could I see the output?

kamaradialbertog · ‎08-06-2011

I have done some more investigation. I have put the debug on and played with clear various interfaces while the 887 was not connecting, i.e. hang status. Here is the log:

000058: Aug 6 14:50:33.182 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

000059: Aug 6 14:53:52.070 GMT: DSL(ATM0): Sent extended command 0xC

000060: Aug 6 14:53:52.070 GMT: DSL(ATM0): ext response 0xF received, data size 49

000061: Aug 6 14:53:52.070 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000062: Aug 6 14:53:52.070 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

[…]

000439: Aug 6 14:57:47.074 GMT: DSL(ATM0): Sent extended command 0xC

000440: Aug 6 14:57:47.074 GMT: DSL(ATM0): ext response 0xF received, data size 49

000441: Aug 6 14:57:47.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000442: Aug 6 14:57:47.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000443: Aug 6 14:57:47.246 GMT: ATM0: atmsar_1a_reset

000444: Aug 6 14:57:47.246 GMT: ATM0: atmsar_get_plim_info

000445: Aug 6 14:57:47.246 GMT: ATM0:atmsar_update_plimtype

000446: Aug 6 14:57:47.246 GMT: ATM0 atmsar_1a_reset: PLIM type is 18, Rate is 1023Mbps

000447: Aug 6 14:57:47.246 GMT: ATM0 atmsar_1a_shutdown: state=4

000448: Aug 6 14:57:47.246 GMT: ATM0: atmsar_shutdown, newstate = 0

000449: Aug 6 14:57:47.246 GMT: Resetting ATM0

000450: Aug 6 14:57:47.246 GMT: atmsar_1a_teardown_vc(ATM0): vc:1 vpi:8 vci:35

000451: Aug 6 14:57:47.246 GMT: Fill up paramaters for PVC 8/35[1] - Request for CoS 0 PCR 1023 SCR 0 MCR 0 Available 1023

000452: Aug 6 14:57:47.246 GMT: ATM0.1 VC 8/35 Current Total Active VC Count 0

000453: Aug 6 14:57:47.246 GMT: ATM(): IP multicast cache invalidated for ATM0.1

000454: Aug 6 14:57:47.246 GMT: ATM: PVC removed, ATM0.1 VCD 1 (8/35)

000455: Aug 6 14:57:47.250 GMT: atmsar_1a_config(ATM0)

000456: Aug 6 14:57:47.250 GMT: atmsar_1a_enable(ATM0)

000457: Aug 6 14:57:47.250 GMT: ATM0: atmsar_init

000458: Aug 6 14:57:47.250 GMT: ATM0 atmsar_update_us_bandwidth(): upstream bw =1023 Kbps

000459: Aug 6 14:57:48.218 GMT: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

000460: Aug 6 14:57:48.218 GMT: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di0

000461: Aug 6 14:57:49.246 GMT: %LINK-3-UPDOWN: Interface ATM0, changed state to down

000462: Aug 6 14:57:49.246 GMT: atmsar_atm_lineaction(ATM0): state=0

000463: Aug 6 14:57:49.442 GMT: ATM0: atmsar_vc_dlcx

000464: Aug 6 14:57:49.442 GMT: (ATM0)1a_enable: delay activation of vcd=1, vc=0x87F2AD6C

000465: Aug 6 14:57:49.442 GMT: atmsar enable ATM0

000466: Aug 6 14:57:49.442 GMT: ATM0: atmsar_bringup_interface: Interface and atm_db flags are UP

000467: Aug 6 14:57:49.574 GMT: DSL(ATM0): Sent extended command 0xC

000468: Aug 6 14:57:49.574 GMT: DSL(ATM0): ext response 0xF received, data size 49

000469: Aug 6 14:57:49.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000470: Aug 6 14:57:49.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000471: Aug 6 14:57:51.442 GMT: %LINK-3-UPDOWN: Interface ATM0, changed state to up

000472: Aug 6 14:57:51.442 GMT: atmsar_atm_lineaction(ATM0): state=4

000473: Aug 6 14:57:51.442 GMT: ATM: Repapulate, ATM0

000474: Aug 6 14:57:51.442 GMT: ATM: Repapulate, ATM0.1

000475: Aug 6 14:57:51.442 GMT: ATM: PVC activated, ATM0.1 VCD 1 (8/35)

000476: Aug 6 14:57:52.074 GMT: DSL(ATM0): Sent extended command 0xC

000477: Aug 6 14:57:52.074 GMT: DSL(ATM0): ext response 0xF received, data size 49

000478: Aug 6 14:57:52.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000479: Aug 6 14:57:52.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000480: Aug 6 14:57:54.574 GMT: DSL(ATM0): Sent extended command 0xC

000481: Aug 6 14:57:54.574 GMT: DSL(ATM0): ext response 0xF received, data size 49

000482: Aug 6 14:57:54.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000483: Aug 6 14:57:54.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000484: Aug 6 14:57:57.074 GMT: DSL(ATM0): Sent extended command 0xC

000485: Aug 6 14:57:57.074 GMT: DSL(ATM0): ext response 0xF received, data size 49

000486: Aug 6 14:57:57.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000487: Aug 6 14:57:57.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000488: Aug 6 14:57:58.854 GMT: (ATM0): VPI/VCI: 8/35, peak 1023, Avg 0, mbs 0

000489: Aug 6 14:57:58.854 GMT: Reserved bw for 8/35 Available bw = 1023

000490: Aug 6 14:57:58.854 GMT: ATM0: atmsar_1a_setup_vc, atm_vc_handle = 0x87F2AD6C

000491: Aug 6 14:57:58.854 GMT: ATM0 atmsar_vc_setup: vcd 1

000492: Aug 6 14:57:58.854 GMT: Fill up paramaters for PVC 8/35[1] - Request for CoS 0 PCR 1023 SCR 0 MCR 0 Available 1023

000493: Aug 6 14:57:58.854 GMT: Scheduler parameters for 8/35. Type UBR. PCR 1023

000494: Aug 6 14:57:58.854 GMT: Total scheduled bandwidth after configuringPVC 8/35 will be 0

000495: Aug 6 14:57:58.854 GMT: atmsar_setup_cos(ATM0): vc:1 wred_name: max_q:40

000496: Aug 6 14:57:58.854 GMT: ATM0: VC setup successful (vcd = 1)

000497: Aug 6 14:57:58.854 GMT: ATM0.1 Current Active VC count 1

000498: Aug 6 14:57:58.854 GMT: ATM: PVC activated, ATM0.1 VCD 1 (8/35)

000499: Aug 6 14:57:59.574 GMT: DSL(ATM0): Sent extended command 0xC

000500: Aug 6 14:57:59.574 GMT: DSL(ATM0): ext response 0xF received, data size 49

000501: Aug 6 14:57:59.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000502: Aug 6 14:57:59.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000503: Aug 6 14:57:59.778 GMT: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up

000504: Aug 6 14:57:59.778 GMT: %DIALER-6-BIND: Interface Vi2 bound to profile Di0

000505: Aug 6 14:58:02.074 GMT: DSL(ATM0): Sent extended command 0xC

000506: Aug 6 14:58:02.074 GMT: DSL(ATM0): ext response 0xF received, data size 49

000507: Aug 6 14:58:02.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000508: Aug 6 14:58:02.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000509: Aug 6 14:58:03.270 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up

000510: Aug 6 14:58:03.270 GMT: ATM: Repapulate, Virtual-Access2

000511: Aug 6 14:58:03.354 GMT: ATM: Repapulate, Dialer0

000512: Aug 6 14:58:04.574 GMT: DSL(ATM0): Sent extended command 0xC

000513: Aug 6 14:58:04.574 GMT: DSL(ATM0): ext response 0xF received, data size 49

000514: Aug 6 14:58:04.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000515: Aug 6 14:58:04.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000516: Aug 6 14:58:06.278 GMT: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

000517: Aug 6 14:58:06.278 GMT: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di0

000518: Aug 6 14:58:06.286 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

000519: Aug 6 14:58:07.074 GMT: DSL(ATM0): Sent extended command 0xC

000520: Aug 6 14:58:07.074 GMT: DSL(ATM0): ext response 0xF received, data size 49

000521: Aug 6 14:58:07.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000522: Aug 6 14:58:07.074 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000523: Aug 6 14:58:07.246 GMT: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up

000524: Aug 6 14:58:07.246 GMT: %DIALER-6-BIND: Interface Vi2 bound to profile Di0

000525: Aug 6 14:58:09.574 GMT: DSL(ATM0): Sent extended command 0xC

000526: Aug 6 14:58:09.574 GMT: DSL(ATM0): ext response 0xF received, data size 49

000527: Aug 6 14:58:09.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000528: Aug 6 14:58:09.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

[…]

000549: Aug 6 14:58:24.574 GMT: DSL(ATM0): Sent extended command 0xC

000550: Aug 6 14:58:24.574 GMT: DSL(ATM0): ext response 0xF received, data size 49

000551: Aug 6 14:58:24.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

000552: Aug 6 14:58:24.574 GMT: DSL(ATM0): ADSL_GET_MANAGEMENT_COUNTERS_EXT - data length = 49

As you can see the error code is different from your. Can you please help me to understand?

Thank you!

Neil Haswell · ‎09-19-2012

Does anyone know if this issue ever got sorted.

I have exactly the same problem.

I have searched various forums and not come up with anything conclusive. ?

edsge teenstra · ‎02-16-2015

Hi

Have you solved this ?

We really appreaciate if you have more information , it looks our customer has the same kind of issues.

We got many routers returned that work well with other xDSL networks with the same firmware and IOS. So we think it has to be the quality of the ISP line from the DSLAM.

How far is your router from the DSLAM ?

And i see here : http://www.speedguide.net/faq/what-is-considered-good-dsl-line-attenuation-371

When i believe that link above your attenuation is quite high ..

Capacity Used: 100% 92%

Noise Margin: 6.0 dB 9.0 dB

Output Power: 20.0 dBm 12.5 dBm

Attenuation: 37.0 dB 15.0 dB

FEC ES Errors: 18 2443

ES Errors: 1 245

SES Errors: 0 1

LOSES Errors: 0 1

UES Errors: 107 0

Any feedback would help this Cisco community !

Regards

Edsge

NetzKing · ‎05-28-2018

Ask your ISP to clear mac address and try once.