12-12-2008 06:53 PM - edited 03-04-2019 12:41 AM
hi every body!
I have few questions about "punt adjacency" .
If we use the command:
switch# show cef not-cef-switched
we get various reasons for a packet that has not been cef -switched or punted to layer 3 engine.Few of reasons are:
no-adj,no-encap,redirect.
I am not cleared about no-adj and no-encap.
A cisco link explains:
(http://www.cisco.com/en/US/tech/tk827/tk831/technologies_tech_note09186a0080094303.shtml)
"Adjacencies are added to the table either through indirect manual configuration or dynamically, when discovered through a mechanism like ARP or using a routing protocol, such as BGP and OSPF, which forms neighbor relationships. If an adjacency is created by the FIB and is not discovered dynamically, then the Layer 2 addressing information is not known and the adjacency is considered incomplete. Once the Layer 2 information is known, the packet is forwarded to the route processor, and the adjacency is determined through ARP."
Based on the above, an incomplete adjacency "means missing layer 2 information"
But then my cisco book also defines "no-encap" as an incomplete arp resolution which essentially means the same thing as"no-adj".
2) My second question is about the statements from my cisco book:
"Packets that are marked as Cef punt are immediately are sent to layer 3 engine for further processing. some of the reasons are:
1)An entry can not be located in the fib.
2)The fib table is full."
My question is since Fib table holds all the prefixes present in routing table,therefore how is it possible for an entry(prefix) to be not present in fib but present in routing table?
Any suggestion?
thanks a lot!
Solved! Go to Solution.
12-13-2008 04:59 PM
no-adj = mac-address information missing so it is punted to layer 3 engine
CEF has a throttling mechanism for how many packets can be sent to the L3 engine - one packet per second.
no-encap = the number of packets dropped after the throttling level has been passed.
So an entry that is missing mac-address information but is within the threshold will be no-adj. An entry that is missing mac-address information but the CEF threshold has been passed will be no-encap -
http://www.cisco.com/en/US/docs/ios/ipswitch/command/reference/isw_s1.html#wp1012056
Jon
12-12-2008 10:19 PM
Hi Sarah,
no-adj: The mac string is missing in the adj
no-encap: need to do the ARP resolution
On switches, FIB are implemented in a TCAM which has a max number of entries so that's why you could have more routes in your routing table (limitation is only the memory of the box) than your TCAM can handle.
Hope this helps
Thanks
Laurent.
12-13-2008 05:12 AM
Thanks for your reply Laurent !
In both cases i.e no-adj,no-encap , mac address is missing. So then how do theses cases differ from each other?
12-13-2008 04:59 PM
no-adj = mac-address information missing so it is punted to layer 3 engine
CEF has a throttling mechanism for how many packets can be sent to the L3 engine - one packet per second.
no-encap = the number of packets dropped after the throttling level has been passed.
So an entry that is missing mac-address information but is within the threshold will be no-adj. An entry that is missing mac-address information but the CEF threshold has been passed will be no-encap -
http://www.cisco.com/en/US/docs/ios/ipswitch/command/reference/isw_s1.html#wp1012056
Jon
12-14-2008 12:48 PM
Hi Jon!
Based on your link, it appears no-encap and encap-fail are same.here is the excerpt from the link.
Encap_fail:
"Indicates the number of packets dropped after exceeding the limit for packets punted to the processor due to missing adjacency information (Cisco Express Forwarding throttles packets passed up to the process level at a rate of one packet every two seconds). "
Are they same Jon?
thanks a lot!
12-14-2008 05:46 PM
Thanks for your info very helpful, I only wish I knew 1/2 of what you know, I would be a happy man. Later
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: