I am little confused about the location of FIB table and adjacency table in both cisco 6500 series and fixed ports switches .
In case of 6500 series switches , this is what my book says:
"Central CEF mode:The CEF FIB and adjacency tables reside on the route processor,
and the route processor performs the express forwarding. Use this CEF mode when
line cards are not available for CEF switching, or when features are not compatible
with distributed CEF."
That is what I understood from the above:
If line cards do no support CEF, then FIB and adjacency tables are built and are located on route processor( control plane ). Data plane operations are implemented in software and route processor performs those operations.
Some Cisco switches actually use different hardware to control the different planes. For
example, the Cisco Catalyst 6500 is a modular switch that uses the Multilayer Switch
Feature Card (MSFC) for control-plane operations, and the supervisor Policy Feature
Card (PFC) for the data-plane operations.
This is what I understood:
Supervisor module has has MSFC and PFC. MSFC implements control plane operation where as PFC implements data plane operation.
But the first paragraph says in Central cef mode, both data plane and control plane operations are implemented by route processor.
Fixed port catalyst switches: for e.g cat 3750 switch
I assume dcef is not possible because 3750 is fixed port switches. So only option is CEF in central mode.
Do these switches implement the Central mode cef in same way as mentioned above. i.e
"Central CEF mode:The CEF FIB and adjacency tables reside on the route processor and the route processor performs the express forwarding. Use this CEF mode whenline cards are not available for CEF switching, or when features are not compatible
with distributed CEF."
Or fixed ports switches such as 3750 implement data plane operation in hardware where FIB tabe and adjacency table are maintained on Data plane.
When talk about Data plane means hardware components such as ASICs used by the switch for hardware switching but control plane is Layer 3 engine or route processor that is responsible for building the FIB table and adjacency tables and downloading this information to the data plane.
The Catalyst 3750 and other familes of MLS switch such as 3550, 3560 and 4500 do not have distinguishable control plane and data plane modules or line cards but in catalyst 6500 family of switches, the control plane hardware is easily distinguishable from the data plane hardware
In fixed port switches, switching, routing, ACL, QoS, and forwarding decisions are made on specialized ASIC that is
central to all interfaces and in some modular chassis, switching, routing, ACL, QoS, and forwarding decisions are made on the Supervisor Engine, we call it central CEF
With distributed switching, a centralized switching engine synchronizes Layer 3 forwarding, routing, and rewrite tables to local tables on distributed line modules that handles forwarding decisions independently, so individual line cards or ports make forwarding decisions without the aid of the centralized switching engine; In other words, switches using distributed switching place additional copies of the CEF FIB and adjacency table on line modules or interfaces for routing and switching of frames, so The main route processor of the switch is responsible for generating a central master FIB and adjacency table and distributing these tables out to each dCEF line card and Each line card that supports dCEF has its own dedicated hardware-based L3 routing engine and CEF route cache, allowing for multiple L3 data plane operations to be performed simultaneously within a single chassis-based system
CEF-based Catalyst switches support one of two methods of hardware switching at Layer 3:
Centralized switching—Centralized switching carries out forwarding decisions on a specialized ASIC that is central to all interfaces of a Layer 3 switch. With centralized switching, routing, ACL, QoS, and forwarding decisions are made on the Supervisor Engine in a modular chassis or by Layer 3 engines in fixed port density Layer 3 switches. As a result, all frames to be routed or switched must pass through the centralized engine via a fabric or bus. Furthermore, with centralized switching, the hardware-switching performance of the Catalyst switch is based on the central forwarding engine and the fabric or bus architecture. Figure 9-3 illustrates centralized switching, logically. Note in Figure 9-3 how frames must pass through the centralized switching engine.
Fixed port switches:
Is following statement correct?
Routing,ACL QOS and forwarding decisions are made by route processor( layer 3 engine) . FIb and adjacency tables are implemented using TCAM.
These switches are the ones that can use centralized switching.
Catalyst 4500 family of switches and the Catalyst 6500 family of switches without the use of Distributed Forwarding Cards (DFC)
Is following statement correct?
Routing ,acl,qos and forwarding decisions are made by supervisor engine. FIb tables and adjacency tables are implemented using tcam.
NOTE: The confusion arises because I have seen another book which shows FIB and adjancency tables implemented in software in the context of CEF in central mode.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...