05-25-2010 10:58 AM - edited 03-04-2019 08:35 AM
Hi all,
I am continiously getting error mentioned below: what may be the issue:
%ATM_AIM-5-CELL_ALARM_UP: Interface ATM0/0 lost cell delineation.
%ATM_AIM-5-CELL_ALARM_DOWN: Interface ATM0/0 regained cell delineation.
Interface ATM0/0 is up
Hardware is ATM AIM E1 connected to AIM slot 1
hwidb=0x63F3E0BC, sardb=0x63A415B0
slot 0, unit 0, subunit 0
MXT5100 versions: Framework 0x3380, Utils 0x3380,
AAL5 0x3380, AAL2 0x3380, AAL1 0x3380,
IMA 0x3380, CS 0x3380, Frame 0x3380.
Current (mxt5100_t)sardb:
Ind_Q(0xF7FF8C0), Ind_Q_idx(352), Ind_Q_size(30000)
Cmd_Q(0xF7FAA60), Cmd_Q_idx(51), Cmd_Q_size(20000)
Inpool(0xF7C5080), Inpool_size(4096)
Outpool(0xF7C60C0), Outpool_size(4096)
Localpool(0xF7D0000), Localpool_size(256)
StorBlk(0xF651000), host_blk(0xF64FF00), em_blk(0xF64FFC0)
tx_buf_desc(0xF7F39E0), tx_free_desc_idx (1023)
MXT5100 sub_channel_mode is disabled
MXT5100 number of buffers in Inpool: 1024, Outpool 0
FPGA revision 0x2070007
MXT5100 Port Info:
Port Number (0), Port ID (0xE05)
Interface Number (4), Interface ID (0x10E1)
Port Type CELL, Port Open Status SUCCESS
VCs configured (2)
Port counters: tx_cells 1710604335, rx_cells 1361852530,
rx_hec_errors 319, rx_cell_validation_errors 318
Cell delineation PRESENT
Times cell delineation has been lost 45
MXT5100 Channel Info:
Channel Info (0):
Chan_ID (0x1225), Open Status SUCCESS, VC(1)VPI/VCI(2/108),
Tx Ring packets(used/max 0/40), Tx SBD(used/max 0/40)
Tx PDU(90092), Tx PDU discard(0)
Tx SDU size err(0), Tx cell CLP0(90092), Tx cell CLP1(0)
Rx PDU(0), Rx PDU discard(0), Rx SDU size err(0)
Rx CRC err(0), Rx cell CLP0(0), Rx cell CLP1(0)
Channel Info (1):
Chan_ID (0xFA5), Open Status SUCCESS, VC(2)VPI/VCI(3/108),
Tx Ring packets(used/max 0/40), Tx SBD(used/max 0/40)
Tx PDU(27094662), Tx PDU discard(0)
Tx SDU size err(0), Tx cell CLP0(54548926), Tx cell CLP1(0)
Rx PDU(18792145), Rx PDU discard(0), Rx SDU size err(0)
Rx CRC err(488), Rx cell CLP0(41323241), Rx cell CLP1(0)
when resetted the interface it works fine for some time and occur again... need urgent help...
Regards
Amar
05-26-2010 04:58 AM
Hello Amar,
from what you say, you may be facing a clocking problem
the fact that after resetting for some time it looks like working leads to this possibility.
may you post configuration of ATM interface controller ATM0 (if it exists) in order to understand if clock is received from line, it is internal or it is using the clock of another E1 interface
Hope to help
Giuseppe
06-15-2010 10:59 AM
=======show version==========
cisco 3745 (R7000) processor (revision 2.0) with 247808K/14336K bytes of memory.
Processor board ID FHK0916F23S
R7000 CPU at 350MHz, Implementation 39, Rev 3.3, 256KB L2, 2048KB L3 Cache
Channelized E1, Version 1.0.
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
Primary Rate ISDN software, Version 1.1.
2 FastEthernet/IEEE 802.3 interface(s)
4 ATM network interface(s)
4 Channelized E1/PRI port(s)
1 Virtual Private Network (VPN) Module(s)
1 ATM/Voice AIM(s)
==============================
network-clock-participate wic 0
no network-clock-participate wic 1
network-clock-participate aim 1
network-clock-select 1 E1 0/0
network-clock-select 2 E1 0/1
controller E1 0/0
mode atm aim 1
clock source line primary
interface ATM0/0
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
load-interval 30
scrambling-payload
no atm auto-configuration
no atm ilmi-keepalive
no atm address-registration
!
interface ATM0/0.200 point-to-point
description ***** PVC to LON-LTSB-RTR (via BGPP01) *****
bandwidth 1700
pvc x/x
vbr-rt 1700 1600 200
oam-pvc manage
protocol ppp Virtual-Template10
==============
Regards
Amar
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide