Chapter 1:

Basic Network and Routing

Concepts

CCNP ROUTE: Implementing IP Routing

ROUTE v7 Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 1
 Chapter 1 Objectives
 Differentiating Between Dynamic Routing Protocols

 How Different Traffic Types, Network Types, and Overlaying

Network Technologies Influence Routing

 Differentiating Between the Various Branch Connectivity

Options and Describing Their Impact on Routing Protocols

 How to Configure Routing Information Protocol Next

Generation (RIPng)

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 2
 Differentiating
Between
Dynamic Routing
Protocols

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 3
 Differentiating Between Dynamic Routing
Protocols
 Enterprise Network Infrastructure
 Dynamic Routing Protocols in the Enterprise Network
Infrastructure
 Choosing a of Dynamic Routing Protocols
 IGP and EGP Routing Protocols
 Types of Routing Protocols
 Importance of convergence
 Route summarization
 Describe what influences routing protocol scalability

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 4
 Enterprise network infrastructure
Enterprise Campus
 An enterprise campus provides access to
the network communications services and
resources to end users and devices.
 It is spread over a single geographic
location, spanning a single floor, building, or
several buildings in the same locality.
 The campus is commonly designed using a
hierarchical model — comprising the core,
distribution, and access layers—creating a
scalable infrastructure.

Enterprise Edge
 An enterprise edge provides users at
geographically disperse remote sites with
access to the same network services as
users at the main site.
 The network edge aggregates private WAN
links that are rented from service providers,
and it enables individual users to establish
VPN connections.
 In addition, the network edge also provides
Internet connectivity for campus and branch
users.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 5
 Dynamic Routing Protocols in the Enterprise Network
Infrastructure
 It is a best practice that you use
one IP routing protocol throughout
the enterprise, if possible.
 One common example of when
multiple routing protocols are used
is when the organization is
multihomed.
 In this scenario, the most
commonly used protocol to
exchange routes with the service
provider is Border Gateway
Protocol (BGP), whereas within the
organization, Open Shortest Path
First (OSPF) or Enhanced Interior
Gateway Routing Protocol (EIGRP)
is typically used.
 In a single-homed infrastructures
static routes are commonly used
between the customer and the ISP.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 6
 Choosing a of Dynamic Routing Protocols

Input requirements :
 Size of network
 Multivendor support
 Knowledge level of specific protocol

Protocol characteristics :
 Type of routing algorithm
 Speed of convergence
 Scalability

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 7
 IGP and EGP Routing Protocols

An autonomous system (AS) represents a collection of network devices

under a common administrator.

Routing protocols can be divided based on whether they exchange routes

within an AS or between different autonomous systems:

Interior Gateway Protocols (IGP)

 Support small, medium-sized, and large organizations, but their
scalability has its limits. Fast convergence, and basic functionality is not
complex to configure. The most commonly used IGPs in enterprises are
EIGRP, OSPF and RIP is rarely used. IS-IS is also commonly found as
ISP IGP
Exterior Gateway Protocols (EGP)
 Used to exchange routes between different autonomous systems. BGP
is the only EGP that is used today. The main function of BGP is to
exchange a huge number of routes between different autonomous
systems.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 8
 Types of Routing Protocols

Distance vector protocols

 The distance vector routing approach determines the direction (vector) and distance (such as
link cost or number of hops) to any link in the network. The only information that a router knows
about a remote network is the distance or metric to reach this network and which path or
interface to use to get there. Distance vector routing protocols do not have an actual map of the
network topology.
Link-state protocols
 The link-state approach uses the Shortest Path First (SPF) algorithm to create an abstract of the
exact topology of the entire network or at least within its area. A link-state routing protocol is like
having a complete map of the network topology. The map is used to determine best path to a
destination.
Path vector protocols
 Path information is used to determine the best paths and to prevent routing loops. Similar to
distance vector protocols, path vector protocols do not have an abstract of the network topology.
Path vector protocols indicate direction and distance, but also include additional information
about the specific path of the destination.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 9
 Importance of Convergence
 The process of when
routers notice change in
the network, exchange
the information about
the change, and
perform necessary
calculations to
reevaluate the best
routes.

 To minimize downtime and quickly respond to network

changes, a fast convergence time is desired.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 10
 Route Summarization

 Route summarization
reduces routing
overhead and
improve stability and
scalability of routing
by reducing the
amount of routing
information that is
maintained and
exchanged between
routers.

Less frequent and smaller updates, as a result of route

summarization, also lower convergence time.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 11
 Routing Protocol Scalability
Scalability factors include:
 Number of routes
 Number of adjacent neighbors
 Number of routers in the network
 Network design
 Frequency of changes
 Available resources (CPU and memory)

 The scalability of the routing protocol and its configuration

options to support a larger network can play an important
role when evaluating routing protocols against each other.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 12
 Understanding Network
Technologies

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 13
 Understanding Network Technologies
 Differentiate traffic types
 Differentiate IPv6 address types
 Describe ICMPv6 neighbor discovery
 Network Types
 NBMA Networks

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 14
 Differentiate traffic types

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 15
 Differentiate traffic types
Unicast
 Unicast addresses are used in a one-to-one context. Unicast traffic is exchanged
only between one sender and one receiver.
Multicast
 Multicast addresses identify a group of interfaces across different devices. Traffic
that is sent to a multicast address is sent to multiple destinations at the same time.
 IPv6 reserved multicast addresses 224.0.0.0–239.255.255.255.
 IPv6 reserved multicast addresses have the prefix FF00::/8.
Anycast
 An anycast address is assigned to an interface on more than one node. When a
packet is sent to an anycast address, it is routed to the nearest interface that has
this address. The nearest interface is found according to the measure of distance of
the particular routing protocol.
Broadcast
 IPv4 broadcast addresses are used when sending traffic to all devices in the subnet.
Local broadcast address 255.255.255.255.
 IPv6 does not use a broadcast address, but uses multicast addresses instead

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 16
 Well-known IPv4 and Assigned IPv6 Multicast
Addresses

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 17
 Differentiate IPv6 address types

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 18
 Describe ICMPv6 neighbor discovery
Router Solicitation (RS)
 Sent by a device to the all IPv6 routers multicast to request a Router
Advertisement message from the router.
Router Advertisement (RA)
 Sent by an IPv6 router to the all IPv6 devices multicast. Includes link
information such as prefix, prefix-length, and the default gateway address.
 The RA also indicates to the host whether it needs to use a stateless or
stateful DHCPv6 server.
Neighbor Solicitation (NS)
 Sent by a device to the solicited node multicast address when it knows the
IPv6 address of a device but not its Ethernet MAC address. This is similar
to ARP for IPv4.
Neighbor Advertisement (NA)
 Sent by a device usually in response to a Neighbor Solicitation message.
Redirect
 This has similar functionality as in IPv4. Sent by a router to inform the
source of a packet of a better next-hop router on the link that is closer to the
destination.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 19
 Network Types

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 20
 Network Types
Point-to-point network
 A network that connects a single pair of routers.
 A serial link is an example of a point-to-point connection.
Broadcast network
 A network that can connect many routers along with the
capability to address a single message to all of the attached
routers.
 Ethernet is an example of a broadcast network.
Nonbroadcast Multiaccess (NBMA) network
 A network that can support many routers but does not have
broadcast capability.
 The sender needs to create an individual copy of the same
packet for each recipient if it wishes to inform all connected
packet can be transmitted.
 Frame Relay and Asynchronous Transfer Mode (ATM) are
examples of an NBMA network type.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 21
 NBMA Networks Issues
Split horizon
 Prevents a routing update that is received on an interface
from being forwarded out of the same interface.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 22
 NBMA Networks Issues
Neighbor discovery
 OSPF over NBMA neighbors are not automatically
discovered.
 You can statically configure neighbors, but an additional
configuration is required to manually configure the hub as a
Designated Router (DR).
 OSPF treats an NBMA network like Ethernet by default
Broadcast replication
 With routers that support multipoint connections over a
single interface that terminates at multiple PVCs, the router
must replicate broadcast packets.
 These replicated broadcast packets consume bandwidth
and cause significant latency variations in user traffic.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 23
 NBMA Networks Issues
Point-to-point subinterfaces
 Each subinterface, which provides connectivity between two
routers, uses its own subnet for addressing.
Point-to-multipoint subinterfaces
 One subnet is shared between all virtual circuits.
 Both EIGRP and OSPF need additional configuration to
support this underlying technology.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 24
 Connecting Remote
Locations with
Headquarters

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 25
 Connecting Remote Locations with
Headquarters
 Identify options for connecting branch offices and remote
locations
 Describe the use of static and default static routes
 Describe basic PPP configuration on point-to-point serial links
 Describe basic Frame Relay on point-to-point serial links
 Explain VRF Lite
 Describe the interaction of routing protocols over MPLS VPNs
 Explain the use of GRE for branch connectivity
 Describe Dynamic Multipoint virtual private networks
 Describe multipoint GRE tunnels
 Describe the Next Hop Resolution Protocol
 Identify the role of IPsec in DMVPN solutions

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 26
 Principles of Static Routing
A static route can be used in the following circumstances
 When it is undesirable to have dynamic routing updates
forwarded across slow bandwidth links, such as a dialup link.
 When the administrator needs total control over the routes used
by the router.
 When a backup to a dynamically recognized route is necessary.
 When it is necessary to reach a network accessible by only one
path (a stub network).
 When a router connects to its ISP and needs to have only a
default route.
 When a router is underpowered and does not have the CPU or
memory resources necessary to handle a dynamic routing
protocol.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 27
 Configuring an IPv4 Static Route
ip route prefix mask { address | interface [ address ]} [ dhcp ] [ distance ] [
name next-hop-name ] [ permanent | track number ] [ tag tag ]

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 28
 Configuring a Static Default Route

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 29
 Basic PPP Overview
 Point-to-Point Protocol (PPP) has several advantages over
its predecessor High-Level Data Link Control (HDLC).
• Authentication
• Multi-link
• Compression
• Quality

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 30
 PPP Authentication Overview
Router(config-if)# ppp authentication { chap | chap pap |
pap chap | pap } [ if-needed ][ list-name | default ] [ callin ]

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 31
 PPP Configuration Example

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 32
 PPPoE

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 33
 Basic Frame Relay Overview
 Frame Relay provides several benefits over traditional point-to-point
leased lines
• No need for separate physical interface per connection on the router
• Bandwidth cost is much more flexible
 Frame Relay is a switched WAN technology where virtual circuits (VCs)
are created by a service provider (SP) through the network.
• The VCs are typically PVCs that are identified by a data-link connection identifier
(DLCI)
 By default, a Frame Relay network is an NBMA network.
• To emulate the LAN broadcast capability that is required by IP routing protocols
Cisco IOS implements pseudo-broadcasting
• Dynamic maps always allow pseudo-broadcasting.
 Dynamic maps created via Frame Relay Inverse Address Resolution
Protocol (INARP) for IPv4 or Frame Relay Inverse Neighbor Discovery
(IND) for IPv6
 Split horizon is disabled by default on Frame Relay physical interfaces.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 34
 Frame Relay Topologies

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 35
 Basic Frame Relay Configuration

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 36
 VPN Connectivity Overview
 MPLS-based VPNs
 Tunneling VPNs
• GRE
• Ipsec
• DMVPN

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 37
 L3 MPLS VPNs

 Traffic forwarding through the MPLS backbone is based on

labels that are previously distributed among the core
routers.
 With a Layer 3 MPLS VPN, the service provider participates
in customer routing.
 The service provider establishes routing peering between
the PE and CE routers.
 Then customer routes that are received on the PE router
are redistributed into MP-BGP and conveyed over the
MPLS backbone to the remote PE router.
 On the remote PE, these customer routes are redistributed
back from MP-BGP into a remote PE-CE routing protocol.
 Routing protocols between PE-CE routers on the local and
remote sites may be totally different.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 38
 L2 MPLS VPNs
 A Layer 2 MPLS VPN CE router interconnects with the PE
router at Layer 2 using any Layer 2 protocol with Ethernet
being the most common.
 Layer 2 traffic is sent between PE routers, over a pre-
established pseudowire.
 Pseudowire emulates a wire between PE routers that
carries Layer 2 frames across the IP-MPLS backbone.
 There are two basic Layer 2 MPLS VPN service
architectures.
• Virtual Private Wire Service (VPWS) is a point-to-point technology that
allows the transport of any Layer 2 protocol at the PE.
• The second type of Layer 2 MPLS VPN is Virtual Private LAN Service
(VPLS), which emulates an Ethernet multiaccess LAN segment over
the MPLS core and provides multipoint- to-multipoint service.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 39
 Tunneling VPNs
GRE
 Tunneling protocol developed by Cisco that enables encapsulation of
arbitrary Layer 3 protocols inside a point-to-point, tunnel-over-IP
network.
 Traffic that is transported over the GRE tunnel is not encrypted
 GRE traffic is usually encapsulated within IPsec.
IPsec
 Is a framework that uses a set of cryptographic protocols to secure
traffic at Layer 3.
DMVPN
 This solution offers the capability to dynamically establish hub-to-spoke
and spoke-to-spoke IPsec tunnels, thus reducing latency and optimizing
network performance.
 DMVPN supports dynamic routing protocols between hub and spokes
as well as IP multicast. It is also suitable for environments with dynamic
IP addresses on physical interfaces such as DSL or cable connections.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 40
 Routing Across MPLS VPNs

 The Layer 2 MPLS VPN backbone solution is providing the Layer

2 service across the backbone, where R1 and R2 are connected
together directly using the same IP subnet.
 If you deploy a routing protocol over the Layer 2 MPLS VPN,
neighbor adjacency is established between your R1 and R2
routers. The figure presents the connectivity through the
backbone, which can be illustrated as one big switch.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 41
 Routing Across MPLS VPNs

 The Layer 3 MPLS VPN backbone solution is providing the Layer

3 service across the backbone, where R1 and R2 are connected
to ISP edge routers.
 A separate IP subnet is used on each side. If you deploy a
routing protocol over this VPN, service providers need to
participate in it.
 Neighbor adjacency is established between your R1 and the
closest PE router and between your R2 and it’s closest PE router.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 42
 Routing Over GRE Tunnel

 A passenger protocol or encapsulated protocol, such as

IPv4 or IPv6 that is being encapsulated.
 A carrier protocol, GRE in this example, that is defined by
Cisco as a multiprotocol carrier protocol.
 A transport protocol, such as IP, that carries the
encapsulated protocol.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 43
 Dynamic Multipoint Virtual Private Network

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 44
 DMVPN
The primary benefits of DMVPNs follow:
 Hub router configuration reduction
• Traditionally, the individual configuration of a GRE tunnel and IPsec
would need to be defined for each individual spoke router. The DMPVN
feature enables the configuration of a single mGRE tunnel interface and a
single IPsec profile on the hub router to manage all spoke routers
 Automatic IPsec initiation
• GRE uses NHRP to configure and resolve the peer destination address.
This feature allows IPsec to be immediately triggered to create point-to-
point GRE tunnels without any IPsec peering configuration.
 Support for dynamically addressed spoke routers
• When using point-to-point GRE and IPsec hub-and-spoke VPN networks,
it is important to know the physical interface IP address of the spoke
routers when configuring the hub router.
• DMVPN enables spoke routers to have dynamic physical interface IP
addresses and uses NHRP to register the dynamic physical interface IP
addresses of the spoke routers with the hub router.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 45
 Multipoint GRE
The main characteristics of the mGRE configuration are as follows:
 Only one tunnel interface needs to be configured on a router to support
multiple remote GRE peers
 To learn the IP addresses of other peer, devices using mGRE require
NHRP to build dynamic GRE tunnels.
 mGRE interfaces also support unicast, multicast, and broadcast traffic.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 46
 NHRP

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 47
 NHRP

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 48
 IPsec
IPsec provides four important security services:
 Confidentiality (encryption)
• No one can eavesdrop on the communication. If the communication is
intercepted, it cannot be read.
 Data integrity
• The receiver can verify that the data was transmitted through the path
without being changed or altered in any way.
 Authentication
• Authentication ensures that the connection is made with the desired
communication partner. IPsec uses Internet Key Exchange (IKE) to
authenticate users and devices that can carry out communication
independently.
 Antireplay protection
• Antireplay protection verifies that each packet is unique and not
duplicated.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 49
 Routing and
TCP/IP
Operations

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 50
 Routing and TCP/IP Operations
 MSS, Fragmentation, and PMTUD
 IPv4 Fragmentation and PMTUD
 Bandwidth Delay Product
 TCP Starvation
 Latency
 ICMP Redirect

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 51
 MSS, Fragmentation, and PMTUD
 An IPv4 packet has a maximum size of 65,535 bytes
 An IPv6 packet with a hop-by-hop extension header and the
jumbo payload option can support up to 4,294,967,295
bytes
 However, most transmission links enforce a smaller
maximum packet length called the maximum transmission
unit (MTU).
 When a router receives an IPv4 packet larger than the MTU
of the egress or outgoing interface, it must fragment the
packet unless the DF (Don’t Fragment) bit is set in the IPv4
header.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 52
 MSS, Fragmentation, and PMTUD
Fragmentation causes several issues including the
following:
 CPU and memory overhead in fragmentation of the packet
 CPU and memory overhead in destination devices during
reassembly of packets
 Retransmission of the entire packet when one fragment is
dropped
 Firewalls that do Layer 4 through Layer 7 filtering may have
trouble processing IPv4 fragments correctly

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 53
 IPv4 Fragmentation and PMTUD
 TCP Maximum Segment Size (MSS) defines the largest amount
of data that the receiving device is able to accept in a single TCP
segment.
 To avoid fragmentation of an IPv4 packet, the selection of the
TCP MSS is the minimum buffer size and MTU of the outgoing
interface minus 40 bytes. The 40 bytes take into account the 20-
byte IPv4 header and the 20-byte TCP header.
 The TCP MSS helps avoid fragmentation at the two ends of the
TCP connection but it does not prevent fragmentation due to a
smaller MTU on a link along the path.
 Path MTU Discovery (PMTUD) was developed for the purpose of
determining the lowest MTU along a path from the packet’s
source to destination.
 PMTUD is only supported by TCP.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 54
 Bandwidth Delay Product
 TCP can experience bottlenecks on paths with high bandwidth and long
round-trip delays.
 These networks are known as a long fat pipe or long fat network , LFN
(pronounced “elephan [t]).”
 The key parameter is the Bandwidth Delay Product (BDP), which is the
product of the bandwidth (bps) times the round-trip delay (RTT in
seconds).
 The BDP is the number of bits it takes to “fill the pipe” (in other words,
the amount of unacknowledged data that TCP must handle to keep the
pipeline full).
 BDP is used to optimize the TCP window size to fully utilize the link.
 The result is the maximum of data that can be transmitted on the link at
any given time. The TCP window size should then use the BDP.
 The TCP window size indicates the amount of data that can be sent
before expecting an acknowledgment, usually several times the MSS.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 55
 TCP Starvation
 TCP incorporates mechanisms for reliability, flow control, and
congestion avoidance.
 However, UDP is a lightweight protocol for faster and simpler
data transmissions and does not include these features.
 When there is a combination of TCP and UDP flows during a
period of congestion, TCP tries to do its part by backing off on
bandwidth, called slow start .
 However, UDP without any flow control mechanisms continues,
potentially using up the available bandwidth given up by TCP.
 This is known as TCP starvation/UDP dominance .
 It is not always possible to separate TCP- and UDP-based flows,
but it is important to be aware of this behavior when mixing
applications that use both transport layer protocols.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 56
 Latency
 Latency is the amount of time for a message to go from point to another.
 Network latency is the amount of time for the packet to travel the
network from the original source to the final destination.
 Several factors can cause latency, including propagation delay,
serialization, data protocols, routing, switching, queuing, and buffering.
 The flow control and reliability features of TCP have an effect on end-to-
end latency.
 TCP requires an established virtual connection, and bidirectional
communications for acknowledgments, window sizes, congestion
control, and other TCP mechanisms, all of which has an effect on
latency.
 UDP is a protocol that does not include reliability or flow control. A
device simply sends packets with UDP segments with the assumption
that they will reach their destination.
 UDP is typically used for applications such as streaming media that
require minimal delay and can tolerate occasional packet loss. UDP has
very low latency, better than most TCP connections.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 57
 ICMP Redirect
 ICMPV4 Redirect messages are used by routers to notify the sender of
a packet that there is a better route available for a particular destination.
 Similar to IPv4, R1 will forward the IPv6 packet to PCB, but unlike ICMP
for IPv4, it will send an ICMPv6 redirect message to PCA informing the
source of the better route. PCA can now send subsequent IPv6 packets
directly to PCB even though it is on a different IPv6 network.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 58
 Implementing RIPng
 Describe general RIP characteristics
 Describe how to configure and verify basic RIPng
 Describe how to configure RIPng to share default routes
 Analyze the RIPng database

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 59
 RIP Overview
 RIP is an IGP that is used in smaller networks.
 It is a distance vector routing protocol that uses hop count
as a routing metric.
 There are three versions of RIP: RIPv1, RIPv2, and RIPng.
RIPv1 and RIPv2 route in IPv4 networks.
 RIPng routes in IPv6 networks.
 RIP is a standardized IGP routing protocol that works in a
mixed-vendor router environment.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 60
 RIP Overview

 RIP uses hop count, the number of routers, as the metric.

 If a device has two paths to the destination network, the
path with fewer hops will be chosen as the path to forward
traffic.
 If a network is 16 or more hops away, the router considers it
unreachable.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 61
 RIP Overview
 As a routing loop-prevention technique, RIP implements
split horizon. Split horizon prevents routing information from
being sent out the same interface from which it was
received.
 Split horizon with poison reverse is a similar technique but
sends the update with a metric of 16, which is considered
unreachable by RIP.
 RIP is also capable of load balancing traffic over equal-cost
paths.
 The default is four equal-cost paths.
 If the maximum number of paths is set to one, load
balancing is disabled.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 62
 Comparing Features in RIPv2 and RIPng

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 63
 RIPv2 Configuration

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 64
 RIPv2 Configuration
 By default, RIPv2 automatically summarizes networks at
major network boundaries, summarizing routes to the
classful network address
 When route summarization is disabled, the software sends
subnet routing information across classful network
boundaries.

Router(config-router)# no auto-summary

 The ip summary-address rip ip-address network-mask

interface command is used to summarize an address or
subnet under a specific interface.

Router(config-if)# ip summary-address rip 10.2.0.0 255.255.0.0

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 65
 Configuring RIPng

R2(config)# ipv6 router rip CCNP_RIP

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 66
 Verify RIPng Configuration

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 67
 RIPng Summarization

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 68
 Propagating a Default Route

R1(config-if)# ipv6 rip name default-information originate | only

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 69
 RIPng Verification Commands

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 70
 RIPng Verification Commands

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 71
 Investigating the RIPng Database

 The RIP process (there can be multiple RIPng processes on a single router).
 The route prefix.
 The route metric, in which RIPng uses hop count as a metric. In the example, all
three routes have a metric of 2. This means the destination network is 2 hops away,
counting itself as a hop.
 Installed and expired, in which the keyword “installed” means the route is in the
routing table. If a network becomes unavailable, the route will become “expired” after
the dead timer expires. An expired route value (in seconds), during which the route
will be advertised as expired, is listed.
 Expires in, in which if the countdown timer reaches 0, the route is removed from the
routing table and marked expired. This timer, the dead timer, is by default three
times the hello timer—180 seconds.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 72
 Chapter 1 Summary
 The role of static routes and dynamic routing protocols in enterprise networks.
 The differences between IGP and EGP routing protocols.
 The three types of routing protocols: distance vector, link-state and path vector.
 The importance of convergence time and how route summarization reduced convergence time
and improves scalability.
 The four traffic types: unicast, multicast, anycast, and broadcast.
 The differences between point-to-point, broadcast, and NBMA networks.
 How point-to-point subinterfaces are used to overcome the limitations of NBMA networks.
 How VPNs are used to provide security of a public Internet.
 Common types of VPNs: MPLS-based VPNs, GRE+IPsec, and DMVPN.
 How a customer establishes connectivity with a service provider using a routing protocol and a
layer 3 MPLS VPN.
 How static GRE tunnels can establish virtual point-to-point links and support dynamic routing
protocols.
 Using DMVPN to provide fully meshed VPN connectivity with a simple hub-andspoke
configuration.
 How DMVPN relies on NHRP, mGRE, and IPsec.
 The differences and similarities between RIPv2 and RIPng.
 How to configure RIPng.
 How to propagate a default route in RIPng.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 73
 Chapter 1 Labs
 CCNPv7_ROUTE_Lab1-1_RIPng

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 74
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 75
 Acknowledgment
• Some of images and texts are from Implementing Cisco IP Routing (ROUTE)
Foundation Learning Guide by Diane Teare, Bob Vachon and Rick Graziani
(1587204568)
• Copyright © 2015 – 2016 Cisco Systems, Inc.
• Special Thanks to Bruno Silva

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 76
 Chapter 2:
EIGRP Implementation

CCNP ROUTE: Implementing IP Routing

ROUTE v7 Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 77
 Chapter 2 Objectives
 Establishing EIGRP Neighbor Relationships
 Building the EIGRP Topology Table
 Optimizing EIGRP Behavior
 Configuring EIGRP for IPv6
 Named EIGRP Configuration

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 78
 Establishing
EIGRP Neighbor
Relationships

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 79
 Enhanced Interior Gateway Routing Protocol
(EIGRP)
 Enhanced Interior Gateway Routing Protocol (EIGRP) is an
advanced distance vector routing protocol designed by
Cisco.
 The basic configuration is simple and easy to understand,
so it is commonly used in smaller networks.
 Its advanced features, which provide rapid convergence,
higher scalability, and support for multiple routed protocols,
fulfill requirements in complex network environments.
 EIGRP supports both IPv4 and IPv6.
 Although standard EIGRP configuration between IPv4 and
IPv6 differs, it can be unified using newly introduced named
EIGRP configuration mode.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 80
 Establishing EIGRP Neighbor Relationships

 EIGRP Characteristics
 EIGRP Reliable Transport
 EIGRP Operation Overview
 Configuring and Verifying Basic EIGRP for IPv4
 EIGRP Timers
 EIGRP Adjacencies in a Frame Relay Network
 EIGRP Adjacencies in a Layer 3 MPLS VPN Network
 EIGRP Adjacencies in a Layer 2 MPLS VPN Ethernet
Network

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 81
 EIGRP Characteristics
Fast convergence
 EIGRP uses the diffusing update algorithm (DUAL) to
achieve rapid convergence. A router running EIGRP stores
its neighbors’ routing tables so that it can quickly adapt to
changes in the network.
 If no appropriate route exists in the local routing table and
no appropriate backup route exists in the topology table,
EIGRP queries its neighbors to discover an alternative
route. These queries are propagated until an alternative
route is found or until it is determined that no alternative
route exists.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 82
 EIGRP Characteristics
Partial updates
 EIGRP sends partial triggered updates rather than periodic
updates. These updates are sent only when the path or the
metric for a route changes. They contain information about
only that changed link rather than the entire routing table.
Propagation of these partial updates is automatically
bounded so that only those routers that require the
information are updated. As a result, EIGRP consumes
significantly less bandwidth than IGRP. This behavior also
differs from link-state protocol operation, which sends a
change update to all routers within an area.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 83
 EIGRP Characteristics
Multiple network layer support
 EIGRP supports IP Version 4 (IPv4) and IP Version 6 (IPv6)
using protocol-dependent modules that are responsible for
protocol requirements specific to the network layer.
EIGRP’s rapid convergence and sophisticated metric offer
superior performance and stability when implemented in
IPv4 and IPv6 networks.
Use of multicast and unicast
 For communication between routers, EIGRP uses multicast
and unicast rather than broadcast. As a result, end stations
are unaffected by routing updates or queries. The multicast
address used for EIGRP for IPv4 is 224.0.0.10, and the
multicast address for EIGRP for IPv6 is FF00::A.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 84
 EIGRP Characteristics
VLSM support
 EIGRP is a classless routing protocol, which means that it
advertises a subnet mask for each destination network. This
enables EIGRP to support discontinuous subnetworks and
VLSM.
Sophisticated metric
 EIGRP represents metric values in a 32-bit format to
provide enough granularity. EIGRP supports unequal metric
load balancing, which allows administrators to distribute
traffic flow more efficiently in their networks.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 85
 EIGRP Reliable Transport

 EIGRP runs directly above the IP layer as its own protocol,

numbered 88.
 RTP is the component of the EIGRP responsible for
guaranteed, ordered delivery of EIGRP packets to all
neighbors.
 It supports intermixed transmission of multicast or unicast
packets.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 86
 EIGRP Operation Overview

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 87
 Configuring and Verifying Basic EIGRP for IPv4

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 88
 Configuring and Verifying Basic EIGRP for IPv4

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 89
 Verifying EIGRP Neighbor Relationships

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 90
 Verifying the EIGRP Interfaces

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 91
 Verifying the EIGRP Networks

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 92
 Configuring Passive Interfaces

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 93
 Verifying Hello and Hold Timers

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 94
 EIGRP Timers
 EIGRP determines default timer values based on link type. If default
values are not suitable for a specific network topology, you can
manipulate values to improve convergence time.
 EIGRP hello and hold timers between neighbors do not need to be
identical to successfully establish EIGRP neighbor relationship;
however, asymmetrical timers may lead to flapping EIGRP neighbor
relationships and network instability.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 95
 EIGRP Adjacencies in a Frame Relay Network

 When configuring EIGRP over point-to-multipoint

subinterfaces, a single IP subnet is used.
 To emulate broadcast multiaccess network and enable
EIGRP to send multicast packets over Frame Relay virtual
circuits (VCs), you must add the broadcast keyword in the
Frame Relay static mapping statement
• frame-relay map ip ip-address dlci broadcast
 When configuring EIGRP over point-to-point subinterfaces,
a different IP subnet is used for each subinterface.
• These are logical interfaces that are emulating a leased line network
and are a routing equivalent to point-to-point physical interfaces

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 96
 EIGRP Adjacencies in a Layer 3 MPLS VPN
Network

 Provider-edge (PE) routers participate in customer routing,

guaranteeing optimum routing between customer sites.
 PE routers carry a separate set of routes for each customer,
resulting in perfect isolation between the customers.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 97
 EIGRP Adjacencies in a Layer 2 MPLS VPN
Ethernet Network

 Customer routers are located within single metropolitan area and they may be connected over
the local Layer 2 MPLS VPN switch network. Customer traffic never passes through the SP
backbone.
 Customer routers are located between several geographically distant areas that need to be
connected over L2 MPLS VPN with point-to-point links through the SP backbone.
 Customer routers are located between several geographically distant areas that need to be
connected over L2 MPLS VPN with multipoint links through the SP core. From the customer
perspective SP network looks like a LAN switch.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 98
 Building the
EIGRP Topology
Table

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 99
 Building the EIGRP Topology Table
 EIGRP Neighbors Routing Information Exchange
 How EIGRP Chooses the Best Path through the Network
 Calculate EIGRP Metric
 Feasibility Condition prevents loops in EIGRP Networks
 Understand EIGRP Path Selection Process

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 100
 EIGRP Neighbors Routing Information
Exchange

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 101
 EIGRP Neighbors Routing Information
Exchange

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 102
 Verifying EIGRP Packet Traffic

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 103
 Verifying the EIGRP Routes

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 104
 Choosing the Best Path (DUAL)

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 105
 EIGRP Topology Table

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 106
 EIGRP Routing Information
 Only the routes that are used by EIGRP, the successor
routes, get advertised.
 Subnets of directly connected interfaces on which EIGRP
has been enabled using the network command
 Subnets learned by redistribution of routes into EIGRP from
other routing protocols or routing information sources
 Redistribution is a method of taking routing information from
one source and advertising it into another routing protocol.
 Redistribution is used in situations when multiple routing
protocols are used in the same autonomous system, or
when you want to include already-defined static routes into
the selected routing protocol.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 107
 EIGRP Metric
EIGRP uses a composite metric to determine the best path to
the destination. The metric’s value derives from a formula that
can use the following parameters:
 Bandwidth: Least value of the bandwidth for all links
between the local router and the destination.
 Delay: Cumulative delay obtained as sum of values of all
delays for all links between the source and destination.
 Reliability: This value represents the worst reliability
between source and destination (based on keepalives).
 Load: This value represents the worst load on the link
between the source and the destination (based on the
packet rate and the configured bandwidth of the interface).

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 108
 EIGRP Metric Calculation
Metric = [(K1 * Bandwidth + [(K2 * Bandwidth) / (256 –
Load)] + K3 * Delay) * K5/(K4 + Reliability)] * 256

 With the default K-Values K1=1, K2=0, K3=1, K4=0, K5=0

 Metric = (Bandwidth + Delay) * 256

 Note that changing the K values is not recommended.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 109
 EIGRP Metric Calculation Example

 Bandwidth = (10^7 / Least bandwidth in kilobits per second)

 Delay = microseconds/10
 Metric = (Bandwidth + Delay) * 256
 Bandwidth = (10,000,000 / 10,000) = 1,000
 Delay = [4000 + 1000 + 5000] = 10000 [tens of microseconds]
 Metric = (1000 + 10,000) * 256 = 2,816,000

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 110
 EIGRP Successor and FS Example

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 111
 EIGRP Path Calculation Example

 Reported Distance

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 112
 EIGRP Path Calculation Example

 Fisable Distance

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 113
 EIGRP Path Calculation Example

 Successor
 Fisable Successor

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 114
 Optimizing EIGRP
Behavior

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 115
 Optimizing EIGRP Behavior
 EIGRP queries
 Describe how stub routing can be used to reduce the
amount of queries when EIGRP goes active
 EIGRP stuck-in-active issue
 Explain how using summary routes lessen the impact of
query scope when EIGRP goes active
 Describe load-balancing options with EIGRP

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 116
 EIGRP Queries

 When a router loses a route and does not have a feasible

successor in its topology table, it looks for an alternative
path to the destination.
 This is known as going active on a route.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 117
 Active Route

 Two major solutions exist to optimize the query propagation process

and to limit the amount of unnecessary EIGRP load on the links.
• Route summarization
• EIGRP stub routing

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 118
 EIGRP Stub Routers

 Routers configured as stubs do not forward EIGRP learned

routes to other neighbors, and more importantly, nonstub
routers do not send query messages to stub routers.
 This saves CPU cycles and bandwidth and speeds up
convergence.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 119
 EIGRP Stub Options

 To configure a router as a stub use the eigrp stub

command in router configuration mode or address family
configuration mode.
 To disable the EIGRP stub routing feature, use the no form
of this command.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 120
 EIGRP Stub Options
 A router that is configured as a stub shares information
about connected and summary routes with all neighboring
routers by default.
 You can combine all stub options except for receive-only to
achieve desired combination of advertised routes.
 The connected option permits the EIGRP stub router to
advertise all connected routes for interfaces that are
matched with an EIGRP network command. This option is
enabled by default and is the most widely practical stub
option.
 The summary option permits the EIGRP stub router to
send summary routes. You can create summary routes
manually, or you can create them automatically by enabling
auto-summary at a major network boundary router.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 121
 EIGRP Stub Options
 The static option permits the EIGRP stub router to
advertise static routes. You still need to redistribute static
routes into EIGRP using the redistribute static command.
 The redistribute option permits the EIGRP stub router to
advertise all redistributed routes, as long as redistribution is
configured on the stub router using the redistribute
command.
 The receive-only option restricts the stub router from
sharing any of its routes with any other router within an
EIGRP autonomous system. This option does not permit
any other option to be specified because it prevents any
type of route from being sent.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 122
 EIGRP Topology for Configuring Stub Routers

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 123
 Initial Configuration (HQ)

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 124
 Initial Configuration (BR1A)

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 125
 Configuring an EIGRP Stub Router

 When the BR1A router is configured as a stub, the EIGRP

adjacency needs to be reestablished.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 126
 BR1A Verified as an EIGRP Stub on HQ

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 127
 Change in the routing tables
 BR1A Routing Table stays exactly the same

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 128
 Configuring an EIGRP Connected Stub

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 129
 Change in the routing tables

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 130
 Configuring an EIGRP Receive-Only Stub

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 131
 Change in the routing tables

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 132
 Stuck in Active
 Once a route goes active and the query sequence I
initiated, it can only come out of the active state and
transition to the passive state when it receives a reply for
every generated query.
 If the router does not receive a reply to all the outstanding
queries within 3 minutes (the default time), the route goes
into the stuck-in-active (SIA) state.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 133
 Stuck in Active
 This timer is called the active timer.
 Once the active timer expires, the neighbor relationship is
reset.
 This setting causes the router to go active on all routes that
were known through the lost neighbor and to re-advertise all
the routes that it knows to the lost neighbor.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 134
 Stuck in Active
 Two new additional EIGRP packets were introduced to
overcome the described limitation.
 When no reply to a query is received, EIGRP sends an SIA
query packet when the active timer is halfway through (after
90 seconds).
 This enables the neighboring router to respond with a SIA
reply and confirm to the upstream router that it is still
searching for a replacement route.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 135
 Stuck in Active
 R1 queries downstream R2 (with an SIA query) at the midway point of the active
timer about the status of the route.
 R2 responds (with an SIA reply) that it still is searching for a replacement route.
 Upon receiving this SIA reply response packet, R1 validates the status of R2
and does not terminate the neighbor relationship.
 Meanwhile, R2 will send up to three SIA queries to R3. If they go unanswered,
R2 will terminate the neighbor relationship with R3. R2 will then update R1 with
an SIA reply indicating that the network 192.168.14.0/24 is unreachable.
 R1 and R2 will remove the active route from their topology tables. The neighbor
relationship between R1 and R2 remains intact.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 136
 Reducing Query Scope by Using Summary
Routes

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 137
 Configuring EIGRP Summarization
 Implementing EIGRP summarization provides several
benefits. Not only does it reduce the size of routing tables
on the routers, but it also limits the query scope.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 138
 HQ RT without summarization

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 139
 Enable auto-summarization in the BRs

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 140
 HQ RT after summarization

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 141
 Testing Connectivity from HQ to the
Summarized Network

 Because both routes have the same cost, HQ will load

balance between these two routes causing unreachability
issues.

 This occurs because both remote networks belong to the

same classfull, creating a discontinuous network
connection.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 142
 Configuring Manual Summarization

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 143
 HQ BR1A after Manual Summarization

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 144
 HQ RT after Manual Summarization

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 145
 Obtaining Default Route
 The candidate can be a statically configured default route
defined locally with the command ip route 0.0.0.0 0.0.0.0
next-hop | interface .
 The candidate can alsobe a default route announced by
the dynamic routing protocol. EIGRP can redistribute
statically defined default routes by using the redistribute
static configuration command.
 In addition, any classful network residing in the local routing
table can become a default candidate when used with the
ip default-network configuration command.
• The command attaches an exterior flag to any classful EIGRP route,
thus making it a candidate for a default route.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 146
 Redistributing Static

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 147
 Redistributing Static

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 148
 Load Balancing with EIGRP
 EIGRP can distribute traffic over multiple links leading to the
same destination to increase the effective network
bandwidth.
 It supports load balancing over equal-metric paths and also
over unequal-metric paths.
 EIGRP enables load balancing between a maximum of four
equal-metric paths by default.
 The maximum number of parallel routes that an IP routing
protocol can support can be changed using the maximum-
paths router configuration command.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 149
 Load Balancing with EIGRP
 When a packet is process switched, load balancing over
equal-metric paths occurs on a per-packet basis.
 When packets are fast switched, load balancing over equal-
metric paths occurs on a per-destination basis.
 Cisco Express Forwarding (CEF) switching, enabled by
default, supports both per-packet and per-destination load
balancing.
 Load balancing over unequal-metric links is disabled by
default.
 Only feasible successor paths can be included in the
EIGRP load-balancing, to ensure the topology stays loop
free.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 150
 Configuring EIGRP Load Balancing

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 151
 Configuring EIGRP Load Balancing

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 152
 Load Balancing Across Unequal-Metric Paths

 The route must be loop free. This condition is satisfied

when the advertised distance is less than the total distance,
or when the route is a feasible successor.
 The metric of the route must be lower than the metric of the
best route (the successor) multiplied by the variance that is
configured on the router.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 153
 Verifying EIGRP Load-Balance

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 154
 Verifying EIGRP Load-Balance

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 155
 Configuring
EIGRP for IPv6

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 156
 Configuring EIGRP for IPv6
 Differences and Similarities of EIGRP for IPv4 and IPv6
 Configure Basic EIGRP for IPv6 Settings
 Configure and Verify EIGRP for IPv6 Summarization
 Verify basic EIGRP for IPv6 settings

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 157
 Overview of EIGRP for IPv6
 EIGRP for IPv6 uses IPv6 prefixes and lengths rather than IPv4
subnets and masks.
 To establish EIGRP for IPv6 neighbor relationship, it uses IPv6
link-local addresses. EIGRP for IPv4 does not have the concept
of link-local address.
 EIGRP uses built-in authentication features of the IPv6 protocol
rather than protocol specific authentication implemented with
IPv4 to guarantee message authentication.
 To transport routing information, EIGRP for IPv6 encapsulates
IPv6 prefixes in the IPv6 messages, not in the IPv4 packets.
 IPv6 has no concept of the classful network; so when you use
EIGRP for IPv6, there is no automatic summarization at the class
boundaries. The only way to summarize IPv6-advertised prefixes
is through manual summarization.
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 158
 Overview of EIGRP for IPv6
 If IPv4 address is not configured on the router, EIGRP for
IPv6 requires an EIGRP router ID before it can start
running. In IPv4, if you do not configure the EIGRP router
ID, the router will automatically assign it using the highest
loopback or the highest active interface IPv4 address.
 EIGRP for IPv6 under a specific interface intended to send
and receive routing protocol messages. In EIGRP for IPv4,
you configure interfaces under the routing protocol
configuration mode.
 EIGRP for IPv6 uses assigned dedicated multicast address
FF02::A, whereas EIGRP for IPv4 uses dedicated multicast
address 224.0.0.10.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 159
 Configuring and Verifying EIGRP for IPv6

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 160
 Configuring and Verifying EIGRP for IPv6

The ipv6 unicast-routing command enables the router:

 To be configured for static and dynamic IPv6 routing
 To forward IPv6 packets
 To send ICMPv6 router advertisement messages

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 161
 Configuring and Verifying EIGRP for IPv6

 EIGRP for IPv6 has a shutdown feature.

 The routing process must be in “no shutdown” mode for EIGRP
for IPv6 processing.
 No shutdown is the default on later IOSs. If necessary, you might
have to issue the no shutdown command in EIGRP for IPv6
configuration mode.
 Another important parameter is the EIGRP router ID.
 Like EIGRP for IPv4, EIGRP for IPv6 uses a 32-bit router ID.
 If no IPv4 active address is configured on the router, the router
will not be able to choose the EIGRP router ID.
 In this case, you must configure the router ID manually under the
EIGRP routing process to make EIGRP for IPv6 operational.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 162
 Configuring and Verifying EIGRP for IPv6
 Before you enable EIGRP for IPv6 on the interface, it must
have a valid IPv6 link-local address.
 EIGRP for IPv6 uses link-local addresses to form EIGRP
neighbor relationships.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 163
 Link-Local Importance for IPv6 Routing
 The link-local address is automatically created on an
interface when the interface obtains a global IPv6 address,
either manually or dynamically.
 IPv6 can also be enabled on an interface without assigning
a global unicast address using the interface mode
command ipv6 enable.
 In both cases, IPv6 link-local address will be assigned
automatically to the interface using EUI-64.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 164
 Verifying EIGRP for IPv6 Neighbor Adjacency
and Topology Table

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 165
 Verifying EIGRP for IPv6 Routing Table

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 166
 Configuring EIGRP for IPv6 Summary Route

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 167
 Named EIGRP
Configuration

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 168
 Named EIGRP Configuration
 Describe how EIGRP named configuration is different from
the classic EIGRP configuration
 Explain what is configured under different address family
configuration modes
 Compare examples of classic and named EIGRP
configuration
 Configuring and verifying EIGRP for IPv6

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 169
 Named EIGRP Configuration
 Configuring EIGRP for both IPv4 and IPv6 on the same
router can become a complex task because configuration
takes place using different router configuration modes
 A newer configuration enables the configuration of EIGRP
for both IPv4 and IPv6 under a single configuration mode.
 EIGRP named configuration helps eliminate configuration
complexity that occurs when configuring EIGRP for both
IPv4 and IPv6
 EIGRP named configuration is available in Cisco IOS
Release 15.0(1)M and later releases.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 170
 Configuring Named EIGRP

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 171
 Configuring Named EIGRP (Previous Config)

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 172
 Address Families
 EIGRP named configuration mode uses the global
configuration command router eigrp virtual-instance-name.
 Both EIGRP for IPv4 and IPv6 can be configured within this
same mode.
 EIGRP supports multiple protocols and can carry
information about many different route types.
 Named EIGRP configuration organizes specific route types
under the same address family.
 IPv4 unicast and IPv6 unicast are two of the most
commonly used address families.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 173
 EIGRP for IPv4 Address Family

address-family ipv4 [ multicast ] [ unicast ] [ vrf vrf-name ]

autonomous-system as-number

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 174
 EIGRP for IPv4 Address Family
 The address-family command enables the IPv4 address
family and starts EIGRP for the defined autonomous
system.
 In IPv4 address family configuration mode, you can enable
EIGRP for specific interfaces by using the network
command, and you can define some other general
parameters such as router-id or eigrp stub.
 Unless specified otherwise, address family is by default
defined as unicast address family used the exchange
unicast routes.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 175
 EIGRP for IPv6 Address Family

address-family ipv6 [ unicast ] [ vrf vrf-name ] autonomous-system

as-number

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 176
 EIGRP for IPv6 Address Family
 IPv6 EIGRP neighbor relationship gets established as soon
as you define the IPv6 address family.
 All IPv6-enabled interfaces are automatically included in the
EIGRP for IPv6 process.
 The IPv6 address family configuration will show up in the
running configuration as a unicast address family by default.
 You can configure or remove individual interfaces from the
EIGRP for IPv6 process by using the af-interface interface-
type interface number command in address family
configuration mode

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 177
 EIGRP for IPv6 Address Family

 af-interface { default | interface-type interface number }

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 178
 Disabling EIGRP for IPv6 on an Interface

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 179
 Named EIGRP Final Config

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 180
 EIGRP Summarization in Named Configuration

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 181
 Configuring IPv6 Passive Interfaces

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 182
 Named EIGRP Configuration Modes
Three different configuration modes:
 Address family configuration mode
• General EIGRP configuration commands for selected address family are entered
under address family configuration mode. Here you can configure the router ID
and define network statements and also configure router as an EIGRP stub.
• Address family configuration mode gives you access to two additional
configuration modes: address family interface configuration mode and address
family topology configuration mode.
 Address family interface configuration mode
• You should use address family interface configuration mode for all those
commands that you have previously configured directly under interfaces. Most
common options are setting summarization with the summary-address command
or marking interfaces as passive using passive-interface command. You can also
modify default hello and hold-time timers.
 Address family topology configuration mode
• Address family topology configuration mode gathers all configuration options that
directly impact the EIGRP topology table. Here you can set load-balancing
parameters such as variance and maximum-paths, or you can redistribute static
routes using the redistribute command.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 183
 Address Family Configuration Mode

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 184
 Address Family Interface Configuration Mode

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 185
 Address Family Topology Configuration Mode

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 186
 Chapter 2 Summary
 EIGRP is an advanced distance vector protocol.
 EIGRP uses RTP for reliable, guaranteed delivery of packets.
 Hello and hold timers can be adapted to influence network convergence.
 IGRP adapts well to various technologies such as Frame Relay, Layer 3 MPLS VPN,
and Layer 2 MPLS VPN.
 EIGRP uses hello, update, query, reply, and acknowledgment packets.
 EIGRP uses a composite metric that is by default based on bandwidth and delay.
 Reported distance is the metric value reported by the neighboring router.
 Feasible distance is the lowest distance to a destination from the perspective of the
local router.
 Alternative path must satisfy the feasibility condition to become a feasible successor.
 The reported distance of an alternate path must be less than the feasible distance.
 When a route is lost and no feasible successor is available, queries are sent to all
neighboring routers on all interfaces.
 EIGRP stub configuration improves network stability and reduces resource
utilization.
 Summarization decreases the size of the IP routing table and optimizes exchange of
routing information.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 187
 Chapter 2 Summary
 EIGRP performs equal-cost load balancing.
 To support unequal-cost load balancing, a variance parameter must be
configured.
 EIGRP for IPv6 uses IPv6 link-local addresses to form neighbor
relationships.
 EIGRP for IPv6 supports only manual prefix summarization.
 To configure EIGRP for IPv6, you must define the routing process and
configure interfaces participating in EIGRP routing.
 EIGRP for IPv6 verification commands have similar syntax to EIGRP for
IPv4 commands.
 Classic EIGRP configuration is divided over different configuration modes.
 Named EIGRP configuration gathers EIGRP configuration in one place.
 Named EIGRP configuration unifies configuration commands for different
address families.
 Named EIGRP configuration is hierarchically organized using three address
family configuration modes.
 The same verification commands for classic EIGRP are used to verify
named EIGRP configuration.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 188
 Chapter 2 Labs
 CCNPv7_ROUTE_Lab2-1_EIGRP-Load-Balancing
 CCNPv7_ROUTE_Lab2-2_EIGRP-Stub-Routing
 CCNPv7_ROUTE_Lab2-3_EIGRP-IPv6
 CCNPv7_ROUTE_Lab2-4_EIGRP-Named-Configuration

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 189
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 190
 Acknowledgment
• Some of images and texts are from Implementing Cisco IP Routing (ROUTE)
Foundation Learning Guide by Diane Teare, Bob Vachon and Rick Graziani
(1587204568)
• Copyright © 2015 – 2016 Cisco Systems, Inc.
• Special Thanks to Bruno Silva

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 191
 Chapter 3:
Open Short Path First

CCNP ROUTE: Implementing IP Routing

ROUTE v7 Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 192
 Chapter 3 Objectives
 Basic OSPF Configuration and OSPF Adjacencies
 How OSPF Builds the Routing Table
 Configuration of Summarization and Stub Areas in OSPF
 Configuration of OSPFv3 for IPv6 and IPv4

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 193
 Establishing
OSPF Neighbor
Relationships

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 194
 Establishing OSPF Neighbor Relationships
 Explain why would you choose OSPF over other routing
protocols
 Describe basic operation steps with link-state protocols
 Describe area and router types in OSPF
 Explain what the design limitations of OSPF are
 List and describe OSPF message types
 Describe OSPF neighbor relationship over point-to-point link
 Describe OSPF neighbor relationship behavior on MPLS VPN
 Describe OSPF neighbor relationship behavior over L2 MPLS
VPN
 List and describe OSPF neighbor states
 List and describe OSPF network types
 Configure passive interfaces

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 195
 OSPF Features
 OSPF was developed by the Internet Engineering Task
Force (IETF) to overcome the limitations of distance vector
routing protocols.
 One of the main reasons why OSPF is largely deployed in
today’s enterprise networks is the fact that it is an open
standard;
 OSPF offers a large level of scalability and fast
convergence.
 Despite its relatively simple configuration in small and
medium-size networks, OSPF implementation and
troubleshooting in large-scale networks can at times be
challenging.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 196
 OSPF Features
Independent transport
 OSPF works on top of IP and uses protocol number 89.
 It does not rely on the functions of the transport layer protocols
TCP or UDP.
Efficient use of updates
 When an OSPF router first discovers a new neighbor, it sends a
full update with all known link-state information.
 All routers within an OSPF area must have identical and
synchronized link-state information in their OSPF ink-state
databases.
 When an OSPF network is in a converged state and a new link
comes up or a link becomes unavailable, an OSPF router sends
only a partial update to all its neighbors.
 This update will then be flooded to all OSPF routers within an
area.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 197
 OSPF Features
Metric
 OSPF uses a metric that is based on the cumulative costs of all
outgoing interfaces from source to destination. The interface cost is
inversely proportional to the interface bandwidth and can be also set up
explicitly.
Update destination address
 OSPF uses multicast and unicast, rather than broadcast, for sending
messages.
 The IPv4 multicast addresses used for OSPF are 224.0.0.5 to send
information to all OSPF routers and 224.0.0.6 to send information to
DR/BDR routers.
 The IPv6 multicast addresses are FF02::5 for all OSPFv3 routers and
FF02::6 for all DR/BDR routers.
 If the underlying network does not have broadcast capabilities, you must
establish OSPF neighbor relationships using a unicast address.
 For IPv6, this address will be a link-local IPv6 address.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 198
 OSPF Features
VLSM support
 OSPF is a classless routing protocol. It supports variable-
length subnet masking (VLSM) and discontinuous networks.
 It carries subnet mask information in the routing updates.
Manual route summarization
 You can manually summarize OSPF interarea routes at the
Area Border Router (ABR), and you have the possibility to
summarize OSPF external routes at the Autonomous
System Boundary Router (ASBR).
 OSPF does not know the concept of auto-summarization.
Authentication
 OSPF supports clear-text, MD5, and SHA authentication.
Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 199
 OSPF Operation Overview

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 200
 OSPF Operation Overview
1. Establish neighbor adjacencies
 OSPF-enabled routers must form adjacencies with their
neighbor before they can share information with that
neighbor.
 An OSPF enabled router sends Hello packets out all OSPF-
enabled interfaces to determine whether neighbors are
present on those links.
 If a neighbor is present, the OSPF enabled router attempts
to establish a neighbor adjacency with that neighbor.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 201
 OSPF Operation Overview
2. Exchange link-state advertisements
 After adjacencies are established, routers then exchange link-
state advertisements (LSAs).
 LSAs contain the state and cost of each directly connected link.
 Routers flood their LSAs to adjacent neighbors. Adjacent
neighbors receiving the LSA immediately flood the LSA to other
directly connected neighbors, until all routers in the area have all
LSAs.
3. Build the topology table
 After the LSAs are received, OSPF-enabled routers build the
topology table (LSDB) based on the received LSAs.
 This database eventually holds all the information about the
topology of the network.
 It is important that all routers in the area have the same
information in their LSDBs.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 202
 OSPF Operation Overview
4. Execute the SPF algorithm
 Routers then execute the SPF algorithm. The SPF
algorithm creates the SPF tree.
5. Build the routing table
 From the SPF tree, the best paths are inserted into the
routing table. Routing decisions are made based on the
entries in the routing table.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 203
 Hierarchical Structure of OSPF

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 204
 Hierarchical Structure of OSPF
OSPF uses a two-layer area hierarchy:
Backbone area, transit area or area 0
 Two principal requirements for the backbone area are that it
must connect to all other nonbackbone areas and this area
must be always contiguous; it is not allowed to have split up
the backbone area.
 Generally, end users are not found within a backbone area.
Nonbackbone area
 The primary function of this area is to connect end users
and resources. Nonbackbone areas are usually set up
according to functional or geographic groupings.
 Traffic between different nonbackbone areas must always
pass through the backbone area.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 205
 Hierarchical Structure of OSPF
 In the multi-area topology there are special commonly OSPF terms:
ABR
 A router that has interfaces connected to at least two different OSPF
areas, including the backbone area. ABRs contain LSDB information for
each area, make route calculation for each area and advertise routing
information between areas.
ASBR
 ASBR is a router that has at least one of its interfaces connected to an
OSPF area and at least one of its interfaces connected to an external
non-OSPF domain.
Internal router
 A router that has all its interfaces connected to only one OSPF area.
Backbone router
 A router that has at least one interface connected to the backbone area.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 206
 OSPF Message Types
 Type 1: Hello packet: Hello packets are used to discover,
build, and maintain OSPF neighbor adjacencies.
 Type 2: Database Description (DBD) packet: When the
OSPF neighbor adjacency is already established, a DBD
packet is used to describe LSDB so that routers can
compare whether databases are in sync.
 Type 3: Link-State Request (LSR) packet : The router will
send an LSR packet to inform OSPF neighbors to send the
most recent version of the missing LSAs.
 Type 4: Link-State Update (LSU) packet : LSU packets
are used for the flooding of LSAs and sending LSA
responses to LSR packets.
 Type 5: Link-State Acknowledgment (LSAck) packet :
LSAcks are used to make flooding of LSAs reliable.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 207
 Basic OSPF Configuration

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 208
 Basic OSPF Configuration

 To enable the OSPF process on the router, use the router

ospf process-id command.
 Process ID numbers between neighbors do not need to
match for the routers to establish an OSPF adjacency.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 209
 Basic OSPF Configuration

 To establish OSPF full adjacency, two neighbor routers

must be in the same area.
 Any individual interface can only be attached to a single
area.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 210
 Configuration of OSPF Router IDs
 To choose the OSPF router ID at the time of OSPF process
initialization, the router uses the following criteria:
1. Use the router ID specified in the router-id ip-address command.
2. Use the highest IPv4 address of all active loopback interfaces on
the router.
3. Use the highest IPv4 address among all active nonloopback
interfaces.
 At least one primary IPv4 address on an interface in the
up/up state must be configured for a router to be able to
choose router ID; otherwise, an error message is logged,
and the OSPF process does not start.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 211
 Clearing the OSPF Processes
 OSPF routing process can be cleared for the manually
configured router ID to take effect.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 212
 OSPF Router ID Criteria
1. Use the router ID specified in the router-id ip-address
command.
• You can configure an arbitrary value in the IPv4 address format, but
this value must be unique.
• If the IPv4 address specified with the router-id command overlaps
with the router ID of another already-active OSPF process, the
router-id command fails.
2. Use the highest IPv4 address of all active loopback
interfaces on the router.
3. Use the highest IPv4 address among all active
nonloopback interfaces.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 213
 Verifying the Router IDs

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 214
 Verifying OSPF Neighborships

 Neighbor ID : Represents neighbor router ID.

 Priority : Priority on the neighbor interface used for the DR/BDR
election.
 State : OSPF neighbor establishment process
 Dead Time : Represents value of the dead timer
 Address : Primary IPv4 address of the neighbor router.
 Interface : Local interface over which an OSPF neighbor relationship is
established.
Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 215
 Verifying the OSPF-Enabled Interfaces

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 216
 Verifying the OSPF Routes

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 217
 OSPF Routes

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 218
 OSPF Adjacency Establishment Steps
1. Down state - the initial state of a neighbor conversation that indicates that no
Hello’s have been heard from the neighbor.
2. Init state - a router receives a Hello from the neighbor but has not yet seen its
own router ID in the neighbor Hello packet
3. 2-Way state - When the router sees its own router ID in the Hello packet received
from the neighbor
4. ExStart state - In the DBD exchange process, the router with the higher router ID
will become master, and it will be the only router that can increment sequence
numbers. With master/slave selection complete, database exchange can start
5. Exchange state - To describe the content of the database, one or multiple DBD
packets may be exchanged. A router compares the content of its own Database
Summary list with the list received from the neighbor, and if there are differences,
it adds missing LSAs to the Link State Request list.
6. Loading state - LSR packet is sent to the neighbor requesting full content of the
missing LSAs from the LS Request list
7. Full state - Finally, when neighbors have a complete version of the LSDB, which
means that databases on the routers are synchronized and that neighbors are
fully adjacent.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 219
 Optimizing OSPF Adjacency Behavior

 As the number of routers on the segment grows, the

number of OSPF adjacencies increases exponentially.
Every router must synchronize its OSPF database with
every other router, and in the case of a large number of
routers, this leads to inefficiency.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 220
 OSPF Adjacencies on Multiaccess Networks

 The routers on the multiaccess segment elect a designated

router (DR) and backup designated router (BDR), which
centralizes communications for all routers connected to the
segment.
 The DR and BDR improve network functioning in the
following ways:
• Reducing routing update traffic: The DR and BDR act as a central
point of contact for link-state information exchange on a multiaccess
network; therefore, each router must establish a full adjacency with
the DR and the BDR only.
• Managing link-state synchronization: The DR and BDR ensure that
the other routers on the network have the same link-state information
about the common segment.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 221
 OSPF Adjacencies on Multiaccess Networks

 Only LSAs are sent to the DR/BDR. The normal routing of

packets on the segment will go to the best next-hop router.
 When the DR is operating, the BDR does not perform any
DR functions. Instead, the BDR receives all the information,
but the DR performs the LSA forwarding and LSDB
synchronization tasks.
 The BDR performs the DR tasks only if the DR fails.
 When the DR fails, the BDR automatically becomes the
new DR, and a new BDR election occurs.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 222
 Neighbor Status

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 223
 DR/BDR Election Process
 The DR/BDR election process takes place on broadcast and
NBMA networks.
 Routers send OSPF Hello packets to discover which OSPF
neighbors are active on the common Ethernet segment.
 Once OSPF neighbors are in the 2-Way state, the DR/BDR
election process begins.
 The OSPF Hello packet contains three specific fields used for the
DR/BDR election:
• Designated Router, Backup Designated Router, and Router Priority.
 From all routers listed in this fields, the router with the highest
priority becomes the DR, and the one with the next highest
priority becomes the BDR.
 If the priority values are equal, the router with the highest OSPF
router ID becomes the DR, and the one with the next highest
OSPF router ID becomes the BDR.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 224
 DR/BDR Election Process
 On the multiaccess broadcast networks, routers use multicast
destination IPv4 address 224.0.0.6 to communicate with the DR
, and the DR uses multicast destination IPv4 address 224.0.0.5
to communicate with all other non-DR routers
 On NBMA networks, the DR and adjacent routers communicate
using unicast addresses.
 The DR/BDR election process not only occurs when the network
first becomes active but also when the DR becomes unavailable.
 In this case, the BDR will immediately become the DR, and the
election of the new BDR starts.
 On the multi-access segment, it is normal behavior that the router
in DROTHER status is fully adjacent with DR/BDR and in 2-WAY
state with all other DROTHER routers present on the segment.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 225
 Using OSPF Priority in the DR/BDR Election

Every broadcast and NBMA OSPF-enabled interface is assigned a

priority value between 0 and 255. By default, the OSPF interface
priority is 1 and can be manually changed by using the ip ospf
priority interface command.
 The router with the highest priority value is elected as the DR.
 The router with the second-highest priority value is the BDR.
 In case of a tie where two routers have the same priority value,
router ID is used as the tiebreaker. The router with the highest
router ID becomes the DR. The router with the second-highest
router ID becomes the BDR.
 A router with a priority that is set to 0 cannot become the DR or
BDR. A router that is not the DR or BDR is called a DROTHER.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 226
 Configuring the OSPF Priority on an Interface

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 227
 Verifying OSPF Neighbor Status

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 228
 OSPF Behavior in NBMA Hub-and-Spoke
Topology
 OSPF treats NBMA
environments like any
other broadcast media
environment, such as
Ethernet; however,
NBMA clouds are
usually built as hub-
and-spoke topologies
using private virtual
circuits (PVCs) or
switched virtual circuits
(SVCs)

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 229
 OSPF Behavior in NBMA Hub-and-Spoke
Topology
 In these cases, the physical topology does not provide
multiaccess capability, on which OSPF relies. In a hub-and-
spoke NBMA environment, you will need to have the hub
router acting as the DR and spoke routers acting as the
DROTHER routers. On the spoke router interfaces, you
want to configure an OSPF priority value of 0 so that the
spoke routers never participate in the DR election.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 230
 The Importance of MTU
 If neighbors have a mismatched IPv4 MTU configured, they
will not be able to form full OSPF adjacency.
 Mismatched neighbors will stay in ExStart state

 By default, the IPv6 MTU must also match between

OSPFv3 neighbors. However, you can override this by
using the ospfv3 mtu-ignore interface command.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 231
 Manipulating OSPF Timers
 Similar to EIGRP, OSPF uses two timers to check neighbor
reachability: the hello and dead intervals.
 OSPF requires that both hello and dead timers be identical
for all routers on the segment to become OSPF neighbors.
 The default value of the OSPF hello timer on multi-access
broadcast and point-to-point links is 10 seconds, and is 40
seconds on all other network types, including NBMA.
 When you configure the hello interval, the default value of
the dead interval is automatically adjusted to four times the
hello interval.
 For broadcast and point-to-point links, it is 30 seconds, and
for all other OSPF network types, it is 120 seconds.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 232
 Examining the Hello/Dead Timers

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 233
 Modifying the Hello and Dead Intervals

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 234
 OSPF Relationship over Point-to-Point Links

 The routers dynamically detects its neighboring routers by

multicasting its Hello packets to all OSPF routers, using the
224.0.0.5 address.
 No DR or BDR election is performed
 The default OSPF hello and dead timers on point-to-point
links are 10 seconds and 40 seconds, respectively.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 235
 OSPF Neighbor Relationship over MPLS

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 236
 OSPF Neighbor States

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 237
  Down: No information has been received on the segment.
 Init: The interface has detected a Hello packet coming from a
neighbor, but bidirectional
 2-Way: There is bidirectional communication with a neighbor.
The router has seen itself in the Hello packets coming from a
neighbor
 ExStart: Routers are trying to establish the initial sequence
number that is going to be used in the information exchange
packets.
 Exchange: Routers will describe their entire LSDB by sending
database description (DBD) packets.
 Loading: In this state, routers are finalizing the information
exchange.
 Full: In this state, adjacency is complete.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 238
 OSPF Network Types

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 239
 OSPF Network Types
 Point-to-point: Routers use multicast to dynamically
discover neighbors. There is no DR/BDR electio. It is a
default OSPF network type for serial links and point-to-point
Frame Relay subinterfaces.
 Broadcast: Multicast is used to dynamically discover
neighbors. The DR and BDR are elected. It is a default
OSPF network type for Ethernet links.
 Nonbroadcast: Used on networks that interconnect more
than two routers but without broadcast capability. Neighbors
must be statically configured, followed by DR/BDR election.
This network type is the default for all physical interfaces
and multipoint subinterfaces using Frame Relay
encapsulation.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 240
 OSPF Network Types
 Point-to-multipoint: OSPF treats this network type as a
logical collection of point-to- point links even though all
interfaces belong to the common IP subnet. Every interface
IP address will appear in the routing table of the neighbors
as a host /32 route. Neighbors are discovered dynamically
using multicast. No DR/BDR election occurs.
 Point-to-multipoint nonbroadcast: Cisco extension that
has the same characteristics as point-to-multipoint type
except for the fact that neighbors are not discovered
dynamically. Neighbors must be statically defined, and
unicast is used for communication.
 Loopback: Default network type on loopback interfaces.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 241
 Configuring Passive Interfaces

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 242
 Building the Link-
State Database

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 243
 Building the Link-State Database
 List and describe different LSA types
 Describe how OSPF LSAs are also reflooded at periodic
intervals
 Describe the exchange of information in a network without a
designated router
 Describe the exchange of information in a network with a
designated router
 Explain when SPF algorithms occur
 Describe how the cost of intra-area routes is calculated
 Describe how the cost of interarea routes is calculated
 Describe rules selecting between intra-area and interarea
routes
Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 244
 OSPF LSA Types

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 245
 OSPF LSA Types
 Type 1, Router LSA: Every router generates router link advertisements for each
area to which it belongs. Router link advertisements describe the state of the router
links to the area and are flooded only within that particular area. The link-state ID of
the type 1 LSA is the originating router ID.
 Type 2, Network LSA: DRs generate network link advertisements for multi-access
networks. Network link advertisements describe the set of routers that are attached
to a particular multiaccess network. Network link advertisements are flooded in the
area that contains the network. The link-state ID of the type 2 LSA is the IP interface
address of the DR.
 Type 3, Summary LSA: An ABR takes the information that it learned in one area
and describes and summarizes it for another area in the summary link
advertisement. This summarization is not on by default. The link-state ID of the type
3 LSA is the destination network number.
 Type 4, ASBR Summary LSA: The ASBR summary link advertisement informs the
rest of the OSPF domain how to get to the ASBR. The link-state ID includes the
router ID of the described ASBR.
 Type 5, Autonomous System LSA: Autonomous system external link
advertisements, which are generated by ASBRs, describe routes to destinations that
are external to the autonomous system. They get flooded everywhere, except into
special areas. The link-state ID of the type 5 LSA is the external network number.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 246
 Other LSA Types
 Type 6: Specialized LSAs that are used in multicast OSPF
applications
 Type 7: Used in special area type NSSA for external routes
 Type 8, 9: Used in OSPFv3 for link-local addresses and
intra-area prefix
 Type 10, 11: Generic LSAs, also called opaque , which
allow future extensions of OSPF

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 247
 Examining the OSPF Link-State Database

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 248
 Routing Table

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 249
 OSPF LSDB

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 250
 Type 1 LSA Details

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 251
 Locally Generated Type 1 LSAs

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 252
 Type 1 LSA
 Type 1 LSAs are generated by every router and flooded
within the area.
 They describe the state of the router links in that area.
 When generating a type 1 LSA, the router uses its own
router ID as the value of LSID.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 253
 OSPF Type 2 Network LSA

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 254
 OSPF Type 2 Network LSA

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 255
 Type 2 LSA
 The DR of the network is responsible for advertising the
network LSA
 A type 2 network LSA lists each of the attached routers that
make up the transit network, including the DR itself, and the
subnet mask that is used on the link.
 The type 2 LSA then floods to all routers within the transit
network area
 Type 2 LSAs never cross an area boundary.
 The LSID for a network LSA is the IP interface address of
the DR that advertises it

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 256
 OSPF Type 3 Summary LSA

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 257
 OSPF Type 3 Summary LSA

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 258
 Type 3 LSA
 The ABRs generate type 3 summary LSAs to describe any
networks that are owned by an area to the rest of the areas in
the OSPF autonomous system
 Summary LSAs are flooded throughout a single area only, but
are regenerated by ABRs to flood into other areas.
 By default, OSPF does not automatically summarize groups of
contiguous subnets.
 As a best practice, you can use manual route summarization
on ABRs to limit the amount of information that is exchanged
between the areas.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 259
 OSPF Type 4 ASBR Summary LSA

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 260
 Type 4 LSA
 A type 4 LSA identifies the ASBR and provides a route to
the ASBR.
 The link-state ID is set to the ASBR router ID.
 All traffic that is destined to an external autonomous system
requires routing table knowledge of the ASBR that
originated the external routes.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 261
 OSPF Type 5 External LSA

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 262
 Type 5 LSA
 The LSID is the external network number.
 Information described in the type 5 LSA combined with the
information received in the type 4 LSA, which describes the
ASBR capability of router R3. This way, R4 learns how to
reach the external networks.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 263
 Periodic OSPF Database Changes
 Although OSPF does not refresh routing updates
periodically, it does reflood LSAs every 30 minutes.
 Each LSA includes the link-state age variable, which counts
the age of the LSA packet
 In a normally operating network, you will not see the age
variable with values higher than 1800 seconds.
 When an LSA reaches a max age of 60 minutes in the
LSDB, it is removed from the LSDB, and the router will
perform a new SPF calculation
 The router floods the LSA to other routers, informing them
to remove the LSA as well.
 Because this update is only used to refresh the LSDB, it is
sometimes called a paranoid update

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 264
 Exchanging and Synchronizing LSDBs

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 265
 Exchanging and Synchronizing LSDBs

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 266
 Synchronizing the LSDB on Multiaccess
Networks
 When routers form a neighbor relationship on a multiaccess
segment, the DR and BDR election takes place when
routers are in the 2-Way state.
 The router with a highest OSPF priority, or highest router ID
in case of a tie, is elected as a DR. Similarly, the router with
the second highest priority or router ID becomes the BDR.
 While the DR and BDR proceed in establishing the
neighborship with all routers on the segment, other routers
establish full adjacency only with the DR and BDR.
 The neighbor state of other neighbors stays in the 2-Way
state.
 Non-DR router exchange their databases only with the DR.
 The DR takes care to synchronize any new or changed
LSAs with the rest of the routers on the segment.
Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 267
 Synchronizing the LSDB on Multiaccess
Networks

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 268
 Running the SPF Algorithm
 Every time there is a change in the network topology, OSPF
needs to reevaluate its shortest path calculations. OSPF
uses SPF to determine best paths toward destinations.
 The network topology that is described in the LSDB is used
as an input for calculation.
 Network topology change can influence best path selection;
therefore, routers must rerun SPF each time there is an
intra-area topology change.
 Interarea changes, which are described in type 3 LSAs, do
not trigger the SPF recalculation because the input
information for the best path calculation remains
unchanged.
 The router determines the best paths for interarea routes
based on the calculation of the best path toward the ABR.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 269
 Verifying OSPF Frequency of the SPF
Algorithm

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 270
 OSPF Best Path Calculation
 Once LSDBs are synchronized among OSPF neighbors, each router
needs to determine on its own the best paths over the network topology.
 SPF it compares total costs of specific paths against each other. The
paths with the lowest costs are selected as the best paths.
 OSPF cost is computed automatically for each interface that is assigned
into an OSPF process, using the following formula:
Cost = Reference bandwidth / Interface bandwidth
 The cost value is a 16-bit positive number between 1 and 65,535, where
a lower value is a more desirable metric.
 Reference bandwidth is set to 100 Mbps by default.
 On high-bandwidth links (100 Mbps and more), automatic cost
assignment no longer works
 “On these links, OSPF costs must be set manually on each interface.”
 The OSPF cost is recomputed after every bandwidth change, and the
Dijkstra’s algorithm determines the best path by adding all link costs
along a path.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 271
 Examining the Interface Bandwidth and OSPF
Cost

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 272
 Default OSPF Costs

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 273
 Modifying the Reference Bandwidth

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 274
 Changing the Interface Bandwidth and OSPF
Cost

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 275
 Calculating the Cost of Intra-Area Routes
 To calculate the cost of intra-area routes, the router first
analyzes OSPF database and identifies all subnets within
its area.
 For each possible route, OSPF calculates the cost to reach
the destination by summing up the individual interface
costs.
 For each subnet, the route with the lowest total cost is
selected as the best route.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 276
 Calculating the Cost of Interarea Routes
 The internal OSPF router within an area receives only
summarized info about interarea routes.
 As a result, the cost of an interarea route cannot be calculated
the same way as for the intra-area routes.
 When ABRs propagate information about the interarea routes
with type 3 LSAs, they include their lowest cost to reach a
specific subnet in the advertisement.
 The internal router adds its cost to reach a specific ABR to the
cost announced in a type 3 LSA.
 Then it selects the route with the lowest total cost as the best
route.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 277
 Selecting Between Intra-Area and Interarea
Routes
 To eliminate the single point of failure on area borders, at
least two ABRs are used in most networks.
 As a result, ABR can learn about a specific subnet from
internal routers and also from the other ABR.
 ABR can learn an intra-area route and also an interarea
route for the same destination.
 Even though the interarea route could have lower cost to
the specific subnet, the intra-area path is always the
preferred choice.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 278
 Optimizing OSPF
Behavior

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 279
 Optimizing OSPF Behavior

 Describe the properties of OSPF route summarization

 Describe benefits of route summarization in OSPF
 Configure summarization on ABR
 Configure summarization on ASBR
 Configure the cost of OSPF default route
 Describe how you can use default routes and stub routing
to direct traffic toward the Internet
 Describe the NSSA areas
 Configure the default route using the default-information
originate command

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 280
 OSPF Route Summarization
 Route summarization is a key to scalability in OSPF.
 Route summarization helps solve two major problems:
• Large routing tables
• Frequent LSA flooding throughout the autonomous system
 Every time that a route disappears in one area, routers in
other areas also get involved in shortest-path calculation.
 To reduce the size of the area database, you can configure
summarization on an area boundary or autonomous system
boundary.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 281
 OSPF Route Summarization Process
 Normally, type 1 and type 2 LSAs are generated inside
each area and translated into type 3 LSAs in other areas.
 With route summarization, the ABRs or ASBRs consolidate
multiple routes into a single advertisement. ABRs
summarize type 3 LSAs, and ASBRs summarize type 5
LSAs.
 Instead of advertising many specific prefixes, advertise only
one summary prefix.
 Route summarization requires a good addressing plan—an
assignment of subnets and addresses that is based on the
OSPF area structure and lends itself to aggregation at the
OSPF area borders.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 282
 Benefits of Route Summarization
 Route summarization directly affects the amount of bandwidth,
CPU power, and memory resources that the OSPF routing
process consumes.
 With route summarization, only the summarized routes are
propagated into the backbone (area 0) increasing the stability of
the network
 The routes being advertised in the type 3 LSAs are appropriately
added to or deleted from the router’s routing table, but an SPF
calculation is not done.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 283
 OSPF Route Summarization
 OSPF offers two methods of route summarization:
• Summarization of internal routes performed on the ABRs
• Summarization of external routes performed on the ASBRs

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 284
 ABR’s Summarization

 area area-id range ip-address mask [ advertise | not-advertise ] [ cost cost ]

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 285
 Configuring OSPF Route Summarization

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 286
 Configuring OSPF Route Summarization

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 287
 Configuring OSPF Route Summarization

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 288
 Configuring OSPF Route Summarization

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 289
 Configuring Summarization on the ABR

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 290
 Configuring OSPF Route Summarization

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 291
 Configuring OSPF Route Summarization

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 292
 Configuring OSPF Route Summarization

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 293
 Configuring OSPF Route Summarization

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 294
 Summarization on ASBR’s

 summary-address {{ ip-address mask } | { prefix mask }} [ not-advertise ] [ tag tag ]

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 295
 OSPF Virtual Links
 OSPF’s two-tiered area hierarchy requires that if more than
one area is configured, one of the areas must be area 0, the
backbone area.
 All other areas must be directly connected to area 0, and
area 0 must be contiguous.
 OSPF expects all nonbackbone areas to inject routes into
the backbone, so that the routes can be distributed to other
areas.
 A virtual link is a link that allows discontiguous area 0s to be
connected, or a disconnected area to be connected to area
0, via a transit area.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 296
 OSPF Virtual Links

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 297
 Virtual Links Issues
 The OSPF virtual link feature should be used only in very
specific cases, for temporary connections or for backup
after a failure.
 Virtual links should not be used as a primary backbone
design feature.
 The virtual link relies on the stability of the underlying intra-
area routing.
 Virtual links cannot go through more than one area, nor
through stub areas.
 If a virtual link needs to be attached to the backbone across
two nonbackbone areas, two virtual links are required, one
per area.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 298
 Virtual Links Configuration Issues
 The OSPF database treats the virtual link between ABR1
and ABR2 as a direct link.
 For greater stability, loopback interfaces are used as router
IDs, and virtual links are created using these loopback
addresses.
 The hello protocol works over virtual links as it does over
standard links, in 10-second intervals.
 An LSA usually refreshes every 30 minutes. However, LSAs
learned through a virtual link have the DoNotAge (DNA)
option set so that the LSA does not age out. This DNA
technique is required to prevent excessive flooding over the
virtual link.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 299
 Configuring OSPF Virtual Links

area area-id virtual-link router-id [ authentication [ message-digest |

null ]][ hello-interval seconds ] [ retransmit-interval seconds ] [
transmitdelay seconds ] [ dead-interval seconds ] [[ authentication-key
key ] | [ message-digest-key key-id md5 key ]]

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 300
 Configuring OSPF Virtual Links

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 301
 Configuring OSPF Virtual Links

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 302
 OSPF Stub Areas
 The stub and totally stubby areas are deployed to reduce
the size of the OSPF database and routing table:
• Stub area: This area type does not accept information about routes
external to the autonomous system, such as routes from non-OSPF
sources. If routers need to route to networks outside the autonomous
system, they use a default route, indicated as 0.0.0.0. Stub areas
cannot contain ASBRs (except that the ABRs may also be ASBRs).
The stub area does not accept external routes.
• Totally stubby area: This Cisco proprietary area type does not
accept external autonomous system routes or summary routes from
other areas internal to the autonomous system. If a router needs to
send a packet to a network external to the area, it sends the packet
using a default route. Totally stubby areas cannot contain ASBRs
(except that the ABRs may also be ASBRs). A totally stubby area
does not accept external or interarea routes.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 303
 Configuring OSPF Stub Areas

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 304
 Configuring OSPF Stub Areas

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 305
 Configuring OSPF Stub Areas

 Configuring a stub area reduces the size of the LSDB inside the area,
resulting in reduced memory requirements for routers in that area. External
network LSAs (type 5), such as those that are redistributed from other
routing protocols into OSPF, are not permitted to flood into a stub area.
 The area stub router configuration mode command is used to define an
area as a stub area. Each router in the stub area must be configured with
the area stub command. The
 Hello packets that are exchanged between OSPF routers contain a stub
area flag that must match on neighboring routers. Until the area 1 stub
command is enabled on R2 in this scenario, the adjacency between R1 and
R2 will be down.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 306
 Configuring OSPF Stub Areas

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 307
 Propagating a Default Route Using OSPF

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 308
 OSPF Totally Stubby Areas

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 309
 OSPF Totally Stubby Areas

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 310
 Cost of the Default Route in a Stub Area
 By default, the ABR of a stub area will advertise a default
route with a cost of 1.
 You can change the cost of the default route by using the
area default-cost command.
 The default-cost option provides the metric for the summary
default route that is generated by the ABR into the stub
area.
area area-id default-cost cost

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 311
 Cost of the Default Route in a Stub Area
 The option of tuning the cost of the default route in the stub
area is useful in stub areas with redundant exit points to the
backbone area

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 312
 The default-information originate Command

 default-information originate [ always ] [ metric metric-

value ] [ metric-type typevalue ] [ route-map map-name ]

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 313
 Other Stubby Area Types
 The NSSA is a nonproprietary extension of the existing stub
area feature that allows the injection of external routes in a
limited fashion into the stub area.

 The area nssa router configuration mode command is used

to define each router in the NSSA area as not-so-stubby
 The area nssa command with the no-summary keyword is
used to define the ABR as totally not-so-stubby.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 314
 OSPFv3

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 315
 OSPFv3
 Implement OSPFv3 in a dual-stack (IPv4/IPv6) environment
 Configure external route summarization and load balancing
in OSPFv3
 Explain the limitations and where you need to be careful
when configuring OSPFv3

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 316
 Configuring OSPFv3

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 317
 Configuring OSPFv3
 Cisco IOS routers offer two OSPF configuration methods for
IPv6:
 Using the traditional ipv6 router ospf global configuration
command
 Using the new-style router ospfv3 global configuration
command

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 318
 Configuring OSPFv3
 OSPFv3 is the IPv6-capable version of the OSPF routing
protocol. It is a rewrite of the OSPF protocol to support
IPv6, although the foundation remains the same as in IPv4
and OSPFv2.
 The OSPFv3 metric is still based on interface cost.
 The packet types and neighbor discovery mechanisms are
the same in OSPFv3 as they are for OSPFv2.
 OSPFv3 also supports the same interface types, including
broadcast, point-to-point, point-tomultipoint,
 NBMA, and virtual links.
 LSAs are still flooded throughout an OSPF domain, and
many of the LSA types are the same, though a few have
been renamed or newly created.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 319
 Enabling OSPFv3

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 320
 OSPFv3 Adjacencies and Routing Table

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 321
 Specifying the Neighbor on an NBMA Interface

 OSPF adjacencies over NBMA links require that IPv6

connectivity for both the link-local and the global addresses
is established. Depending on the transport network, this
may require mapping of IPv6 addresses to Layer 2 circuit
identifiers

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 322
 Specifying the Neighbor on an NBMA Interface

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 323
 OSPFv3 LSDB

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 324
 Renamed LSA
 Interarea prefix LSAs for ABRs (Type 3): Type 3 LSAs
advertise internal networks to routers in other areas
(interarea routes). Type 3 LSAs may represent a single
network or a set of networks summarized into one
advertisement. Only ABRs generate summary LSAs. In
OSPF for IPv6, addresses for these LSAs are expressed as
prefix/ prefix length instead of address and mask. The
default route is expressed as a prefix with length 0.
 Interarea router LSAs for ASBRs (Type 4): Type 4 LSAs
advertise the location of an ASBR. Routers that are trying to
reach an external network use these advertisements to
determine the best path to the next hop. ASBRs generate
Type 4 LSAs.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 325
 New LSA
 Link LSAs (Type 8): Type 8 LSAs have local-link flooding
scope and are never flooded beyond the link with which
they are associated. Link LSAs provide the link-local
address of the router to all other routers attached to the link.
They inform other routers attached to the link of a list of
IPv6 prefixes to associate with the link. In addition, they
allow the router to assert a collection of option bits to
associate with the network LSA that will be originated for
the link.
 Intra-area prefix LSAs (Type 9): A router can originate
multiple intra-area prefix LSAs for each router or transit
network, each with a unique link-state ID. The linkstate ID
for each intra-area prefix LSA describes its association to
either the router LSA or the network LSA. The link-state ID
also contains prefixes for stub and transit networks.
Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 326
 OSPFv3 for IPv4 and IPv6
 The newest OSPFv3 configuration approach utilizes a
single OSPFv3 process.
 It is capable of supporting IPv4 and IPv6 within a single
OSPFv3 process.
 OSPFv3 builds a single database with LSAs that carry IPv4
and IPv6 information.
 The OSPF adjacencies are established separately for each
address family.
 Settings that are specific to an address family (IPv4/IPv6)
are configured inside that address family router
configuration mode.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 327
 Configuring OSPFv3 Using the router ospfv3

 The address-family ipv6 unicast has been automatically

created on R1. Cisco IOS Software has parsed the previous
old-style OSPFv3 configuration and found that the OSPF
process was enabled only for IPv6.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 328
 OSPFv3 Old-Style OSPF Configuration
Commands

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 329
 OSPFv3 New-Style OSPF Configuration
Commands

 The preferred interface mode command for the new style

OSPFv3 configuration is the ospfv3 process-id
{ipv4|ipv6} area area-id command.
 It allows you to selectively activate the OSPFv3 process for
an address family (IPv4 or IPv6) on a given interface.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 330
 Enabling OSPFv3 for IPv4

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 331
 OSPFv3 Adjacencies for Both IPv4 and IPv6
Address Families

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 332
 OSPFv3 LSDB

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 333
 IPv4 Routing Table with OSPFv3 Routes

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 334
 OSPFv3 ipv6 Routing Table

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 335
 Configuring OSPFv3

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 336
 Area 2 Routers Configured as a Totally Stubby
Area

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 337
 OSPFv3 Summarization

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 338
 Configuring Advanced OSPFv3
 Configuring the summary-prefix Command on an ASBR

summary-prefix prefix [ not-advertise | tag tag-value ] [ nssa-only ]

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 339
 OSPFv3 Caveats
 The OSPFv3 address families feature is supported as of
Cisco IOS Release 15.1(3)S and Cisco IOS Release
15.2(1)T.
 Cisco devices that run software older than these releases
and third-party devices will not form neighbor relationships
with devices running the address family feature for the IPv4
address family because they do not set the address family
bit.
 Therefore, those devices will not participate in the IPv4
address family SPF calculations and will not install the IPv4
OSPFv3 routes in the IPv6 Routing Information Base (RIB).

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 340
 Chapter 3 Summary
 OSPF uses a two-layer hierarchical approach dividing networks
into a backbone area (area 0) and nonbackbone areas.
 For its operation, OSPF uses five packet types: Hello, DBD, LSR,
LSU, and LSAck.
 OSPF neighbors go through several different neighbor states
before adjacency results in Full state.
 OSPF elects DR/BDR routers on a multiaccess segment to
optimize exchange of information.
 The most common OSPF network types are point-to-point,
broadcast, nonbroadcast, and loopback.
 OSPF uses several different LSA types to describe the network
topology.
 LSAs are stored in an LSDB, which is synchronized with every
network change.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 341
 Chapter 3 Summary
 OSPF calculates interface costs based on default reference bandwidth and
interface bandwidth.
 Using SPF, OSPF determines the total lowest cost paths and selects them
as the best routes.
 Intra-area routes are always preferred over interarea routes.
 Route summarization improves CPU utilization, reduces LSA flooding, and
reduces routing table sizes.
 The area range command is used summarize at the ABR. The summary-
address command is sued to summarize at the ASBR.
 Default routes can be used in OSPF to prevent the need for specific route
to each destination network.
 OSPF uses the default-information originate command to inject a default
route.
 There are several OSPF area types: normal, backbone, stub, totally stubby,
NSSA, and totally stubby NSSA.
 Use the area area-id command to define an area as stubby.
 Use the area area-id stub command with the no-summary keyword only
on the ABR to define an area as totally stubby.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 342
 Chapter 3 Summary
 For stub areas, external routes are not visible in the routing table,
but are accessible via the intra-area default route.
 For totally stubby areas, interarea and external routes are not
visible in the routing table, but are accessible via the intra-area
default route.
 OSPFv3 for IPv6 supports the same basic mechanisms that
OSPFv2 for IPv4, including the use of areas to provide network
segmentation and LSAs to exchange routing updates.
 OSPFv3 features two new LSA types and has renamed two
traditional LSA types.
 OSPFv3 uses link-local addresses to source LSAs.
 OSPFv3 is enabled per-interface on Cisco routers.
 New-style OSPFv3 and traditional OSPFv3 for IPv6, configured
with ipv6 router ospf , can coexist in the network to provide IPv6
routing.

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 343
 Chapter 3 Labs
 CCNPv7_ROUTE_Lab3-1_OSPF-Virtual-Links
 CCNPv7_ROUTE_Lab3-2_Multi-Area-OSPF
 CCNPv7_ROUTE_Lab3-3_OSPFv3-Address-Families

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 344
Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 345
 Acknowledgment
• Some of images and texts are from Implementing Cisco IP Routing (ROUTE)
Foundation Learning Guide by Diane Teare, Bob Vachon and Rick Graziani
(1587204568)
• Copyright © 2015 – 2016 Cisco Systems, Inc.
• Special Thanks to Bruno Silva

Chapter 3
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 346
 Chapter 4:
Manipulating Routing
Updates

CCNP ROUTE: Implementing IP Routing

ROUTE v7 Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 347
 Chapter 4 Objectives
 This chapter covers the following topics:
 Using Multiple IP Routing Protocols on a Network
 Implementing Route Redistribution
 Controlling Routing Update Traffic

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 348
 Using Multiple IP
Routing Protocols
on a Network

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 349
 Using Multiple IP Routing Protocols on a
Network
 Describe the need for using more than one protocol in a
network
 Describe how routing protocols interact
 Describe solutions for operating in a multiple routing
protocol environment

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 350
 Using Multiple IP Routing Protocols on a
Network
 Simple routing protocols work well for simple networks, but
as networks grow and become more complex, it may be
necessary to change the routing protocols.
 Often, the transition between routing protocols takes place
gradually, so there are multiple routing protocols that are
operating in the network for variable lengths of time.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 351
 Why Run Multiple Routing Protocols?
 When migrating from an older Interior Gateway Protocol
(IGP) to a new IGP.
 The same applies to company mergers between companies
that are each using a different routing protocol.
 In mixed-router vendor environments.
 When the use of a new protocol is desired, but the old
routing protocol is needed for host systems
 When some departments do not want to upgrade their
routers to support a new routing protocol.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 352
 Running Multiple Routing Protocols
 When running multiple routing protocols, a router may learn
of a route from different routing sources. If a router learns of
a specific destination from two different routing domains,
the route with the lowest administrative distance would get
installed in routing table.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 353
 Administrative Distance
 The administrative distance is used to rate a routing
protocol’s believability (also called its trustworthiness). Each
routing protocol is prioritized in order from most to least
believable using an assigned value called the administrative
distance.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 354
 Multiple Routing Protocols Solutions
 Careful routing protocol design and traffic optimization
solutions should be implemented when supporting complex
multiprotocol networks.
 These solutions include the following:
• Summarization (Chapter 2 & 3)
• Redistribution between routing protocols
• Route filtering

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 355
 Implementing
Route
Redistribution

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 356
 Implementing Route Redistribution
 Describe the need for route redistribution
 Identify some considerations for route redistribution
 Describe how to configure and verify route redistribution
 Identify the different types of route redistribution

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 357
 Defining Route Redistribution
 Cisco routers allow internetworks using multiple routing
protocols to exchange routing information using the route
redistribution feature.
 Route redistribution is defined as the capability of boundary
routers connecting different routing domains to exchange
and advertise routing information between those routing
domains (autonomous systems).
 Redistribution shares routing information about routes that
the router has learned with other routing protocols.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 358
 Planning to Redistribute Routes
 Network administrators must manage redistribution carefully
because it can lead to routing loops, which negatively affect an
internetwork.
 Different routing protocols have different requirements and
capabilities, so it is important for network administrators to create
a detailed plan before making any routing protocol changes.
 An accurate topology map of the network and an inventory of all
network devices are critical for success.
 To have a scalable solution and limit the amount of routing
update traffic, the redistribution process must selectively insert
the routes that are learned.
 When a router redistributes routes, it only propagates routes that
are in the routing table. Therefore, a router can redistribute
dynamically learned routes, static routes, and direct connected
routes.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 359
 Redistributing Routes

 Redistribution is always performed outbound .

 This means that the router doing redistribution does not
change its own routing table.
 Only downstream routers receiving the redistributed routes
could add them to their respective routing tables.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 360
 Redistributing Routes

 Without redistribution, routers in the OSPF domain are not

aware of EIGRP routes, and routers in the EIGRP domain
are not aware of OSPF routes.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 361
 Seed Metrics
 When a router is redistributing, the redistributed route must have
a metric appropriate for the receiving protocol.
 The seed or default metric is defined during redistribution
configuration. After the seed metric for a redistributed route is
established, the metric increments normally within the
autonomous system.
The seed metric can be configured using either of the following:
 The default-metric router configuration command, which
establishes the seed metric for all redistributed routes. The
default metric specified applies to all protocols being redistributed
into this protocol.
 The redistribute router configuration command using either the
metric option or a route map. Using the metric parameter in the
redistribute command, set a specific metric for the protocol
being redistributed.
 A metric configured in a redistribute command overrides the
value in the default-metric command for that one protocol.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 362
 Default Seed Metrics
Default seed metric value for redistributed routes for each IP
routing protocol is as follows:
 Routes redistributed into EIGRP and RIP are assigned a metric
of infinity. This informs the router that the route is unreachable
and should not be advertised. Therefore, a seed metric must be
specified. Exceptions to this rule are redistributed connected or
static routes and routes that are being redistributed between two
EIGRP autonomous systems.
 Routes redistributed into OSPF are assigned a default type 2
(E2) metric of 20. However, redistributed BGP routes are
assigned a default type 2 metric of 1.
 Routes redistributed into for BGP maintain their IGP routing
metrics.
 Routes redistributed into Intermediate System-to-Intermediate
System (IS-IS) Protocol are assigned a default metric of 0. But
unlike RIP or EIGRP, a seed metric of 0 is not treated as
unreachable by IS-IS.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 363
 Default Seed Metrics

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 364
 Redistributing RIP Routes into OSPF

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 365
 Redistributing RIP Routes into OSPF

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 366
 Configuring and Verifying Basic Redistribution
in IPv4 and IPv6

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 367
 Redistributing OSPFv2 Routes into the EIGRP
Routing Domain
 Router(config-router)# redistribute protocol process-id [ metric
bandwidth-metric delay-metric reliability-metric effective-
bandwidth-metric mtu-bytes ] [ route-map map-tag ]

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 368
 Redistributing OSPFv2 Routes into the EIGRP
Routing Domain

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 369
 Verifying Redistributed OSPF Routes on R2

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 370
 Redistributing OSPFv3 Routes into the EIGRP
for IPv6 Routing Domain

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 371
 Redistributing Connected Routes into EIGRP
for IPv6

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 372
 Redistributing EIGRP Routes into the OSPFv2
Routing Domain
 Router(config-router)# redistribute protocol process-id [
metric metric-value ] [ metric-type type-value ] [ route-
map map-tag ] [ subnets ]

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 373
 Redistributing EIGRP Routes into OSPF

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 374
 OSPF Metric-Type
The following external packet types can be configured:
 E1: Type O E1 external routes calculate the cost by adding
the external cost to the internal cost of each link that the
packet crosses. Use this type when there are multiple
ASBRs advertising an external route to the same
autonomous system to avoid suboptimal routing.
 E2 (default): The external cost of O E2 routes is fixed and
does not change across OSPF domain. Use this type if only
one ASBR is advertising an external route to the
autonomous system

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 375
 Redistributing EIGRP Routes into OSPF as
External Type 1 Routes

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 376
 Redistributing EIGRP for IPv6 Routes into
OSPFv3

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 377
 Types of Redistribution Techniques
One-Point Redistribution
 One-way redistribution - This method only redistributes the networks
learned from one routing protocol into the other routing protocol.
 With this method, R1 performs one-way redistribution because it only
redistributes AS1 routes into the AS2 routing domain.
 AS2 routes are not being redistributed in AS1.
 Typically, AS1 routers would require the use of a default route or one or
more static routes to reach AS2 routes.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 378
 Types of Redistribution Techniques
One-Point Redistribution
 Two-way redistribution: This method redistributes routes
between the two routing processes in both directions.
 R1 is the one-point of redistribution between AS1 and AS2.
 R1 provides two-way redistribution because it redistributes
AS1 routes into AS2 and AS2 routes into AS1.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 379
 Types of Redistribution Techniques
Multipoint Redistribution
 One-way redistribution: This method consists of two or more
boundary routers only redistributing networks learned from one routing
protocol into the other routing protocol.
 The boundary routers R3 and R4 are both redistributing AS1 routes into
the AS2 routing domain.
 Again, AS1 routers would require the use of a default route or one or
more static routes to reach AS2 routes.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 380
 Types of Redistribution Techniques
Multipoint Redistribution
 Two-way redistribution : Also referred to as mutual redistribution , this
method consists of two or more boundary routers redistributing routes in
both directions.
 The boundary routers R3 and R4 provide two-way redistribution
because they redistribute AS1 routes into AS2 and AS2 routes into AS1.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 381
 Redistribution Problems
 Generic multipoint two-way redistribution requires careful
design and configuration.
 Problems that can occur during multipoint two-way
redistribution include the following:
• Suboptimal routing. (Only part of the total cost is considered in routing
decisions.)
• Self-sustained routing loops upon route loss.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 382
 Two-Way Multipoint Redistribution Issue

 The cost of the internal links in AS1 (that is, 10 Mbps)

differs from the cost of the internal links in AS2 (that is, 100
Mbps). In the figure, it is obvious that the best path between
R1 and R4 is via R3, but during redistribution from AS2 to
AS1, the metric is lost, and R1 is sending the packets
toward R4 via R2, resulting in suboptimal routing.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 383
 Two-Way Multipoint Redistribution Issue

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 384
 Two-Way Multipoint Redistribution Issue
 The 10.2.0.0/24 network is learned natively within the RIP part of the network, R4
first sees it with a hop count of 5.
 R4 then propagates this route to R3 and R2 with a hop count of 6.
 R3 propagates the route to R1 with a hop count of 7, and R2 redistributes it into
OSPF.
 Now R1 has a choice to make. It has a route to the 10.2.0.0.0/24 network from RIP
with an AD of 120 (RIP) and the same network with an AD of 110 (OSPF).
 Because OSPF has a better (lower) AD, R1 redistributes the network back to RIP
with the metric that is set in the redistribute command.
 If the redistribute command is configured to assign a static metric of 3 hops (or
lower); however, R3 starts preferring the path R1-R2-R4 to reach 10.2.0.0.0/24,
because the hop count advertised by R1 is 3, and the hop count advertised by R4 is
6.
 This results in suboptimal routing.
 Worse, because R3 now prefers the path to R1, it will advertise this to R4 with a hop
count of 4. R4 now has the choice of the route from R3 with a hop count of 4 or the
true path to the 10.2.0.0/24 network with a hop count of 5.
 R4 will select the path to R3 and advertise this to R2. There is now a routing loop
(R4, R2, R1, R3, and R4). Packets destined for the 10.2.0.0/24 network that enter
this loop will bounce around the loop and never reach the destination. Network
10.2.0.0/24 becomes unreachable.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 385
 Preventing Routing Loops in a Redistribution
Environment
 Redistribute routes in only one direction, on only one
boundary router within the network.
 If redistribution must be done in both directions or on
multiple boundary routers, the redistribution should be
tuned.
 To prevent routing loops in a multipoint redistribution
scenario:
• Only redistribute internal routes from one autonomous system to
another (and vice versa).
• Tag routes in redistribution points and filter based on these tags when
configuring redistribution in the other direction.
• Propagate metrics from one autonomous system to another
autonomous system properly. (Even though this is not sufficient to
prevent loops.)
• Use default routes to avoid having to do two-way redistribution.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 386
 Verifying Redistribution Operation
 Know your network topology, particularly where redundant
routes exist.
 Examine the topology table of each configured routing
protocol to ensure that all appropriate prefixes are being
learned.
 Perform a trace using the traceroute [ ip-address ] EXEC
command on some of the routes that go across the
autonomous systems to verify that the shortest path is being
used for routing.
 If you encounter routing problems, use the traceroute and
debug commands to observe the routing update traffic on
the boundary routers and on the internal routers.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 387
 Controlling
Routing Update
Traffic

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 388
 Controlling Routing Update Traffic
 Describe the general mechanics and need for route filtering
 Identify how to use and configure distribute lists
 Identify how to use and configure prefix lists
 Identify how to use and configure route maps
 Describe how to modify administrative distance

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 389
 Why Filter Routes?

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 390
 Route Filtering Methods
 Distribute lists
• A distribute list allows an access control lists (ACLs) to be applied to
routing updates.
 Prefix lists
• A prefix list is an alternative to ACLs designed to filter routes. It can be
used with distribute lists, route maps, and other commands.
 Route maps
• Route maps are complex access lists that allow conditions to be
tested against a packet or route, and then actions taken to modify
attributes of the packet or route.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 391
 Using Distribute Lists
 A distribute list allows an ACL to be applied to routing
updates.
 Classic ACLs do not affect traffic that is originated by the
router, so applying one to an interface has no effect on the
outgoing routing advertisements.
 When you link an ACL to a distribute list, routing updates
can be controlled no matter what their source is.
 ACLs are configured in the global configuration mode and
are then associated with a distribute list under the routing
protocol.
 The ACL should permit the networks that should be
advertised or redistributed and deny the networks that
should be filtered.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 392
 Using Distribute Lists
 The router then applies the ACL to the routing updates for
that protocol. Options in the distribute-list command allow
updates to be filtered based on three factors:
• Incoming interface
• Outgoing interface
• Redistribution from another routing protocol
 Using a distribute list gives the administrator great flexibility
in determining just which routes will be permitted and which
will be denied.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 393
 Configuring Distribute Lists [out]
 distribute-list [ access-list-number | name ] out [
interface-type interface-number | routing process |
autonomous-system-number ] command.

 The distribute-list out command filters updates going out

of the interface or routing protocol specified in the
command, into the routing process under which it is
configured.
Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 394
 Configuring Distribute Lists [in]
 distribute-list [ access-list-number | name ] in [
interface-type interface-number ]

 The distribute-list in command filters updates going into

the interface specified in the command, into the routing
process under which it is configured.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 395
 Distribute List and ACL Example [out]

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 396
 Distribute List and ACL Example [in]

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 397
 Distribute List Issues
 Traditionally, route filtering was accomplished using ACLs
with the distribute-list command; however, using ACLs as
route filters for distribute lists has several drawbacks,
including the following:
• A subnet mask cannot be easily matched.
• Access lists are evaluated sequentially for every IP prefix in the
routing update.
• Extended access lists can be cumbersome to configure.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 398
 Prefix List Characteristics
 Prefix lists are similar to access lists in many ways.
 A prefix list can consist of any number of lines, each of
which indicates a test and a result.
 The router can interpret the lines in the specified order,
although Cisco IOS Software optimizes prefix lists for
processing in a tree structure.
 When a router evaluates a route against the prefix list, the
first line that matches will result in either a “permit” or
“deny.”
 If none of the lines in the list match, the result is “implicitly
deny.”

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 399
 The Advantages of Using Prefix Lists
 Friendlier command-line interface
 Faster processing
• A significant performance improvement over access lists in loading
and route lookup of large lists.
 Support for incremental modifications
• Sequence numbers are assigned to ip prefix-list statements, making
it easier to edit.
 Greater flexibility
• Routers match networks in a routing update against the prefix list
using as many bits as indicated. A prefix list can specify the exact size
of the subnet mask, or it can indicate that the subnet mask must be in
a specified range.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 400
 Configuring Prefix Lists
 ip prefix-list { list-name | list-number } [ seq seq-value
] { deny | permit } network/ length [ ge ge-value ] [ le
le-value ]

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 401
 Distribute List and Prefix List Example

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 402
 Prefix List Examples

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 403
 Verifying Prefix Lists

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 404
 Manipulating Redistribution Using ACLs, Prefix
Lists, and Distribute Lists

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 405
 Redistributing OSPFv2 Routes into the EIGRP
Routing Domain Using an ACL and Distribute
List

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 406
 Redistributing EIGRP Routes into the OSPF
Routing Domain Using a Prefix List and
Distribute List

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 407
 Understanding Route Maps
 Route maps are complex access lists that allow some
conditions to be tested against the packet or route in
question using match commands.
 If the conditions match, some actions can be taken to
modify attributes of the packet or route.
 These actions are specified by set commands.
 A collection of route-map statements that have the same
route map name is considered one route map.
 Within a route map, each route-map statement is
numbered and therefore can be edited individually.
 The statements in a route map correspond to the lines of an
access list.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 408
 Route Map Applications
 Route filtering during redistribution
• Route maps offer the benefit of manipulating routing metrics through
the use of set commands.
• The route map is applied using the redistribute command.
 Policy-based routing (PBR)
• Route maps can be used to match source and destination addresses,
protocol types, and end-user applications. When a match occurs, a
set command can be used to define the interface or next-hop address
to which the packet should be sent.
• The route map is applied to an interface using the ip policy route-
map interface configuration command.
 BGP
• In addition to filtering, route maps provide sophisticated manipulation
of BGP path attributes. The route map is applied using the BGP
neighbor router configuration command.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 409
 Configuring Route Maps
Step 1. Define the route map using the route-map global
configuration command.

Step 2. Define the matching conditions using the match

command and optionally the action to be taken when each
condition is matched using the set command.

Step 3. Apply the route map.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 410
 Define the Route Map
 route-map map-tag [ permit | deny ] [ sequence-number ]

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 411
 Route Map Rules
 Route map sequence numbers do not automatically increment. When the
sequence-number parameter of the route-map command is not used, the
following occurs:
• If no other entry is already defined with the supplied route-map map-tag , an entry is created, with
the sequence-number set to 10.
• If only one entry is already defined with the supplied route-map tag, that entry is the default entry for
the route-map command, and the sequence-number of the entry is unchanged.
• If more than one entry is already defined with the supplied route-map tag, an error message is
displayed, indicating that the sequence-number is required.
• If the no route-map map-tag command is specified (without the sequence-number parameter), the
whole route map is deleted.
 Like an access list, an implicit deny any appears at the end of a route map. The
consequences of this deny depend on how the route map is being used.
 The match condition route map configuration commands are used to define the
conditions to be checked. The set condition route map configuration commands
are used to define the actions to be followed if there is a match and the action to
be taken is permit.
 A route-map statement without any match statements will be considered
matched.
Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 412
 Demonstration of the route-map Command

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 413
 Define the Matching Conditions

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 414
 Define the Set Actions

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 415
 Define the Set Actions

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 416
 Using Route Maps with Redistribution

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 417
 Manipulating Redistribution Using Route Maps

 R1 and R4 will be configured to support mutual

redistribution without any filtering mechanism.
 R1 and R4 will be configured to support mutual
redistribution using route maps.
 Change administrative distance for certain routes to enable
optimal routing.
Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 418
 Mutual Redistribution Without Filters

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 419
 Verifying Redistributed Routes

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 420
 Manipulating Redistribution Using Route Maps

 R1 and R4 will be configured to support mutual

redistribution without any filtering mechanism.
 R1 and R4 will be configured to support mutual
redistribution using route maps.
 Change administrative distance for certain routes to enable
optimal routing.
Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 421
 Mutual Redistribution with Route Maps

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 422
 Mutual Redistribution with Route Maps

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 423
 Verifying Redistributed Routes

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 424
 Change Administrative Distance to Enable
Optimal Routing

 R1 and R4 will be configured to support mutual

redistribution without any filtering mechanism.
 R1 and R4 will be configured to support mutual
redistribution using route maps.
 Change administrative distance for certain routes to enable
optimal routing.
Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 425
 Examine R1 Routing Table

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 426
 Changing External Route Administrative
Distance

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 427
 Manipulating Redistribution Using Route
Tagging

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 428
 Manipulating Redistribution Using Route
Tagging

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 429
 Caveats of Redistribution
 Redistribution of routing information adds to the complexity
of a network and increases the potential for routing
confusion, so you should use it only when necessary.
 The key issues that arise when you are using redistribution
are as follows:
• Routing loops
• Incompatible routing information
• Inconsistent convergence time

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 430
 Chapter 4 Summary
This chapter covered how to support multiple routing
protocols by using redistribution and route filtering
techniques, through discussion of the following topics:
 Reasons for using more than one routing protocol
(migration, host system needs, mixed-vendor environment,
political and geographic borders, Multiprotocol Label
Switching [MPLS] virtual private networks [VPNs]).
 Routing information can be exchanged between them
(referred to as redistribution), and how Cisco routers
operate in a multiple routing protocol environment.
 Route redistribution is always performed outbound . The
router doing redistribution does not change its routing table.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 431
 Chapter 4 Summary
 A router assigns a seed metric to redistributed routes using
the default-metric routercconfiguration command or the
redistribute command with the metric parameter.
 The redistribution techniques, one-point and multipoint:
• The two methods of one-point route redistribution are one-way and
two-way. Suboptimal routing is a possible issue with these
techniques.
• The two methods of multipoint route redistribution are one-way and
two-way. Multipoint redistribution is likely to introduce potential routing
loops.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 432
 Chapter 4 Summary
 To prevent routing issues, use one of the following options:
• Redistribute a default route from the core autonomous system into the
edge autonomous system, and redistribute routes from the edge
routing protocols into the core routing protocol.
• Redistribute multiple static routes about the core autonomous system
networks into the edge autonomous system, and redistribute routes
from the edge routing protocols into the core routing protocol.
• Redistribute routes from the core autonomous system into the edge
autonomous system with filtering to block out inappropriate routes.
• Redistribute all routes from the core autonomous system into the
edge autonomous system, and from the edge autonomous system
into the core autonomous system, and then modify the administrative
distance associated with redistributed routes so that they are not the
selected routes when multiple routes exist for the same destination.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 433
 Chapter 4 Summary
 Configuration of redistribution between various IP routing
protocols:
• To redistribute into EIGRP, use the redistribu te protocol [ process-id
] [ match route-type ] [ metric metric-value ] [ route-map map-tag ]
router configuration command.
• To redistribute into OSPF, use the redistribute protocol [ process-id ]
[ metric metric-value ] [ metric-type type-value ] [ route-map map-
tag ] [ subnets ] [ tag tagvalue ] router configuration command.
 Using the show ip route [ ip-address ] and traceroute [ ip-
address ] commands to verify route redistribution.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 434
 Chapter 4 Summary
 Distribute lists, allowing an access list to be applied to
routing updates:
• The distribute-list { access-list-number | name } out [ interface-name
] router configuration command assigns the access list to filter
outgoing routing updates. This command filters updates going out of
the interface or routing protocol specified in the command, into the
routing process under which it is configured.
• The distribute-list { access-list-number | name } [ route-map map-
tag ] in [ interface-type interface-number ] router configuration
command assigns the access list to filter routing updates coming in
through an interface. This command filters updates going into the
interface specified in the command, into the routing process under
which it is configured.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 435
 Chapter 4 Summary
 Prefix lists can be used with distribute lists as an alternative
to ACLs, with improvements in performance, support for
incremental modifications, a more userfriendly command-
line interface, and greater flexibility. Prefix lists are
configured with the ip prefix-list { list-name | list-number } [
seq seq-value ] { deny | permit } network / length [ ge ge-
value ] [ le le-value ] global configuration command.
 Whether a prefix in a prefix list is permitted or denied is
based on the following rules:
• An empty prefix list permits all prefixes.
• If a prefix is permitted, the route is used. If a prefix is denied, the route
is not used.
• Prefix lists consist of statements with sequence numbers. The router
begins the search for a match at the top of the prefix list, which is the
Chapter 4
statement with the lowest sequence number.
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 436
 Chapter 4 Summary
• When a match occurs, the router does not need to go through the rest
of the prefix list. For efficiency, you might want to put the most
common matches (permits or denies) near the top of the list by
specifying a lower sequence number.
• An implicit deny Is assumed if a given prefix does not match any
entries in a prefix list.
 Prefix list sequence numbers:
• Sequence numbers are generated automatically, unless you disable
this automatic generation.
• A prefix list is an ordered list. The sequence number is significant
when a given prefix is matched by multiple entries of a prefix list, in
which case the one with the smallest sequence number is considered
the real match.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 437
 Chapter 4 Summary
• The evaluation of a prefix list starts with the lowest sequence number
and continues down the list until a match is found, in which case the
permit or deny statement is applied to that network and the
remainder of the list is not evaluated.
 Using route maps for route filtering during redistribution,
PBR, and BGP.
 The characteristics of route maps, configured using the
route-map map-tag [ permit | deny ] [ sequence-number ]
global configuration command:
 Route maps allow some conditions to be tested against the
packet or route in question using match commands. If the
conditions match, some actions can be taken to modify
attributes of the packet or route; these actions are specified
by set commands.

Chapter 4 A collection of route-map statements that have the 438
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public
 Chapter 4 Summary
 A collection of route-map statements that have the same
route map name is considered one route map.
 Within a route map, each route-map statement is
numbered and therefore can be edited individually.
 The default for the route-map command is permit , with a
sequence-number of 10.
 Only one condition listed on the same match statement
must match for the entire statement to be considered a
match. However, all match statements within a route-map
statement must match for the route map to be considered
matched.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 439
 Chapter 4 Summary
 When used with a redistribute command, a route-map
statement with permit indicates that the matched route is to
be redistributed, and a route-map statement with deny
indicates that the matched route is not to be redistributed.

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 440
 Chapter 4 Labs
 CCNPv7 ROUTE Lab 4.1-Redistribution EIGRP OSPF
 CCNPv7 ROUTE Lab 4.2-Controlling Routing Updates
 CCNPv7 ROUTE Lab 4.3-Redistribution EIGRP for IPv6
and OSPFv3

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 441
Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 442
 Acknowledgment
• Some of images and texts are from Implementing Cisco IP Routing (ROUTE)
Foundation Learning Guide by Diane Teare, Bob Vachon and Rick Graziani
(1587204568)
• Copyright © 2015 – 2016 Cisco Systems, Inc.
• Special Thanks to Bruno Silva

Chapter 4
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 443
 Chapter 5:
Path Control
Implementation

CCNP ROUTE: Implementing IP Routing

ROUTE v7 Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 444
 Chapter 5 Objectives
 Using Cisco Express Forwarding Switching
 Understanding Path Control
 Implementing Path Control Using Policy-Based Routing
 Implementing Path Control Using Cisco IOS IP SLAs

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 445
 Using Cisco
Express
Forwarding
Switching

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 446
 Using Cisco Express Forwarding Switching

 Describe the different switching mechanisms that a Cisco

router uses
 Describe how Cisco Express Forwarding (CEF) works
 Describe how to verify that CEF is working
 Describe how to verify the content of the CEF tables
 Describe how to enable and disable CEF by interface and
globally

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 447
 Control and Data Plane
 A Layer 3 device employs a distributed architecture in which
the control plane and data plane are relatively independent.
 For example, the exchange of routing protocol information
is performed in the control plane by the route processor,
whereas data packets are forwarded in the data plane by an
interface micro-coded processor.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 448
 Control and Data Plane
 The main functions of the control layer between the routing
protocol and the firmware data plane microcode include the
following:
• Managing the internal data and control circuits for the packet-
forwarding and control functions.
• Extracting the other routing and packet-forwarding-related control
information from Layer 2 and Layer 3 bridging and routing protocols
and the configuration data, and then conveying the information to the
interface module for control of the data plane.
• Collecting the data plane information, such as traffic statistics, from
the interface module to the route processor.
• Handling certain data packets that are sent from the Ethernet
interface modules to the route processor.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 449
 Cisco Switching Mechanisms
 Process switching
 Fast switching
 Cisco Express Forwarding

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 450
 Process switching

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 451
 Process switching
 This switching method is the slowest of the three methods.
 Every packet is examined by the CPU in the control plane
and all forwarding decisions are made in software.
 When a packet arrives on the ingress interface, it is
forwarded to the control plane where the CPU matches the
destination address with an entry in its routing table.
 It then determines the exit interface and forwards the
packet.
 The router does this for every packet, even if the destination
is the same for a stream of packets.
 Process switching is the most CPU-intensive method that is
available in Cisco routers. It greatly degrades performance
and is generally used only as a last resort or during
troubleshooting.
Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 452
 Fast switching

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 453
 Fast switching
 This switching method is faster than process switching.
 With fast switching, the initial packet of a traffic flow is
process switched.
 This means that it is examined by the CPU and the
forwarding decision is made in software.
 However, the forwarding decision is also stored in the data
plane hardware fast-switching cache.
 When subsequent frames in the flow arrive, the destination
is found in the hardware fast-switching cache and the
frames are then forwarded without interrupting the CPU.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 454
 Cisco Express Forwarding

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 455
 Cisco Express Forwarding
 This switching method is the fastest switching mode and is less
CPU-intensive than fast switching and process switching.
 The control plane CPU of a CEF-enabled router creates two
hardware-based tables called the Forwarding Information Base
(FIB) table and an adjacency table using Layer 3 and 2 tables
including the routing and Address Resolution Protocol (ARP)
tables.
 When a network has converged, the FIB and adjacency tables
contain all the information a router would have to consider when
forwarding a packet.
 These two tables are then used to make hardware-based
forwarding decisions for all frames in a data flow, even the first
frame.
 The FIB contains precomputed reverse lookups and next-hop
information for routes, including the interface and Layer 2
information.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 456
 Process and Fast Switching

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 457
 Process and Fast Switching
 Specifically, an entry is created in the fast-switching cache
to ensure that the subsequent packets for the same
destination prefix will be fast switched.
 All subsequent packets for the same destination are fast
switched:
• The switching occurs in the interrupt code. (The packet is processed
immediately.)
• Fast destination lookup is performed (no recursion).
• The encapsulation uses a pregenerated Layer 2 header that contains
the destination IP Address and Layer 2 source MAC address. (No
ARP request or ARP cache lookup is necessary.)

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 458
 Cisco Express Forwarding

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 459
 Cisco Express Forwarding
 CEF separates the control plane software from the data
plane hardware, thereby achieving higher data throughput.
 The control plane is responsible for building the FIB table
and adjacency tables in software.
 The data plane is responsible for forwarding IP unicast
traffic using hardware.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 460
 CEF FIB Table
 The FIB is derived from the IP routing table and is arranged for
maximum lookup throughput.
 CEF IP destination prefixes are stored from the most-specific to
the least specific entry.
 The FIB lookup is based on the Layer 3 destination address
prefix (longest match), so it matches the structure of CEF entries.
When the CEF FIB table is full, a wildcard entry redirects frames
to the Layer 3 engine.
 The FIB table is updated after each network change, but only
once, and contains all known routes; there is no need to build a
route cache by central-processing initial packets from each data
flow.
 Each change in the IP routing table triggers a similar change in
the FIB table because it contains all next-hop addresses that are
associated with all destination networks.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 461
 CEF Adjancency Table
 CEF also caches Layer 2 next-hop addresses and frame
header rewrite information for all FIB entries in the
adjacency table.
 The adjacency table is derived from the ARP table, and it
contains Layer 2 header rewrite (MAC) information for each
next hop that is contained in the FIB.
 Each time that an adjacency entry is created (such as
through ARP), a link-layer header for that adjacent node is
precomputed and is stored in the adjacency table.
 CEF uses a specific process to build forwarding tables in
the hardware and then uses the information from those
tables to forward packets at line speed.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 462
 CEF Exceptions
 Not all packets can be CEF switched and processed in the
hardware. When traffic cannot be processed in the hardware, it
must be received by software processing of the Layer 3 engine.

 Some examples of IP exception packets are packets that have

the following characteristics:
 They use IP header options.
 They have an expiring IP Time To Live (TTL) counter.
 They are forwarded to a tunnel interface.
 They arrive with unsupported encapsulation types.
 They are routed to an interface with unsupported encapsulation
types.
 They exceed the maximum transmission unit (MTU) of an output
interface and mustbe fragmented.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 463
 Enable and Disable CEF by Interface

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 464
 Enable and Disable CEF Globally

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 465
 Understanding
Path Control

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 466
 Understanding Path Control
 Identify the need for path control
 Describe how to use policy-based routing (PBR) to control
path selection
 Describe how to use IP service-level agreement (IP SLA) to
control path selection

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 467
 The Need for Path Control
 Path control tools can be used to change the default destination
forwarding and optimize the path of the packets for some specific
application.
 Other examples of path control include switching traffic to the
backup link if there is a primary link failure, or forwarding some
traffic to the backup link if the primary link is congested.
 Path control mechanisms can improve performance in such a
situation.
 Similarly, load balancing can divide traffic among parallel paths.
 It is important to provide predictable and deterministic control
over traffic patterns.
 Unfortunately, there is not a “one-command” solution to
implement path control.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 468
 The Need for Path Control
 You can use all of these tools as part of an integrated
strategy to implement path control.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 469
 Implementing Path Control Using Policy-Based
Routing
 PBR enables the administrator to define a routing policy
other than basic destination-based routing using the routing
table.
 With PBR, route maps can be used to match source and
destination addresses, protocol types, and end-user
applications.
 When a match occurs, a set command can be used to
define items, such as the interface or next-hop address to
which the packet should be sent.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 470
 PBR Features
 Source-based transit-provider selection
• PBR policies can be implemented by ISPs and other organizations to
route traffic that originates from different sets of users through different
Internet connections across the policy routers.
 QoS
• PBR policies can be implemented to provide quality of service (QoS) to
differentiated traffic by setting the type of service (ToS) values in the IP
packet headers in routers at the periphery of the network and then
leveraging queuing mechanisms to prioritize traffic in the network’s core
or backbone.
 Cost savings
• PBR policies can be implemented to direct the bulk traffic associated with
a specific activity to use a higher-bandwidth, high-cost link for a short
time and to continue basic connectivity over a lower-bandwidth, low-cost
link for interactive traffic.
 Load sharing
• PBR policies can be implemented based on the traffic characteristics to
distribute traffic among multiple paths.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 471
 Steps for Configuring PBR
1. Enable PBR by configuring a route map using the route-
map global configuration command.
2. Implement the traffic-matching configuration, specifying
which traffic will be manipulated. This is done using the
match commands within the route map.
3. Define the action for the matched traffic. This is done
using the set commands within the route map.
4. Optionally, fast-switched PBR or CEF-switched PBR can
be enabled.
5. Apply the route map to incoming traffic or to traffic locally
generated on the router using the ip policy route-map
interface configuration command.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 472
 Configuring PBR – Route-Map
 If the statement is marked as permit , such as in route-
map MY-MAP permit 10 , packets that meet all the match
criteria are policy-based routed.
 If the statement is marked as deny , such as in route-map
MY-MAP deny 10 , a packet meeting the match criteria is
not policy-based routed. Instead, it is sent through the
normal forwarding channels and destination-based routing
is performed.
 If no match is found in the route map, the packet is not
dropped. It is forwarded through the normal routing channel,
which means that destination-based routing is performed.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 473
 PBR match Commands

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 474
 PBR set Commands

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 475
 Configuring PBR Example
 Verify normal traffic paths as selected by the traditional
destination-based routing
 Configure PBR to alter the traffic flow for one client station
 Verify both the PBR configuration and the new traffic path

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 476
 Verify Normal Traffic Paths

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 477
 Configure PBR to Alter the Traffic Flow from
the Notebook

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 478
 Verify the PBR Configuration and Traffic Path

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 479
 Implementing Path Control Using Cisco IOS IP
SLAs
 PBR is a static path control mechanism. It cannot respond
dynamically to changes in network health.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 480
 IP SLA Features
 Cisco IOS IP SLAs perform network performance measurement
within Cisco devices.
 The IP SLAs use active traffic monitoring (generation of traffic in
a continuous, reliable, and predictable manner) for measuring
network performance.
 Cisco IOS IP SLAs actively send simulated data across the
network to measure performance between multiple network
locations or across multiple network paths.
 The information collected includes data about response time,
one-way latency, jitter, packet loss, voice-quality scoring, network
resource availability, application performance, and server
response time.
 In its simplest form, Cisco IOS IP SLAs verify whether a network
element, such as an IP address on a router interface or an open
TCP port on an IP host, is active and responsive.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 481
 Cisco IOS IP SLA Sources and Targets

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 482
 Steps for Configuring IP SLAs
 Step 1. Define one or more IP SLA operations (or probes).
 Step 2. Define one or more tracking objects to track the
state of IOS IP SLA operations.
 Step 3. Define the action associated with the tracking
object.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 483
 Step 1. Configuring Cisco IOS IP SLA
Operations
 Use the ip sla operation-number global configuration
command to begin configuring a Cisco IOS IP SLA
operation and to enter IP SLA configuration mode. The
operationnumber is the identification number of the IP SLA
operation to be configured.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 484
 IP SLA icmp-echo
 The complete command syntax is icmp-echo { destination-
ip-address | destinationhostname} [ source-ip { ip - address
| hostname } | source-interface interface-name ].

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 485
 IP SLA ICMP Echo Configuration Mode
Commands

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 486
 Schedule the IP SLA Operation
 Once a Cisco IP SLA operation is configured, it needs to be
scheduled using the ip sla schedule global
configuration command.
ip sla schedule operation-number [ life { forever | seconds
}] [ start-time { hh:mm [ :ss ] [ month day | day month ] |
pending | now | after hh:mm:ss }] [ ageout seconds ] [
recurring ]

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 487
 Step 2: Configuring Cisco IOS IP SLA Tracking
Objects
 Use the track object-number ip sla operation-
number { state | reachability } global configuration
command to track the state of an IOS IP SLA operation, and
enter track configuration mode.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 488
 delay Command Parameters
 Once in IP SLA track configuration mode, use the optional
delay { up seconds [ down seconds ] | [ up
seconds ] down seconds } track configuration
command to specify a period of time to delay
communicating state changes of a tracked object.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 489
 Step 3: Defining an Action Associated with a
Tracking Object
 Many types of actions can be associated with a tracked
object.
 A simple path control action is to use the ip route prefix
mask { ip-address | interface-type interface-
number [ ip-address ]} [ track number ] global
configuration command.
 The command can be used with the track keyword to
establish a static route that tracks an object.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 490
 Configuring IP SLA Example
 The static route to ISP1a (ISP-1), which has been assigned
an administrative distance of 2
 The static route to ISP2a (ISP-2), which has been assigned
an administrative distance of 3

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 491
 In the example, you will
 Configure an IP SLA operation with the ISP 1 DNS server
 Define a tracking object assign an action
 Configure an IP SLA operation with the ISP 2 DNS server
 Define a tracking object assign an action

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 492
 Configure IP SLA and Track Object for ISP 1

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 493
 Configure IP SLA and Track Object for ISP 2

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 494
 Configuring PBR and IP SLA Example
 In this scenario, traffic paths for the clients at first branch
office (router BR1) will be optimized using PBR and IP SLA.
EIGRP is already configured between HQ and BR1, and all
traffic flows over the Ethernet WAN link because it has the
lowest EIGRP metric route.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 495
 In the example, you will
 The new network policy for BR1 dictates that
• Web traffic to the HQ site should be redirected over the serial link.
• All other traffic from Notebook should go via BR2 but only if BR2 is
reachable.
 In the example, you will
• Redirect web traffic from clients on the BR1 router going to the HQ
router over the serial link using PBR
• Ensure that BR2 is reachable by using an IP SLA ICMP echo test to
its WAN interface
• Redirect all other traffic from Notebook to router BR2 if BR2 is
reachable

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 496
 Redirecting Web Traffic from BR1 to HQ Using
PBR

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 497
 Ensuring That BR2 Is Reachable Using IP SLA

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 498
 Redirect Traffic from Notebook to BR2 If
Reachable

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 499
 Verify Route Maps

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 500
 Verify That the Route Map Is Applied

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 501
 Verify IP SLA Operations

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 502
 Verify Tracking Objects

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 503
 Chapter 5 Summary
 Packet-switching mechanisms on a Cisco IOS platform, including
process switching, fast switching, and CEF switching.
 Overview of path control tools, including PBR and Cisco IOS IP SLAs.
 Using PBR to control path selection, providing benefits including source-
based transit provider selection, QoS, cost savings, and load sharing.
PBR is applied to incoming packets; enabling PBR causes the router to
evaluate all packets incoming on the interface using a route map
configured for that purpose.
 Configuring and verifying PBR, including the following steps:
• Choose the path control tool to use; for PBR, route-map commands are used
• Implement the traffic-matching configuration, specifying which traffic will be
manipulated; match commands are used within route maps
• Define the action for the matched traffic, using set commands within route maps
• Apply the route map to incoming traffic or to traffic locally generated on the router
• Verify path control results, using show commands

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 504
 Chapter 5 Summary
 Cisco IOS IP SLAs, which use active traffic monitoring, generating traffic in
a continuous, reliable, and predictable manner, to measure network
performance. IOS IP SLAs can be used in conjunction with other tools,
including the following:
• Object tracking, to track the reachability of specified objects
• Cisco IOS IP SLAs probes, to send different types of probes toward the desired objects
• Static routes with tracking options, as a simpler alternative to PBR
• Route maps with PBR, to associate the results of the tracking to the routing process
 Cisco IOS IP SLA terminology, including the following:
• All the Cisco IOS IP SLA measurement probe operations are configured on the IP SLA
source, either by the CLI or through an SNMP tool that supports IP SLA operation. The
source sends probe packets to the target.
• There are two types of IP SLA operations: those in which the target device is running
the IP SLA responder component, and those in which the target device is not running
the IP SLA responder component (such as a web server or IP host).
• An IP SLA operation is a measurement that includes protocol, frequency, traps, and
thresholds.
 Configuring and verifying IOS IP SLAs.

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 505
 Chapter 5 Labs
 CCNPv7 ROUTE Lab5.1 Path Control Using PBR
 CCNPv7 ROUTE Lab 5.2 IP SLA Tracking and Path
Control

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 506
Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 507
 Acknowledgment
• Some of images and texts are from Implementing Cisco IP Routing (ROUTE)
Foundation Learning Guide by Diane Teare, Bob Vachon and Rick Graziani
(1587204568)
• Copyright © 2015 – 2016 Cisco Systems, Inc.
• Special Thanks to Bruno Silva

Chapter 5
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 508