route caching is comprised of a l3 process and a layer 2 engine
the route process ships a flow's first packet, then the l2 process takes control by shipping the rest of the flow
a flow is a unidirectional stream of packets that share the same protocol... if this is a joint communication then naturally, there are two flows being managed
the downside of route caching is the delay caused by software processing the first packet
enter CEF, hardware based switching, faster as a result and requires less processing power
CEF keeps two tables a FIB (forward information base) and an adjacency table. the fib is basically the routing table formatted differently
as ARP discovers new and adjacent hosts, this information is updated in the adjacency table
with MLS, four tables are now used for packet switching...
No comments:
Post a Comment