[nsp] ATM interface errors

[Clinton Work]

I'm seen a similar problem where a VC will get stuck on the PA-A3. The tell
tale sign was that OutPktDrops would increment for each packet sent down the
VC. Removing and adding back the VC or shutting/no shutting the main
interface would clear the problem. The root cause was traced to a bad PA-A3
port adapter and the problem hasn't happened again since the PA was
replaced.

show atm pvc 110

ATM2/0.110: VCD: 14, VPI: 0, VCI: 110
VBR-NRT, PeakRate: 2081, Average Rate: 2081, Burst Cells: 33
AAL5-LLC/SNAP, etype:0x0, Flags: 0x20, VCmode: 0x0
OAM frequency: 0 second(s), OAM retry frequency: 1 second(s), OAM retry
frequency: 1 second(s)
OAM up retry count: 3, OAM down retry count: 5
OAM Loopback status: OAM Disabled
OAM VC state: Not Managed
ILMI VC state: Not Managed
PA TxRingLimit: 81 particles
PA Rx Limit: 24 particles
InARP frequency: 15 minutes(s)
Transmit priority 2
InPkts: 433231, OutPkts: 59739, InBytes: 60202983, OutBytes: 5620713
InPRoc: 272534, OutPRoc: 11500, Broadcasts: 0
InFast: 160697, OutFast: 50107, InAS: 0, OutAS: 0
InPktDrops: 0, OutPktDrops: 77666/0/77666 (holdq/outputq/total)  <--- 
OutPktDrops incrementing
CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0
 --More--         F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
OAM cell drops: 0
Status: UP


=====================================
Clinton Work                 clinton at scripty.com
Airdrie, AB



----- Original Message ----- 
From: "James Galliford" <JamesG at corp.ptd.net>
To: "Charles Sprickman" <spork at inch.com>; <cisco-nsp at puck.nether.net>
Sent: 21 January, 2004 6:16 AM
Subject: RE: [nsp] ATM interface errors


> We have seen this happen on ATM-OC3 adapters once in a great while.  The
> interfaces looks happy, doesn't show a high amount of errors but it just
> won't pass any traffic.  The only way to bring the PA back into service
> is by resetting the adapter via either a 'clear controller' or
> 'shut/no-shut'.  Unfortunately, it seems that the only way to resolve
> this permanently is to have the adapter replaced.
>