[c-nsp] CEF inconsistency with 12.2(25)S1

[F. David Sinn]

CEF consistency-check is only meaningful on systems with distributed 
forwarding abilities (7500's, 12000's) as it is used to confirm that 
the CEF table on the line-card is consistent with the CEF table on the 
RP.

The problem you are describing is with the v6 routing processes feeding 
into CEF, or how CEF is dealing with that data.  Sounds like a bug to 
me.

David


On Nov 1, 2004, at 3:39 AM, Bernhard Schmidt wrote:

> Hi,
>
> since I upgraded two of my backbone routers to 12.2(25)S I periodically
> had some issues with updates in the routing table not being reflected 
> in
> CEF. Update to 12.2(25)S1 did not solve the problem.
>
> Recent example:
>
> BACK1-C7206-OTN-SATIP#sh ipv6 route 2001:7fd::/32
> IPv6 Routing Table - 577 entries
> [...]
> B   2001:7FD::/32 [20/20]
>      via FE80::426E:E, Tunnel301
>
> BACK1-C7206-OTN-SATIP#sh ipv6 cef 2001:7fd::/32
> 2001:7FD::/32
>   nexthop FE80::20C:86FF:FE9A:3819 GigabitEthernet0/3
>
> Same thing on the box connected at Gi0/3 -> I have a nice loop here.
>
> "no ipv6 cef; ipv6 cef" fixes the problem, but since only a few 
> prefixes
> are broken at a time you have to notice the problem first.
>
> Any ideas? I have
>
> cef table consistency-check IPv6
> cef table consistency-check IPv6 data-checking
> cef table consistency-check IPv6 error-message
>
> but "show cef table consistency-check" doesn't show any errors.
>
> Bernhard
> _______________________________________________
> 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/
>