[6]

CHAPTER 1 CCIE Routing and Switching Exam Quick Reference Sheets by Anthony Sequeira

Administrators can create static routes that “float.” A floating static

Routing Information Base and route means the administrator increases the administrative distance of
Routing Protocol Interaction the static route to be greater than the administrative distance of the
dynamic routing protocol in use. This means the static route is relied on
only when the dynamic route does not exist.
Administrative distance
If a router learns of a network from multiple sources (routing protocols
or static configurations), it uses the administrative distance value to Routing table
determine which route to install in the routing (forwarding) table. The
The routing table has been the principal element of IP routing and the
default administrative distance values are listed here.
primary goal of routing protocols to build and maintain for most of
modern internetworking. The main routing table model, the hop-by-hop
Source Administrative Distance
routing paradigm, has the routing table list for each destination network
Connected interface 0 the next-hop address to reach that destination. As long as the routing
Static route 1 tables are consistent and accurate, with no misinformation, this simple
EIGRP summary route 5 hop-by-hop paradigm works well enough to deliver data to anywhere
from anywhere in the network. In recent practice, this simple hop-by-
External BGP 20
hop model is being abandoned for new technologies such as
Internal EIGRP 90 Multiprotocol Label Switching (MPLS). These technologies allow a
IGRP 100 simple and efficient label lookup to dictate the next hop that data
OSPF 110 should follow to reach a specific destination. Although this determina-
IS-IS 115 tion can be based on the routing table information, it can easily be
based on other parameters, such as quality of service or other traffic
RIP 120
engineering considerations. Note that MPLS is explored in its own
Exterior Gateway Protocol 140 chapter of this Short Cut.
On-Demand Routing 160
External EIGRP 170
Internal BGP 200
Unknown 255

© 2007 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 132 for more details.

CHAPTER 1
Routing information base and forwarding
information base interaction
The routing and forwarding architecture in Cisco routers and multilayer
switches used to be a centralized, cache-based system that combined
what is called a control plane and a data plane. The control plane refers
to the resources and technologies used to create and maintain the
routing table. The data plane refers to those resources and technologies
needed to actually move data from the ingress port to the egress port on
the device. This centralized architecture has migrated so that the two
planes can be separated to enhance scalability and availability in the
routing environment.
The separation of routing and forwarding tasks has created the Routing
Information Base (RIB) and the Forwarding Information Base (FIB).
The RIB operates in software, and the control plane resources take the
best routes from the RIB and place them in the FIB. The FIB resides in
much faster hardware resources. The Cisco implementation of this
enhanced routing and forwarding architecture is called Cisco Express
Forwarding (CEF).
Redistribution
Redistribution between routing protocols
Route redistribution might be required in an internetwork because
multiple routing protocols must coexist in the first place. Multiple
© 2007 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 132 for more details.
[7]
CCIE Routing and Switching Exam Quick Reference Sheets by Anthony Sequeira
routing protocols might be a necessity because of an interim period
during conversion from one to another, application-specific protocol
requirements, political reasons, or a lack of multivendor interoperability.
A major issue with redistribution is the seed metric to be used when the
routes enter the new routing protocol. Normally, the seed metric is
generated from the originating interface. For example, EIGRP would
use the bandwidth and delay of the originating interface to seed the
metric. With redistributed routes, however, these routes are not
connected to the router. Some routing protocols feature a default seed
metric for redistribution, whereas others do not. Here is a list of the
defaults for the various protocols. Note that Infinity indicates a seed
metric must be configured; otherwise, the route will not be used by the
receiving protocol.
Protocol Default Seed Metric
OSPF 20; except BGP, which is 1
IS-IS 0
RIP Infinity
IGRP/EIGRP Infinity

CHAPTER 1
Redistribution into RIP
Remember to set a default metric, using either the redistribute
command or the default-metric command. The command to redistrib-
ute routes into RIP is as follows:
redistribute protocol [process-id] [match route-type]
[metric metric-value] [route-map map-tag]
The match keyword allows you to match certain route types when
redistributing OSPF. For example, you can specify internal, or external
1, or external 2. The route-map keyword allows you to specify a route
map for controlling or altering the routes that are being redistributed.
Redistribution into OSPF
The default seed metric is 20. The default metric type for redistributed
routes is Type 2. Subnets are not redistributed by default. The
command for redistribution into OSPF is as follows:
redistribute protocol [process-id] [metric metric-value]
[metric-type type-value] [route-map map-tag] [subnets]
[tag tag-value]
The subnets keyword is critical in this command and specifies that
subnets should indeed be redistributed. The tag value allows the admin-
istrator to configure an optional tag value that can be used later to
easily identify these routes.
© 2007 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 132 for more details.
[8]
CCIE Routing and Switching Exam Quick Reference Sheets by Anthony Sequeira
Redistribution into EIGRP
Remember that like RIP, you must set a default seed metric when redis-
tributing into EIGRP. The command for redistribution into EIGRP is as
follows:
redistribute protocol [process-id] [match {internal | external
1 | external 2}] [metric metric-value] [route-map map-tag]
Troubleshooting routing loops
You can perform one-way or two-way redistributions. Redistribution
can also be performed in multiple locations throughout the topology.
With one-way redistribution, you typically pass a default route into the
“edge” protocol, and take all the edge protocol routes and redistribute
them into the core protocol of the network.
With two-way redistribution, all routes from each routing protocol are
passed into each other. If two-way redistribution is performed in multi-
ple areas in the network, there is an excellent chance for route “feed-
back” and routing loops. Routing loops are highly likely to occur
because routing information from one autonomous system can easily be
passed back into that same autonomous system.
 [9]

CHAPTER 1 CCIE Routing and Switching Exam Quick Reference Sheets by Anthony Sequeira

The safest way to eliminate the chance for a loop is to redistribute only
in one direction (one-way redistribution). If this is not possible, and
two-way redistribution is desired, try these techniques to ensure a lack
of loops:

Redistribute from the core protocol into the edge with filtering to block
routes that are native to the edge.

Apply two-way redistribution on all routes, and manipulate administra-

tive distance associated with the external routes so that they are not
selected when multiple routes exist for the same destination.

An excellent technique to detect a routing loop during redistribution is

to use the debug ip routing command. This command shows all
routing table activity as it occurs and demonstrates a loop condition
through routing table instability.

© 2007 Cisco Systems Inc. All rights reserved. This publication is protected by copyright. Please see page 132 for more details.