This article is intended for those new to CEF and its impact on the way Multilayer Switching is done in Cisco hardware. Of course, this article can also serve as a review for those familiar with Cisco Express Forwarding but are looking for a refresher. In this first article we are going to go over the components that make up this switching architecture followed by some fundamental examples to illustrate these components and concepts at work. Before we get started be sure to download the topology we are going to be using in the lab examples for clarity.

Modern Catalyst Multilayer switches utilize Cisco Express Forwarding-based MLS. This terminology and architecture of this switching model can be tough to understand at first, but trust me, it really isn’t that difficult to grasp after you start working with it.

There are a couple different functions provided by a CEF-based MLS. The first function is building routing information. This routing information is built by the Layer 3 engine within the control plane and includes both static and dynamic routes. This information can be seen in the routing table. The second function provided by Cisco Express Forwarding is hardware switching of packets. Hardware switching of packets is done in the Layer 3 Forwarding Engine within the data plane. The data plane is where Cisco Express Forwarding works its magic. The control plane is where layer 3 decisions are made, when those layer 3 packets can NOT be switched in hardware.

Since CEF’s magic is provided in the data plane, we will start with it. It is the most fun anyway. The Layer 3 Forwarding Engine within the data plane has two components of its own.

Cisco Express Forwarding FIB is the first component, and the second is the Cisco Express Forwarding Adjacency table. The CEF FIB is basically just a reformatted routing table ordered such that the most specific routes are found first. The Forwarding Information Base contains next hop information for each prefix. The routing and next-hop information is built in software in the control plane, and then passed to the Layer 3 forwarding engine and placed in the Forwarding Information Base. It is really important to understand that this is basically a reordered routing table with some additional entries in it. When a packet enters the switch, the switch consults the Forwarding Information Base and finds the longest match prefix and obtains the next hop address. I know this doesn’t sound like magic yet, but stay with me, there is more and this stuff pretty neat.

In our second component, the adjacency table, contains and maintains layer 2 addresses for every entry in the Forwarding Information Base. This table is built from the Layer 3 engine in the same way the Forwarding Information Base is built. It is built from the ARP table that is built with the Layer 3 engine in the control plane and then passed to the Layer 3 Forwarding Engine and placed in the Cisco Express Forwarding Adjacency table. If you know how packets are encapsulated and rewritten as they make their way across a layer 3 network, you are probably beginning to develop an idea of what is going to happen with the adjacency table.

Having the FIB and Adjacency tables both handled in hardware, we’re able to see how Cisco Express Forwarding can dramatically improve the performance of layer 3 forwarding operations. It copies the work the Layer 3 Engine does in software, and the Layer 3 Forwarding Engine uses it to make multilayer switching decisions in hardware. Between the FIB having next hop layer 3 information, and the adjacency table having both the layer 3 and layer 2 information, CEF has at its disposal everything it needs to forward packets without consulting a routing table running in software, and without the need to do an ARP for layer 2 header rewrite. These operations are all in hardware and it all happens at line speed. Don’t you love it when tidbits of information are all pulled together.

Before we move on I want to take a look at two scenarios to see the paths packets take through a CEF-enabled MLS. In scenario 1, we have a valid FIB entry and associated adjacency table entry. A packet comes in the ingress interface, the Forwarding Information Base is consulted and an entry is found. The FIB is matched on the longest prefix. The layer two information is retrieved from the adjacency table and the packet is then forwarded through the packet rewrite engine, which rewrites the appropriate packet and frame header information at line speed and sends the packet out the egress interface. Notice there are no ARP requests are made, no software based processing is performed, and frame information is written in hardware.

In scenario 2, a packet comes ingress on an interface, the FIB is consulted and is not able to be CEF switched because of one of several different reasons. At this point the packet is punted to the Layer 3 engine for further processing. We aren’t going to cover all the scenarios in which a CEF Punt occurs here. We’ll save those for Part II.

It should be obvious, but it is worth mentioning here for clarity. As changes happen in the routing and ARP tables that are maintained by the Layer 3 Engine, those changes are automatically sent to the Layer 3 Forwarding Engine. This updates the CEF Forwarding Information Base and the Adjacency tables instantaneously.

Now that we have all of the basics out of the way, it is time to start looking at the relationship between the routing table, ARP table, the Cisco Express Forwarding Forwarding Information Base table, and the Cisco Express Forwarding adjacency table. Let’s start by looking at the IP addresses of the connected interfaces of the two devices used in these demonstrations.

MPLS1#show ip interface brief

InterfaceIP-AddressOK?MethodStatusProtocol

FastEthernet0/0            unassigned      YES NVRAM  administratively down down    

FastEthernet1/0172.16.13.1YESNVRAMupup

FastEthernet1/1172.16.12.1YESNVRAMupup

FastEthernet2/0            172.16.15.1     YES NVRAM  up                    up      

FastEthernet2/1            unassigned      YES NVRAM  administratively down down    

FastEthernet3/0unassignedYESNVRAMadministrativelydowndown

FastEthernet3/1            unassigned      YES NVRAM  administratively down down    

Loopback010.0.0.1YESNVRAMupup

Tunnel7                    10.0.0.1        YES TFTP   up                    down    

Tunnel70210.0.0.1YESTFTPupdown

Tunnel703                  10.0.0.1        YES TFTP   up                    down    

MPLS2#show ip interface brief

Interface                  IP-Address      OK? Method Status                Protocol

FastEthernet0/0            unassigned      YES NVRAM  administratively down down    

FastEthernet1/0            172.16.12.2     YES NVRAM  up                    up      

FastEthernet1/1            172.16.23.2     YES NVRAM  up                    up      

FastEthernet2/0172.16.24.2YESNVRAMupup

FastEthernet2/1172.16.25.2YESNVRAMupup

FastEthernet3/0unassignedYESNVRAMadministrativelydowndown

FastEthernet3/1            unassigned      YES NVRAM  administratively down down    

Loopback010.0.0.2YESNVRAMupup

Now we are going to look at the routing table on MPLS1:

MPLS1#show ip route

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

D-EIGRP,EX-EIGRPexternal,O-OSPF,IA-OSPFinterarea

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1-OSPFexternaltype1,E2-OSPFexternaltype2

       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     172.16.0.0/28 is subnetted, 6 subnets

O       172.16.24.0 [110/2] via 172.16.12.2, 01:12:32, FastEthernet1/1

O       172.16.25.0 [110/2] via 172.16.12.2, 01:12:32, FastEthernet1/1

O       172.16.23.0 [110/2] via 172.16.12.2, 01:12:32, FastEthernet1/1

C       172.16.12.0 is directly connected, FastEthernet1/1

C       172.16.13.0 is directly connected, FastEthernet1/0

C172.16.15.0isdirectlyconnected,FastEthernet2/0

     10.0.0.0/32 is subnetted, 2 subnets

O       10.0.0.2 [110/2] via 172.16.12.2, 01:12:32, FastEthernet1/1

C10.0.0.1isdirectlyconnected,Loopback0

Next is the FIB on MPLS1. Pay attention to the similarities and in particular the next hop addresses.

MPLS1#show ip cef

Prefix              Next Hop             Interface

0.0.0.0/0dropNull0(defaultroutehandlerentry)

0.0.0.0/8drop

0.0.0.0/32          receive

10.0.0.1/32         receive

10.0.0.2/32         172.16.12.2          FastEthernet1/1

127.0.0.0/8         drop

172.16.12.0/28attachedFastEthernet1/1

172.16.12.0/32      receive

172.16.12.1/32      receive

172.16.12.2/32      172.16.12.2          FastEthernet1/1

172.16.12.15/32     receive

172.16.13.0/28      attached             FastEthernet1/0

172.16.13.0/32receive

172.16.13.1/32      receive

172.16.13.15/32     receive

172.16.15.0/28attachedFastEthernet2/0

172.16.15.0/32      receive

172.16.15.1/32      receive

172.16.15.15/32     receive

172.16.23.0/28      172.16.12.2          FastEthernet1/1

172.16.24.0/28      172.16.12.2          FastEthernet1/1

172.16.25.0/28      172.16.12.2          FastEthernet1/1

224.0.0.0/4         drop

224.0.0.0/24receive

240.0.0.0/4         drop

255.255.255.255/32receive

Next, is the ARP table on MPLS1..followed by the Cisco Express Forwarding Adjacency table.

MPLS1#show ip arp

Protocol  Address          Age (min)  Hardware Addr   Type   Interface

Internet  172.16.13.1             -   ca00.0bd0.001c  ARPA   FastEthernet1/0

Internet172.16.12.1-ca00.0bd0.001dARPAFastEthernet1/1

Internet  172.16.12.2            73   ca01.0bd0.001c  ARPA   FastEthernet1/1

Internet  172.16.15.1             -   ca00.0bd0.0038  ARPA   FastEthernet2/0

MPLS1#show adjacency detail

Protocol Interface                 Address

TAGFastEthernet1/1172.16.12.2(7)

0packets,0bytes

                                   CA010BD0001C

                                   CA000BD0001D8847

                                   TFIB       02:48:53  

                                   Epoch: 0

IP       FastEthernet1/1           172.16.12.2(17)

                                   0 packets, 0 bytes

                                   CA010BD0001C

CA000BD0001D0800

                                   ARP        02:48:53  

                                   Epoch: 0

The correlations here should all be apparent. Notice the last 4 digits on the line under the bolded MAC addresses. These are ethertype codes. 8847 is MPLS-IP. 0800 is Ethernet.

And that about brings Cisco Express Forwarding Part I to a conclusion. I have brought to you a foundational knowledge of what Cisco Express Forwarding does and how it works. There are several more details to be covered in later articles. Right now I just to get this introduction out there because we need to understand Cisco Express Forwarding and the Forwarding Information Base for MPLS Part 3.