Procedure https://cll-ng.cisco.

com/content/xtrac/2

Discovery 2: Analyze Cisco Express Forwarding

Task 1: Analyze Cisco Express Forwarding
Step 1: Inspect the content of the FIB and adjacency tables on the HQ router.
You can use show ip cef and show adjacency enable-level commands to verify FIB and adjacency tables, respectively.
On HQ, enter the following commands:
HQ# show ip cef
Prefix Next Hop Interface
0.0.0.0/0 no route
0.0.0.0/8 drop
0.0.0.0/32 receive
10.10.10.0/30 attached Ethernet0/0
10.10.10.0/32 receive Ethernet0/0
10.10.10.1/32 receive Ethernet0/0
10.10.10.3/32 receive Ethernet0/0
127.0.0.0/8 drop
192.168.100.0/24 attached Ethernet0/1
192.168.100.0/32 receive Ethernet0/1
192.168.100.1/32 receive Ethernet0/1
192.168.100.255/32 receive Ethernet0/1
224.0.0.0/4 drop
224.0.0.0/24 receive
240.0.0.0/4 drop
255.255.255.255/32 receive

HQ# show adjacency

Protocol Interface Address

You can notice that there is an entry in the FIB table for every network that HQ knows about—that is, for every entry in the routing table, there is already a
preconfigured entry in the FIB table. Because HQ is currently not configured with any routing protocol, only local networks are present in the routing table. Router
HQ has no information about remote network 192.168.110.0/24.
However, the adjacency table contains no entries. The adjacency table is built from the ARP table. Because you have not generated any traffic yet, there are no
entries in the ARP table, and, therefore, the adjacency table is also empty.
Step 2: Initiate traffic on the HQ router toward the neighboring router BR1 using ping. Verify the content of the adjacency and FIB tables.
On HQ, enter the following commands:
HQ# ping 10.10.10.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.10.10.2, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms
Notice that the first packet was lost. This packet loss is because the HQ router was waiting for an ARP reply from BR1, which is needed to complete a new ARP
entry on HQ.
On HQ, enter the following commands:
HQ# show adjacency

Protocol Interface Address

IP Ethernet0/0 10.10.10.2(7)

HQ# show ip cef

Prefix Next Hop Interface

0.0.0.0/0 no route
0.0.0.0/8 drop
0.0.0.0/32 receive
10.10.10.0/30 attached Ethernet0/0
10.10.10.0/32 receive Ethernet0/0
10.10.10.1/32 receive Ethernet0/0
10.10.10.2/32 attached Ethernet0/0
10.10.10.3/32 receive Ethernet0/0
127.0.0.0/8 drop
192.168.100.0/24 attached Ethernet0/1
192.168.100.0/32 receive Ethernet0/1
192.168.100.1/32 receive Ethernet0/1
192.168.100.255/32 receive Ethernet0/1
224.0.0.0/4 drop
224.0.0.0/24 receive
240.0.0.0/4 drop
255.255.255.255/32 receive
Notice that the adjacency table changed as the HQ router learned about the new end host via the ARP protocol. As a consequence, the new entry is also inserted

1 din 3 25.05.2020, 11:29

Procedure https://cll-ng.cisco.com/content/xtrac/2

into the FIB table.

Step 3: Turn on EIGRP on the HQ router. BR1 is already configured. When the routing adjacency is up, verify that new routes were received.
On HQ, enter the following commands:
HQ(config)# router eigrp 1
HQ(config-router)# network 0.0.0.0
*Feb 11 12:10:48.280: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.10.10.2 (Ethernet0/0) is up: new adjacency
As you can see from the final line of the output, EIGRP adjacency is up.
On HQ, enter the following commands:
HQ# show ip route

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

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
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, H - NHRP, l - LISP
+ - replicated route, % - next hop override

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

C 10.10.10.0/30 is directly connected, Ethernet0/0
L 10.10.10.1/32 is directly connected, Ethernet0/0
192.168.100.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.100.0/24 is directly connected, Ethernet0/1
L 192.168.100.1/32 is directly connected, Ethernet0/1
D 192.168.110.0/24 [90/307200] via 10.10.10.2, 00:00:24, Ethernet0/0
You can see that HQ learned a new EIGRP route to 192.168.110.0/24 network, the LAN on BR1 router.
Step 4: Verify the FIB and adjacency tables again.
On HQ, enter the following commands:
HQ# show ip cef

Prefix Next Hop Interface

0.0.0.0/0 no route
0.0.0.0/8 drop
0.0.0.0/32 receive
10.10.10.0/30 attached Ethernet0/0
10.10.10.0/32 receive Ethernet0/0
10.10.10.1/32 receive Ethernet0/0
10.10.10.2/32 attached Ethernet0/0
10.10.10.3/32 receive Ethernet0/0
127.0.0.0/8 drop
192.168.100.0/24 attached Ethernet0/1
192.168.100.0/32 receive Ethernet0/1
192.168.100.1/32 receive Ethernet0/1
192.168.100.255/32 receive Ethernet0/1
192.168.110.0/24 10.10.10.2 Ethernet0/0
224.0.0.0/4 drop
224.0.0.0/24 receive
240.0.0.0/4 drop
255.255.255.255/32 receive
HQ# show adjacency

Protocol Interface Address

IP Ethernet0/0 10.10.10.2(11)
Notice that now the FIB table has a new entry for the 192.168.110.0/24 network. This new entry is because the routing table changed when a new route was
learned via EIGRP. On the other hand, the adjacency table remained the same, which was expected because the ARP table did not change.
Step 5: Verify that Cisco Express Forwarding is enabled for interface Ethernet 0/0 on the HQ router.
You can use the show ip interface interface command to verify the Cisco Express Forwarding status of the particular interface.
On HQ, enter the following command:
HQ# show ip interface ethernet 0/0

Ethernet0/0 is up, line protocol is up

Internet address is 10.10.10.1/30
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is disabled
Multicast reserved groups joined: 224.0.0.10
Outgoing access list is not set
Inbound access list is not set
Proxy ARP is enabled
Local Proxy ARP is disabled
Security level is default

2 din 3 25.05.2020, 11:29

Procedure https://cll-ng.cisco.com/content/xtrac/2

Split horizon is enabled

ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is enabled
IP fast switching on the same interface is disabled
IP Flow switching is disabled
IP CEF switching is enabled
IP CEF switching turbo vector
IP multicast fast switching is enabled
Notice the line "IP CEF switching is enabled" in the output, which tells you that Cisco Express Forwarding is enabled on this interface. Cisco Express Forwarding
for IPv4 is enabled, by default, on all interfaces with the global-level ip cef command. Cisco Express Forwarding should be used whenever possible. You might
need to disable Cisco Express Forwarding when you experience some problems and need to troubleshoot the issue.
Cisco Express Forwarding for IPv6, on the other hand, is not enabled by default. However, it is enabled automatically when you enable IPv6 unicast routing on
your devices. As a prerequisite, IPv4 Cisco Express Forwarding must be enabled to use IPv6 Cisco Express Forwarding.
Step 6: Disable Cisco Express Forwarding on interface Ethernet0/0 on the HQ router. Verify that Cisco Express Forwarding is disabled on the interface.
You can use the no ip route-cache cef interface-level command to disable Cisco Express Forwarding on a particular interface.
On HQ, enter the following commands:
HQ(config)# interface ethernet 0/0
HQ(config-if)# no ip route-cache cef
HQ(config-if)# end

HQ# show ip interface ethernet 0/0 | include CEF

IP CEF switching is disabled
IP route-cache flags are Fast, No CEF
Notice the line "IP CEF switching is disabled," which confirms that Cisco Express Forwarding is disabled on the interface.
Step 7: Disable Cisco Express Forwarding globally on the HQ router. Verify that Cisco Express Forwarding is disabled globally.
You can use the no ip cef global-level command to disable Cisco Express Forwarding on all interfaces of the router. You can verify whether Cisco Express
Forwarding is enabled globally with the show ip cef command.
On HQ, enter the following commands:
HQ(config)# no ip cef
HQ(config)# end
HQ# show ip cef
%IPv4 CEF not running

© 2020 Cisco Systems, Inc.

3 din 3 25.05.2020, 11:29