[nsp] ATM interface errors

[Charles Sprickman]

On Wed, 21 Jan 2004, Dennis Peng wrote:

> It's possible the SAR crashed. Did you seen any ATMPA-3-SARCRASH
> errors in the syslog/console?

Nope, all I've got is some CPUHOG messages around the down time:

Jan 21 02:15:24 l3-router-lo-0 3005853: Jan 21 02:15:22.121 EDT:
%LINK-3-UPDOWN: Interface ATM4/0, changed state to down
Jan 21 02:15:24 l3-router-lo-0 3005854: Jan 21 02:15:24.373 EDT: No active
members in BVI2, shutting down
Jan 21 02:15:24 l3-router-lo-0 3005855:
Jan 21 02:15:24 l3-router-lo-0 3005856: Jan 21 02:15:24.385 EDT:
%SYS-3-CPUHOG:
Task ran for 2156 msec (41/14), process = Net Background, PC = 606204CC.
Jan 21 02:15:24 l3-router-lo-0 3005857: -Traceback= 606204D4 605D36D4
Jan 21 02:15:25 l3-router-lo-0 3005858: Jan 21 02:15:24.389 EDT:
%LINEPROTO-5-UPDOWN: Line protocol on Interface ATM4/0, changed state to
down
Jan 21 02:15:29 l3-router-lo-0 3005859: Jan 21 02:15:26.565 EDT:
%LINK-3-UPDOWN: Interface ATM4/0, changed state to up
Jan 21 02:15:32 l3-router-lo-0 3005860: Jan 21 02:15:26.673 EDT:
%LINEPROTO-5-UPDOWN: Line protocol on Interface ATM4/0.1050, changed state
to up

(this continues with some OSPF adjacencies that are over DSL
dropping)

That's about it.  When I do the shut/no shut to bring it back there's
nothing interesting in the logs. This is an older/clunky IOS (still
waiting on my POTS line for OOB access for an upgrade):

Version 12.2(8)T5

Thanks,

Charles

> CSCea32118 allows us to recover automatically if the SAR crashes. Any
> crashes should be reported to TAC so we can identify and fix the
> problem.
>
> Dennis
>
> Charles Sprickman [spork at inch.com] wrote:
> > Hi,
> >
> > Perhaps someone here familiar with DSL agg. on a PA-A3 can help me out
> > here.
> >
> > I have a DS3 ATM backhaul to Covad for DSL.  Last night I saw it drop out
> > from the customer end, so I dialed in and had a look at the atm interface
> > while I was waiting on the Covad NOC to pick up the phone.
> >
> > The interface was showing up/up, but zero input packets, zero CRC errors,
> > zero input errors.  I could see a loop when Covad looped the BPX we're
> > plugged into and vice-versa (DS3 is just a x-conn from our cabinet to
> > theirs), but still no traffic.  Clients with OAM enabled were showing OAM
> > cells out, but none in.
> >
> > Looking more closely at the interface stats, I saw that the "ignored"
> > count was incrementing rapidly.  I bounced my side and everything slowly
> > came back to normal.  What does "ignored" indicate on this interface?  We
> > double-checked we were both set to "cbitplcp" and had cell-scrambling
> > enabled.  According to the NOC, no changes tonight, and all they saw was
> > the circuit bounce up/down at about the time I noticed my line was dead.
> >
> > Any ideas what may have happened?  The circuit was (by my account) running
> > clean.  Covad has no idea of what may have caused this, nor what we can do
> > to make sure it doesn't happen again...
> >
> > Any input appreciated.
> >
> > Thanks,
> >
> > Charles
> >
> > --
> > Charles Sprickman
> > spork at inch.com
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>