[c-nsp] Anybody else hit by 7600 RIP bug (CSCsi66768)

[Rubens Kuhl Jr.]

On 5/23/07, Rodney Dunn <rodunn at cisco.com> wrote:
> The title of that bug is:
>
> CSCsi66768 odr route can not be redistributed into ospf
>
>
> On Wed, May 23, 2007 at 02:04:47AM -0300, Rubens Kuhl Jr. wrote:
> > We have been suffering a RIP bug on C7600, IOS 12.3(33)SRB, that
> > causes ugly tracebacks, with no public description yet;
>
> The TAC engineer is entitled and it's part of their job to fix that
> if they find a bug like that. The one exception is if there are
> security/PSIRT implications and then they can't say anything as it's
> under the control of PSIRT.

>  the lack of a
> > public description on the most likely bug is making our assigned TAC
> > engineer not tell us what this is about, so we can't think whether it
> > applies to us or not, or design an workaround.
>
> The reason you can't see the bug is because it was found in our testing
> organization on pre-released code and was marked as Unreproducible
>
>
>
> Symptom:
>
> A traceback is seen in the log and ODR redistribution is affected:
>
> %IPRT-3-NDB_STATE_ERROR: NDB state error (BAD EVENT STATE) (0x0) 10.0.0.0/24, state 7, event 2->1,
> nh_type 1 flags 4 -Process= "CDP Protocol", ipl= 0, pid= 256
> -Traceback= 40675A28 40675F6C 40D45D88 40D46B98 40D4854C 40D48690 40D43B24 40D44F68 40ACC158
> 42E34B34 40ACBA84 40ACBB0C 404D2074 404CCB08 404CC05C 41674FA0

In our case the traceback occurs in the RIP process, and it's not
redistributing the routes to any other router process.

> Conditions:
>
> The problem is seen on a 7600 router running 12.2.33SRB.
>
> Workaround:
>
> none
>
>
> Is that the symptom you are seeing?
>
> If so, tell the TAC engineer to reopen the bug, make it viewable on CCO,
> and attach your SR to the bug so DE can investigate it again.

The SR has been attached to the bug now, but I don't think it's really
the case, as changing the RIP timers made the problem disappear. The
curious thing is the same configuration with the same version on the
same hardware doesn't generate tracebacks on the other router.


Rubens