cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1574
Views
0
Helpful
4
Replies

ATM interface on Cisco 887 flaps intermittently at random times during the day

arun.ratnaraj
Level 1
Level 1

Hi Guys,

 

I've got an issue with a Cisco 887 where the ADSL link flaps intermittently every day few times randomly. We have already swapped out the Cisco 887 with a new one.

 

We have also got the carrier to come onsite and check and make some adjustments to the line.

 

Here are the stats before the line tech came onsite:

Also, before the tech came onsite I observed >600 CRC errors in 20mins using the command (show controllers vDSL 0). After the line tech checked the line I only observed ~500 CRC errors in over 24hrs. Attenuation also improved but the noise margin didn't improve that much.



***Attached is also the "show interfaces" output.

 

rtr#show controllers vDSL 0

Line Attenuation: 45.0 dB 31.5 dB
Signal Attenuation: 45.0 dB 0.0 dB
Noise Margin: 9.1 dB 11.0 dB

CRC Errors: 0 2248 0 0
Header Errors: 0 4220 0 23

 

Please check the config and the ADSL stats from the Cisco 887.

 

The stats below are taken after the work carried out by the line tech.

 

CONFIGURATION:

!
interface ATM0
description WAN-Ipera-SID-<ID>
bandwidth 384
no ip address
load-interval 30
no atm ilmi-keepalive
pvc 8/35 
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
!

!
interface Dialer1
description WAN-###
ip address negotiated
ip nbar protocol-discovery
ip virtual-reassembly in
encapsulation ppp
dialer pool 1
dialer idle-timeout 0
dialer persistent
dialer-group 1
ppp chap hostname #################
ppp chap password 7 #################
!

 

***********************************************************************#show controllers vdsl 0

 

rtr#show controllers vdsl 0
Controller VDSL 0 is UP

Daemon Status: Up

XTU-R (DS) XTU-C (US)
Chip Vendor ID: 'BDCM' 'BDCM'
Chip Vendor Specific: 0x0000 0x939F
Chip Vendor Country: 0xB500 0xB500
Modem Vendor ID: 'CSCO' ' '
Modem Vendor Specific: 0x4602 0x0000
Modem Vendor Country: 0xB500 0x0000
Serial Number Near: FGL174422AT 887VA-M- 15.1(4)M 
Serial Number Far: 
Modem Version Near: 15.1(4)M
Modem Version Far: 0x939f

Modem Status: TC Sync (Showtime!) 
DSL Config Mode: AUTO 
Trained Mode: G.992.1 (ADSL) Annex A 
TC Mode: ATM 
Selftest Result: 0x00 
DELT configuration: disabled 
DELT state: not running 
Trellis: ON ON
Line Attenuation: 37.0 dB 23.0 dB
Signal Attenuation: 37.0 dB 0.0 dB
Noise Margin: 10.4 dB 11.0 dB
Attainable Rate: 9720 kbits/s 1252 kbits/s
Actual Power: 19.9 dBm 12.3 dBm
Total FECS: 50480 0
Total ES: 15 0
Total SES: 0 0
Total LOSS: 0 0
Total UAS: 0 0
Total LPRS: 0 0
Total LOFS: 0 0
Total LOLS: 0 0
Bit swap: 0 0

Full inits: 112
Failed full inits: 0
Short inits: 0
Failed short inits: 0

Firmware Source File Name (version)
-------- ------ -------------------
VDSL embedded VDSL_LINUX_DEV_01212008 (1)

Modem FW Version: 110506_1916-4.02L.03.A2pv6C032b.d23i
Modem PHY Version: A2pv6C032b.d23i


DS Channel1 DS Channel0 US Channel1 US Channel0
Speed (kbps): 0 8096 0 1024
Previous Speed: 0 8096 0 1024
Total Cells: 0 101120461 0 0
User Cells: 0 6863 0 0
Reed-Solomon EC: 0 50480 0 0
CRC Errors: 0 59 0 0
Header Errors: 0 275 0 1
Interleave (ms): 0.00 8.00 0.00 4.00
Actual INP: 0.00 1.16 0.00 0.66

Training Log : Stopped
Training Log Filename : flash:vdsllog.bin

 

 

***********************************************************************#show controllers vdsl 0 datapath

 

rtr#show controllers vdsl 0 datapath 
Controller VDSL 0 is UP

***********************************************
* Data Path Counters on Host-Modem interface *
***********************************************

Modem Switch Statistics: GMII2 Port CPU Port
Number of octets Tx: 311735391 311224223
Number of octets Rx: 311224223 311735519
Number of unicast packets Tx: 1680453 1695413
Number of unicast packets Rx: 1695195 1680236
Number of broadcast packets Tx: 0 0
Number of broadcast packets Rx: 0 0
Number of multicast packets Tx: 0 0
Number of multicast packets Rx: 0 0
Number of Rx FCS Errors: 0 0
Number of Rx Alignment Errors: 0 0
Number of Tx pause frames: 0 0
Number of Rx pause frames: 0 0
Number of single collision frames: 0 0
Number of multiple collision frames: 0 0
Number of dropped packets Tx: 0 0
Number of dropped packets Rx: 0 0
Number of framein discards Tx: 0 0
Number of excess frame discards Rx: 0 0


************************************************
* Data Path Counters on Modem-DSLAM interface *
************************************************

ptm0 Link encap:Ethernet HWaddr 02:10:18:01:00:02 
UP BROADCAST RUNNING MULTICAST MTU:1600 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

atm/ptm interface statistics for port 0
in octets 2756
out octets 5989
in packets 28
out packets 32
in OAM cells 0
out OAM cells 0
in ASM cells 0
out ASM cells 0
in packet errors 0
in cell errors 0

 

***********************************************
* Data Path XCONN Stats *
***********************************************

BCM Ethernet Statistics: To XTM To Other
Number of Packets: 1695416 2

BCM XTM Statistics:
PVC RxAAL5FromEth RxRawFromEth TxAAL5ToEth TxRawToEth TxToOthers
8/35 4247 0 4109 0 0


***********************************************
* PTM Path congestion Stats *
***********************************************

Set Count : 0
Clear Count : 0
Tx congested: N
PTM Congestion State: 0

 

 

***********************************************************************Portion of the log messages

Sep 8 20:58:27.327: %CONTROLLER-5-UPDOWN: Controller VDSL 0, changed state to down
Sep 8 20:58:31.587: %LINK-3-UPDOWN: Interface ATM0, changed state to down
Sep 8 20:58:32.587: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down
Sep 8 20:58:32.791: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep 8 20:58:32.791: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
.Sep 8 20:58:32.795: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
.Sep 8 20:58:51.347: %CONTROLLER-5-UPDOWN: Controller VDSL 0, changed state to up
.Sep 8 20:59:01.632: %LINK-3-UPDOWN: Interface ATM0, changed state to up
.Sep 8 20:59:02.632: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up
.Sep 8 20:59:07.616: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
.Sep 8 20:59:07.616: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
.Sep 8 20:59:07.704: %AAA-3-BADSERVERTYPEERROR: Cannot process authentication server type radius (UNKNOWN)
.Sep 8 20:59:11.912: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
.Sep 8 20:59:20.732: %DTP-5-NONTRUNKPORTON: Port Fa2 has become non-trunk
.Sep 8 20:59:21.228: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet2, changed state to down
.Sep 8 20:59:22.236: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to up
.Sep 8 20:59:22.388: %DTP-5-TRUNKPORTON: Port Fa2 has become dot1q trunk
.Sep 8 20:59:23.236: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet2, changed state to up
.Sep 8 20:59:56.481: %DTP-5-NONTRUNKPORTON: Port Fa2 has become non-trunk
.Sep 8 20:59:56.973: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet2, changed state to down
.Sep 8 20:59:57.981: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to up
.Sep 8 20:59:58.125: %DTP-5-TRUNKPORTON: Port Fa2 has become dot1q trunk
.Sep 8 20:59:58.981: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet2, changed state to up
.Sep 8 21:00:05.937: %DTP-5-NONTRUNKPORTON: Port Fa2 has become non-trunk





Any thoughts on the potential causes for this issue would be appreciated.



Thanks



Arun

 

4 Replies 4

Leo Laohoo
Hall of Fame
Hall of Fame

Post the complete output to the command "sh dsl interface".

Hi Leo,

That command "show dsl interface" does not work on the Cisco 887.

Regards

That command "show dsl interface" does not work on the Cisco 887.

Uh, what?   Is the DSL line connected straight to the 887 DSL port or is there a modem there?

Hi Leo,

This is at a remote site. I haven't been there myself. I believe the carrier ADSL service terminates on an ATA onsite at the premise which then connects to the Cisco 887's ATM0 interface.

Regards