[nsp] CEF problem on 6509 (native)

[David Sinn]

A "clear ip *" should cause the MLS table to be re-built from scratch.

A "clear mls ip destination" or one of the other "clear mls ip" commands
might get rid of the errant entry that you have.  I tried it on a
destination on one of my test boxes and the Index didn't change.  Not
positive if it should.

David

On 11/12/03 11:42 AM, "Sorin CONSTANTINESCU" <adonay at dumnez.eu.org> wrote:

> 
> Hi,
> 
> I found out what the problem is (with some help from the list), but i
> don't know how i can get rid of it.
> 
> The router has a mls cef entry for x.y.z.25 different from x.y.z.0/24,
> when in the routing table i have only entry, for x.y.z.0/24:
> 
> r2#show mls cef x.y.z.0 255.255.255.0
> 
> Index      Prefix           Mask                Adjacency
> 13429      x.y.z.0       255.255.255.0       00d0.0568.980a
> r2#show mls cef x.y.z.25 255.255.255.255
> 
> Index      Prefix           Mask                Adjacency
> 2240       x.y.z.25      255.255.255.255     00a0.d2a4.5003
> r2#
> 
> This client is connected via a cable-modem. The CMTS is Cuda (router, not
> bridge).
> 
> I don't get it from where does this router learn that mls cef entry. The
> layer3 path is
> 
> r2 --> r1 --> CUDA CMTS --> client
> 
> I've even monitored CUDA's traffic for 00a0.d2a4.5003 or x.y.z.25 to see
> what packets come/go when the mls cef entry is renewed, but i haven't seen
> any.
> 
> r2 does not have any interface in the vlan in which the CUDA CMTS is
> connected.
> 
> I really don't know what to do next. If there's anything i forgot to add,
> please drop pe an email.
> 
> Thanks!