Just for the sake of clarity: "cache" in this context doesn't refer to a
faster-than-usual memory. The route cache is in the exact same RAM as the
routing table. For more details, see the documents Marko mentioned.
Thanks,
Zsombor
Steven Aiello wrote:
>
> Another question,
>
> in CEF is the
Steve,
There are a few reasons why a lookup through the CEF table is
faster than a lookup in the IP routing table.
A lookup in the IP routing table is done top down until a match
is found, much like how an access-list is processed. The problem,
however, is that the IP table is no
> in CEF is the whole routing table held in a cache? If so what is the
> diffrence between this and the routing table held in RAM? Is the cache
> faster than the regular RAM in the router?
There are few excellent documents about this on our favourite website.
Watch for wrap.
[Cisco I
Couple of items:
CEF is a very low overhead process and, in terms of
CPU and memory, you should be fine. I am not as
certain that your intentions to use the MAC address of
the router as a filter point will work. Typically you
use an IP extended ACL for CAR. Also review how
routers filter outbound
Are you talking about the one by Albritton? If so, then I second that! It
is very good.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Javier Contreras
> Sent: Tuesday, September 12, 2000 10:59 AM
> To: [EMAIL PROTECTED]
>
Hi!
I would really recommend you get the Inside Cisco IOS architecture book,
it
gives a lot of information on the different switching modes of cisco...
In resume, CEF builds the "switching table" in configuration time (instead
on
the first packet of a flow, as fast-switching does). To hold the
6 matches
Mail list logo
