18 messages in net.nether.puck.cisco-nsp[c-nsp] 12.2(25)S on NPEG1
FromSent OnAttachments
Mark Pace BalzanJan 23, 2005 8:20 am 
Jared MauchJan 23, 2005 9:13 am 
nishal goburdhanJan 25, 2005 7:39 am 
Marcus StoegbauerJan 25, 2005 9:23 am 
Santiago Felipe PerezJan 28, 2005 5:41 am 
David J. HughesJan 31, 2005 6:08 pm 
james edwardsJan 31, 2005 6:26 pm 
Clayton KossmeyerJan 31, 2005 7:20 pm 
David J. HughesJan 31, 2005 7:25 pm 
james edwardsJan 31, 2005 7:31 pm 
Clayton KossmeyerJan 31, 2005 7:33 pm 
nishal goburdhanFeb 2, 2005 11:48 am 
james edwardsFeb 3, 2005 5:35 pm 
Denis V. SchapovJul 4, 2005 1:00 am 
nishal goburdhanJul 14, 2005 6:42 am 
nishal goburdhanAug 12, 2005 6:21 pm 
Andris ZarinsAug 14, 2005 9:48 am 
nishal goburdhanAug 14, 2005 4:48 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] 12.2(25)S on NPEG1Actions...
From:nishal goburdhan (nis@is.co.za)
Date:Jul 14, 2005 6:42:06 am
List:net.nether.puck.cisco-nsp

On Mon, Jul 04, 2005 at 02:00:51PM +0900, Denis V. Schapov wrote:

Hi.

Could someone point me on DDTS id for this issue ? I mean CEF/fast-swiching flapping with

'no ip route-cache' 'no ip route-cache cef'

after some configuration changes on interfaces.

We have the same problem on 7204VXR/NPE300 running 12.2(25)S4.

Denis.

heh. aside from the usual - "code upgrade" path; i can confirm that we still see
this problem with 12.2(25)S4 - haven't tested S5 yet, we haven't had much luck
in getting this one resolved.

i imagine that one of the problems is that the symptoms (for us anyway) are not
always consistent. yes, the router *logs* that it's disabled interface and global cef...but often
it would leave cef dependent features, like urpf, still applied (which you would
expect it to remove from all interfaces if the router stopped cef switching). other times it's just interface cef, and sometimes, it's just netflow that gives
us inconsistent results; in all cases, an interface refresh:

'ip route-cache cef' 'ip flow ingress'

resolves the (interface) problem.

one of our staff managed to isolate the 'event' to removal of a channel-group,
that still had urpf enabled. this would successfully re-create the event, but
since we've had this happen often out of working hours, it's unclear that this
is the sole contributor.

iirc, we were advised to try 12.2(26.9)S but haven't opted for that route...

--n.