[nsp] CEF problem on 6509 (native)

[Iva Cabric]

On Wed, Nov 12, 2003 at 09:42:07PM +0200, Sorin CONSTANTINESCU 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.

Check MAC addresses from Adjacency fields it should give you an idea
where to look. From above, prefix x.y.z.25 goes to some Allied Telesis
equipment is that r1 or something else?

MAC address serach tool is here:

http://www.shmoo.com/tools/mac/