Implementing Cisco IP Routing

ROUTE
Implementing Cisco IP Routing

Volume 1
Version 1.0
Student Guide
Text Part Number: 97-2814-01
DISCLAIMER WARRANTY: THIS CONTENT IS BEING PROVIDED AS IS. CISCO MAKES AND YOU RECEIVE NO WARRANTIES IN CONNECTION WITH THE CONTENT PROVIDED HEREUNDER, EXPRESS, IMPLIED, STATUTORY OR IN ANY OTHER PROVISION OF THIS CONTENT OR COMMUNICATION BETWEEN CISCO AND YOU. CISCO SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. This learning product may contain early release content, and while Cisco believes it to be accurate, it falls subject to the disclaimer above.
Student Guide
2009 Cisco Systems, Inc. All Rights Reserved.
Students, this letter describes important course evaluation access information!
Welcome to Cisco Systems Learning. Through the Cisco Learning Partner Program, Cisco Systems is committed to bringing you the highest-quality training in the industry. Cisco learning products are designed to advance your professional goals and give you the expertise you need to build and maintain strategic networks. Cisco relies on customer feedback to guide business decisions; therefore, your valuable input will help shape future Cisco course curricula, products, and training offerings. We would appreciate a few minutes of your time to complete a brief Cisco online course evaluation of your instructor and the course materials in this student kit. On the final day of class, your instructor will provide you with a URL directing you to a short post-course evaluation. If there is no Internet access in the classroom, please complete the evaluation within the next 48 hours or as soon as you can access the web. On behalf of Cisco, thank you for choosing Cisco Learning Partners for your Internet technology training. Sincerely, Cisco Systems Learning
Table of Contents
Volume 1 Course Introduction
Overview Learner Skills and Knowledge Course Goal and Objectives Course Flow Additional References Cisco Glossary of Terms Your Training Curriculum General Administration
1
1 1 3 4 6 6 7 10
Planning Routing Services to Requirements

Overview Module Objectives
1-1
1-1 1-1
Assessing Complex Enterprise Network Requirements

Overview Objectives Defining Cisco Network Models Traffic Conditions in a Converged Network Cisco SONA Framework Routing and Routing Protocols Summary
1-3
1-3 1-3 1-4 1-10 1-13 1-19 1-22
Creating an Implementation Plan and Documenting the Implementation

Overview Objectives Creating an Implementation Plan Implementation Plan Tasks Implementation Plan Documentation Implementation Plan Example Summary
1-23
1-23 1-23 1-24 1-28 1-32 1-34 1-40
Lab 1-1 Debrief

Overview Objectives Lab Overview and Verification Sample Solutions and Alternatives Summary Module Summary Module Self-Check Module Self-Check Answer Key
1-41
1-41 1-41 1-42 1-46 1-49 1-51 1-53 1-56
Implementing an EIGRP-Based Solution

2-1
2-1 2-1
Planning Routing Implementations with EIGRP

Overview Objectives EIGRP Capabilities and Attributes EIGRP Operation and Metric Example: EIGRP Tables Example: Advertised Distance (AD) Example: Feasible Distance (FD) Example: Successor and Feasible Successor Example: EIGRP Metrics Calculation Planning and Documenting for EIGRP Implementing Basic EIGRP Example: Basic EIGRP Configuration Summary
2-3
2-3 2-3 2-4 2-8 2-13 2-16 2-17 2-18 2-22 2-24 2-27 2-33 2-35
Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture
Overview Objectives Verify EIGRP Routes for IPv4 Using the Passive-Interface Command with EIGRP Advertising an IP Default Network in EIGRP Determining Summary Boundaries Utilizing Manual Route Summarization Summary
2-37
2-37 2-37 2-38 2-49 2-52 2-55 2-59 2-62
Lab 2-1 Debrief

Overview Objectives Lab Overview and Verification Sample Solutions and Alternatives Summary
2-63
2-63 2-63 2-64 2-68 2-71
Configuring and Verifying EIGRP for the Enterprise WAN Architecture

Overview Objectives EIGRP Over Frame Relay and on a Physical Interface EIGRP over Multipoint Subinterfaces EIGRP over Point-to-Point Subinterfaces Load Balancing Across Equal-Metric Paths Load Balancing Across Unequal-Metric Paths EIGRP Bandwidth use Across WAN Links EIGRP over EoMPLS and Metro Ethernet Summary
2-73
2-73 2-73 2-74 2-79 2-85 2-88 2-90 2-94 2-100 2-108
Lab 2-2 Debrief

2-109
2-109 2-109 2-110 2-116 2-119
ii
Implementing Cisco IP Routing (ROUTE) v1.0
2009 Cisco Systems, Inc.
Implementing and Verifying EIGRP Authentication

Overview Objectives Router Authentication for EIGRP MD5 Authentication for EIGRP Implementing MD5 Authentication for EIGRP Verifying MD5 Authentication for EIGRP Summary
2-121
2-121 2-121 2-122 2-126 2-128 2-137 2-141
Lab 2-3 Debrief

2-143
2-143 2-143 2-144 2-148 2-151
Advanced EIGRP Features in an Enterprise Network

Overview Objectives Scalability in Large Networks EIGRP Queries SIA Connections in EIGRP EIGRP Stub Routers Summary
2-153
2-153 2-153 2-154 2-157 2-158 2-161 2-171
Lab 2-4 Debrief

Overview Objectives Lab Overview and Verification Instructions Summary Module Summary Module Self-Check Module Self-Check Answer Key
2-173
2-173 2-173 2-174 2-176 2-178 2-179 2-181 2-191
iii
iv
ROUTE
Course Introduction
Overview
Implementing Cisco IP Routing (ROUTE) v1.0 is an instructor-led training program presented by Cisco training partners to their end customers. This five-day course is designed to help students prepare for Cisco CCNP certification. The ROUTE course is a component of the CCNP curriculum. The ROUTE course is designed to provide professionals of medium to large network sites with information on the use of advanced routing in implementing scalability for Cisco routers that are connected to LANs and WANs. The goal is to train professionals to dramatically increase the number of routers and sites using these techniques instead of redesigning the network when additional sites or wiring configurations are added. The ROUTE training reinforces the instruction by providing students with hands-on labs to ensure they thoroughly understand how to implement advanced routing within their networks.
Student Skills and Knowledge

This subtopic lists the skills and knowledge that students must possess to benefit fully from the course. The subtopic also includes recommended Cisco learning offerings that students should first complete to benefit fully from this course.
Learner Skills and Knowledge

Students considered for this training will have attended the following classes or obtained equivalent level training: ICND1 Interconnecting Cisco Network Devices part 1 v1.0 ICND2 Interconnecting Cisco Network Devices part 2 v1.0 Knowledge of the Cisco Lifecycle deployment
2009 Cis co S y st em s, Inc. A ll right s reserved.
ROUTE v1. 00-3
Course Goal and Objectives

This topic describes the course goal and objectives.
Course Goal
To train network professionals on the techniques to plan, implement, and monitor a scalable IP routing network.
ROUTE v1. 00-4
Upon completing this course, you will be able to meet these objectives: Plan Routing Services to meet requirements Implement an EIGRP-based solution Implement a Scalable Multiarea Network OSPF-based solution Implement an IPv4-based redistribution solution Implement Path Control Implement and verify a Layer 3 solution using BGP to connect an enterprise network to an Internet service provider
Course Introduction
Course Flow
This topic presents the suggested flow of the course materials.
Course Flow
Day 1 Course Introduction Day 2 Module 2: Implementing an EIGRPbased Solution Day 3 Module 3: Implementing a Scalable Multiarea Network OSPF-based Solution Day 4 Module 4: Implement an IPv4-based redistribution solution Day 5 Module 6: Connecting an Enterprise Network to ISP Networks
A M
Module 1: Planning Routing Services to Requirements
Lunch
Module 2: P Implementing M an EIGRPbased Solution Module 2: Implementing an EIGRPbased Solution Module 3: Implementing a Scalable Multiarea Network OSPF-based Solution Module 6: Connecting an Enterprise Network to ISP Networks
Module 5: Implement Path Control
ROUTE v1. 00-5
The schedule reflects the recommended structure for this course. This structure allows enough time for the instructor to present the course information and for you to work through the lab activities. The exact timing of the subject materials and labs depends on the pace of your specific class.
ROUTE E-learning Modules

Path Control Implementation IPv6 Implementation Routing Facilities for Branch Offices and Mobile Workers
ROUTE v1. 00-6
Implementing Cisco IP Routing (ROUTE) v1.0 training has three e-learning modules, which also include information required to pass the Cisco 642-902 ROUTE certification exam. The following modules provided: Implementing Path Control Implementing IPv6 Routing Facilities for Branch Offices and Mobile Workers The ELT content is supplied on a CD that is given out to each student, along with the other course materials.
Course Introduction
Additional References
This topic presents the Cisco icons and symbols that are used in this course, as well as information on where to find additional technical references.
Cisco Icons and Symbols

Router Web Server Network Cloud Serial Link Laptop Circuit-Switched Link File Server Workgroup Switch End Users Camera PC/Video
PC
Ethernet
IP Phone
ROUTE v1. 00-7
Cisco Glossary of Terms

For additional information on Cisco terminology, refer to the Cisco Internetworking Terms and Acronyms glossary of terms at http://www.cisco.com/en/US/docs/internetworking/terms_acronyms/CISCO12.html.
Your Training Curriculum

This topic presents the training curriculum for this course.
Cisco Career Certifications

Cisco Certifications
www.cisco.com/go/certifications
2009 Cis co S y st em s, Inc. A ll right s reserved. ROUTE v1. 00-8
You are encouraged to join the Cisco Certification Community, a discussion forum open to anyone holding a valid Cisco Career Certification (such as Cisco CCIE, CCNA, CCDA, CCNP, CCDP, CCIP, CCVP, or CCSP). It provides a gathering place for Cisco certified professionals to share questions, suggestions, and information about Cisco Career Certification programs and other certification-related topics. For more information, visit www.cisco.com/go/certifications.
Course Introduction
Cisco Career Certifications

Expand Your Professional Options and Advance Your Career
ROUTE v1. 00-9
Cisco Career Certifications (cont.)

Customize Your Learning to Match Your Job Responsibilities
If, in addition to Core Networking, you also
Assist senior staff i n designing routed and switched network infrastructure Implement and troubleshoot MPLS solutions in your enterpri se network
Additional Recommended Cisco Curriculum:

Designing for Cisco Internetwork Solutions (DESGN) Implementing Cisco MPLS (MPLS) OR Advanced Implementing and Troubleshooting MPLS VPNs (AMPLS) Configuring BGP on Cisco Routers (BGP) OR Building Core Networks with OSPF, ISIS, BGP and MPLS (BCN) Implementing Cisco Quality of Service (QoS) Implementing Cisco Unified Wireless Networking Essentials (IUWNE) Implementing Cisco IOS Network Security (IINS) CCDA CCIP
Related Cisco Career Certification:
Implement and troubleshoot IBGP solutions in your enterpri se network
CCIP
Implement and troubleshoot QoS solutions for a converged network Implement and troubleshoot wireless network devi ces Implement and troubleshoot network securi ty devices
CCIP CCNA-Wireless CCNA-Security
RO UTE v 1.00-10
Course Introduction
General Administration
This topic presents the general administration for this course.
General Administration
Class-Related Issues
Sign-in sheet Length and times Break and lunch room locations Attire
Facilities-Related Issues
Course materials Site emergency procedures Rest rooms Telephones and faxes
RO UTE v 1.00-11
The instructor will discuss the following administrative issues so that you know exactly what to expect from the class: Sign-in process Start and anticipated end times of each class day Class break and lunch facilities Appropriate attire during class Materials you can expect to receive during class What to do in the event of an emergency Location of the rest rooms How to send and receive telephone and fax messages
10
Learner Introductions
Your name Your company Job responsibilities Skills and knowledge Brief history Objective
RO UTE v 1.00-12
Prepare to share this information: Your name Your company Your job responsibilities The prerequisite skills that you have A profile of your experience What you would like to learn from this course
Course Introduction
11
12
Module 1

Overview
The convergence of voice, video, and data has not only changed the conceptual network models but has also affected the way that networks support services and applications. Correct information must be identified and collected to use in the implementation plan. This module describes Cisco conceptual models and architectures for converged networks, as well as how to build an implementation plan.
Module Objectives
Upon completing this module, you will be able to describe the converged network requirements of various network and networked applications within Cisco network architectures, including the creation of the implementation plan. This ability includes being able to meet these objectives: Identify the distinctive business and technical requirements of complex enterprise networks (compared to the simpler networks of CCNA) Assess a provided network design and to select the proper tools and resources and planning the work Assess a provided network design to create an implementation plan Review ICND2 skills and knowledge Discuss lab results to assess skills needed for implementing complex networks
1-2
Lesson 1
Assessing Complex Enterprise Network Requirements

Overview
This lesson starts by introducing Cisco Enterprise Architectures and describing how they align with the traditional three-layer hierarchical network model. The lesson examines the Cisco Enterprise Composite Network Model and discusses the traffic patterns in converged networks. It also introduces the Cisco vision of the future of the Intelligent Information Network (IIN) and the Cisco Service-Oriented Network Architecture (Cisco SONA). The lesson concludes with a discussion of where routing protocols fit into these models.
Objectives
Upon completing this lesson, you will be able to describe the converged network requirements of various networks and network applications within Cisco network architectures. This will result in the ability to identify the information that you must collect when filling out an implementation plan. This ability includes being able to meet these objectives: Define Cisco network models. Understand traffic conditions in a converged network. Understand the Cisco SONA framework. Understand routing and routing protocols.
Defining Cisco Network Models

This topic describes Cisco network models, starting with the Cisco Enterprise Architectures and how they map to a traditional three-layer hierarchical network model.
Cisco Enterprise Architectures
ROUTE v1. 01-2
Cisco provides an enterprise-wide systems architecture that helps companies protect, optimize, and grow the infrastructure that supports their business processes. The architecture provides for the integration of the entire networkcampuses, data centers, WANs, branches, and teleworkersoffering staff secure access to tools, processes, and services. The Cisco Enterprise Campus Architecture combines intelligent switching and routing of core infrastructure with tightly integrated productivity-enhancing technologies, including IP communications, mobility, and advanced security. The architecture provides the enterprise with high availability through a resilient multilayer design, redundant hardware and software features, and automatic procedures for reconfiguring network paths when failures occur. Multicast provides optimized bandwidth consumption and quality of service (QoS) prevents oversubscription, ensuring that real-time traffic, such as voice and video, and critical data are not dropped or delayed. Integrated security protects against and mitigates the impact of worms, viruses, and other attacks on the network, even at the port level. The Cisco enterprise-wide architecture extends support for standards, such as 802.1x and Extensible Authentication Protocol (EAP). It also provides the flexibility to add IP Security (IPsec) and Multiprotocol Label Switching (MPLS), virtual private networks (VPNs), identity and access management, and VLANs to compartmentalize access. These features help improve performance and security and decrease costs.
1-4
The Cisco Enterprise Data Center Architecture is a cohesive, adaptive network architecture. It supports the requirements for consolidation, business continuance, and security, while enabling emerging service-oriented architectures, virtualization, and on-demand computing. IT staff can easily provide departmental staff, suppliers, or customers with secure access to applications and resources. This simplifies and streamlines management, significantly reducing overhead. Redundant data centers provide backup using synchronous and asynchronous data and application replication. The network and devices offer server and application load balancing to maximize performance. This solution allows the enterprise to scale without major changes to the infrastructure. The Cisco Enterprise Branch Architecture allows enterprises to extend head-office applications and services, such as security, IP communications, and advanced application performance to thousands of remote locations and users or to a small group of branches. Cisco integrates security, switching, network analysis, caching, and converged voice and video services into a series of integrated services routers in the branch, so that the enterprises can deploy new services when they are ready, without buying new equipment. This solution provides secure access to voice, mission-critical data, and video applications anywhere and anytime. Advanced network routing, VPNs, redundant WAN links, application content caching, and local IP telephony call processing provide a robust architecture with high levels of resilience for all the branch offices. An optimized network leverages the WAN and LAN to reduce traffic and save bandwidth and operational expenses. The enterprise can easily support branch offices with the ability to centrally configure, monitor, and manage devices located at remote sites, including tools such as AutoQoS, which proactively resolve congestion and bandwidth issues before they affect network performance. The Cisco Enterprise Teleworker Architecture allows enterprises to securely deliver voice and data services to small remote offices and home offices using a standard broadband access service. This ability provides a business resiliency solution for the enterprise and a flexible work environment for employees. Centralized management minimizes IT support costs, while robust integrated security mitigates the unique security challenges of this environment. Integrated security and identity-based networking services enable the enterprise to extend campus security policies to the teleworker. Staff can securely log in to the network over an always-on VPN and gain access to authorized applications and services from a single costeffective platform. Productivity can further be enhanced by adding an IP phone, providing costeffective access to a centralized IP communications system with voice and unified messaging services. The Cisco Enterprise WAN Architecture offers the convergence of voice, video, and data services over a single IP communications network, which enables the enterprise to costeffectively span large geographic areas. QoS, granular service levels, and comprehensive encryption options help ensure the secure delivery of high-quality corporate voice, video, and data resources to all corporate sites, enabling staff to work productively and efficiently wherever they are located. Security is provided with multiservice VPNs (IPsec and MPLS) in Layer 2 or Layer 3 WANs, hub-and-spoke topologies, or full-mesh topologies.
1-5
Cisco Hierarchical Network Model
ROUTE v1. 01-3
Traditionally, the three-layer hierarchical model has been used in network designs. This model provides a modular framework that allows flexibility in network design and facilitates implementation and troubleshooting. The hierarchical model divides networks or their modular blocks into access, distribution, and core layers with these features: Access layer: This layer is used to grant user access to network devices. In a network campus, the access layer generally incorporates switched LAN devices with ports that provide connectivity to workstations and servers. In a WAN environment, the access layer for remote sites or teleworkers may provide access to the corporate network across WAN technology. Distribution layer: This layer aggregates the wiring closets and uses switches to segment workgroups and isolate network problems in a campus environment. Similarly, the distribution layer aggregates WAN connections at the edge of the campus and provides policy-based connectivity. Core layer (also referred to as the backbone): This layer is a high-speed backbone and is designed to switch packets as fast as possible. Because the core is critical for connectivity, it must provide a high level of availability and adapt to changes very quickly.
Note The hierarchical model can be applied to any network type: LAN, WAN, wireless LAN (WLAN), metropolitan-area networks (MAN), VPN, or any modular block of the Cisco networking model.
1-6
Example: Hierarchical Campus Model
ROUTE v1. 01-4
Example: Hierarchical Network Model WAN
ROUTE v1. 01-5
For example, the hierarchical model can be applied specifically to the enterprise campus. The hierarchical model can also be applied to the enterprise WAN. Obviously, another model is required to break down and analyze an existing modern enterprise network or plan a new one.
1-7
Enterprise Composite Network Model Functional Areas
ROUTE v1. 01-6
Since intelligent network service security has become of critical importance to all network planning and implementation, Cisco has developed a set of best practices for security called the Cisco SAFE Blueprint. SAFE helps network designers and administrators properly deploy security solutions to support network solutions and the existing network infrastructure. SAFE includes the Enterprise Composite Network Model, which can be used by network professionals to describe and analyze any modern enterprise network. Three functional areas are defined by the model: Enterprise Campus: This functional area contains the modules required to build a hierarchical, highly robust campus network. Access, distribution, and core principles are applied to these modules. Enterprise Edge: This functional area aggregates connectivity from the various elements at the edge of the enterprise network. It provides a description of connectivity to remote locations, the Internet, and remote users. Service Provider Edge: This area provides a description of connectivity to service providers such as Internet service providers (ISPs), WAN providers, and the public switched telephone network (PSTN).
1-8
Enterprise Composite Network Model
ROUTE v1. 01-7
Various modules form an integrated converged network that supports business processes. As shown in the figure, the campus comprises six modules: Building, with access switches and end devices (PCs and IP phones) Building distribution, with distribution multilayer switches Core, sometimes called the backbone Edge distribution, which concentrates all branches and teleworkers accessing the campus via WAN or Internet Server farm, which represents the data center Management, which represents the network management functionality Additional modules in the other functional areas represent e-commerce functionality, corporate Internet connections, remote access and VPN connections, and traditional WAN (Frame Relay, ATM, and leased lines with PPP) connections.
1-9
Traffic Conditions in a Converged Network

This topic describes the traffic types and requirements in converged networks.
Network Traffic Mix

Converged network traffic mix:
Voice and video traffic Voice applications traffic Mission-critical applications traffic Transactional traffic Routing update traffic Network management traffic
ROUTE v1. 01-8
Converged networks with integrated voice, video, and data contain various traffic patterns: Voice and video traffic, for example, IP telephony, and video broadcast and conferencing Voice applications traffic, generated by voice-related applications (such as contact centers) Mission-critical traffic, generated, for example, by stock exchange applications Transactional traffic, generated by e-commerce applications Routing update traffic, from routing protocols like Routing Information Protocol (RIP), Open Shortest Path First Protocol (OSPF), Enhanced Interior Gateway Routing Protocol (EIGRP), Intermediate System-to-Intermediate System (IS-IS) Protocol, and Border Gateway Protocol (BGP) Network management traffic
1-10
Network Requirements
Key requirements:
Performance Bandwidth Delay Jitter Security Access Transmission
ROUTE v1. 01-9
The diversity of the traffic mix poses stringent requirements on the network in terms of performance and security. The requirements significantly differ, depending on the traffic type. For example, voice and video require constant bandwidth and low delay and jitter, while transactional traffic requires high reliability and security with relatively low bandwidth. Video traffic is frequently carried as IP multicast traffic. Also, voice applications such as IP telephony require high reliability and availability, because the user expectations for a dial tone in the IP network are exactly the same as in traditional phone network. To meet the traffic requirements in the network, for example, voice and video traffic must be treated differently from other traffic, such as web-based traffic. QoS mechanisms are mandatory in converged networks. Security is a key issue not only for fixed networks but also wireless mobility, for which access to the network is possible from virtually anywhere. Several security strategies, such as device hardening with strict access control and authentication, intrusion protection, intrusion detection, traffic protection with encryption, and so on can minimize or even eliminate network security threats.
1-11
Example: Enterprise network
RO UTE v 1.01-10
The figure above shows a hierarchical enterprise network with some remote offices. In such environments, many different traffic types exist. IP telephony is used as well as video applications, which add a lot of delay to time-sensitive (VoIP) and bandwidth-consuming (video) traffic streams. Server farms contain storage for mission-critical data and e-commerce applications generating transactional traffic. Traffic toward the server farm requires fast transport and bandwidth guarantees. You must have remote and Internet-connectivity Layer 3 devices sending updates in order to efficiently route traffic. Network design and configuration must be able to provide guaranteed services for all this traffic and satisfy the requirements for performance and security.
1-12
Cisco SONA Framework

This topic describes Cisco SONA, which guides an evolution of enterprise networks toward an IIN. The IIN and its features are also described in this section.
Cisco SONA Framework

Cisco Service-Oriented Network Architecture (SONA) is an architectural framework. Cisco SONA brings several advantages to enterprises: Outlines how enterprises can evolve toward the Intelligent Information Network (IIN) Illustrates how to build integrated systems across a fully converged intelligent network Improves flexibility and increases efficiency Optimizes applications, processes, and resources
RO UTE v 1.01-11
Cisco is helping organizations address new IT challenges, such as the deployment of serviceoriented architectures, web services, and virtualization. Cisco SONA is an architectural framework that guides the evolution of enterprise networks to an IIN. The Cisco SONA framework provides several advantages to enterprises: Outlines the path toward the IIN Illustrates how to build integrated systems across a fully converged IIN Improves flexibility and increases efficiency, which results in optimized applications, processes, and resources Cisco SONA uses the extensive product line services, proven architectures, and the experience of Cisco and its partners to help enterprises achieve their business goals.
1-13
Cisco SONA Framework Layers
RO UTE v 1.01-12
The Cisco SONA framework shows how integrated systems can both allow for a dynamic, flexible architecture and provide for operational efficiency through standardization and virtualization. It centers on the concept that the network is the common element that connects and enables all components of the IT infrastructure. Cisco SONA outlines these three layers of the IIN: Networked infrastructure layer: This layer is where all of the IT resources are interconnected across a converged network foundation. The IT resources include servers, storage, and clients. The network infrastructure layer represents how these resources exist in different places in the network, including the campus, branch, data center, WAN and MAN, and teleworker. The objective for customers in this layer is to have anywhere and anytime connectivity. Interactive services layer: This layer enables efficient allocation of resources to applications and business processes delivered through the networked infrastructure. This layer comprises these services: Voice and collaboration services Mobility services Security and identity services Storage services Computer services Application networking services Network infrastructure virtualization Services management Adaptive management services
1-14
Application layer: This layer includes business applications and collaboration applications. The objective for customers in this layer is to meet business requirements and achieve efficiencies by leveraging the interactive services layer.
1-15
Intelligent Information Network

IIN integrates networked resources and information assets. IIN extends intelligence across multiple products and infrastructure layers. IIN actively participates in the delivery of services and applications. Three phases in building an IIN are: Integrated transport Integrated services Integrated applications
RO UTE v 1.01-13
The Cisco vision of the future of the Intelligent Information Network (IIN) encompasses these features: Integration of networked resources and information assets that have been largely unlinked: Modern converged networks with integrated voice, video, and data require that IT departments more closely link the IT infrastructure with the network. Intelligence across multiple products and infrastructure layers: The intelligence built into each component of the network is extended network-wide and applies end to end. Active participation of the network in the delivery of services and applications: With added intelligence, the IIN makes it possible for the network to actively manage, monitor, and optimize service and application delivery across the entire IT environment. With the listed features, the IIN offers much more than basic connectivity, bandwidth for users, and access to applications. The IIN offers end-to-end functionality and centralized, unified control that promotes true business transparency and agility. The IIN technology vision offers an evolutionary approach that consists of three phases in which functionality can be added to the infrastructure as required: Integrated transport: Everything, including data, voice, and video, is consolidated onto an IP network for secure network convergence. By integrating data, voice, and video transport into a single, standards-based, modular network, organizations can simplify network management and generate enterprise-wide efficiencies. Network convergence also lays the foundation for a new class of IP-enabled applications delivered through Cisco Unified Communications solutions.
1-16
Integrated services: Once the network infrastructure has been converged, IT resources can be pooled and shared or virtualized to flexibly address the changing needs of the organization. Integrated services help to unify common elements, such as storage and data center server capacity. By extending virtualization capabilities to encompass server, storage, and network elements, an organization can transparently use all of its resources more efficiently. Business continuity is also enhanced because shared resources across the IIN provide services in the event of a local systems failure. Integrated applications: With Cisco Application-Oriented Networking (AON) technology, Cisco has entered the third phase of building the IIN. This phase focuses on making the network application-aware so that it can optimize application performance and more efficiently deliver networked applications to users. In addition to capabilities such as content caching, load balancing, and application-level security, Cisco AON Software makes it possible for the network to simplify the application infrastructure by integrating intelligent application message handling, optimization, and security into the existing network.
1-17
Example: Enterprise Network

Networked infrastructure layer Interactive services layer Application layer
RO UTE v 1.01-14
The figure above shows a hierarchical enterprise network with some remote offices. Segmentation can be done to three basic layers of SONA: Networked infrastructure layer Interactive services layer Application layer The networked infrastructure layer represents the physical infrastructurethe combination of network, servers, clients, and storage hardware that is deployed throughout an enterprise network. The interactive services layer represents the network-based functionality by making resources available to applications and business processes. Application delivery, real-time communication, management, mobility, security, transport, and virtualization are parts of the interactive services layer. The application layer represents the enterprise software that addresses the needs of organizational processes and data flow, often in a large, distributed environment.
1-18
Routing and Routing Protocols

This topic describes routing and routing protocols.
Routing Protocols
RO UTE v 1.01-15
To review, the focus of this course is on selecting, planning, implementing, tuning, and troubleshooting IP advanced routing protocols. This is a technical course at the level of Cisco CCNP. All of the models and tools described previously are important in the initial part of the process of selecting and planning. The best practice is to use one IP routing protocol throughout the enterprise if possible. In many cases, this practice is not possible, which will be discussed in detail in another module. For example, Border Gateway Protocol (BGP) will be a factor in the Corporate Internet and ECommerce modules if multihomed to ISPs is implemented. You will usually use static routes for remote access and VPN users. Therefore, you are likely to have to deal with multiple routing protocols. The Enterprise Composite Network Model can assist in determining where each routing protocol is implemented, where the boundaries are, and how traffic flows are managed. It is obvious that advanced IP routing protocols must be implemented in all core networks to support high availability requirements. Less advanced routing protocols (such as RIP) and static routes may exist at the access and distribution levels within modules.
1-19
Routing Protocol Comparison

Parameters
Size of Network (Small-Medium-Large-Very Large) Speed of Convergence (Very High-High-Medium-Low) Use of VLSM (Yes-No) Mixed-Vendor Devices (Yes-No) Network Support Staff Knowledge (Good-Fair-Poor)
EIGRP
Large
OSPF
Large
BGP
Very Large
Very High
High
Low
Yes
Yes
Yes
No
Yes
Yes
Good
Good
Fair
RO UTE v 1.01-16
This table provides a simple comparison of three IP routing protocols. The remainder of this course consists of technical details for each of these.
1-20
Example: Enterprise Network
EIGRP is used as IGP BGP is used as EGP Static routes for remote access and VPN
RO UTE v 1.01-17
Based on a best practice, one IP routing protocol has been selected throughout the whole enterprise network in the figure above. Enterprise networks usually employ an Interior Gateway Protocol (IGP) such as RIP, EIGRP, or OSPF for the exchange of routing information within their networks. EIGRP has been used in the example above, as it has very fast convergence and supports a large network size. The network in the figure above has Internet connectivity in which multihoming with multiple routers has been implemented. For such interautonomous system connectivity, an Exterior Gateway Protocol (EGP) is used. BGP is an example of an EGP protocol, is selected above. It supports very large networks and has excellent traffic policy options. Besides advanced IP routing protocols supporting high availability requirements, static routes exist at the access and distribution levels for remote and VPN access.
1-21
Summary
This topic summarizes the key points that were discussed in this lesson.
Summary
Cisco Enterprise Architectures with hierarchical network models facilitate the deployment of converged networks. Converged networks with their traffic mix have higher demands on the network and its resources. The SONA framework guides the evolution of the enterprise network toward the IIN. The network models can be important tools for selecting and implementing an advanced IP routing protocol.
RO UTE v 1.01-18
1-22
Lesson 2
Creating an Implementation Plan and Documenting the Implementation

Overview
An implementation plan and its documentation are a result of good processes and procedures during network design, implementation, and performance testing. This lesson assesses a provided network design, identifies network requirements, creates an implementation plan, and provides guidelines for creating the documentation. To create an implementation plan, you must have detailed network information, tools, resources, and a work plan. By selecting the proper tools and resources, as well as a plan of work, you can make implementation of the network is faster, more cost-effective, and capable of meeting high industry standards.
Objectives
Upon completion of this lesson, you will be able to describe the requirements of the enterprise network, implementation plan, and documentation of the implementation process, as well as describe their results. These abilities include being able to meet these objectives: Create an implementation plan Define the implementation plan tasks Develop the implementation plan documentation Create an implementation plan example
Creating an Implementation Plan

This topic describes the steps required to create a typical implementation plan, the types of information it contains and types of tasks within it.
Implementing Routing in the Network

Ad-hoc approach
Identify the need for the implementation Implement routing in the network
Structured approach
Create an implementation plan Implement the solution Document the implementation
ROUTE v1. 01-2
How is the implementation of routing protocols performed? For any other process, the following options exist: Ad-hoc approach Structured approach In an ad-hoc approach, the network engineer identifies the need for routing protocol implementation and implements the solution without planning any of the tasks. If the size of the network is increasing, new equipment and remote offices are added to its administration. Many activities such as connectivity, routing, and security, are required. The network engineer can simply examine and configure the required functionalities as they arrive. Scalability issues, suboptimal routing, and security issues are more likely to occur with this approach. A good implementation plan is required to avoid such difficulties. In a structured approach, the network engineer identifies the need for a routing protocol implementation and starts with planning first. Based on the existing topology, the engineer reviews all new changes, taking into account many aspects of the implementation. The engineer defines a new topology, including an IP addressing plan, scalability issues, link utilization, remote network connectivity, and other network parameters. The engineer does not review the technical aspect of the implementation only. The implementation plan must meet technical and business requirements as well. The engineer writes all details into the implementation plan documentation prior to the implementation. After the successful implementation he creates good documentation. This documentation includes the implementation plan itself, along with tools, resources, and implementation results.
1-24
Structured Approach
Well-known models and methodologies that can aid in structuring the network implementation tasks include the following:
Cisco Lifecycle Services (PPDIOO) IT Infrastructure Library (ITIL) Fault, Configuration, Accounting, Performance, and Security (FCAPS) Telecommunications Management Network (TMN)
Choose a model with elements that fit your organization as well as its business and technical needs.
ROUTE v1. 01-3
The implementation plan is part of the well-known models and methodologies of every IT company, which can help structure the network implementation task. These methodologies are generic models that categorize the lifecycle approach of each process and help provide highquality IT services. For many models and methodologies related to network implementation, network implementation with an implementation plan is just one of the building blocks. The following models are a few good examples: The Cisco Lifecycle Services approach defines the minimum set of activities needed, by technology and by network complexity, to help customers successfully deploy and operate Cisco technologies and optimize their performance throughout the lifecycle of the network. This approach is referred to as the PPDIOO model based on the six phases in the network lifecycle: Prepare, Plan, Design, Implement, Operate, and Optimize. The implementation plan is part of the Design phase and the implementation itself is part of the Implement phase. IT Infrastructure Library (ITIL) is a framework of best practices for IT service management that provides high quality IT services. IT services are aligned with business requirements and processes in IT. The implementation plan and implementation are part of ITIL best practices. The Fault, Configuration, Accounting, Performance, and Security (FCAPS) model was created by the International Organization for Standardization (ISO). It defines five categories as the minimum necessary for successful network management: configuration management, fault management, accounting management, performance management and security management. Both the implementation plan and implementation are in the configuration management category.
1-25
The Telecommunications Management Network (TMN) model is a protocol model similar to the FCAPS model and defines a framework for the management of telecommunication networks. The Telecommunications Standardization Sector (ITU-T) took the main aspects of the FCAPS model, refined them, and created a framework for which the implementation plan and implementation itself are one of the building blocks.
Note Each organization is different and has different requirements. Choose the model and elements that fit your organization and its business and technical needs.
1-26
Models and Tools

Select the implementation model Adapt the model to your organizations needs Select the tools supporting the model Create the implementation plan
ROUTE v1. 01-4
After you decide on a structured approach, you must choose a model and methodology.. You may combine different models to adapt the solution to fit requirements. The Cisco Lifecycle Services approach is a step-by-step approach for successfully deploying technology solutions; it will be used as an example throughout the course. Once you have selected an implementation model, you must adapt it to the needs of your organization. If you choose service components and define processes and procedures properly when creating your implementation plan, you can produce a successful implementation. You must select cost-effective tools to successfully deploy and optimize Cisco technologies. Once you collect the requirements, models, and tools. you must create the implementation plan. Then you can successfully implement the solution.
1-27
Implementation Plan Tasks

This topic describes the types of tasks that are detailed in a typical implementation plan.
Create the Implementation Plan

Identify the required information for the plan: Network-specific information, activities, and tasks Dependencies of the existing installation Recommended resources Create the implementation plan Implement the solution Verify the implementation Create the documentation
ROUTE v1. 01-5
During the design process you must clearly define the model and network and business requirements before you can create an implementation plan. Prior to developing the implementation plan, you must identify the following required information: Network-specific information, activities, and tasks associated with implementation plan development Dependencies of your implementation plan development on other service components Recommended resources to accomplish the activities and tasks associated with implementation plan development The next logical step is to develop the implementation plan, followed by implementation, verification, and creation of good documentation.
1-28
Identify the Required Network Information

Existing topology, equipment, and software version IP addressing plan Scalability configuration (summarization, stub areas, and so on) List of advertized networks Link utilization Metric requirements for primary and backup links
ROUTE v1. 01-6
One of your most important tasks is to identify network-specific information, because the implementation must support the topology and its requirements. You will likely need to change the existing network installation in order to have a successful implementation. The following network-specific information is required: Existing topology, equipment, software version IP addressing plan Scalability requirements (summarization, stub areas, and so on) List of advertised networks Link utilization Metric requirements for primary and backup links Based on the information above, the network engineer can decide about the tasks required. The existing network may not require topology, IP addressing, or any other changes. In a best case scenario, when the network is built following the Cisco recommended design, the new implementation is just an addition to the existing network.
1-29
Identify Other Requirements

Site specific implementation requirements Dependencies on existing installation Configuration and verification commands Implementation schedule and resources Tools
Online Resources
In addition to network information, there are many other requirements for the successful creation of an implementation plan and for implementation: Site-specific implementation requirements Dependencies on the existing installation Configuration and verification commands Implementation schedule and resources Tools
1-30
Create the Implementation Plan

Plan the work tasks Select the site-specific tools and configurations Configure and coordinate work with specialists Create verification tests
ROUTE v1. 01-8
After you gather network requirements, existing documentation, implementation schedule options, identified implementation risks, management plan, and roles and responsibilities implementation, you can create the plan. You must define and document the following tasks to create a site-specific implementation plan: Identify applications and devices to be implemented Identify installation tasks and checklists Create site-specific configurations Define site-specific installation tasks and checklists Define device configuration and software requirements Create installation verification tests
1-31
Implementation Plan Documentation

This topic describes the types of implementation information that should be documented and how to document them.
Implementation Plan Documentation

Good documentation is a result of good processes and procedures. Documentation must be: Correct Up-to-date Accessible Documentation must support: Future upgrades and changes Troubleshooting Reporting
ROUTE v1. 01-9
Creating and documenting an excellent implementation plan according to a well-known model and methodology is the first step for good documentation. Documentation must be correct and up-to-date as you will use it during the implementation process and during verification at the end. At the end of the implementation, you will add all verification steps and results to produce documentation that is useful for future processes. The documentation will provide the last known good status of the network and, together with all the details inside, will make it easy to create an implementation plan for future changes and upgrades in the network. At the same time, the documentation must be accessible. This is one of the requirements for a successful troubleshooting session. The documentation contains all of the information about the equipment, configuration, and known issues, as well as baseline, verification tasks, and their results. Having good documentation available to a troubleshooting engineer at any time is essential to ensuring efficient troubleshooting. If the IT department needs to create a report, the documentation can support the information in the report, because it contains all the tasks performed, the schedule, and the resources involved.
1-32
What to Document?
Network information Tools Resources Implementation plan tasks Verification tasks Performance measurement and results Screenshots and photos
RO UTE v 1.01-10
The documentation consists of: Network information Tools Resources Implementation plan tasks Verification tasks Performance measurement and results Screenshots and photos Each part of the documentation presents its own phase of the network lifecycle implementation and verification process. The documentation creation process cannot be finished in one step; it is not finished until the end of the project. The process starts with the implementation plan, which describes all the tasks needed and ends with the verification steps. The typical process when creating documentation includes creating a template and adding information to it during every step of the implementation process. Finally, several verification steps are required to verify that the information is correct. If a standard company template does not exist, then convert the documentation to the company standards and standard models and methodologies. At the end of the project, safely store the document, as it can be used at any time to review the network and determine when changes are required.
1-33
Implementation Plan Example

This topic describes how to assess a network design and create an implementation plan.
Example: Implementation Plan

Identify the existing situation and requirements Follow these steps to create an implementation plan: Plan Select the tools and resources Coordinate the work with specialists Verify Interpret the performance results Document the baseline, performance, and recommendation
RO UTE v 1.01-11
In order to create an implementation plan, you must define the existing situation and requirements correctly. Review the given network, select tools and resources, and create the implementation tasks required. The following steps are required during the creation of an implementation plan: Plan Select the tools and resources Coordinate work with specialists Verify Interpret performance results Document baseline, performance, and recommendations
1-34
Enterprise Network Topology Required
RO UTE v 1.01-12
The figure presents an enterprise network in which a hierarchical design is applied. The company would like to implement a scalable solution with a routing protocol that provides fast convergence. For optimal routing and packet forwarding, hierarchical addressing with summarization is required. Users require high-speed access to the server farm with redundant connectivity for protection. The company has many remote offices and a redundant connection to the Internet is required to provide the remote offices with nonstop access to its server farm. For remote offices, a secure connection must be implemented to prevent unauthorized persons from accessing data. Network professionals must review the existing topology and other network information needed to implement a new solution. Network professionals must take all requirements into account and create a complete implementation plan. They must document an implementation plan, along with the results of the verification tests.
1-35
Identify Network Information and Requirements

Existing topology, equipment, and software version IP addressing plan, configuration, and link utilization Requirements for: Connectivity and configuration Protection and optimization Security and remote access
RO UTE v 1.01-13
The first step before creating an implementation plan is to gather existing information about the network and all the requirements. The existing topology provides redundant connectivity among all of the network devices. Internet connectivity is dual-homed, which provides redundant access to the remote sites as well as World Wide Web resources. The equipment can provide all of the functionalities required, but the software version of the operation system must be upgraded. The networking equipment has existing IP addressing that need to be changed in order to ensure optimal routing and forwarding of packets as well as summarization. Requirements for server farm access and remote office connectivity do not include changes in the Quality of Service (QoS) configuration. The server farm hosts the companys critical applications. Aside from Voice over IP (VoIP), these applications require preferred treatment. Open Shortest Path First (OSPF) is configured in the network. This configuration must be changed, as a faster convergence time is required. The EIGRP routing protocol is a better selection. Security configuration is required to provide secure access to internal resources and to provide remote office connectivity. Existing security is sufficient and no changes are needed. After identification of network information, document all details and requirements, including: A list of equipment, topology (physical and logical), and design documents The current and required software versions The current configuration and documentation, such as for IP addressing, summarization, routing information, QoS, and security Site requirement specifications, including IP addressing, required software, topology changes, routing protocol requirements, QoS, and security.
1-36
Creation of the Implementation Plan

Create an implementation plan and document it Project contact list Location information Tasks and detailed descriptions Verification steps Representation of the results
RO UTE v 1.01-14
You must identify the current status of the network and current network requirements before creating the first part of documentation. You must then obtain the following information: Project contact list and statements of work Location information and means of accessing to the premises Tools and resources Assumptions Tasks and detailed descriptions Network Staging Plan The following examples show the typical content of an implementation plan and a description of each section. The project contact list introduces all of the people involved and their commitments.
1-37
Project Contact List

Cisco Project Team Project Manager: Telephone: Email: Project Engineer: Telephone: Email: Design Engineer: Telephone: Email: Account Manager: Telephone: Email: Systems Engineer: Telephone: Email: <Customer> Project Team Project Manager: Telephone: Email: Project Engineer: Telephone: Email: Design Engineer: Telephone: Email: Account Manager: Telephone: Email: Systems Engineer: Telephone: Email:
Location information and access details of the premises define where the equipment is located and how to reach it. Equipment Floor Plan
Location Floor Room Suite Position Rack No. Details
A tools description provides a list of tools that the implementation engineer will require to carry out the work detailed in this document.
1-38
Tools Required
Item No. 1. 2. 3. Item PC with a VT100 emulator, 10BaseT interface, FTP Server and TFTP Client applications Console port cable DB9-RJ45/DB25 10BaseT Ethernet cable
The implementation task list must provide a breakdown of the implementation process, followed by a detailed description of each activity. The output of each activity should be indicated on the implementation record. Implementation Tasks
Step No. 1. 2. 3. 4. 5. 6. Task Connect to the router Verify the current installation and create a backup file Change the Cisco IOS version on all devices Update the IP address configuration on distribution routers Configure EIGRP Verify the configuration and record the results
After the implementation plan is completed successfully, documentation must be created with all of the details, verification steps, and results.
1-39
Summary
Summary
Using well known models and methodologies can aid in structuring the network implementation tasks and creating an implementation plan. An implementation plan consists of the project and network overview, required tools, and information, as well as the implementation tasks. The tasks in the implementation plan provide a detailed explanation of all actions that must be taken in order to configure the network according to requirements. Good documentation is a result of good processes and procedures, and includes performance testing and documentation of results.
RO UTE v 1.01-15
1-40
Lesson 3
Lab 1-1 Debrief

Overview
In Lab 1-1, students create the implementation plan for routing protocol selection and implementation. The first part of the lab is focused on gathering requirements and required data. After a student successfully surveys the existing topology and gathers all of the data, the student must create an implementation plan, and then perform implementation and verification. The student must then document the project. After students complete the lab, the instructor will lead a discussion about lab topology, tasks, verification, and checkpoints. The instructor will also provide a sample solution and different alternatives. Students will present their implementation plans and solutions.
Objectives
Upon completing this lesson, you will be able to explain the gathering of network requirements and required data. You will be able to create an implementation plan, verify it, and document the whole process. This ability includes being able to meet these objectives: Complete the Lab Overview and Verification Describe a Sample Solution and Alternatives
Lab Overview and Verification

This topic describes lab topology and key checkpoints used to create a solution and to start with the verification.
Lab Topology
ROUTE v1. 01-2
The figure above presents the physical lab topology used for all labs in the Planning Routing Services course. The topology uses four pod routers, two switches, and backbone equipment. A physical lab is not needed for this lab, as the implementation plan is the theoretical part of each implementation. Implementation and verification make up the practical part, but will be practiced throughout the whole course. Based on the topology, students will create requirements, gather all of the data, and create implementation plans. Finally, they will describe and document the verification process.
1-42
Lab Review: What Did You Accomplish?

Task 1: Identify the requirements the network must meet What were the steps you took to identify the tasks and requirements? Task 2: Identify the required information Which tools did you need and where did you gather the application and data requirements? Where did you get the existing equipment and topology information? Who defined the routing protocols, scalability, and other configuration details? Task 3: Create an Implementation Plan How was documentation created and when?
ROUTE v1. 01-3
In the first task, you must identify the requirements the network has to meet to establish a foundation for the implementation plan. There are two common approaches to this. You can either define the requirements based on company needs, or gather the requirements from the network administrator. In the first approach, you must select the correct tools to be able to analyze the network and define the requirements in order to start gathering data and creating a good implementation plan. If you choose the second method, you can speed up the process and get the real requirements from the person who knows all the details of the network. In the second task, the requirements are defined, but the real data is missing. Again, you can do some research and collect all the necessary data using the different tools. As an option, two network administrators can provide all of the data. Then you can select the routing protocols, scalability options, and define other configuration details. With all of the details, you can create a good implementation plan, then implement, verify, and document the process.
1-43
Verification
Did you have enough information to create an implementation plan? Did you successfully finish the configuration of the network? What was the last step you did in the lab?
ROUTE v1. 01-4
A common approach to verifying the implementation process for a routing protocol is to follow the following steps: Evaluate if enough information was gathered in order to create a good implementation plan. Verify that the routing protocol configuration is successful. Create the documentation, which includes all the requirements, required data, implementation and verification steps, as well as implmentation results.
1-44
Checkpoints
Determine which tasks are needed to identify the requirements Document the requirements Gather the application and data requirements Gather the existing equipment, software version, and topology Define the IP addressing plan Select the routing protocols and define the scalability configuration Create the implementation plan and implement the solution Verify and document the implementation
ROUTE v1. 01-5
During the configuration and verification phase, a network operator can deal with several checkpoints. After completing all configuration tasks, the network operator can complete implementation of a routing protocol or perform additional verification and troubleshooting, as needed. Optionally, the network operator can check the creation of the implementation plan in different stages using checkpoints verifying each stage. With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Determine which tasks are needed to identify the requirements Document the requirements Gather the application and data requirements Gather the existing equipment, software version, and topology Define the IP addressing plan Select routing protocols and define scalability configuration Create an implementation plan and implement the solution Verify and document the implementation
1-45
Sample Solutions and Alternatives

This topic describes sample solution and other alternatives.
A Sample Solution
EIGRP AS 100, IP addressing with mask /24 and /30 for point-topoint links, the default route to Internet, summarization on routers R1 and R2, and no redistribution
ROUTE v1. 01-6
A sample solution includes the implementation details and the details for each task of the implementation plan. Different solutions are possible and the figure points out a few details of a successful configuration. A proper implementation of the routing protocol might include the following attributes: Implementation of EIGRP AS 100 IP addressing with mask /24 and /30 for point-to-point links An Internet gateway that uses the default route announced by routers BBR1 and BBR2 Implementation of summarization on routers R1 and R2; because only one routing protocol is used, there is no need for redistribution between different routing protocols.
Note As the purpose of lab 1-1 is for you to create an implementation plan, there is no single solution to the lab. The solution presented here is just a sample that satisfies the lab requirements.
1-46
Alternative Solutions
OSPF, IP addressing with mask /24 and /30 on peer-to-peer links, BGP and partial redistribution on BBR1 and BBR1, summarization on routers R1 and R2
ROUTE v1. 01-7
You can achieve the same or similar results by using different configuration steps and a different routing protocol. Instead of EIGRP, you can use the OSPF routing protocol. If you use multihoming and have your own BGP autonomous system number and public IP address space, you can run BGP on routers BBR1 and BBR2 instead of using the default route to the Internet. If you use more than one routing process, you may need to use redistribution or the default route.
Note As the purpose of lab 1-1 is for you to create an implementation plan, there is no single solution to the lab. The alternative solution presented here is just a sample that satisfies the lab requirements.
1-47
Q and A
Why is IP addressing important? Why is routing protocol selection important? Why is the implementation plan important? Why is verification important? What is the last and final step after the successful implementation of the routing protocol in the network?
ROUTE v1. 01-8
IP addressing is important because a good addressing plan makes redistribution and summarization possible. It also helps when a scalable solution is required. Routing protocol selection is important, because different organizations require different convergence speeds, levels of scalability, and levels of interoperability. EIGRP has a faster convergence speed than OSPF but OSPF might be more scalable in some cases. An implementation plan is needed in order to correctly implement the proper configuration. Sometimes the steps must be implemented in a specific order. Sometimes the number of steps is so high that without an implementation plan, it is likely that some details might be omitted accidentally. Verification follows implementation. It is important because it proves our concept and the configuration steps used. The final step before handover is the creation of documentation. Good documentation is required in order to implement and verify the network. It also helps later when upgrading and troubleshooting takes place.
1-48
Summary
Summary
Gather all the requirements and required data. Create a good implementation plan. Implement the network using the steps in the implementation plan. Verify and document the implementation.
ROUTE v1. 01-9
1-49
1-50
Module Summary
This topic summarizes the key points that were discussed in this module.
Module Summary
Cisco provides an enterprise-wide systems architecture that helps companies protect, optimize, and grow the infrastructure that supports their business processes. The architecture provides for integration of the entire networkcampuses, data centers, WANs, branches, and teleworkersoffering staff secure access to tools, processes, and services. The implementation plan and documentation are a result of good processes and procedures during network design, implementation and performance testing at the end.
ROUTE v1. 01-1
This module describes the Cisco conceptual models and architectures for converged networks. It examines the three tiers of the hierarchical network model in detail, the traffic conditions in a converged network, and the use of routing protocols. Additionally, it describes the creation of an implementation plan, for which the requirements and the required data provide a baseline to define all of the tasks required to produce a successful implementation. Verification after the implementation proves the concept, and documentation is created to finish the implementation process. .
1-51
1-52
Module Self-Check
Use the questions here to review what you learned in this module. The correct answers and solutions are found in the Module Self-Check Answer Key. Q1) Which three layers are parts of the Cisco hierarchical network model? (Choose three.) (Source: Assessing Complex Enterprise Network Requirements) A) B) C) D) E) Q2) Core Distribution Redistribution Access Workgroup
What is SAFE? (Source: Assessing Complex Enterprise Network Requirements) A) B) C) D) security protocol blueprint for network designers and administrators of best practices for the proper deployment of security solutions routing protocol authentication Cisco hierarchical network model white paper
Q3)
What are two key network requirements? (Choose two.) (Source: Assessing Complex Enterprise Network Requirements) A) B) C) D) performance security connectivity convergence speed
Q4)
Which advantage is not a SONA advantage for enterprises? (Source: Assessing Complex Enterprise Network Requirements) A) B) C) D) outlines how enterprises can evolve toward the IIN illustrates how to build integrated systems across a fully converged IIN improves flexibility and increases efficiency, which results in optimized applications, processes, and resources uses the limited product line services
Q5)
What are three SONA framework layers? (Source: Assessing Complex Enterprise Network Requirements) ______________________________________________________________________ ______________________________________________________________________ ______________________________________________________________________
Q6)
Which routing protocol supports a very high convergence speed and the use of VLSM? (Source: Assessing Complex Enterprise Network Requirements) A) B) C) D) EIGRP BGP OSPF RIP
1-53
Q7)
What are three main steps for a structured approach to implement routing in a network? (Choose three.) (Source: Creating an Implementation Plan and Documenting the Implementation) A) B) C) D) select the tools used for implementation create an implementation plan implement the solution document the implementation
Q8)
What is the name of the Cisco model and methodology that describes a structured approach to network implementation? (Source: Creating an Implementation Plan and Documenting the Implementation) A) B) C) D) Cisco Lifecycle Services Cisco ITIL Cisco FCAPS Cisco TMN
Q9)
Which three items must be identified prior to the creation of an implementation plan? (Choose three.) (Source: Creating an Implementation Plan and Documenting the Implementation) A) B) C) D) network-specific information, activities and tasks associated with the implementation plan development dependencies your implementation plan development has on other service components recommended resources to accomplish the activities and task associated with implementation plan development implementation plan and verification tasks
Q10)
What information must you know in order to create an implementation plan for EIGRP routing protocol? (Choose three.) (Source: Creating an Implementation Plan and Documenting the Implementation) A) B) C) D) existing topology, equipment, software version IP addressing plan and scalability requirements tools needed to evaluate application requirements list of advertized networks and metrics
Q11)
When changing the software version of the existing network infrastructure, Layer 3 devices are part of the implementation plan for routing protocols. (Source: Creating an Implementation Plan and Documenting the Implementation) A) B) true false
Q12)
What is not part of the implementation plan documentation for configuring a routing protocol in an enterprise network? (Source: Creating an Implementation Plan and Documenting the Implementation) A) B) C) D) E) tools future upgrade tasks implementation plan tasks verification tasks performance measurement and results
1-54
Q13)
Interpretation of performance results must be done prior to the verification steps within the implementation plan for routing protocols. (Source: Creating an Implementation Plan and Documenting the Implementation) A) B) true false
1-55
Module Self-Check Answer Key

Q1) Q2) Q3) Q4) Q5) Q6) Q7) Q8) Q9) Q10) Q11) Q12) Q13) A, B, D B A, B D Networked infrastructure layer, interactive services layer, application layer A B, C, D A A, B, C A, B, D A B B
1-56
Module 2
Implementing an EIGRPBased Solution

Overview
In routing environments, Enhanced Interior Gateway Routing Protocol (EIGRP) offers benefits and features over historical distance-vector routing protocols such as Routing Information Protocol version 1 (RIPv1). These benefits include rapid convergence, lower bandwidth utilization, and multiple routed protocol support besides IP. This module describes how EIGRP works and how to implement and verify EIGRP operations. It also explores advanced topics like route summarization, load balancing, EIGRP bandwidth usage, and authentication. The module concludes with a discussion of EIGRP issues and problems as well as how to correct them.
Module Objectives
Upon completing this module, you will be able to implement and verify EIGRP operations. This ability includes being able to meet these objectives: Identify the technologies, components, and metrics of EIGRP needed to implement routing in diverse, large-scale internetworks based on requirements. Configure EIGRP according to a given implementation plan and set of requirements. Discuss the lab results for configuring and verifying EIGRP operations. Configure and verify EIGRP over circuit emulation, MPLS VPNs, and Frame Relay for operational performance. Discuss the lab results for configuring and verifying EIGRP circuit emulation, MPLS VPNs, and Frame Relay operations. Configure and verify EIGRP authentication for operational performance. Discuss the lab results for configuring and verifying EIGRP authentication. Implement and verify the advanced EIGRP features in an Enterprise Network. Discuss the lab results for implementing and verifying EIGRP operations.
2-2
Lesson 1
Planning Routing Implementations with EIGRP

Overview
To select the appropriate routing protocols for an internetwork, you must understand the key features and terminology that are necessary to evaluate a given protocol against other choices. Routing protocols are distinguished from one another by the way that each selects the best pathway and the way that each calculates the routing protocol metric. Knowing the correct commands to use when you configure Enhanced Interior Gateway Routing Protocol (EIGRP) helps to ensure that the migration to this routing protocol is smooth and quick. This lesson reviews the benefits of EIGRP and discusses the key capabilities that distinguish EIGRP from other routing protocols, including the four underlying technologies within EIGRP. The three tables that EIGRP uses in the path selection process are described, and EIGRP metric calculation is explored in detail. An implementation plan is described as the first step in configuring EIGRP, followed by basic EIGRP configuration.
Objectives
Upon completing this lesson, you will be able to describe the components and metrics of EIGRP, how EIGRP selects routes between routers in diverse, large-scale internetworks, the implementation plan creation process, and basic EIGRP configuration. This ability includes being able to meet these objectives: List EIGRP capabilities and attributes. Define EIGRP operation and metrics. Plan and Document EIGRP. Implement Basic EIGRP.
EIGRP Capabilities and Attributes

Key capabilities that distinguish EIGRP from other routing protocols include fast convergence, support for variable-length subnet masking (VLSM), partial updates, and support for multiple network layer protocols. This topic describes these capabilities.
EIGRP Capabilities and Attributes

Advanced distance vector Multicast and unicast instead of broadcast address Support for multiple network-layer protocols 100% loop-free classless routing Fast convergence Partial updates Flexible network design
ROUTE v1. 02-2
EIGRP is a Cisco proprietary protocol that combines the advantages of link-state and distance vector routing protocols. EIGRP has its roots as a distance vector routing protocol and is predictable in its behavior. EIGRP is easy to configure and is adaptable to a wide variety of network topologies. The addition of several link-state features, such as dynamic neighbor discovery, makes EIGRP an advanced distance vector protocol. EIGRP is an enhanced IGRP because of its rapid convergence and the guarantee of a loop-free topology at all times. A hybrid protocol, EIGRP uses the Diffusing Update Algorithm (DUAL) and includes the following key features: Fast convergence: A router running EIGRP stores all of its neighbors routing tables so that it can quickly adapt to alternate routes. If no appropriate route exists, EIGRP queries its neighbors to discover an alternate route. These queries propagate until an alternate route is found. Partial updates: EIGRP does not send periodic updates. Instead, it sends partial triggered updates; these are sent only when the path or the metric changes for a route and contain information about only the changed routes. Propagation of partial updates is automatically bounded so that only those routers that need the information are updated. Because of these two capabilities, EIGRP consumes significantly less bandwidth. This behavior is different from link-state protocols, in which an update is transmitted to all link-state routers within an area. Multiple network-layer protocol support: EIGRP supports multiple network-layer protocols (for example IP) by using protocol-dependent modules. These modules are responsible for protocol requirements specific to the network layer. The rapid convergence and sophisticated metric structure of EIGRP offers superior performance and stability.
2-4 Implementing Cisco IP Routing (ROUTE) v1.0 2009 Cisco Systems, Inc.
Note
This course covers only the TCP/IP implementation of EIGRP.
Multicast and unicast: EIGRP uses multicast and unicast, rather than broadcast. The multicast address used for EIGRP is 224.0.0.10.
EIGRP Capabilities and Attributes (Cont.)

Support for VLSM and discontiguous subnets Load balancing across equal- and unequal-cost pathways Easy configuration for WANs and LANs Manual summarization at any point Sophisticated metric
ROUTE v1. 02-3
EIGRP features also include: VLSM support: EIGRP is a classless routing protocol, which means that it advertises a subnet mask for each destination network. This feature enables EIGRP to support discontinuous subnetworks and VLSM. With EIGRP, routes are automatically summarized at the major network number boundary, but EIGRP can be configured to summarize on any bit boundary on any router interface. Seamless connectivity across all data-link layer protocols and topologies: EIGRP does not require special configuration to work across any Layer 2 protocols. Other routing protocols, such as Open Shortest Path First (OSPF), use different configurations for different Layer 2 protocols, such as Ethernet and Frame Relay. EIGRP operates effectively in both LAN and WAN environments. WAN support for dedicated point-to-point links and nonbroadcast multiaccess (NBMA) topologies is standard for EIGRP. EIGRP accommodates differences in media types and speeds when neighbor adjacencies form across WAN links and can be configured to limit the amount of bandwidth that the protocol uses on WAN links. 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.
2-5
EIGRP Key Technologies

EIGRP Runs directly above the IP layer Neighbor discovery and recovery Uses Hello packets between neighbors Reliable Transport Protocol Guaranteed, ordered EIGRP packet delivery to all neighbors Used for flooding
88EIGRP 6TCP 17UDP
Frame Payload Frame Header IP Header Protocol Number Packet Payload
C R C
ROUTE v1. 02-4
EIGRP runs directly above the IP layer (protocol number 88) and employs four key technologies that combine to differentiate it from other routing technologies: neighbor discovery and recovery, reliable transport protocol, Diffusing Update Algorithm (DUAL) finite-state machines, and protocol-dependent modules. Neighbor discovery and recovery mechanism: This mechanism enables routers to learn dynamically about other routers on their directly-attached networks. Routers must also discover when their neighbors become unreachable or inoperative. This process is achieved with low overhead by periodically sending small hello packets. As long as a router receives hello packets from a neighboring router, it assumes that the neighbor is functioning and the two can exchange routing information. Reliable Transport Protocol: This protocol is responsible for guaranteed, ordered delivery of EIGRP packets to all neighbors. It supports intermixed transmission of multicast or unicast packets. For efficiency, only certain EIGRP packets are transmitted reliably. For example, on a multiaccess network that has multicast capabilities, such as Ethernet, it is not necessary to send hello packets reliably to all neighbors individually, so EIGRP sends a single multicast hello packet containing an indicator that informs the receivers that the packet need not be acknowledged. Other types of packets, such as updates, contain an indicator in the packet that acknowledgment is required. Reliable transport protocol contains a provision for sending multicast packets quickly, even when unacknowledged packets are pending. This provision helps ensure that convergence time remains low in the presence of varying link speeds. DUAL enables EIGRP routers to find out whether a path to the destination network is loopfree. DUAL allows a router running EIGRP to find alternate paths based on updates received from other routers..
2-6
Protocol-dependent modules are responsible for network layer protocol-specific requirements. The IP-EIGRP module is responsible for sending and receiving EIGRP packets, which are encapsulated in IP as well as for parsing EIGRP packets and informing DUAL of the new information that has been received. IP-EIGRP asks DUAL to make routing decisions, to put results in the IP routing table and to redistribute routes learned by other IP routing protocols.
2-7
EIGRP Operation and Metric

EIGRP uses the neighbor table to list adjacent routers. The topology table lists all the learned routes to each destination, while the routing table contains the best route to each destination. This best route is called the successor route. A feasible successor route is a backup route to a destination, which is kept in the topology table. This topic describes how EIGRP uses these tables and routes in its operation.
EIGRP Packets
Hello: Establish neighbor relationships Update: Send routing updates Query: Ask neighbors about routing information Reply: Respond to query about routing information ACK: Acknowledge a reliable packet

EIGRP uses the following five generic packet types: Hello: Routers use hello packets for neighbor discovery. The packets are sent as multicasts and do not require acknowledgments. Update: Update packets contain route change information. They are sent reliably to the affected routers only. These updates can be unicast to a specific router or multicast to multiple attached routers. Query: When a router performs a route computation and does not have a feasible successor, it sends a reliable query packet to its neighbors to determine if they have a feasible successor for the destination. Queries are normally multicast but can be retransmitted as unicast packets in certain cases. Reply: A router sends a reply packet in response to a query packet. Replies are unicast reliably to the originator of the query. ACK: The acknowledgment (ACK) packet acknowledges update, query, and reply packets. ACK packets are unicast hello packets and contain a nonzero acknowledgment number.
2-8
Initial Route Discovery
ROUTE v1. 02-6
The process to establish and discover neighbor routes occurs simultaneously with EIGRP. A high-level description of the process follows, using the topology in the figure as an example: 1. A new router (router R1) comes up on the link and sends a hello packet through all of its EIGRP-configured interfaces. 2. Routers receiving the hello packet (router R2) on one interface reply with update packets that contain all the routes they have in their routing tables, except those learned through that interface (split horizon). Router R2 sends an update packet to router R1, but a neighbor relationship is not established until router R2 sends a hello packet to router R1. The update packet from router R2 has the initialization bit set, indicating that this is the initialization process. The update packet includes information about the routes that the neighbor (router R2) is aware of, including the metric that the neighbor is advertising for each destination. 3. After both routers have exchanged hellos and the neighbor adjacency is established, router R1 replies to router R2 with an ACK packet, indicating that it received the update information. 4. Router R1 assimilates all update packets in its topology table. The topology table includes all destinations advertised by neighboring (adjacent) routers. It lists each destination, all the neighbors that can reach the destination, and their associated metric. 5. Router R1 then sends an update packet to router R2. 6. Upon receiving the update packet, router R2 sends an ACK packet to router R1. After routers R1 and R2 successfully receive the update packets from each other, they are ready to update their routing tables with the successor routes from the topology table.
2-9
EIGRP Neighbor Table

The list of directly connected routers running EIGRP with which this router has an adjacency
IP EIGRP Neighbor Table Next-Hop Router Interface
ROUTE v1. 02-7
When a router discovers and forms an adjacency with a new neighbor, it records the neighbors address and the interface through which it can be reached as an entry in the neighbor table. One neighbor table exists for each protocol-dependent module. The EIGRP neighbor table is comparable to the adjacencies database that link-state routing protocols use and serves the same purpose: to ensure bidirectional communication between each of the directly connected neighbors. When a neighbor sends a hello packet, it advertises a hold time, which is the amount of time that a router treats a neighbor as reachable and operational. If a hello packet is not received within the hold time, the hold time expires and DUAL is aware of the topology change. The neighbor-table entry also includes information required by the reliable transport protocol. Sequence numbers are employed to match acknowledgments with data packets, and the last sequence number received from the neighbor is recorded, so that out-of-order packets can be detected. A transmission list is used to queue packets for possible retransmission on a perneighbor basis. Round-trip timers are kept in the neighbor-table entry to estimate an optimal retransmission interval.
2-10
EIGRP Topology Table

The list of all routes learned from each EIGRP neighbor The source for the topology table: IP EIGRP Neighbor Table
IP EIGRP Topology Table Destination 1 FD and AD via Each Neighbor
ROUTE v1. 02-8
When the router dynamically discovers a new neighbor, it sends an update about the routes it knows to its new neighbor and receives the same from the new neighbor. These updates populate the topology table. The topology table contains all destinations advertised by neighboring routers. It is important to note that if a neighbor is advertising a destination, it must be using that route to forward packets; this rule must be strictly followed by all distance vector protocols. The topology table also maintains the metric that each neighbor advertises for each destination, the advertised distance (AD), and the metric that this router would use to reach the destination via that neighbor, the feasible distance (FD). The FD is the cost for this router to reach the neighbor for this destination, plus the neighbors metric to reach the destination. The topology table is updated when a directly connected route or interface changes or when a neighboring router reports a change to a route. A topology-table entry for a destination can be in one of two states: active or passive. A destination is in the passive state when the router is not performing a recomputation; it is in the active state when the router is performing a recomputation. If feasible successors are always available, a destination never has to go into the active state, thereby avoiding a recomputation. The desired state is the passive state. A recomputation occurs when a destination has no feasible successors. The router initiates the recomputation by sending a query packet to each of its neighboring routers. If the neighboring router has a route for the destination, it sends a reply packet; if it does not have a route, it sends a query packet to its neighbors. In this case, the route is also in the active state in the neighboring router. While a destination is in the active state, a router cannot change the destinations routing table information. After a router has received a reply from each neighboring router, the topology-table entry for the destination returns to the passive state, and the router can select a successor.
2-11
EIGRP IP Routing Table

The list of all best routes from the EIGRP topology table and other routing processes The source for the EIGRP routes in an IP routing table: IP EIGRP Topology Table
The IP Routing Table Destination 1 Best Route
ROUTE v1. 02-9
A router compares all FDs to reach a specific network, then selects the route with the lowest FD and places it in the IP routing table; this is called the successor route. The FD for the chosen route becomes the EIGRP routing metric to reach that network in the routing table.
2-12
Example: EIGRP Tables
RO UTE v 1.02-10
Example: EIGRP Tables

The network shown illustrates the EIGRP tables; router R3s tables are displayed. Routers R1 and R2 have established a neighbor relationship with router R3 and have sent their routing tables to router R3. Both routers R1 and R2 have paths to network 10.1.1.0/24, among many others that are not shown. The routing table on router R1 has an EIGRP metric of 1000 for 10.1.1.0/24, so router R1 advertises 10.1.1.0/24 to router R3 with a metric of 1000. Router R3 installs the route to 10.1.1.0/24 via router R1 in its EIGRP topology table with an advertised distance of 1000. Router R2 has network 10.1.1.0/24 with a metric of 1500 in its IP routing table, so router R2 advertises 10.1.1.0/24 to router R3 with an advertised distance of 1500. Router R3 places the route to 10.1.1.0/24 network via router R2 in the EIGRP topology table with an advertised distance of 1500. Therefore, router R3 has two entries to reach 10.1.1.0/24 in its topology table. The EIGRP metric for router R3 to reach both routers R1 and R2 is 1000. This cost (1000) is added to the respective advertised distance from each router, resulting in the feasible distances from router R3 to reach network 10.1.1.0/24 shown in the figure. Router R3 chooses the least-cost feasible distance, which is 2000, via router R1, and installs it in the IP routing table as the best route to reach 10.1.1.0/24. The EIGRP metric in the routing table is equal to the feasible distance from the EIGRP topology table. Router R1 is the successor for the route to 10.1.1.0/24.
2-13
DUAL Terminology
Upstream and downstream router Selects lowest-cost loop-free paths to each destination Advertised Distance (AD) = next-hop router-destination Feasible Distance (FD) = local router cost + AD Lowest-cost = lowest FD (Current) successor = next-hop router with the lowest-FD-cost loop-free path Feasible successor = backup router with loop-free path (its AD < current successor FD)
RO UTE v 1.02-11
DUAL uses the distance information, known as a metric or cost, to select efficient, loop-free paths. The lowest-cost route is calculated by adding the cost between the next-hop router and the destinationreferred to as the advertised distance (AD)to the cost between the local router and the next-hop router. The sum of these costs is referred to as the feasible distance (FD). A successor, also called a current successor, is a neighboring router that has a least-cost path to a destination (the lowest FD) that is guaranteed not to be part of a routing loop; successors are used for forwarding packets. Multiple successors can exist if they have the same FD. By default, up to four successors can be added to the routing table (the router can be configured to accept up to six per destination). As well as keeping least-cost paths, DUAL keeps backup paths to each destination. The nexthop router for a backup path is called the feasible successor. To qualify as a feasible successor, a next-hop router must have an AD less than the FD of the current successor route.
2-14
DUAL Operation
The topology table is changed when: The cost or state of a directly connected link changes An EIGRP packet (update, query, reply) is received A neighbor is lost DUAL computes an alternate path if the primary (successor) is lost Local computation: a feasible successor is present in the topologythe route is passive DUAL recomputation: no feasible successor is present in the topologythe route is active
RO UTE v 1.02-12
If the route via the successor becomes invalid (because of a topology change) or if a neighbor changes the metric, DUAL checks for a feasible successor to the destination route. If one is found, DUAL uses it, thereby avoiding the need to recompute the route. If no suitable feasible successor exists, a recomputation must occur to determine the new successor. Although a recomputation is not processor-intensive, it does affect convergence time, so it is best to avoid any unnecessary recomputations.
2-15
Example: Advertised Distance (AD)

Advertised distance is the distance (metric) to a destination as advertised by an upstream neighbor
Topology Table
Destination 10.0.0.0/8 10.0.0.0/8 10.0.0.0/8
Advertised Distance (AD) 20+10=30 1+10+10=21 100+20+10+10=140
Neighbor R8 R2 R4
RO UTE v 1.02-13
Example: Advertised Distance (AD)

The figure above shows an example of how the AD is calculated. Router R1 has several options available to reach network 10.0.0.0/8. Routers R2, R4, and R8 each send an update to router R1. Each update contains an AD, which is the cost that router is advertising to reach network 10.0.0.0/8.
2-16
Example: Feasible Distance (FD)

Lowest cost = lowest FD
Topology Table
Destination 10.0.0.0/8 10.0.0.0/8 10.0.0.0/8
Feasible Distance (FD) 100+20+10=130 100+1+10+10=121 100+100+20+10+10=240
Neighbor R8 R2 R4
RO UTE v 1.02-14
Example: Feasible Distance (FD)

The figure above shows an example of how the FD is calculated. Router R1 has several options available to reach network 10.0.0.0/8. Each update from the three neighbors has a different AD. By adding the cost of the local link to routers R2, R4, and R8 to the AD of each path, router R1 calculates the FD for each path to network 10.0.0.0/8.
2-17
Example: Successor and Feasible Successor

Advertised distance is the distance (metric) to a destination as advertised by an upstream neighbor
Router As Routing Table Destination 10.0.0.0/8 10.0.0.0/8 10.0.0.0/8

AD 30 21 140
FD 130 121 240
Neighbor R8 R2 R4
Status FS S
121
R2
RO UTE v 1.02-15
Example: Successor and Feasible Successor

The figure above shows the successor and feasible successor on router R1 to network 10.0.0.0/8. Three paths exist for network 10.0.0.0/8. The FD and AD values are calculated for all three pathsthe three candidates for the routing table. The candidate with the lowest FD value becomes the successor. If the AD for one of the remaining two candidates is lower than the FD on the successor route, then this candidate becomes a feasible successor. The route via router R2 becomes the successor. The route via router R8 becomes the feasible successor. Only the successor route goes into the routing table.
2-18
Example: Successor and Feasible Successor Solve Loop Issue

R1 receives information about 10.0.0./8 from R8 and R4 FD on R1 is smaller than AD from R4 and the update from R4 is not FS
RO UTE v 1.02-16
The scenario on this slide shows how the DUAL algorithm solves the EIGRP routing loop issue. Router R8 with an AD of 30 sends the routing update about network 10.0.0.0/8. Router R1 receives an update, calculates the FD value (130), and sends an update to both neighbors. Routers R1, R2, and R4 are in a loop, and the picture above shows the update sent to router R2, which comes back to router R1. The update travelled via routers R2 and R4, and the AD of the update received on router R1 is 330. The value is higher than the FD value (130) calculated from the original update received from router R8. Because the FD of the update coming from R8 is smaller than the AD in the update coming from router R4, the route from the second update does not become feasible successor. This way DUAL solves the routing loop issue.
2-19
EIGRP Metric
The use of metric components is represented by K values Metric components are: Bandwidth (K1) Delay (K3) Reliability (K4 and K5) Loading (K2) MTU is included in the update but not used for metric calculation
RO UTE v 1.02-17
EIGRP uses the composite metric to determine the best path. The metric can be based on five criteria, but EIGRP uses only two of these criteria by default: Bandwidth: The smallest bandwidth between source and destination Delay: The cumulative interface delay along the path The following criteria can be used, but are not recommended, because using them typically results in frequent recalculation of the topology table: Reliability: This value represents the worst reliability between source and destination, based on keepalives. Loading: This value represents the worst load on a link between the source and destination, computed based on the packet rate and the configured bandwidth of the interface. Maximum Transmission Unit (MTU): This represents the smallest MTU in the path. MTU is included in the EIGRP routing update but is not actually used in the metric calculation.
2-20
EIGRP Metric Calculation

By default, EIGRP metric: Metric = bandwidth (slowest link) + delay (sum of delays) Delay = sum of the delays in the path, in tens of microseconds, multiplied by 256. Bandwidth = [107 / (minimum bandwidth link along the path, in kilobits per second)] * 256 Formula with default K values (K1 = 1, K2 = 0, K3 = 1, K4 = 0, K5 = 0): Metric = [K1 * BW + ((K2 * BW) / (256 load)) + K3 * delay] If K5 not equal to 0: Metric = Metric * [K5 / (reliability + K4)] Note: Multiplication by 256 is because of older protocol.
2009 Cis co S y st em s, Inc. A ll right s reserved. RO UTE v 1.02-18
EIGRP calculates the metric by adding together weighted values of different variables of the link to the network in question. The default constant weight values are K1 = K3 = 1, and K2 = K4 = K5 = 0. In EIGRP metric calculations, when K5 is 0 (the default), variables (bandwidth, bandwidth divided by load, and delay) are weighted with the constants K1, K2, and K3. The following is the formula used: metric = (K1 * bandwidth )+ [(K2 * bandwidth) / (256 load)] + (K3 * delay) If these K values are equal to their defaults, the formula becomes the following: metric = (1 * bandwidth ) + [(0 * bandwidth) / (256 load)] + (1 * delay) metric = bandwidth + delay If K5 is not equal to 0, the following additional operation is performed: metric = metric * [K5 / (reliability + K4)] K values are carried in EIGRP hello packets. Mismatched K values can cause a neighbor to be reset (Only K1 and K3 are used, by default, in metric compilation.) These K values should be modified only after careful planning; changing these values can prevent your network from converging and is generally not recommended. The format of the delay and bandwidth values used for EIGRP metric calculations is different from those displayed by the show interface command. The EIGRP delay value is the sum of the delays in the path, in tens of microseconds, multiplied by 256. The show interface command displays delay in microseconds. The EIGRP bandwidth is calculated using the minimum bandwidth link along the path, in kilobits per second. The value 107 is divided by this value, and then the result is multiplied by 256, because of the older protocol.
2-21
Example: EIGRP Metrics Calculation

Path 1: R1 > R2 > R3 > R4 Least bandwidth = 64 [kb/s] Total delay = 2,000 + 2,000 + 2,000 [tens of microseconds] Metric = (1 * 107 / 64) * 256 + 1 * (2,000 + 2,000 + 2,000) * 256 = 40,000,000 + 1,536,000 = 41,536,000
RO UTE v 1.02-19
Example: EIGRP Metrics Calculation

Router R1 has two paths to reach networks behind router R4. The bandwidths (in kb/s) and the delays (in tens of microseconds) of the various links are also shown in the figure. The least bandwidth along the top path (R1 > R2 > R3 > R4) is 64 kb/s. The EIGRP bandwidth calculation for this path is as follows: Bandwidth = (107 / least bandwidth in kb/s) * 256 Bandwidth = (10,000,000 / 64) * 256 = 156,250 * 256 = 40,000,000 The delay through the top path is as follows: Delay = [(delay R1 R2) + (delay R2 R3) + (delay R3 R4)] * 256
Delay = [2000 + 2000 + 2000] * 256 Delay = 1,536,000 Therefore, the EIGRP metric calculation for the top path is as follows: Metric = bandwidth + delay Metric = 40,000,000 + 1,536,000 Metric = 41,536,000
2-22
Example: EIGRP Metrics Calculation (Cont.)

Path 2: R1 > R5 > R6 > R7 > R4 Least bandwidth = 256 [kb/s] Total delay = 2,000 + 2,000 + 2,000 + 2,000 [tens of microseconds] Metric = (1 * 107 / 256) * 256 + 1 * (2,000 + 2,000 + 2,000 + 2,000) * 256 = 10,000,000 + 2,048,000 = 12,048,000
RO UTE v 1.02-20
The least bandwidth along the lower path (R1 R5 R6 EIGRP bandwidth calculation for this path is as follows: Bandwidth = (107 / least bandwidth in kb/s) * 256 Bandwidth = (10,000,000 / 256) * 256 = 10,000,000 The delay through the lower path is as follows: Delay = [(delay R1 256 R5) + (delay R5
R7
R4) is 256 kb/s. The
R6) + (delay R6
R7) + (delay R7
R4)] *
Delay = [2000 + 2000 + 2000 + 2000] * 256 Delay = 2,048,000 Therefore, the EIGRP metric calculation for the lower path is as follows: Metric = bandwidth + delay Metric = 10,000,000 + 2,048,000 Metric = 12,048,000 Router R1 therefore chooses the lower path, with a metric of 12,048,000 over the top path, with a metric of 41,536,000. Router R1 installs the lower path, with a next-hop router of R5 and a metric of 12,048,000, in the IP routing table. The bottleneck along the top path, the 64-kb/s link, can explain why the router takes the lower path. This slow link means that the rate of transfer to Router R4 can be at a maximum of 64 kb/s. Along the lower path, the lowest speed is 256 kb/s, meaning the throughput rate can be as high as that speed. Therefore, the lower path represents a better choice, for example, for moving large files quickly.
2-23
Planning and Documenting for EIGRP

This topic describes how to plan, implement, and document the EIGRP deployment.
Planning for EIGRP

Assess the requirements and options: IP addressing plan Network topology Primary versus backup links WAN bandwidth utilization Define hierarchical network design Evaluate EIGRP scaling options Summarization: where necessary EIGRP stub
RO UTE v 1.02-21
The EIGRP routing protocol implementation depends on specific needs and topologies. When preparing to deploy EIGRP routing in a network, the existing state and requirements first need to be gathered and different deployment options considered: The IP addressing plan determines how EIGRP can be deployed and how well the EIGRP deployment might scale. Thus, a detailed IP addressing plan along with IP subnetting information must be collected. A solid IP addressing plan should enable the usage of EIGRP summarization, making it easier to scale the network and optimize EIGRP behavior. A network topology consists of links connecting the network equipment (routers, switches, and so on). A detailed network topology plan should be presented, in order to assess EIGRP scalability requirements and determine which EIGRP features might be required (for example EIGRP stub routing). EIGRP can be used to employ traffic engineering, which helps with efficient bandwidth utilization and enables the administrator to have control over the traffic patterns. By changing the interface metrics, EIGRP traffic engineering can be deployed to improve bandwidth utilization.
2-24
EIGRP Implementation Plan

Verify and configure IP addressing Enable EIGRP using the correct AS number Define networks to include per router Define a special metric to influence path selection
Router R1 Networks 10.1.1.0
Router
R1
Link
Fa0
Metric
Bandwidth = 10 Mb/s
RO UTE v 1.02-22
Once you have assessed the requirements, you can create the implementation plan. The information necessary to implement EIGRP routing is: The IP addresses (or, more precisely, the networks) that need to be included and advertised by EIGRP The correct autonomous system (AS) number used to enable the EIGRP process, which must be the same on the routers in the EIGRP domain. A list of routers where EIGRP must be enabled, along with the connected networks that need to be advertised (per individual router) A listing in the table of any specific metric that needs to be applied to certain interfaces in order to deploy EIGRP traffic engineering, along with the interface where the metric needs to be applied When an implementation plan is created, a list of tasks for each router in the network must be defined: Enable the EIGRP routing protocol. Configure the proper network statements based on the information collected. You can also apply the metric to proper interfaces, if you wish. After implementation, you should confirm that EIGRP is deployed properly on each router: Verify the setup of the EIGRP neighbor relationship or relationships. Verify that the EIGRP topology table is populated with the necessary information. Verify that the IP routing table is populated with the necessary information. Verify that there is connectivity in the network. Verify that EIGRP behaves as expected when the topology changes (test link failure and router failure events).
2009 Cisco Systems, Inc. Implementing an EIGRP-Based Solution 2-25
Documenting EIGRP
Documenting EIGRP Topologyuse topology map AS numbering and IP addressing Networks included in EIGRP per routers Non-default metric applied
Router R1 networks Router R2 10.1.1.0 networks 10.1.2.0 Router R3 10.2.1.0 networks ...
10.2.2.0 10.3.1.0 ... 10.3.2.0 ...
Router
R1 R2 R2 R2
Link
Fa0 Serial1 Serial2 Tunnel
Metric
Bandwidth = 10 Mb/s Delay = 100 Delay = 200 Bandwidth = 2 Mb/s
RO UTE v 1.02-23
After a successful EIGRP deployment, you should document the solution in order to keep the information about the deployment available for future reference. The implementation plan itself is only half of the information. In order to complete the documentation, you must include the verification process and its results, as well.
2-26
Implementing Basic EIGRP

This topic describes how to plan and implement the basic EIGRP configuration.
Example: Planning for Basic EIGRP

Define the network requirements Gather the required parameters Define EIGRP routing Configure basic EIGRP Verify EIGRP configuration
RO UTE v 1.02-24
For the example in the figure above, prepare an implementation plan to configure basic EIGRP and proceed with the configuration. When you plan for the basic EIGRP configuration, you must ensure that your plan includes the: Define the network requirements Gather the required parameters Define the EIGRP routing Configure the basic EIGRP Verify the EIGRP configuration
2-27
Requirements for Basic EIGRP Configuration

EIGRP routing protocol AS number Interfaces for EIGRP neighbor relationship Networks participating in EIGRP Interface bandwidth
RO UTE v 1.02-25
The network in the figure consists of three routers. Routers R1 and R2 are in the same EIGRP autonomous system (AS). Router R3 represents an external network that is not part of the EIGRP AS 110. Requirements for the basic EIGRP configuration are: EIGRP routing protocol AS number: Routers in the same EIGRP domain must have the same AS number, as each EIGRP process must be started with the same AS number. The AS number 110 is used in our example. Interfaces for EIGRP neighbor relationship: Interfaces included in the EIGRP routing protocol will exchange routing updates and other packets between their neighbors. You must define the interfaces to show which networks are part of the EIGRP process. Both routers (R1 and R2) have one serial and one Fast Ethernet interface included in the EIGRP process. IP addressing is defined as listed in the figure. Networks participating in EIGRP: EIGRP routers must advertise their local networks to all neighbors. All the interfaces and their networks must be defined. Both routers (R1 and R2) are advertising directly to connected networks that are part of the EIGRP domain. Interface Bandwidth: Interface bandwidth is changing the metric of the link. In order to influence path selection, interface bandwidth must be defined properly. The real bandwidth on the serial link between routers R1 and R2 is 512 kb/s and the proper configuration must be applied in order to reflect the real bandwidth. This will result in proper selection of preferred routes in the EIGRP process.
Note Default bandwidth for a serial interface is 1544 kb/s.
2-28
Steps to Configure Basic EIGRP

Define EIGRP as a routing protocol Define the attached networks participating in EIGRP Define the interface bandwidth
RO UTE v 1.02-26
Once you have defined all of the required information, an implementation plan showing the following tasks is required to configure a basic EIGRP configuration: Define EIGRP as a routing protocol Define the attached networks participating in EIGRP Define the interface bandwidth
2-29
Define EIGRP as a Routing Protocol

Define EIGRP as the routing protocol All routers in the internetwork that must exchange EIGRP routing updates must have the same autonomous system number
RO UTE v 1.02-27
During the first step of a basic EIGRP configuration, you must define EIGRP as a routing protocol. You must specify an AS number that identifies the routes to the other EIGRP routers. Be aware that all routers in the same EIGRP domain must have the same AS number. Use the router eigrp 110 command to configure the EIGRP routing protocol and add any subsequent subcommands belonging to this routing process. This command also identifies the local AS to which this router belongs. AS 110 is used as an example. The command enters router configuration mode.
Note You can configure more than one EIGRP autonomous system on the same router, but you should configure only one EIGRP autonomous system in any single autonomous system.
For more details about the router eigrp command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-30
Define Networks Participating in EIGRP

Define the attached networks participating in EIGRP The wildcard-mask is an inverse mask used to determine how to interpret the address. The mask has wildcard bits, where 0 is a match and 1 is do not care.
RO UTE v 1.02-28
In order to start sending and receiving EIGRP routing updates, networks of directly connected interfaces must be defined. Only the network statements for interfaces where the router will send and receive updates need to be configured. Use the network 172.16.1.0 0.0.0.255 command in router configuration mode to specify the network for an EIGRP routing process. When the network command is configured for an EIGRP routing process, the router matches one or more local interfaces. The network command matches only local interfaces that are configured with addresses that are within the same subnet as the address that has been configured with the network command. The router then establishes neighbors through the matched interfaces. There is no limit to the number of network statements (network commands) that you can configure on a router.
Note The wildcard mask in the network command is optional. It is an inverse mask used to determine how to interpret the network number. The mask has wildcard bits, where 0 indicates a match and 1 indicates the bits which are not relevant. For example, 0.0.255.255 indicates a match in the first two octets.
For more details about the network (EIGRP) command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-31
Define Interface Bandwidth

Define the bandwidth on the serial0/0/1 interface for the purpose of sending routing update traffic
RO UTE v 1.02-29
EIGRP uses the minimum path bandwidth to determine a routing metric. The TCP protocol adjusts the initial retransmission parameters based on the apparent bandwidth of the outgoing interface. Use the bandwidth 512 command in interface configuration mode to specify or change the informational value used for an EIGRP routing process. If you do not change the bandwidth for the interfaces, EIGRP assumes that the default bandwidth on the serial link is the T1. If the link is actually slower, the router might not be able to converge or routing updates might be lost. The bandwidth command sets an informational parameter only; you cannot adjust the actual bandwidth of an interface with this command. For some media, such as Ethernet, the bandwidth is fixed; for other media, such as serial lines, you can change the actual bandwidth by adjusting hardware. For both classes of media, you can use the bandwidth configuration command to communicate the current bandwidth to the higher-level protocols.
Note At higher bandwidths, the value you configure with the bandwidth command is not what is displayed by the show interface command. The value shown is used in EIGRP updates and computing the load.
For generic serial interfaces such as PPP or High-Level Data Link Control (HDLC), set the bandwidth to the line speed. For Frame Relay on point-to-point interfaces, set the bandwidth to the committed information rate (CIR). For Frame Relay multipoint connections, set the bandwidth to the sum of all CIRs, or, if the permanent virtual circuits (PVCs) have different CIRs, then set the bandwidth to the lowest CIR multiplied by the number of PVCs on the multipoint connection. For more details about the bandwidth command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
Example: Basic EIGRP Configuration
RO UTE v 1.02-30
Example: Basic EIGRP Configuration

On router R1, EIGRP is enabled in autonomous system 110. The network 172.16.1.0 0.0.0.255 command starts EIGRP on the Fast Ethernet 0/0 interface and allows router R1 to advertise this network. With the wildcard mask used, this command specifies that only interfaces on the 172.16.1.0/24 subnet will participate in EIGRP. However, the full class B network 172.16.0.0 will be advertised, because EIGRP automatically summarizes routes on the major network boundary by default. The network 192.168.1.0 command starts EIGRP on the Serial 0/0/1 interface, and allows router R1 to advertise this network. If you do not use the optional wildcard mask, the EIGRP process assumes that all directly connected networks that are part of the overall major network will participate in the EIGRP routing process, and EIGRP will attempt to establish EIGRP neighbor relationships from each interface that is part of that Class A, B, or C major network. Use the optional wildcard mask to identify a specific IP address, subnet, or network. The router interprets the network number using the wildcard mask to determine which connected networks will participate in the EIGRP routing process. If specifying an interface address, use the mask 0.0.0.0 to match all four octets of the address. An address and wildcard mask combination of 0.0.0.0 255.255.255.255 matches all interfaces on the router. In the example above, router R1 is connected to router R3, which is external to AS 110. Network 172.16.5.0 is used on the link between router R1 and R3, but the statement for network 172.16.1.0 on router R1 is using a wildcard mask and router R1 does not try to form an adjacency with the router R3. Without the wildcard mask, router R1 would send EIGRP packets to the external network (toward router R3), which would waste bandwidth and CPU cycles and provide unnecessary information to the external network. The wildcard mask in the example above tells EIGRP to establish a relationship with EIGRP routers from interfaces that are part of subnet 172.16.1.0/24 only.
2-33
Note
The configuration of router R2 is identical to that of R1 described here. The only difference in terms of the EIGRP configuration is that the advertised network of the Fast Ethernet interface is different. The Fast Ethernet interface of router R2 is using a different subnet on the link.
2-34
Summary
Summary
EIGRP is an enhanced distance-vector protocol using these four key technologies: Neighbor discovery and recovery Reliable transport protocol DUAL Protocol-independent modules EIGRP uses various data structures (neighbor and topology tables) for proper operation, which are populated based on DUAL operation and metrics deployed. When planning EIGRP deployment, define the network requirements, gather the required parameters, and define the EIGRP routing. Basic EIGRP configuration requires the definition of EIGRP as a routing protocol, attached networks participating in EIGRP, and interface bandwidth for path manipulation.
2-35
2-36
Lesson 2
Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture
Overview
To assist in verification, this lesson introduces various Cisco IOS software show commands and defines the key fields in each. For a scalable Enhanced Interior Gateway Routing Protocol (EIGRP) network, configuring manual route summarization at key points on the internetwork is vital when implementing an optimized network configuration. Knowing the correct commands to use when you configure EIGRP helps to ensure that migration to this routing protocol is smooth and quick. Understanding which show command to use when verifying the EIGRP configuration saves valuable time. This lesson also provides advanced configuration options for EIGRP, including route summarization, passive interfaces, and default network origination.
Objectives
Upon completing this lesson, you will be able to describe how to verify and implement EIGRP routing. This ability includes being able to meet these objectives: Verify EIGRP routes for IPv4. Verify EIGRP operation for IPv4. Use the passive-interface command with EIGRP. Advertise an IP default network in EIGRP. Determine summary boundaries. Utilize manual route summarization.
Verify EIGRP Routes for IPv4

This topic describes how EIGRP configuration and operation can be verified using the appropriate commands.
EIGRP Deployment
ROUTE v1. 02-2
Router R1 has EIGRP enabled in autonomous system 110. The network 172.16.1.0 0.0.0.255 command starts EIGRP on the Fast Ethernet 0/0 interface and allows router R1 to advertise this network. With the wildcard mask used, this command specifies that only interfaces on the 172.16.1.0/24 subnet will participate in EIGRP. Note, however, the full class B network 1 72.16.0.0 will be advertised, because EIGRP automatically summarizes routes on the major network boundary by default. The network 192.168.1.0 command starts EIGRP on the Serial 0/0/1 interface and allows router R1 to advertise this network. Router R2 has EIGRP enabled in autonomous system 110. The network 172.17.2.0 0.0.0.255 command starts EIGRP on the Fast Ethernet 0/0 interface and allows router R2 to advertise this network. With the wildcard mask used, this command specifies that only interfaces on the 172.17.2.0/24 subnet will participate in EIGRP. Note, however, the full class B network 172.17.0.0 will be advertised, because EIGRP automatically summarizes routes on the major network boundary by default. The network 192.168.1.0 command starts EIGRP on the serial 0/0/1 interface and allows router R2 to advertise this network.
2-38
Verifying EIGRP Neighbors
ROUTE v1. 02-3
Both routers R1 and R2 are configured with the EIGRP routing protocol in autonomous system (AS) 110 and are advertising their networks to the neighbors. Before updates are sent, EIGRP is building the EIGRP neighbor table. The EIGRP neighbor table displays the neighbors discovered by EIGRP, including the IP address and interface on which each neighbor is reachable. The EIGRP neighbor table can be displayed using the show ip eigrp neighbors command. Use this command to determine when neighbors become active or inactive. You can also use it for debugging certain types of transport problems. The outputs of the command in the figure list currently used neighbor relationshipsrouter R1 has formed an adjacency with router R2 and vice versa. For more details about the show ip eigrp neighbors command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-39
Verifying EIGRP Neighbors (Cont.)

2
1. 2. 3. 4. 5. 6. 7. 8. 9.
3
Neighbor index Neighbor IP address
Interfac e on which the neighbor is reachable Remaining hold time Neighbor uptime Smooth round-trip time Retransmission timeout Number of pac kets to send to neighbor Last sequence received
ROUTE v1. 02-4
This output of the show ip eigrp neighbors command includes the following key elements: 1. H (handle): This column lists the order in which a peering session was established with the specified neighbor. The order is specified with sequential numbering starting with 0. 2. Address: This column contains the IP address of the EIGRP peer. 3. Interface: This column contains the interface on which the router is receiving hello packets from the peer. 4. Hold Time: This column contains the length of time (in seconds) that the Cisco IOS software will wait to hear from the peer before declaring it down. If the peer is using the default hold time, this number will be less than 15. If the peer is configured with a nondefault hold time, the non-default hold time will be displayed. Originally, the expected packet was a hello packet, but with current Cisco IOS software releases, any EIGRP packet received after the first hello from that neighbor resets the timer. 5. Uptime: This is the elapsed time (in hours: minutes: seconds) since the local router first heard from this neighbor. 6. Smooth Round Trip Timer (SRTT): The smooth round-trip time is the number of milliseconds required for an EIGRP packet to be sent to this neighbor and for the local router to receive an acknowledgment of that packet. This timer is used to determine the retransmit interval, also known as the retransmit timeout (RTO). 7. Retransmission timeout (RTO): This is the amount of time (in milliseconds) the software waits before resending a packet from the retransmission queue to a neighbor. 8. Queue count: This is the number of EIGRP packets (update, query, and reply) that the software is waiting to send. If this value is consistently higher than 0, a congestion problem might exist. A 0 indicates that no EIGRP packets are in the queue. 9. Seq Num: This is the sequence number of the last update, query, or reply packet that was received from this neighbor.
Verifying EIGRP Neighbors (Cont.)

Total retransmission count Current retry count
Neighbor version of Cisco IOS Current pending packets
ROUTE v1. 02-5
Detailed neighbor information can be examined with the show ip eigrp neighbor detail command. The command also reveals how many times a retransmission has occurred, the current retry count (router R1 in the figure has the value 2 for the retry count), the packets that are currently waiting to be sent (you can see that router R1 has three updates waiting to be sent), and the Cisco IOS version on the neighboring router For more details about the show ip eigrp neighbors detail command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-41
Verifying EIGRP Routes

Network EIGRP route type AD / Metric Next hop Route age
ROUTE v1. 02-6
If you run the show ip route command, the output will contain all of the routes in the routing table. To verify only EIGRP routes for any neighbors the router recognizes, use the show ip route eigrp command. EIGRP supports several route types: EIGRP routes from the local AS (D), EIGRP routes from the external AS (EX), and summary routes. EIGRP routes in the routers R1 routing table above are identified with a D in the left column; any external EIGRP routes (from outside of this autonomous system) would be identified with an EX. After the network number, there is a field that looks similar to [90/40514560]. The numbers may be different from the one in the example. The first number, 90 in the example above, is the administrative distance. It is used to select the best path when a router learns two or more routes from different routing sources. For example, consider that this router also uses Routing Information Protocol (RIP), and RIP has a route to network 172.17.0.0 that is three hops away. The router, without administrative distance, cannot compare the three hops for RIP to an EIGRP metric of 40514560. The router does not know the bandwidth associated with the hops and EIGRP does not use a hop count as a metric. To avoid problems like this, Cisco established an administrative distance value for each routing protocol; the lower the value, the more preferred the route is. By default, EIGRP internal routes have an administrative distance of 90 and RIP has an administrative distance of 120. Because EIGRP has a metric based upon bandwidth and delays, it is preferred over the RIP hop count. As a result, in this example, the EIGRP route is installed in the routing table. The second number in the brackets is the EIGRP metric. Recall that the default EIGRP metric is the least-cost bandwidth plus the accumulated delays. The EIGRP metric for a certain network is the same as its feasible distance (FD) in the EIGRP topology table. The next field, via 192.168.1.102 in the example above, identifies the address of the next-hop router to which this router passes the packets for the destination network 172.17.0.0/16. The next-hop address in the routing table is the same as the successor in the EIGRP topology table.
2-42
Each route also has a time associated with it: the length of time, perhaps days or months, since EIGRP last advertised this network to this router. EIGRP does not refresh routes periodically; it resends the routing information only when neighbor adjacencies change. The next field in the output is the interface (serial 0/0/1 in this case) from which packets for 172.17.0.0 are sent. Notice that the routing table includes routes to null0 for the advertised routes. The Cisco IOS software automatically inserts these routes in the table. They are called summary routes. Null0 is a directly connected, software-only interface. The use of the null0 interface prevents the router from trying to forward traffic to other routers in search of a more precise, longer match. For example, if the router in the figure receives a packet to an unknown subnet that is part of the summarized range (such as 172.16.3.5) the packet matches the summary route based on the longest match. The packet is forwarded to the null0 interface (in other words, it is dropped, or sent to the bit bucket) which prevents the router from forwarding the packet to a default route and possibly creating a routing loop. For more details about the show ip route command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-43
Verifying EIGRP Operation

K values
Load-balancing setting Networks being announced EIGRP local AD

To display the parameters and current state of the active routing protocol process, use the show ip protocols command. The sample output in the example above shows that EIGRP process 110 is running. The command output displays any filtering of routing that is occurring on EIGRP outbound or inbound updates. It also identifies if EIGRP is generating a default network or receiving a default network in EIGRP updates. The command output provides information about additional default settings for EIGRP, such as default K values, hop count, and variance.
Note Because the routers must have identical K values for EIGRP to establish an adjacency, you should run the show ip protocols command to determine the current K value setting before attempting an adjacency.
This sample output also indicates that automatic summarization is enabled (this is the default setting) and that the router is allowed to load-balance over a maximum of four paths. (The Cisco IOS software allows configuration of up to six paths for equal-cost load balancing, using the maximum-path configuration command.) The networks that the router is routing are also displayed. As shown in the figure, the format of the output varies, depending on the use of the wildcard mask in the network command. If a wildcard mask is used, the network address is displayed with a prefix length. If a wildcard mask is not used, the Class A, B, or C major network is displayed. The routing information sources section of this command output identifies all other routers that have an EIGRP neighbor relationship with this router.
2-44
The show ip protocols command output also provides the two administrative distances. First, an administrative distance of 90 applies to networks from other routers inside the autonomous system; these are considered internal networks. Second, an administrative distance of 170 applies to networks introduced to EIGRP for this autonomous system through redistribution; these are called external networks. The source of the external routes is not inside the autonomous system. For more details about the show ip protocols command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-45
Verifying EIGRP Operation (Cont.)

Peer count Route status

Feasible distance Advertised distance Outgoing interface
ROUTE v1. 02-8
Next hop
The show ip eigrp interfaces command displays information about interfaces configured for EIGRP. Use this command to determine which interfaces EIGRP is active on, and to learn information about EIGRP for interfaces. As shown in this sample output, the following key elements are included in the output: Interface: Interface over which EIGRP is configured Peers: Number of directly connected EIGRP neighbors Xmit Queue Un/Reliable: Number of packets remaining in the Unreliable and Reliable transmit queues Mean SRTT: Mean smooth round-trip time (SRTT) interval (in seconds). Pacing Time Un/Reliable: Pacing time used to determine when EIGRP packets should be sent out of the interface (unreliable and reliable packets) Multicast Flow Timer: Maximum number of seconds in which the router will send multicast EIGRP packets Pending Routes: Number of routes in the packets sitting in the transmit queue waiting to be sent To verify EIGRP operations further, you can use the show ip eigrp topology command. Use this command to determine the Diffusing Update Algorithm (DUAL) states and to debug any possible DUAL problems. If this command is used without any keywords or arguments, only routes that are feasible successors are displayed. The sample output above shows that Router R1 has an ID of 192.168.1.101 and resides in the autonomous system 110 (the EIGRP ID is the highest IP address on an active interface for this router). The command output lists the networks known by this router through the EIGRP routing process. The codes in the command output showing the state of this topology table entry are defined as follows:
2-46
Passive (P): This network is available and installation can occur in the routing table. Passive is the correct state for a stable network. Passive state is an indication that no EIGRP computations are being performed for this destination. Active (A): This network is currently unavailable and installation cannot occur in the routing table. A network in an active state has outstanding queries. Active state is an indication that EIGRP computations are being performed for this destination. Update (U): This code applies if a network is being updated (an update packet is being sent to this destination). This code also applies if the router is waiting for an acknowledgment for an update packet. Query (Q): This code applies if there is an outstanding query packet for this network and the network is not in the active state. The code indicates that a query packet was sent to this destination. This code also applies if the router is waiting for an acknowledgment for a query packet. Reply (R): This code applies if the router is generating a reply for this network or is waiting for an acknowledgment for a reply packet. This code indicates that a reply packet was sent to this destination. Stuck-in-active (SIA) status: This code signifies an EIGRP convergence problem for the network with which the route is associated. The number of successors available for a route is indicated in the command output, as well. In this example, all networks have one successor. If there were equal-cost paths to the same network, a maximum of six paths would be shown. The number of successors corresponds to the number of best routes with equal cost. For each network, the FD is displayed, followed by the next-hop address and then a field similar to (40514560/28160) in the figure. The first number in this field is the FD for that network through this next-hop router. The second number is the advertised distance (AD) from the next-hop router to the destination network. For more details about the show ip eigrp interfaces and show ip eigrp topology commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-47
Verifying EIGRP Operation (Cont.)

EIGRP packet counters
ROUTE v1. 02-9
To examine the number of various EIGRP packets sent and received, use the show ip eigrp traffic command, as illustrated in the figure. You can see that router R1 has sent 429 and received 192 hello messages, sent 4 and received 4 update messages, sent 1 query message and received 0 query messages, sent 0 reply messages and received 1 reply message, and sent 4 ACK messages and received 3 ACK messages. For more details about the show ip eigrp traffic command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-48
Using the Passive-Interface Command with EIGRP

This topic describes how to control routing updates using the passive-interface command.
Using Passive Interfaces

EIGRP announces the directly connected network of an interface EIGRP does not try to form neighbor relationships over the interface where only the host is connected Reduces traffic overhead
No peer here

No peer here

RO UTE v 1.02-10
Routers R1 and R2 have no neighbors available over the FastEtehrent0/0 interfaces, thus there is no need to try to establish adjacency over the interfaces. Moreover, the packets sent are overhead to the link bandwidth and also consume CPU resources of the router. In order to stop sending hello packets over the interface without neighbors, use the passive-interface command on the specified interface. In the above example, the passive-interface command is used in both routers for the Fast Ethernet interface 0/0. EIGRP will not bring up adjacencies on a passive interface, regardless of whether the neighbor command is configured.
Note Configuring the passive-interface command suppresses all incoming and outgoing routing updates and hello messages.
The passive-interface command has the following properties: Prevents a neighbor relationship from being established over the passive interface Stops routing updates from being received or sent over the passive interface Allows a subnet on the passive interface to be announced in an EIGRP process For more details about the passive-interface command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-49
Using Passive Interfaces (Cont.)

No need to talk to host by EIGRP Disables EIGRP on all interfaces by default Enables EIGRP only on selected interfaces

Within ISPs and large enterprise networks, distribution routers may have more than 100 interfaces, so manual configuration of the passive-interface command on interfaces where adjacency is not desired may create a problem. In some networks, this means entering 100 or more passive interface statements. With the default passive interface feature, this issue is solved by allowing all interfaces to be set as passive by default using a single passive-interface default command. Where adjacencies are desired, the individual interfaces are configured using the no passive-interface command. In the example above, routers R1 and R2 are configured with the passive-interface default command and all interfaces are refusing the establishment of EIGRP adjacency by default. The Serial 0/0/1 interface on each router is then configured to allow EIGRP adjacency as neighbors are expected. The passive-interface command is disabled for these interfaces.. For more details about the passive-interface default command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-50
Verify Operation with Passive Interfaces
RO UTE v 1.02-12
The main questions to ask when verifying operation with passive interfaces are: Do we see all the neighbors? Which interfaces in the routing process are passive? To see all of the EIGRP neighbors available, use the show ip eigrp neighbors command. To see the passive interfaces in the routing protocol, use show ip protocols command. The command output above for router R1 shows that interface FastEthernet 0/0 is defined as a passive interface. For more details about the show ip protocols command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-51
Advertising an IP Default Network in EIGRP

This topic describes the ip default-network command that is used to configure the last resort gateway or default route.
Using the ip default network Command with EIGRP

Default routes decrease the size of the routing table Multiple candidates: 0.0.0.0 is statically set or advertised by the routing protocol Any EIGRP major network route is flagged as a candidate default with the ip default-network command
EIGRP solution:
Flags network as a default route candidate Multiple default candidates supported Announced with the Exterior flag
RO UTE v 1.02-13
The major purpose of using default routes is to decrease the size of the routing table. This especially applies to stub networks or networks at the access layer (generally, it applies to all networks that are on lower hierarchical layers). The router, before installation of a default route, first collects default route candidates. The candidate can be a statically configured default route with the following command: ip route 0.0.0.0 0.0.0.0 next-hop | interface. In this command, interface is an outgoing interface through which all packets with unknown destinations will be forwarded, and nexthop is an IP address to which packets with unknown destinations will be forwarded. Any major network residing in the local routing table can become a candidate to use the ip default-network command. The command is also used to attach an Exterior flag to any major EIGRP or IGRP route, thus making it a candidate for a default route.
Note In EIGRP, no default routes can be directly injected (as in the OSPF environment with the default-information originate command).
The router examines all the default candidates and selects the best one based on the administrative distance and route metric. When selected, the router sets the gateway of last resort to the next hop of the selected candidate. This does not apply when the best candidate happens to be one of the directly connected routes.
2-52
Note
Any route residing in a routing table can be marked as a default candidate even if the route is not an EIGRP route.
Using the ip default network Command with EIGRP (Cont.)

Flagging an external network as a default route candidate
RO UTE v 1.02-14
The EIGRP default route can be created with the ip default-network command. A router configured with this command considers the network listed in the command as the last-resort gateway that it will announce to other routers. The network specified by this command must be reachable by the router that uses this command before it announces it as a candidate default route to other EIGRP routers. The network specified by this command must also be passed to other EIGRP routers so that those routers can use this network as their default network and set the gateway of last resort to this default network. This means that the network must either be an EIGRP-derived network in the routing table or be generated using a static route, which has been redistributed into EIGRP.
Note Multiple default networks can be configured; downstream routers use the EIGRP metric to determine the best default route.
Router R2 is has access to the external network 172.31.0.0/16 via its serial interface. The static route is configured in order to provide reachability, as routers R2 and R3 are not exchanging routing updates. Router R2 is configured with the 172.31.0.0 network as a candidate default network using the ip default-network 172.31.0.0 command. This network is passed to router R1. For more details about the ip default-network command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-53
Verifying Default Network Information
Flagged candidate Flagged candidate

Routers R1 and R2 are configured for EIGRP and router R2 has a configuration using the ip default-network command. In order to verify the processing of the default routes and default candidates, you must look at the IP routing tables on both of the routers. The 172.31.0.0 network is passed from router R2 to router R1. The ip default-network command does not benefit router R2 directly. On router R1, the EIGRP-learned 172.31.0.0 network is flagged as a candidate default network (as indicated by the * in the routing table). Router R1 also sets the gateway of last resort to 10.64.0.2 (toward router R2) to reach the default network of 172.31.0.0.
Note When you configure the ip default-network command, a static route (the ip route command) is generated in the routers configuration; however, the Cisco IOS software does not display a message to indicate that this has been done. The entry appears as a static route in the routing table of the router in which the command is configured, as can be seen in router R1s configuration and routing table in the figure. This can be confusing if you want to remove the default network. The configuration must be removed with the no ip route command.
2-54
Determining Summary Boundaries

This topic explains why administrators may need to use manual route summarization over default automatic route summarization.
Route Summarization
Improves network scalability Smaller routing tables Fewer updates Should follow IP addressing
RO UTE v 1.02-16
To reduce routing overhead and improve stability and scalability of routing, you can use route aggregation (summarization). However, to implement route aggregation, you must divide the network into contiguous IP address areas. This requires you to have a solid understanding of IP address assignment on route aggregation and hierarchical routing. The purpose of route summarization is to squeeze several subnets into one aggregate entry that covers all of them. Summarization results in smaller routing tables and smaller updates. Consequently, it also results in less routing traffic and lower CPU utilization (minor changes in the network go unnoticed).
2-55
EIGRP Automatic Route Summarization

Performed on major network boundaries Subnetworks are summarized to a single classful (major) network. Automatic summarization occurs by default. Could result in routing issuesdisable auto summarization
RO UTE v 1.02-17
Some EIGRP features (such as automatic route summarization routes at major network boundaries) are characteristics of distance vector operation. Traditional distance vector protocols, which are classful routing protocols, cannot assume the mask for networks that are not directly connected, because routing updates do not exchange masks. EIGRP automatically summarizes routes at the classful boundary. In some cases, you may not want automatic summarization to occur. For example, if you have discontiguous networks, you need to disable automatic summarization to minimize router confusion.
Note Automatic summarization is enabled by default for EIGRP.
2-56
EIGRP Manual Route Summarization

Configurable on a per-interface basis in any router within a network. Summarization results in a route pointing to null0. Loop prevention mechanism When the last specific route of the summary goes away, the summary is deleted. The minimum metric of the specific routes = metric of the summary route.
RO UTE v 1.02-18
A drawback to using distance vector protocols is that you cannot create summary routes at arbitrary boundaries within a major network. The ability to summarize routes is desirable, because it allows you to keep smaller routing tables. EIGRP allows administrators to disable automatic summarization and create one or more summary routes within the network on any bit boundary, as long as a more specific route exists in the routing table. When the last specific route of the summary goes away, the summary is deleted from the routing table. The minimum metric of the specific routes is used as the metric of the summary route. Recall that Cisco IOS software automatically inserts summary routes to interface null0 in the routing table for automatically summarized routes, to prevent routing loops. For the same reason, Cisco IOS software also creates a summary route to interface null0 when manual summarization is configured. For example, if the summarizing router receives a packet to an unknown subnet that is part of the summarized range, the packet matches the summary route based on the longest match. The packet is forwarded to the null0 interface (in other words, it is dropped), which prevents the router from forwarding the packet to a default route and possibly creating a routing loop. For manual summarization to be effective, blocks of contiguous addresses (subnets) must come together at a common router so that the router can advertise a single summary route. The number of subnets that can be represented by a summary route is directly related to the difference in the number of bits between the subnet mask and the summary mask. The formula 2n, where n equals the difference in the number of bits between the summary and subnet mask, indicates how many subnets can be represented by a single summary route. For example, if the summary mask contains three fewer bits than the subnet mask, eight (23 = 8) subnets can be aggregated into one advertisement. For example, if network 10.0.0.0 is divided into /24 subnets and is summarized to the summarization block 10.1.8.0/21, the difference between the /24 networks and the /21 summarizations is 3 bits; therefore, 23 = 8 subnets can be aggregated. The summarized subnets range from 10.1.8.0/24 through 10.1.15.0/24.
When configuring summary routes, the administrator needs to specify the IP address of the summary route and the summary mask. The Cisco IOS software for EIGRP handles many of the details that surround proper implementation, including details about metrics, loop prevention, and removal of the summary routes from the routing table if none of the more specific routes are valid.
2-58
Utilizing Manual Route Summarization

This topic explains why administrators may need to use manual route summarization over default automatic route summarization.
Configuring Route Summarization

Creating a summary route for 172.16.0.0/16

RO UTE v 1.02-19

EIGRP automatically summarizes routes at the classful boundary. In some cases, you may not want automatic summarization to occur. For example, if you have discontiguous networks, you need to disable automatic summarization to minimize router confusion. To disable automatic summarization, use the no auto-summary EIGRP router configuration command.
Note EIGRP router does not perform automatic summarization of networks in which it does not participate.
A discontiguous network 172.16.0.0 is used in the network on specific router R1 and R2 interfaces. On routers R1 and R2, automatic summarization has been disabled, so the 172.16.1.0 and 172.16.2.0 subnets are advertised into network 10.0.0.0. The routing tables of routers in the 10.0.0.0 network, including router R3, include these discontiguous subnets. An EIGRP router automatically summarizes routes only for networks to which it is attached. If a network is not automatically summarized at the major network boundary, as is the case in this example on routers R1 and R2 because autosummarization is turned off, all the subnet routes are carried into the router R3 routing table. Router R3 will not automatically summarize the 172.16.1.0 and 172.16.2.0 subnets, because it does not own the 172.16.0.0 network. Therefore, router R3 will send routes to the 172.16.1.0 and 172.16.2.0 subnets to the WAN. If you configure a summary route on the router R3 interface serial 0/0/0, as shown in the figure, only one route will be sent on the WAN. This route will represent all subnets that belong to network 172.16.0.0.
2-59
To configure manual route summarization on router R3, you must select the interface to propagate the summary route. Interface Serial0/0/0 is used in the example above. When configuring the summary route, you should use the ip summary-address eigrp command. You must specify the EIGRP routing protocol, AS number, and the summary address and the mask of the routes.
Note For manual route summarization, the summary route is advertised only if a component (a more specific entry) of the summary route is present in the routing table.
For more details about the auto-summary and ip summary-address eigrp commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-60
Verifying Route Summarization

In order to verify that summarization is configured correctly, you must look at the IP routing table. Router R3 was configured for summarization and the routing table on router R3 is presented in the figure above. Router R3 has both 172.16.1.0 and 172.16.2.0, the discontiguous subnets, in its routing table. Because of the summarization, only network 172.16.0.0 is advertised out of the serial0/0/0 interface, though. The summary route pointing to the Null0 interface prevents routing loops. This approach is based on the assumption that the router doing summarization has more information on the subnets covered by the summary route besides the summary route itself.
2-61
Summary
Summary
EIGRP operation can be verified by examining the EIGRP neighbor relationship information and IP routing table for the presence of EIGRP routes. The neighbor command can be used to form the EIGRP neighbor relationship with only specific neighbors using unicast packets. EIGRP is, by default, enabled on all interfaces included with the network command. To prevent unnecessary traffic, interfaces without neighbors should be made passive.
RO UTE v 1.02-21
Summary (Cont.)
Create and advertise a default route in an EIGRP autonomous system with the ip default-network network-number command. EIGRP performs automatic network-boundary summarization, but administrators can disable automatic summarization and perform manual route summarization on an interface-by-interface basis. Summarizing routes results in smaller routing tables. For manual route summarization, the summary route is advertised only if a more specific entry of the summary route is present in the routing table.
RO UTE v 1.02-22
2-62
Lesson 3
Lab 2-1 Debrief

Overview
In Lab 2-1, students configure and verify EIGRP operations. First a student configures basic EIGRP and advertises all the specific subnets used in the network. Next, the student defines EIGRP path selection so that the primary path is preferred and the second path remains as a backup. Because EIGRP uses a lot of bandwidth and CPU resources, the student must optimize EIGRP operation. The student must also configure EIGRP operation in scalable way, in which summarization is configured in order to improve convergence time and add stability.
Objectives
Upon completing this lesson, you will be able to explain how to configure and verify EIGRP operations. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

This topic describes lab topology, as well as the key checkpoints used to create a solution and start with the verification.
Lab Topology
ROUTE v1. 02-2
The figure above presents the physical lab topology used for Lab 2-1: configure and verify EIGRP operations. The topology uses four pod routers, one backbone router, and one pod switch. Based on the topology, students will identify the required parameters and configure a basic EIGRP routing protocol in order to establish Layer 3 reachability in the network, as well as influence EIGRP path selection, optimize EIGRP operation, and provide a scalable solution.
2-64

Task 1: Configure Basic EIGRP What steps did you take to configure the EIGRP routing protocol and advertise all of the specific IP subnets used in the network? Task 2: Influence EIGRP Path Selection What must be changed so that the primary path is preferred and the secondary path remains as a backup? Task 3: Optimize EIGRP Operation How do you prevent the formation of an adjacency, as well as preserve interface bandwidth and CPU resources? Task 4: Scale EIGRP Operation How is summarization configured in order to improve convergence time and add to stability?
ROUTE v1. 02-3
In the first task, you configured basic EIGRP routing. All routers are configured for EIGRP routing protocol according to the implementation plan. In the second task, you influenced the EIGRP path selection. You implemented redundancy in the network and the routers are able to select the primary path, while the backup path remains in the routing table. You must also change the metric in order to influence path selection in EIGRP routing protocol. In the third task, you optimized the EIGRP operation. Routing update suppression prevented the formation of EIGRP adjacencies. At the same time, CPU resources were preserved without the use of filtering. The passive-interface command is the solution to optimize the EIGRP operation in this step. In the fourth task, you configured scaling options of the EIGRP operation. Summarization was configured to summarize many subnets into one summary route, which was sent to the adjacent routers. Only one summary route is sent instead of many more-specific subnets.
2-65
Verification
Did you have enough information to create the implementation plan? Do the EIGRP-enabled routers form the adjacencies? Do you see all of the EIGRP-advertised networks in the IP routing table as EIGRP routes? Do you see two routes in the IP routing table after manipulating the path where the correct one is preferred? You cannot see the adjacency where the EIGRP routing protocol packets are suppressed, but the path to the destination still exists via another route; why is this? Do you see a summary route to Null0 interface as well as many more-specific subnets?
ROUTE v1. 02-4
A common approach to verifying the implementation process for configuring EIGRP operations is as follows: In order to create the implementation plan, sufficient information must be gathered. After a successful EIGRP configuration, all neighboring routers running EIGRP form an adjacency. Adjacent routers start exchanging routing protocol information and EIGRP routes populate the IP routing table. When a redundant path exists, one of them becomes primary path. Path manipulation results in the desired path being the primary and redundant paths being the backups. You cannot see the adjacency where EIGRP routing protocol packets are suppressed, but the path to the destination still exists via another route. The router performing the summarization includes a summary route to the Null0 interface, as well as routes to more-specific subnets. The remaining EIGRP neighbors only have a summary route.
2-66
Checkpoints
Configure the EIGRP routing protocol Advertise only specific subnets used in the network Manipulate the path by changing the metric Ensure the backup path still exists in the IP routing table Suppress the EIGRP routing protocol packet to preserve interface bandwidth and CPU resources without filtering Enable manual summarization to hide more specific subnets and improve stability
ROUTE v1. 02-5
During the configuration and verification phase, a network operator can deal with several checkpoints. After completing all the configuration tasks, the network operator may have successfully configured EIGRP operations, or may need to do additional verification and troubleshooting. With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Configure the EIGRP routing protocol. Advertise only specific subnets used in the network. Manipulate the path by changing the metric. Ensure that the backup path still exists in the IP routing table. Suppress the EIGRP routing protocol packet to preserve interface bandwidth and CPU resources without filtering. Enable manual summarization to hide more specific subnets and improve stability.
2-67

This topic describes a sample solution and other alternatives.
Sample Solution
EIGRP is configured on the routers. Specific subnets used in the network are advertised. The metric for the link between routers R1 and R3 is changed. The LAN interfaces on routers R1 and R3 are configured as passive. Summarization is configured on router R1.
ROUTE v1. 02-6
A sample solution includes implementation details and details for each task of the implementation plan. Different solutions are possible and the figure above shows a few details of a successful configuration. The proper implementation of route redistribution between multiple IP routing protocols includes the following checkpoints: EIGRP routing protocol is configured on the pod routers. Specific subnets used in the network are advertised. The metric for the link between routers R1 and R3 is changed in order to manipulate the primary and backup path. The LAN interface on routers R1 and R3 is configured as passive to suppress EIGRP routing packets and preserve link bandwidth and CPU resources. Summarization is configured on router R1 for a scalable EIGRP implementation that results in the summary route being advertised only to other neighbors.
2-68
EIGRP can be configured per interface or globally Different metrics, administrative distance, and filtering can be applied Static routes can be used and EIGRP can be disabled between routers R1 and BBR1. The use of another routing protocol can be an alternative solution, which is not realistic.
ROUTE v1. 02-7
Different metrics, administrative distance, and filtering can be applied to change the behavior of the EIGRP routing protocol. They can also be applied to manipulate the path when there is a redundancy in the network or to preserve CPU resources. You can use static routes, as well, but if all of the routers are configured with static routes, the solution will not be scalable. One of the options is to disable EIGRP between routers R1 and BBR1 and configure the default route or several static routes pointing toward router BBR1. The use of another routing protocol can be an alternative solution, which is not realistic as changing the routing protocol is not the case during fine tuning of the existing protocol.
2-69
Q and A
Why is routing protocol selection important? Why is changing the metric important? Does filtering preserve CPU router resources? Why does the passive-interface command result in no adjacency between the routers? Why does summarizing the router IP routing table contain a summary route to Null0 as well as more specific subnets? Why do the IP routing tables for some routers contain only a summary route?
ROUTE v1. 02-8
A routing protocol exchanges routing updates and populates the IP routing table, which is used for destination-based forwarding. Different routing protocols process routing updates in different ways. The metric defines the importance and the quality of the routes in the routing protocol. By manipulating the administrative distance and metric value, you can implement path manipulation, as well. Filtering does not preserve CPU resources. The passive-interface command suppresses routing protocol packets, preventing routers from forming adjacencies. The summary route is advertised and the neighboring routers send packets to the router that is summarizing the subnets in the routing table. If one of the more-specific subnets is lost, the router still sends the summary route to its neighbors, but the destination is not reachable and packets must be dropped (sent to the Null0 interface). A router summarizing the subnets contains the summary route as well as more-specific subnets. Because the idea of summarization is to decrease the sizes of the routing tables for neighboring routers, only a summary route is sent. This is enough to preserve the connectivity in the network.
2-70
Summary
Summary
Configure EIGRP and advertise all of the specific IP subnets in the network. Influencing EIGRP Path Selection can be applied by using a changing metric and backup path still exists in the IP routing table. By suppressing EIGRP routing packets, an EIGRP adjacency is not formed and the routing updates are not exchanged which results in more interface bandwidth and less CPU cycles used. Summarization decreases the size of the IP routing table, as only the summary route is present. The summarizing router has a summary route to the Null0 interface, as well as routes to morespecific subnets.
ROUTE v1. 02-9
2-71
2-72
Lesson 4
Configuring and Verifying EIGRP for the Enterprise WAN Architecture

Overview
EIGRP can operate over various underlying network technologiesEthernet over Multiprotocol Label Switching (EoMPLS), MPLS virtual private network (MPLS VPN), and physical Frame Relay, as well as multipoint and point-to-point Frame Relay subinterfaces. Load balancing across multiple links is a valuable option for efficient bandwidth utilization. If you limit the amount of bandwidth that Enhanced Interior Gateway Routing Protocol (EIGRP) uses across these WAN links, you can provide user traffic with better access to the WAN links. This lesson provides insight into EIGRP deployment over various WAN technologies, as well as advanced configuration options for EIGRP load balancing and limitation of EIGRP bandwidth utilization on WAN links.
Objectives
Upon completing this lesson, you will be able to describe, recognize, and deploy EIGRP over various WAN technologies and be able to scale the deployment with load balancing and proper bandwidth utilization. This ability includes being able to meet these objectives: Configure and verify EIGRP over Frame Relay and on a physical interface. Configure and verify EIGRP over multipoint subinterfaces. Configure and verify EIGRP over point-to-point subinterfaces. Implement load balancing across equal-metric paths. Implement load balancing across unequal-metric aths. Determine EIGRP bandwidth use across WAN links. Implement EIGRP over Layer 2 and Layer 3 MPLS VPN.
EIGRP Over Frame Relay and on a Physical Interface

This topic describes how EIGRP can be deployed using Frame Relay physical interfaces.
Frame Relay Overview

Frame Relay network NBMA = nonbroadcast multiaccess network Pseudo-broadcasting Requires mapping from Layer 3 to Layer 2 (IP-to-DLCI) Static mapping Dynamic mapping Neighbor loss detected only after the hold time expires or the interface goes down Different topologies Full mesh Partial mesh Hub and spoke
Frame Relay is a switched WAN technology for which virtual circuits are created through the network. In order to provide IP layer connectivity mapping between IP addresses and data-link connection identifiers (DLCIs) must be deployedeither dynamically or statically. Usually, switched WAN networks do not support broadcasting capability equivalent to LAN broadcasting. To emulate the LAN broadcasting capability that is required by IP routing protocols (for example, to send hello or update packets to all neighbors reachable over an IP subnet), Cisco IOS Software implements pseudo-broadcasting. This is when the Layer 2 code in Cisco IOS Software creates several copies of the same broadcast or multicast packetone for each neighbor reachable through the WAN media. In environments where a single router has a large number of neighbors reachable through a single WAN interface, pseudo-broadcasting must be tightly controlled, as it can use a large amount of CPU time and WAN bandwidth. Pseudo-broadcasting is controlled with the broadcast option specified on static maps in a Frame Relay configuration. Pseudo-broadcasting cannot be controlled for neighbors reachable through dynamic maps created via Inverse Address Resolution Protocol (Inverse ARP) on a Frame Relay, as dynamic maps always allow pseudo-broadcasting. To control pseudo-broadcasting in Frame Relay, you must define the manual static maps and disable Inverse ARP. Neighbor loss is detected only after the hold time expires or the interface goes down. It is important to know that an interface is up as long as at least one DLCI is alive. The different topologies for Frame Relay are full mesh, partial mesh, and hub and spoke.
EIGRP with Dynamic Mapping

A single IP subnet is used Inverse ARP is enabled by default Split horizon is disabled on the physical interface by default

To deploy EIGRP over a physical interface using dynamic mapping, thus relying on Inverse ARP, no changes are needed to the basic configuration. The EIGRP process is enabled using the required autonomous system (AS) number (110 in the example on the figure). Proper interfaces and networks can also be included in the topology by specifying the network command under the EIGRP routing process. The split-horizon behavior is disabled by default on the physical interface. Therefore, routers R2 and R3 can provide connectivity between their connected networks. Inverse ARP does not provide dynamic mapping for the communication between routers R2 and R3; this must be configured manually.
2-75
EIGRP with Dynamic Mapping (Cont.)


ROUTE v1. 02-4
The sample outputs of the show ip eigrp neighbors command on this slide show the neighbors of routers R1 and R3. Router R1 forms an adjacency with router R2 and another with router R3 over the serial0/0 physical interface. Likewise, routers R2 and R3 form adjacencies with router R1. Apart from that, they can also form an EIGRP adjacency to each other if the IP-to-DLCI mapping for that connectivity is also provided. On the sample output for router R3, it is apparent that router R3 has adjacencies to routers R1 and R2.
2-76
EIGRP with Static Mapping

A single IP subnet is used Split horizon is disabled on the physical interface by default Inverse ARP is not used

To deploy EIGRP over a physical interface on router R1 using static mapping, thus disabling the Inverse ARP, no changes are needed to the basic configuration of EIGRP. The EIGRP process is enabled using the required AS number (110 in the example in the figure above). Proper interfaces and networks are included in the topology by specifying the network command under the EIGRP routing process. In addition, manual IP-to-DLCI mapping statements on the serial 0/0 interface are necessary on all three routers: R1, R2, and R3. The split-horizon behavior is disabled by default on the physical interface, thus routers R2 and R3 can provide connectivity between their connected networks, as well.
2-77
EIGRP with Static Mapping (Cont.)
ROUTE v1. 02-6
The figure above shows the adjacency formed between router R1 and routers R2 and R3 over the serial0/0 physical interface. The adjacency formed using static mapping is the same as the one formed using dynamic mapping. The same applies to routers R2 and R3, which form the adjacency with router R1. Routers R2 and R3 can also form an EIGRP adjacency to each other if the IP-to-DLCI mapping for that connectivity is provided. The sample output from the show ip eigrp neighbors command in the figure above shows the neighbors on router R1 and R3. It is apparent that router R1 has two neighbors (routers R2 and R3), and router R3 also has two neighbors (routers R1 and R2).
2-78
EIGRP over Multipoint Subinterfaces

This topic describes how EIGRP can be deployed using Frame Relay multipoint subinterfaces.
Frame Relay Multipoint Subinterfaces

Several multipoint subinterfaces can be created: Logical interfaces emulating the multiaccess network Like NBMA physical interfaces for routing purposes IP address space may be saved, since a single subnet is used. Subinterfaces are applicable to partial-mesh and full-mesh topologies. Neighbor loss is detected only after the hold time expires or the subinterface goes down.
ROUTE v1. 02-7
Several subinterfaces can be created over Frame Relay interfaces. They are logical interfaces emulating a multi-access network and provide the routing equivalent to nonbroadcast multiaccess (NBMA) physical interfaces. As with NBMA physical interfaces, a single subnet is usedpreserving the IP address space. EIGRP neighbor loss detection is particularly slow on multipoint subinterfaces configured over low-speed WAN links. This is because the default values of the EIGRP timers on these interfaces are 60 seconds for the hello timer and 180 seconds for the hold timer. In the worst case, neighbor loss detection can take up to 3 minutes. Frame Relay multipoint is applicable to partial-mesh and full-mesh topologies. Partial-mesh Frame Relay networks must deal with the possibility of a split horizon, which prevents routing updates from being retransmitted on the same interface on which they were received.
2-79
EIGRP over Multipoint Subinterfaces

A single IP subnet is used. Mapping is applied to the subinterface. Split horizon must be disabled in partial-mesh topologies.
ROUTE v1. 02-8
To use the multipoint behavior of a subinterface, you must add the multipoint keyword at the end of the interface command when creating the subinterface. With Frame Relay, the mapping on the multipoint subinterfaces is created by using the proper local DLCI value: By specifying the proper local DLCI value and relying on the Inverse ARP With manual IP-to-DLCI mapping EIGRP is configured with no changes to the basic deployment. To enable the EIGRP process, use the required AS number (110 in the example on the figure) and include the proper interfaces and networks in the topology via the network command under the EIGRP routing process. Additionally, you can configure manual IP-to-DLCI mapping statements (via the frame-relay map command with the broadcast keyword on the serial 0/0 multipoint subinterfaces on routers R1, R2, and R3), in order to define the mapping between a destination protocol address and the DLCI used to connect to the destination address. If routers R2 and R3 need to provide connectivity between their connected networks, you must disable the EIGRP split horizon on the multipoint subinterface of router R1. The router R1 configuration includes the frame-relay map command to its own IP address on the multipoint serial subinterface in order to ping the local address for router R1 from router R1 itself.
2-80
EIGRP over Multipoint Subinterfaces (Cont.)
ROUTE v1. 02-9
If you want to verify the operation of the EIGRP routing protocol over the Frame Relay multipoint subinterface, you can use the show ip eigrp neighbors command. The figure above shows two sample outputs for routers R1 and R3. Router R1 forms the adjacency with routers R2 and R3 over the serial0/0.1 multipoint subinterface. This is done in the same way routers R2 and R3 form the adjacency with router R1 and between each other if IP-to-DLCI mapping for that connectivity is provided.
2-81
EIGRP Unicast Neighbor

Setting a neighbor with the command to enable a unicast neighbor relationship

The neighbor command is used in EIGRP in order to define a neighboring router with which to exchange routing information. Instead of using multicast packets, EIGRP exchanges routing information with the neighbors in the form of unicast packets whenever the neighbor command is configured for an interface. EIGRP stops processing all multicast packets that come inbound on that interface. At the same time, EIGRP stops sending multicast packets on that interface. Multiple neighbor statements can be used to establish peering sessions with specific EIGRP neighbors. The interface through which EIGRP will exchange routing updates must be specified in the neighbor statement. The interfaces through which two EIGRP neighbors exchange routing updates must be configured with IP addresses from the same network.
Note EIGRP neighbor adjacencies cannot be established or maintained over an interface that is configured as passive.
Router R1 is configured with the neighbor command for router R2. For more details about the neighbor command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-82
EIGRP Unicast Neighbor (cont.)

Router R1 is configured with the neighbor command and will not accept multicast packets anymore. In order to establish an adjacency, router R2 must be configured as well. In the example above, router R2 is configured with the neighbor command for router R1, which enables the use of unicast packets accepted by router R1. Router R3 is not configured with the neighbor command.
2-83
Verifying EIGRP Unicast Neighbors


RO UTE v 1.02-12
To verify the configuration, use the show ip eigrp neighbors command. As you can see in the output above, routers R1 and R2 have formed the neighbor relationship. The sample output does not show that the neighbor command was used on both routers. It only indicates that a neighbor relationship was established, which is a proof that the configuration was successfully completed. Router R3 is not using the neighbor command and no neighbor relationship was established, because routers R1 and R2 are not accepting multicast packets. For more details about the show ip eigrp neighbors command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-84
EIGRP over Point-to-Point Subinterfaces

This topic describes how EIGRP can be deployed using Frame Relay point-to-point subinterfaces.
Frame Relay Point-to-Point Subinterfaces

Several point-to-point subinterfaces can be created: Logical interfaces emulating a leased-line network Like physical point-to-point interfaces for routing purposes Each point-to-point subinterface requires its own subnet. Applicable to hub-and-spoke topologies. Neighbor loss is detected after the hold time expires, the subinterface goes down, or the DLCI is lost.
RO UTE v 1.02-13
Several point-to-point subinterfaces can be created over Frame Relay interfaces. They are logical interfaces emulating a leased line network and provide a routing equivalent to point-topoint physical interfaces. As with physical point-to-point interfaces, each interface requires its own subnet. Frame Relay point-to point is applicable to hub-and-spoke topologies. EIGRP neighbor loss detection is quite fast on point-to-point subinterfaces for several reasons: The default values of the EIGRP hello timer and the EIGRP hold timer are identical to the values used on point-to-point links (5 seconds for the hello timer and 15 seconds for the hold timer). In the worst case, the neighbor loss is detected within 15 seconds. On Frame Relay networks, the subinterface is declared down if the DLCI attached to the interface is lost and neighbor loss detection is immediate. For multipoint subinterfaces, all of the permanent virtual circuits (PVCs) attached to it must be lost for the interface to be declared down.
Note Neighbor loss detection due to DLCI loss only works if the Frame Relay network supports end-to-end Integrated Local Management Interface (ILMI) signaling. On some Frame Relay networks, one end of the connections might fail (for example, due to a router failure), but the DLCI will still be declared operational at the other end of the connection.
2-85
EIGRP over Point-to-Point Subinterfaces

RO UTE v 1.02-14
To enable subinterfaces for point-to-point, you need to create them using the point-to-point keyword at the end of the interface command. With Frame Relay, the mapping of the point-topoint subinterfaces is created by specifying the proper local DLCI value. EIGRP is configured with no changes to the basic deployment. To enable the EIGRP process, use the required AS number (110 in the example on the figure) and include the proper interfaces and networks in the topology via the network command under the EIGRP routing process. Additionally, you can configure manual IP-to-DLCI mapping statements (via the frame-relay map command with the broadcast keyword on the serial 0/0 multipoint subinterfaces on routers R1, R2, and R3).
2-86
EIGRP over Point-to-Point Subinterfaces (Cont.)
RO UTE v 1.02-15
The show ip eigrp neighbors command can be used to verify the operation of the EIGRP routing protocol over the Frame Relay point-to point subinterface. The figure above shows two sample outputs for router R1 and R3. Router R1 forms an adjacency with router R2 over the serial0/0.2 point-to-point interface and with router R3 over the serial0/0.3 point-to-point subinterface. Likewise, routers R2 and R3 form the adjacency with router R1. On the figure above it is apparent that router R3 has one neighbor over the serial0/0.1 point-to-point subinterface.
2-87
Load Balancing Across Equal-Metric Paths

This topic explains how EIGRP performs load balancing across equal-metric paths and describes how to change the default configuration.
EIGRP Load Balancing

Routes with a metric equal to the minimum metric are installed in the routing table - equal-metric load balancing Up to 16 entries can be in the routing table for the same destination (default is 4) Maximum number is configurable To disable load balancing, set the value to one

To control the maximum number of parallel routes that an IP routing protocol can support
RO UTE v 1.02-16
Equal-metric load balancing is a routers capability to distribute traffic over all of its network ports that have the same metric to the destination address. Load balancing increases the use of network segments and increases the effective network bandwidth. For IP, the Cisco IOS Software applies load balancing between a maximum of four equalmetric paths by default. You can configure the maximum number of parallel routes that an IP routing protocol can support using the maximum-paths router configuration command. Up to 16 equally good routes can be kept in the routing table.
Note Setting the maximum-paths value to 1 disables load balancing.
When a packet is process-switched, load balancing over equal-metric paths occurs on a perpacket basis. When packets are fast-switched, load balancing over equal-metric paths occurs on a per-destination basis. (Thus, if you are testing load balancing, do not ping to or from routers with fast-switching interfaces, because the packets generated locally by this router are processswitched rather than fast-switched, and the ping might produce confusing results.) For more details about the maximum-paths command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-88
EIGRP Load Balancing (Cont.)

RO UTE v 1.02-17
The configuration example above shows the use of the maximum-paths command, which is applied under the EIGRP routing process. Router R1 is configured to support up to three equalmetric paths. If the maximum-paths command is not used, EIGRP can, by default, use four equal-metric paths. The sample output above shows router R1s routing table, where the three paths have the same metric (cost). All three paths through routers R2, R3, and R4 are used to reach the destination network 172.16.2.0 behind router R6. The path through router R5 is not used, because the metric is too big. Even if the metric is the same as the others, the path will not be used, as 3 is the maximum number set by the maximum-paths command.
2-89
Load Balancing Across Unequal-Metric Paths

This topic explains how EIGRP performs load balancing across unequal-metric paths and describes how to configure load balancing.
EIGRP Unequal-Cost Load Balancing

The router can balance traffic across multiple routes that have different metrics to a destination Successor is always used Feasible successors are used if the cost is less than (minimum cost * variance) Variance is only a multiplier, not a max-path parameter The maximum number of paths is limited by the maximum paths command Variance opens the gate for unequal-cost load balancing

To control load balancing in an internetwork based on EIGRP

EIGRP can also balance traffic across multiple routes that have different metrics, which is called unequal-metric load balancing. The degree to which EIGRP performs load balancing is controlled by the variance (EIGRP) command. Setting a variance value (1-128) enables EIGRP to install multiple loop-free routes with unequal cost in a local routing table. EIGRP will always install a successor into the local routing table. Additional feasible successors are candidates for the local routing table. Additional entries through EIGRP must meet two criteria to be installed in the local routing table: The route must be loop-free. This condition is satisfied when the advertised distance (AD) 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 configured on the router. The default value for the variance (EIGRP) command is 1, which indicates equal-cost load balancingonly routes with the same metric as the successor are installed in the local routing table. The variance command is not limiting the maximum number of paths. It is the multiplier that defines the range of metric values that are accepted for load balancing by the EIGRP process. If the variance is set to 2, any EIGRP-learned route with a metric less than 2 times the successor metric will be installed in the local routing table. If the variance command allows EIGRP to use 9 paths and the maximum-path command sets the maximum paths value to 3, only the first 3 paths of the 9 paths will show up in the IP routing tablethe maximum-path command will limit the maximum number.
2-90
Note
EIGRP does not load-share between multiple routes; it only installs the routes in the local routing table. Then the local routing table enables switching hardware or software to loadshare between the multiple paths.
For more details about the EIGRP variance command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-91
EIGRP Unequal-Cost Load Balancing (Cont.)
R1 EIGRP Topology for 172.16.2.0

Ne two rk 172 .16.2.0 Neig hbor R2 R3 R4 R5 FD 30 20 45 50 AD 10 10 25 10
- AD(R4)>FD(R3) - Variance: 50(FD)>2*20(FD,Successor)

Router R1 in the example above is configured with a variance of 2, and the range of metric values, which are the feasible distances (FDs) to network 172.16.2.0/24, is from 20 to 50 (generic values, in order to make computation easier). This range of values determines the feasibility of a potential route. A route is feasible if the next router in the path is closer to the destination than the current router and if the metric of the alternate path is within the variance. Load balancing can use only feasible paths, which are included inside the local routing table. The two feasibility conditions are: The local best metric (the current FD) must be greater than the best metric (AD) learned from the next router. In other words, the next router in the path must be closer to the destination than the current router, which prevents routing loops. The variance multiplied by the local best metric (the current FD) must be greater than the metric through the next router (the alternative FD). This condition is true if the metric of the alternate path is within the variance. If both of these conditions are met, the route is called feasible and can be added to the routing table. The example below shows four paths from router R1 to network 172.16.2.0/24 with the following metrics: Path 1: 30 (via R2) Path 2: 20 (via R3) Path 3: 45 (via R4) Path 4: 50 (via R5)
2-92
All the paths have different metrics. By default, router R1 only places path 2, via R3, in the routing table, because it is the least-cost patha successor route with the lowest FD. For it to load balance over paths 1 and 2, a variance command must be applied to router R1 to change the value in such way that path 1 (with a greater metric than the successor route) can be used as well. The variance value must be set such that the result of multiplying the variance and successor FD will be greater than the second FD candidate. In our example, the variance value is set to 2, which produces a result of 40 (20 * 2 = 40) and path 1 through router R2, becomes the second route in the local routing table (the FD of 30 is less than 40). Router R4 is not considered for load balancing with this variance, because the FD through router R4 is more than twice the FD for the successor (router R3). Router R4 will never be a feasible successor no matter what the variance is. This is because router R4s advertised distance of 25 is greater than router R3s FD of 20; therefore, to avoid a potential routing loop, router R4 is not considered a feasible successor. Router R5 is not considered for load balancing with this variance, because the FD through router R5 is more than twice the FD for the successor (router R3). In this example, however, router R5 will be a feasible successor no matter what the variance is. This is because router R5s advertised distance of 10 is lower than router R3s FD of 20. Load balancing is proportional to the bandwidth. Routes via R2 and R3 in the picture above are used for load balancing. The FD of the route via R2 equals 30. The FD of the route via R3 equals 20. The total FD is 50 and the ratio of traffic between the two paths (via R2 : via R3) is 3/5 : 2/5.
2-93
EIGRP Bandwidth use Across WAN Links

This topic explains how EIGRP can utilize bandwidth across WAN links in an environment where the default bandwidth usage, of up to 50%, may not be optimal.
EIGRP Bandwidth Utilization over WAN

Up to 50% of bandwidth is utilized by default and can be changed Point-to-point interfaces Treat bandwidth as T1 by default Configure bandwidth manually Multipoint interfaces Bandwidth on the physical interface divided by the number of neighbors on that interface

To configure the percentage of bandwidth that may be used by EIGRP on an interface
RO UTE v 1.02-20
EIGRP operates efficiently in WAN environments. It is scalable on both point-to-point links and on multipoint NBMA links. Because of the inherent differences in the operational characteristics of WAN links, the default configuration parameters may not be the best option for all WAN links. A solid understanding of EIGRP operation, coupled with knowledge of available link speeds, can yield an efficient, reliable, and scalable router configuration. By default, EIGRP may use up to 50 percent of the bandwidth of an interface or subinterface. When calculating how much bandwidth to use, EIGRP uses either the bandwidth of the link set by the bandwidth command, or the links default bandwidth if none is configured. This percentage can be changed on a per-interface basis by using the ip bandwidth-percent eigrp interface configuration command. Cisco IOS Software assumes that the point-to-point Frame Relay subinterfaces (such as all serial interfaces) operate at full T1 link speed. In many implementations however, only fractional T1 speeds are available. Therefore, when configuring these subinterfaces, set the bandwidth to match the contracted committed information rate (CIR). When configuring multipoint interfaces, especially for Frame Relay (but also for ATM and ISDN PRI), it is important to understand that all neighbors share the bandwidth equally. That is, EIGRP uses the bandwidth command on the physical interface divided by the number of Frame Relay neighbors connected on that physical interface to calculate the bandwidth assigned to each neighbor. The EIGRP configuration should reflect the correct percentage of the actual available bandwidth on the line.
In the figure above, a sample configuration is used, in which an EIGRP process with an AS number 110 can get 80% of the bandwidth configured on that interface. This percentage can be greater than 100, which may be useful if the bandwidth is configured artificially low for routing-policy reasons. For more details about the ip bandwidth-percent eigrp command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-95
Bandwidth Utilization Issues

Each PVC can have a different CIR, creating an EIGRP packetpacing problem. Multipoint interfaces: Convert to point-to-point configuration OR Manually configure bandwidth by multiplying the lowest CIR by the number of PVCs.
PVC 1 2 3 4
Bandwidth (kb/s) 64 128 256 256
RO UTE v 1.02-21
Each installation has a unique topology and requires a unique configuration. Since CIR values differ, a subinterface will often requires a hybrid configuration that blends the characteristics of point-to-point circuits with multipoint circuits. When configuring multipoint interfaces, configure the bandwidth to represent the minimum CIR multiplied by the number of circuits. This approach may not fully use the higher-speed circuits, but it ensures that the circuits with the lowest CIR values are not overdriven. If the topology has a small number of very low-speed circuits, these interfaces are defined typically as point-to-point, so that their bandwidth can be set to match the provisioned CIR. In the figure above, 64k b/s is the smallest amount of bandwidth among all PVCs in the multipoint configuration and this should be taken into account for bandwidth calculation.
2-96
EIGRP Hub-and-Spoke WAN Utilization

Configure each VC as point-to-pointdo not change number of VCs to preserve the configuration Set bandwidth to 1/10 of link capacity Increase EIGRP utilization to 50% of actual VC capacity

RO UTE v 1.02-22
The example above shows a hub-and-spoke topology with ten virtual circuits to the ten remotes sites. Only four of the ten remote sites are shown in the figure above. The configurations for routers R1 and R5, using EIGRP AS 110, are also shown in the figure. The circuits are provisioned as 64-kb/s links, but there is insufficient bandwidth at the interface to support this allocation. For example, if the hub tries to communicate to all remote sites at the same time, the bandwidth that is required exceeds the available link speed of 256 kb/s for the hub (10 times the CIR of 64 kb/s equals 640 kb/s). The configuration for router R1 shows that the bandwidth 256 command has been applied to the main interface (serial0) and has set the bandwidth to 256 kb/s. Because 10 virtual circuits (VCs) are configured, each of them automatically gets 10% of the main interface bandwidth. Therefore, the bandwidth command is not needed on each subinterface. The ip bandwidth-percent eigrp 110 128 command sets the maximum percentage of an interfaces bandwidth that EIGRP can use to 128% for EIGRP AS 110. In a point-to-point topology, all virtual circuits are treated equally; the subinterfaces are assigned a bandwidth equal to one-tenth of the available link speed (25 kb/s). Based on the ip bandwidth-percent eigrp 110 128 command applied on each interface and subinterface, the EIGRP allocation percentage is raised to 128 percent of the specified bandwidth in an attempt to ensure that the EIGRP packets are delivered through the Frame Relay network. This adjustment causes the EIGRP packets to receive 32 kb/s of the provisioned 64 kb/s on each circuit (128% of the 25kb/s equals 32 kb/s). This extra configuration restores the 50-50 ratio that was changed when the bandwidth was set to an artificially low value. In order to ensure that this calculation is correct, the number of VCs must not be changed.
2-97
EIGRP Multipoint WAN Utilization

Solution 1: create on multipoint interfaces (Lowest CIR * number of VCs) = (56 kb/s * 4) = 224 kb/s
RO UTE v 1.02-23
In a multipoint topology, where virtual circuits may not have equal bandwidth, the rule is to use the lowest CIR and multiply it by the number of VCs to get the bandwidth that should be set on the interface. With this configuration, the smallest and the slowest link will not suffer with higher speed links. In the figure above, the example shows four VCs with different CIRs configured. The CIR toward routers R2, R3, and R4 is configured to 256 kb/s and the CIR toward router R5 is configured to 56 kb/s. Thus, on router R1, the bandwidth is set to 224 kb/s, which is 4 times the lowest CIR in the system (56 kb/s).
2-98
EIGRP Hybrid Multipoint WAN Utilization (Cont.)

Solution 2: create separate multipoint interfaces Configure the lowest CIR VC as point-to-point and set bandwidth = CIR. Configure higher CIR VCs as multipoint, combine CIRs, and configure the sum of bandwidth to the subinterface.

RO UTE v 1.02-24
In a hybrid multipoint and point-to-point topology, you should create separate point-to-point VCs for the lowest CIR VCs. All other VCs, which have a higher and possibly equal CIR, should be configured as one multipoint VC. For this multipoint VC, the CIR must be a combination of all individual CIRs. The figure above shows an example in which one VC is a low-speed circuit with 56kb/s of bandwidth and the other three VCs have bandwidth of 256 kb/s. The preferred configuration on router R1 shows the low-speed circuit configured as point-to-point with the bandwidth set to the CIR value. The remaining circuits are designated as a multipoint subinterface, and their CIRs are added together to set the bandwidth for the subinterface. In multipoint interfaces, the bandwidth is shared equally among all circuits. In this case, the bandwidth is set to 768 kb/s, which is the sum of the three CIRs (3 * 256 kb/s = 768 kb/s). Each link will be allocated one-third of this bandwidth, resulting in 256 kb/s each.
2-99
EIGRP over EoMPLS and Metro Ethernet

This topic provides an overview of EoMPLS technology and explains how EIGRP can be deployed in an EoMPLS environment.
AToM Overview
Service providers offer Layer 2 transport services to connect customer equipment (CE) Ethernet, Ethernet VLAN ATM PPP, HLDC, and so on Any Transport Over MPLS Enables the sending of Layer 2 frames across the MPLS backbone Unifies Layer 2 and Layer 3 over a common MPLS infrastructure Virtual circuits represent Layer 2 links Labels identify virtual circuits
RO UTE v 1.02-25
Many ISPs currently offer Layer 2 transport services to their customers. These services are offered over a circuit-based infrastructure to build Layer 2 virtual private networks (VPNs). Initially, VPNs were built using leased lines. Later, service providers offered Layer 2 VPNs based on point-to-point data link layer connectivity, using ATM or Frame Relay virtual circuits. Customers built their own Layer 3 networks to accommodate IP traffic. As a result, separate networks exist for Layer 2 and Layer 3 traffic. However, maintaining separate networks for Layer 2 VPNs and Internet traffic is difficult and costly. Therefore, ISPs want a single IP-based network to provide both Layer 2 and Layer 3 services. MPLS VPN was introduced to meet the requirement for a unified network for Layer 3 VPN services. However, some customers still wanted Layer 2 connections. This can be Ethernet VLAN extensions across a metropolitan area or ATM services. Any Transport over MPLS (AToM) was introduced to facilitate Layer 2 connectivity across an MPLS backbone. AToM benefits ISPs that offer Layer 2 connectivity to customers with traditional offerings such as ATM, Frame Relay, and serial/Point-to-Point Protocol (PPP) services. Additionally, it benefits service providers specializing in Ethernet connectivity in metropolitan areas. Services for Layer 2 VPNs also appeal to service providers' enterprise customers, who may already run many of these networks and want just point-to-point connectivity.
Note For more information about MPLS, please attend the Implementing MPLS VPN Cisco course.
2-100
Layer 2 and Layer 3 MPLS VPN Solutions

Layer 2 MPLS VPN backbone solution
Layer 3 MPLS VPN backbone solution
RO UTE v 1.02-26
The figure above presents the basic difference between a Layer 2 MPLS VPN and a Layer 3 MPLS VPN backbone solution. Customer routers (R1 and R2 on this slide) are connected across the MPLS VPN backbone, and it is important to define the difference. The Layer 2 MPLS VPN backbone solution is providing the Layer 2 service across the backbone, where routers R1 and R2 are connected together directly using the same IP subnet. This slide presents the connectivity through the backbone as a switch. The Layer 3 MPLS VPN backbone solution is providing the Layer 3 service across the backbone, where routers R1 and R2 are connected to ISP edge routers. A separate IP subnet is used on each side. This slide presents the connectivity through the backbone as a router.
2-101
Layer 3 MPLS VPN Overview

Service provider is connecting multiple customers over a common MPLS backbone using MPLS VPNs Customer Edge (CE) devices connect into the service provider MPLS VPN network
RO UTE v 1.02-27
The MPLS VPN architecture provides the ISPs with a peer-to-peer VPN architecture that combines the best feature of an overlay VPN (support for overlapping customer address spaces) with the best features of peer-to-peer VPNs: 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. The MPLS VPN terminology divides the overall network into the customer-controlled part (Cnetwork) and the provider-controlled part (P-network). Contiguous portions of the C-network are called sites and are linked with the P-network via Customer Edge routers (CE-routers). The CE-routers are connected to the provider edge routers (PE-routers), which serve as the edge devices of the provider network. The core devices in the provider network (P-routers) provide the transit transport across the provider backbone and do not carry customer routes. The architecture of a PE-router in an MPLS VPN is very similar to the architecture of a point of presence (POP) in the dedicated PE-router peer-to-peer model; the only difference is that the whole architecture is condensed into one physical device. Each customer is assigned an independent routing table (virtual routing table) that corresponds to the dedicated PE-router in the traditional peer-to-peer model. Routing across the provider backbone is performed by another routing process that uses global IP routing table, corresponding to the intra-POP Prouter in a traditional peer-to-peer model. The MPLS VPN backbone provides a Layer 3 backbone in which the CE routers see PE routers as additional customer routers in the path. The PE routers maintain separate routing tables for each customer.
2-102
Customer MPLS Perspective

CE routers run EIGRP and exchange routing updates with the PE router The PE router appears as another router in the customers network The service providers P-routers are hidden from the customer CE-routers are unaware of MPLS VPN EIGRP parameters must be agreed upon with service provider
RO UTE v 1.02-28
The MPLS VPN technology has the following routing requirements: The customer routers should not be aware of MPLS VPN. They should run standard IP routing software. The provider core routers (P-routers) must not carry VPN routes, in order to ensure the MPLS VPN solution is scalable. The provider edge routers (PE-routers) must support MPLS VPN services and traditional Internet services. The MPLS VPN backbone looks like a standard corporate backbone to the CE-routers. The CErouters run standard IP routing software and exchange routing updates with the PE-routers that appear to them as normal routers in customers network. The standard design rules that are used for enterprise MPLS VPN backbones can be applied to the design of the customers network. The P-routers are hidden from the customers view and CE-routers are unaware of the MPLS VPN. The internal topology of the MPLS backbone is therefore transparent to the customer.
2-103
Ethernet Port-to-Port Connectivity

Customer routers R1 and R2 exchange Ethernet frames Frame propagation occurs across the MPLS transport network Ethernet frames: from R1 to PE1 and from PE2 to router R2 MPLS packet: Between PE1 and PE2 EoMPLS service does participate in Spanning Tree Protocol nor learns MAC addresses
RO UTE v 1.02-29
An MPLS backbone provides a Layer 2 Ethernet port-to-port connection between the two customer routers R1 and R2. Routers R1 and R2 are exchanging Ethernet frames. The Provider Edge 1 (PE1) router takes whatever Ethernet frame it receives from router R1 on the link to PE1, encapsulates it into an MPLS packet, and forwards it across the backbone to the PE2 router. PE2 de-encapsulates the MPLS packet and reproduces the Ethernet frame on its link towards router R2. The AToM feature does not include any MAC layer address learning and filtering. That means that routers PE1 and PE2 do not filter any frames based on those addresses. Nor does the AToM feature use STP (Spanning Tree Protocol). Bridge protocol data units (BPDUs) are propagated transparently and not processed. The LAN loop detection must be performed by other functions or avoided by design.
2-104
Ethernet VLAN Connectivity

Customer routers R1 and R2 exchange Ethernet frames via VLAN subinterfaces Frame propagation occurs across the MPLS transport network Ethernet frames: from R1 to PE1 and from PE2 to router R2 MPLS packet: Between PE1 and PE2 EoMPLS service does participate in Spanning Tree Protocol nor learns MAC addresses
RO UTE v 1.02-30
The two customer routers R1 and R2 are connected to the MPLS edge routers PE1 and PE2 via VLAN subinterfaces. The interface encapsulation between routers R1 and R2 and the PE routers supports VLANs. Different subinterfaces in the PE routers are used to connect to different VLANs. The PE1 subinterface to the VLAN where router R1 is connected is used for AToM forwarding. When an Ethernet frame arrives on the specific VLAN subinterface, it is encapsulated into MPLS and forwarded across the backbone to router PE2. Router PE2 de-encapsulates the packet and reproduces the Ethernet frame on the outgoing subinterface toward router R2. Although the learning of MAC addresses and STP are not features of AToM, combining AToM with a LAN switch allows the service provider to utilize those missing features.
2-105
EIGRP over EoMPLS
RO UTE v 1.02-31
In the example in the slide, it is assumed that the MPLS network is configured properly and only the EIGRP configuration is observed. When deploying EIGRP over EoMPLS, there are no changes to the EIGRP configuration from the customer perspective. EIGRP needs to be enabled with the correct autonomous system (AS) number (the same on both routers R1 and R2). In addition, the network commands must include all of the interfaces required in the EIGRP process. This applies to the link toward routers PE1 and PE2 as well as routers R1 and R2, which will form the neighbor relationship to each other over the MPLS backbone. From the EIGRP perspective, the MPLS backbone and routers PE1 and PE2 are not visible. A neighbor relationship is established directly between routers R1 and R2 as it is visible from the show ip eigrp neighbors command output.
2-106
EIGRP over Layer 3 MPLS VPN


RO UTE v 1.02-32
Routers R1 and R2 are deployed with EIGRP as if there were a corporate core network between them. EIGRP is enabled on the proper interfaces using the network command. The only difference is that the customer has to agree with the service provider regarding the EIGRP parameters (such as the AS number, authentication password, and so on), as these parameters are often governed by the service provider. The PE routers receive IPv4 routing updates from the CE routers and install these updates in the appropriate virtual routing and forwarding (VRF) table. This part of the configuration and operation is the responsibility of a service provider.
2-107
Summary
Summary
When EIGRP is deployed over a Frame Relay physical interface, neighbor loss is detected after the hold time expires or all DLCIs are down. EIGRP routing behavior over Frame Relay multipoint interfaces is equivalent to NBMA physical interfaces. When EIGRP is deployed over a Frame Relay point-to-point interface, neighbor loss is detected after the hold time expires or the interface DLCI goes down EIGRP performs equal-cost load balancing by default for up to four paths (up to six paths can be supported).
RO UTE v 1.02-33
Summary (Cont.)
To support unequal-cost load balancing, a multiplier parameter (variance) should be configured. EIGRP uses up to 50% of the bandwidth of an interface by default. This may not be the best option for all WAN links, due to the inherent differences in the operational characteristics of WANs. CE-routers connected to a service providers EoMPLS (Layer 2 MPLS VPN) treat the connection as a separate subnet. Therefore, EIGRP operates normally without changes in the basic configuration. A customer connected to a Layer 3 MPLS VPN must agree with its service provider on EIGRP parameters (AS number, authentication, and so on) in order to deploy routing.
RO UTE v 1.02-34
2-108
Lesson 5
Lab 2-2 Debrief

Overview
In Lab 2-2, students configure and verify EIGRP circuit emulation and Frame Relay operations. First, they configure EIGRP on point-to-point interfaces, then multipoint interfaces. After that, they adjust EIGRP over multipoint WAN interface and configure EIGRP unequal-cost path load balancing.
Objectives
Upon completing this lesson, you will be able to configure and verify EIGRP circuit emulation and Frame Relay operations. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

This topic describes the lab topology and key checkpoints used to create a solution and to start with the verification.
Lab Topology
ROUTE v1. 02-2
The figure above presents the physical lab topology used for Lab 2-2: configuring and verifying EIGRP circuit emulation and Frame Relay operations. The topology uses four pod routers and two backbone routers. All routers participate in the EIGRP routing protocol. Based on the topology, students will identify the required parameters and EIGRP configuration over point-to-point and multipoint WAN interfaces.
2-110

Task 1: Configure EIGRP over point-to-point WAN interfaces What steps did you take to configure the EIGRP routing protocol on point-to-point WAN interfaces? How do you automatically configure EIGRP to advertise any additional network that is added to the router? Can a secondary IP address be added to the router? Task 2: Configure EIGRP over a multipoint WAN interface What steps did you take to configure the EIGRP routing protocol on multipoint WAN interfaces?
ROUTE v1. 02-3
2-111
Lab Review: What Did You Accomplish? (Cont.)

Task 3: Adjusting EIGRP operation over a multipoint WAN interface What is an EIGRP split horizon? How can an EIGRP split horizon behavior be changed on a WAN multipoint interface? Task 4Deploying EIGRP unequal-cost path load balancing What do you use to manipulate the path in an EIGRP routing protocol? How can you perform path manipulation without using path control tools?
ROUTE v1. 02-4
In the first task, you configured EIGRP over point-to-point WAN interfaces. The EIGRP configuration automatically advertises any additional network that is added to the router. You also added a secondary IP address to the router. In the second task, you configured EIGRP over a multipoint WAN interface. Again, the EIGRP configuration automatically advertises any additional network that is added to the router. In the third task, you configured additional EIGRP functionalities in order to adjust the EIGRP operation over a multipoint WAN interface. Split horizon was disabled. In the fourth task, you deployed EIGRP unequal-cost path load balancing. In order to manipulate the path, you changed the metric in EIGRP.
2-112
Verification
Did you have enough information to create the implementation plan? Do EIGRP-enabled routers form adjacencies on point-to-point and multipoint links after EIGRP is configured? Do you see all of the EIGRP-advertised networks in the IP routing table as EIGRP routes (after point-to-point and after multipoint configuration respectively)? What are the changes when split horizon is disabled on the interface? What is changed to manipulate the path of the packets and what must be implemented to perform unequal-cost load balancing?
ROUTE v1. 02-5
A common approach to verifying the implementation process for a routing protocol is to answer the following questions: Did you have sufficient information to create the implementation plan? Do EIGRP-enabled routers form adjacencies on point-to-point and multipoint links after EIGRP is configured? Do you see all of the EIGRP-advertised networks in the IP routing table as EIGRP routes (after point-to-point and multipoint configuration)? What are the changes when split horizon behavior is disabled on the interface? What is changed to manipulate the path of the packets and what must be implemented to perform unequal-cost load balancing?
2-113
Checkpoints
Configure EIGRP routing protocol on point-to-point interfaces. Automatically advertise any additional network that is added to the router. Ensure EIGRP networks are present in the IP routing table. Configure EIGRP routing protocol on multipoint interfaces. Ensure new EIGRP networks are present in the IP routing table. Simulate a connectivity failure between routers R3 and R4 and examine the EIGRP operation afterwards.
ROUTE v1. 02-6
2-114
Checkpoints (Cont.)
Change the EIGRP split horizon behavior on the WAN multipoint interface Adjust the metric to manipulate load balancing. Simulate a connectivity failure between routers R1 and R3 and examine the EIGRP operation afterwards. Change the EIGRP metric to manipulate unequal-cost path load balancing. Verify connectivity.
ROUTE v1. 02-7
During the configuration and verification phase, the network operator deals with several checkpoints. After completing all configuration tasks, the network operator has either finished the lab successfully or must perform additional verification and troubleshooting. With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Configure the EIGRP routing protocol on point-to-point interfaces. Automatically advertise any additional network that is added to the router. Ensure that EIGRP networks are present in the IP routing table. Configure the EIGRP routing protocol on multipoint interfaces. Ensure new EIGRP networks are present in the IP routing table. Simulate a connectivity failure between routers R3 and R4 and examine the EIGRP operation afterwards. Change the EIGRP split horizon behavior on the WAN multipoint interface. Adjust the metric to manipulate load balancing. Simulate a connectivity failure between routers R1 and R3 and examine the EIGRP operation afterwards. Change the EIGRP metric to manipulate unequal-cost path load balancing. Verify connectivity.
2-115

A Sample Solution
EIGRP is configured on point-to-point and multipoint interfaces. All of the specific IP subnets used in the network are advertised, as well as all new networks added later. Split horizon is disabled, and the metric is changed in order to provide load balancing and unequal-cost path load-balancing.
ROUTE v1. 02-8
The sample solution includes implementation details and details for each task of the implementation plan. Different solutions are possible and the figure shows a few details of a successful configuration. Proper implementation includes the following details: EIGRP is configured on point-to-point and multipoint interfaces. All of the specific IP subnets used in the network (including all networks added later) are advertised. Split horizon behavior is disabled and the metric is changed in order provide load balancing and unequal-cost path load balancing.
2-116
A different metric and administrative distance can be applied as well as filtering or static routes can be used in a few segments of the EIGRP network. EIGRP-specific functionalities do not have many alternative solutions; while another routing protocol can be used, this is not a realistic solution.
ROUTE v1. 02-9
A different metric and administrative distance can be applied, as well as filtering or static routes can be used in few segments of the EIGRP network to provide a similar solution. However, EIGRP-specific functionalities do not have many alternative solutions. To implement a similar solution, another routing protocol can be used, which is not a realistic solution as changing the routing protocol is not the case during fine tuning of the existing protocol.
2-117
Q and A
Why is the selection of a routing protocol important? What is the difference between point-to-point and multipoint interfaces when configuring an EIGRP? Why is changing the metric important? How does split horizon work?
RO UTE v 1.02-10
The routing protocol, with its metric and administrative distance, exchanges routing updates. It also populates the IP routing table, which is used for destination-based forwarding. Different routing protocols process routing updates in different ways. When configuring EIGRP on point-to-point interfaces, just two routers are connected to the link. They exchange routing updates. If the interface is a multipoint interface, routing updates received from one neighbor must be sent to another neighbor through the same interface. The metric provides the importance or the quality of the routes within a routing protocol. By manipulating the administrative distance and metric value, you can implement path manipulation, as well. Because of the split horizon behavior, the routing updates are not sent back to the interface from which they were received. This breaks the exchange of EIGRP routing updates.
2-118
Summary
Summary
Configure EIGRP on point-to-point interfaces and advertise all of the specific IP subnets in the network; you should also provide automatic advertising of any additional network that is added to the router. Configure EIGRP on the multipoint interfaces and advertise all of the specific IP subnets in the network; you should also provide automatic advertising of any additional network that is added to the router. Manipulate the EIGRP configuration on the multipoint interface by disabling split horizon. Change the metric in order to deploy unequal-cost path load balancing.
RO UTE v 1.02-11
2-119
2-120
Lesson 6
Implementing and Verifying EIGRP Authentication

Overview
You can prevent your router from receiving false route updates by configuring neighbor router authentication. Enhanced Interior Gateway Routing Protocol (EIGRP) neighbor authentication (also called neighbor router authentication or route authentication) can be configured in such a way that routers can participate in routing based on predefined passwords. This lesson describes EIGRP Message Digest 5 (MD5) authentication and how to configure and verify it.
Objectives
Upon completing this lesson, you will be able to implement and verify authentication in an EIGRP network. This ability includes being able to meet these objectives: Determine router authentication for EIGRP. Determine MD5 authentication for EIGRP. Implement MD5 authentication for EIGRP. Verify MD5 authentication for EIGRP.
Router Authentication for EIGRP

This topic describes the router authentication used by routing protocols.
Router Authentication
Implement security to the routing protocol by supporting authentication A router authenticates the source of each routing update packet that it receives. Prevent false routing updates from updating the routing table: Prevent deliberate false routing updates sourced by unapproved sources Ignore malicious updates, thus preventing them from disrupting the routing or taking down the adjacency
ROUTE v1. 02-2
Neighbor router authentication (also called route authentication) can be configured in such way that routers only participate in routing based on predefined passwords. Without neighbor authentication, unauthorized or deliberately malicious routing updates can compromise the security of your network traffic. A security compromise may occur if any unfriendly party interferes with your network. For example, an unauthorized router might launch a fictitious routing update to convince your router to send traffic to an incorrect destination. When neighbor authentication has been configured on routers, those routers authenticate the source of each routing update packet they receive. They do so by exchanging an authentication key that is known to both the sending and the receiving router. By default, no authentication is used for routing protocol packets.
2-122
Router Authentication (Cont.)

Many routing protocols support authentication Simple password authentication is supported by: OSPF RIPv2 MD5 authentication is supported by: EIGRP OSPF RIPv2 BGP
ROUTE v1. 02-3
There are two types of authentication: simple password authentication (also called plaintext authentication) and Message Digest 5 (MD5) authentication. Simple password authentication is supported by Open Shortest Path First (OSPF) and Routing Information Protocol version 2 (RIPv2). MD5 authentication is supported by OSPF, RIPv2, Border Gateway Protocol (BGP), and EIGRP.
Note Authentication for EIGRP, OSPF, and BGP is covered in this course.
2-123
Simple Password vs. MD5 Authentication

Simple password authentication: The router sends a packet and a key. The neighbor checks if the key matches its key. The process is not secure. MD5 authentication: This authentication is secure, as described in RFC1321. This authentication does not include confidentiality (content not encrypted). The router generates a message digest. The message digest is sent with the packet. The key is not sent.
ROUTE v1. 02-4
The behavior of simple password authentication is the same as that of MD5 authentication, except that MD5 sends a message digest instead of the authenticating key itself. MD5 creates the message digest using the key and a message, but the key itself is not sent, which prevents it from being read while it is being transmitted. Simple password authentication sends the authenticating key itself over the wire.
Note Note that simple password authentication is not recommended for use as part of your security strategy, because it is vulnerable to passive attacks. Anybody with a link analyzer could easily view the password on the wire. The primary use of simple password authentication is to avoid accidental changes to the routing infrastructure. Using MD5 authentication, however, is a recommended security practice.
With simple password authentication, a password (key) is configured on a router, and each participating neighbor router must be configured with the same key. When a packet is sent over the wire, the password, in plaintext, is sent along with it. MD5 authentication is a cryptographic authentication. A key (password) and key ID are configured on each router. The router uses an algorithm to generate a message digest (also called a hash) from the key and key ID, and appends the message digest to the packet. Unlike simple authentication, the key is not exchanged over the wire; the message digest is sent instead of the key, which ensures that no one can eavesdrop on the line and learn keys during transmission. Although MD5 authentication provides authenticity, it does not provide confidentiality. The content of the routing update is not encrypted.
2-124
Note
As with all keys, passwords, and other security secrets, it is imperative that you closely guard authenticating keys used in neighbor authentication. In order to obtain the security benefits of this feature, you must keep all authenticating keys confidential. Also, when performing router management tasks via Simple Network Management Protocol (SNMP), do not ignore the risk associated with sending keys using non-encrypted SNMP.
2-125
MD5 Authentication for EIGRP

This topic describes MD5 authentication as it is used in EIGRP.
MD5 Authentication for EIGRP

EIGRP supports MD5 authentication. The router generates a MD5 message digest. Multiple keys can be configured in all EIGRP routers. The receiving router computes the MD5 hash from the received EIGRP information. Time should be synchronized between all routers, and NTP can be used.
ROUTE v1. 02-5
EIGRP supports MD5 authentication to prevent the introduction of unauthorized or false routing messages from unapproved sources. EIGRP neighbor authentication (also called neighbor router authentication or route authentication) can be configured in such way that routers can participate in routing based on predefined passwords. By default, no authentication is used for EIGRP packets. EIGRP must be configured to use MD5 authentication. When neighbor authentication has been configured on a router, the router authenticates the source of each routing update packet that it receives. In order to start using EIGRP MD5 authentication, you must configure an authenticating key (sometimes referred to as a password) and a key identifier on both the sending router and the receiving router. Each EIGRP router takes the key and key ID and generates a message digest that is appended to each routing update and sent to the neighbor. The receiving router computes the MD5 hash from the received EIGRP information. If the hash matches the value received, the packet is accepted. If it does not, the packet is silently dropped. Each key has its own key ID, which is stored locally. The combination of the key ID and the interface associated with the message uniquely identifies the authentication algorithm and the MD5 authentication key in use. You can increase the security of EIGRP MD5 authentication by making frequent key changes. The definition of multiple keys is supported, which can be changed based on time that is defined in the configuration. Transitioning between the keys is implemented in a way that provides non-disruptive exchange of EIGRP routing updates. The key changes must be well-planned and supported by the time synchronization between the routers. The key rollover works only if the times on the adjacent routers are synchronized. You can use several mechanisms for time synchronization. Network Time Protocol (NTP) is the most commonly used time synchronization mechanism to ensure that the correct time is used by all the participating EIGRP routers using the key rollover mechanism.
Key Chain
EIGRP allows keys to be managed using key chains A key chain is a set of keys associated with an interface. Includes key IDs, keys, and key lifetimes The first valid activated key is used in the outgoing direction. Incoming packets are checked against all valid keys.
ROUTE v1. 02-6
EIGRP allows keys to be managed using key chains. Each key definition within the key chain can specify a time duration for when that key will be activated (its lifetime). Then, during a given key's lifetime, routing update packets are sent with this activated key. Only one authentication packet is sent, regardless of how many valid keys exist. The software examines the key numbers in order from lowest to highest. It then uses the first valid key it encounters. Keys cannot be used at times when they are not activated. Therefore, for a given key chain, you should ensure that key activation times overlap. This will help you avoid any period of time for which no key is activated. If a period occurs during when no key is activated, neighbor authentication cannot occur, and therefore routing updates will fail. Note that the router needs to know the correct time to be able to rotate through keys in a way that is synchronized with the other participating routers, so that all routers are using the same key at the same moment. Refer to the Network Time Protocol (NTP) and calendar commands in the Performing Basic System Management chapter of the Cisco IOS Configuration Fundamentals Configuration Guide for information about configuring the time on your router.
2-127
Implementing MD5 Authentication for EIGRP

This topic describes how to configure MD5 authentication for EIGRP.
Planning for EIGRP Authentication

Examine the existing EIGRP configuration Define the authentication type Define how many keys will be used Define if an optional lifetime parameter will be used
ROUTE v1. 02-7
Before configuring authentication for EIGRP, a network administrator must examine the existing EIGRP configuration and define the network requirements. The existing EIGRP configuration defines which autonomous system (AS) number is used for EIGRP and which routers and interfaces participate in the EIGRP configuration. The network requirements for EIGRP authentication define which parameters must be gathered and include the definition of the authentication type, number of keys used in the EIGRP network, and optional lifetime parameters used. The next step is to gather of all of the parameters needed to provide enough details for the network operator to start setting up EIGRP authentication.
2-128
Requirements for EIGRP Authentication

EIGRP AS number Authentication mode One or more keys Key lifetimes (optional)
ROUTE v1. 02-8
Requirements to configure EIGRP authentication include the following elements: The EIGRP AS number The authentication mode selected The definition of one or more keys The lifetime of each defined key The EIGRP AS number must be defined, as authentication is locked to the EIGRP process. The authentication mode used is MD5. The definition of the keys is a process by which the network administrator and network designer must develop a security plan. They are not trying to encrypt the packet, but authenticate the source of the EIGRP routing updates. Using more keys and changing them can reduce the potential risk. When more keys are used, it makes sense to change the keys based on predefined time intervals. A keys lifetime can be defined. It is optional and requires an NTP server in order to synchronize the clocks of all routers running EIGRP.
2-129
Steps to Configure EIGRP MD5 Authentication

Configure the authentication mode for EIGRP Configure the key chain Configure the lifetime of each key in the key chain Enable authentication to use the key or keys in the key chain
ROUTE v1. 02-9
EIGRP MD5 authentication configuration steps:

Step 1 Step 2 Step 3 Step 4
Configure the authentication mode for EIGRP. Configure the key chain. Optional: Configure the lifetime parameters for the keys. Enable authentication to use the key or keys in the key chain.
To complete these steps, you must have information about the existing EIGRP process, definitions of all the keys, and any lifetime parameters to be used in the configuration.
2-130
Configure Authentication Mode
Specify the type of authentication used in EIGRP packets for router R1 and R2
RO UTE v 1.02-10
You must configure authentication between any two neighbors exchanging EIGRP routing updates. You must also use the correct AS number and enable the authentication configuration on all interfaces between the neighbors across the EIGRP domain. The example in this slide shows two routers, R1 and R2, that are running the EIGRP process with AS number 110. They are connected via the serial 0/0/1 interfaces and configuration must be applied to both interfaces involved. To configure MD5 authentication for EIGRP, complete the following steps:
Step 1
Enter the configuration mode for the interface on which you want to enable authentication. Specify the type of the authentication using the ip authentication mode eigrp 110 md5 interface command.
Step 2
The only authentication type available is MD5, and AS number 110 is used in the example on this slide, where both routers R1 and R2 are configured for MD5 authentication. When authentication is configured, an MD5 keyed digest is added to each EIGRP packet in the specified AS. For more details about the ip authentication mode eigrp command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-131
Configure the Key Chain

Create the key-chain to enter key chain key configuration mode. Create an authentication key on a key chain. Define the authentication string for a key (password).
RO UTE v 1.02-11
When authentication is enabled on the interface, a group of authentication keys must be defined. The key chain global configuration command is used to define all of the keys used for EIGRP MD5 authentication. Once you are in the key chain configuration mode, use the key command to identify the key in the key chain. Each key is defined by the number, which defines the key ID. When the key command is used, the configuration enters the key chain key configuration mode, where the key-string authentication-key configuration command must be used to specify the authentication string (or password). The key ID and authentication string must be the same on all neighboring routers. In the example on this slide, each interface is configured to enter its own key chain. The key chain configured on router R1 is routerR1chain and key-chain on router R2 is routerR2chain. Inside each of the key chains, two keys are defined, key 1 and key 2.
Note The key ID number of an authentication key on a key chain can range from 0 to 2147483647, and there is no need for the numbers to be consecutive.
Key 1 includes the authentication string firstkey and key 2 includes the authentication string secondkey.
Note The authentication string used to authenticate sent and received EIGRP packets can contain from 1 to 80 uppercase and lowercase alphanumeric characters; the one exception is that the except that the first character cannot be a number.
For more details about the key chain, key, and key-string (authentication) commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-132
Configure the Lifetime of The Key or Keys
If you wish, you can define when the key will be accepted or sent.
RO UTE v 1.02-12
Once you define more keys and ensure each key includes an authentication string, you can then configure a key lifetime, if you wish. Two commands can be used to define the lifetime of the key. The accept-lifetime command in the key chain key configuration mode is used to set the time-period during which the authentication key on a key chain is received as valid. The sendlifetime command in the key chain key configuration mode is used to set the time-period during which an authentication key on a key chain is valid to be sent. In the example on this slide, router R1 is configured with the key chain routerR1chain and two keys are inside the key chain. Each key has an authentication string and lifetime specified. The network administrator wants to change the keys on all the routers in the network on a regular basis to improve the security, initially every month. One week is enough time to change the keys on all the routers, so the validity of key 2 is configured 1 week before the expiration of key 1 to ensure that all the routers in the network will accept the configuration. The authentication string for key 1 is set to firstkey and the accept-lifetime and send-lifetime commands have been used to specify the validity of key 1. This key is acceptable for use on packets received by router R1 from January 1, 2009 onwards, as specified in the acceptlifetime 04:00:00 Jan 1 2009 infinite command. However, the send-lifetime 04:00:00 Jan 1 2009 04:00:00 Jan 31 2009 command specifies that this key was valid for use when sending packets from January 1, 2009 until January 31, 2009. It will no longer be valid for use in sending packets after 4:00 a.m. on January 31, 2009. The authentication string for key 2 is set to secondkey. The accept-lifetime and send-lifetime commands have been used to specify the validity of key 2, as well as for key 1. Key 2 is acceptable for use on packets received by router R1 from January 25, 2009 onwards, as specified in the accept-lifetime 04:00:00 Jan 25 2009 infinite command. This key can also be used when sending packets from January 25, 2009 onwards, as specified in the send-lifetime 04:00:00 Jan 25 2009 infinite command. When more than one key is configured, key 1 is used first until its lifetime expires. Then the next key is used. The bar chart in this slide presents the result of the configuration. From
Starting January 1, 2009, key 1 was used for sent packets as well as for received packets. Starting January 25, 2009, key 2 was valid for sent and received packets, but it was not actually used, since key 1 was still valid. Starting January 31, 2009, key 1 was no longer valid. Immediately key 2 started to be used for all sent and received packets. From January 25, 2009 to January 31, 2009, router R1 will accept and attempt to verify the MD5 digest of any EIGRP packets with a key ID equal to 1 or a key ID equal to 2. All other MD5 packets will be dropped. The syntax of the start time in the accept-lifetime and send-lifetime commands can be either of the following: hh:mm:ss month date year hh:mm:ss date month year When using the infinite parameter to configure the lifetime, the key is valid for use on received packets from the start-time value and never expires. The default start time and the earliest acceptable date is January 1, 1993. If an end time is specified, the key is valid for use on the received packets from the start-time value until the end-time value. The syntax is the same as the start-time value. The end-time value must be after the start-time value. The default end time is infinite. The same or a similar configuration can be applied to router R2 as well. The optional lifetime parameters can be the same or different. It is important that at least one key is valid to send and at least one key is valid as a receive key. Of course both keys must be the same, otherwise it is very likely that the authentication will fail. For more details about the accept-lifetime and send-lifetime commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-134
Enable Authentication of EIGRP Packets
Enable authentication of EIGRP packets using the key or keys in the key chains routerR1chain and routerR2chain on routers R1 and R2, respectively.
RO UTE v 1.02-13
When an authentication type is selected and a key chain is configured, then authentication of EIGRP packets must be enabled on all interfaces participating in the EIGRP domain as well. Authentication is enabled using the ip authentication key-chain eigrp interface command. In the example on this slide, each interface is configured to use keys in its local key chain. Router R1 is configured to use the routerR1chain key chain and router R2 is configured to use the routerR2chain key chain. The key chain contains the list of all the available keys and must be configured separately to specify all of the keys required. The name of the key chain is of local significance and can be different on the two neighboring routers.
Note The name of the authentication key chain is a user-defined string.
For more details about the ip authentication key-chain eigrp command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-135
Router R1 Configuration for MD5 Authentication
RO UTE v 1.02-14
The configuration of router R1 on this slide shows that MD5 authentication is configured on the serial 0/0/1 interface with the ip authentication mode eigrp 110 md5 command. The ip authentication key-chain eigrp 110 routerR1chain command specifies that the key chain routerR1chain is to be used. The key chain routerR1chain command indicates to enter configuration mode for the routerR1chain key chain. Two keys are defined. Key 1 is set to firstkey with the key-string firstkey command. This key is acceptable for use on packets received by router R1 from January 1, 2009 onward, as specified in the accept-lifetime 04:00:00 Jan 1 2009 infinite command. In contrast, the send-lifetime 04:00:00 Jan 1 2009 04:00:00 Jan 31 2009 command specifies that this key is valid for use when sending packets from January 2, 2009 to January 31, 2009. Key 2 is set to secondkey with the key-string secondkey command. This key is acceptable for use on packets received by router R1 from January 25, 2009 onward, as specified in the acceptlifetime 04:00:00 Jan 25 2009 infinite command. This key can also be used when sending packets from January 25, 2009 onward, as specified in the send-lifetime 04:00:00 Jan 25 2009 infinite command. Router R1 will therefore accept and attempt to verify the MD5 digest of any EIGRP packets with a key ID equal to 1. Router R1 will also accept a packet with a key ID equal to 2. All other MD5 packets will be dropped. Router R1 will send all EIGRP packets using key 2, because key 1 is no longer valid for use when sending packets. MD5 EIGRP authentication configuration on router R2 is very similar. The lifetimes of the keys are typically the same, and the key chain names can be different (it is of local significance in the router). The IP addresses on the interfaces are different and set according to the IP addressing scheme of router R2. In the ip authentication key-chain eigrp command, the configuration must refer to its local key chain name and networks advertised under the EIGRP 110 routing process must reflect the real networks used.
2-136
Verifying MD5 Authentication for EIGRP

This topic describes how to verify MD5 authentication for EIGRP.
Verifying MD5 Authentication for EIGRP

Verify that the EIGRP neighbor relationship is up

Verify that the IP routing table is populated

If authentication is not successful, then routers will not process EIGRP packets and will not form neighbor relationships. Also, routers will not build the EIGRP tables and populate the IP routing table with EIGRP routes. The output on the figure on this slide shows two commands that can be used to verify the EIGRP neighbors and IP routing table. The show ip eigrp neighbors verification command shows the EIGRP neighbors table on router R1, which indicates that the two routers have successfully formed an EIGRP adjacency. The show ip route verification command on router R1 shows that the 172.17.0.0 network has been learned via EIGRP over the serial connection, which proves that the authentication must have been successful. For more details about the show ip eigrp neighbors and show ip route commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-137
Verifying MD5 Authentication for EIGRP (Cont.)

Verify the key chains and keys This output of the show key chain command is from January 27, 2009.
RO UTE v 1.02-16
You can use the show key chain verification command to see the key chain, key string, and the lifetime of the keys configured under the key chain. The keys must be the same on both neighbors and the lifetime must be set properly. The output of the show key chain command on router R1 is shown on this slide. Key chain routerR1chain and both key 1 (with authentication string firstkey) and key 2 (with authentication string secondkey) are shown in the sample output. Under each key, the lifetime of the key is shown as well. You can verify the configuration by checking that the output is the same from the neighboring router (router R2 in our topology). For more details about the show key chain command, please check the Cisco IOS IP routing protocols command reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-138
Verifying MD5 Authentication for EIGRP (Cont.)

Use debug to verify the operation
RO UTE v 1.02-17
Use the debug eigrp packet command to display general debugging information. If a communication session is closing when it should not be, an end-to-end connection problem could be the cause. The debug eigrp packet command is useful for analyzing the messages traveling between the local and remote hosts, including authentication messages. The sample output on this slide shows successful MD5 authentication. The output of the debug eigrp packet command on router R1 shows that router R1 is receiving EIGRP packets with MD5 authentication, with a key ID equal to 1, from router R2. Similarly, the output of the debug eigrp packet command on router R2 shows that router R2 is receiving EIGRP packets with MD5 authentication, with a key ID equal to 2, from router R1. For more details about the debug eigrp packet command, please check the Cisco IOS debug command reference via the following link: http://www.cisco.com/en/US/docs/ios/debug/command/reference/db_book.html
2-139
Misconfigured Key

The MD5 authentication key is different for routers R1 and R2.

The EIGRP neighbor relationship is down.
RO UTE v 1.02-18
The sample output on this slide shows the MD5 authentication problems. The output of the debug eigrp packet command on router R1 shows that router R1 is receiving EIGRP packets with MD5 authentication, with a key ID equal to 2, from router R2, but there is an authentication mismatch. The EIGRP packets from router R2 are ignored and the neighbor relationship is declared to be down. The output of the show ip eigrp neighbors command confirms that router R1 does not have any EIGRP neighbors. The two routers keep trying to reestablish their neighbor relationship using key 2. Because of the different key strings used by each router in this scenario, router R1 will authenticate hello messages sent by router R2 using the key string secondkey. However, when router R1 sends a hello message back to router R2 using a different key string, an authentication mismatch occurs.
2-140
Summary
Summary
There are two types of router authentication: simple password and MD5 authentication. When EIGRP authentication is configured, the router generates and checks every EIGRP packet and authenticates the source of each routing update packet that it receives. EIGRP supports MD5 authentication. To configure MD5 authentication, use the ip authentication mode eigrp and ip authentication key-chain interface commands. The key chain must also be configured to define the keys. Use show ip eigrp neighbors, show ip route, and debug eigrp packets to verify MD5 authentication.
RO UTE v 1.02-19
2-141
2-142
Lesson 7
Lab 2-3 Debrief

Overview
In Lab 2-3, students configure and verify EIGRP authentication. They also implement EIGRP authentication over LAN and WAN interfaces.
Objectives
Upon completing this lesson, you will be able to configure and verify EIGRP authentication. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

Lab Topology
ROUTE v1. 02-2
The figure above presents the physical lab topology used for the Lab 2-3: Configure and Verify EIGRP Authentication. The topology uses four pod routers. All routers participate in the EIGRP routing protocol. Based on the topology, students will identify the required parameters for configuring EIGRP authentication on LAN and WAN interfaces.
2-144

Task 1: Configure EIGRP authentication over LAN interfaces What steps did you take to configure EIGRP authentication on a LAN segment? How can you configure keys so they do not expire? How can you define the key chain used for router authentication? Task 2: Configure EIGRP authentication over WAN interfaces What steps did you take to configure EIGRP authentication on a WAN segment? How can you configure keys so they do not expire? How can you define the key chain used for router authentication?
ROUTE v1. 02-3
In the first task, you configured EIGRP authentication over LAN interfaces. You configured a key chain with a key that never expires. You enabled secure authentication and used the defined key chain to provide security when exchanging EIGRP packets. In the second task, you configured EIGRP authentication over WAN interfaces. You configured a second key chain with a key that never expires. And again, you enabled secure authentication using the defined key chain.
2-145
Verification
Did you have enough information to create an implementation plan? Did you enable EIGRP authentication on the LAN interfaces? Did you use a secure authentication method for authentication over LAN interfaces? Did you establish adjacencies between the routers over the LAN interface and enter EIGRP routes into the IP routing table? Did you enable EIGRP authentication on the WAN interfaces? Didi you use a secure authentication method for authentication over WAN interfaces? Did you establish adjacencies between the routers over WAN interface and enter EIGRP routes into the IP routing table?
ROUTE v1. 02-4
A common approach to verifying the implementation process for a routing protocol is to answer the following questions: Did you have enough information to create an implementation plan? Did you enable EIGRP authentication on the LAN interfaces? Did you use a secure authentication method for authentication over LAN interfaces? Did you establish adjacencies between the routers over the LAN interface and enter EIGRP routes into the IP routing table? Did you enable EIGRP authentication on the WAN interfaces? Did you use a secure authentication method for authentication over WAN interfaces? Did you establish adjacencies between the routers over WAN interface and enter EIGRP routes into the IP routing table?
2-146
Checkpoints
Configure the key chain to use for authentication on LAN interfaces. Configure a key to use in the key chain for authentication over the LAN interfaces. Enable secure authentication on LAN segments. Use the defined key chain for router authentication. Configure another key chain to use for authentication on WAN interfaces. Configure a key to use in the key chain for authentication over the WAN interfaces. Enable secure authentication on WAN segments. Use the defined key chain for router authentication.
ROUTE v1. 02-5
During the configuration and verification phase, the network operator can deal with several checkpoints. After completing all configuration tasks, the network operator has either finished the lab successfully or must perform additional verification and troubleshooting. With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Configure the key chain to use for authentication on LAN interfaces. Configure a key to use in the key chain for authentication over the LAN interfaces. Enable secure authentication on LAN segments. Use the defined key chain for router authentication. Configure another key chain to use for authentication on WAN interfaces. Configure a key to use in the key chain for authentication over the WAN interfaces. Enable secure authentication on WAN segments. Use the defined key chain for router authentication.
2-147

Sample Solution
Use static routes to establish reachability instead of a routing protocol, which is typically not recommended, as static routes do not scale. Another routing protocol can be used to implement a similar solution and use the supported authentication type. Changing the routing protocol is not a realistic solution as changing the routing protocol is not the case during fine tuning of the existing protocol.
ROUTE v1. 02-6
The sample solution includes implementation details and details for each task of the implementation plan. Different solutions are possible and this slide shows a few details of a successful configuration. Proper implementation includes the following items: Configure a key chain with the key used for LAN authentication and use it for router authentication on LAN segments. Configure another key chain with the key used for WAN authentication and use it for router authentication on WAN segments.
2-148
Use static routes to establish reachability instead of routing protocol, which is typically not possible, as static routes do not scale. Another routing protocol can be used to implement a similar solution. Changing the routing protocol is not a realistic solution.
ROUTE v1. 02-7
Use static routes to establish reachability instead of a routing protocol, which is typically not recommended, as static routes do not scale. Another routing protocol can be used to implement a similar solution and use the supported authentication type. Changing the routing protocol is not a realistic solution as changing the routing protocol is not the case during fine tuning of the existing protocol.
2-149
Q and A
Why should you use authentication with routing protocols? What kind of authentication does EIGRP support? When do the keys in a key chain expire? Can you change the key expiration time? What is the difference between authentication on LAN and WAN segments?
ROUTE v1. 02-8
Authentication provides additional security in networks by verifying the source and destination of each routing update. Only routers with the correct authentication configured can exchange routing protocol packets. EIGRP supports MD5 authentication. The expiration time can be configured for each key and the key can be configured not to expire. There is no difference between LAN and WAN authentication. In both cases, you must enable MD5 authentication, configure a key chain, and use the keys in the key chain properly.
2-150
Summary
Summary
Configure EIGRP authentication on LAN segments, where the key without expiration is used in the key chain. Configure EIGRP authentication on WAN segments, where the key without expiration is used in the key chain.
ROUTE v1. 02-9
2-151
2-152
Lesson 8
Advanced EIGRP Features in an Enterprise Network

Overview
Network administrators benefit from understanding how to configure Enhanced Interior Gateway Routing Protocol (EIGRP) to prevent common routing problems that hinder network scalability. For example, you can implement EIGRP stub routers to limit the EIGRP query range, making EIGRP more scalable with fewer complications. EIGRP is a scalable routing protocol, which ensures that as a network grows larger, it operates efficiently and adjusts rapidly to changes. This lesson describes advanced EIGRP features and practical EIGRP-specific design and configuration techniques to implement an effective, scalable network.
Objectives
Upon completing this lesson, you will be able to implement advanced EIGRP features in an Enterprise Network by applying the planned implementation processes using correct Cisco IOS commands and applications. You will also be able to verify that the configuration was correctly implemented. This ability includes being able to meet these objectives: Define scalability in large networks. Understand EIGRP queries. Define SIA connections in EIGRP. Understand EIGRP stub routers.
Scalability in Large Networks

This topic explains factors affecting scalability in large internetworks.
Scalability in Large Networks

Operating one large, flat EIGRP network is not a scalable solution for to the following reasons: Large routing tables High memory requirements Large amount of routing traffic
ROUTE v1. 02-2
Large, flat EIGRP networks are normally not scalable for two main reasons: High memory demands can lead to problems. The problems result from having a large topology table, having a large number of routes in a routing table, and, in some environments (such as a concentration of routers at a central site), from having a large number of neighbors in an adjacency table. High bandwidth demands can also create problems, resulting from the exchange of routing updates. The sending of queries and replies in one large EIGRP domain (which may include links with low bandwidth and links with a significant number of transmission errors) often results in a large amount of routing traffic, which consequently results in even more traffic and congestion.
2-154
Factors that Influence EIGRP Scalability

Amount of routing information exchanged between peers Number of routers Depth of topologythe number of hops that information must travel to reach all routers Number of alternate paths through the network
ROUTE v1. 02-3
The following are some of the factors that affect network scalability: Amount of information exchanged between neighbors: If more routing information than is necessary is exchanged between EIGRP neighbors, the routers have to work harder both at neighbor startup and when reacting to changes in the network. Route summarization is needed to improve the convergence time. Number of routers: When a topology change occurs in the network, EIGRP resource consumption is directly related to the number of routers that are involved in the change. Depth of the topology: The topology depth can affect the convergence time. Depth refers to the number of hops that information must travel to reach all routers. A multinational network without route summarization is an example of a network with large depth and, therefore, higher convergence times. A three-tiered network design (as described in Module 1) is highly recommended for all IP routing environments. There should never be more than seven hops between any two routing devices on an internetwork. The propagation delay and query process across multiple hops when changes occur may slow network convergence. Number of alternate paths through the network: A network should provide alternate paths to avoid single points of failure. However, too much complexity (too many alternate paths) can also lead to EIGRP convergence problems, because the EIGRP routing process needs to explore all possible paths for lost routes (using queries). This complexity creates the ideal condition for a router to become stuck-in-active (SIA) as it awaits a response to queries that are being propagated through many alternate paths.
2-155
EIGRP Design Challenges

The number of neighboring routers on the common subnet The number of changes in the network The amount of EIGRP load on the WAN Every time a route disappears from the EIGRP process, DUAL computation is neededresulting in high link utilization and CPU load
ROUTE v1. 02-4
When you implement EIGRP as the routing protocol, you need to address some design challenges. The three major factors are: The size of the topology and routing tables, including the number of neighboring routers on the common subnet The number of changes in the network The amount of EIGRP load on the WAN These three factors mainly dictate the EIGRP design and introduce the need for query boundaries (using summarization, redistribution, and so on). Without any boundaries, queries are propagated throughout the EIGRP domain and, often, all of the routers get involved in a Diffusing Update Algorithm (DUAL) computation. This EIGRP feature not only places additional bandwidth demands on links in the network, but also results in high CPU utilization. Frequent DUAL computations have an effect on all tables, which are maintained by the routersfrom EIGRP structures to various caches built during the forwarding process.
2-156
EIGRP Queries
This topic explains how EIGRP uses queries to converge rapidly when a route is lost.
EIGRP Query Process

Queries are sent when a route is lost and no feasible successor is availableroute is in an active state Queries are sent to all neighboring routers on all interfaces except the interface of the successor If neighbors have the lost route information, they answer the query (and stop the query from spreading), otherwise queries are sent to their neighbors
ROUTE v1. 02-5
As an advanced distance vector protocol, EIGRP relies on neighboring routers to provide routing information. Recall that 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; a route is considered passive when a router is not performing recompilation on that route. When the route is lost, the router sends query packets to all neighbors on interfaces other than the one used to reach the previous successor (split horizon behavior). These packets query if each of the neighbors has a route to the given destination. If a router has an alternate route, it answers the query and does not propagate it further. If a neighbor does not have an alternate route, it queries each of its own neighbors for an alternate path. The queries then propagate through the network, creating an expanding tree of queries. When a router answers a query, it stops the spread of the query through that branch of the network. The figure in the slide presents a network example for which a single lost route might result in an enormous number of queries sent throughout the EIGRP domain. When the route to network 10.1.1.0 on router R1 is lost, router R1 sends a query to all neighboring routers and to all interfaces except the interface of the successor (split horizon). The query is propagated to router R2. Since it has no information about the lost route, router R2 cascades the query to its neighbors, which cascade it to their neighbors, and so on. Each query requires a reply from the neighbor and the amount of traffic increases. The network topology, in the figure in the slide, shows that there is no redundant path to network 10.1.1.0 available. The EIGRP query propagation process is far from efficient. Many queries are sent and each query is followed by a reply. Several solutions exist to optimize the query propagation process and to limit the amount of unnecessary EIGRP load on the links. The solutions that can be used are summarization, redistribution, and the EIGRP stub routing feature.
SIA Connections in EIGRP

Stuck-in-active (SIA) routes can be some of the most challenging problems to resolve in an EIGRP network. This topic explains why SIA connections occur.
EIGRP Query Process Stuck-in-Active

The router must get replies to all its queries for a lost route to start calculating successor information If any reply to the query is lost or missing within 3 minutes: The route is SIA The router resets the neighbor relationship with the neighbor that fails to reply
ROUTE v1. 02-6
EIGRP uses a reliable multicast approach to search for an alternate to a lost route; therefore, it is imperative that EIGRP receive a reply for each query it generates in the network. Once a route goes active and the query sequence is 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 three minutes (the default time), the route goes into the SIA state. When the route goes into the SIA state, the querying router resets the neighbor relationship to the neighbor that failed to reply. This setting causes the router to go active on all routes known through the lost neighbor, and to re-advertise all the routes that it knows about to the lost neighbor. The most common reasons for SIA routes are as follows: The router being queried is too busy to answer the query because of high CPU usage or memory problems and cannot allocate the memory to process the query or build the reply packet. The link between the two routers is not good; therefore, some packets are lost between the routers. While the receiving router receives enough packets to maintain the neighbor relationship, the router does not receive all of the queries or replies. A failure causes traffic on a link to flow in one direction onlythis is called a unidirectional link.
2-158
Active Process Enhancement

Before:
Router R1 resets the neighbor relationship to router R2 when the normal active timer expires.
After:
An SIA query is used from router R1. Router R3s neighbor relationship is resetproblem on the link.
ROUTE v1. 02-7
A route becomes active when it goes down or its metric become worse and there are no feasible successors. It sends a query to all its neighbors asking for a new path to the lost route. The process requires replies from all of the neighbors. If replies are lost, then two new messages are required. SIA query and SIA reply are two new additions to the type, length, value (TLV) triplets in the EIGRP packet header. These packets are generated automatically since Cisco IOS Release 12.1(5) with the Active Process Enhancement feature. This feature enables an EIGRP router to monitor the search progression for a successor route and ensures that the neighbor is still reachable. The result is improved network reliability by reducing the unintended termination of neighbor adjacency. Before a SIA query and SIA reply were available, the following would occur: 1. Router R1 sends a query for network 10.1.1.0/24 to router R2. 2. Router R2 has no entry for this network, so it queries router R3. If problems exist between router R2 and router R3, the reply packet from router R3 to router R2 may be delayed or lost. 3. Router R1 has no visibility of the downstream progress and assumes that no response indicates problems with router R2. After router R1s three-minute active timer expires, the neighbor relationship with router R2 is reset, along with all known routes from router R2. With the Active Process Enhancement feature, the events take a different course. 1. Router R1 queries downstream router R2 (with an SIA query) at the midway point of the active timer (one and a half minutes by default) about the status of the route. 2. Router R2 responds (with an SIA reply) that it is searching for a replacement route. 3. Upon receiving this SIA reply response packet, router R1 validates the status of router R2 and does not terminate the neighbor relationship.
4. Meanwhile, router R2 will send up to three SIA queries to router R3. If they go unanswered, router R2 will terminate the neighbor relationship with router R3. Router R2 will then update router R1 with an SIA reply indicating that the network 10.1.1.0/24 is unreachable. 5. Routers R1 and R2 will remove the active route from their topology tables. The neighbor relationship between routers R1 and R2 remains intact.
2-160
EIGRP Stub Routers

The stability of large-scale EIGRP networks is often dependent on the range of queries through the network. This topic explains how to mark the spokes of a large network as stubs to reduce the number of EIGRP queries and thus improve network scaling.
Updates and Queries Without an EIGRP Stub
ROUTE v1. 02-8
When a router running EIGRP loses its connection to a network, it first searches for alternate loop-free paths. If it finds none, it then sends queries to each of its neighbors, looking for an alternate path. If the neighbor does not have another path to this destination, it replies with infinity. After receiving all replies, router R1 then removes all references to this route from its local tables. In large hub-and-spoke networks, the hub routers have to build queries and process replies from each of the spokes; this limits scaling. Without the stub feature, a hub router will send a query to the spoke routers if a route is lost somewhere in the network. If there is a communication problem over the WAN link between the hub router and the spoke router, replies may not be received for all queries (this is known as SIA), and the network may become unstable. By default (when a router is not stub-enabled), queries for network 10.1.1.0/24 are sent to the remote routers, thus unnecessarily utilizing the bandwidth and possibly invoking routes that are stuck-in-active. Each of the remote sites also sends a query towards router R2, with router R2 receiving five queries that it must process and answer. If these spokes are remote sites, they typically have two connections for redundancy. Router R1 should never use the spokes as a path to anything reachable through router R2, so there is no reason to learn about, or query for, routes through these spokes. Hub-and-spoke network topologies commonly use stub routing. If a true stub network is required, the hub router can be configured to send a default route to the spoke routers. This approach is the simplest and conserves the most bandwidth and memory on the spoke routers.
2-161
Updates and Queries Using EIGRP Stub

Router R1 should never use spoke routers to reach any network available through router R2. There is no reason to learn about or query for routes through spoke routers. Spoke routers should not be used for transit trafficthey can be configured as stubs.
ROUTE v1. 02-9
The EIGRP stub routing feature allows a network administrator to prevent the sending of queries to the spoke router under any condition. Remote sites allow the hub (regional office) sites to immediately answer queries without propagating the queries to the remote sites. This saves CPU cycles and bandwidth. It also lessens the convergence time, even when the remote sites are dual-homed to two or more hub (regional) sites. The figure in the slide shows that spoke routers are configured as stubs to signal to routers R1 and R2 that the paths through the spoke routers should not be used for transit traffic. Router R1 is not sending queries for network 10.1.1.0/24 to stubs, reducing the total number of queries and total bandwidth used. Marking the remote routers as stubs also reduces the complexity of the topology. It is highly recommended that you use both EIGRP route summarization and EIGRP stub features to provide the best scalability.
Note The EIGRP stub routing feature does not automatically enable route summarization on the hub router. In most cases, the network administrator should configure route summarization on the hub routers.
Note
Although EIGRP is a classless routing protocol, it behaves in a classful way by default. For example, one default behavior of EIGRP is to have automatic summarization turned on. When you configure the hub router to send a default route to the remote router, ensure that the ip classless command is on the remote router. By default, the ip classless command is enabled in all Cisco IOS images that support the EIGRP stub routing feature.
2-162
EIGRP Stub
The EIGRP stub routing feature does the following: Improves network stability Reduces resource utilization Simplifies remote router (spoke) configuration The feature is commonly used in hub-and-spoke topologies Each stub router reports its status to neighbors. Queries are not sent to the stub routers.
RO UTE v 1.02-10
The EIGRP stub feature was first introduced in Cisco IOS Release 12.0(7)T. Only the remote routers are configured as stubs. A stub router sends a special peer information packet to all neighboring routers to report its status as a stub router. Any neighbor that receives a packet informing it of the stub status does not query the stub router for any routes. Therefore, a router that has a stub peer does not query that peer; instead, hub routers connected to the stub router answer the query on behalf of the stub router. The stub routing feature does not prevent routes from being advertised to the remote router. The EIGRP stub routing feature also simplifies the configuration and maintenance of hub-andspoke networks, improves network stability, and reduces resource utilization. When stub routing is enabled in dual-homed remote configurations, you do not have to configure filtering on remote routers to prevent them from appearing as transit paths to the hub routers.
Caution EIGRP stub routing should be used on stub routers only. A stub router is defined as a router that is connected to the network core or hub layer and through which core transit traffic should not flow. A stub router should only have hub routers for EIGRP neighbors; ignoring this restriction may cause undesirable behavior.
2-163
EIGRP Stub Configuration Planning

Examine the topology and existing EIGRP configuration Define requirements Stub routers Redistribution Summarization Create an implementation plan Configure and verify the configuration
RO UTE v 1.02-11
When you configure EIGRP stub behavior on stub routers, you should examine the existing topology and configuration and follow the design. The design is based on the topology and requirements. Stub routers, together with the redistribution and summarization, limit the query range in the topology. The next step is to create the implementation plan, then configure the EIGRP stub functionality on all required routers in the EIGRP domain. When you configure EIGRP stub routers, you optimize query and reply processing and you can verify that the configuration and design are both correct.
2-164
EIGRP Stub Options

Stub options (default is with connected and summary) receive-only: prevents the stub from sending any type of route connected: permits the stub to send connected routes (may still need to redistribute) static: permits the stub to send static routes (must still redistribute) summary: permits the stub to send summary routes redistribute: permits the stub to send redistributed routes
RO UTE v 1.02-12
A router configured as a stub shares information about connected and summary routes with all neighboring routers by default. The receive-only option restricts the router from sharing any of its routes with any other router within an EIGRP autonomous system (AS). This option does not permit any other option to be specified, because it prevents any type of route from being sent. The other options (connected, static, and summary) cannot be used with the receive-only option. Use this option if there is a single interface on the router. The connected option permits the EIGRP stub routing feature to send connected routes. If a network command does not include the connected routes, it might be necessary to redistribute the connected routes with the redistribute connected command under the EIGRP process. This option is enabled by default and is the most widely practical stub option. The static option permits the EIGRP stub routing feature to send static routes. You still need to redistribute static routes with the redistribute static command. The summary option permits the EIGRP stub routing feature to send summary routes. You can either create summary routes manually, or create them automatically by enabling autosummary at a major network border router. The summary option is enabled by default. The redistribute option permits the EIGRP stub routing feature to send redistributed routes. You still need to redistribute routes with the redistribute command.
2-165
Configuring eigrp stub connected
Router R2 will advertise to router R1 10.1.2.0/24 Router R2 will not advertise to router R1 10.1.2.0/23 10.1.3.0/24 10.1.4.0/24

RO UTE v 1.02-13
You can use the eigrp stub router configuration mode command to configure EIGRP stub functionality on the routers. You can modify the eigrp stub command with several options to optimize the exchange of routes based on the topology and requirements.
Note The eigrp stub command options can be used in any combination except for the receiveonly keyword, which prevents that router in advertising networks.
The figure in the slide shows the eigrp stub connected command on Router R2. Because the connected keyword is used, router R2 advertises the connected networks to its neighbors. Router R2, in the example in the slide, advertises the 10.1.2.0/24 route only. Network 10.1.2.0/24 is connected and, at the same time, is covered by the network statement under EIGRP AS 110 routing process. Although 10.1.3.0/24 is also a connected network, it is not advertised to router R1 because it is not advertised in a network command, and connected routes are not redistributed. The same applies to the static route for network 10.1.4.0/24. This route is not included in the EIGRP routing updates, because the EIGRP stub functionality for static routes is not specified under the EIGRP routing process. The eigrp stub connected command is only used as an example. For more details about eigrp stub command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
2-166
Configuring eigrp stub summary

RO UTE v 1.02-14
The figure in the slide shows that the eigrp stub summary command is used on router R2. Because the summary keyword is used, router R2 will advertise summary routes only to its neighbors. Router R2 will only advertise 10.1.2.0/23, the summary route that is configured on the router R2. No other routes are advertised, because the eigrp stub summary command is the only eigrp stub command used under the EIGRP AS 110 routing process in the example in the slide.
Note Summary routes can be created manually with the summary-address command or automatically at a major network border router with the auto-summary command enabled, which is enabled by default.
2-167
Configuring eigrp stub static

RO UTE v 1.02-15
The figure in the slide shows that the eigrp stub static command is used on router R2. Because of the static keyword, router R2 will advertise static routes only to its neighbors. Router R2 will only advertise 10.1.4.0/24, the static route that is configured on the router R2. It will not advertise any other routes, because the eigrp stub static command is the only eigrp stub command used under the EIGRP AS 110 routing process in the example in the slide.
Note Without the configuration of the eigrp stub static option, EIGRP will not send any static routes. This includes internal static routes that normally would be automatically redistributed. It will still be necessary to redistribute static routes with the redistribute static command.
2-168
Configuring eigrp stub receive-only
Router R2 will not advertise anything to router R1 Router R1 needs to have a static route to the networks behind router R2 to reach them

The figure in the slide shows that the eigrp stub receive-only command is used on router R2. Because the receive-only keyword is used, router R2 will not advertise anything to its neighbors. Router R2, in the example in the slide, requires that static routes be configured in order to reach the networks behind router R2.
Note The receive-only keyword restricts the router from sharing any of its routes with any other router in the same EIGRP autonomous system and cannot be combined with any other option within the eigrp stub command.
2-169
Configuring eigrp stub redistributed
Router R2 will advertise routes from RIP to router R1
RO UTE v 1.02-17
From the figure in the slide, it is apparent that router R2 is running the EIGRP AS 110 and RIP routing processes. At the same time, it is configured with the eigrp stub redistributed command within the EIGRP AS 110 routing process. Because the redistributed keyword is used, router R2 will advertise all RIP routes that are redistributed from the RIP routing protocol into the EIGRP AS 110 process. The sample configuration shows that the redistribute command is used under the EIGRP AS 110 process. This is required in order to include redistributed networks within the EIGRP advertisements.
2-170
Summary
Summary
Factors that affect network scalability include the amount of information exchanged between peers, the number of routers, the depth of the topology, and the number of alternate paths through the network. When a route is lost and no feasible successor is available, queries are sent to all neighboring routers on all interfaces. Once a route goes active and the query sequence is 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 of the outstanding queries within 3 minutes (the default time), the route goes into the SIA state. The stub routing feature improves network stability, reduces resource utilization, and simplifies stub router configuration.
RO UTE v 1.02-18
2-171
2-172
Lesson 9
Lab 2-4 Debrief

Overview
In Lab 2-4, students implement and troubleshoot EIGRP operations. They also solve EIGRP adjacency and limited connectivity issues.
Objectives
Upon completing this lesson, you will be able to implement and troubleshoot EIGRP operations to solve EIGRP adjacency and limited connectivity issues. This ability includes being able to meet these objectives: Complete the lab overview and verification Presents instructions to troubleshoot EIGRP implementation

This topic describes the lab topology and key checkpoints used to create a solution and start with the verification.
Lab Topology
ROUTE v1. 02-2
The figure in the slide presents the physical lab topology used for the Lab 2-4: Implement and Troubleshoot EIGRP Operations. The topology uses four pod routers and two backbone routers. All routers are participating in the EIGRP routing protocol. The configuration is broken in order to prepare the lab for students, who will go through troubleshooting steps. Based on the topology, students will identify required parameters to implement and troubleshoot EIGRP operations.
2-174
Lab Overview
Trouble Ticket AEIGRP Adjacency Issues There is no connectivity to the additional IP subnet being deployed on a LAN segment between routers R2 and R4. There are issue with the EIGRP adjacency to router BBR1. A configuration was applied that should have improved the metric calculation on R4, but instead resulted in no connectivity from that router. Summarization was configured, but is not working as expected. Trouble Ticket BLimited Connectivity A new spoke location, router R3, was deployed with no connectivity to the LAN subnets attached to routers R2 and R4.
ROUTE v1. 02-3
The lab consists of two trouble tickets: Trouble Ticket AEIGRP Adjacency Issues: There is no connectivity to an additional IP subnet being deployed on a LAN segment between routers R2 and R4. The next problem is an issue with EIGRP adjacency to router BBR1. A configuration that should have improved the metric calculation on router R4 instead caused there to be no connectivity from that router. Finally, summarization is configured, but is not working as expected. Trouble Ticket BLimited Connectivity: A newly deployed spoke location, router R3, has no connectivity to the LAN subnets attached to routers R2 and R4.
2-175
Instructions
This subtopic presents instructions to troubleshoot EIGRP implementation.
Instructions
Create the troubleshooting plan. Verify that you can see no more errors for the entries generated on routers R2 and R4. Verify that EIGRP adjacency on the LAN segment between routers R2 and R4 has been formed. Verify that the secondary IP address from the LAN segment is also present on router R1, and that you can ping the IP addresses from that subnet Verify that EIGRP adjacency has been formed between routers R1 and BBR1. Verify that routers in your pod have received subnets 192.168.x.0/24, announced by router BBR1.
ROUTE v1. 02-4
Instructions (Cont.)
Verify that routers have specific information about every subnet in your network and that you have connectivity to those subnets. Verify that router R3 receives IP routing information for the IP subnets located on the LAN segment between routers R2 and R4. Verify that you can ping the IP addresses from the IP subnets located on the LAN segment between routers R2 and R4.
ROUTE v1. 02-5
2-176
A common approach to verifying the implementation process for a routing protocol is to follow these instructions: Create the troubleshooting plan. Verify that you can see no more errors for the entries generated on routers R2 and R4. Verify that EIGRP adjacency on the LAN segment between routers R2 and R4 has been formed. Verify that the secondary IP address from the LAN segment is present on router R1 and that you can ping the IP addresses from that subnet. Verify that EIGRP adjacency has been formed between routers R1 and BBR1. Verify that the routers in your pod have received the subnets 192.168.x.0/24 announced by router BBR1. Verify that routers have specific information about every subnet in your network and that you have connectivity to those networks. Verify that router R3 receives IP routing information for the IP subnets located on the LAN segment between routers R2 and R4. Verify that you can ping the IP addresses from the IP subnets located on the LAN segment between routers R2 and R4.
2-177
Summary
Summary
Connectivity issues, wrong authentication, and metric configuration result in EIGRP adjacency issues. Incorrectly configuring a newly deployed site can lead to limited connectivity.
ROUTE v1. 02-6
2-178
Module Summary
Module Summary
EIGRP starts by building a table of adjacent neighbors. Route exchanges with these neighbors result in an EIGRP topology table. The DUAL process calculates the best EIGRP routes, which are moved into the IP routing table. Steps to configure basic EIGRP are: define EIGRP as a routing protocol, define attached networks participating in EIGRP, and, if desired, define interface bandwidth. The configuration of a passive interface, IP default-network, and summarization are all advanced steps to improve network scalability and decrease the number of EIGRP updates exchanged between EIGRP neighbors.
ROUTE v1. 02-1
Module Summary (Cont.)

Any Transport over MPLS (AToM) supports EIGRP, allowing service provider PE-routers to be aware of EIGRP and P-routers to be hidden from the customer network. EIGRP supports MD5 authentication, which checks and authenticates the source of each routing update packet received. Features such as stub routing and active process enhancement help improve network stability and performance.
ROUTE v1. 02-2
Configuring Enhanced Interior Gateway Routing Protocol (EIGRP) for your routing environment enables you to achieve benefits such as rapid convergence, lower bandwidth utilization, and multiple routed protocol support. Using EIGRP ensures that as a network grows larger, it will still operate efficiently and adjust to changes rapidly.
2-180
Module Self-Check
Use the questions here to review what you learned in this module. The correct answers and solutions are found in the Module Self-Check Answer Key. Q1) Which three features are benefits of EIGRP? (Choose three.) (Source: Planning Routing Implementations with EIGRP) A) B) C) D) Q2) fast convergence support for VLSM and discontiguous subnets same metric algorithm as OSPF manual route summarization at any point in the network
What is listed in the EIGRP topology table? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) directly connected routers that have formed an EIGRP adjacency best routes to a destination network all routes learned from each EIGRP neighbor all EIGRP neighbors in the EIGRP domain
Q3)
What is listed in the EIGRP neighbor table? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) directly connected routers that have formed EIGRP adjacencies best routes to a destination network all routes learned from each EIGRP neighbor all EIGRP neighbors in the EIGRP domain
Q4)
What is listed in the IP routing table? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) directly connected routers that have formed EIGRP adjacencies best routes to a destination network all routes learned from each EIGRP neighbor all EIGRP neighbors in the EIGRP domain
Q5)
Which two statements are true of the EIGRP metric calculation? (Choose two.) (Source: Planning Routing Implementations with EIGRP) A) B) C) D) The following are the default K values: K1 = 1, K2 = 1, K3 = 0, K4=0, K5 = 0. To convert an IGRP metric to an EIGRP metric, multiply the IGRP metric by 256. To convert an EIGRP metric to an IGRP metric, multiply the EIGRP metric by 256. The following are the default K values: K1 = 1, K2 = 0, K3 = 1, K4 = 0, K5=0.
Q6)
Which three characteristics are key features of EIGRP? (Choose three.) (Source: Planning Routing Implementations with EIGRP) A) B) C) D) fast convergence partial updates support for multiple Layer 3 protocols backward compatibility with RIP
2-181
Q7)
Which of these are key EIGRP technologies? (Choose three.) (Source: Planning Routing Implementations with EIGRP) A) B) C) D) E) RTP protocol-dependent modules protocol-independent modules DUAL RMTP
Q8)
Which two characteristics are features of EIGRP? (Choose two.) (Source: Planning Routing Implementations with EIGRP) A) B) C) D) support for load balancing across unequal-cost paths manual summarization at any point on the internetwork provisioning of highly structured area design requirements automatic redistribution of static routes
Q9)
Which type of database is a list of all EIGRP adjacencies? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) EIGRP topology table EIGRP neighbor table IP routing table IP EIGRP adjacency table
Q10)
Which type of database contains a list of the best EIGRP routes to reach a destination? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) EIGRP topology table EIGRP neighbor table IP routing table IP EIGRP adjacency table
Q11)
Which type of database contains a list of all possible EIGRP routes to reach a destination? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) EIGRP topology table EIGRP neighbor table IP routing table IP EIGRP adjacency table
Q12)
Which five criteria may be considered by EIGRP when calculating the metric? (Choose five.) (Source: Planning Routing Implementations with EIGRP) A) B) C) D) E) F) G) MTU bandwidth cost delay load hop count reliability
2-182
Q13)
Which packet type establishes neighbor relationships? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) E) ACK hello query reply update
Q14)
Which packet type is responsible for sending routing advertisements? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) E) ACK hello query reply update
Q15)
What should a network engineer do before configuring EIGRP in the network? (Choose three.) (Source: Planning Routing Implementations with EIGRP) A) B) C) D) E) assess the requirements assess the existing configuration and topology create the documentation verify the EIGRP neighbors create an implementation plan
Q16)
Which parameters are included in an EIGRP implementation plan? (Choose two.) (Source: Planning Routing Implementations with EIGRP) A) B) C) D) E) IP addressing EIGRP AS number the difference in the metric between EIGRP and IGRP feasible distance of feasible successor feasible distance of successor
Q17)
Which packet type is used to ask neighbors about routing information? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) E) ACK hello query reply update
Q18)
DUAL selects as the successor for a specific destination network the next-hop router with which of these? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) highest FD lowest FD highest AD lowest AD
2-183
Q19)
What is the formula for selecting a feasible successor? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) The AD of the current successor route is less than the FD of the feasible successor route. The FD of the current successor route is less than the AD of the feasible successor route. The FD of the feasible successor route is less than the AD of the current successor route. The AD of the feasible successor route is less than the FD of the current successor route.
Q20)
What does EIGRP do when a successor fails and there are no feasible successors, but there are alternate paths available? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) It immediately uses the alternate pathway with the lowest FD and sends queries and updates to ensure that this pathway is loop-free. It automatically uses the alternate pathway with the lowest FD. It sends queries to see if the alternate paths are still viable. When a loop-free path is found, the path is installed in the routing table. It removes the network from the routing table and waits for the periodic update from EIGRP neighbors to see if an alternate route exists.
Q21)
Which two conditions signify the active state for EIGRP? (Choose two.) (Source: Planning Routing Implementations with EIGRP) A) B) C) D) The route can be used and is stable. The route cannot be used. EIGRP queries are outstanding and the router is waiting for EIGRP replies. This is the best route with the lowest FD.
2-184
Q22)
Test your understanding of EIGRP by matching terms with statements. Write the number of the statement in front of the term that the statement describes. (Source: Planning Routing Implementations with EIGRP) Term _____ 1. _____ 2. _____ 3. _____ 4. _____ 5. _____ 6. _____ 7. _____ 8. Statement 1. 2. 3. 4. 5. 6. 7. 8. a network protocol that EIGRP supports a database that contains successor and feasible successor information a database that includes administrative distance a neighbor router that has the best path to a destination a neighbor router that has the best alternate loop-free path to a destination an algorithm used by EIGRP to ensure fast convergence a multicast packet used to discover neighbors a packet sent by EIGRP routers when a new neighbor is discovered or a change occurs successor feasible successor hello topology table IP update routing table DUAL
Q23)
What is the purpose of the network command for EIGRP? (Source: Planning Routing Implementations with EIGRP) A) B) C) D) to determine which router interfaces participate in EIGRP and which networks the router advertises to specify the AS number to which the router belongs to define the EIGRP neighbors to tell EIGRP which networks to advertise, those directly connected and those learned through EIGRP
Q24)
Which command creates a default route for EIGRP? (Source: Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture) A) B) C) D) ip default-network network-number ip route 0.0.0.0 0.0.0.0 outbound-interface ip route 0.0.0.0 255.0.0.0 outbound-interface ip route 0.0.0.0 255.255.255.255 outbound-interface
Q25)
Which command displays an indication if a network is SIA? (Source: Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture) A) B) C) show ip route show ip protocol show ip eigrp topology
2-185
Q26)
What is the correct network command to allow updates to propagate only out of interfaces that are part of subnet 10.1.0.0/16? (Source: Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture) A) B) C) D) network 10.1.0.0 mask 255.255.0.0 network 10.1.0.0 mask 0.0.255.255 network 10.1.0.0 255.255.0.0 network 10.1.0.0 0.0.255.255
Q27)
Which three of these are true of configuring the ip default-network command for EIGRP? (Choose three.) (Source: Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture) A) B) C) D) The network must be reachable by the router using this command. The command will set the gateway of last resort to 0.0.0.0 on the router issuing this command. The network must be advertised to other neighbors as an EIGRP route. The network will be flagged by other EIGRP routers as a candidate default route.
Q28)
What does the passive state in the EIGRP topology table signify? (Source: Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture) A) B) C) D) There are outstanding queries for this network. The network is unreachable. The network is up and operational, and this state signifies normal conditions. A feasible successor has been selected.
Q29)
Which command indicates the number of EIGRP peer routers on an interface? (Source: Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture) A) B) C) D) show ip eigrp interfaces show ip eigrp neighbors show ip route show ip eigrp topology
Q30)
Which command is used to disable automatic EIGRP network-boundary summarization, and where is it applied? (Source: Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture) A) B) C) D) no boundary-summarization at the interface level no auto-summary under the routing process no auto-summary at the interface level no boundary-summarization under the routing process
Q31)
Which command is used to configure manual summarization of all the subnets in network 10.1.32.0/21 for EIGRP in AS 101? (Source: Implementing and Verifying Basic EIGRP for the Enterprise LAN Architecture) A) B) C) D) ip summary-address eigrp 101 10.1.32.0 255.255.248.0 ip eigrp 101 summary-address 10.1.32.0 255.255.240.0 ip summary-address eigrp 101 10.1.32.0 255.255.240.0 ip eigrp 101 summary-address 10.1.32.0 255.255.248.0
2-186
Q32)
By default, how many equal-cost paths to the same destination network can EIGRP place in the routing table? (Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) C) D) one two four six
Q33)
Between headquarters and remote site A, there are two dedicated serial PPP connections, one at 64 kb/s, and the other at 128 kb/s. What is the appropriate variance to allow for unequal-cost load balancing across these links? (Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) C) D) 1 2 3 4
Q34)
What is the default bandwidth percentage that EIGRP uses on WAN links? (Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) C) D) 25 percent 50 percent 75 percent 100 percent
Q35)
Which two statements best describes AToM? (Choose two.) (Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) C) D) AToM stands for Any Transport over MPLS AToM unifies Layer 2 and Layer 3 over a common MPLS infrastructure. AToM must be enabled for EIGRP in an MPLS environment. Authentication is required in an AToM design.
Q36)
Which router does not participate in customer routing? (Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) C) D) C router CE router PE router P router
Q37)
What are three requirements for MPLS VPN technology? (Choose three.) (Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) C) D) CE routers should not be aware of MPLS VPN. The service providers P routers must be hidden from the customer. C routers must be directly connected to PE routers. Each PE router must appear as another router in the customers network.
Q38)
You do not need to change the basic configuration when you deploy EIGRP over a physical interface using dynamic mapping, thus relying on Inverse ARP. ((Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) true false
2-187
Q39)
Which two topologies use EIGRP over Frame Relay multipoint subinterfaces? (Choose two.) (Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) C) D) point-to-point partial-mesh full-mesh hub-and-spoke
Q40)
What are two main reasons for the relatively fast EIGRP neighbor loss detection on point-to-point subinterfaces? (Choose two.) (Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) C) D) There is a small default EIGRP hello and hold timer, which is identical to the value used on point-to-point links. On Frame Relay networks, the subinterface is declared down if the DLCI attached to the interface is lost. Neighbors send immediate EIGRP update packets to inform each other of neighbor loss. The EIGRP process is checking for neighbors every 5 seconds
Q41)
Which topologies use EIGRP over Frame Relay multipoint subinterfaces? (Choose two.) (Source: Configuring and Verifying EIGRP for the Enterprise WAN Architecture) A) B) C) D) point-to-point partial-mesh full-mesh hub-and-spoke
Q42)
Which authentication does EIGRP support? (Source: Implementing and Verifying EIGRP Authentication) A) B) C) D) MD5 MD5 and simple password simple password none
Q43)
When EIGRP authentication is configured between two routers, each router has its own unique password. (Source: Implementing and Verifying EIGRP Authentication) A) B) true false
Q44)
Which three of these are used to generate the message digest when EIGRP MD5 authentication is configured? (Choose three.) (Source: Implementing and Verifying EIGRP Authentication) A) B) C) D) E) packet sequence number key ID key router ID
2-188
Q45)
What does the accept-lifetime 04:00:00 Jan 1 2006 infinite command do? (Source: Implementing and Verifying EIGRP Authentication) A) B) C) D) specifies that a key is acceptable for use on received packets from the first of January 2006 onward specifies that a key is acceptable for use on sent packets from the first of January 2006 onward specifies that a key is acceptable for use on received packets until the first of January 2006 specifies that a key is acceptable for use on sent packets until the first of January 2006
Q46)
Which command specifies that EIGRP MD5 authentication in AS 100 be used? (Source: Implementing and Verifying EIGRP Authentication) A) B) C) D) E) ip authentication mode eigrp 100 md5 ip eigrp 100 authentication mode md5 ip authentication-key eigrp 100 ip message-digest-key eigrp 100 ip eigrp 100 authentication message-digest
Q47)
Which command is used to troubleshoot EIGRP authentication? (Source: Implementing and Verifying EIGRP Authentication) A) B) C) D) E) debug ip eigrp adj debug ip eigrp packets debug eigrp packets debug ip eigrp adjacency events debug eigrp adj
Q48)
When a router gets a query from a neighboring router that is not a successor for the network listed in the query, and that network is in a passive state on this router, what does the router do? (Source: Advanced EIGRP Features in an Enterprise Network) A) B) The router replies that the destination is unreachable. The router attempts to find a new successor. If successful, it replies with new information. If unsuccessful, it marks the destination as unreachable and queries all neighboring routers except the previous successor. The router replies with the current successor information. The router marks the destination as unreachable and queries all neighboring routers except the previous successor.
C) D) Q49)
Which three of these factors affect network scalability? (Choose three.) (Source: Advanced EIGRP Features in an Enterprise Network) A) B) C) D) number of alternate paths through the network amount of information exchanged between neighbors the amount of different AS numbers used in the network depth of the topology
2-189
Q50)
Which three statements about implementing EIGRP stub routers are true? (Choose three.) (Source: Advanced EIGRP Features in an Enterprise Network) A) B) C) D) Stub routing is commonly used on networks with hub-and-spoke topologies. The EIGRP stub feature should be configured only on remote spoke routers. EIGRP stub routers can and should be used as transit points to other parts of the network and other autonomous systems. Queries are not propagated to EIGRP stub routers; EIGRP updates are sent to stub routers, or a default route is passed.
Q51)
How long does a querying router wait to reset a neighbor that fails to reply to a query? (Source: Advanced EIGRP Features in an Enterprise Network) A) B) C) D) 15 seconds 40 seconds 1 minute 3 minutes
Q52)
Which command configures an EIGRP stub router to not send any routing updates? (Source: Advanced EIGRP Features in an Enterprise Network) A) B) C) D) eigrp stub eigrp stub receive-only eigrp stub no-send eigrp stub none
2-190

Q1) Q2) Q3) Q4) Q5) Q6) Q7) Q8) Q9) Q10) Q11) Q12) Q13) Q14) Q15) Q16) Q17) Q18) Q19) Q20) Q21) Q22) Q23) Q24) Q25) Q26) Q27) Q28) Q29) Q30) Q31) Q32) Q33) Q34) Q35) A, B, D C A B B, D A, B, C A, B, D A, B B C A A, B, D, E, G B E A, B, E A, B C B D C B, C A=4, B=5, C=7, D=2, E=1, F=8, G=3, H=6 A A C D A, C, D C A B A C B B A,B
2-191
Q36) Q37) Q38) Q39) Q40) Q41) Q42) Q43) Q44) Q45) Q46) Q47) Q48) Q49) Q50) Q51) Q52)
D A, B, D A B, C A, B B, C A B A, C, D A A C C A, B, D A, B, D D B
2-192
ROUTE

Volume 2
Version 1.0
Student Guide
Student Guide
Table of Contents
Volume 2 Implementing a Scalable Multiarea Network OSPF-Based Solution
3-1
3-1 3-1
Planning Routing Implementations with OSPF as the Scalable Routing Protocol

Overview Objectives Link-State Routing Protocols OSPF Area Structure OSPF Adjacency Database Calculating the OSPF Metric Link-State Data Structures Maintaining Link-State Sequence Numbers Example: LSA Sequence Numbers and Maximum Age Planning for Implementing OSPF Summary
3-3
3-3 3-3 3-4 3-6 3-9 3-10 3-12 3-15 3-17 3-18 3-23
How OSPF Packet Processes Work

Overview Objectives OSPF Packet Types Establishing OSPF Neighbor Adjacencies Exchanging and Synchronizing LSDBs Maintaining Network Routes Verifying Packet Flow Example: debug ip ospf packet Summary
3-25
3-25 3-25 3-26 3-29 3-31 3-36 3-38 3-38 3-40
Improving Routing Performance in a Complex Enterprise Network

Overview Objectives Introducing OSPF Network Types Adjacency Behavior in Point-to-Point Links Adjacency Behavior in a Broadcast Network Adjacency Behavior in a Metro Ethernet and EoMPLS Network Adjacency Behavior in MPLS networks Selecting a DR and BDR OSPF over Different Frame Relay Implementations OSPF over Frame Relay NBMA Example: NBMA Configuration Example Using Sub-Interfaces in OSPF over Frame Relay Example: Point-to-Point Subinterface Example: Multipoint Subinterface Implementing OSPF over a Point-to-Point Frame Relay Network Example: Point-to-Point Configuration Implementing OSPF over a Point-to-Multipoint Frame Relay Network Example: Point-to-Multipoint Configuration Example: OSPF over NBMA Topology Summary Summary
3-41
3-41 3-41 3-43 3-44 3-45 3-47 3-49 3-51 3-54 3-59 3-62 3-64 3-66 3-68 3-69 3-70 3-72 3-74 3-77 3-78
Configuring and Verifying OSPF Routing

Overview Objectives Initializing Single-Area and Multiarea OSPF Activating OSPF within a Router in Single-Area and Multiarea Defining the Router ID Verify OSPF Operations Identifying LSA Types within the LSDB Type 1 Type 2 Types 3 and 4 Type 5 Type 6 Type 7 Type 8 Types 9, 10, and 11 LSA Type 1 Link Types Example: LSA Type 4ASBR Summary LSA Example: Types of Link State Advertisements (LSAs) Limiting Adjacencies in OSPF with the Passive-Interface Command Design Limitations of OSPF OSPF Virtual Links and Solutions to Non-Contiguous Area Problems Changing the Cost Metric Summary
3-79
3-79 3-79 3-80 3-82 3-85 3-90 3-97 3-97 3-97 3-97 3-98 3-98 3-98 3-98 3-98 3-99 3-102 3-105 3-126 3-128 3-130 3-136 3-138
Lab 3-1 Debrief

Overview Objectives Lab Overview and Verification Sample Solution and Alternatives Summary
3-141
3-141 3-141 3-142 3-148 3-151
Lab 3-2 Debrief

3-153
3-153 3-153 3-154 3-158 3-161
Configuring and Verifying OSPF Route Summarization

Overview Objectives OSPF Route Summarization Implementing OSPF Route Summarization Benefits of a Default Route in OSPF Using a Default Route in OSPF Summary
3-163
3-163 3-163 3-164 3-166 3-173 3-174 3-176
Lab 3-3 Debrief

3-177
3-177 3-177 3-178 3-182 3-185
Configuring and Verifying OSPF Special Area Types

Overview Objectives OSPF Area Types Defining and Implementing a Stub Area Defining and Implementing a Totally Stubby Area Example: Totally Stubby Configuration
ii Implementing Cisco IP Routing (ROUTE) v1.0
3-187
3-187 3-187 3-188 3-192 3-195 3-197
Interpreting Routing Tables for OSPF Area Types Defining and Implementing a Not-So-Stubby-Area and Totally NSSA in OSPF Verifying All OSPF Area Types Summary
3-198 3-202 3-208 3-209
Lab 3-4 Debrief

3-211
3-211 3-211 3-212 3-217 3-220
Configuring and Verifying OSPF Authentication

Overview Objectives Types of OSPF Authentication Implementing Simple Password Authentication for OSPF Configuring MD5 Authentication for OSPF Troubleshooting Authentication for OSPF Summary
3-221
3-221 3-221 3-222 3-223 3-228 3-232 3-239
Lab 3-5 Debrief

Overview Objectives Lab Overview and Verification Sample Solution and Alternatives Summary Module Summary Module Self-Check Module Self-Check Answer Key
3-241
3-241 3-241 3-242 3-246 3-249 3-251 3-253 3-269
Implement an IPv4-Based Redistribution Solution

4-1
4-1 4-1
Assessing Network Routing Performance and Security Issues

Overview Objectives Common Network Performance Issues How Distribute Lists Work Using Distribution Lists to Control Routing Updates How Prefix Lists Work Using a Prefix List to Control Routing Updates How Route Maps Work Using Route-Maps to Control Routing Updates Using Route-Maps to Filter Routes Suppressing Routing Updates using a Passive Interface Summary
4-3
4-3 4-3 4-5 4-11 4-13 4-17 4-21 4-25 4-33 4-36 4-37 4-40
Operating a Network Using Multiple IP Routing Protocols

Overview Objectives Describe a Complex Routing Network Defining Route Redistribution Default Metrics for Redistributed Routes Determining Where to Redistribute Caveats of Redistribution Summary
4-41
4-41 4-41 4-42 4-45 4-49 4-53 4-57 4-62
iii
Configuring and Verifying Route Redistribution

Overview Objectives Examples of Redistribution The Administrative Distance Attribute Route Redistribution using Administrative Distance Impact of using Administrative Distance for Route Manipulation Redistribution Using Route Maps Route Redistribution using Route Maps Summary
4-63
4-63 4-63 4-64 4-76 4-78 4-82 4-87 4-89 4-91
Lab 4-1 Debrief

Overview Objectives Lab Overview and Verification Sample Solution and Alternatives Summary Module Summary Module Self-Check Module Self-Check Answer Key
4-93
4-93 4-93 4-94 4-98 4-101 4-103 4-105 4-108
iv
Module 3
Implementing a Scalable Multiarea Network OSPFBased Solution

Overview
This module examines Open Shortest Path First (OSPF), which is one of the most commonly used interior gateway protocols in IP networking. OSPF is an open-standard protocol based primarily on RFC 2328, with some enhancements for IP version 6 (IPv6) based on RFC 2740. OSPF is a complex protocol made up of several protocol handshakes, database advertisements, and packet types. Configuration and verification of OSPF in a Cisco Systems router is a primary learning objective of this module. The lessons move from simple to more advanced configuration topics. Each of the important OSPF commands is explained and described in an example. All of the important OSPF show commands are defined.
Module Objectives
Upon completing this module, you will be able to build a scalable multiarea network with OSPF. This ability includes being able to meet these objectives: Identify, analyze, and match OSPF multiarea routing functions and benefits for routing efficiency in a complex enterprise network Demonstrate how OSPF improves packet processes in a multiarea enterprise network Configure OSPF to improve routing performance in a complex enterprise network Discuss lab results for configuring and verifying OSPF to improve routing performance Given a network design, configure OSPF multiarea routing to improve network operations and reach performance expectations Discuss lab results for implementing and verifying OSPF multiarea routing Configure OSPF route summarization for interarea and external routes
Discuss lab results for configuring and verifying OSPF route summarization for interarea and external routes Configure and verify the OSPF area parameters, including stub areas, not-so-stubby areas (NSSAs), and totally stubby areas Discuss lab results for configuring and verifying OSPF special area types Implement authentication in an OSPF network Discuss lab results for configuring and verifying OSPF authentication
3-2
Lesson 1
Planning Routing Implementations with OSPF as the Scalable Routing Protocol

Overview
Open Shortest Path First (OSPF) is one of the most commonly used IP routing protocols in networking. It is an open standard that is used by both enterprise and service provider networks. This lesson introduces each of the major characteristics of the OSPF routing protocol, including a description of link-state routing protocols, the OSPF hierarchical structure, link-state adjacencies, and Shortest Path First (SPF) calculations. Since the creation of the implementation plan the first step in configuring the OSPF routing protocol, it is also described.
Objectives
Upon completing this lesson, you will be able to explain link state protocols, components, the metrics of OSPF, the way in which OSPF operates, and the implementation plan creation process. This ability includes being able to meet these objectives: Determine link-state routing protocols Determine OSPF area structure Determine OSPF adjacency database Calculate the OSPF metric Determine link-State data structures Maintain link-state sequence numbers Plan for OSPF implementation
Link-State Routing Protocols

This topic describes the features of link-state routing protocols.
Link-State Protocols
2009 Cis co S yst em s, Inc. A ll rights reserved.
ROUTE v1.03-2
The need to overcome the limitations of distance vector routing protocols led to the development of link-state routing protocols. By using link-state advertisements (LSAs), each router builds its own view of the network, and also maintains a list of neighbors, a list of all routers in the area, and a list of the best paths to each destination. OSPF is classified as a linkstate routing protocol, because of the manner in which it distributes routing information and calculates routes. Link-state routing protocols generate routing updates only when a change occurs in the network topology. When a link changes state, the device that detected the change creates a link-state advertisement (LSA) concerning that link. The LSA is propagated to all neighboring devices using a special multicast address. Each routing device creates a copy of the LSA, updates its link-state database (LSDB), and forwards the LSA to all neighboring devices (within an area, as described later in this lesson). This flooding of the LSA ensures that all routing devices update their databases before updating routing tables to reflect the new topology. The LSDB is used to calculate the best paths through the network. Link-state routers find the best paths to a destination by applying Dijkstras algorithm, also known as SPF, against the LSDB to build the SPF tree. The best paths are then selected from the SPF tree and placed in the routing table.
Note The 224.0.0.5 multicast address is used by OSPF routers and the 224.0.0.6 multicast address is used by OSPF designated routers (RFC 1583, JXM1).
3-4
Link-State Protocol Data Structures

Link-state routers recognize more information about the network than their distance vector counterparts. Neighbor table: also known as the adjacency database Topology table: referred as the LSDB Routing table: also known as the forwarding database Each router has a full picture of the topology Link-state routers tend to make more accurate decisions
ROUTE v1.03-3
Link-state routing protocols collect routing information from all other routers in the network or from within a defined area of the network. When link-state routing protocols have collected this information from all routers, each router independently calculates its best path to all destinations in the network using Dijkstras algorithm. Incorrect information from any particular router is less likely to cause confusion, because each router maintains its own view of the network. For consistent routing decisions to be taken by all the routers in the network, each router must keep a record of the following information: Its immediate neighbor routers: If the router loses contact with a neighboring router, within a few seconds, it will invalidate all paths through that router and recalculate its paths through the network. Adjacency information about neighbors is stored in the neighbor table, also known as an adjacency database, in OSPF. All the other routers in the network, or in its area of the network, and their attached networks: The router recognizes other routers and networks through LSAs, which are flooded through the network. LSAs are stored in a topology table, also called an LSDB. The LSDB is identical for all OSPF routers in an area. The memory resources that are needed to maintain these tables represent one drawback to link-state protocols. The best path to each destination: Each router independently calculates the best paths to each destination in the network using Dijkstras algorithm. The best paths are then offered to the routing table or forwarding database. Packets arriving at the router are forwarded based on the information held in the routing table. Each router is able to independently select a loop-free and efficient pathway. This benefit overcomes the routing by rumors limitation of distance vector routing.
Implementing a Scalable Multiarea Network OSPF-Based Solution
3-5
OSPF Area Structure

This topic describes the two-tier hierarchy structure of OSPF, including the characteristics of transit areas and regular areas, as well as the terminology used.
OSPF Areas
Link-state routing requires a hierarchical network structure This two-level hierarchy consists of the following: Transit area (backbone or area 0) Normal areas (non-backbone areas)
ROUTE v1.03-4
In small networks, the web of router links is not complex, and paths to individual destinations are easily deduced. However, in large networks, the web is highly complex and the number of potential paths to each destination is large. Therefore, the Dijkstra calculations comparing all these possible routes can be very complex and can take a significant amount of time to complete. Link-state routing protocols usually reduce the size of the Dijkstra calculations by partitioning the network into areas. The number of routers in an area and the number of LSAs that flood within the area are small, which means that the link-state or topology database for an area is small. Consequently, the Dijkstra calculation is easier and takes less time. Routers inside an area maintain detailed information about the links and only general or summary information about routers and links in other areas. Link-state routing protocols use a two-layer area hierarchy: Backbone or transit area: The primary function of this OSPF area is to quickly and efficiently move IP packets. Backbone areas interconnect with other OSPF area types. The OSPF hierarchical area structure requires that all areas connect directly to the backbone area. You will notice that in the figure in the slide, links between area 1 routers and area 2 routers are not allowed. Generally, end users are not found within a backbone area. It is also known as OSPF area 0.
3-6
Normal or non-backbone area: The primary function of this OSPF area is to connect users and resources. Normal areas are usually set up according to functional or geographical groupings. By default, a normal area does not allow traffic from another area to use its links to reach other areas. All traffic from other areas must cross a transit area such as area 0. Normal areas can be of different types. The optimal number of routers per area varies based on factors such as network stability, but in the Designing Large-Scale Internetworks document, Cisco recommends that there generally be no more than 50 routers per area.
3-7
Area Terminology and Router Types

ABR: Area Border Router ASBR: Autonomous System Boundary Router R5, R6: Internal routers R1: Backbone router
ROUTE v1.03-5
All OSPF areas and routers running OSPF routing protocol compose the OSPF autonomous system. Routers that make up non-backbone (normal) areas are known as internal routers and they have all interfaces in one area only. Routers that make up area 0 are known as backbone routers (internal routers in backbone). OSPF hierarchical networking defines area 0 as the core. All other areas connect directly to backbone area 0. An Area Border Router (ABR) connects area 0 to the non-backbone areas. An OSPF ABR plays a very important role in network design and has interfaces in more than one area. An ABR has the following characteristics: It separates LSA flooding zones. It becomes the primary point for area address summarization. It functions regularly as the source for default routes. It maintains the LSDB for each area with which it is connected. The ideal design is to have each ABR connected to two areas only, the backbone and another area, with three areas being the upper limit. An Autonomous System Boundary Router (ASBR) connects any OSPF area to a different routing administration (such as Border Gateway Protocol [BGP] or Enhanced Interior Gateway Routing Protocol [EIGRP]). The ASBR is the point where external routes can be redistributed into OSPF.
3-8
OSPF Adjacency Database

This topic describes how routers running a link-state routing protocol establish neighbor adjacencies with their neighboring routers.
OSPF Adjacencies
Routing updates and topology information are passed only between adjacent routers.
Forming OSPF adjacencies on point-to-point WAN links
Forming OSPF adjacencies on LAN links is different than forming them on point-to-point links.
2009 Cis co S yst em s, Inc. A ll rights reserved. ROUTE v1.03-6
A router running a link-state routing protocol must first establish neighbor adjacencies with its neighboring routers. A router achieves this neighbor adjacency by exchanging hello packets with the neighboring routers. Once routers become adjacent, they begin exchanging the link-state information to synchronize the LSDB. Link-state information must be synchronized between routers and the process is described later in this module. Only by reliably flooding link-state information can you ensure that every router in the area or domain has the latest, most accurate view of the network. Only then can the router make reliable routing decisions that are consistent with the decisions of other routers in the network. The two OSPF routers on a point-to-point serial link, which are usually encapsulated in HighLevel Data Link Control (HDLC) or PPP, form a full adjacency with each other. OSPF routers on the LAN form adjacencies in a different way and the process is described later in this module.
3-9
Calculating the OSPF Metric

This topic describes the SPF algorithm and the calculations used by OSPF to find the best path to each destination network. The routing table is then populated with the best paths.
OSPF Calculation
Routers find the best paths to destinations by applying Dijkstras SPF algorithm to the LSDB. The best path is calculated based on the lowest total cost and sent to the routing table.
ROUTE v1.03-7
All routers form an adjacency, which is the prerequisite for the LSDB creation process. Once they have all formed adjacencies, they start exchanging LSAs. Router R1 has four neighboring routers: R2, R3, R4, and R5. From these routers, it receives the LSAs from all other routers in the network. From these LSAs, it can also deduce the links between all routers and draw the web of routers depicted in the figure in the slide. In this way an LSDB is created. Edsger Dijkstra designed a mathematical algorithm for calculating the best paths through complex networks. Link-state routing protocols use Dijkstras algorithm to calculate the best paths through a network. They assign a cost to each link in the network and place the specific node at the root of a tree, then sum the costs toward each given destination. In this way they calculate the branches of the tree to determine the best path to each destination. The best path is calculated with respect to the lowest total cost of links to a specific destination and is put in the forwarding database (routing table). For OSPF, the default behavior is that the interface cost is calculated based on its configured bandwidth. You can also manually define an OSPF cost for each interface, which overrides the default cost value. The figure illustrates an example of a Dijkstra calculation. Each Ethernet link in the figure is assigned an OSPF cost of 10. By summing the costs to each destination, the router can deduce the best path to each destination. The right side of the figure shows the result of Dijkstra calculation, in which the SPF tree is defining the best paths. From these best paths, shown with solid lines, routes to destination networks attached to each router are offered to the routing table; for each route, the next-hop address is the appropriate neighboring router (R2, R3, R4, or R5).
3-10
OSPF Metric
Also called cost Defined per interface, but may be altered Inversely proportional to the bandwidth of that interface COST = 100,000,000 / bandwidth [b/s]
Link Type
64-kb/s s erial link T1 (1.544-Mb/s serial link) E1 (2.048-Mb/s serial link) Ethernet Fast Ethernet ATM
Default Cost
1562 64 48 10 1 1
ROUTE v1.03-8
The cost (also called the metric) of an interface in OSPF is an indication of the overhead required to send packets across a certain interface. The cost of an interface is inversely proportional to the bandwidth of that interface. A higher bandwidth indicates a lower cost. There is more overhead (higher cost) and time delays involved in crossing a 56 kb/s serial line than crossing a 10 Mb/s Ethernet line. The formula used to calculate the cost is: Cost = 100,000,000 / bandwidth in b/s For example, it will cost 108/107 = 10 to cross a 10-Mb Ethernet line and will cost 108/1544000 = 64 to cross a T1 line. By default, the cost of an interface is calculated based on the bandwidth and can be changed by using the OSPF configuration command. If you change the link bandwidth, it will also indirectly change the cost. Only one cost can be assigned per interface and it is advertised as the link cost in the router link advertisements. Links have different default costs, as follows: 56-kb/s serial link: default cost is 1785 64-kb/s serial link: default cost is 1562 T1 (1.544-Mb/s serial link): default cost is 64 E1 (2.048-Mb/s serial link): default cost is 48 Ethernet: default cost is 10 Fast Ethernet: default cost is 1 FDDI: default cost is 1 ATM: default cost is 1
3-11
Link-State Data Structures

This topic describes how routers use link-state updates (LSUs) to verify that links are still active.
Building the LSDB

The Hello protocol is used to define neighbors Adjacency is established Adjacent routers exchange LSAs Each router builds an LSDB using LSAs
ROUTE v1.03-9
Routers that share a common segment become neighbors on that segment. Neighbors are elected via the Hello protocol. Hello packets are sent periodically out of each interface and routers become neighbors as soon as they see themselves listed in the neighbor's Hello packet. This way, a two-way communication is guaranteed. Two routers will not become neighbors unless they agree on the following: Area ID: Two routers having a common segment; their interfaces have to belong to the same area on that segment. Authentication: OSPF allows for the configuration of a password for a specific area. Routers that want to become neighbors have to exchange the same password on a particular segment. Hello and dead intervals: OSPF exchanges hello packets on each segment. This is a form of keepalive used by routers in order to acknowledge their existence on a segment and in order to elect a designated router (DR) on multiaccess segments. OSPF requires these intervals to be exactly the same between two neighbors. Stub area flag: Two routers have to agree on the stub area flag in the hello packets in order to become neighbors. Stub areas will be discussed in a later section. Keep in mind for now that defining stub areas will affect the neighbor election process. Adjacency is the next step after the process of becoming neighbors. Adjacent routers are routers that go beyond the simple hello exchange and proceed into the database exchange process. Link-state update packets are exchanged and acknowledgement is required. Selection and processing of link-state updates is based on the sequence numbers. At the end, the adjacent routers will have the exact same link-state database.
The following is a brief summary of the states an interface passes through before becoming adjacent to another router: Down Attempt INIT Two-way Exstart Exchange Loading Full
3-13
Link-State Data Structures: LSA Operation
ROUTE v1. 0 3-10
Each LSA entry has its own aging timer, which the link-state age field carries. The default timer value for OSPF is 30 minutes (expressed in seconds in the link-state age field). After an LSA entry ages, the router that originated the entry sends the LSA (with a higher sequence number, in a Link State Update, or LSU) to verify that the link is still active. The LSU can contain one or more LSAs. This LSA validation method saves on bandwidth compared to distance vector routers, each of which sends its entire routing table at short intervals. When each router receives the LSU, it does the following: If the LSA does not already exist, the router adds the entry to its LSDB, sends a link-state acknowledgment back, floods the information to other routers, runs SPF, and updates its routing table. If the entry already exists and the received LSA has the same sequence number, the router ignores the LSA entry. If the entry already exists but the LSA includes newer information (it has a higher sequence number), the router adds the entry to its LSDB, sends a link-state acknowledgment back, floods the information to other routers, runs SPF, and updates its routing table. If the entry already exists but the LSA includes older information, it sends an LSU to the sender with its newer information.
3-14
Maintaining Link-State Sequence Numbers

This topic describes the process of maintaining a database of only the most recent link-state sequence numbers.
Defining the More Recent LSA

An LSA is more recent if it has:
A higher sequence number A higher checksum number An age equal to the maximum age (poisoning) A significantly smaller link-state age (the LSA is significantly younger)
ROUTE v1. 0 3-11
A combination of the maximum age (maxage) and refresh timers, as well as link-state sequence numbers, helps OSPF maintain a database of only the most recent link-state records. An LSA is more recent if it has: A higher sequence number A higher checksum number An age equal to the maximum age (poisoning) A significantly smaller link-state age (the LSA is significantly younger)
3-15
LSA Sequence Numbering

Each LSA in the LSDB maintains a sequence number
4-byte number begins with 0x80000001; ends with 0x7FFFFFFF
OSPF floods each LSA every 30 minutes

Each time, the sequence number is incremented by one. The LSA with the higher (newer) sequence number is more recent
Ultimately, a sequence number will wrap around to 0x80000001

The existing LSA was prematurely aged to the maximum age (one hour) and flushed.
ROUTE v1. 0 3-12
The link-state sequence number field in an LSA header is 32 bits long (4 bytes). Beginning with the leftmost bit set, the first legal sequence number is 0x80000001 and the last one is 0x7FFFFFFF. The number is incremented in each new LSA until it reaches 0xFFFFFFFF. The next number is then 0x00000000, followed by 0x00000001, etc. 0x8000000 is reserved and never used. This field is used to detect old or redundant LSAs; the larger the number, the more recent the LSA. To ensure an accurate database, OSPF floods (refreshes) each LSA every 30 minutes. Each time a record is flooded, the sequence number is incremented by one. An LSA record will reset its maximum age when it receives a new LSA update. An LSA will never remain longer in the database than the maximum age of one hour without a refresh. It is possible for an LSA to remain in the database for long periods of time, getting refreshed every 30 minutes. At some point, the sequence number will need to wrap back to the starting sequence number. When this occurs, the existing LSA will be prematurely aged out (the maximum age timer is immediately set to one hour) and flushed. The LSA will then begin its sequencing at 0x80000001 again. When a router encounters two instances of an LSA, it must determine which is more recent. The LSA with the higher link-state sequence number is the more recent LSA.
3-16
LSA Sequence Numbers and Maximum Age

Every OSPF router announces a router LSA for those interfaces that it owns in that area. Router with link ID 192.168.1.67 has been updated eight times; the last update was 48 seconds ago.
ROUTE v1. 0 3-13
Example: LSA Sequence Numbers and Maximum Age

The show ip ospf database command displays lists of information related to the Open Shortest Path First (OSPF) database for a specific router. The output of the command shown in the figure in the slide provides an example of how the link-state age and LSA sequence numbers are kept in the database. Every OSPF router has interfaces in one or more areas and announces a router LSA for those interfaces that it owns in those areas. The link ID is the ID of the router that created the router LSA. The advertising router (shown as ADV Router in the output) is the router ID of the OSPF router that announced the router LSA. Generally, the link ID and advertising router for a router LSA are the same. The first router LSA entry in the OSPF database indicates that the router LSA with link ID 192.168.1.67 has been updated eight times (because the sequence number is 0x80000008), and that the last update occurred 48 seconds ago. For more details about the show ip ospf database command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-17
Planning for Implementing OSPF

This topic describes how to plan, implement, and document the OSPF deployment.
Planning for OSPF

Assess the requirements and options: IP addressing plan Network topology Primary vs. backup links WAN bandwidth utilization Define hierarchical network design and areas Evaluate OSPF scaling options Summarization - where necessary Define stub areas
ROUTE v1. 0 3-14
The OSPF routing protocol implementation depends on specific needs and topologies. When preparing to deploy OSPF routing in a network, you must first gather the existing state and requirements, and also consider different deployment considerations as follows: The IP addressing plan governs how OSPF can be deployed and how well the OSPF deployment might scale. Thus, a detailed IP addressing plan, along with IP subnetting information, must be defined. A solid IP addressing plan should enable usage of OSPF summarization in order to scale the network and to optimize OSPF behavior more easily. A network topology consists of links connecting the network equipment (routers, switches, and so on). A detailed network topology plan should be presented in order to assess OSPF scalability requirements and determine which OSPF features might be required (for example OSPF summarization and redistribution). OSPF can control the size of the LSDB by using different areas, which decrease the LSDB size and limit the propagation of link-state updates in case of a topology change within one area.
3-18
OSPF Implementation Plan

Verify and configure IP addressing Enable OSPF for the correct interfaces Enable OSPF for the correct areas Define special metric to influence path selection Verify the configuration
Area
0 0 1 0 2 0 3
Router
R1 R2 R2 R3 R3 R4 R4
Interface
S0/0, S0/1 S0/0, S0/1 S0/2 S0/0, S0/1 S0/2 S0/0, S0/1 S0/2
ROUTE v1. 0 3-15
Once you have assessed the requirements, you can create the implementation plan. In order to implement OSPF routing you must do the following: Learn IP addressing, or more precisely, the networks that need to be included and advertised by OSPF. Enable the OSPF process for the correct interfaces or the correct network statements under the OSPF routing process configuration mode. The OSPF process must be enabled for the correct areas on the interfaces. Any specific metric that needs to be applied to certain interfaces in order to influence the default best path selection by OSPF routing protocol must be known. The table should include the required metric along with the interface where the metric needs to be applied. When the implementation plan is created, the list of task for each router in the network must be defined as follows: Enable the OSPF routing protocol on an interface, or use the correct network statements under the OSPF routing process configuration mode. Assign the correct area ID to the interface through the OSPF configuration under the interface or under the OSPF routing process configuration mode. You can also apply the metric to proper interfaces.
3-19
After implementation, you should perform verification to confirm that OSPF has been deployed properly on each router: Verify the setup of OSPF adjacency. Verify that the OSPF LSDB is populated with the proper information. Verify that the IP routing table is populated with the proper information. Verify that there is connectivity in the network. Verify that OSPF behaves as expected when a topology change occurs (test link failure and router failure events).
3-20
Documenting OSPF
Documenting OSPF:
Topology Areas and IP addressing Networks and interfaces included in OSPF per router Default and non-default metrics applied Configuration and verification results
Router R1 networks Router R2 10.1.1.0 networks 10.1.2.0 Router R3 10.2.1.0 ... networks
10.2.2.0 10.2.0.0 / 16 ...
Router
R3 R3 R3
Link
Eth0 Serial0/0 Serial0/1
Cost
10 30 64
ROUTE v1. 0 3-16
After a successful OSPF deployment, you should document the solution, and then put the information about the deployment in a safe place. The implementation plan itself is half of the information. In order to complete the documentation, you must also include the verification process and results.
3-21
Example: Planning for Basic OSPF

Define the network requirements Gather the required parameters Define the OSPF areas and routing Configure basic OSPF Verify the OSPF configuration Complete the documentation
ROUTE v1. 0 3-17
The example in the figure in the slide illustrates the steps necessary to prepare an implementation plan to configure basic OSPF. When you are planning for the basic OSPF configuration, you should ensure that the implementation plan includes the following steps: Define the network requirements. Gather the required parameters. Define OSPF routing. Configure basic OSPF. Verify the OSPF configuration.
3-22
Summary
Summary
Link-state routing protocols respond quickly to changes, send triggered updates when changes occur, and send periodic updates every 30 minutes. A two-tier hierarchical network structure is used by OSPF, in which the network is divided into areas. This area structure is used to separate the LSDB into more manageable pieces. Adjacencies are built by OSPF routers using the Hello protocol. LSUs are sent over these logical adjacencies, in order to exchange database information between adjacent OSPF routers. Dijkstras SPF algorithm is used to calculate best paths for all destinations. SPF is run against the LSDB, and the result is a table of best paths, known as the routing table.
ROUTE v1. 0 3-18
Summary (Cont.)
After an LSA entry ages, the router that originated the entry sends an LSU about the network to verify that the link is still active. The LSU can contain one or more LSAs. Each LSA in the LSDB has a sequence number, which is incremented by one each time the LSA is flooded. When a router encounters two instances of an LSA, it must determine which is more recent. The LSA with the higher LSA sequence number is the more recent. When planning an OSPF deployment, define the network requirements, gather the required parameters, and define the OSPF routing.
ROUTE v1. 0 3-19
3-23
3-24
Lesson 2
How OSPF Packet Processes Work

Overview
The Open Shortest Path First Protocol (OSPF) protocol has several functions and five packet types to support them: hello, database description (DBD), link-state request (LSR), link-state update (LSU), and link-state acknowledgement (LSAck). The five OSPF packet types enable all OSPF information flow between routers. This lesson defines each packet type and explains where and how these packets interact to build OSPF neighbor adjacencies and maintain the OSPF topology database.
Objectives
Upon completing this lesson, you will be able to explain how information flows between routers to maintain OSPF links and which packets are used. This ability includes being able to meet these objectives: Determine OSPF packet types Establish OSPF neighbor adjacencies Exchange and synchronize LSDBs Maintain network routes Verify packet flow
OSPF Packet Types

This topic describes the five OSPF packet types.
OSPF Functions
High-level functions of OSPF include the following:
Discover neighbors and form adjacencies Flood link-state database (LSDB) information Compute the shortest path Install routes in the route-forwarding table
Additional functions of OSPF include the following:

Detect changes in the link state Propagate changes to maintain link-state database synchronization
Several OSPF packet types are involved
ROUTE v1.03-2
In order for OSPF to operate properly, several processes must occur: Neighbor discovery to form adjacencies Flooding of the link state information in order to build a link-state database (LSDB) Computation of SPF to find out the shortest path to all known destinations Populating of the route forwarding table with the best routes to known destinations Once OSPF initially populates the router forwarding table, the state of the links around the OSPF autonomous system may change. OSPF is able to detect these changes and respond by flooding this information throughout the OSPF autonomous system, or at least in the area where the change was detected. The flooding of new information is needed in order to maintain the link-state databases (LSDBs) in all neighboring routers. For all functions above, several OSPF packet types are involved and will be described in this Lesson.
3-26
OSPF Packet Header Format

This debug output shows fields in the OSPF header.
ROUTE v1.03-3
All five OSPF packets are encapsulated directly into an IP payload, as shown in the figure. The OSPF packet does not use TCP or User Datagram Protocol (UDP). OSPF requires a reliable packet transport scheme, and because it does not use TCP, it has defined its own acknowledgment routine using an acknowledgment packet (OSPF packet type 5). In the IP header, a protocol identifier of 89 defines all OSPF packets. Each of the OSPF packets begins with the same header format. This header has the following fields: Version number: Version 2 for OSPF with IPv4 and version 3 for OSPF with IPv6 Type: Differentiates the five OSPF packet types Packet length: Is the length of the OSPF packet in bytes Router ID: Defines which router is the source of the packet Area ID: Defines the area where the packet originated Checksum: Is used for packet-header error detection to ensure that the OSPF packet was not corrupted during transmission Authentication type: Is an option in OSPF that describes either no authentication, cleartext passwords, or encrypted Message Digest 5 (MD5) formats for router authentication Authentication: Is used in the authentication scheme Data: Each of the five packet types includes different data Hello packets: Contains a list of known neighbors DBD packet: Contains a summary of the link-state database (LSDB), which includes all known router IDs and their last sequence numbers, among a number of other fields LSR packet: Contains the type of LSU needed and the router ID that has the needed LSU LSU packet: Contains the full link-state advertisement (LSA) entries. Multiple LSA entries can fit in one OSPF update packet LSAck packet: Is empty
Implementing a Scalable Multiarea Network OSPF-Based Solution 3-27

OSPF Packet Types

OSPF uses five types of routing protocol packets.
ROUTE v1.03-4
OSPF uses five types of routing protocol packets, which share a common protocol header. The protocol ID number inside the IP header is 89, and all five packet types are used in the normal operation of OSPF. OSPF Packets The table contains descriptions of each type.
Type 1 2 3 4 5 Packet Name Hello DBD LSR LSU LSAck Description Discovers neighbors and builds adjacencies between them Checks for database synchronization between routers Requests specific link-state records from another router Sends specifically requested link-state records Acknowledges the other packet types
3-28
Establishing OSPF Neighbor Adjacencies

This topic describes how OSPF neighbor adjacencies are established.
Neighbor Relationship: The Hello Packet

* Entries must match on neighboring routers
ROUTE v1.03-5
Each interface participating in OSPF uses IP multicast address 224.0.0.5 to send hello packets periodically. A hello packet contains the following information: Router ID: The router ID is a 32-bit number that uniquely identifies the router. The highest IP address on an active interface is chosen by default, unless a loopback interface or the router ID is configured; for example, IP address 172.16.12.1 would be chosen over 172.16.1.1. This identification is important in establishing neighbor relationships and coordinating LSU exchanges. Also, the router ID breaks ties during the designated router (DR) and backup designated router (BDR) selection processes if the OSPF priority values are equal. Hello and dead intervals: The hello interval specifies the frequency, in seconds, with which a router sends hello packets (10 seconds is the default on multiaccess networks). The dead interval is the time in seconds that a router waits to hear from a neighbor before declaring the neighboring router out of service (four times the hello interval, by default). These timers must be the same on neighboring routers; otherwise an adjacency will not be established. Neighbors: The neighbors field lists the adjacent routers with established bidirectional communication. This bidirectional communication is indicated when the router recognizes itself listed in the neighbors field of the hello packet from the neighbor. Area ID: To communicate, two routers must share a common segment, and their interfaces must belong to the same OSPF area on that segment (they must also share the same subnet and mask). These routers will all have the same link-state information. Router priority: The router priority is an 8-bit number that indicates the priority of a router. Priority is used when selecting a DR and BDR. DR and BDR IP addresses: These are the IP addresses of the DR and BDR for the specific network, if they are known.
2009 Cisco Systems, Inc. Implementing a Scalable Multiarea Network OSPF-Based Solution 3-29
Authentication password: If router authentication is enabled, two routers must exchange the same password. Authentication is not required, but if it is enabled, all peer routers must have the same password. Stub area flag: A stub area is a special area. Two routers must agree on the stub area flag in the hello packets. Designating a stub area is a technique that reduces number of routing updates by replacing many of them with a default route.
Note The following fields must match when hello packets are exchanged between the neighboring routers: hello and dead intervals, area ID, authentication password, and stub area flag.
3-30
Exchanging and Synchronizing LSDBs

Once a bidirectional adjacency is formed, OSPF must exchange and synchronize the LSDBs between routers. This topic describes the process of exchanging and synchronizing the LSDBs between routers.
OSPF Routing Update Packets

Use of Multicast and unicast IP address Four types of update packets LSDB synchronization process Discover neighbor Establish bidirectional communication Elect a designated router, if desired Form an adjacency Discover the network routes Update and synchronize link-state databases
ROUTE v1.03-6
All routing updates are sent in IP packets (protocol type 89), for which OSPF does not do any fragmentation and reassembly on the IP. Four types of update packets are used when exchanging and synchronizing LSDBs: Type 2 database description packet: Used to describe the network routes of each neighbor. Type 3 link-state request packet: After database description packets are exchanged, the routers request missing information by using request packets. Type 4 link-state update packet: All missing information is sent to the neighbors by sending update packets, which contain different LSAs. Type 5 link-state acknowledgment packet: Every packet is acknowledged, to ensure reliable transport and reliable exchange of information. Type 4 and type 5 packets are sent to multicast IP addresses, except when retransmitting, when sent across a virtual link, and when sent on non-broadcast networks. All other packets are sent to unicast IP addresses. The LSDB synchronization process starts with neighbor discovery. After a neighbor has been discovered, bidirectional communication commences. A designated router may also be elected (for example if the OSPF protocol is active on the LAN). Then routers make a decision whether or not an adjacency is formed. If an adjacency is to be formed, neighbors have to synchronize link-state databases. First, network routes are discovered, and then missing information is exchanged. Finally, LSDB is synchronized, as described in the following pages.
Establishing Bidirectional Communication
ROUTE v1.03-7
When routers running OSPF are initialized, an exchange process using the Hello protocol is the first procedure. The exchange process that happens when routers appear on the network is illustrated in the figure in the slide: 1. Router R1 is enabled on the LAN and is in a down state, because it has not exchanged information with any other router. It begins by sending a hello packet through each of its interfaces participating in OSPF, even though it does not know the identity of the DR or of any other routers. The hello packet is sent out using the multicast address 224.0.0.5. 2. All directly connected routers running OSPF receive the hello packet from router R1 and add router R1 to their lists of neighbors. After adding router R1 to the list other router are in the initial state (INIT state). 3. Each of the routers that received the hello packet sends a unicast reply hello packet to router R1 with its corresponding information. The neighbor field in the hello packet includes all neighboring routers and router R1. 4. When router R1 receives these hello packets, it adds all the routers that had its router ID in their hello packets to its own neighbor relationship database. After this process router R1 is in the two-way state. At this point, all routers that have each other in their lists of neighbors have established bidirectional communication. If the link type is a broadcast network, generally a LAN link like Ethernet, then a DR and BDR must first be selected. The DR forms bidirectional adjacencies with all other routers on the LAN link. This process must occur before the routers can begin exchanging link-state information. Periodically (every 10 seconds on broadcast networks, by default) the routers within a network exchange hello packets to ensure that communication is still working. The hello updates include the DR, BDR, and the list of routers for which hello packets have been received by the router. Remember that received means that the receiving router recognizes its own name as one of the entries in the received hello packet.
Note The concept of DR and BDR will be described later in this module.
3-32
Discovering the Network Routes
ROUTE v1.03-8
After the DR and BDR have been selected (applied to LAN link types), the routers are considered to be in the exstart state. The routers are then ready to discover the link-state information about the internetwork and create their LSDBs. The exchange protocol is used to discover the network routes, and it gets all the routers from exchange state to a full state of communication. The first step in this process is for the DR and BDR to establish adjacencies with each of the other routers. When adjacent routers are in a FULL state, they do not repeat the exchange protocol unless the full state changes. As shown in the figure, the exchange protocol operates as follows:
Step 1
In the exstart state, the DR and BDR establish adjacencies with each router in the network. During this process, a master-slave relationship is created between each router and its adjacent DR and BDR. The router with the higher router ID acts as the master during the exchange processRouter R2 becomes DR.
Only the DR exchanges and synchronizes link-state information with the routers to which it has established adjacencies. Having the DR represent the network in this capacity reduces the amount of routing update traffic. The concepts of DR and BDR will be explained later in this module.
Note
The master and slave routers exchange one or more DBD packets. The routers are in the exchange state. A DBD includes information about the LSA entry header that appears in the LSDB of the router. The entries can be about a link or about a network. Each LSA entry header includes information about the link-state type, the address of the advertising router, the cost of the link, and the sequence number. The router uses the sequence number to determine the newness of the received link-state information.
3-33
Adding the Link-State Entries
ROUTE v1.03-9
Step 2
When the router receives the DBD, it performs these actions, as shown in the figure: 1. It acknowledges the receipt of the DBD using the LSAck packet. 2. It compares the information it received with the information it has. If the DBD has a more up-to-date link-state entry, then the router sends an LSR to the other router. When routers start sending LSRs they are in the loading state. 3. The other router responds with the complete information about the requested entry in an LSU packet. Again, when the router receives an LSU, it sends an LSAck.
Step 3
The router adds the new link-state entries to its LSDB.
When all LSRs have been satisfied for a given router, the adjacent routers are considered synchronized. They are in a full state. The routers must be in a full state before they can route traffic. At this point, all the routers in the area should have identical LSDBs.
3-34
OSPF Neighbor States

OSPF routers progress through seven states:
Down: no active neighbor detected INIT: hello packet received Two-way: own router ID in received hello Exstart: master and slave roles determined Exchange: database description packets sent Loading: exchange of LSRs and LSUs Full: neighbors fully adjacent
ROUTE v1. 0 3-10
The following is a brief summary of the states an interface passes through before becoming adjacent to another router: Down: No information has been received from anybody on the segment. Attempt: In nonbroadcast multiaccess clouds such as Frame Relay and X.25, this state indicates that no recent information has been received from the neighbor. An effort should be made to contact the neighbor by sending hello packets at the reduced rate poll interval. INIT: The interface has detected a hello packet coming from a neighbor but bidirectional communication has not yet been established. Two-way: There is bidirectional communication with a neighbor. The router has seen itself in the hello packets coming from a neighbor. At the end of this stage, the DR and BDR election would have been done. When routers are in the two-way state they must decide whether to proceed in building an adjacency or not. The decision is based on whether one of the routers is a DR or BDR or the link is a point-to-point or a virtual link. Exstart: Routers are trying to establish the initial sequence number that is going to be used in the information exchange packets. The sequence number ensures that routers always get the most recent information. One router will become the primary and the other will become secondary. The primary router will poll the secondary for information. Exchange: Routers will describe their entire link-state database by sending database description packets. In this state, packets may be flooded to other interfaces on the router. Loading: In this state, routers are finalizing the information exchange. Routers have built a link-state request list and a link-state retransmission list. Any information that looks incomplete or outdated will be put on the request list. Any update that is sent will be put on the retransmission list until it gets acknowledged. Full: In this state, adjacency is complete. The neighboring routers are fully adjacent. Adjacent routers will have similar link-state databases.
3-35
Maintaining Network Routes

This topic describes how OSPF maintains synchronization of the LSDBs (topology tables) of all routers in the network.
Flooding Changes in Topology

Router R1 that detects a topology change adjusts its LSA and floods the LSA: Router R1 notifies all OSPF neighbors using 224.0.0.5, or, on LAN links, all OSPF DRs and BDRs using 224.0.0.6. The DR notifies others on 224.0.0.5. The LSDBs of all routers must be synchronized.
ROUTE v1. 0 3-11
In a link-state routing environment, it is very important for the LSDBs (topology tables) of all routers to stay synchronized. When there is a change in a link state, the routers use a flooding process to notify the other routers in the network of the change. LSUs provide the mechanism for flooding LSAs. A router that detects a topology change adjusts its LSA, increments its LSA sequence number and floods the LSA. Only the LSA originator can adjust or regenerate the LSA. A router that receives an LSA update packet compares the received LSA to its own copy. If the received LSA is more recent, it is installed in the database and flooded. If the database copy is newer, it is send back to the sending neighbor. This is an exception to the rule, because a router is not supposed to re-originate the LSAs of other routers. Periodic LSA refreshment is another mechanism to maintain the LSDB. Each LSA has an age field. LSAs are aged when flooded and in the topology database. LSAs that reach the maximum age are purged from the topology database (garbage collection). Each router has to resend its LSA (the LSA that was originated from that router) before it ages out in the topology databases. LSAs with an age equal to the maximum age are used to immediately remove LSAs from the database (route poisoning). In general, the flooding process steps in a multiaccess network are as follows:
Step 1
A router notices a change in a link state and multicasts an LSU packet (which includes the updated LSA entry) to all OSPF neighbors (on point-to-point links) at 224.0.0.5 or to all OSPF DRs and BDRs (on LAN links like the one in the figure in the slide) at 224.0.0.6. An LSU packet may contain several distinct LSAs.
3-36
Step 2
The DR acknowledges receipt of the change and floods the LSU to others on the network using the OSPF multicast address 224.0.0.5. After receiving the LSU, each router responds to the DR with an LSAck. To make the flooding procedure reliable, each LSA must be acknowledged separately. If a router is connected to other networks, it floods the LSU to those other networks by forwarding the LSU to the DR of the multiaccess network (or to the adjacent router if it is in a point-to-point network). The DR, in turn, multicasts the LSU to the other routers in the network. The router updates its LSDB using the LSU that includes the changed LSA. It then recomputes the shortest path first (SPF) algorithm against the updated database after a short delay (the SPF delay) and updates the routing table as necessary.
Although it is not shown in this figure, all LSUs are acknowledged.
Step 3
Step 4
Note
When is the SPF algorithm run? A change in the topology database is a necessary, but not sufficient condition for SPF recalculation. The SPF algorithm is triggered if: The LSA Options field has changed The age of the LSA instance is set to MaxAge The length field in the LSA header has changed The contents of the LSA (excluding the LSA header) have changed An SPF calculation is performed separately for each area in the topology database. OSPF simplifies the synchronization issue by requiring only adjacent routers to remain synchronized. Summaries of individual link-state entries, not the complete link-state entries, are sent every 30 minutes to ensure proper LSDB synchronization. Each link-state entry has a timer to determine when the LSA refresh update must be sent. Each link-state entry also has a maximum age of 60 minutes. If a link-state entry has not been refreshed within 60 minutes, it is removed from the LSDB.
Note On a Cisco router, if a route already exists, the routing table is used at the same time the SPF algorithm is calculating new best route to the destination. However, if the SPF is calculating a new route, the new route is used only after the SPF calculation is complete.
3-37
Verifying Packet Flow

This topic describes how to verify that OSPF packets are flowing properly between two routers.
The debug ip ospf packet Command

Debugging a single packet

This debug output shows the fields in the OSPF header.
ROUTE v1. 0 3-12
The debug ip ospf packet command is used to verify that OSPF packets are flowing properly between two routers as well as for troubleshooting.
Example: debug ip ospf packet

The output of this debug command is shown in the figure. Notice that the output shows the fields in the OSPF header, but they are not described in any detail. After each field there is a parameter for it. The values are described in the table below. From the table below and from the sample output we can say the following:

OSPF: rcv. v:2 t:1 l:48 rid:10.0.0.12 aid:0.0.0.1

3-38
- OSPF packet - was received - OSPF version 2 - Hello packet - 48 bytes is the OSPF packet length - The OSPF router ID is 10.0.0.12 - The OSPF area ID is 0.0.0.1
chk:D882 aut:0 auk: from Serial0/0/0.2
- The OSPF checksum is D882 - Authentication is not being used - There is no key, as authentication is not being used - The packet was received via interface Serial0/0/0.2
OSPF Packet Header Fields The table lists the OSPF packet header fields represented in this output.
Field v t Description Provides the version of OSPF Specifies the OSPF packet type: 1: hello 2: DBD 3: LSR 4: LSU 5: LSAck l rid aid chk Specifies the OSPF packet length in bytes Provides the OSPF router ID Shows the OSPF area ID Displays the OSPF checksum Provides the OSPF authentication type: 0: No authentication aut 1: Simple password 2: MD5 auk keyid seq Specifies the OSPF authentication key, if used Displays the MD5 key ID; only used for MD5 authentication Provides the sequence number; only used for MD5 authentication
For more details about the debug ip ospf packet command, please check the Cisco IOS Debug Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/debug/command/reference/db_book.html
3-39
Summary
Summary
There are five OSPF packet types: hello, DBD, LSU, LSR, and LSAck. The Hello protocol forms logical neighbor adjacency relationships. A DR may be required to coordinate adjacency formations. The exchange protocol passes through several states (down, INIT, two-way, exstart, exchange, and loading) before finally reaching the goal of the full state. When the protocol is in the full state, its databases are synchronized with adjacent routers. LSAs are sent when a change occurs, but are also sent every 30 minutes to ensure database integrity. The maximum time that an LSA will stay in the database, without an update, is 1 hour. Use the debug ip ospf packet command to verify that OSPF packets are flowing properly between two routers.
ROUTE v1. 0 3-13
3-40
Lesson 3
Improving Routing Performance in a Complex Enterprise Network

Overview
Open Shortest Path First Protocol (OSPF) areas may be made up of different types of network links. You must know which ones are being used in order to properly configure OSPF to work with all of them and their different adjacency behaviors as well as over certain network types. It is important to note that OSPF pays special attention to different network types, such as point-to-point and broadcast networks, and that the OSPF default settings do not always work properly with some network topologies. This lesson describes each OSPF network type, how the adjacencies are formed for these OSPF network types, and how link-state advertisements (LSAs) are flooded on each.
Objectives
Upon completing this lesson, you will be able to describe the features of various OSPF network architectures. This ability includes being able to meet these objectives: Introduce OSPF network types Determine adjacency behavior in point-to-point links Determine adjacency behavior in a broadcast network Determine adjacency behavior in a Metro Ethernet and EoMPLS network Determine adjacency behavior in MPLS networks Select a DR and BDR Implement OSPF over different Frame Relay implementations Implement OSPF over Frame Relay NBMA Use subinterfaces in OSPF over Frame Relay
Implement OSPF over a point-to-point Frame Relay network Implement OSPF over a point-to-multipoint Frame Relay network
3-42
Introducing OSPF Network Types

This topic describes the three types of networks defined by OSPF.
OSPF Network Types

Point-to-point: A network that joins a single pair of routers. Broadcast: A multiaccess broadcast network, such as Ethernet. Nonbroadcast multiaccess (NBMA): A network that interconnects more than two routers but that has no broadcast capability. Examples: Frame Relay, ATM, and X.25 Five modes of OSPF operation are available for NBMA networks
ROUTE v1.03-2
OSPF defines distinct types of networks, based on their physical link types. OSPF operation on each type is different, including how adjacencies are established and what configuration is required. There are three types of networks that are defined by OSPF: Point-to-point: A network that joins a single pair of routers. Broadcast: A multiaccess broadcast network, such as Ethernet. Nonbroadcast multiaccess (NBMA): A network that interconnects more than two routers but that has no broadcast capability. Frame Relay, ATM, and X.25 are examples of NBMA networks. There are five modes of OSPF operation available for NBMA networks, as described later in this lesson.
3-43
Adjacency Behavior in Point-to-Point Links

This topic describes the adjacency behavior for point-to-point serial links.
Point-to-Point Links
Usually a serial interface running either PPP or HDLC May also be a point-to-point subinterface running Frame Relay or ATM Does not require DR or BDR election Is automatically detected by OSPF Sends OSPF packets using multicast 224.0.0.5
ROUTE v1.03-3
A point-to-point network joins a single pair of routers. A T1 serial line configured with a linklayer protocol such as PPP or High-Level Data Link Control (HDLC) is an example of a pointto-point network. On point-to-point networks, the router dynamically detects its neighboring routers by multicasting its hello packets to all OSPF routers, using the address 224.0.0.5. On point-topoint networks, neighboring routers become adjacent whenever they can communicate directly. No designated router (DR) or backup designated router (BDR) election is performed. This is because there can be only two routers on a point-to-point link, so there is no need for a DR or BDR. Usually, the IP source address of an OSPF packet is set to the address of the outgoing interface on the router. It is possible to use IP unnumbered interfaces with OSPF. On unnumbered interfaces, the IP source address is set to the IP address of another interface on the router. The default OSPF hello and dead intervals on point-to-point links are 10 seconds and 40 seconds, respectively.
3-44
Adjacency Behavior in a Broadcast Network

This topic describes the adjacency behavior for a broadcast network link.
Multiaccess Broadcast Network

This generally applies to LAN technologies like Ethernet. DR and BDR selection are required. All neighbor routers form full adjacencies with the DR and BDR only. Packets to the DR and the BDR use 224.0.0.6. Packets from DR to all other routers use 224.0.0.5.
ROUTE v1.03-4
An OSPF router on a multiaccess broadcast network such as Ethernet forms an adjacency with its DR and BDR. Adjacent routers have synchronized link-state databases (LSDBs). A common media segment is the basis for adjacency, such as an Ethernet segment connecting two routers. When routers first come up on the Ethernet, they perform the hello process and then elect the DR and BDR. The routers then attempt to form adjacencies with the DR and BDR. The routers on a segment must elect a DR and a BDR to represent the multiaccess broadcast network. The BDR does not perform any DR functions when the DR is operating. 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. If the DR fails, the BDR automatically becomes the DR and a new BDR election occurs. The DR and BDR improve network functioning in the following ways: Reducing routing update traffic: The DR and BDR act as central point of contact for link-state information exchange on a multiaccess broadcast network; therefore, each router must establish a full adjacency with the DR and the BDR only. Each router, rather than exchanging link-state information with every other router on the segment, sends the linkstate information to the DR and BDR only. The DR represents the multiaccess broadcast network in the sense that it sends link-state information from each router to all other routers in the network. This flooding process significantly reduces the router-related traffic on a segment.
3-45
Managing link-state synchronization: The DR and BDR ensure that the other routers on the network have the same link-state information about the internetwork. In this way, the DR and BDR reduce the number of routing errors.
Note After a DR and BDR have been selected, any router added to the network establishes adjacencies with the DR and BDR only.
3-46
Adjacency Behavior in a Metro Ethernet and EoMPLS Network

This topic describes the adjacency behavior in a Metro Ethernet and Ethernet over Multiprotocol Label Switching (EoMPLS) network link.
OSPF Adjacency Over Metro Ethernet and EoMPLS

EoMPLS and Metro Ethernet service does not participate in STP, nor does it learn MAC addresses Customer routers R1 and R2 exchange Ethernet frames via an interface or VLAN subinterfaces OSPF behaves the same as on Ethernet OSPF network type = Multiaccess Broadcast Network DR and BDR are elected Routers form full adjacencies with the DR and BDR only
ROUTE v1.03-5
The service providers MPLS backbone is used to enable Layer 2 Ethernet connectivity between the two customer routers R1 and R2, whether an EoMPLS or Metro Ethernet service is used. Routers R1 and R2 thus exchange Ethernet frames. Provider edge router (PE-router) PE1 takes the Ethernet frames received from router R1 on the link to PE1, encapsulates them into MPLS packets, and forwards them across the backbone to router PE2. Router PE2 de-encapsulates the MPLS packets and reproduces the Ethernet frames on the link towards router R2. EoMPLS and Metro Ethernet typically do not participate in Spanning Tree Protocol (STP) and bridge protocol data unit (BPDU) exchanges, so EoMPLS and Metro Ethernet are transparent to the customer routers. The Ethernet frames are transparently exchanged across the MPLS backbone. Keep in mind that customer routers can be connected either in a port-to-port fashion, in which PE-routers take whatever Ethernet frame is received and forward the frames across the Layer 2 MPLS VPN backbone, or in a VLAN subinterface fashion, in which frames for a particular VLAN, identified with subinterface in configuration, are encapsulated and sent across the Layer 2 MPLS VPN backbone. When deploying OSPF over EoMPLS, there are no changes to the existing OSPF configuration from the customer perspective. OSPF needs to be enabled and network commands must include the interfaces required by the relevant OSPF area in order to start the OSPF properly.
Routers R1 and R2 form a neighbor relationship with each other over the Layer 2 MPLS VPN backbone. From an OSPF perspective, the Layer 2 MPLS VPN backbone, router PE1, and router PE2 are all invisible. A neighbor relationship is established between routers R1 and R2 directly, and behaves in the same way as on a regular Ethernet broadcast network.
3-48
Adjacency Behavior in MPLS networks

This topic describes the adjacency behavior in an MPLS network link.
OSPF Adjacency Over MPLS VPN

Customer routers run OSPF and exchange routing updates with the PE routers PE routers appear as another router in the customers network Service providers P routers are hidden from the customer Customer routers are unaware of MPLS VPN Customer and service provider must agree on OSPF parameters Customer Routers to PE connection can be of any type OSPF behaves per the connection type (point-to-point, broadcast, NBMA)
ROUTE v1.03-6
With the Layer 3 MPLS VPN architecture, the ISP provides a peer-to-peer VPN architecture. In this architecture, Provider Edge-routers (PE-routers) participate in customer routing, guaranteeing optimum routing between customer sites. Therefore, the PE-routers carry a separate set of routes for each customer, resulting in perfect isolation between the customers. The following apply to the Layer 3 MPLS VPN technology, even when running OSPF as a provider edge-customer edge (PE-CE) routing protocol: The customer routers should not be aware of MPLS VPN; they should run standard IP routing software. The provider routers (P-routers) must not carry VPN routes for the MPLS VPN solution to be scalable. The provider edge routers (PE-routers) must support MPLS VPN services and traditional Internet services. To OSPF, the Layer 3 MPLS VPN backbone looks like a standard corporate backbone and it run standard IP routing software. Routing updates are exchanged between the Customer-routers (C-routers) and the PE routers that appear as normal routers in the customers network. OSPF is enabled on proper interfaces using the network command. The standard design rules that are used for enterprise Layer 3 MPLS VPN backbones can be applied to the design of the customers network. The P routers are hidden from the customers view and Customer Edgerouters (CE routers) are unaware of MPLS VPN. The internal topology of the Layer 3 MPLS backbone is therefore totally transparent to the customer. The PE routers receive IPv4 routing updates from the CE routers and install them in the appropriate VRF table. This part of the configuration and operation is the responsibility of a service provider.
3-49
The CE-PE can have any OSPF network typepoint-to-point, broadcast, or even nonbroadcast multiaccess. The only difference between a CE-PE design and a regular OSPF design is that the customer has to agree with the service provider about the OSPF parameters (AS number, authentication password, and so on), where usually these parameters are governed by the service provider.
3-50
Selecting a DR and BDR

This topic describes how OSPF routers apply conditions to the OSPF priority values of other routers during the hello packet exchange process to elect a DR and BDR.
Electing the DR and BDR

Hello packets are exchanged via IP multicast DR: The router with the highest OSPF priority BDR: The router with the second-highest priority value The OSPF router ID is used as the tiebreaker The DR election is nonpreemptive
ROUTE v1.03-7
To elect a DR and BDR, the routers view the OSPF priority value of other routers during the hello packet exchange process and then use the following conditions to determine which router to select: The router with the highest priority value is the DR. The router with the second-highest priority value is the BDR. The default for the interface OSPF priority is 1. In the case of a tie, the router ID is used. 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 set to zero cannot become the DR or BDR. A router that is not the DR or BDR is called a DROTHER. If a router with a higher priority value is added to the network, it does not preempt the DR and BDR. The only time a DR or BDR changes is when one of them is out of service. If the DR is out of service, the BDR becomes the DR and a new BDR is selected. If the BDR is out of service, a new BDR is elected. To determine whether the DR is out of service, the BDR uses the wait timer. This timer is a reliability feature. If the BDR does not confirm that the DR is forwarding LSAs before the timer expires, then the BDR assumes that the DR is out of service.
Note The highest IP address on an active interface is normally used as the router ID; however, you can override this selection by configuring an IP address on a loopback interface or using the router-id router configuration command.
3-51
In a multiaccess broadcast environment, each network segment has its own DR and BDR. A router connected to multiple multiaccess broadcast networks can be a DR on one segment and a regular router on another segment.
Note The DR operation is at the link level; a DR is selected for every multiaccess broadcast link in the OSPF network.
3-52
Setting the Priority for DR Election

This interface configuration command assigns the OSPF priority to an interface. Different interfaces on a router may be assigned different values. The default priority is 1. The range is from 0 to 255. 0 means the router cannot be the DR or BDR. A router that is not the DR or BDR is DROTHER.
ROUTE v1.03-8
Use the ip ospf priority command to designate which router interfaces on a multiaccess link are the DR and the BDR. The default priority is 1, and the range is from 0 to 255. The interface with the highest priority becomes the DR, and the interface with the second-highest priority becomes the BDR. Interfaces that are set to a priority of 0 cannot be involved in the DR or BDR election process.
Note The priority of an interface takes effect only when the existing DR goes down. A DR does not relinquish its status just because a new interface reports a higher priority in its hello packet.
For more details about the ip ospf priority command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-53
OSPF over Different Frame Relay Implementations

This topic describes the adjacency behavior for a Frame Relay NBMA network.
NBMA Topology
A single interface interconnects multiple sites NBMA topologies support multiple routers, but without broadcasting capabilities Five modes of OSPF operation are available
ROUTE v1.03-9
When a single interface interconnects multiple sites over an NBMA network, the nonbroadcast nature of the network can lead to reachability issues. NBMA networks can support more than two routers but have no broadcast capability. For example, if the NBMA topology is not fully meshed, then a broadcast or multicast sent by one router will not reach all the other routers. Frame Relay, ATM, and X.25 are examples of NBMA networks. To implement broadcasting or multicasting in an NBMA network, the router replicates the packets to be broadcast or multicast and sends them individually on each permanent virtual circuit (PVC) to all destinations. This process is CPU- and bandwidth-intensive. The default OSPF hello and dead intervals on NBMA interfaces are 30 seconds and 120 seconds, respectively.
3-54
DR Election in NBMA Topology

OSPF considers NBMA to be like other broadcast media. The DR and BDR need to have fully meshed connectivity with all other routers, but NBMA networks are not always fully meshed. The DR and BDR each need a list of neighbors. OSPF neighbors are not automatically discovered by the router.
ROUTE v1. 0 3-10
OSPF treats NBMA environments like any other broadcast media environments, such as Ethernet; however, NBMA clouds are usually built in hub-and-spoke topologies, using PVCs or switched virtual circuits (SVCs). A hub-and-spoke topology means that the NBMA network is only a partial mesh. In these cases, the physical topology does not provide multiaccess capability, on which OSPF relies. The election of the DR becomes an issue in NBMA topologies, because the DR and BDR need to have full physical connectivity with all routers in the NBMA network. The DR and BDR also need to have a list of all the other routers, so that they can establish adjacencies. OSPF cannot automatically build adjacencies with neighboring routers over NBMA interfaces.
3-55
Frame Relay Topologies
ROUTE v1. 0 3-11
There are several OSPF configuration choices for a Frame Relay network, depending on the Frame Relay network topology. With Frame Relay, remote sites interconnect in a variety of ways. By default, interfaces that support Frame Relay are multipoint connection types. The following examples are types of Frame Relay topologies: Star topology: A star topology, also known as a hub-and-spoke configuration, is the most common Frame Relay network topology. In this topology, remote sites connect to a central site that generally provides a service or application. The star topology is the least expensive topology, because it requires the smallest number of PVCs. The central router provides a multipoint connection, because it typically uses a single interface to interconnect multiple PVCs. Full-mesh topology: In a full-mesh topology, all routers have virtual circuits to all other destinations. This method, although costly, provides direct connections from each site to all other sites and allows for redundancy. As the number of nodes in the full-mesh topology increases, the topology becomes increasingly expensive. To figure out how many virtual circuits are needed to implement a fully meshed topology, use the formula (n * (n 1)) / 2, where n is the number of nodes in the network. Partial-mesh topology: In a partial-mesh topology, not all sites have direct access to a central site. This method reduces the cost of implementing a full-mesh topology.
3-56
OSPF over NBMA Topology Modes of Operation

There are five modes of OSPF operation. RFC 2328-compliant modes are as follows: Nonbroadcast (NBMA) Point-to-multipoint Additional modes from Cisco are as follows: Point-to-multipoint nonbroadcast Broadcast Point-to-point
ROUTE v1. 0 3-12
As described in RFC 2328, OSPF runs in one of the following two official modes in NBMA topologies: Nonbroadcast: The nonbroadcast (NBMA) mode simulates the operation of OSPF in broadcast networks. Neighbors must be manually configured, and DR and BDR election is required. This configuration is typically used with fully meshed networks. Point-to-multipoint: The point-to-multipoint mode treats the nonbroadcast network as a collection of point-to-point links. In this environment, the routers automatically identify their neighboring routers but do not elect a DR and BDR. This configuration is typically used with partially meshed networks. The choice between NBMA and point-to-multipoint modes determines the way the Hello protocol and flooding work over the nonbroadcast network. The main advantage of the pointto-multipoint mode is that it requires less manual configuration, and the main advantage of the nonbroadcast mode is that there is less overhead traffic. Cisco has defined the following additional modes: Point-to-multipoint nonbroadcast Broadcast Point-to-point
3-57
The description of all the modes is as follows:

OSPF network type over NBMA topology Description
Cisco extension. Makes the WAN interface appear to be a LAN Has one IP subnet Uses multicast OSPF hello packets to automatically discover the neighbors Elects the DR and BDR. Requires a full-mesh or a partial-mesh topology
RFC-compliant mode. Has one IP subnet Requires neighbors to be manually configured Elects the DR and BDR Requires that the DR and BDR have full connectivity with all other routers Is typically used in a full-mesh or a partial-mesh topology
RFC-compliant mode. Has one IP subnet Uses multicast OSPF hello packets to automatically discover the neighbors Does not require DR and BDRrouter sends additional LSAs with more information about neighboring routers Is typically used in partial-mesh or star topology
Cisco extension. Is used in place of RFC-compliant point-to-multipoint mode if multicast and broadcast are not enabled on the virtual circuits, because the router cannot dynamically discover its neighboring routers using hello multicast packets Requires neighbors to be manually configured Does not require DR and BDR election Cisco extension. Has a different IP subnet on each subinterface Does not have DR or BDR election Is used when only two routers need to form an adjacency on a pair of interfaces Can be used with either LAN or WAN Interfaces
Broadcast mode is a workaround for statically listing all existing neighboring routers. The interface is set to broadcast and behaves as though the router connects to a LAN. DR and BDR election is still performed; therefore, take special care to ensure either a full-mesh topology or a static election of the DR based on the interface priority. The other modes are examined in the following topics.
3-58
OSPF over Frame Relay NBMA

This topic describes how to configure an NBMA topology in an OSPF over Frame Relay network.
Nonbroadcast Mode (NBMA Mode)

Treated as a broadcast network by OSPF (like a LAN) All serial ports are part of the same IP subnet Frame Relay, X.25, and ATM networks default to nonbroadcast mode Duplicates LSA updates
ROUTE v1. 0 3-13
In nonbroadcast mode, OSPF emulates operation over a broadcast network. A DR and BDR are elected for the NBMA network, and the DR originates an LSA for the network. In this environment, the routers are usually fully meshed to facilitate the establishment of adjacencies among the routers. If the routers are not fully meshed, then you should select the DR and BDR manually to ensure that the selected DR and BDR have full connectivity to all other neighboring routers. Neighboring routers are statically defined to start the DR and BDR election process. When using nonbroadcast mode, all routers are on one IP subnet. For flooding over a nonbroadcast interface, the link-state update (LSU) packet must be replicated for each PVC. The updates are sent to each of the neighboring routers defined in the neighbor table on the interface. When there are few neighbors in the network, nonbroadcast mode is the most efficient way to run OSPF over NBMA networks, because it has less overhead than point-to-multipoint mode. Frame Relay networks default to OSPF nonbroadcast mode.
3-59
Steps to Configure NBMA Mode

Enable the OSPF routing process Define the interfaces that OSPF will run on
NBMA-specific configuration:
Statically define a neighbor relationship Define the OSPF network type
ROUTE v1. 0 3-14
At the beginning, one or more OSPF routing processes must be enabled on the router, followed by configuration that defines which interfaces are involved in OSPF routing. Details will be described in the following lessons. Once all the required information is defined and basic OSPF configuration is applied, an implementation plan showing the following tasks is required to configure the NBMA-specific configuration: Manual configuration of the neighbors Definition of the OSPF network type
3-60
Nonbroadcast Mode Operation

Neighbors must be statically configured The OSPF network type must be defined

Use this command to statically define neighbor relationships in an NBMA network.

This command defines the OSPF non-broadcast network type.
ROUTE v1. 0 3-15
To configure Open Shortest Path First (OSPF) routers interconnecting to nonbroadcast networks, use the neighbor (OSPF) command in router configuration mode. Adjacent relationships must be statically defined in NBMA networks using the nonbroadcast mode. One neighbor entry must be included in the Cisco IOS Software configuration for each known nonbroadcast network neighbor and the neighbor address must be on the primary address of the interface.
Note You cannot use the neighbor (OSPF) command to specify an OSPF neighbor on nonbroadcast networks within an OSPF Virtual Private Network (VPN) routing instance.
The neighbor 192.168.1.2 priority 0 command in the figure in this slide shows the configuration where the priority 0 optional keyword is used. A number indicates the router priority value of the nonbroadcast neighbor associated with the IP address specified. The default value is 0. If this value is used, then the specified neighbor cannot become DR or BDR. Additionally, an OSPF network type must be defined. To configure the OSPF network type to a type other than the default for a given medium, use the ip ospf network command in the interface configuration mode. The ip ospf network non-broadcast command in the figure shows that network type selected is NBMA. For more details about the neighbor (OSPF) and ip ospf network commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-61
NBMA Configuration Example
ROUTE v1. 0 3-16
Example: NBMA Configuration Example

This figure illustrates an example of statically defined adjacencies and the configuration of a nonbroadcast OSPF network type. All three routers are using the default nonbroadcast mode on their Frame Relay interfaces; therefore, each must manually configure its neighboring routers. The priority should be set to 0 for routers R2 and R3, because a full-mesh topology does not exist. This configuration ensures that router R1 becomes the DR because only router R1 has full connectivity to the other two routers. No BDR will be elected in this case.
Note The default priority on the neighbor command is 0. Setting the OSPF priority to 0 at the interface level on routers R2 and R3 did result in a priority of 0 and the routers not being elected as DR or BDR.
In an NBMA network, neighbor statements are required only on the DR and BDR. In a huband-spoke topology, neighbor statements must be used on the hub, which must be configured to become the DR. Neighbor statements are not mandatory on the spoke routers. In a full-mesh NBMA topology, you may need neighbor statements on all routers unless you have statically configured the DR and BDR using the priority command.
3-62
The show ip ospf neighbor Command
ROUTE v1. 0 3-17
To display OSPF neighbor information on a per-interface basis, you must use the show ip ospf neighbor command. This table describes the output of the show ip ospf neighbor command:
Field Description Neighbor router ID Router priority of the neighbor Neighbor state Expected time before Cisco IOS software will declare the neighbor dead IP address of the interface Local interface to reach the neighbor
Example: show ip ospf neighbor Command Router R1 in the figure has a serial Frame Relay NBMA interface and a Fast Ethernet interface. The serial 0/0/0 interface on this router has two neighbors; both show a state of FULL/DROTHER. DROTHER means that the neighboring router is not a DR or BDR (because router R1 is the DR and there is no BDR in this network). The neighbor learned on FastEthernet 0/0 shows a state of FULL/BDR, which means that it has successfully exchanged LSDB information with the router issuing the show command, and that it is the BDR. For more details about show ip ospf neighbor command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-63
Using Sub-Interfaces in OSPF over Frame Relay

This topic describes how to configure a physical interface into multiple subinterfaces.
Using Subinterfaces
Several logical subinterfaces can be created over all multiaccess WAN networks: point-to-point multipoint Each subinterface requires an IP subnet. Logical interfaces behave in exactly the same way as physical interfaces for routing purposes Statistics and traffic shaping behavior differs between interfaces and subinterfaces
ROUTE v1. 0 3-18
A physical interface can be split into multiple logical interfaces, called subinterfaces. Each subinterface is defined as a point-to-point or a point-to-multipoint interface. Subinterfaces were originally created to better handle issues caused by split horizon over an NBMA for distancevector-based routing protocols. Each subinterface requires an IP subnet. Logical interfaces behave in exactly the same way as physical interfaces for routing purposes. Statistics and traffic shaping behavior differs between interfaces and subinterfaces. During the configuration of subinterfaces, you must choose the point-to-point or multipoint keywords. The choice of modes affects the operation of OSPF. The default OSPF mode on a point-to-point Frame Relay subinterface is the point-to-point mode; the default OSPF mode on a Frame Relay point-to-multipoint subinterface is the nonbroadcast mode. The default OSPF mode on a main Frame Relay interface is also the nonbroadcast mode. The following topics will describe point-to-point and multipoint subinterfaces and their use in the OSPF NBMA mode.
3-64
Point-to-Point Subinterfaces
Each PVC gets its own subinterface. PVCs are treated like point-to-point links. Each subinterface requires a subnet. OSPF point-to-point mode is the default. DR and BDR are not used. You do not need to configure neighbors.

This shows how to configure a point-to-point subinterface.
ROUTE v1. 0 3-19
When point-to-point subinterfaces are configured, each permanent virtual circuit (PVC) gets its own subinterface, and PVCs are treated like point-to-point links. A point-to-point subinterface has the properties of any physical point-to-point interface and requires its own subnet. There is no DR or BDR election process. Neighbor discovery is automatic, so neighbors do not need to be configured. To configure the point-to-point interface, you must select the point-to-point keyword during subinterface configuration, as shown on the figure in this slide.
3-65
Point-to-Point Subinterface Example
ROUTE v1. 0 3-20
Example: Point-to-Point Subinterface

Point-to-point mode is used when only two nodes exist; this mode is typically used only with point-to-point subinterfaces. Each point-to-point connection is one IP subnet. An adjacency forms over the point-to-point network with no DR or BDR election. In the figure, the router R1 serial 0/0/0 interface is configured with point-to-point subinterfaces. Although all three routers have only one physical serial port, router R1 appears to have two logical ports. Each logical port (subinterface) has its own IP address and operates as a point-topoint OSPF network type. This type of configuration avoids the need for a DR or BDR and removes the requirement to define the neighbors statically.
3-66
Multipoint Subinterfaces
Multiple PVCs are on a single subinterface. Each subinterface requires a subnet. OSPF nonbroadcast mode is the default. The DR is used. Neighbors need to be statically configured.

This shows how to configure a multipoint subinterface.
ROUTE v1. 0 3-21
When multipoint subinterfaces are configured, there are multiple permanent virtual circuits (PVCs) on a single subinterface. Each subinterface requires a subnet. Multipoint Frame Relay subinterfaces default to OSPF nonbroadcast mode, which requires neighbors to be statically configured and performs a DR and BDR election. To configure the multipoint interface, you must select the multipoint keyword during subinterface configuration, as shown in the figure in this slide.
3-67
Multipoint Subinterface Example
ROUTE v1. 0 3-22
Example: Multipoint Subinterface

In this figure, router R1 has one single interface, serial 0/0/0, which has been logically separated into two subinterfaces: one point-to-point (S0/0/0.1) and one point-to-multipoint (S0/0/0.2). The multipoint subinterface supports two other routers in a single subnet. Each subinterface requires a subnet. On a multipoint interface, neighbors are statically defined. OSPF defaults to point-to-point mode on the point-to-point subinterface. OSPF defaults to nonbroadcast mode on the point-to-multipoint interface.
3-68
Implementing OSPF over a Point-to-Point Frame Relay Network

This topic describes how to configure a point-to-point topology in an OSPF over Frame Relay network.
Point-to-Point Mode
Leased-line emulation Automatic configuration of adjacency DR is not used Only a single subnet is used
ROUTE v1. 0 3-23
Networks in point-to-point mode are designed to emulate leased-line networks. This is a Cisco proprietary mode. Because they are treated as point-to-point links, the DR and BDR are not used, and the adjacency forms over the point-to-point network with no DR or BDR election. Only a single subnet is used per point-to-point link.
3-69
Point-to-Point Configuration Example
ROUTE v1. 0 3-24
Example: Point-to-Point Configuration

This figure shows partial configuration of routers R1 and R2 in point-to-point mode. This configuration does not require subinterfaces and uses only a single subnet. In point-to-point mode, a DR or BDR is not used; therefore, DR and BDR election and priorities are not a concern. For more details about the ip ospf network command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-70
Point-to-Point Verification Example
ROUTE v1. 0 3-25
The show ip ospf interface command displays key OSPF details for each interface. The OSPF network type, area number, cost, and state of the interface are all displayed. The hello interval for a point-to-multipoint interface is 30 seconds, with a dead interval of 120 seconds. The point-to-point and broadcast modes default to a 10-second hello timer. The hello and dead timers on the neighboring interfaces must match in order for the neighbors to form successful adjacencies. The listed adjacent neighboring routers are all dynamically learned. Manual configuration of neighboring routers is not necessary. For more details about the show ip ospf interface commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-71
Implementing OSPF over a Point-to-Multipoint Frame Relay Network

This topic describes how to configure a point-to-multipoint topology and point-to-multipoint nonbroadcast topologies in an OSPF over Frame Relay network.
Point-to-Multipoint Mode
Fixes partial-mesh and star topologies Automatic configuration of adjacency DR is not used Only a single subnet is used
ROUTE v1. 0 3-26
Networks in point-to-multipoint mode are designed to work with partial-mesh or star topologies. With RFC 2328-compliant point-to-multipoint mode, OSPF treats all router-torouter connections over the nonbroadcast network as if they were point-to-point links. In pointto-multipoint mode, DRs are not used, and a type 2 LSA (as described in the next lesson) is not flooded to adjacent routers. Instead, OSPF point-to-multipoint works by exchanging additional LSUs that are designed to automatically discover neighboring routers and add them to the neighbor table. In large networks, using point-to-multipoint mode reduces the number of PVCs required for complete connectivity, because you are not required to have a full-mesh topology. In addition, not having a full-mesh topology reduces the number of neighbor entries in the neighbor table. Point-to-multipoint mode has the following properties: Does not require a fully meshed network: This environment allows routing to occur between two routers that are not directly connected but are connected through a router that has virtual circuits to each of the two routers. All three routers connected to the Frame Relay network in the figure can be configured for point-to-multipoint mode. Does not require a static neighbor configuration: In nonbroadcast mode, neighboring routers are statically defined to start the DR election process and allow the exchange of routing updates. Because the point-to-multipoint mode treats the network as a collection of point-to-point links, multicast hello packets discover neighboring routers dynamically. Statically configuring neighboring routers is not necessary.
3-72
Uses one IP subnet: As in nonbroadcast mode, when you are using point-to-multipoint mode, all routers are on one IP subnet. Duplicates LSA packets: Also as in nonbroadcast mode, when flooding out a nonbroadcast interface in point-to-multipoint mode, the router must replicate the LSU. The LSU packet is sent to each of the neighboring routers of the interface, as defined in the neighbor table.
3-73
Point-to-Multipoint Configuration Example
ROUTE v1. 0 3-27
Example: Point-to-Multipoint Configuration

This figure shows partial configurations of routers R1 and R2 in point-to-multipoint mode. This configuration does not require subinterfaces and uses only a single subnet. In point-to-multipoint mode, a DR or BDR is not used; therefore, DR and BDR election and priorities are not a concern.
3-74
Point-to-Multipoint Verification Example
ROUTE v1. 0 3-28
The show ip ospf interface command displays key OSPF details for each interface. The OSPF network type, area number, cost, and state of the interface are all displayed. The hello interval for a point-to-multipoint interface is 30 seconds, with a dead interval of 120 seconds. The point-to-multipoint and the nonbroadcast modes default to a 30-second hello timer, while the point-to-point and broadcast modes default to a 10-second hello timer. The hello and dead timers on the neighboring interfaces must match in order for the neighbors to form successful adjacencies. The listed adjacent neighboring routers are all dynamically learned. Manual configuration of neighboring routers is not necessary. For more details about the show ip ospf interface command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-75
Point-to-Multipoint Nonbroadcast
Cisco extension to the RFC-compliant point-to-multipoint mode Must manually define neighborsas with NBMA mode DR, BDR not usedas with point-to-multipoint mode Used in special cases where neighbors cannot be automatically discovered Example: Virtual circuits without multicast and broadcast enabled

Defines the OSPF network type
ROUTE v1. 0 3-29
Cisco defines additional modes for the OSPF neighbor relationship, including point-tomultipoint nonbroadcast. This mode is a Cisco extension of the RFC-compliant point-tomultipoint mode. You must statically define neighbors, and you can modify the cost of the link to the neighboring router to reflect the different bandwidths of each link. The RFC point-tomultipoint mode was developed to support underlying point-to-multipoint virtual circuits that support multicast and broadcast; therefore, this mode allows dynamic neighboring router discovery. For this reason, no DR or BDR is used. This mode is used in special cases where neighbors cannot be automatically discovered. If, for example, multicast and broadcast are not enabled on the virtual circuits, the RFC-compliant point-to-multipoint mode cannot be used, because the router cannot dynamically discover its neighboring routers using the hello multicast packets; this Cisco mode should be used instead. To define point-to-multipoint nonbroadcast mode, you must use the ip ospf network point-tomultipoint non-broadcast command in an interface configuration mode, as shown on the figure in this slide.
3-76
OSPF over NBMA Topology Summary

OSPF Mode NBMA Preferred Topology Full- or partialmesh Full- or partialmesh Partial-mesh or star Partial-mesh or star Partial-mesh or star, using subinterface Subnet Address Hello Timer 10 s ec Adjacency Automatic, DR/BDR elected Manual configuration, DR/BDR elected Automatic, no DR/BDR Manual configuration, no DR or BDR Automatic, no DR or BDR RFC or Cisco Cisco
Broadcast
Same
Nonbroadcast (NBMA) Point-tomultipoint Point-tomultipoint nonbroadcast Point-to-point
Same
30 s ec
RFC
Same
30 s ec
RFC
Same
30 s ec
Cisco
Different for each subinterface
10 s ec
Cisco
ROUTE v1. 0 3-30
Example: OSPF over NBMA Topology Summary

The figure provides a concise comparison of the various modes of operation for OSPF over NBMA topologies.
3-77
Summary
Summary
OSPF defines three types of networks: point-to-point, broadcast, and NBMA. On point-to-point links, the adjacency is dynamic, uses multicast addresses, and has no DR or BDR. On broadcast links, the adjacency is dynamic and includes election of a DR and BDR. All updates are sent to the DR, which forwards the updates to all routers. OSPF over Metro Ethernet and EoMPLS requires no changes to the OSPF configuration from the customer perspective. OSPF over MPLS VPN requires the customer routers to run OSPF and exchange routing updates with the PE routers. The router with the highest OSPF priority is selected as the DR. The router with the second-highest priority value is selected as the BDR.
2009 Cis co S yst em s, Inc. A ll rights reserved. ROUTE v1. 0 3-31
Summary (Cont.)
The OSPF mode of operation on Frame Relay depends on the underlying Frame Relay network. OSPF mode options include nonbroadcast, broadcast, point-to-multipoint, point-to-multipoint nonbroadcast, and point-to-point. By default on NBMA links, adjacency requires the manual definition of neighbors for the DR and BDR, because OSPF will consider the network similar to broadcast media. A physical interface can be split into multiple logical interfaces called subinterfaces. Each subinterface requires an IP subnet. With point-to-point mode, leased line is emulated, the adjacency is automatically configured, and no DR is required. In point-to-multipoint mode, no DR or BDR is needed and neighbors are automatically discovered. In point-to-multipoint nonbroadcast mode, no DR or BDR is needed, but neighbors must be statically configured.
3-78
Lesson 4
Configuring and Verifying OSPF Routing

Overview
This lesson discusses the primary configuration commands for a single-area and multiarea Open Shortest Path First protocol (OSPF) design and how to configure the router OSPF and network commands. The network command for OSPF requires a special inverse mask that is defined in this lesson. For verification, several OSPF show commands are described in this lesson, introducing the OSPF verification process together with a description of the link state database (LSDB) and details about link state advertisements (LSAs). OSPF has some design limitations and solutions such as virtual links, passive interface command, and changing the cost metric are described.
Objectives
Upon completing this lesson, you will be able to explain how to configure OSPF single-area and multiarea routing, and also explain how to configure several advanced features. This ability includes being able to meet these objectives: Initialize single-area and multiarea OSPF Activate OSPF within a router in single-area and multiarea Define the router ID Verify OSPF operations Identify LSA types within the LSDB Limit adjacencies in OSPF with the passive-interface command Define the design limitations of OSPF Define OSPF virtual links and solve the non-contiguous area problem Change the cost metric
Initializing Single-Area and Multiarea OSPF

This topic describes the procedure to configure single-area and multiarea OSPF and the differences between the two.
Initializing Single-Area and Multiarea OSPF
ROUTE v1.03-2
Single area design in OSPF put all routers into a single OSPF area. This results in many updates being processed on every router and in larger routing tables. The OSPF configuration follows a single area design, in which all of the routers are treated as being internal routers to the area and all of the interfaces are members of that single area. The best design should use a single area as the backbone area. Multiarea design is a better solution than single-area design. In a multiarea design, the network is segmented to limit the propagation of LSAs and to make routing tables smaller. There are two types of routers, from the configuration point of view: Routers with single-area configuration: internal routers, backbone routers, autonomous system border routers residing in one area Routers with a multiarea configuration: area border routers and autonomous system border routers residing in more than one area
3-80
Planning for OSPF

Assess the requirements and options: Contiguous IP addressing plan Network topology with multiple areas Define different area types, ABRs, and ASBRs Define summarization and redistribution points Create an implementation plan Configure the OSPF
ROUTE v1.03-3
The type of OSPF routing protocol implementation you should choose depends on your specific needs and topology. When you prepare to deploy OSPF routing in a network, you must first gather the existing state and requirements, and then consider different deployment options: The IP addressing plan governs how OSPF can be deployed and how well the OSPF deployment might scale. Thus, a detailed IP addressing plan, along with the IP subnetting information, must be created. A solid IP addressing plan should enable usage of OSPF area design and summarization, to more easily scale the network, as well as optimize OSPF behavior and propagation of Link State Advertisements (LSAs). The network topology consists of links that connect the network equipment (routers, switches, and so on) and belong to different OSPF areas in a multiarea OSPF design. A detailed network topology plan should be presented in order to assess the OSPF scalability requirements and to determine the different OSPF areas, area border routers (ABRs), and autonomous system border routers (ASBRs), as well as summarization and redistribution points. An implementation plan must be created prior to the configuration of OSPF routing in the network.
3-81
Activating OSPF within a Router in Single-Area and Multiarea

This topic describes the two-step process to configure basic single-area and multiarea OSPF.
Steps to Configure Basic OSPF

Configure OSPF routing processes on every OSPF router Define one or more processes globally on the router Define the interfaces that OSPF will run on
Or
Enable OSPF explicitly on an interface
ROUTE v1.03-4
Once you have gathered all of the required information, you must create an implementation plan showing the following tasks to perform basic OSPF configuration: Define one or more OSPF processes globally on the router. Define the interfaces that OSPF will run on. The basic OSPF configuration can be applied directly on the router interface as well. In this case, there is just one step, which enables OSPF on an interface and assigns the interface to the desired OSPF area: Enable OSPF explicitly on an interface
3-82
Configuring OSPF for Multiple Areas
ROUTE v1.03-5
To configure the OSPF process, complete the following steps: Enable the OSPF process on the router Identify which interfaces on the router are part of the OSPF process To configure an OSPF routing process, use the router ospf command in global configuration mode, as shown in the figure in the slide. The process-id parameter inside the router ospf command is an internally used identification parameter for the OSPF routing process. It is locally assigned and can be any positive integer. A unique value is assigned for each OSPF routing process in the router. To define the interfaces on which OSPF runs and define the area IDs for those interfaces, use the network area command in router configuration mode, as shown in the figure in the slide. The wildcard-mask parameter in the network area command determines how to interpret the IP address. The mask has wildcard bits, in which 0 is a match and 1 indicates that the value is not significant. For example, 0.0.255.255 indicates a match in the first two octets. Starting with Cisco IOS Release 12.3(11)T (and some specific versions of earlier releases), OSPF can be enabled directly on the interface using the ip ospf area command, which simplifies the configuration of unnumbered interfaces. Because the command is configured explicitly for the interface, it takes precedence over the network area command. The command is shown in the figure in the slide as well. The figure shows the OSPF configuration for Fast Ethernet broadcast networks and serial pointto-point links. Router R1 is in area 0, router R3 is in area 1, and router R2 is the area border router (ABR) between the two areas. Router R1 is configured for OSPF with a process-id value of 1, and a network statement assigns all interfaces defined in the 10.0.0.0 network to OSPF process 1. Router R2 is running OSPF process 50 and has a network statement for area 0. The configuration for area 1 in the example in the slide uses the ip ospf 50 area 1 interface command for serial point-to-point; alternatively, a separate network router configuration command could have been used.
Note
The network statement and wildcard mask are not used for route summarization purposes. The network statement is used strictly to turn OSPF on for an interface or for multiple interfaces.
For more details about the router ospf, network area, and ip ospf area commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-84
Defining the Router ID

For an OSPF routing process to start successfully, it must be able to determine an OSPF router ID. This topic describes how to select the OSPF router ID using the router-id command.
OSPF Router ID
The router is known to OSPF by the router ID number. This router ID is used in LSDBs to differentiate one router from the next. OSPF requires at least one active interface with an IP address. By default, the router ID is: The highest IP address on an active interface at the moment of OSPF process startup. If a loopback interface exists, the router ID is the highest IP address on any active loopback interface. A loopback interface overrides the OSPF router ID. The OSPF router-id command can be used to override the default OSPF router ID selection process. Using a loopback interface or a router-id command is recommended for stability.
The OSPF database uses the OSPF router ID to describe each router in the network uniquely. Remember that every router keeps a complete topology database of all routers and links in an area (or network); therefore, each router should have a unique router ID. The OSPF routing process chooses a router ID for itself when it starts up. The router ID is a unique IP address that can be assigned in the following ways: By default, the highest IP address of any active physical interface when OSPF starts is chosen as the router ID. The interface does not have to be part of the OSPF process, but it has to be up. There must be at least one IP interface that is up on the router for OSPF to use as a router ID. If no interface is up and available with an IP address when the OSPF process starts, the following error message occurs:

If there is a loopback interface, its address will always be preferred as the router ID over of a physical interface address, because a loopback interface never goes down. If there is more than one loopback interface, then the highest IP address on any active loopback interface becomes the router ID. Using the router-id command is the preferred procedure to set the router ID and is always used in preference to the other two procedures. Once the OSPF router ID is set, it does not change, even if the interface that the router is using for the router ID goes down. The OSPF router ID changes only if the router reloads or if the OSPF routing process restarts.
Configuration of Loopback Interfaces

OSPF is running and the new loopback takes effect in either of these two situations:
When the router is reloaded When the OSPF process is removed and reconfigured
ROUTE v1.03-7
To modify the OSPF router ID to a loopback address, first define a loopback interface as follows:

Configuring an IP address on a loopback interface overrides the highest IP address being used as the router ID. OSPF is more reliable if a loopback interface is configured, because the interface is always active and cannot fail, as opposed to a real interface. For this reason, you should use a loopback address on all key routers. If the loopback address is advertised with the network command, then this address can be pinged for testing purposes. A private IP address can be used to save registered public IP addresses.
Note A loopback address requires a different subnet for each router, unless the host address itself is advertised. By default, OSPF advertises loopback addresses as /32 host routes.
If the OSPF process is already running, the router must be reloaded or the OSPF process must be removed and reconfigured before the new loopback address will take effect.
3-86
Setting OSPF Router ID

This OSPF routing process configuration command changes the OSPF router ID. The 32-bit number in the IP address format is used. This must be configured before the OSPF process, otherwise the OSPF process needs to be restarted or the router must be reloaded.

This is the command for a manual OSPF process restart.
ROUTE v1.03-8
Use the OSPF router-id command in router configuration mode to ensure that OSPF uses a specific router ID. The ip-address parameter can be any unique, arbitrary 32-bit value in an IP address dotted-decimal format. After the router-id command is configured, use the clear ip ospf process command. This command restarts the OSPF routing process so that it will reselect the new IP address as its router ID.
Caution The clear ip ospf process command will temporarily disrupt an operational network.
Note
Router IDs must be unique throughout the autonomous system (AS), no matter how they are configured.
For more details about the router-id and clear ip ospf commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-87
OSPF Router ID Verification

ROUTE v1.03-9
You can use the show ip ospf command to verify the OSPF router ID. This command also displays OSPF timer settings and other statistics, including the number of times the shortest path first (SPF) algorithm has been executed. This command also has optional parameters so that you can further specify the information to be displayed. The figure shows partial output from this command on router R2 in the last example; router R2 is an ABR. The full output is as follows:

For more details about the show ip ospf command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-89
Verify OSPF Operations

This topic describes how to configure a default route injection into OSPF.
Steps to Verify Basic OSPF

Verify OSPF routing protocol Verify OSPF interface information Verify OSPF neighbors Verify OSPF routes learned by the router in the IP routing table Verify configured IP routing protocol processes Verify OSPF link state database (LSDB)
ROUTE v1. 0 3-10
Once the basic OSPF is configured, you can use several verification commands to verify its operation. One of the first verification steps is to verify the presence of the OSPF routing process. If the OSPF process has been configured successfully, there must be an OSPF router inside the IP routing table. Additionally you can verify the OSPF interfaces, routing process neighbors, and database.
3-90
Example: The show ip ospf Command

This command displays the OSPF router ID, timers, and statistics.

You can use the show ip ospf command to display general information about Open Shortest Path First (OSPF) routing processes. As shown in the last topic, the show ip ospf command displays the OSPF router ID, OSPF timers, the number of times the SPF algorithm has been executed, and link-state advertisement (LSA) information. For more details about the show ip ospf command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-91
Example: The show ip ospf interface Command

This command displays the OSPF router ID, area ID, and adjacency information.

The show ip ospf interface command displays OSPF-related interface information. You can use this command to verify that interfaces are configured in the intended areas. In addition, this command displays the timer intervals (including the hello interval) and shows the neighbor adjacencies. The command output in the figure in the slide is from router R2 from the last configuration example. The output details the OSPF status of the FastEthernet 0/0 interface. You can use the output to verify that OSPF is running on this interface, and what OSPF area the interface is in. This command also displays other information, such as the OSPF process ID, the OSPF router ID, the OSPF network type, the designated router (DR) and backup designated router (BDR), timers, and neighbor adjacency. For more details about the show ip ospf interface command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-92
Example: The show ip ospf neighbor Command

This command displays information about the OSPF neighbors, including the DR and BDR information.

ROUTE v1. 0 3-13
One of the most important OSPF verification and troubleshooting commands is the show ip ospf neighbor command. OSPF does not send or receive updates without having full adjacencies between neighbors. The show ip ospf neighbor command displays a list of neighbors, including their OSPF router IDs, their OSPF priorities, their neighbor adjacency states (for example, INIT, exstart, or full), and their dead timers. In the first output in the slide, router R2 (from the last configuration example) has two neighbors. The first entry in the table represents the adjacency formed on the Fast Ethernet interface. A FULL state means that the link-state database (LSDB) has been exchanged successfully. The DR entry means that a router is the designated router. The second line in the table represents the neighbor of router R2 on the serial interface. DR and BDR are not used on point-to-point interfaces (indicated by a dash []). The second output in the figure shows partial output of the show ip ospf neighbor detail command output, providing details of the neighbors of router R2. The full output is as follows:

For more details about the show ip ospf neighbor and show ip ospf neighbor detail commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-94
Example: The show ip route ospf Command

This command displays all OSPF routes learned by the router.

ROUTE v1. 0 3-14
Use the show ip route ospf command to verify the OSPF routes in the IP routing table known to the router. This command is one of the best ways to determine connectivity between the local router and the rest of the internetwork. This command also has optional parameters so that you can further specify the information to be displayed, including the OSPF process ID. The O code represents OSPF routes, and IA means interarea. In the figure, the 10.2.1.0 subnet is recognized on FastEthernet 0/0 via neighbor 10.64.0.2. The entry [110/65] in the routing table represents the administrative distance assigned to OSPF (110), and the total cost of the route to subnet 10.2.1.0 (cost of 65). For more details about the show ip route ospf command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-95
Example: The show ip protocols Command

This command verifies the configured IP routing protocol processes, parameters, and statistics.

ROUTE v1. 0 3-15
You can use the show ip protocols command to verify the OSPF routing protocol parameters about timers, filters, metrics, networks, and other information for the entire router. The command output in the slide shows that the OSPF routing protocol with process number 1 is configured. The router-id of the router is 10.64.0.1, and it belongs to area 0. For more details about the show ip protocols command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-96
Identifying LSA Types within the LSDB

LSAs are the building blocks of the OSPF LSDB. Individually, they act as database records; in combination, they describe the entire topology of an OSPF network or area. This topic describes the LSAs defined by OSPF.
LSA Types
LSA Type 1 2 3 or 4 5 6 7 8 9, 10, 11
Description Router LSAs Network LSAs Summary LSAs Autonomous system external LSAs Multicast OSPF LSAs LSAs defined for not-so-stubby areas External attribute LSAs for Border Gateway Protocol (BGP) Opaque LSAs
ROUTE v1. 0 3-16
The following are descriptions of each type of LSA. LSA types 1 through 5 and 7 are explained in more detail in the following pages.
Type 1
Every router generates router link advertisements for each area to which it belongs. Router link advertisements describe the state of the routers links to the area, and are flooded only within that particular area. For all types of LSAs, there are 20-byte LSA headers. One of the fields of the LSA header is the link-state ID. The link-state ID of the type 1 LSA is the originating router ID.
Type 2
DRs generate network link advertisements for multiaccess networks that describe the set of routers 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.
Types 3 and 4
ABRs generate summary link advertisements. Summary link advertisements describe the following interarea routes: Type 3 describes routes to networks and aggregates routes.
Type 4 describes routes to ASBRs. The link-state ID is the destination network number for type 3 LSAs and the router ID of the described ASBR for type 4 LSAs. These LSAs are flooded throughout the backbone area to the other ABRs. The link entries are not flooded into totally stubby areas or not-so-stubby areas (NSSAs).
Type 5
ASBRs generate AS external link advertisements. External link advertisements describe routes to destinations external to the AS and are flooded everywhere with the exception of stub areas, totally stubby areas, and NSSAs. The link-state ID of the type 5 LSA is the external network number.
Type 6
Type 6 LSAs are specialized LSAs that are used in multicast OSPF applications.
Type 7
Type 7 LSAs are used in NSSAs for external routes.
Type 8
Type 8 LSAs are specialized LSAs that are used in internetworking OSPF and Border Gateway Protocol (BGP).
Types 9, 10, and 11

The opaque LSAs, types 9, 10, and 11, are designated for future upgrades to OSPF for application-specific purposes. For example, Cisco Systems uses opaque LSAs for Multiprotocol Label Switching (MPLS) with OSPF. Standard LSDB flooding mechanisms are used for distribution of opaque LSAs. Each of the three types has a different flooding scope.
3-98
LSA Type 1: Router LSA

One router LSA for every router in an area (intra-area) Includes a list of directly attached links Links identified by the IP prefix and link type LSA identified by the router ID of the originating router Floods within its area only; does not cross an ABR
ROUTE v1. 0 3-17
A router advertises a type 1 LSA that floods to all other routers in the area in which it originated. A type 1 LSA describes the collective states of the directly connected links (interfaces) of the router. Each type 1 LSA is identified by the router ID. Each router link is defined as one of four link types: type 1, 2, 3, or 4. The LSA includes a link ID field that identifies, by the network number and mask, the object to which this link connects.
LSA Type 1 Link Types

Depending on the type, the link ID has different meanings, as described in the table.
Link Type 1 Description Point-to-point connection to another router Connection to a transit network Link ID Neighboring router ID
IP address of DR
3 4
Connection to a stub network Virtual link
IP network or subnet number Neighboring router ID
A stub network is a dead-end link that has only one router attached. In addition, the type 1 LSA describes whether the router is an ABR or ASBR.
3-99
LSA Type 2: Network LSA

One network LSA for each transit broadcast or NBMA network in an area (intra-area) Includes a list of attached routers on the transit link Includes a subnet mask of the link Advertised by the DR of the broadcast network Floods within its area only; does not cross an ABR
ROUTE v1. 0 3-18
A type 2 LSA is generated for every transit broadcast or nonbroadcast multiaccess (NBMA) network within an area. A transit network has at least two directly attached OSPF routers. A multiaccess network like Ethernet is an example of a transit network. 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 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 link-state ID for a network LSA is the IP interface address of the DR that advertises it.
3-100
LSA Type 3: Summary LSA

Used to flood network information to areas outside the originating area (interarea) Describes the network number and mask of the link Advertised by the ABR of the originating area, regenerated by all subsequent ABRs to flood throughout the AS Advertised for every subnet and not summarized, by default
ROUTE v1. 0 3-19
The ABR sends type 3 summary LSAs. Type 3 LSAs advertise any networks owned by an area to the rest of the areas in the OSPF AS, as shown in the figure. The link-state ID is set to the network number; the mask is also advertised. By default, OSPF does not automatically summarize groups of contiguous subnets, nor does it summarize a network to its classful boundary. The network operator, through configuration commands, must specify how the summarization will occur. By default, a type 3 LSA is advertised into the backbone area for every subnet defined in the originating area, which can cause significant flooding problems. Consequently, you should always consider using manual route summarization at the ABR. Summary LSAs are flooded throughout a single area only, but are regenerated by ABRs to flood into other areas.
Note By default, summary LSAs do not contain summarized routes.
3-101
LSA Type 4: ASBR Summary LSA

Used to advertise a metric to the ASBR, which is used for path selection Generated by the ABR of the originating area Regenerated by all subsequent ABRs to flood throughout the AS Contain the router ID of the ASBR
ROUTE v1. 0 3-20
A type 4 summary LSA is generated by an ABR only when an ASBR exists within an area. A type 4 LSA identifies the ASBR and provides a route to it. The link-state ID is set to the ASBR router ID. All traffic destined to an external AS requires routing table knowledge of the ASBR that originated the external routes.
Example: LSA Type 4ASBR Summary LSA

In the figure, the ASBR sends a type 1 router LSA with a bit (known as the external bit [e bit]) that is set to identify itself as an ASBR. When the ABR (identified with the border bit [b bit] in the router LSA) receives this type 1 LSA, it builds a type 4 LSA and floods it to the backbone, area 0. Subsequent ABRs regenerate a type 4 LSA to flood into their areas.
3-102
LSA Type 5: External LSA

Used to advertise networks from other ASs Advertised and owned by the originating ASBR Flooded throughout the entire AS The advertising router ID (ASBR) is unchanged throughout the AS A type 4 LSA is needed to find the ASBR By default, routes are not summarized
ROUTE v1. 0 3-21
Type 5 external LSAs describe routes to networks outside the OSPF AS. Type 5 LSAs are originated by the ASBR and are flooded to the entire AS. The link-state ID is the external network number. Because of the flooding scope and depending on the number of external networks, the default lack of route summarization can also be a major issue with external LSAs. Therefore, you should always attempt to summarize blocks of external network numbers at the ASBR to reduce flooding problems.
3-103
LSA Type 7: NSSA External LSA

Used to advertise networks from other ASs injected into the NSSA. Have the same format as a type 5 external LSA Advertised and owned by the originating ASBR Translated to LSA type 5 on first NSSA subsequent ABR By default, routes are not summarized
ROUTE v1. 0 3-22
Type 7 external LSAs describe routes to networks outside the OSPF AS. Redistribution from an external autonomous system into an NSSA area creates this special LSA type 7, which can only exist in an NSSA area. An NSSA autonomous system boundary router (ASBR) generates this LSA and an NSSA area border router (ABR) translates it into a type 5 LSA, which gets propagated into the OSPF domain to all areas that can support Type 5 LSAs. Routers operating NSSA areas set the N-bit to signify that they can support type 7 NSSAs. These option bits must be checked during neighbor establishment. They must match for an adjacency to form. The link-state ID is the external network number. Because of the flooding scope and depending on the number of external networks, the default lack of route summarization can also be a major issue with external LSAs. Therefore, you should always attempt to summarize blocks of external network numbers at the ASBR to reduce flooding problems. The advertising router is set to the router ID of the router that injected the external route into OSPFa router inside this NSSA area. This address is also set as the Forward Address for this prefix; the address used to determine the path to take towards this external destination.
3-104
Example of Different LSAs

Note: Only one example of each LSA type exchange is demonstrated in this graphic.
ROUTE v1. 0 3-23
Example: Types of Link State Advertisements (LSAs)

Link-state advertisements are packets that OSPF uses to advertise changes in the condition of a specific link to other OSPF routers. There are various types of link-state packets used by OSPF, each of which is generated for a different purpose and flooded in the network. The following are the different types of LSA packets that can be generated by the source router and entered into the destination router's LSA database. Type 1: Router link LSAs: Router LSAs are generated by each router for each area it is in. The link-state ID is the originating router's ID. Type 2: Intra-area network link LSAs: Network LSAs are generated by designated routers (DRs). The link-state ID is the IP interface address of the DR. Type 3: Network summary LSAs for ABRs: Summary LSAs are generated by ABRs. The link-state ID is the destination network number. Type 4: ASBR summary LSAs for ASBRs: Summary LSAs are generated by ABRs. The link-state ID is the router ID of the described ASBR. Type 5: Autonomous System External LSAs: Type 5 LSAs are generated by the ASBRs. The link-state ID is the external network number. Type 7: Not-So-Stubby Area External LSAs: Type 7 LSAs are generated by ASBRs.
3-105
Note
OSPF has more LSAs. Types 9, 10, and 11 (Opaque LSAs) may be used for distributing application-specific information through an OSPF domain. Type 9 LSAs are not flooded beyond the local network or subnetwork. Type 10 LSAs are not flooded beyond the borders of their associated area. Type 11 LSAs are flooded throughout the AS. The flooding scope of type 11 LSAs is equivalent to that of AS-external (type 5) LSAs. Cisco MPLS Traffic Engineering (Cisco MPLS TE) functionality has been implemented with type 10 opaque LSAs. For more information about opaque LSAs, please see RFC 2370. Type 8 LSAs are specialized LSAs that are used in internetworking OSPF and Border Gateway Protocol (BGP).
3-106
OSPF LSDB: Intra-Area Routing
ROUTE v1. 0 3-24
The figure in the slide shows the topology that will be used to describe the OSPF link state database (LSDB) for intra-area routing. All routers are configured for OSPF routing and the show ip ospf database command is used to get information about an OSPF LSDB. The router link states presented on the next figure are type 1 and type 2 LSAs, since we are focused on OSPF intra-area database entries.
3-107
OSPF LSDB: Intra-Area Routing (Cont.)

LSA Type 1 from area 0

ROUTE v1. 0 3-25
The figure in the slide illustrates the use of the show ip ospf database command to get information about an OSPF LSDB. The router link states are type 1 LSAs and the net link states are type 2 LSAs. The database columns are as follows: Link ID: This identifies each LSA. ADV router: This shows the address of the advertising router, the source router of the LSA. Age: This shows the maximum age counter in seconds; the maximum configurable age counter is 1 hour, or 3,600 seconds. Seq#: This is the sequence number of the LSA; the number begins at 0x80000001 and increases with each update of the LSA. Checksum: This is the checksum of the individual LSA, which can be used to ensure reliable receipt of that LSA. Link count: This is the total number of directly attached links, which is used only on router LSAs. The link count includes all point-to-point, transit, and stub links. Each point-to-point serial link counts as two; all other links count as one, including Ethernet links. The output in the figure is partial output from an ABRrouter R2. The full command output from this router is as follows:

3-108
For more details about the show ip ospf database command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-109
OSPF LSDB: Interarea Routing

ROUTE v1. 0 3-26
The figure in the slide presents the topology that will be used to describe the OSPF link state database (LSDB) for inter-area routing. All routers are configured for OSPF routing and the show ip ospf database command is used to get information about an OSPF LSDB. The router link states presented on the next figure are type 1 and type 3 LSAs.
3-110
OSPF LSDB: Interarea Routing (Cont.)


LSA Type 3
for area 0

LSA Type 3
for area 1
ROUTE v1. 0 3-27
The figure in the slide illustrates the use of the show ip ospf database command to get information about an OSPF LSDB. The router link states are type 1 LSAs and the summary net link states are type 3 LSAs. Since router R2 is the ABR, it has the database for both areas that it is connected to. That makes it the best place to see the OSPF database. The output in the figure is the full command output from this router. To advertise routes from one area into another, the ABR creates summary links, which you can see using the show ip ospf database summary command.
3-111
OSPF LSDB: External Routes

ROUTE v1. 0 3-28
The figure in the slide shows the topology that will be used to describe the OSPF link state database (LSDB) for external routes. All routers are configured for OSPF routing and the show ip ospf database command is used to get information about an OSPF LSDB. The router link states presented on the next figure are type 1, type 3, type 4, and type 5 LSAs.
3-112
OSPF LSDB: External Routes (Cont.)


LSA Type 3
for area 0
LSA Type 4 of ASBR from ABR
LSA Type 5 from ASBR

ROUTE v1. 0 3-29
The figure in the slide illustrates the use of the show ip ospf database command to get information about an OSPF LSDB in terms of external routes. The router link states are type 1 LSAs and the summary net link states are type 3 LSAs. Additionally, the autonomous system boundary router (ASBR) creates (type 5) external LSAs to advertise external routes into OSPF. External LSAs are flooded unaltered into all areas. However, the ASBR is not in area 0. Routers in area 0 do not know how to reach the ASBR. To advertise the reachability of an ASBR into other areas, the ABR creates (type 4) ASBR-summary LSAs. The output in the figure is partial output from an ABR: router R2. The full command output from this router is as follows:


3-113
3-114
OSPF LSDB: NSSA


ROUTE v1. 0 3-30
The figure in the slide presents the topology that will be used to describe the OSPF link state database (LSDB) for NSSA routing. All routers are configured for OSPF routing and the show ip ospf database command is used to get information about an OSPF LSDB. The router link states presented on the next figure are type 1, type 3, type 5, and type 7 LSAs.
3-115
OSPF LSDB: NSSA (Cont.)


LSA Type 3
for area 0
LSA Type 7 from ASBR
LSA Type 5 from ABR
ROUTE v1. 0 3-31
The figure in the slide illustrates the use of the show ip ospf database command to get information about an OSPF LSDB for NSSA routing. The router link states are type 1 LSAs and the summary net link states are type 3 LSAs and both are used to advertise routes from one area into another. To advertise external routes into an NSSA, the autonomous system boundary router (ASBR) also creates NSSA external LSAs (type 7). The ABR converts type 7 LSAs into type 5 LSAs, and propagates the type 5 LSAs into normal areas. The ASBR summary LSAs are not needed in this case, because the ABR originates the external LSA and the ABR is reachable within area 0. You can compare this example with a scenario in which the NSSA is a normal area by looking at the previous database example. The output in the figure is partial output from an ABR: router R2. The full command output from this router is as follows:

3-116
3-117
OSPF LSDB: Virtual Link


ROUTE v1. 0 3-32
The figure in the slide presents the topology that will be used to describe the OSPF link state database (LSDB) when virtual links are configured. All routers are configured for OSPF routing and the show ip ospf database command is used to get information about an OSPF LSDB. The router link states presented in the next figure are type 1 and type 3 LSAs.
3-118
OSPF LSDB: Virtual Link (Cont.)

ROUTE v1. 0 3-33
The figure in the slide illustrates the use of the show ip ospf database command to get information about an OSPF LSDB when virtual links are configured. The router link states are type 1 LSAs and the summary net link states are type 3 LSAs and both are used to advertise routes from one area into another. Notice that LSAs learned through the virtual link have the DoNotAge (DNA) option. The virtual link is treated like a demand circuit. The output in the figure is partial output from router R1. The full command output from this router is as follows:

3-119
Router R3 considers itself an ABR, because it has a link to Area 0 (the virtual link). As a result, it generates a summary LSA for 12.0.0.0 into area 1 and area 0, which you can see when you issue the show ip ospf database summary command on router R3.

3-120
3-121
The show ip route Command

ROUTE v1. 0 3-34
The show ip route command example in this figure depicts both external type routes (O E2) and interarea (O IA) routes. The last entry (O E2) is an external route (from the ASBR, via the ABR). The two numbers in brackets, [110/50], are the administrative distance and the total cost of the route to a specific destination network. In this case, the administrative distance is set to the default of 110 for all OSPF routes, and the total cost of the route has been calculated as 50.
3-122
Interpreting the Routing Table: Types of Routes

Router Designator
OSPF intra-area (router LSA) and network LSA
Description
Networks from within the area of the router Advertised by means of router LSA and the network LSAs Networks from outside the area of the router, but within the OSPF autonomous system Advertised by means of summary LSAs
O IA
OSPF interarea (summary LSA)
O E1 O E2
Type 1 external routes Type 2 external routes
Networks outside of the autonomous system of the router Advertised by means of external LSAs
ROUTE v1. 0 3-35
The figure defines each of the routing table descriptors for OSPF. The router and network LSAs describe the details within an area. The routing table reflects this link-state information with a designation of O, meaning that the route is OSPF intra-area. When an ABR receives summary LSAs, it adds them to its LSDB and regenerates them into the local area. When an ABR receives external LSAs, it adds them to its LSDB and floods them into the area. The internal routers then assimilate the information into their databases. Summary LSAs appear in the routing table as IA (interarea routes). External LSAs appear in the routing table marked as external type 1 (E1) or external type 2 (E2) routes. The SPF algorithm is then run against the LSDB to build the SPF tree. The SPF tree is used to determine the best paths. The order in which the best paths are calculated is as follows: 1. All routers calculate the best paths to destinations within their areas (intra-area) and add these entries to the routing table. These are the type 1 and type 2 LSAs, which are noted in the routing table with a routing designator of O (OSPF intra-area). 2. All routers calculate the best paths to the other areas within the internetwork. These best paths are the interarea route entries, or type 3 and type 4 LSAs, and are noted with a routing designator of O IA (interarea). 3. All routers (except those that are in a form of stub area) calculate the best paths to the external AS (type 5) destinations; these are noted with either an O E1 or an O E2 route designator, depending on the configuration. At this point, a router can communicate with any network within or outside the OSPF AS.
3-123
Calculating Costs for E1 and E2 Routes
ROUTE v1. 0 3-36
The cost of an external route varies depending on the external type configured on the ASBR. 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 AS to avoid suboptimal routing. E2 (default): The external cost of O E2 packet routes is always the external cost only. Use this type if only one ASBR is advertising an external route to the AS. The figure in the slide shows the network diagram with two ASBRs (routers R5 and R6). Both ASBR routers are sending external routes into the OSPF autonomous system. External routes can be sent as E1 or as E2. The router R1 receives the same external routes from routers R2 and R3. In the example in the slide, the path from R1 to R6 is shorter than the path from R1 to R5. If external routes are received as E2 routes (default setting), then the cost is the same regardless of the topology in the OSPF domain, which means there will be suboptimal routing. If external routes are received as E1 routes, then the cost is different, because the internal OSPF cost is added to the external cost. The routing is optimal and the shortest path is selected to the destination.
3-124
OSPF LSDB Overload Protection

Excessive LSAs generated by other routers can drain local router resources. This feature can limit the processing of non-self-generated LSAs for a defined OSPF process. Only a warning message can be sent or neighbors can be ignored.
Limit the number of non-self-generated LSAs.
ROUTE v1. 0 3-37
If other routers are misconfigured, causing, for example, a large number of prefixes to be redistributed, large numbers of LSAs can be generated. These excessive LSAs can drain local CPU and memory resources. OSPF LSDB overload protection can be configured to protect against this issue with Cisco IOS Release 12.3(7)T and later releases (and some specific versions of earlier releases) by using the max-lsa command. When this feature is enabled, the router keeps count of the number of received (non-selfgenerated) LSAs that it keeps in its LSDB. An error message is logged when this number reaches a configured threshold number, and a notification is sent when it exceeds the threshold number. If the LSA count still exceeds the threshold after one minute, the OSPF process takes down all adjacencies and clears the OSPF database; this is called the ignore state. In the ignore state, no OSPF packets are sent or received by interfaces that belong to that OSPF process. The OSPF process remains in the ignore state for the time that is defined by the ignore-time parameter. The ignore-count parameter defines the maximum number of times that the OSPF process can consecutively enter the ignore state before remaining permanently down and requiring manual intervention. If the OSPF process remains normal for the time that is defined by the reset-time parameter, the ignore state counter is reset to 0. For more details about the max-lsa command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-125
Limiting Adjacencies in OSPF with the PassiveInterface Command

This topic describes how routing advertisements can be controlled using the passive-interface command.
OSPF Passive Interface

The sending and receiving of routing updates is disabled. The specified interface address appears as a stub network in the OSPF domain.


ROUTE v1. 0 3-38
To prevent other routers on a local network from learning about routes dynamically, you can keep routing update messages from being sent through a router interface. This feature applies to all IP-based routing protocols except BGP. OSPF behaves somewhat differently. In OSPF, the interface address you specify as passive appears as a stub network in the OSPF domain. OSPF routing information is neither sent nor received through the specified router interface. To disable the sending and receiving of OSPF routing updates on an interface, use the passiveinterface command in router configuration mode. Within ISPs and large enterprise networks, many of the distribution routers have more than 200 interfaces. Thus, a large number of LSAs can be flooded over the domain. The OSPF routing protocol can be configured on all interfaces, and the passive-interface command can be set on the interfaces where adjacency is not desired. In some networks, this means the coding of 100 or more passive interface statements. With the Default Passive Interface feature, this problem is solved by allowing all interfaces to be set as passive by default using a single passive-interface default command, then configuring individual interfaces where adjacencies are desired using the no passive-interface command. In the example in the slide, routers are configured for OSPF routing protocol. The configuration of routers R1 and R2 is observed, where the passive interface feature is configured.
3-126
Router R1 has a set of interfaces that act as a stub network. LSAs are not received through these interfaces anyway and there is no need for LSAs to be sent from there either. The only interface that should participate in OSPF process is interface Serial0/0/1. The passive-interface default command is used on router R1, as it is easier to make all of the interfaces passive and just enable one or more, where OSPF LSAs can be sent and received. In our example in the slide, the no passive-interface Serial0/0/1 command is used to enable the propagation of LSAs on interface Serial0/0/1. Router R2 is slightly different. Only one interface is acting as a stub interface, where the propagation of LSAs should be stopped. The passive-interface Ethernet0 command is stopping the propagation of LSAs through interface Ethernet0 and other interfaces are normally processing OSPF LSAs. For more details about the passive-interface command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-127
Design Limitations of OSPF

This topic describes the effects of using a non-contiguous backbone area, area 0, or area that does not connect to area 0.
Design Limitations of OSPF

If more than one area is configured, one of these areas has be to be area 0, the backbone area. All areas must be connected to area 0. Area 0 must be contiguous.
ROUTE v1. 0 3-39
OSPF has special restrictions when multiple areas are involved throughout the OSPF autonomous system. If more than one area is configured, one of these areas has to be area 0. This is called the backbone area. When designing networks, it is good practice to start from core layer, which becomes area 0, and then expand into other areas later on. The backbone has to be at the center of all other areas and other areas have to be physically connected to the backbone. The main reason is that the OSPF expects all areas to inject routing information into the backbone, which distributes that information into other areas. In the figure in the slide, it is evident that all areas are directly connected to the backbone. In the rare situations in which a new area is introduced that cannot have a direct physical access to the backbone, a solution is required. Virtual links, discussed in the next section, must be configured in such case.
3-128
Virtual Links as a Solution

An extension to the backbone Carried by a nonbackbone area Cannot be created across a stub or NSSA area, or over unnumbered links Are used to: Allow areas to connect to areas other than 0 Repair a discontiguous area 0 (for example, if two companies merge and have separate backbone areas)
ROUTE v1. 0 3-40
OSPF has a solution to extend the reach of the backbone across other areas. This solution is called the virtual link. It provides an extension to the OSPF backbone and allows a router to connect logically to the backbone even though there is no direct physical link. Between the two routers involved in the creation of the virtual-link, there is a non-backbone area. The routers at each end become part of the backbone and both act as ABRs. The virtual link relies on intra-area routing, and its stability is dependent on the stability of the underlying area. Virtual links cannot run through more than one area or over stub areas. They can only run through normal non-backbone areas. If a virtual link needs to be attached to the backbone across two non-backbone areas, then two virtual links are required: one virtual link to serve each area. Virtual links are used for two purposes: Linking an area that does not have a physical connection to the backbone Patching the backbone in case a discontinuity with area 0 occurs A good example of when virtual links might be required is when two companies merge that do not have a direct link between their backbone areas. A similar problem occurs when you add a non-backbone area to an OSPF network and the new area does not have a direct physical connection to the existing OSPF backbone area, area 0.
3-129
OSPF Virtual Links and Solutions to NonContiguous Area Problems

This topic describes OSPF virtual links, which are used to address the non-contiguous area issues, and how to configure these virtual links.
No Direct Physical Connection to Area 0

Area 20 added with no physical access to area 0 A virtual link provides a logical path to the backbone area The OSPF database treats the link between routers ABR1 and ABR2 as a direct link
ROUTE v1. 0 3-41
All areas in an OSPF autonomous system must be physically connected to the backbone area (area 0). When this is not possible, you can use a virtual link to connect to the backbone through a non-backbone area. The area through which you configure the virtual link is known as a transit area and must have full routing information. In the example in the slide, area 20 is added to the existing OSPF topology. Because it has no direct physical link to the backbone area, area 0, a virtual link across non-backbone area 10 is created. In this case, the virtual link provides a logical path between area 20 and the backbone area. The OSPF database treats the virtual link between ABR1 and ABR2 as a direct link. For greater stability, the loopback interface is used as a router ID and virtual links are created using these loopback addresses.
3-130
Discontiguous Area 0
Two companies merge without a direct link between them. Virtual links are used to connect the discontiguous areas 0. A logical link is built between routers ABR1 and ABR2. Virtual links are recommended for backup or temporary connections, too.
ROUTE v1. 0 3-42
The two-tiered area hierarchy of OSPF requires that all areas be directly connect to the backbone area, area 0, and that area 0 be contiguous. A virtual link is a link that allows discontiguous areas 0 to be connected, or that allows a disconnected area to be connected to area 0, via a transit area. The OSPF virtual link feature should be used only in very specific cases, for temporary connections or backup after a failure. Virtual links should not be used as a primary backbone design feature. Virtual links are part of the OSPF open standard and have been a part of Cisco IOS Software since Cisco IOS Release 10.0. In the figure in the slide, area 0 is discontiguous, because the two companies have merged and there is no direct link between their backbone areas. A logical link (virtual link) is built between the two ABRs, routers ABR1 and ABR2. This virtual link is similar to a standard OSPF adjacency. However, in a virtual link, the routers do not have to be directly attached to neighboring routers. The hello protocol works over virtual links as it does over standard links, in 10-second intervals. However, LSA updates work differently on virtual links. An LSA usually refreshes every 30 minutes; 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.
3-131
OSPF Virtual Link Configuration

Configure a virtual link. The router ID of the remote router is used in the command.
ROUTE v1. 0 3-43
You can use the area virtual-link command in router configuration mode, along with any necessary optional parameters, to define an OSPF virtual link. The configuration must be done on both sides of the virtual link and the area virtual-link command on each side must include the router ID of the far-end router. To find the router ID of the far-end router, use the show ip ospf command, show ip ospf interface command, or show ip protocol command on that remote router. In the figure in the slide, two companies have merged, and because there is no direct physical link, area 0 is discontiguous. A virtual link is used as a strategy to temporarily connect the Company 1 and Company 2 backbone areas, areas 0. Area 1 is used as the transit area. Router ABR1 builds a virtual link to router ABR2, and router ABR2 builds a virtual link to router ABR1. Each router points to the router ID of the other router. For more details about the area virtual-link command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-132
Virtual Link Verification
Verify the configuration of the virtual link.

You can use the show ip ospf virtual-links command to verify that the configured virtual link works properly. In the example in the slide, it is evident that the virtual link toward the neighboring router with the router ID 10.2.2.2 is up and area 1 is used as a transit area. The output shows also that interface Serial0/0/1 is used to form the virtual link as well as several OSPF timers. Other commands that are useful when troubleshooting virtual links are show ip ospf neighbor, show ip ospf database, and debug ip ospf adj. Routers across a virtual link become adjacent and exchange LSAs via the virtual link in a way that is similar to how they exchange LSAs over a physical link. Example output from the show ip ospf neighbor command follows:

For more details about the show ip ospf virtual-links and show ip ospf neighbor commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-133
Virtual Link Verification in OSPF LSDB
Verify the virtual link in the OSPF database.
ROUTE v1. 0 3-45
The show ip ospf database command shows the virtual link as one of the router links. The LSAs learned through the virtual link have the DoNotAge (DNA) option. An example output from the show ip ospf database router 10.2.2.2 command shows the information from router ABR2. The output of this show command for the virtual link LSA is as follows :

3-135
Changing the Cost Metric

This topic explains how to change the cost metric from the default values.
OSPF Cost
The cost, or metric, is an indication of the overhead to send packets over an interface. OSPF cost is used as the route selection criteria. Dijkstras algorithm determines the best path by adding all link costs along a path. OSPF cost is computed automatically. Cost = 10 8 / Bandwidth (in b/s) Bandwidth is specified on the interface with the bandwidth command. OSPF cost is recomputed after every bandwidth change.
ROUTE v1. 0 3-46
The OSPF cost is an indication of the overhead to send packets over an interface. OSPF cost is computed automatically for each interface assigned into an OSPF process using the following formula: cost = 108 / bandwidth (The bandwidth is specified on the interface with the bandwidth interface command.) The cost value is a 16-bit positive number between 1 and 65,535, where a lower value is a more desirable metric. For example, a 64-kb/s link gets a metric of 1562, while a T1 link gets a metric of 64. Cost is applied on all router link paths and route decisions are made on the total cost of a path. The metric is only relevant on an outbound path (route decisions are not made for inbound traffic). The OSPF cost is recomputed after every bandwidth change and Dijkstras algorithm determines the best path by adding all link costs along a path. On high bandwidth links (155 Mb/s and more), automatic cost assignment no longer works (it would result in all costs being equal to 1). On these links, OSPF costs must be set manually on each interface.
3-136
Changing The Default OSPF Cost
Changes the OSPF cost on the specified interface to 10.
Changes the reference bandwidth used to compute the default OSPF costs from 100 to 10000.
ROUTE v1. 0 3-47
In general, the OSPF cost in Cisco routers is calculated using the following formula: (100 Mb/s) / (bandwidth in Mb/s). However, the cost is calculated based on a maximum bandwidth of 100 Mb/s, which is a cost of 1. If you have faster interfaces, you may want to recalibrate the cost of 1 to a higher bandwidth. When you are using the bandwidth of the interface to determine OSPF cost, always remember to use the bandwidth interface command to define the bandwidth of the interface (in kb/s) accurately. The bandwidth command is the reference for calculating the cost. To override the automatically calculated default cost, manually define the cost using the ip ospf cost interface command on a per-interface basis. The cost value is an integer from 1 to 65,535. The lower the number, the better and more preferred the link. In the figure in the slide, the ip ospf cost 10 command manually defines the cost of the GE interface. In the example in the slide, interfaces that are faster than 100 Mb/s are being used (Gigabit Ethernet and Fast Ethernet). The automatic cost assignment is returning the value 1. For all faster links, a new reference value must be configured. Use the auto-cost command in router configuration mode on all routers in the network to ensure accurate route calculations. The reference-bandwidth value in the auto-cost command is a reference bandwidth in megabits per second. It ranges from 1 to 4,294,967, with a default value of 100. In the example in the slide, the reference-bandwidth value in router R2 is set to 10000. In this way, the cost of the Fast Ethernet link is changed to 100, while the Gigabit Ethernet link cost is changed to 10. Thus, the link costs are differentiated. For more details about the ip ospf cost and auto-cost commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-137
Summary
Summary
There are four router types: internal routers, backbone routers, ABRs, and ASBRs. The configuration of OSPF is a two-step process: Define one or more OSPF processes in the router. Define the interfaces that OSPF will run on. OSPF selects a router ID at startup time: Define the router ID with the router-id command. If you do not define the router ID, and there is a loopback interface, the highest IP address of the loopback interface is used. If you do not define the router ID, and there is no loopback interface, the highest IP address of all active interfaces is used.
ROUTE v1. 0 3-48
Summary
Use the show ip protocols, show ip route ospf, show ip ospf interface, show ip ospf, show ip ospf neighbor, and show ip ospf database commands to verify OSPF operation. There are 11 OSPF LSA types. The following are the most commonly used: Type 1 router, Type 2 network, Type 3 and 4 summary, Type 5 external, Type 7 external To prevent other routers on a local network from learning about routes dynamically, you can keep routing update messages from being sent through a router interface by using the passiveinterface command.
ROUTE v1. 0 3-49
3-138
Summary
All OSPF areas must be connected to a backbone area, area 0, which must be contiguous. A virtual link allows discontiguous areas 0 to be connected, or a disconnected area to be connected to area 0 via a transit area. Virtual links should only be used for temporary connections or backup after a failure, not as a primary backbone design feature. The OSPF cost defaults to (100 Mb/s) / (bandwidth in megabits per second). The cost can be changed on a per-interface basis, and so can the reference bandwidth (100 Mb/s).
ROUTE v1. 0 3-50
3-139
3-140
Lesson 5
Lab 3-1 Debrief

Overview
In Lab 3-1, students configure and verify OSPF to improve routing performance. First, a student uses OSPF to exchange routing information in order to achieve IP connectivity over the LAN interfaces. The student then establishes reachability and configures OSPF on the WAN segment. The OSPF interface network type should reflect the Frame Relay WAN segment representation. The student will configure OSPF over Frame Relay using the point-to-point and multipoint OSPF network types.
Objectives
Upon completing this lesson, you will be able to implement and verify OSPF to improve routing performance. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

Lab Topology
ROUTE v1.03-2
The figure above presents the physical lab topology used for Lab 3-1: Configure and verify OSPF to improve routing performance. The topology uses 4 pod routers. Based on the topology, students will identify the required parameters and configure an OSPF routing protocol in order to establish Layer 3 reachability in the network.
3-142

Task 1: Configure OSPF over LAN interfaces What steps did you take to configure the OSPF routing protocol and advertise all of the specific IP subnets used in the network? How can you change the configuration to prevent any network added to the router from being advertised? How does this change the default OSPF DR and BDR selection on the LAN segment? Task 2: Configure OSPF over Frame Relay using the point-topoint OSPF network type What must you change on router R3 to be able to add a WAN segment to the OSPF in the same area as the LAN segment? What must you change on router R4 to be able to add a WAN segment to the OSPF in the same area as the LAN segment and where only the WAN segment subnet is advertised?
ROUTE v1.03-3
3-143

Task 3: Configure OSPF over Frame Relay using the point-tomultipoint OSPF network type How does the configuration reflect the Frame Relay multipoint network type when you include the WAN segment on router R1 into OSPF and enable OSPF adjacency over the serial interface towards routers R2 and R4? How do you change the configuration to also advertise, from the major network, any networks that are added later? This is the OSPF configuration on routers R2 and R4, where the WAN segment towards router R1 is included in the OSPF.
ROUTE v1.03-4
In the first task, you configured OSPF over LAN interfaces. You configured OSPF routing protocol and advertised all of the specific IP subnets used in the network. You then prevented any network added to the router from being advertised. In order to change the default OSPF DR and BDR selection on the LAN segment, you manipulated the OSPF router priority. In the second task, you configured OSPF over Frame Relay using the point-to-point OSPF network type. You added the WAN segment to the OSPF in the same area as the LAN segment. You then configured the OSPF routing protocol to advertise the WAN segment subnet only. In the third task, you configured OSPF over Frame Relay using the point-to-multipoint OSPF network type. You configured OSPF on the WAN segments on routers R2 and R4 toward router R1, reflecting the Frame Relay multipoint network type. You configured OSPF to advertise any networks from the major network that are added later.
3-144
Verification
Did you have enough information to create an implementation plan? Are the proper adjacencies established on the LAN segment? For how long are the adjacencies up? Do you see the proper OSPF routes in the IP routing table when comparing it to the OSPF database? Which router is the DR on the LAN segment between routers R1 and R3? Are the proper adjacencies established on the WAN segment between routers R3 and R4? For how long are the adjacencies up?
ROUTE v1.03-5
3-145
Verification (Cont.)
After enabling OSPF on the WAN segment, do you see the proper OSPF routes in the IP routing table when comparing it to the OSPF database? Are proper adjacencies established on the WAN segment between routers R1, R2, and R4 in your pod? For how long are the adjacencies up? After enabling OSPF on the WAN segment on routers R2 and R4, do you see the proper the OSPF routes in the IP routing table when comparing it to the OSPF database?
ROUTE v1.03-6
A common approach to verifying the implementation process for a routing protocol is to answer the following questions: Did you have enough information to create implementation plan? Are the proper adjacencies established on the LAN segment? For how long are the adjacencies up? Do you see the proper OSPF routes in the IP routing table when comparing the IP routing table to OSPF database? Which router is the DR on the LAN segment between routers R1 and R3? Are the proper adjacencies established on the WAN segment between routers R3 and R4? For how long are the adjacencies up? After enabling OSPF on the WAN segment, do you see the proper OSPF routes in the IP routing table when comparing the IP routing table to the OSPF database? Are the proper adjacencies established on the WAN segment between routers R1, R2, and R4 in your pod? For how long are the adjacencies up? After enabling OSPF on the WAN segment on routers R2 and R4, do you see the proper OSPF routes in the IP routing table when comparing the IP routing table to the OSPF database?
3-146
Checkpoints
Configure the OSPF routing protocol on LAN segment. Advertise only the specific subnets used in the network. Check for the DR on the LAN segment. Configure the OSPF routing protocol on the WAN segment between routers R3 and R4. Advertise only the specific subnets used in the network. Check for the correct OSPF network type on the WAN segments. Configure the OSPF routing protocol on the WAN segments between routers R1, R2, and R4. Check for the proper entries in the IP routing table.
ROUTE v1.03-7
With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Configure the OSPF routing protocol on the LAN segment. Advertise only the specific subnets used in the network. Check for the DR on the LAN segment. Configure the OSPF routing protocol on the WAN segment between routers R3 and R4. Advertise only the specific subnets used in the network. Check for the correct OSPF network type on the WAN segments. Configure the OSPF routing protocol on the WAN segments between routers R1, R2, and R4. Check for the proper entries in the IP routing table.
3-147
Sample Solution and Alternatives

Sample Solution
Configure OSPF on the LAN segment and advertise only the specific subnets used in the network. Configure OSPF on the WAN segment between routers R3 and R4, and advertise only the specific subnets used in the network. Configure the OSPF routing protocol on the WAN segments between routers R1, R2, and R4.
ROUTE v1.03-8
This sample solution includes implementation details and details for each task of the implementation plan. Different solutions are possible and the figure points out some of the details of a successful configuration. The proper implementation of OSPF configuration and verification to improve routing performance includes the following items: Configure OSPF on the LAN segment and advertise only the specific subnets used in the network. Configure OSPF on the WAN segment between router R3 and R4, and advertise only the specific subnets used in the network. Configure the OSPF routing protocol on the WAN segments between routers R1, R2, and R4.
3-148
You can use several routing protocols to provide reachability in the network. Changing the routing protocol is not a realistic solution, though you can modify the existing solution. You can also fulfill the same requirements by reconfiguring to different Frame Relay types.
ROUTE v1.03-9
You can use several routing protocols to provide reachability in the network. Changing the routing protocol is not a realistic solution as changing the routing protocol is not the case during fine tuning of the existing protocol. You can also fulfill the same requirements by reconfiguring to different Frame Relay types.
3-149
Q and A
Why is routing protocol selection important? How is a DR and BDR selection performed? How is OSPF enabled on a LAN segment? Is an OSPF network type important when enabling an OSPF on the WAN segment?
ROUTE v1. 0 3-10
A routing protocol, with its metric and administrative distance, exchanges routing updates and populates its IP routing table, which is used for destination-based forwarding. Different routing protocols process routing updates in different ways. LAN links elect one router as the designated router (DR) and another as the backup designated router (BDR), to ensure that all of the routers on the same LAN have identical databases. The OSPF priority value is used to elect a DR and BDR. The router with the highest priority value is the DR. In case of a tie, the router with the highest router ID becomes the DR. The highest IP address on an active interface is normally used as the router ID, which can be manipulated by configuring an IP address on a loopback interface or using the router-id router configuration command. Once elected the DR passes its database to any new routers that come up. OSPF on a LAN segment is configured using the network command in OSPF router configuration mode with the network for that LAN segment. The router priority value can be added to the particular interface in order to manipulate DR and BDR election. It is important to specify the OSPF network type on the WAN segment. This is because the OSPF network type defines how the OSPF adjacencies will be established, as well as how OSPF routing packets will be propagated.
3-150
Summary
Summary
Configure OSPF on the LAN segment to advertise only specific subnets and to observe DR selection. Configure OSPF on the WAN segment to advertise only specific subnets. Configure OSPF on the WAN segment to advertise any additional networks from the major network, if added later.
ROUTE v1. 0 3-11
3-151
3-152
Lesson 6
Lab 3-2 Debrief

Overview
In Lab 3-2, students implement and verify OSPF multiarea routing. First, they define the backbone area, where the selected routers are configured for the OSPF backbone area. They then configure the remaining routers for nonbackbone normal areas, as there is no need to filter any subnets. They tune the OSPF configuration by manipulating the cost and router ID. They can perform additional optimization by suppressing routing updates.
Objectives
Upon completing this lesson, you will be able to implement and verify OSPF multiarea routing. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

This topic describes lab topology and key checkpoints used to create a solution and to start with verification.
Lab Topology
ROUTE v1. 03-2
The figure above presents the physical lab topology used for the Lab 3-2: Implement and Verify OSPF Multiarea Routing. The topology uses four pod routers and one backbone router. Based on this topology, students will divide the will be divided into more OSPF areas (backbone and nonbackbone) and apply the correct configuration to each router.
3-154

Task 1: Configuring OSPF backbone area What steps did you take to configure the OSPF routing protocol on a router belonging to the backbone area? Task 2: Configuring OSPF nonbackbone areas What steps did you take to configure the OSPF routing protocol on routers belonging to different nonbackbone areas? Task 3: Tuning an OSPF operation How can the default cost calculation be changed? How can the router ID be changed? How can you preserve CPU cycles on router R3 by eliminating the unnecessary OSPF traffic on a LAN segment?
ROUTE v1. 03-3
In the first task, you configured the OSPF backbone area, which means configuring routers in backbone area. Selections of the routers are members of the backbone area and the correct area type must be configured on each interface, which is part of the backbone area. In the second task, you configured the OSPF nonbackbone areas and configured the routers in the nonbackbone areas. Some routers represent a nonbackbone area where they have all or just a few interfaces in a nonbackbone area. In the third task, you must tune OSPF operation. You must change the default cost calculation to manipulate the path for the packets. You must change the router ID to manipulate the DR and BDR selection. Finally, you must configure some interfaces as passive to preserve the CPU cycles on the router by eliminating unnecessary OSPF traffic.
Implementing a Scalable Multiarea Network OSPF-based Solution
3-155
Verification
Did you have enough information to create an implementation plan? Is adjacency in area 0 between routers R1 and BBR2 established? Is the IP routing table populated with correct OSPF routes? Is adjacency established between the routers of nonbackbone areas? Is the IP routing table populated with the correct OSPF routes? How is a change in cost calculation done? What is the router ID of router R1? Is the IP routing table populated with the correct OSPF routes? Did router R3 stop trying to set up an OSPF adjacency via the LAN segment?
To verify the implementation of OSPF, answer the following questions: Did you have enough information to create an implementation plan? Is an adjacency in area 0 between routers R1 and BBR2 established? Is the IP routing table populated with the correct OSPF routes? Is an adjacency established between routers in the nonbackbone areas? Is the IP routing table populated with the correct OSPF routes? How is a cost calculation change done? What is the router ID of router R1? Is the IP routing table populated with the correct OSPF routes? Did router R3 stop trying to set up an OSPF adjacency via the LAN segment?
3-156
Checkpoints
Configure OSPF in area 0. Check for adjacencies in area 0 between routers R1 and BBR2. Check the IP routing table for the proper OSPF routes. Configure OSPF in nonbackbone areas Check if an adjacency is established between the routers of nonbackbone areas. Check the IP routing table for proper OSPF routes. Change the cost calculation. Manipulate the OSPF router ID of router R1. Check the IP routing table for the proper OSPF routes. Check that router R3 stopped trying to set up an OSPF adjacency via the LAN segment.
ROUTE v1. 03-5
With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Configure OSPF in area 0. Check for adjacencies in area 0 between routers R1 and BBR2. Check the IP routing table for the proper OSPF routes. Configure the OSPF in nonbackbone areas. Check if an adjacency is established between the routers of nonbackbone areas. Check the IP routing table for the proper OSPF routes. Change the cost calculation. Manipulate the OSPF router ID of router R1. Check the IP routing table for proper OSPF routes. Check if router R3 has stopped trying to set up an OSPF adjacency via the LAN segment.
3-157

Sample Solution
Configure OSPF for backbone and nonbackbone areas. Select the correct OSPF network type for each WAN segment. Change the default cost calculation to manipulate the path selection and change the router ID to manipulate DR and BDR selection. Configure the passive interface to suppress routing traffic and preserve CPU cycles on router R3.
ROUTE v1. 03-6
The sample solution includes the implementation details and details for each task of the implementation plan. Different solutions are possible and the figure points out a few details of successful configuration. The proper implementation and verification of OSPF multiarea routing includes the following details: Configure OSPF for the backbone and nonbackbone areas. Select the correct OSPF network type for each WAN segment. Change the default cost calculation to manipulate the path selection and change the router ID to manipulate the DR and BDR selection. Configure the passive interface to suppress routing traffic and preserve CPU cycles on router R3.
3-158
You can design different backbone and nonbackbone areas, for which nonbackbone areas can be non-standard in order to reduce the number of routing updates. You can configure a different IP adress on the loopback interface to manipulate the router ID. Because changing the routing protocol is not a realistic solution, you can configure static and default routes.
ROUTE v1. 03-7
In order to create a similar configuration, you can design different backbone and nonbackbone areas, for which the nonbackbone areas can be non-standard in order to reduce the number of routing updates. You can configure a different IP address on the loopback interface to manipulate the router ID. Because it is not realistic to change the routing protocol, you can configure static and default routes, in order to provide reachability while still preserving OSPF as a routing protocol in the network.
3-159
Q and A
What is the purpose of backbone and nonbackbone areas? How can a default cost calculation be changed? Why is the router ID important? How does a passive interface work in an OSPF routing protocol?
ROUTE v1. 03-8
OSPF segments the network in different areas to optimize the routing in the whole network. All nonbackbone areas must be connected to backbone area. Routing information is exchanged between the areas in a controlled way; summarization takes place on the area border routers limiting the number of updates that the small changes locally in the area are not triggering the topology change recalculation in other areas. You can change the default cost calculation by changing the cost per neighbor in OSPF routing process configuration mode. The OSPF routing protocol adds the router ID to all OSPF updates and is visible in the OSPF topology database. The router ID inside the update packet defines the source of the update packets and must be unique in the network. When a passive interface is enabled, the sending and receiving of routing updates is disabled. The specified interface address appears as a stub network in the OSPF domain.
3-160
Summary
Summary
Configure OSPF for a backbone area. Configure OSPF for a nonbackbone area. Tune OSPF operation by changing how default cost calculation is performed; you can change the cost calculation by changing the router ID and configuring a passive interface. Doing this preserves CPU cycles by eliminating unnecessary OSPF traffic on the LAN segment.
ROUTE v1. 03-9
3-161
3-162
Lesson 7
Configuring and Verifying OSPF Route Summarization

Overview
Scalability, improved CPU and memory utilization, and the ability to mix small routers with large routers are all benefits of using proper route summarization techniques. A key feature of Open Shortest Path First (OSPF) protocol is the ability to summarize routes at area and autonomous system (AS) boundaries. Route summarization is important, because it reduces the amount of OSPF link-state advertisement (LSA) flooding and the sizes of link-state databases (LSDBs) and routing tables, which also reduces memory and CPU utilization on the routers. The OSPF network can scale to very large sizes, in part because of route summarization. Default routes reduce routing table size, and also reduce memory and CPU utilization. OSPF injects a default route unconditionally or based on the presence of the default route inside the routing table. This lesson defines the different types of route summarization and describes the configuration commands for each type. It also describes the benefits of default routes and how to configure them.
Objectives
Upon completing this lesson, you will be able to describe the procedure for configuring OSPF route summarization for interarea and external routes. This ability includes being able to meet these objectives: Describe OSPF route summarization Implement OSPF route summarization Identify the benefits of a default route in OSPF Use a default route in OSPF
OSPF Route Summarization

This topic describes the functions of interarea route summarization and external route summarization.
Summarization
Networks are normally translated into type 3 LSAs in other areas. Route summarization is the consolidation of advertised addresses. On ABR, summarize type 3 LSAs On ASBR, summarize type 5 LSAs A good addressing plan is required. A drawback is the possibility of suboptimal routing.
ROUTE v1.03-2
Route summarization is a key to scalability in OSPF. Route summarization helps solve two major problems: large routing tables and frequent LSA flooding throughout the AS. Every time a route disappears in one area, routers in other areas also get involved in shortest-path calculation. In order to reduce the size of the area database, you can configure summarization on an area boundary or autonomous system boundary. 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 ABR or ASBR routers consolidate multiple routes into a single advertisement. ABR routers summarize type 3 LSAs and ASBR routers summarize type 5 LSAs. Instead of advertising many specific prefixes, advertise only one summary prefix. If the OSPF design includes many Area Border Routers (ABRs) or Autonomous System Boundary Routers, suboptimal routing is possible. This is one of the drawbacks of summarization. Of course, route summarization requires a good addressing planan assignment of subnets and addresses that is based on the OSPF area structure and lends itself to aggregation at the OSPF area borders.
Note Recall that summary LSAs (type 3) and external LSAs (type 5) do not, by default, contain summarized routes.
3-164
Benefits of Route Summarization

Minimizes the number of routing table entries Localizes the impact of a topology change Reduces LSA flooding and saves CPU resources
ROUTE v1.03-3
Route summarization directly affects the amount of bandwidth, CPU power, and memory resources that the OSPF routing process consumes. Without route summarization, every specific-link LSA is propagated into the OSPF backbone and beyond, causing unnecessary network traffic and router overhead. With route summarization, only the summarized routes are propagated into the backbone (area 0). Summarization prevents every router from having to rerun the SPF algorithm, increases the stability of the network, and reduces unnecessary LSA flooding. Also, if a network link fails, the topology change is not propagated into the backbone (and other areas by way of the backbone). Specific-link LSA flooding outside the area does not occur.
3-165
Implementing OSPF Route Summarization

This topic describes how to configure route summarization in OSPF.
Interarea Route Summarization

A summary route will be generated if at least one subnet within the area falls in the summary address range. A summarized route metric will be equal to the lowest cost of all subnets within the summary address range. Only for the summary routes of connected areas: The ABR creates a route to Null 0 to avoid loops.
ROUTE v1.03-4
The summarization of internal routes can be done only by ABRs (router R2 in the figure above). Without summarization, all of the prefixes from an area are passed into the backbone as type 3 interarea routes. When summarization is enabled, the ABR intercepts this process and instead injects a single type 3 LSA, which describes the summary route into the backbone. Multiple routes inside the area are summarized. A summary route is generated if at least one subnet within the area falls in the summary address range and the summarized route metric is equal to the lowest cost of all the subnets within the summary address range. Interarea summarization can only be done for the intra-area routes of connected areas, and the ABR creates a route to Null0 in order to avoid loops in the absence of more specific routes.
3-166
Using Route Summarization

Interarea summary link carries a mask One or more entries can represent several subnets
ROUTE v1.03-5
OSPF is a classless routing protocol, which means that it carries subnet mask information along with route information. Therefore, OSPF supports multiple subnet masks for the same major network, which is known as variable-length subnet masking (VLSM). OSPF also supports discontiguous subnets, because the subnet masks are part of the LSDB. Some older distance vector protocols do not support VLSM or discontiguous subnets. For example, if a major network crosses the boundaries of an OSPF and an older distance vector routing protocol domain, then VLSM information redistributed into the older routing distance vector protocol is lost, and the static routes may have to be configured manually there. Network numbers in areas should be assigned contiguously to ensure that these addresses can be summarized into a minimal number of summary addresses. For example, in the figure above, the list of 12 networks in the routing table of the ABR can be summarized into two summary address advertisements. The block of addresses from 172.16.8.0 through 172.16.15.0/24 can be summarized using 172.16.8.0/21, and the block from 172.16.16.0 through 172.16.19.0/24 can be summarized using 172.16.16.0/22.
3-167
Configure Interarea Route Summarization

Configures type 3 summarization on ABRs
ROUTE v1.03-6
OSPF does not perform automatic summarization on major network boundaries. To consolidate and summarize routes at an area boundary, use the area range command in router configuration mode. The ABR will summarize routes for a specific area before injecting them into a different area via the backbone as type 3 summary LSAs. Before summarization is possible, OSPF must be configured with the contiguous IP addressing implementation. Without proper addressing implementation, effective summarization cannot be done. Cisco IOS Software creates a summary route to interface Null0 when manual summarization is configured, to prevent routing loops. For example, if the summarizing router receives a packet to an unknown subnet that is part of the summarized range, the packet matches the summary route based on the longest match. The packet is forwarded to the Null0 interface (in other words, it is dropped), which prevents the router from forwarding the packet to a default route and possibly creating a routing loop. For more details about the area range command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-168
Route Summarization Configuration Example at the ABR
ROUTE v1.03-7
The figure shows that route summarization can occur in both directions: from a nonbackbone area to area 0 and from area 0 to a nonbackbone area. In the example, the router ABR configuration specifies the following summarization: area 0 range 172.16.96.0 255.255.224.0: Identifies area 0 as the area containing the range of networks to be summarized into area 1. Router ABR summarizes the range of subnets from 172.16.96.0 to 172.16.127.0 into one range: 172.16.96.0 255.255.224.0. area 1 range 172.16.64.0 255.255.224.0: Identifies area 1 as the area containing the range of networks to be summarized into area 0. Router ABR summarizes the range of subnets from 172.16.64.0 to 172.16.95.0 into one range: 172.16.64.0 255.255.224.0.
Note Depending on your network topology, you may not want to summarize area 0 networks into other areas. For example, if you have more than one ABR between a nonbackbone area and the backbone area, sending a summary (type 3) LSA with the explicit network information into an area ensures that the shortest path to destinations outside the area is selected. If you summarize the addresses, suboptimal path selection may occur.
3-169
External Route Summarization

Summarization can be used for external routes: on an AS boundary for type 5 LSAs (redistributed routes) on an NSSA ABR for type 5 translated from type 7 A summary route to Null 0 will be created for each summary range
ROUTE v1.03-8
Summarization can also be used for external routes. Each route that is redistributed into OSPF from other protocols is advertised individually with an external link state advertisement (LSA). To reduce the size of the OSPF link state database, you can configure a summary for external routes. Summarization of external routes can be done on the ASBR for type 5 LSAs (redistributed routes) before injecting them into the OSPF domain. Summarization of external routes can be done by the ABR in not-so-stubby areas (NSSAs) as well, where the ABR router creates type 5 summary routes from type 7 external routes. Without summarization, all of the redistributed external prefixes from external autonomous system are passed into the OSPF area. A summary route to Null0 is created automatically for each summary range.
3-170
Configure External Route Summarization

Configures type 5 summarization of redistributed routes on ASBRs
ROUTE v1.03-9
To create aggregate addresses for OSPF at an autonomous system boundary, use the summaryaddress command in router configuration mode. ASBR will summarize external routes before injecting them into the OSPF domain as type 5 external LSAs. You must implement contiguous IP addressing before you can achieve optimal summarization. Sometimes only type 3 or type 5 summarization is required, but in large OSPF networks, both configurations can be applied. For more details about the summary-address command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-171
Route Summarization Configuration Example at ASBR
ROUTE v1. 0 3-10
The figure depicts route summarization on the ASBR. On the right-hand side, an external AS running EIGRP has its routes redistributed into OSPF. Because of the contiguous subnet block in the external EIGRP network, it is possible to summarize the 32 different subnets into one summarized route. Instead of 32 external type 5 LSAs flooding into the OSPF network, there is only one.
Note EIGRP routes must also be redistributed into OSPF in this example; redistribution is covered in the Implement an IPv4-Based Redistribution Solution module.
3-172
Benefits of a Default Route in OSPF

Occasionally, you will be required to configure OSPF to advertise a default route into the routes AS. This topic describes the benefits of a default route in OSPF.
Default Routes in OSPF

A default route is injected into OSPF as an external type 5 LSA. Default route distribution is not on by default. Benefits of default routes include: A smaller routing table Fewer resources used in the router
ROUTE v1. 0 3-11
To be able to perform routing from an OSPF autonomous system toward external networks or toward the Internet, you must either know all of the destination networks or create a default route. In order to learn all of the destinations, you can either create a number of static routes, or configure redistribution. But the most scalable and optimized way is through the use of a default route. The benefits of a default route include the following: Smaller routing table Fewer resources and less CPU power needed; no need to recalculate the SPF algorithm if one or more networks fail The figure shows how OSPF injects a default route into a standard area (the different types of areas are described in the next lesson). Any OSPF router can originate the default routes injected into a standard area, but the OSPF routers by default do not generate a default route into the OSPF domain. In order for OSPF to generate a default route, you must run a configuration command. A default route shows up in the OSPF database as a type 5 external LSA. Here is an example of how it looks in the database:

3-173
Using a Default Route in OSPF

This topic describes how to configure a default route injection into OSPF.
Configure OSPF Default Route

The first command allows the ASBR to originate a type 5 default route if it has the gateway of last resort. The second command allows the ASBR to originate a type 5 default route even if there is no gateway of last resort (optional). Use the route map to define a dependency on any condition inside the route map (optional).
ROUTE v1. 0 3-12
To generate a default external route into an OSPF routing domain, use the default-information originate router configuration command, as shown in the figure above. There are two ways to advertise a default route into a standard area: Advertise 0.0.0.0/0 into the OSPF domain when the advertising router already has a default route. Use the default-information originate command to allow the ASBR to originate a type 5 default route inside the OSPD autonomous system. You can also use different keywords in the configuration command, order to configure dependency on IP routing table entries: Advertise 0.0.0.0/0, regardless of whether the advertising router already has a default route. The second method can be accomplished by adding the keyword always to the defaultinformation originate command, as shown in the figure in the slide. Whenever you use the redistribute or the default-information router configuration command to redistribute routes into an OSPF routing domain, the Cisco IOS software automatically becomes an Autonomous System Boundary Router (ASBR). However, an ASBR by default does not generate a default route into the OSPF routing domain. The software must still have a default route for itself before it generates one, except when you have specified the always keyword. You can also use a route map to define dependency on any condition inside the route map. For more details about the default-information originate command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-174
Default Route Configuration Example
ROUTE v1. 0 3-13
In the figure above, an OSPF network is multihomed to dual Internet service providers (ISPs). Because the number of prefixes in the ISPs routing table is high, it makes no sense to redistribute them into an OSPF autonomous system. The default route is sent into the OSPF AS in order to provide connectivity to the external destinations. In the customer design, ISP A is preferred, and ISP B is used as a backup. In order to define the priority, the optional metric parameter has been used to establish a preference for the default route to ISP A. In the example above, router As default route has a metric of 10 attached to it. It is preferred over the default route advertised by router R2, which has a metric of 100. Because the default-information originate command is used without the optional parameter always, the default route must exist inside the IP routing table in order to advertise the default route into an OSPF domain. Both routers in the figure above have a default route statically defined. For more details about the default-information originate command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-175
Summary
Summary
Route summarization improves CPU utilization, reduces LSA flooding, and reduces routing table sizes. The area range command is used to summarize at the ABR. The summary-address command is used to summarize at the ASBR. Default routes can be used in OSPF to prevent the need for a specific route to each destination network. The benefits include a much smaller routing table and an LSDB with complete reachability. OSPF uses the default-information originate command to inject a default route.
ROUTE v1. 0 3-14
3-176
Lesson 8
Lab 3-3 Debrief

Overview
In Lab 3-3, students configure and verify OSPF route summarization for interarea and external routes. After each student performs an initial examination of the OSPF routing information and an IP routing table, it is evident that optimization is required. Each must optimize an OSPF link-state database and, consequently, an IP routing table, in order to make them smaller with summarization. Once students summarize internal routes, they can do additional work for external routes, as well.
Objectives
Upon completing this lesson, you will be able to configure and verify OSPF route summarization for interarea and external routes. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

Lab Topology
ROUTE v1. 03-2
The figure in this slide presents the physical the lab topology used for the Lab 3-3: Configure and verify OSPF route summarization for interarea and external routes. The topology uses four pod routers and one backbone router. Based on this topology and the OSPF routing protocol configuration, several internal and external OSPF routes exist in the IP routing tables in all of the routers in different areas. The configuration will be optimized by using summarization.
3-178

Task 1: Examining OSPF Routing Information How can you verify the operation of an OSPF routing protocol? What can you see by observing the OSPF neighbors, OSPF database, OSPF interfaces, and IP routing table? Task 2: Summarizing OSPF Internal Routes How are internal routes defined? How is summarization performed for internal routes? Task 3: Summarizing OSPF External Routes Where do you apply the summarization of external routes? How many sources of external routes exist in the lab?
ROUTE v1. 03-3
In the first task, you will examine the operation of an OSPF routing protocol by checking the information from the OSPF neighbors, OSPF database, and OSPF interfaces. You will also examine the IP routing table. Your pod is preconfigured with the OSPF configuration and the proper configuration steps are needed in order to optimize the size of the OSPF database and IP routing table. In the second task, summarization of the OSPF internal routes is required. An OSPF can differentiate between internal and external (redistributed) routes. When applying internal route summarization, the summarization command is applied from the direction (area) where the routes are received. In the third task, OSPF summarization of OSPF external routes is required. Summarization of external routes should be done as close to the source as possible. Preferably, the router redistributing the routes should summarize them as well. There is only one source of external routers. Keep in mind that the summarization command is different than the one for the internal routes, because external routes have no concept of areas.
3-179
Verification
Did you have enough information to create an implementation plan? Were you able to define the OSPF topology and the content of an IP routing table? Does the summary route exist on the routers in areas 3 and 24? Does the OSPF link-state database contain relevant information? Is the routing information for the external networks 192.168.x.0/24 presented as summary information in the OSPF link-state database and, therefore, in the IP routing tables on relevant routers? Do all the routers have IP connectivity to the pod external networks?
ROUTE v1. 03-4
To verify the configuration of OSPF, answer the following questions: Did you have enough information to create an implementation plan? Were you able to define the OSPF topology and the content of an IP routing table? Does the summary route exist on the routers in areas 3 and 24? Does the OSPF link-state database contain relevant information? Is the routing information for the external networks 192.168.x.0/24 presented as summary information in the OSPF link-state database and, therefore, in the IP routing tables on relevant routers? Do all the routers have IP connectivity to the pod external networks?
3-180
Checkpoints
Examine the IP routing information exchanged by routers configured with the OSPF routing protocol. Define the internal and external routes. Configure the summarization of internal routes. Check if the adjacencies are up. Check if the IP routing tables and OSPF databases reflect the summarization. Configure the summarization of external routes. Check if the adjacencies are up. Check if the IP routing tables and OSPF databases reflect the summarization.
ROUTE v1. 03-5
With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Examine the IP routing information exchanged by routers configured with OSPF routing protocol. Define internal and external routes. Configure the summarization of internal routes. Check if the adjacencies are up. Check if the IP routing tables and OSPF databases reflect the summarization. Configure the summarization of external routes. Check if the adjacencies are up. Check if the IP routing tables and OSPF databases reflect the summarization.
3-181

A Sample Solution
The OSPF topology and OSPF operation are verified, along with the IP routing table, which shows the OSPF routes. Internal summarization is configured for areas 3 and 24 on ABRs. External summarization is configured on an ASBR router, which redistributes external routes into the OSPF routing protocol.
ROUTE v1. 03-6
The sample solution in the slide includes implementation details and details for each task of the implementation plan. Different solutions are possible; the figure points out a few details of a successful configuration. The proper implementation of route redistribution between multiple IP routing protocols include the following details: The OSPF topology and OSPF operation are verified, along with the IP routing table, which shows OSPF routes. Internal summarization summarizes the internal OSPF routes sent into area 3 and area 24. ABR routers are configured for summarization. External summarization is configured on an ASBR router, which redistributes the external routes into the OSPF routing protocol.
3-182
Change the area types in order to optimize the amount of OSPF information entering into a specific area. Because changing the routing protocol is not a realistic solution, static and default routes can be configured together with route filtering.
ROUTE v1. 03-7
The OSPF routing protocol supports different area types, which prevent the insertion of all OSPF routing updates. By selecting different OSPF area types, the network operator can filter network announcements on the ABR or ASBR routers and ensure that only a summary or default route is entered. In order to provide reachability in the network, several routing protocols can be used. Changing the routing protocol is not a realistic solution, because system administrators will not redesign and reconfigure the whole network for another routing protocol. Sometimes reconfiguration is not even possible, because not all devices may support the desired routing protocol. On the other hand, static and default routes can be configured together with route filtering. Filtering prevents routing updates from being exchanged, and static and default routes provide reachability. Static routes are not a scalable solution.
3-183
Q and A
How can you verify OSPF routes in an IP routing table? How can you verify the OSPF topology and operation? Where do you perform summarization into areas 3 and 24? Where do you perform summarization of external routes? Is there a difference between summarization of internal and external routes? How can you verify summarization results?
ROUTE v1. 03-8
You can verify the IP routing table by observing the contents of the IP routing table for the OSPF routes. You can verify the operation of the OSPF routing protocol by checking the information of OSPF neighbors, the OSPF database, OSPF interfaces, and the IP routing table. You should configure summarization of internal routes on ABR routers. You should configure summarization of external routes as close as possible to the source of redistribution, preferably on the ASBR routers. You use different configuration commands to configure external and internal summarization. You can verify summarization results by observing the IP routing table and OSPF database.
3-184
Summary
Summary
IP routing information exchanged by routers configured with OSPF routing protocol was examined. You can optimize the OSPF link-state database and consequently the IP routing table by using summarization to making the database smaller. OSPF routing operation can be further optimized by summarizing OSPF external routes.
ROUTE v1. 03-9
3-185
3-186
Lesson 9
Configuring and Verifying OSPF Special Area Types

Overview
The Open Shortest Path First (OSPF) protocol defines several special-case area types, including stub areas, totally stubby areas, and not-so-stubby areas (NSSAs). The purpose of all three types of stub areas is to inject default routes into an area so that external and summary link-state advertisements (LSAs) are not flooded in. Stub areas are designed to reduce the amount of flooding, the link-state database (LSDB) size, and the routing table size in routers within the area. Network designers should always consider using stub area techniques when building networks. Stub area techniques improve performance in OSPF networks and allow the network to scale to significantly larger sizes. This lesson discusses OSPF area types and how to configure them.
Objectives
Upon completing this lesson, you will be able to implement and verify different OSPF area types, including the stub area, totally stubby area, NSSA, and totally NSSA. This ability includes being able to meet these objectives: Determine OSPF area types Define and implement a stub area Define and implement a totally stubby area Interpret routing tables for OSPF area types Define and implement a not-so-stubby area and totally NSSA in OSPF Verify all OSPF area types
OSPF Area Types

This topic describes the OSPF area types.
OSPF Area Types and Structure

OSPF is based on a two-level hierarchical area structure Each area has its own topology database Area Types Backbone area: Connects all other areas Normal area: Contains all of the internal and external routing information Stub area: Contains internal and area routing information, but not external routing information Totally stubby area: Contains area routing information only; Cisco proprietary Not-so-stubby area: Contains area and external routing information
ROUTE v1.03-2
OSPF is based on a two-level hierarchical area structure. The hierarchy defines backbone and nonbackbone areas. Each area has its own topology, which is invisible from outside the area. A router belonging to several areas (called an Area Border Router, or ABR) has several topology databases. All areas have to be connected to a backbone area or linked to it with a virtual link. The backbone area has to be contiguous. A nonbackbone area can be discontiguous. Area types are: Backbone area: Connects all other areas Normal area: Contains all internal and external routing information Stub area: Contains internal and area routing information, but not external routing information Totally stubby area: Contains area routing information only; Cisco proprietary Not-so-stubby area (NSSA): Contains area and external routing information
3-188
Types of Areas
ROUTE v1.03-3
The characteristics assigned to an area control the type of route information that it receives. The possible area types are as follows: Normal area: This default area accepts link updates, route summaries, and external routes. Backbone area (transit area): The backbone area is the central entity to which all other areas connect. The backbone area is labeled area 0. All other areas connect to this area to exchange and route information. The OSPF backbone includes all the properties of a standard OSPF area. Stub area: This area does not accept information about routes external to the autonomous system (AS), such as routes from non-OSPF sources. If routers need to route to networks outside the AS, they use a default route, noted as 0.0.0.0. Stub areas cannot contain autonomous system boundary routers (ASBRs) (except that ABRs may also be ASBRs). Totally stubby area: This area does not accept external AS routes or summary routes from other areas internal to the AS. If the 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 ABRs may also be ASBRs). NSSA: NSSA is an addendum to the OSPF RFC. This area defines a special LSA type 7. An NSSA offers benefits that are similar to those of a stub area or totally stubby area. However, NSSAs allow ASBRs, which is prohibited in a stub area.
3-189
OSPF Router and LSA Types

ABR is generating Summary LSAs ASBR is generating External LSAs Summary and External LSAs can be blocked and default route is sent instead
ROUTE v1.03-4
The OSPF defines three main router types: Internal router: This type of router resides inside any area and is a member of one area only. Area Border Router (ABR): This type of router that is a member of more than one area. As a border router, it has the ability to control routing traffic from one area to another. Different types of LSAs are exchanged between areas. ABRs can transmit these LSAs, or block them and send default routes instead. Autonomous System Boundary Router (ASBR): This type of router is used to insert external routing information from another non-OSPF autonomous system. ASBR routers generate External LSAs, which can be blocked by ABR routers. OSPF routers are able to generate and send the following six types of LSAs: Router Link (LSA type 1), Network Link (LSA type 2), Network Summary (LSA type 3), ASBR Summary (LSA type 4), External (LSA type 5), and NSSA External (LSA type 7).
3-190
Stub and Totally Stub Area Rules

An area can be stub or totally stub if:
There is one ABR or more All routers that are members of the stub area are configured as stub routers There is no ASBR in the area The area is not an area 0 No virtual links go through the area
ROUTE v1.03-5
Stub and totally stubby areas do not carry any external routes, known as type 5 LSAs. An area can be qualified as a stub or totally stubby area if it has the following characteristics: There is either a single exit point from that area, or, if there are multiple exits, one or more ABRs inject a default into the stub area and suboptimal routing paths are acceptable. Routing to other areas or autonomous systems could take a suboptimal path to reach the destination by exiting the area at a point that is farther from the destination than other exit points. All OSPF routers inside the stub area, including ABRs and internal routers, must be configured as stub routers before they can become neighbors and exchange routing information. There is no ASBR inside the area. The area is not the backbone area, area 0. The area is not needed as a transit area for virtual links. Recall that a virtual link is a link that allows an area to connect to the backbone via a transit area. Virtual links are generally used for temporary connections or backup after a failure; they should not be considered as part of the primary OSPF design.
3-191
Defining and Implementing a Stub Area

This topic defines OSPF stub areas and describes how to configure them.
OSPF Stub Areas

External LSAs are stopped. The default route is advertised into the stub area by the ABR.
ROUTE v1.03-6
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 redistributed from other routing protocols into OSPF, are not permitted to flood into a stub area. Routing from these areas to the outside is based on a default route (0.0.0.0). If a packet is addressed to a network that is not in the routing table of an internal router, the router automatically forwards the packet to the ABR, which sends a 0.0.0.0 LSA. Forwarding the packet to the ABR allows routers within the stub to reduce the size of their routing tables, because a single default route replaces many external routes. A stub area is typically created when a hub-and-spoke topology is used, with each spoke being a stub area, such as a branch office. In this case, the branch office does not need to know about every network at the headquarters site, because it can use a default route to reach the networks.
3-192
Stub Area Configuration
This command turns on stub area networking. Configure all routers in the stub area as stub routers.
This command defines the cost of a default route sent into the stub area (default is 1); defining the cost is optional.
ROUTE v1.03-7
Once you have gathered all the required information for an implementation plan, you must complete the following tasks to configure OSPF stub areas: Configure all routers in the stub area as stub routers Configure the cost for the default route on an ABR router (optional) To configure an area as a stub, all routers inside the area must be configured as stub routers. The area stub router configuration mode command is used to define an area as a stub area. By default, the ABR 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. You only use this command on Area Border Routers (ABRs) attached to stub areas or NSSAs. The default-cost option provides the metric for the summary default route generated by the ABR into the stub area. For more details about the area stub and area default-cost commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-193
OSPF Stub Area Configuration Example
ROUTE v1.03-8
Area 2 in the figure in this slide is defined as the stub area. No routes from the external AS are forwarded into the stub area. The last line in each configuration (area 2 stub) defines the stub area. Router ABR automatically advertises 0.0.0.0 (the default route) with a default cost metric of 1 into the stub area. Each router in the stub area must be configured with the area stub command. The hello packet exchanged between OSPF routers contains a stub area flag that must match on neighboring routers. The area 2 stub command must be enabled on all routers in the stub, so that they all have the stub flag set; they can then become neighbors and exchange routing information. The routes that appear in the routing table of router R2 are as follows: Intra-area routes, which are designated with an O in the routing table The default route and interarea routes, which are both designated with an IA in the routing table The default route is also denoted with an asterisk (O *IA) Configuration of the router ABR includes the area 2 default-cost 10 command, which changes the default value of the cost for default routes from 1 to 10.
3-194
Defining and Implementing a Totally Stubby Area

This topic defines OSPF totally stubby areas and describes how to configure them.
OSPF Totally Stubby Areas

External and Summary LSAs are stopped The default route is sent instead Cisco proprietary feature
ROUTE v1.03-9
The totally stubby area technique is a Cisco proprietary enhancement that further reduces the number of routes in the routing table. A totally stubby area is a stub area that blocks external type 5 LSAs as well as summary type 3 and type 4 LSAs (interarea routes) from entering the area. Because it blocks these routes, a totally stubby area recognizes only intra-area routes and the default route of 0.0.0.0. ABRs inject the default summary link 0.0.0.0 into the totally stubby area. Each router picks the closest ABR as a gateway to everything outside the area. Totally stubby areas minimize routing information further than stub areas and increase the stability and scalability of OSPF internetworks. Using totally stubby areas is typically a better solution than using stub areas, as long as the ABR is a Cisco router.
3-195
Totally Stubby Area Configuration
This command turns on stub area networking Configure all routers in the stub area as stub routers
First command defines the totally stubby area on the ABR router Second command defines the cost of a default route sent into the totally stubby area (default is 1); defining the cost is optional
ROUTE v1. 0 3-10
Once you have gathered all the required information for an implementation plan, you must complete the following tasks to configure OSPF totally stubby areas: Configure all routers in stub areas as stub routers Configure the ABR router as a totally stubby router Configure the cost of the default route on the ABR router, if desired To configure an area as totally stubby, you must configure all routers inside the area as stub routers. The area stub router configuration mode command defines an area as a stub area. Additionally, the ABR router must be configured for totally stubby functionality. Run the area stub command with the no-summary keyword on the ABR router to configure it as totally stubby. By default, the ABR 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. For more details about the area stub and area default-cost commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-196
Totally Stubby Configuration Example

Router R2 is the preferred ABR
ROUTE v1. 0 3-11
Example: Totally Stubby Configuration

The figure in this slide shows an example of a totally stubby area configuration. All routes advertised into area 1 (from area 0 and the external AS) default to 0.0.0.0. The default route cost is set to 5 on router R2 and to 10 on router R4. Both default routes are advertised into area 1. However, the default route from router R2 is advertised with a lower cost. This makes routes through R2 preferable even if the internal cost from router R3 to router R4 is the same as the internal cost from router R3 to router R2. Notice that router R3 requires the area 1 stub command, yet the no-summary extension is not required. Only ABRs use the no-summary extension to keep summary LSAs from being propagated into the stub area.
Note Remember that all routers in a stub or totally stubby area must be configured as stub routers. An OSPF adjacency will not form between stub and nonstub routers.
3-197
Interpreting Routing Tables for OSPF Area Types

This topic interprets information shown on routing tables for stub areas and totally stubby areas.
Routing Table in a Normal Area
ROUTE v1. 0 3-12
The figure shows how the routing table might look for an OSPF router in a standard area without a stub or totally stubby configuration. Intra-area, interarea, and external routes are all maintained in a standard area.
3-198
Routing Table in a Stub Area

Use the area 1 stub command to configure a stub area.
ROUTE v1. 0 3-13
The figure in this slide shows how the same routing table looks if the area is configured as a stub area. Intra-area and interarea routes are all maintained. In a stub area, ABR routers block external LSAs, and external routes are not visible in the routing table but accessible via the intra-area default route. ABR inserts an intra-area default route instead of forwarding external LSAs into the stub area.
3-199
Routing Table in a Stub Area with Summarization

Use the area 1 stub and area 1 range commands.
ROUTE v1. 0 3-14
The figure in this slide shows how the same routing table looks if stub area functionality is used and summarization is performed on each ABR. External LSAs are blocked by the ABR routers, which also perform summarization. The intra-area and summarized interarea routes are all maintained in the routing tables of stub area routers. External routes are not visible in the routing tables for each stub area, but are accessible via the intra-area default routes for that stub area.
3-200
Routing Table in a Totally Stubby Area

Use the area 1 stub command on all internal routers. Use the area 1 stub no-summary command on the ABRs.
ROUTE v1. 0 3-15
The figure in this slide shows how the same routing table looks if the area is configured as a totally stubby area. Notice that routers in the totally stubby area have the smallest routing tables of all the configurations you have seen so far. Intra-area routes are maintained. Interarea and external routes are not visible in the routing tables for each stub area, but are accessible via the intra-area default routes for that stub area. ABR routers block interarea and external LSAs and insert the default routes instead.
3-201
Defining and Implementing a Not-So-Stubby-Area and Totally NSSA in OSPF

This topic defines OSPF not-so-stubby areas (NSSAs) and describes how to configure them.
OSPF Not-So-Stubby Areas (NSSAs)

NSSA breaks stub area rules ASBR is allowed inside LSA type 7 sent by ASBR ABR converts LSA type 7 to LSA type 5 ABR sends the default route into NSSA instead of external (LSA type 5) routes
ROUTE v1. 0 3-16
The OSPF NSSA feature is described by RFC 3101 and was first introduced in Cisco IOS Software Release 11.2. It 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. Redistribution into an NSSA creates a special type of LSA known as a type 7 LSA, which can exist only in an NSSA. An NSSA ASBR (router ASBR1 in the figure in this slide) generates this LSA, and an NSSA ABR translates it into a type 5 LSA, which gets propagated into the OSPF domain. Type 7 LSAs have a propagate (P) bit in the LSA header to prevent propagation loops between the NSSA and the backbone area. The NSSA retains the other stub area features; the ABR sends a default route into the NSSA instead of external routes from other ASBRs (for example from ASBR2 in the figure in this slide). The type 7 LSA is described in the routing table as an O N2 or O N1 (N means NSSA). N1 means that the metric is calculated like external type 1; N2 means that the metric is calculated like external type 2. The default is O N2.
Note The external type 1 (E1) metric adds external and internal costs together to reflect the whole cost to the destination. The external type 2 (E2) metric takes only the external cost, which is reflected in the OSPF cost.
3-202
OSPF Totally NSSA Areas

ABR is blocking Type 3, 4, 5 LSAs ABR is sending the default route into the NSSA instead This is a Cisco proprietary feature
ROUTE v1. 0 3-17
The OSPF totally NSSA feature is an extension to the NSSA feature like the totally stubby feature is an extension to the stub area feature. It is a Cisco proprietary feature that blocks type 3, 4, and 5 LSAs. A single default route replaces both inbound-external (type 5) LSAs and summary (type 3 and 4) LSAs in the totally NSSA area. The ABRs for the totally NSSA area must be configured to prevent the flooding of summary routes for other areas into the NSSA area. Only ABR routers control the propagation of type 3 LSAs from the backbone. If ABR router is configured on any other routers in the area, it will have no effect at all.
3-203
Totally NSSA Area Configuration
This command turns on NSSA area networking Set on all routers in the NSSA area
The first command defines the totally NSSA area on ABRs The second command defines the cost of a default route sent into the NSSA area (default is 1)
ROUTE v1. 0 3-18
Once all the required information is defined, you must complete the following tasks to configure OSPF totally NSSAs: Configure all routers in the NSSA area as NSSA routers Configure the ABR as totally not-so-stubby (for configuration of the totally NSSA feature only) Configure the cost for the default route on the ABR router (optional).
Note Default cost of the default route is 1
To configure an area as an NSSA, you must configure all routers inside the area for NSSA functionality. The area nssa router configuration mode command is used to define each router in the NSSA area as not-so-stubby. Each ABR router must be configured for NSSA, too.
Note Remember that all routers in the NSSA must be configured with the area nssa command in order to form adjacencies.
Totally NSSA functionality requires one more step; you must configure each ABR router for totally NSSA functionality. The area nssa command with the no-summary keyword at the end is used to define the ABR router as a totally not-so-stubby. By default, the ABR 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. For more details about the area nssa and area default-cost commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-204
NSSA Configuration Example
ROUTE v1. 0 3-19
In the figure in this slide, router ASBR is the Autonomous System Boundary Router (ASBR) that is redistributing Routing Information Protocol (RIP) routes into area 1, the NSSA. Router ABR is the NSSA Area Border Router (ABR). This router converts LSA type 7 into type 5 for advertisement into the backbone area 0. Router ABR is also configured to summarize the type 5 LSAs that originate from the RIP network: The 172.16.0.0 subnets will be summarized to 172.16.0.0/16 and advertised into area 0. To cause router ABR (the NSSA ABR) to generate an O *N2 default route (O *N2 0.0.0.0/0) into the NSSA, use the area nssa command with the default-information-originate option on router R2. For more details about the area nssa command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-205
Totally NSSA Configuration Example
ROUTE v1. 0 3-20
In the figure, the ABR router is using the area 1 nssa no-summary command. This command works the same as the totally stubby technique. A single default route replaces both inboundexternal (type 5) LSAs and summary (type 3 and 4) LSAs into the area. The NSSA ABR, which is router ABR, automatically generates the O *N2 default route into the NSSA area with the no-summary option configured at the ABR, so the defaultinformation-originate option is not required. All other routers in the NSSA area only require the area 1 nssa command. The totally not-so-stubby configuration is a Cisco proprietary feature like the totally stubby configuration.
3-206
Example of Different Areas
ROUTE v1. 0 3-21
The figure in this slide shows different area types as follows: Normal area accepts link updates, summaries, and external routes. Stub area does not accept external LSAs. Totally Stubby area does not accept summary or external LSAs. NSSA area does not accept external LSAs, but allows ASBR. Totally NSSA area does not accept summary or external LSAs, but allows ASBR.
3-207
Verifying All OSPF Area Types

This topic describes how to verify all types of OSPF stub areas.
show Commands for Stub and NSSA
Displays which areas are normal, stub, or NSSA
Displays the details of the LSAs
Displays the details of each LSA type 7 update in the database
Displays all routes

The show commands in the figure are used to display information about all of the types of stub areas that may be configured.
3-208
Summary
Summary
There are several OSPF area types: normal, backbone, stub, totally stubby, NSSA, and totally NSSA. Use the area area-id stub command to define an area as stubby. Use the area area-id stub command with the no-summary keyword on the ABR only to define an area as totally stubby. 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. Use the area area-id nssa command to define an area as NSSA. Use the show ip ospf, show ip ospf database , and show ip route commands to verify all types of stub areas. Use the show ip ospf database nssa-external command to display details of type 7 LSAs.
3-209
3-210
Lesson 10
Lab 3-4 Debrief

Overview
In Lab 3-4, students configure and verify OSPF special area types. After performing an initial examination of OSPF, the routing information, and the IP routing table, they discover that the routers in each OSPF area are announcing their own subnets and external routes are included in OSPF. In order to minimize the OSPF routing information in area 24, students convert the area into an OSPF stub area. The results do not meet expectations, so students perform additional optimization by converting the area into a totally-stub area. At the same time, students must reduce OSPF information in area 3, as well, by converting area 3 into a totally not-so-stubby area (NSSA).
Objectives
Upon completing this lesson, you will be able to configure and verify the OSPF special area types. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

Lab Topology
ROUTE v1. 03-2
The figure in the slide presents the physical lab topology used for Lab 3-4: Configure and verify OSPF special area types. The topology uses four pod routers and one backbone router. Based on this topology and the OSPF routing protocol configuration, several internal and external OSPF routes exist in the IP routing table in all routers in the different areas. Optimization is required to make the IP routing tables smaller. One of the solutions is to change the area types, which will limit the amount of information exchanged between the areas and replace many updates with a summary route.
3-212

Task 1: Examining OSPF Routing Information How can you verify the operation of an OSPF routing protocol? What you can see by observing OSPF neighbors, the OSPF database, OSPF interfaces, and the IP routing table? Task 2: Optimizing OSPF Routing for Area 24 What steps are required to restrict OSPF from announcing information about OSPF external routers, while preserving the insertion of internal routes from other areas? Task 3: Minimizing OSPF Information in Area 24 What steps are also required to restrict OSPF from announcing information about OSPF internal routers from other OSPF areas?
ROUTE v1. 03-3
3-213

Task 4: Reducing OSPF Information in Area 3 What steps are required to minimize the sizes of the OSPF link-state database and IP routing table on a router inside the area in such a way that only information about the area announced routes (internal or external) is allowed and redistribution of external routes is preserved.
ROUTE v1. 03-4
In the first task, you examine OSPF routing information. Your pod is preconfigured with the OSPF configuration. The steps you must follow in order to optimize the OSPF routing protocol are in the following tasks. In the second task, you configure the optimization for OSPF Routing in area 24. Optimization prevents OSPF from announcing information about the OSPF external routers while preserving the insertion of the internal routes from other areas. You do this by configuring a stub area. In the third task, you minimize the OSPF information in area 24. You must optimize the IP routing table by preventing OSPF from announcing information about the OSPF internal routers from other OSPF areas. You do this by configuring a totally-stubby area. In the fourth task, you must reduce the size of the OSPF link-state database and IP routing table on the router inside area 3. You must allow only information about the routes announced by the area (internal and external). At the same time, you must preserve the redistribution of external routes. You do this by configuring a totally not-so-stubby area (totally NSSA).
3-214
Verification
Did you have enough information to create an implementation plan? Were you able to define the OSPF topology and content of the IP routing table? After task 2, were external routes from other areas are suppressed and internal routes, while internal routes remained in the IP routing table and were injectable? After task 3, were external and internal routes from other areas suppressed? After task 4, were external and internal routes from other areas prevented from being injected, while redistribution of external routes was allowed?
ROUTE v1. 03-5
To verify the implementation process for configuring OSPF operations, answer the following questions: Did you have enough information to create an implementation plan? Were you able to define the OSPF topology and content of the IP routing table? After task 2, were external routes from other areas are suppressed and internal routes, while internal routes remained in the IP routing table and were injectable? After task 3, were external and internal routes from other areas suppressed? After task 4, were external and internal routes from other areas prevented from being injected, while redistribution of external routes was allowed?
3-215
Checkpoints
Examine the IP routing information exchanged by routers configured with the OSPF routing protocol. Change the area type to suppress external routes from other areas to be injected. Check the IP routing table and OSPF database for verification. Change the area type to suppress external and internal routes from other areas to be injected. Check the IP routing table and OSPF database for verification. Change the area type to suppress external and internal routes but allow the injection of external routes into the area. Check the IP routing table and OSPF database for verification.
ROUTE v1. 03-6
With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Examine the IP routing information exchanged by routers configured with the OSPF routing protocol. Change the area type to suppress external routes from other areas to be injected. Check the IP routing table and OSPF database for verification. Change the area type to suppress external and internal routes from other areas to be injected. Check the IP routing table and OSPF database for verification. Change the area type to suppress external and internal routes but allow injection of external routes into the area. Check the IP routing table and OSPF database for verification.
3-216

A Sample Solution
The IP routing table is verified for OSPF routes. The existing configuration of the area type for area 24 has been changed from normal to stub and then to totally-stubby in order to manipulate the insertion of routes into the area. The existing configuration for area 3 has been changed to a totally not-so-stubby (NSSA) area in order to manipulate the insertion of routes into the area.
ROUTE v1. 03-7
A sample solution includes implementation details and details for each task of the implementation plan. Different solutions are possible; the figure in the slide points out a few details of a successful configuration. Proper implementation of route redistribution between multiple IP routing protocols includes the following details: The IP routing table is verified for OSPF routes. The configuration of the area type for area 24 has been changed from normal to stub and then to totally-stubby in order to manipulate the insertion of routes into the area. The configuration for area 3 has been changed to a totally not-so-stubby area (totally NSSA) in order to manipulate the insertion of routes into the area.
3-217
Summarization and filtering can be used in order to manipulate the insertion of routes into a specific area. Because changing the routing protocol is not a realistic solution, you can implement static and default routes with filtering instead.
ROUTE v1. 03-8
In order to decrease the size of the routing table and to prevent the insertion of routes, you can use summarization together with the filtering of routes. In order to provide reachability in the network, you can use several routing protocols. Changing the routing protocol is not a realistic solution, as the network system administrators will not redesign and reconfigure the whole network for another routing protocol. Sometimes reconfiguration is not even possible, because not all devices may support the desired routing protocol. Instead, static and default routes can be configured together with route filtering. Filtering prevents routing updates from being exchanged, and the static and default routes provide reachability. Static routes are not a scalable solution.
3-218
Q and A
How you can verify OSPF routes and the OSPF topology? What can you change in OSPF to manipulate which routes are inserted into an area? Which OSPF area type suppresses external routes from other areas to be inserted? Which OSPF area type suppresses external and internal routes from other areas to be inserted? Which area type suppresses external routes from other areas to be inserted, but allows redistribution of external routes? Which area type suppresses external and internal routes from other areas to be inserted, but allows redistribution of external routes?
ROUTE v1. 03-9
You can verify the IP routing table by observing the contents of the IP routing table for OSPF routes. You can verify the operation of the OSPF routing protocol by checking the information of OSPF neighbors, the OSPF database, OSPF interfaces, and the IP routing table. You can use summarization and OSPF area types to manipulate which routes are inserted into the area. The stub OSPF area type suppresses external routes from other areas to be inserted. The totally-stub OSPF area type suppresses external and internal routes from other areas to be inserted. The not-so-stubby (NSSA) OSPF area type suppresses external routes from other areas to be inserted, but allows redistribution of external routes. The totally NSSA OSPF area type suppresses external and internal routes from other areas to be inserted, but allows redistribution of external routes.
3-219
Summary
Summary
The IP routing table provides information that can be used to verify the proper configuration of different OSPF area types. To optimize OSPF you must configure area 24 as an OSPF stub area. To minimize OSPF information in area 24, you must configure an OSPF totally-stub area. To reduce OSPF information in area 3, you must configure an OSPF totally not-so-stubby (NSSA) area.
RO UTE v 1.03-10
3-220
Lesson 11
Configuring and Verifying OSPF Authentication

Overview
You can prevent your router from receiving fraudulent route updates by configuring neighbor router authentication. You can configure Open Shortest Path First Protocol (OSPF) neighbor authentication (also called neighbor router authentication or route authentication) in such a way that routers can participate in routing based on predefined passwords. This lesson describes the two types of OSPF authentications, how to configure, and verify them.
Objectives
Upon completing this lesson, you will be able to implement authentication in an OSPF network. This ability includes being able to meet these objectives: Define types of OSPF authentication Implement simple password authentication for OSPF Configure MD5 authentication for OSPF Troubleshoot authentication for OSPF
Types of OSPF Authentication

This topic describes two types of authentication used in OSPF.
OSPF Authentication Types

OSPF supports two types of authentication: Simple password (or plaintext) authentication MD5 authentication The router generates and checks every OSPF packet. The source of each routing update packet received is authenticated. Each participating neighbor must have the same key (password) configured.
ROUTE v1.03-2
OSPF neighbor authentication (also called neighbor router authentication or route authentication) can be configured in such a way that routers participate in routing based on predefined passwords. Recall that once you have configured neighbor authentication on a router, the router authenticates the source of each routing update packet that it receives. It does this by exchanging an authenticating key (sometimes referred to as a password) that is known to both the sending and the receiving router. By default, OSPF is not using authentication, which means that routing exchanges over a network are not authenticated. OSPF supports two authentication methods: Simple password or plaintext authentication Message Digest 5 (MD5) authentication OSPF MD5 authentication includes a non-decreasing sequence number in each OSPF packet to protect against replay attacks.
3-222
Implementing Simple Password Authentication for OSPF

This topic describes how to configure simple password authentication.
Configure Simple Password Authentication for OSPF

This command defines a password to be used with a neighboring router. The neighboring router must have the same password configured.

Specifies the authentication type for an interface or the authentication type for an area.
ROUTE v1.03-3
To implement OSPF authentication, you must create an implementation plan. The implementation plan includes two main steps for the configuration of authentication: Key (password) configuration Authentication-type configuration The first step to configure OSPF simple password authentication is to configure the key (password). Assign a password to be used with the neighboring routers that use OSPF simple password authentication by issuing the ip ospf authentication-key interface configuration command, as shown in the figure.
Note In Cisco IOS Software Release 12.4, the router will give a warning message if you try to configure a password longer than eight characters; only the first eight characters will be used. Some earlier Cisco IOS releases did not provide this warning.
The password created by this command is used as a key that is inserted directly into the OSPF header when Cisco IOS software originates routing protocol packets. A separate password can be assigned to each network on a per-interface basis. All neighboring routers on the same network must have the same password to be able to exchange OSPF information.
3-223
Note
If the service password-encryption command is not used when configuring OSPF authentication, the key will be stored as plaintext in the router configuration. If you configure the service password-encryption command, the key will be stored and displayed in an encrypted form; when it is displayed, there will be an encryption-type of 7 specified before the encrypted key.
The second step to configure OSPF simple password authentication is to configure the authentication type. Specify the authentication type using the ip ospf authentication interface configuration command, as shown in the figure. The ip ospf authentication command was introduced in Cisco IOS Software Release 12.0. For backward compatibility, the authentication type for an area is still supported. If the authentication type is not specified for an interface, the authentication type for the area will be used (the area default is null authentication). To enable authentication for an OSPF area, use the area authentication router configuration command. For more details about the ip ospf authentication-key, ip ospf authentication, and area authentication commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-224
Simple Password Authentication Configuration Example
ROUTE v1.03-4
The figure in the slide shows the network used to illustrate the configuration, verification, and troubleshooting of simple password authentication. The configuration of the router R1 is shown in this figure. Simple password authentication is configured on interface serial 0/0/1. The ip ospf authentication command is used without the additional keywords. The interface is configured with an authentication key of plainkey. The configuration of router R2 is shown in this figure as well. You should notice that the connecting interfaces on both routers R1 and R2 are configured with the same authentication key. The only difference is that router R2 authentication is configured for the whole area 0 and authentication on router R1 is configured on the serial0/0/1 interface only.
3-225
Simple Password Authentication Configuration for Virtual Links
ROUTE v1.03-5
The figure in the slide shows the network used to illustrate the configuration of simple password authentication for virtual links. The configuration of routers R1 and R3 is similar. Plaintext authentication is configured for the whole area 0 and the virtual link to area 0 is created via transit area 1 with plaintext authentication enabled. The authentication key cisco is configured on both routers.
3-226
Verifying Simple Password Authentication
ROUTE v1.03-6
The figure shows the output of the show ip ospf interface and ping commands. The show ip ospf interface command shows that router R1 has one adjacent neighbor and simple password authentication is enabled. The results of the ping command to the router R2 loopback interface address are also displayed, to illustrate that the link is working. This and proves that devices are accessible. For more details about the show ip ospf interface command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html For more details about the ping command, please check the Cisco IOS Configuration Fundamentals Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_book.html
3-227
Configuring MD5 Authentication for OSPF

This topic describes how to configure MD5 authentication.
Configure OSPF MD5 Authentication

Defines a key ID and key to be used with a neighboring router. Neighboring router must have the same combination of key ID and key configured.

Specifies the authentication type for an interface or the authentication type for an area.
ROUTE v1.03-7
The first step when configuring OSPF MD5 authentication is to configure the key ID and the key (password). You can assign a key ID and key to be used with neighboring routers that use OSPF MD5 authentication using the ip ospf message-digest-key command, as shown in the figure in the slide.
Note In Cisco IOS Software Release 12.4, the router will give a warning message if you try to configure a password longer than 16 characters; only the first 16 characters will be used. Some earlier Cisco IOS releases did not provide this warning.
The key and the key ID specified in this command are used to generate a message digest (also called a hash) of each OSPF packet; the message digest is appended to the packet. A separate password can be assigned to each network on a per-interface basis. Usually, one key per interface is used to generate authentication information when sending packets and to authenticate incoming packets. All neighboring routers on the same network must have the same password to be able to exchange OSPF information; in other words, the same key ID on the neighbor router must have the same key value. The key ID allows for uninterrupted transitions between keys, which is helpful for administrators who wish to change the OSPF password without disrupting communication. If an interface is configured with a new key, the router will send multiple copies of the same packet, each authenticated by different keys. The router will stop sending duplicate packets when it detects that all of its neighbors have adopted the new key.
3-228
For illustrating the process of changing keys, suppose the current configuration is as follows:

Then you change the configuration to the following:

The system assumes that its neighbors do not have the new key yet, so it begins a rollover process. It sends multiple copies of the same packet, each authenticated by different keys. In this example, the system sends out two copies of the same packet, the first one authenticated by key 100 and the second one authenticated by key 101. Rollover allows neighboring routers to continue communication while the network administrator is updating them with the new key. Rollover stops when the local system finds that all its neighbors know the new key. The system detects that a neighbor has the new key when it receives packets from the neighbor authenticated by the new key. After all neighbors have been updated with the new key, the old key should be removed. In this example, you would enter the following:

Then only key 101 will be used for authentication on FastEthernet interface 0/0.
Note You should not keep more than one key per interface. Every time you add a new key, you should remove the old key to prevent the local system from continuing to communicate with a hostile system that knows the old key.If you do not use the service password-encryption command when configuring OSPF authentication, the key will be stored as plaintext in the router configuration. If you use the service password-encryption command, the key will be stored and displayed in an encrypted form; when it is displayed, there will be an encryptiontype of 7 specified before the encrypted key.
The second step when configuring OSPF MD5 authentication is to configure the authentication type. Specify the authentication type using the ip ospf authentication command as shown in the figure in the slide. For MD5 authentication, use the ip ospf authentication command with the message-digest parameter. Before using this command, configure the message digest key for the interface with the ip ospf message-digest-key command. Recall that the ip ospf authentication command was introduced in Cisco IOS Software Release 12.0. As with simple password authentication, the MD5 authentication type for an area is still supported using the area authentication router configuration command, for backward compatibility. For more details about the ip ospf message-digest-key, ip ospf authentication, and area authentication commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
3-229
OSPF MD5 Authentication Configuration Example
ROUTE v1.03-8
The figure in the slide shows the network used to illustrate the configuration, verification, and troubleshooting of simple password authentication. The configuration of router R1 is shown in this figure in the slide. MD5 authentication is configured on interface serial 0/0/1. The ip ospf authentication command is used with the message-digest keyword. The interface is configured with authentication key number 1 set to mysecret. The configuration of router R2 is shown in this figure, as well. You should notice that the connecting interfaces on both routers R1 and R2 are configured with the same authentication key ID and the key. The authentication configuration on router R2 is enabled for the whole area 0, not only on the serial 0/0/1 interface as with router R1.
3-230
Verifying MD5 Authentication
ROUTE v1.03-9
The figure shows the output of the show ip ospf interface and ping commands. The show ip ospf interface command shows that router R1 has one adjacent neighbor and message digest authentication is enabled. The results of a ping command to the router R2 loopback interface address are also displayed, to illustrate that the link is working. This proves the accessibility of devices.
3-231
Troubleshooting Authentication for OSPF

This topic describes how to verify and troubleshoot authentication and focuses on simple password authentication.
Authentication Verification
Problems include the following:
Authentication problems: Authentication is not configured on both sides. A different authentication type is configured on either side. Different passwords are configured on either side.
This command displays the OSPF adjacency-related events.
ROUTE v1. 0 3-10
Authentication for OSPF routing packets prevents your router from receiving fraudulent route updates. Once authentication is configured, all the neighbors must use the same password and authentication type. If the authentication type is not the same for both neighbors, or one neighbor is not configured at all, then OSPF will not be able to exchange routing updates successfully. The same applies for the password, which must be the same for both neighboring routers. After OSPF configuration, the authentication verification, authentication type, and password must be observed. Once the authentication configuration is correct, an OSPF neighborship is established, routing updates are exchanged, and OSPF routes are entered in the IP routing table. If the destinations are not accessible, or there are no neighbors or OSPF routes or both in the IP routing table, then you can use debugging to obtain additional information about OSPF authentication problems. To display information on OSPF related adjacency events, such as packets being dropped due to authentication problems, use the debug ip ospf adj command from privileged EXEC mode. For more details about the debug ip ospf adj command, please check the Cisco IOS Debug Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/debug/command/reference/db_book.html
3-232
Successful Simple Password Authentication Verification

Authentication is configured correctly
ROUTE v1. 0 3-11
The following output of the debug ip ospf adj command (part of which is shown in the figure) illustrates successful simple password authentication on router R1 after the serial 0/0/1 interface, on which authentication has been configured, comes up:

3-233
The output of the show ip ospf neighbor command shown in the figure illustrates that router R1 has successfully formed an adjacency with router R2.
3-234
Troubleshooting Simple Password Authentication Problems

Simple authentication is not configured on router R2
Different keys on routers R1 and R2
ROUTE v1. 0 3-12
If simple password authentication is configured on router R1s serial 0/0/1 interface but no authentication is configured on router R2s serial 0/0/1 interface, the routers will not be able to form an adjacency over that link. The output of the debug ip ospf adj command shown in the upper portion of the figure illustrates that the routers report a mismatch in authentication type; no OSPF packets will be sent between the neighbors.
Note The different types of authentication have these type codes: nulltype 0, simple passwordtype 1, MD5type 2.
If simple password authentication is configured on router R1s serial 0/0/1 interface and on the router R2s serial 0/0/1 interface, but with different passwords, the routers will not be able to form an adjacency over that link. The output of the debug ip ospf adj command shown in the lower portion of the figure illustrates that the routers report an authentication key mismatch; no OSPF packets will be sent between the neighbors.
3-235
Successful MD5 Authentication Verification

Authentication is configured correctly
ROUTE v1. 0 3-13
The following output of the debug ip ospf adj command (part of which is shown in the figure in the slide) illustrates a successful MD5 authentication on router R1 after the serial 0/0/1 interface, on which authentication has been configured, comes up:

3-236
The output of the show ip ospf neighbor command shown in the figure illustrates that router R1 has successfully formed an adjacency with router R2.
3-237
Troubleshooting MD5 Authentication Problems

MD5 authentication configured on both routers Router R1 has key 1 and router R2 has key 2, both with the same passwords:
ROUTE v1. 0 3-14
If MD5 authentication is configured on router R1s serial 0/0/1 interface and on the router R2s serial 0/0/1 interface, but router R1 has key 1 and router R2 has key 2, the routers will not be able to form an adjacency over that link, even though both have the same passwords configured. The output of the debug ip ospf adj command shown in the figure illustrates that the routers report an authentication key mismatch. No OSPF packets will be sent between the neighbors.
3-238
Summary
Summary
When authentication is configured, the router generates and checks every OSPF packet and authenticates the source of each routing update packet that it receives. OSPF supports two types of authentication: Simple password (or plaintext) authentication: The router sends an OSPF packet and key. MD5 authentication: The router generates a message digest, or hash, of the key, key ID, and message. The message digest is sent with the packet; the key is not sent. To configure simple password authentication, use the ip ospf authentication-key password command and the ip ospf authentication command.
ROUTE v1. 0 3-15
Summary (Cont.)
To configure MD5 authentication, use the ip ospf messagedigest-key key-id md5 key command and the ip ospf authentication message-digest command. Use the show ip ospf neighbor, show ip route, ping, and debug ip ospf adj commands to verify and troubleshoot both types of authentication. With MD5 authentication, the debug ip ospf adj command output indicates the key ID sent.
ROUTE v1. 0 3-16
3-239
3-240
Lesson 12
Lab 3-5 Debrief

Overview
In Lab 3-5, students configure and verify OSPF authentication.
Objectives
Upon completing this lesson, you will be able to configure and verify OSPF authentication. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

Lab Topology
ROUTE v1. 03-2
The figure in the slide presents the physical lab topology used for Lab 3-5: Configure and Verify OSPF Authentication. The topology uses four pod routers and one backbone router. Based on the topology, students will identify the required parameters and configure OSPF authentication in order to establish a neighbor relationship and secure exchange of routing packets. The backbone routers are preconfigured with authentication and the configuration of the pod routers must match. For the rest of the pod routers, the proper configuration must be applied.
3-242

Task 1: Examining OSPF Routing Information How can you verify the operation of an OSPF routing protocol? What can you see by observing the OSPF neighbors, OSPF database, OSPF interfaces, and IP routing table? Task 2: Enabling OSPF Link Authentication How is OSPF link authentication between two routers implemented? Task 3: Enabling OSPF Area Authentication How is OSPF area authentication implemented on a router?
ROUTE v1. 03-3
In the first task, you will examine the OSPF routing information. Your pod is preconfigured with the OSPF configuration and the proper configuration steps are needed in order to configure authentication in the following tasks. In the second task, you must enable OSPF link authentication on the LAN segment between routers R2 and R4. You must use the authentication that provides the highest level of security. In the third task, you must enable OSPF area authentication in the whole area. Again, you must use the authentication that provides the highest level of security.
3-243
Verification
Did you have enough information to create an implementation plan? Were you able to define the OSPF topology and the contents of the IP routing table? Verify that after link authentication configuration, the adjacencies, IP routing table, and OSPF database are included into OSPF. Examine the OSPF link authentication process. Verify that after link authentication configuration, the adjacencies, IP routing table, and OSPF database are included into OSPF. Examine the OSPF area authentication process. Verify that when a router with an improper or missing OSPF authentication is connected to the area, an OSPF adjacency is not set up.
ROUTE v1. 03-4
To verify the implementation process for configuring OSPF authentication, answer the following questions: Did you have enough information to create an implementation plan? Were you able to define the OSPF topology and the content of the IP routing table? After link authentication configuration, were all the adjacencies, the IP routing table, and the OSPF database included in OSPF? What do you see when you examine the OSPF link authentication process? After area authentication configuration, were all the adjacencies, the IP routing table, and the OSPF database included in OSPF? What do you see when you examine the OSPF link authentication process? When a router with an improper or missing OSPF authentication is connected to the area, is it prevented from establishing an OSPF adjacency?
3-244
Checkpoints
Examine the IP routing information exchanged by routers configured with the OSPF routing protocol. Configure OSPF link authentication on the LAN segment. Check the IP routing table and OSPF database to verify that the adjacency on that link is up and link is included in the OSPF process. Configure OSPF area authentication. Check the IP routing table and OSPF database to verify that the adjacencies in the area are up and the links are included in the OSPF process. Check for the OSPF information in the router where area authentication is not configured.
ROUTE v1. 03-5
With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Examine the IP routing information exchanged by routers configured with the OSPF routing protocol. Configure OSPF link authentication on a LAN segment. Check the IP routing table and OSPF database to verify that an adjacencies on the links are up and the links included in the OSPF process. Configure OSPF area authentication. Check the IP routing table and OSPF database to verify that the adjacencies in the area are up and the links are included in the OSPF process. Check for OSPF information in the router where the area authentication is not configured.
3-245

A Sample Solution
The OSPF topology and OSPF operation are verified, along with the IP routing table, which shows the OSPF routes. OSPF link authentication is configured on the LAN segment. OSPF area authentication is configured in the whole area. MD5 authentication is used as the highest security provided in the OSPF.
ROUTE v1. 03-6
A sample solution includes implementation details and details for each task of the implementation plan. Different solutions are possible; the figure points out a few details of a successful configuration. Proper implementation of route redistribution between multiple IP routing protocols includes the following details: The OSPF topology and OSPF operation are verified, as well as the IP routing table, which shows OSPF routes. OSPF link authentication is configured on the LAN segment between routers R2 and R4. OSPF area authentication is configured in the whole area. MD5 authentication is used as the highest security provided in the OSPF.
3-246
Different authentication types can be used (clear text instead of MD5). Different areas and redistribution can be used to control the updates, but they do not provide authentication.
ROUTE v1. 03-7
In order to provide reachability and authentication, you can select between MD5 and simple authentication. In both cases, authentication provides a level of security in the network, but MD5 authentication is more secure. In order to control the routing updates, you can use several areas and redistribution. The use of different areas, by itself, does not provide authentication, but you can use a different authentication key in each area. Redistribution does not provide authentication either, but it provides a way for you to control routing updates, if this is a concern.
3-247
Q and A
How can you verify the OSPF routes in an IP routing table? How many authentication types are supported by OSPF? How do you configure OSPF link authentication? How do you configure OSPF area authentication? Is OSPF area authentication applied to all OSPF-enabled interfaces on the router where it is configured?
ROUTE v1. 03-8
You can verify OSPF routes in the IP routing table; all the routes with the letter O in front of them represent the OSPF routes. OSPF supports two types of authentication: simple and MD5 authentication. You can configure link authentication on the interface, along with the authentication key used on both neighboring routers. You can configure area authentication in OSPF router configuration mode and apply it to the whole area. You need an authentication key on each interface facing the OSPF neighbor. Area authentication is enabled for the whole area. The interfaces used must also be configured with the authentication key.
3-248
Summary
Summary
IP routing information exchanged by routers that are configured with the OSPF routing protocol is examined. Simple OSPF authentication is configured between routers on a LAN segment. You do not only deploy OSPF area authentication on each link, but also in the whole area, for which all OSPF interfaces are involved.
ROUTE v1. 03-9
3-249
3-250
Module Summary
Module Summary
Open Shortest Path First (OSPF) protocol is one of the most commonly used link-state IP routing protocols in networking. It is an open standard and offers quick convergence and the ability to scale large networks. OSPF uses five types of routing protocol packets and six common link-state advertisements (LSAs). The routing protocol packets are hello, database description, link-state request, linkstate update, and link-state acknowledgement. LSAs are router link (LSA type 1), network link (LSA type 2), network summary (LSA type 3), ASBR summary (LSA type 4), external (LSA type 5), and NSSA external (LSA type 7). OSPF has the following three network types: point-to-point, broadcast, and nonbroadcast multiaccess (NBMA), for which NBMA supports five modes of OSPF operation: NBMA, point-tomultipoint, point-to-multipoint nonbroadcast, broadcast, and point-to-point.
Module Summary (Cont.)

The configuration of OSPF is a two-step process: Enter the OSPF configuration with the router ospf command. Use the network command to describe which interfaces will run OSPF in which area. Route summarization reduces OSPF LSA flooding and the routing table size, which reduces memory and CPU utilization on routers. The OSPF area types supported are backbone area, normal area, stub area, totally stubby area, and not-so-stubby area (NSSA). Stub area techniques improve OSPF performance by reducing the amount of LSA flooding. OSPF supports two types of authentication: Simple password (or plaintext) authentication MD5 authentication
ROUTE v1. 03-2
Open Shortest Path First Protocol (OSPF) is one of the most commonly used interior gateway protocols in IP networking. OSPF is a complex, open-standard protocol made up of several protocol handshakes, database advertisements, and packet types.
3-252
Module Self-Check
Use the questions here to review what you learned in this module. The correct answers and solutions are found in the Module Self-Check Answer Key. Q1) All of these tables are maintained by a link-state routing protocol except which one? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) Q2) routing topology update neighbor
The memory needed to maintain tables is one disadvantage of link-state protocols. (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) true false
Q3)
Match each table to its function. (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) _____ _____ _____ routing topology neighbor 1. stores LSAs 2. stores adjacencies 3. stores best paths
Q4)
Which term refers to the router that connects area 0 to a nonbackbone area? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) Area Boundary Router Area Border Router Autonomous System Boundary Router backbone router
Q5)
What is the recommended guideline for the maximum number of routers per OSPF area? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) 50 10 200 500
Q6)
Which OSPF packet helps form neighbor adjacencies? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) exchange packet hello packet neighbor discovery packet adjacency packet
3-253
Q7)
Which criterion does SPF use to determine the best path? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) lowest delay highest bandwidth lowest total cost of the route total bandwidth of the route
Q8)
Which table is populated as a result of SPF calculations? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) topology routing adjacency neighbor
Q9)
Cisco recommends no more than _____ area or areas per ABR in addition to area 0. (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) one two four eight
Q10)
An area border router maintains _____. (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) a separate database for each area with which it is connected a single database for all areas two databases: one for the backbone and one for all other areas a separate routing table for each area
Q11)
In a multiarea network, any area can be the backbone area, although it is most often area 0. (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) true false
Q12)
When an OSPF router receives an LSA, it is installed in the _____. (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) neighbor table topology table routing table update table
Q13)
An OSPF router receives an LSA and checks the sequence number of the LSA. This number matches the sequence number of an LSA that the receiving router already has. What does the receiving router do with the received LSA? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) ignores the LSA adds the LSA to the database sends the newer LSU to the source router floods the LSA to the other routers
3-254
Q14)
An OSPF router receives an LSA. The router checks the sequence number of the LSA and finds that this number is higher than the sequence number it already has. Which two tasks does the router perform with the LSA? (Choose two.) (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) ignores the LSA adds the LSA to the database sends the newer LSU to the source router floods the LSA to the other routers
Q15)
An OSPF router receives an LSA. The router checks the sequence number of the LSA and finds that this number is lower than the sequence number it already has. What does the router do with the LSA? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) ignores the LSA adds the LSA to the database sends the newer LSU to the source router floods the LSA to the other routers
Q16)
Each LSA has its own age timer. By default, how long does an LSA wait before requiring an update? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) 30 seconds 1 minute 30 minutes 1 hour
Q17)
A network engineer must configure the OSPF routing protocol in the network. The engineer needs all of these to implement the OSPF routing protocol except which one? (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) C) D) implementation plan verification plan the Cisco IOS Router Configuration Guide for the OSPF routing protocol documentation of the OSPF implementation
Q18)
During planning for basic OSPF implementation, the network engineer must go through the following steps: define the network requirements, gather the required parameters, define the OSPF areas and routing, configure basic OSPF, verify the OSPF configuration, and complete the documentation. (Source: Planning Routing Implementations with OSPF as a Scalable Routing Protocol) A) B) true false
Q19)
What is the IP protocol number for OSPF packets? (Source: How OSPF Packet Processes Work) A) B) C) D) 89 86 20 76
3-255
Q20)
All of these are OSPF packet types except which one? (Source: How OSPF Packet Processes Work) A) B) C) D) E) F) LSU LSR DBD LSAck hello query
Q21)
Which multicast address does the OSPF Hello protocol use? (Source: How OSPF Packet Processes Work) A) B) C) D) 224.0.0.5 224.0.0.6 224.0.0.7 224.0.0.8
Q22)
The Hello protocol sends periodic updates to ensure that a neighbor relationship is maintained between adjacent routers. (Source: How OSPF Packet Processes Work) A) B) true false
Q23)
Place the exchange protocol states in the correct order. (Source: How OSPF Packet Processes Work) A) B) C) D) E) F) G) _____ two-way _____ loading _____ down _____ full _____ exchange _____ init _____ exstart
Q24)
DBD packets are involved during which two states? (Choose two.) (Source: How OSPF Packet Processes Work) A) B) C) D) exstart loading exchange two-way
Q25)
At what interval does OSPF refresh LSAs? (Source: How OSPF Packet Processes Work) A) B) C) D) 10 seconds 30 seconds 30 minutes 1 hour
Q26)
All of these fields are in an OSPF packet header except which one? (Source: How OSPF Packet Processes Work) A) B) C) D) packet length router ID authentication type MaxAge time
3-256
Q27)
OSPF does not require a hello protocol on point-to-point links, because adjacent routers are directly connected. (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) true false
Q28)
Three routers are connected to an Ethernet LAN. One is a small router that should not take on the role of DR or BDR. How do you ensure that it never will? (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) Set the interface priority to 100. Set the interface priority to 0. Leave the interface priority set to 1 and set the priority of the other two routers to 10. Use the no designated-router command on the Ethernet interface.
Q29)
When the DR fails, the BDR automatically builds new adjacencies, exchanges databases with other routers, and takes over as DR. (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) true false
Q30)
What is the default hello interval for NBMA interfaces? (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) 10 seconds 30 seconds 120 seconds 60 seconds
Q31)
An OSPF router automatically builds adjacencies with neighboring routers on an NBMA link. (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) true false
Q32)
Which mode of OSPF operation is RFC-compliant? (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) point-to-multipoint nonbroadcast point-to-multipoint broadcast point-to-point
Q33)
Match the OSPF over Frame Relay mode of operation with its description. (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) broadcast point-to-multipoint nonbroadcast does not discover neighbors automatically discovers neighbors automatically and requires a DR and BDR election is used in partial-mesh topologies, discovers neighbors automatically, and does not require a DR and BDR election
Implementing a Scalable Multiarea Network OSPF-Based Solution 3-257
_____ 1. _____ 2. _____ 3.
Q34)
Which two OSPF over Frame Relay modes elect a DR? (Choose two.) (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) broadcast nonbroadcast point-to-multipoint point-to-point
Q35)
A point-to-point subinterface provides which two benefits for OSPF over Frame Relay? (Choose two.) (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) works with multiple vendors does not require manual configuration of neighbors does not require a DR and BDR saves on subnets
Q36)
Which statement below is true for an OSPF adjacency built over a Layer 2 MPLS VPN backbone? (Choose two.) (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) The DR and BDR are elected. The OSPF parameters must be agreed upon with service provider. Provider edge routers appear as additional routers in the customers network. The OSPF network type is multiaccess broadcast.
Q37)
Which destination IP address does OSPF use when advertising to all SPF routers? (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) 224.0.0.6 224.0.0.5 255.255.255.255 the IP address of the output interface
Q38)
What are the three types of networks defined by OSPF? (Choose three.) (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) E) point-to-point broadcast point-to-multipoint point-to-multipoint nonbroadcast nonbroadcast multiaccess
Q39)
When an OSPF adjacency is built over a Layer 3 MPLS VPN backbone, customer routers are unaware of the MPLS VPN topology. (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) true false
Q40)
The BDR, like the DR, maintains a full set of adjacencies on a broadcast link. (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) true false
3-258
Q41)
Which two OSPF over Frame Relay modes require a DR? (Choose two.) (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) point-to-point broadcast point-to-multipoint nonbroadcast
Q42)
Which two statements regarding OSPF nonbroadcast mode are correct? (Choose two.) (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) This mode requires manual neighbor commands. This mode does not use a DR and BDR. This mode uses a DR and BDR. This mode requires multiple subnets.
Q43)
When you are using an OSPF neighbor command, you must configure it under an interface. (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) true false
Q44)
Which OSPF mode requires neighbor commands? (Source: Improving Routing Performance in a Complex Enterprise Network) A) B) C) D) broadcast point-to-point point-to-multipoint point-to-multipoint nonbroadcast
Q45)
Which two commands are required for a basic OSPF configuration? (Choose two.) (Source: Configuring and Verifying OSPF Routing) A) B) C) D) network ip-address mask area area-id network ip-address wildcard-mask area area-id router ospf process-id ip router ospf
Q46)
Which OSPF show command describes a list of OSPF adjacencies? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) show ip ospf interface show ip ospf show ip route show ip ospf neighbor
Q47)
All of these techniques are used for router ID selection except which one? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) highest IP address on an interface IP address on a loopback interface lowest IP address when multiple loopback interfaces are used the router-id command
Q48)
When you use the router-id command, the router ID immediately changes to the IP address that has been entered. (Source: Configuring and Verifying OSPF Routing) A) B) true false
3-259
Q49)
Which network statement is used to configure OSPF on an interface with an IP address of 172.16.1.1 in area 0? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) network 172.16.0.0 0.0.0.255 area 0 network 172.16.1.1 0.0.0.0 area 0 network 172.16.1.1 255.255.255.255 area 0 network 172.16.0.0 0.0.255.255 area 0
Q50)
Only one OSPF process can run on a Cisco router at one time. (Source: Configuring and Verifying OSPF Routing) A) B) true false
Q51)
A router has a FastEthernet interface with an IP address of 172.16.45.1, a loopback 0 interface with an IP address of 10.3.3.3, a loopback 1 interface with an IP address of 10.2.2.2, and a router-id command with an IP address of 10.1.1.1. Which router ID will be selected? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) 172.16.45.1 10.3.3.3 10.2.2.2 10.1.1.1
Q52)
The show ip ospf neighbor command shows the FULL state on one of the two neighbors in its table. Which neighbor or neighbors will successfully exchange LSDB information? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) a neighbor in the FULL state a neighbor not in FULL state any neighbor, regardless of whether or not it is in the FULL state no neighbor, regardless of whether or not it is in the FULL state
Q53)
Which two show commands can be used to verify the OSPF router ID of a router? (Choose two.) (Source: Configuring and Verifying OSPF Routing) A) B) C) D) show ip ospf interface show ip ospf neighbor show ip ospf show ip route
Q54)
When you configure a loopback interface, you choose an IP address that is not going to be advertised by OSPF. This loopback address _____. (Source: Configuring and Verifying OSPF Routing) A) B) C) D) cannot be a router ID, because it cannot be pinged can be the router ID, even though it cannot be pinged can be the router ID and can be pinged if a private address is selected cannot be the router ID; you should always advertise loopback addresses
Q55)
Which statement describes the process ID used in the router ospf command? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) All OSPF routers in a network must have the same OSPF process ID. The OSPF process ID is an internal number; process IDs on different routers do not need to match. The OSPF process ID is similar to an AS number. There can be only one OSPF process ID in a router configuration.
3-260
Q56)
Which three benefits are derived from a multiarea design in OSPF? (Choose three.) (Source: Configuring and Verifying OSPF Routing) A) B) C) D) reduced amount LSA flooding reduced number SPF calculations reduced size of the neighbor table reduced size of the routing table
Q57)
List the four link types that a type 1 LSA defines. (Source: Configuring and Verifying OSPF Routing) A) B) C) D) ________________ ________________ ________________ ________________
Q58)
Match each LSA name with the number that corresponds to its LSA type. (Source: Configuring and Verifying OSPF Routing) A) B) C) D) E) F) G) _____ 5 _____ 2 _____ 3 and 4 _____ 6 _____ 1 _____ 911 _____ 7 external network summary multicast router opaque NSSA
Q59)
If the OSPF routing table shows an O E1 route, what does this mean? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) It is an interarea route that uses the external cost plus the interarea cost. It is an interarea route that uses the external cost only. It is an external route that uses the external cost only. It is an external route that uses the external cost plus the internal cost.
Q60)
Which two LSAs describe intra-area routing information? (Choose two.) (Source: Configuring and Verifying OSPF Routing) A) B) C) D) E) summary external 1 external 2 router network
3-261
Q61)
Where will a type 3 LSA be sent? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) only within the area it originates from within the area it originates from plus the backbone area within the area it originates from, plus between all other areas within the backbone area, plus between all other areas
Q62)
An O E1 route sums up the external metric and the interarea metric, while the O E2 route uses the external metric only. The O E1 route is the default for OSPF; the router must be configured to support O E2. (Source: Configuring and Verifying OSPF Routing) A) B) true false
Q63)
A network uses Gigabit Ethernet and you want OSPF to correctly calculate the metric using bandwidth. Which command should you use to ensure that this happens? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) ip ospf cost on the interface auto-cost reference-bandwidth under the OSPF routing process bandwidth under the interface bandwidth under the OSPF routing process
Q64)
Looking at the routing table, you notice [110/55]. What does this mean? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) The O E1 cost is 110, and the O E2 cost is 55. The administrative distance is 110, and the metric is 55. The administrative distance is 55, and the metric is 110. The total cost of the route is 165.
Q65)
What does it mean if a route in the routing table has an indicator of O? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) It is intra-area. It is interarea. It is external. It is a stub.
Q66)
What is the difference between an LSA 3 and an LSA 4? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) LSA 3 is a summary LSA, and LSA 4 is E1. LSA 3 is E1, and LSA 4 is a summary. LSA 3 is a summary for networks, and LSA 4 is a summary for ASBRs. LSA 3 is a summary for ASBRs, and LSA 4 is a summary for networks.
Q67)
By default, OSPF assigns a cost of 1 to a bandwidth of _____. (Source: Configuring and Verifying OSPF Routing) A) B) C) D) T1 1 Gb/s 100 Mb/s 10 Gb/s
3-262
Q68)
The OSPF LSDB shows an LSA with an age of 1799. What does this mean? (Source: Configuring and Verifying OSPF Routing) A) B) C) D) The LSA is going to age out in 1 second. It has been 1799 minutes since the last update. The LSA will be refreshed in 1 second. The LSA was just refreshed, and another refresh is coming in 29 minutes and 59 seconds.
Q69)
What are the two reasons why route summarization is important? (Choose two.) (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) reduces LSA type 1 flooding reduces LSA type 3 flooding reduces the size of the routing table reduces the size of the neighbor table
Q70)
Which two features play a key role in route summarization? (Choose two.) (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) contiguous IP addressing discontinuous IP addressing FLSM VLSM
Q71)
Which command would you use to summarize routes into area 0 from the ABR? (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) summary-address area x range network area x summary
Q72)
Which command would you use to summarize routes into OSPF from the ASBR? (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) summary-address area x range network area x summary
Q73)
A default route is identified in the OSPF database as an _____. (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) E) LSA type 1 LSA type 2 LSA type 3 LSA type 4 LSA type 5
Q74)
The primary purpose of a default route is to reduce the sizes of the routing table and the LSDB. A default route avoids detailed updating of routes by inserting a single 0.0.0.0 route into the routing table, making this 0.0.0.0 route act as a gateway of last resort. (Source: Configuring and Verifying OSPF Route Summarization) A) B) true false
3-263
Q75)
When should you use the always keyword with the default-information originate command? (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) it is on by default; configuration not required when you want to send summarized routes when your default route is always in the routing table when you want the default route advertised, even if it is not in the routing table
Q76)
A summary LSA (type 3 LSA) is designed to automatically summarize a network into blocks. (Source: Configuring and Verifying OSPF Route Summarization) A) B) true false
Q77)
Route summarization reduces the flooding of which two of the following LSA types? (Choose two.) (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) E) router network summary external NSSA
Q78)
You are at the ABR of area 1 and want to classfully summarize network 172.16.32.0 through 172.16.63.0 into area 0. Write the configuration command that you would use. (Source: Configuring and Verifying OSPF Route Summarization)
Q79)
You are at the ASBR between an OSPF area 0 and an EIGRP network. EIGRP routes are being redistributed into OSPF. Write the correct summarization command to summarize the EIGRP block 172.16.32.0 through 172.16.63.0. (Source: Configuring and Verifying OSPF Route Summarization)
Q80)
It is important that you always summarize the routes from area 0 into other areas. Suboptimal path selection can occur if you do not. (Source: Configuring and Verifying OSPF Route Summarization) A) B) true false
Q81)
The area range command has an optional not-advertise parameter, which is used to prevent advertising of _____. (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) all summary LSAs into area 0 summary LSAs that match the area range command all external LSAs external LSAs that match the area range command
3-264
Q82)
Generally, a default route is described in the routing table as an _____. (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) O route O IA route O *E1 route O *E2 route
Q83)
Which command is best to use if you want to establish a default route from a router that has no default route in its routing table? (Source: Configuring and Verifying OSPF Route Summarization) A) B) C) D) ip route 0.0.0.0 0.0.0.0 next hop address default-information originate default-information originate always static route
Q84)
The area x range and network commands are similar because both use inverse masks for configuration purposes. (Source: Configuring and Verifying OSPF Route Summarization) A) B) true false
Q85)
All of these are permitted in a stub area except which one? (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) an ABR an ASBR summary routes summary LSAs
Q86)
Which type of router advertises the default into a stub area? (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) ASBR backbone router ABR internal router
Q87)
What is the correct configuration for stub area 10? (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) area 10 stub-area router ospf 10 stub area 10 stub area 10 stub no-summary
Q88)
What is the meaning of the no-summary parameter of the area x stub command? (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) There is no route summarization in the stub area. No summary LSAs are sent into the stub area. No type 5 LSAs are sent into in the stub area. There are no external LSAs in the stub area.
3-265
Q89)
The default route has a cost of 1 from the stub area ABR if no area default-cost command is used. (Source: Configuring and Verifying OSPF Special Area Types) A) B) true false
Q90)
A disadvantage of NSSA is that it does not have a totally stubby feature, like a normal stub area. (Source: Configuring and Verifying OSPF Special Area Types) A) B) true false
Q91)
Which characteristic is not a prerequisite for stub areas? (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) virtual links not allowed ASBRs not allowed ABRs not allowed one way in and out of the stub area
Q92)
Stub area design will not improve _____. (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) CPU utilization on routers in the stub memory requirements on routers in the stub ability to reach outside networks LSDB size on routers in the stub
Q93)
An LSA type 7 appears in the routing table as an _____. (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) O E1 route O E2 route O N2 route O I/A route
Q94)
What is the difference between a stub area and a totally stubby area configuration? (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) no-summary option on the ABR area area-id totally-stubby command on the internal routers area area-id nssa command on the internal routers default-cost command on the ABR
Q95)
A stub area blocks summary LSAs (type 3 and 4 LSAs). (Source: Configuring and Verifying OSPF Special Area Types) A) B) true false
Q96)
Where should you configure the area area-id stub command when you are configuring a stub area? (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) on all routers in the area on the ABR on the ASBR on routers that require stub capability within the area
3-266
Q97)
In NSSA, the NSSA ABR translates type 7 LSAs into type 5 LSAs. (Source: Configuring and Verifying OSPF Special Area Types) A) B) true false
Q98)
The ABR injects a default route into which three types of areas? (Choose three.) (Source: Configuring and Verifying OSPF Special Area Types) A) B) C) D) stub totally stubby NSSA totally stubby area 0
Q99)
Which two types of authentication are used in OSPF? (Choose two.) (Source: Configuring and Verifying OSPF Authentication) A) B) C) D) MD5 encrypted password simple password MD6
Q100) When OSPF authentication is configured between two routers, each router has its own unique password. (Source: Configuring and Verifying OSPF Authentication) A) B) true false
Q101) Which three of the following are used to generate the message digest when OSPF MD5 authentication is configured? (Choose three.) (Source: Configuring and Verifying OSPF Authentication) A) B) C) D) E) packet sequence number key ID key router ID
Q102) Which command is used to specify that OSPF simple password authentication is to be used? (Source: Configuring and Verifying OSPF Authentication) A) B) C) D) E) ip ospf authentication simple ip ospf authentication ip ospf authentication-key ip ospf message-digest-key ip ospf authentication message-digest
Q103) Which command is used to specify that OSPF MD5 authentication is to be used? (Source: Configuring and Verifying OSPF Authentication) A) B) C) D) E) ip ospf authentication simple ip ospf authentication ip ospf authentication-key ip ospf message-digest-key ip ospf authentication message-digest
3-267
Q104) When a new MD5 key is configured on a router for OSPF authentication, the router will use both the old and new keys until the new key is configured on neighboring routers. (Source: Configuring and Verifying OSPF Authentication) A) B) true false
Q105) Which command is used to troubleshoot OSPF authentication? (Source: Configuring and Verifying OSPF Authentication) A) B) C) D) debug ip ospf adj debug ip ospf adjacency events debug ip ospf database debug ip ospf packets
3-268

Q1) Q2) Q3) Q4) Q5) Q6) Q7) Q8) Q9) Q10) Q11) Q12) Q13) Q14) Q15) Q16) Q17) Q18) Q19) Q20) Q21) Q22) Q23) Q24) Q25) Q26) Q27) Q28) Q29) Q30) Q31) Q32) Q33) Q34) Q35) C A 1 = B, 2 = C, 3 = A B A B C B B A B B A B, D C C C A A F A A A = 3, B = 6, C = 1, D = 7, E = 5, F = 2, G = 4 A, C C D B B B B B B 1 = C, 2 = A, 3 = B A, B B, C
3-269
Q36) Q37) Q38) Q39) Q40) Q41) Q42) Q43) Q44) Q45) Q46) Q47) Q48) Q49) Q50) Q51) Q52) Q53) Q54) Q55) Q56) Q57)
A, D B A, B, E A A B, D A, C B D B, C D C B B B D A A, C B B A, B, D A = point-to-point B = transit C = stub D = virtual link A = 5, B = 2, C = 3 and 4, D = 6, E = 1, F = 9 and 11, G = 7 D D, E D B B B A C C C B, C A, D

Q58) Q59) Q60) Q61) Q62) Q63) Q64) Q65) Q66) Q67) Q68) Q69) Q70)
3-270
Q71) Q72) Q73) Q74) Q75) Q76) Q77) Q78) Q79) Q80) Q81) Q82) Q83) Q84) Q85) Q86) Q87) Q88) Q89) Q90) Q91) Q92) Q93) Q94) Q95) Q96) Q97) Q98) Q99) Q100) Q101) Q102) Q103) Q104) Q105)
B A E A D B C, D area 1 range 172.16.0.0 255.255.0.0 summary-address 172.16.32.0 255.255.224.0 B B D C B B C C B A B C C C A B A A A, B, C A, C B A, C, D B E A A
3-271
3-272
Module 4

Overview
This module explains why it is necessary to manipulate routing information. Without manipulation, route redistribution between IP routing domains may result in suboptimal routing. There are also times when routing information would waste bandwidth on a router interface, because the routing information is not needed. The implementation of redistribution in a multiprotocol network using Cisco IOS features according to a given network design and requirements is a primary learning objective of this module. The lessons describe prefix lists, distribution lists, and route maps first, and then describe the controlling of routing traffic with configuration and verification steps.
Module Objectives
Upon completing this module, you will be able to implement a redistribution solution in a multiprotocol network that uses Cisco IOS features to control the path selection and a loop free topology according to a given network design and requirements. This ability includes being able to meet these objectives: Identify common network performance issues Define how prefix lists work Determine how to use a prefix-list to control routing updates Determine how distribution lists work Use distribution lists to control routing updates Determine how route maps work Determine how to use route maps to control routing updates Use route-maps to filter routes
4-2
Lesson 1
Assessing Network Routing Performance and Security Issues

Overview
Routing updates compete with user data for bandwidth and router resources, yet routing updates are critical because they carry the information that routers need to make sound routing decisions. To ensure that the network operates efficiently, you must control and tune routing updates. Information about networks must be sent where it is needed and filtered from where it is not needed. There is no one type of route filter that is appropriate for every situation. Therefore, the more techniques that you have at your disposal, the better your chance of having a smooth, well-run network. This lesson discusses common network performance issues and how to control the updates that are sent and received by dynamic routing protocols. Prefix lists, distribute lists, and route maps are described as the main mechanisms to filter and control routing update traffic.
Objectives
Upon completing this lesson, you will be able to describe prefix lists, distribute lists, and route maps. You will also be able to explain how to use them to filter and control routing update traffic. This ability includes being able to meet these objectives: Determine common network performance issues Identify how distribute lists work Use distribute lists to control routing updates Identify how prefix lists work Use a prefix list to control routing updates Identify how route maps work
Use route maps to control routing updates Use route maps to filter routes Suppress routing updates using passive interface command
4-4
Common Network Performance Issues

This topic describes common network performance and security issues caused by update inefficiencies.
Common Factors Affecting Network Performance

Routing factors that influence CPU utilization include: The size of the routing information update The frequency of the updates The weaknesses in the design The presence of any route maps or filters Incorrectly configured route filters Running different protocols in different areas within the same autonomous system The number of routing protocol processes receiving the updates
ROUTE v1.04-2
Routing updates can decrease network performance. If a Layer 3-enabled switch or router receives a large number of updates, they must be processed. The CPU utilization spike during this processing depends on the following factors: The size of the routing update The frequency of the updates The number of routing protocol processes receiving the updates The presence of any route filters The weaknesses in the design Some factors are also dependent on the routing protocol. The size of routing updates and their frequency is directly proportional to the amount of traffic that must be sent over the links and processed by the CPUs. The same applies to the number of routing processes per router, where more routing processes generate more updates and require more CPU resources. Several solutions exist, and a good design and filtering may significantly improve network performance. However, the wrong design and incorrectly configured route filters will not improve network performance at all.
4-5
Routing Updates
Qualities of routing updates that influence CPU utilization include: The size of the routing information update The frequency of the updates A bad design
ROUTE v1.04-3
In some network deployments, high CPU utilization is normal. In general, larger Layer 2 or Layer 3 networks demand more CPU resources to process network-related traffic. Examples of operations with potentially high CPU utilization are as follows: IP routing table updates Cisco IOS commands More devices and links inside an autonomous system produce more routing update traffic. Redistribution from an external autonomous system adds to the size, as well. When a router receives a large number of routing updates, the routing information must be processed.
4-6
Filtering Routing Updates

Routing update filters may improve network performance Ensure router filters are configured correctly
ROUTE v1.04-4
Route filtering works by regulating the routes that are entered into or advertised out of the routing table. Filtering has different effects on link state routing protocols compared to distance vector protocols. Distance vector protocols advertise routes based on what is in the protocols route table. Link state protocols on the opposite side determine their routes based on the information in their link state databases. Distance vector protocols filter routes the router advertises to its neighbors; link state protocols, in contrast, do not take into account the advertised route entries of each routers neighbors. Filters can be configured to prevent updates through router interfaces, to control the advertising of routes in routing updates, or to control the processing of routing updates. If filters are not configured correctly or if filters are applied to the wrong interfaces, network performance issues will result.
4-7
Running Multiple Routing Protocols

You can run different protocols in different areas within the same autonomous system.
If many routing protocol processes receive updates at the same time, performance will be affected.
ROUTE v1.04-5
You can configure multiple routing protocols in a single router to connect networks that use different routing protocols. For example, you can run Enhanced Interior Gateway Routing Protocol (EIGRP) on one subnetted network, Open Shortest Path First (OSPF) on another subnetted network, and exchange routing information between them in a controlled fashion. Additionally, the same router can be connected to the ISP and exchange Border Gateway Protocol (BGP) routes, as well. Router R1 in the figure in the slide runs EIGRP, OSPF, and BGP. The available routing protocols were not designed to interoperate with one another, so each protocol collects different types of information and reacts to topology changes in its own way. This behavior produces a large amount of routing update traffic that must be processed by each protocol separately in a different way. For example, Routing Information Protocol (RIP) uses a hop-count metric and OSPF uses link metric information. Maintaining all routing, topology, and database tables inside the routers requires not only a great deal of CPU capacity, but also large amounts of memory resources.
4-8
Controlling Routing Updates

Design change Limit the number of routing protocols used Passive interfaces Redistribution with route filtering Access lists Prefix lists Distribute lists Route maps
ROUTE v1.04-6
To increase the network performance, routing updates must be exchanged in a controlled way and the network designer must take into account the recommended design rules. The passive interface technique prevents all routing updates from being advertised out of an interface. However, in many cases you do not want to prevent all routing information from being advertised. You might want to block the advertisement of only certain specific routes. For example, you might do so to prevent routing loops when you are implementing two-way route redistribution with dual redistribution points. When routing information is being exchanged between different networks that use different routing protocols, you can use many configuration options to filter the routing information. A good design must limit the number of routing protocols running on one router, because filtering must be applied to the redistribution between different protocols. You can use various methods of filtering routes, with various effects, to increase network performance. You can use the following tools to control routing updates and redistribution: Access lists Prefix lists Distribute lists Route maps
4-9
Using Route Filters

A neighbor relationship is established Adjacent routes exchange routing updates The process takes effect after multiple stages have been completed
ROUTE v1.04-7
The figure in the slide shows how filtering is used to control incoming routing update traffic. Only inbound filtering is shown.
Step 1
A routing update arrives at a routers interface and the router stores the packet in the interface buffer and triggers the CPU to make a decision. The routers CPU checks if there is an incoming filter applied to this interface. If no filter is applied, then the routing update packet is processed normally. If a filter is applied, then the next step is taken. The routers CPU checks if there is an entry for this address in the routing update packet. If there is no entry, the route is dropped. If entry exists, the next step is taken. The routers CPU processes the routing update packet according to the filter configuration.
Step 2
Step 3
Step 4
4-10
How Distribute Lists Work

This topic describes how distribute lists can be used to control routing updates.
Controlling Routing Update Traffic Using Distribute Lists
ROUTE v1.04-8
The ways to control or prevent dynamic routing updates are as follows: Passive interface: As previously stated, this feature prevents all routing updates from being sent through an interface. For EIGRP and Open Shortest Path First Protocol (OSPF), this method includes Hello protocol packets. Default routes: This feature instructs the router that if it does not have a route for a given destination, it should send the packet to the default route. Therefore, no dynamic routing updates about the remote destinations are necessary. Static routes: This feature allows routes to remote destinations to be manually configured in the router. Therefore, no dynamic routing updates about the remote destinations are necessary. Another way to control routing updates is a technique called a distribute list. A distribute list allows the application of an access list to the routing updates. You may be familiar with access lists associated with an interface and how they are used to control IP traffic. However, routers can have many interfaces, and route information can also be obtained through route redistribution, which does not involve an interface at all. Additionally, access lists do not affect traffic that is originated by the router, so applying one to an interface would have no effect on the outgoing routing advertisements. When you link an access list to a distribute list, routing updates can be controlled no matter what their source is. Configure access lists in global configuration mode, and then configure the associated distribute list under the routing protocol. The access list should permit the networks that will be advertised or redistributed, and deny the networks that will remain hidden.
4-11
The router then applies the access list 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 the router distributes.
4-12
Using Distribution Lists to Control Routing Updates

This topic describes how to implement and verify the distribute list route-filtering technique.
Steps to Configure Distribute List Filters

Define the traffic filtering requirements to permit or deny routes using one of these two methods: Configure an access list (ACL) Configure a route map Configure a distribute list to use the ACL or a route map: Apply it to the inbound or outbound updates
ROUTE v1.04-9
When you are planning how to configure distribute list filters, you must complete the following steps and create an implementation plan for the filters: Define traffic filtering requirements to permit or deny routes using one of these two methods:

Configure an access list Configure a route map
Configure a distribute list to use the access list or route map:
Apply it to the inbound or outbound updates
4-13
Configuring a Distribute List Filter

A distribute list filter can be applied to transmitted, received, or redistributed routing updates.
Filtering of updates being advertised from OSPF into RIP routing protocol according to access list 10
Filtering of networks received in updates from interface Serial0 according to access list 7
You can filter routing update traffic for any protocol by defining an access list and applying it to the specific routing protocol. You use the distribute-list command and link it to an access list to complete the filtering of routing update traffic. (The inbound distribute-list command allows the use of a route map instead of an access list.) A distribute list enables you to filter routing updates coming into a specific interface from or going out to neighboring routers using the same routing protocol. A distribute list also allows you to filter routes redistributed from other routing protocols or sources. Use the distribute-list out command to assign the access list to filter outgoing routing updates or to assign it to routes being redistributed into the protocol. The distribute-list out command cannot be used with link-state routing protocols for blocking outbound link-state advertisements (LSAs) on an interface. The distribute-list out command in the figure in the slide filters the updates being redistributed from OSPF into RIP routing protocol. Access list 10 is used to define the networks permitted or denied. Use the distribute-list in command to cause the access list to filter incoming routing updates coming in through an interface. This command prevents most routing protocols from placing the filtered routes in their databases. When this command is used with OSPF, the routes are placed in the database but not in the routing table. The distribute-list in command in the figure in the slide filters the networks received in updates from interface Serial0 according to access list 7. For more details about the distribute-list out and distribute-list in commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-14
Filtering Routing Updates with a Distribute List

Hides network 10.0.0.0 using interface filtering
ROUTE v1. 0 4-11
The figure in the slide shows the configuration of router R2, which is hiding network 10.0.0.0 behind the serial 0 interface. The distribute-list 7 out s0 command applies access list 7 to routing updates sent out from interface serial 0 to other routers running this routing protocol. This access list permits routing information about network 172.16.0.0 only. The implicit deny any statement at the end of the access list prevents routing updates about any other networks from being advertised. As a result, network 10.0.0.0 is hidden from the rest of the network.
4-15
Controlling Redistribution with Distribute Lists
ROUTE v1. 0 4-12
With redistribution, using a distribute list helps prevent all routes from being redistributed from RIP routing protocol into OSPF and vice versa. As shown in the figure in the slide, only networks 10.1.0.0 to 10.3.0.0 are redistributed from RIP into OSPF. Other networks are not permitted with access list 2 and are denied. Access list 2 allows the subset of RIP routes and denies all others. The distribute list configured under OSPF refers to this access list number 2. The same redistribution processing applies to networks 10.8.0.0 to 10.11.0.0, originated by OSPF. They can be redistributed from OSPF to RIP. Redistribution into RIP from OSPF is filtered with access list 3. The distribute list configured under RIP refers to this access list number 3 and permits only a subset of networks. A distribute list hides network information, which may be considered a drawback in some circumstances. In a network with redundant paths, the goal of using a distribute list may be to prevent routing loops. The distribute list permits routing updates that enable only the desired paths to be advertised. Therefore, other routers in the network do not know about the other ways to reach the filtered networks.
4-16
How Prefix Lists Work

This topic describes the how prefix lists can be used to control routing updates.
IP Prefix Filters
Traditionally, IP prefix filters were implemented with IP access lists configured with the distribute-list command. Prefix lists: Better performance than access lists User-friendly command-line interface Match routes in part of an address space with a subnet mask longer or shorter than a set number
ROUTE v1. 0 4-13
Traditionally, IP prefix filters were implemented with IP access lists configured with the distribute-list command. IP access lists used as route filters have several drawbacks: The 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. Using the ip prefix-list command has several benefits compared to using the access-list command. The intended use of prefix lists is limited to route filtering, where access lists were originally intended to be used for packet filtering and were then extended to route filtering. A router transforms a prefix list into a tree structure, with each branch of the tree serving as a test. The Cisco IOS software determines a verdict of either permit or deny much faster this way than when sequentially interpreting access lists. The command-line interface (CLI) that you use to configure the ip prefix-list command provides you with the ability to assign a line number to each line of the prefix list. The router will use this number to sort the entries in the prefix list. If you initially sequence the lines with some gaps in between the sequence numbers, you can insert additional lines later. You can also remove individual lines without removing the entire list. Routers match network numbers in a routing update against the prefix list using as many bits as indicated. For example, you can specify a prefix list to be 10.0.0.0/16, which will match 10.0.0.0 routes but not 10.1.0.0 routes.
4-17
The prefix list can specify the size of the subnet mask, and can also indicate that the subnet mask must be in a specified range. Prefix lists are similar to access lists in a number of 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 optimizes this 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. Testing is done using prefixes. The router compares the indicated number of bits in the prefix with the same number of bits in the network number in the update. If they match, testing continues with an examination of the number of bits set in the subnet mask. The prefix list line can indicate a range in which the number must be in order to pass the test. If you do not indicate a range in the prefix line, the subnet mask must match the prefix size.
4-18
Controlling Redistribution with Prefix Lists
ROUTE v1. 0 4-14
With redistribution, a prefix list can be used instead of a distribute list. As shown in the figure in the slide, networks 10.1.0.0 to 10.3.0.0 are redistributed only from RIP into OSPF. The other networks are not permitted with the prefix list PFX1 and are denied. PFX1 allows the subset of RIP routes and denies all others. The route map into OSPF matches the networks permitted by PFX1. The same applies to networks 10.8.0.0 to 10.11.0.0, originated by OSPF. They can be redistributed from OSPF to RIP. The redistribution into RIP from OSPF is filtered with the prefix list PFX2. The route map into RIP matches networks permitted by PFX2. In a network with redundant paths, the goal of using prefix lists and route maps may be to prevent routing loops. The prefix lists permit routing updates that enable only the desired paths to be advertised. Therefore, other routers in the network do not know about the other ways to reach the filtered networks.
4-19
Prefix List Matching Rules

Filter by exact prefix length mask filtering / Filter within a range using ge using le using ge and le The matching process also considers the subnet mask
ROUTE v1. 0 4-15
Prefix lists are configured to filter traffic based on a match of an exact prefix length or a match within a range when the ge and le keywords are used. The ge and le keywords are used to specify a range of prefix lengths. They provide a more flexible configuration than can be obtained using only the network/length arguments. A prefix list is processed using an exact match when neither the ge nor le keyword is specified. If only the ge value is specified, the range is the value entered for the ge-length argument to a full 32-bit length. If only the le value is specified, the range is from the value entered for the network/length argument to the lelength argument. If both the ge and le values are specified, the range is between the values used for the ge-length and le-length arguments. The following formula shows this behavior: length < ge-length < le-length <= 32
4-20
Using a Prefix List to Control Routing Updates

This topic describes how to implement and verify a prefix list for route filtering and redistribution.
Prefix List Matching Without ge or le

Similar to IP access lists with no wildcard bits

Which prefixes are matched? 192.168.0.0/16: Match 192.168.0.0/20: No Match 192.168.2.0/24: No Match
ROUTE v1. 0 4-16
To create a prefix list or to add a prefix list entry, use the ip prefix-list command in global configuration mode. Prefix lists are configured with permit or deny keywords to either permit or deny a prefix based on a matching condition. An implicit deny statement is applied to traffic that does not match any prefix list entry. A prefix list entry consists of an IP address and a bit mask. The IP address can be for a classful network, a subnet, or a single host route. The bit mask is a number from 1 to 32. If the seq keyword is configured without a sequence number, the default sequence number is 5. In this scenario, the first prefix list entry (like in the example in the slide) is assigned the number 5 and subsequent prefix list entries increment by 5. For example, the next two entries would have sequence numbers 10 and 15. If a sequence number is entered for the first prefix list entry but not for subsequent entries, the subsequent entry numbers increment by 5. For example, if the first configured sequence number is 3, subsequent entries will be 8, 13, and 18. Default sequence numbers can be suppressed by entering the no ip prefix-list command with the seq keyword. The evaluation of a prefix list starts with the lowest sequence number and continues down the list until a match is found. When an IP address match is found, the permit or deny statement is applied to that network and the remainder of the list is not evaluated.
Tip For best performance, the most frequently processed prefix list statements should be configured with the lowest sequence numbers. The seq number keyword and argument can be used for resequencing.
4-21
Prefix list entries without the ge or le option only match the route with the specified IP address and subnet mask. In the example in the slide, the prefix list entry permit 192.168.0.0/16 will not match the route 192.168.2.0/24, because of the mismatch in the IP address. It will also not match the route 192.168.0.0/20, because of the mismatch in the subnet mask. For more details about the ip prefix-list command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-22
Prefix List Matching With ge or le

A prefix list entry with the ge or le keyword matches any prefix within a specified address space for which the subnet mask falls within the specified limits.

Which prefixes are matched? 192.168.0.0/16, List1: Match 192.168.0.0/16, List2: No Match
ROUTE v1. 0 4-17
Prefix list entries for which you specify the ge or le option match any prefix within the address space that you specify by the network/length parameter, as long as the subnet mask length of the route falls within the range that you specify by the le and ge parameters. In the first example, the prefix list named List1, the route 192.168.2.0/24 is not matched by the prefix list entry permit 192.168.0.0/16 le 20, even though the IP address falls within the specified address range, because the subnet mask is too long. In the second example, the prefix list named List2, the route 192.168.0.0/16 is not matched by the prefix list entry permit 192.168.0.0/18 ge 18 because the subnet mask is too short.
4-23
Configuring Prefix Lists Examples

What will be matched by?
1. ip prefix-list A permit 0.0.0.0/0 ge 32 2. ip prefix-list B permit 128.0.0.0/2 ge 17 3. ip prefix-list C permit 0.0.0.0/0 le 32 4. ip prefix-list D permit 0.0.0.0/0 5. ip prefix-list E permit 0.0.0.0/1 le 24
ROUTE v1. 0 4-18
The slide contains some commonly used prefix list examples.
4-24
How Route Maps Work

This topic describes the functionality of route maps, which are powerful and flexible configuration tools.
Route Maps
Route maps are similar to a scripting language for these reasons: They work like access lists, but are more sophisticated. They offer top-down processing. When one of them finds a match, it stops searching. Lines are sequence-numbered for easier editing. Insertion of lines Deletion of lines Route maps are named, rather than numbered, for easier documentation. Match criteria and set criteria can be used; similar to the if-then logic in in scripting languages.
ROUTE v1. 0 4-20
Route maps are complex access lists that allow conditions to be tested against a packet or route using the match commands. If the conditions match, then actions can be taken to modify attributes of the packet or route. These actions are specified by the 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 can be edited individually. The statements in a route map are analogous to the lines of an access list. Specifying the match conditions in a route map is similar to specifying the source and destination addresses and masks in an access list. One major difference between route maps and access lists is that route maps can use the set commands to modify the packet or route.
4-25
Route Map Applications

The common uses of route maps are as follows:
Redistribution route filtering a more sophisticated alternative to distribute lists Policy-based routing the ability to determine a routing policy based on criteria other than the destination network BGP policy implementation the primary tool for defining BGP routing policies
ROUTE v1. 0 4-21
Network administrators use the route map tool for a variety of purposes. Several of the more common applications for route maps are as follows: Route filtering during redistribution: Redistribution nearly always requires some amount of route filtering. Although distribute lists can be used for this purpose, route maps offer an added benefit of manipulating routing metrics through the use of the set commands. 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 describes the interface or next-hop address to which the packet should be sent. PBR allows the operator to define a routing policy other than basic destination-based routing using the routing table. Border Gateway Protocol (BGP): Route maps are the primary tools for implementing a BGP policy. Network administrators assign route maps to specific BGP sessions (neighbors) to control which routes are allowed to flow into and out of the BGP process. In addition to their use in filtering, route maps allow for sophisticated manipulation of BGP path attributes.
4-26
Route Map Operation

A list of statements constitutes a route map. The list is processed in a top-down manner, like access lists are. The first match found for a route is applied. The sequence number is used for inserting or deleting specific route map statements.
ROUTE v1. 0 4-22
Route maps operate in a manner similar to access lists. When determining which routes will be redistributed from one protocol to the next, the router checks each route against the route map, beginning with the top line. Each line is sequence-numbered, both for top-down processing purposes and for editing purposes. Lines can be added or removed from a route map as changes are required. Each line has a permit or deny statement. If a route is matched in the matching statements and the line has a permit statement, then the router sets the metrics or other defined conditions and permits the redistribution of that route. The route map stops processing at the first match. If the packet is matched and the route map line has a deny statement, then the router stops at the matched line in the map and does not redistribute that route. Routes are filtered using this method. Routers search for matches on a line-by-line basis. If a router reaches the bottom of the route map without finding a match, it denies the route from being redistributed. There is always an implicit deny statement at the end of a route map.
4-27
Route Map Operation (Cont.)

The match statement may contain multiple references. Multiple match criteria in the same line: logical OR. At least one reference must permit the route for it to be a candidate for redistribution.

Multiple match statements on separate lines: logical AND. All match statements must permit the route for it to remain a candidate for redistribution. Route map permit or deny statements determine if the candidate will be redistributed.
Matching statements in a route map can be complex. Multiple match criteria in the same line are processed with OR logic. Separate match criteria can also be applied vertically under a route map line. In this case, each match uses AND logic. A route map may consist of multiple route-map statements. The statements are processed top-down, like statements are processed for an access list. The first match found for a route is applied. The sequence number is used for inserting or deleting specific route map statements in a specific place in the route map. The match route map configuration command define the conditions to be checked. The set route map configuration command define the actions that you should follow if there is a match. The single-match statement may contain multiple conditions. At least one condition in the match statement must be true to consider the statement a match (logical OR). A route map statement may contain multiple-match statements. All match statements in the route map statement must be true to consider the route map statement a match (logical AND). The sequence number specifies the order in which conditions are checked. For example, if there are two statements in a route map named MyRouteMap, one with sequence number 10 and the other with sequence number 20, the one with sequence number 10 is checked first. If the match conditions in the statement with sequence number 10 are not met, then the statement with sequence number 20 is checked. As is true of an access list, there is an implicit deny any statement at the end of a route map. The consequences of this depend on how the route map is used.
4-28
Steps to Configure A Route Map

Define the route map conditions Define the conditions to match Define the action to be taken on a match Attach the route map to an interface
ROUTE v1. 0 4-24
When you are planning to configure route maps, you must follow these steps and create an implementation plan for them: Define the route map conditions

Define the conditions to match Define the action to be taken when each condition is matched
Attach the route map to an interface
4-29
Configuring A Route Map
Defines the route map with the name MyRouteMap conditions.
Matches based on the prefix list MyList when defining the conditions to match.
Defines that interface ethernet 0 be used to forward packets that pass a match clause.
ROUTE v1. 0 4-25
To define the conditions for redistributing routes from one routing protocol into another, or to enable policy routing, use the route-map command in the global configuration mode and the match and set commands in the route map configuration modes. The commands in the slide show the route map configuration used to enable policy routing. The match and set commands are used with the route map command to define the conditions for policy-routing packets. The match command specifies the condition under which policy routing occurs. The set command specifies the routing actions to perform if the criterion enforced by the match command is met. You might want to route packets some way other than along the obvious shortest path. The sequence-number argument works as follows: If no entry is defined with the supplied tag, an entry is created with the sequence-number argument set to 10. If only one entry is defined with the supplied tag, that entry becomes the default entry for the following route-map command. The sequence-number argument of this entry is unchanged. If more than one entry is defined with the supplied tag, an error message is printed to indicate that a sequence-number argument is required. If the no route-map map-tag command is specified (with no sequence-number argument), the whole route map is deleted.
4-30
The match command is applied within a route map. The following bullets present a general list of match criteria. Some criteria are used for BGP policy, some criteria are used for PBR, and some criteria are used for redistribution filtering: match community match interface match ip address match ip next-hop match ip route-source match length match metric match route-type match tag The set commands are used within a route map to change or add characteristics, such as metrics, to any routes that have met a match criterion. The following bullets present a general list of set actions: set automatic-tag set default interface set interface set ip default next-hop set ip default next-hop verify-availability set ip global set ip next-hop set ip next-hop verify-availability set ip vrf set level (IP) set local-preference set metric (BGP-OSPF-RIP) set metric-type set next-hop set tag (IP) For more details about the route-map, match, and set commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-31
Attaching a Route Map to an Interface
Defines a route map named MyRouteMap to be used for policy routing on an interface.
Set the metric to 3 if the route is from IP address 172.21.16.18.
ROUTE v1. 0 4-26
Use the ip policy route-map command, in addition to the route-map command, and the match and set commands to define the conditions for policy-routing packets. The ip policy route-map MyRouteMap command in the example in the slide is used to define a route map named MyRouteMap to be used for policy routing on an interface. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteriathe conditions under which policy routing is allowed for the interface, based on the destination IP address of the packet. The set commands specify the set actionsthe particular policy routing actions to perform if the criteria enforced by the match commands are met. You might enable policy routing if you want your packets to take a route other than the obvious shortest path. In the route map example in the slide, the route-map MyRouteMap command matches ip address 172.21.16.18 and sets the metric to 3 when the condition under the match command is met. The configured route map is then attached to the interface serial 0 using the ip policy route-map MyRouteMap command. For more details about the ip policy route-map command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-32
Using Route-Maps to Control Routing Updates

This topic describes how to use the route-map command to define the conditions for route filtering and redistribution.
Steps to Configure Redistribution with Route Maps

Define the route map Define match statements Define set statements Define redistribution using the route map
ROUTE v1. 0 4-27
When you plan to configure route maps, you must follow these steps and create an implementation plan for them: Define the route map

Define match statements Define set statements
Define redistribution using route-maps
4-33
Route Map Redistribution Commands
Define the route map used during redistribution.
Configure redistribution from RIP to the EIGRP routing protocol using the route map to filter updates.
ROUTE v1. 0 4-28
When used for redistribution filtering, a route map is applied to the route redistribution process by adding the route-map command to the end of the redistribute (IP) routing protocol command. Use the route-map command and the match and set route-map configuration commands to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteriathe conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actionsthe particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map. Use route maps when you want detailed control over how routes are redistributed between the routing processes. The destination routing protocol is the one you specify with the router global configuration command. The source routing protocol is the one you specify with the redistribute (IP) configuration command. In the figure in the slide, the EIGRP process with the autonomous system number 7 is configured locally in router R1. The redistribute rip route-map rip_to_eigrp metric 1 1 1 1 1 command is used to configure redistribution of RIP routes into the EIGRP 7 routing process, where the route map named rip_to_eigrp is used to influence the redistribution of RIP routes into the EIGRP routing process. The route map is configured to match the routes tagged with 88. These routes are denied from being redistributed into the EIGRP 7 routing process. The routes without the tag 88 reach the second route-map statement and are tagged with 77. The set tag 77 command is used in the route-map. These routes are allowed to be distributed into the EIGPR routing process 7. For more details about the redistribute command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-34
Route Maps and Redistribution Commands Example
Routes matching either access list 23 or 29 are redistributed with an OSPF cost of 500, external type 1. Routes permitted by access list 37 are not redistributed. All other routes are redistributed with an OSPF cost metric of 5000, external type 2.
ROUTE v1. 0 4-29
In this example, RIPv1 is being redistributed into OSPF 10. A route map named redisRIP has been attached to the redistribute (IP) command. Sequence number 10 of the route map looks for an IP address match in access list 23 or access list 29. If a match is found, then the router redistributes the route into OSPF with a cost metric of 500 and sets the new OSPF route to external type 1. If there is no match to line 10, move to line 20. If there is a match in access list 37, then do not let that route redistribute into OSPF because the route-map statement with sequence number 20 is a deny statement. If there is no match to sequence number 20, move to 30. Because the route-map statement with sequence number 30 is a permit statement and there is no match criterion, all remaining routes are redistributed into OSPF with a cost metric of 5000 and an external metric of type 2.
4-35
Using Route-Maps to Filter Routes

This topic describes how to implement and verify route maps with route filtering.
ROUTE v1. 0 4-30
You can apply prefix lists, distribute lists, and route maps on either incoming or outgoing information. The incoming prefix list, the incoming distribute list, and the incoming route map must all permit the routes that are received from a neighbor before they will be accepted into the IP routing table. Outgoing routes must pass the outgoing distribute list, the outgoing prefix list, and the outgoing route map before they will be transmitted to the neighbor.
4-36
Suppressing Routing Updates using a Passive Interface

This topic describes how to configure dynamic routing protocol updates for passive interfaces and provides several examples where a passive interface can be used to limit overhead of routing protocols.
Passive Interface
Routers can have many interfaces Not all are allowed to send and receive routing updates The suppression of routing updates over some interfaces can be enabled Passive interfaces are used to: Suppress updates on an interface Suppress updates on all interfaces Each routing protocol has different rules OSPF: routing information is neither sent nor received EIGRP: routing process is disabled on an interface RIP: the sending of updates is disabled, but listening is allowed
ROUTE v1. 0 4-31
Routers can have many interfaces and there are times when you must include an interface in a network command, although you do not want that interface to participate in the routing protocol. In such cases the routing protocol might be configured differently to exclude the interface from routing purpose. A better solution is to suppress routing updates over all or some interfaces, which can be enabled globally in the routing process. A passive interface can be configured to suppress updates on the specific interface or on all interfaces. General rules for passive interfaces state that if you disable the sending of routing updates on an interface, the particular subnet will continue to be advertised to other interfaces and the interface will continue to receive and process updates from other routers. It is possible to set all interfaces as passive by default. You can then enable specific interfaces one-by-one. This is useful in ISP and large enterprise networks, where many of the distribution routers have more than 200 interfaces. This old solution meant entering 200 or more passive-interface statements. General rules are not always the same for different routing protocols. The passive interface behavior varies from one protocol to another. For the Open Shortest Path First (OSPF) protocol, OSPF routing information is neither sent nor received through the specified router interface that is configured as passive. The specified interface address appears as a stub network in the OSPF domain.
2009 Cisco Systems, Inc. Implement an IPv4-Based Redistribution Solution 4-37
Enhanced Interior Gateway Routing Protocol (EIGRP) is disabled on an interface that is configured as passive, although it advertises the route. For passive interfaces, EIGRP suppresses the exchange of hello packets between two routers, which results in the loss of their neighbor relationship. This not only stops routing updates from being advertised, but also suppresses incoming routing updates. With Routing Information Protocol (RIP), passive interfaces do not send multicast updates, but can listen to incoming updates from other RIP-speaking neighbors. Routers are still able to receive updates on a passive interface and use them in the routing table.
4-38
Using the passive-interface Command
ROUTE v1. 0 4-32
In the figure in the slide, routers R1 and R2 run EIGRP and have a network statement that encompasses all of their interfaces; however, you should run EIGRP only on the link between router R1 and router R2. Router R1 has several interfaces; the passive-interface default command was used to set all interfaces to passive, and then the no passive-interface command was used to enable the one interface from which the EIGRP updates are desired. Router R2 has only two interfaces; the passive-interface command was used for the one interface that is not to participate in EIGRP routing. It is important to understand how this configuration affects the information that is exchanged between routers R1 and R2, and between them and router R3. Unless you configure another routing protocol and redistribute between it and EIGRP, router R1 does not tell router R3 that it has a way to reach the networks advertised by router R2 via EIGRP. Likewise, router R2 does not tell router R3 that it has a way to reach the networks advertised by router R1 via EIGRP. Redundancy is built into this network. However, the three routers are not able to use the redundancy effectively. For example, if the link between router R3 and router R1 fails, router R3 does not know that it has an alternate route through router R2. For more details about the passive-interface command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-39
Summary
Summary
Sending an excessive number of routing updates, running different protocols in different areas within the same autonomous system, and incorrectly configuring route filters are common causes of network performance issues. Distribution lists use access lists or route maps to define the traffic filtering requirements to permit or deny routes. The distribute-list command allows updates to be filtered based on the incoming interface, outgoing interface, or redistribution from another routing protocol. Prefix lists significantly improve the performance of complex filters relative to traditional IP prefix filters implemented with IP access lists. The matching process for prefix lists takes into account the subnet mask. A filter can be configured for the exact prefix length, or it can be configured within a range using the ge and le keywords.
Summary (Cont.)
Route maps are complex ACLs that allow conditions to be tested against a packet or route using the match command. If the conditions match, then actions, specified by the set command, can be taken to modify the attributes of the packet or route. When used for redistribution filtering, a route map is applied to the route redistribution process by adding the route-map command to the end of the redistribute routing protocol command. When route maps are used to filter routing update traffic, they can be applied to incoming or outgoing traffic. The routes that are permitted can have their attributes set or changed by the set command in the route map. A passive interface can be configured to suppress updates on a specific interface or on all interfaces.
ROUTE v1. 0 4-34
4-40
Lesson 2
Operating a Network Using Multiple IP Routing Protocols

Overview
Simple routing protocols work well for simple networks, but as networks grow and become more complex, it may be necessary to change 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. This lesson examines several reasons for using more than one routing protocol. It is important to understand how to exchange routing information between these routing protocols and how Cisco routers operate in an environment with multiple routing protocols. This lesson describes redistribution from one routing protocol to another and how Cisco routers make route selections when multiple protocols are active in the network.
Objectives
Upon completing this lesson, you will be able to explain what route redistribution is and why it may be necessary. This ability includes being able to meet these objectives: Describe a complex routing network Define route redistribution Determine default metrics for redistributed routes Determine where to redistribute Identify caveats of redistribution
Describe a Complex Routing Network

This topic describes the need to use multiple IP routing protocols.
Complex Routing Scenarios

Networks can be dispersed Politically Geographically As a result of acquisitionscompany mergers Careful design and traffic optimization are required Redistribution Routing traffic filtering Summarization
ROUTE v1.04-2
There are many reasons for complex routing scenarios. When a network grows, it typically becomes more complex as network administrators adjust it based on factors like political borders, geographical borders, and mergers with other companies. In all such situations network administrators face complex routing scenarios, in which the use of multiple IP routing protocols is not an exception but the rule. With large numbers of routers and routing protocols running, the number of routing updates increases. As the network grows larger, traffic from those updates can slow the network down, indicating that a change is required. There are many possible solutions when the design of a network must be changed or optimized. A scalable routing protocol may be necessary, and the following careful design and traffic optimization are suggested: Redistribution Routing traffic filtering Summarization Routing traffic filtering and summarization are described in separate lessons. In this lesson, redistribution between different routing protocols is described.
4-42
Using Multiple Routing Protocols

Temporarily during conversion or migration only Application-specific protocols One size does not always fit all Political boundaries Groups that do not work well with others Mismatch between devices Multivendor interoperability Host-based routers
ROUTE v1.04-3
Multiple routing protocols may be necessary in the following situations: When you are migrating from an older interior gateway protocol (IGP) to a new IGP. Multiple redistribution boundaries may exist until the new protocol has completely displaced the old protocol. The same applies to company mergers between companies that are each using a different routing protocol. When the use of a new protocol is desired, but the old routing protocol is needed for host systems. This is true, for example, for UNIX host-based routers running RIP. When some departments do not want to upgrade their routers to support a new routing protocol. In mixed-router vendor environments. In these environments, you can use a routing protocol specific to Cisco, such as EIGRP, in the Cisco portion of the network and a common standards-based routing protocol, like OSPF, to communicate with devices from other vendors. When multiple routing protocols are running in different parts of the network, there may be a need for hosts in one part of the network to reach hosts in the other part. One solution is to advertise a default route into each routing protocol, but this is not always the best policy. The network design may not allow default routes. If there is more than one way to get to a destination network, routers may need information about routes in the other parts of the network to determine the best path to that destination. Additionally, if there are multiple paths, a router must have sufficient information to determine a loop-free path to the remote networks.
4-43
Cisco routers allow internetworks using different routing protocols, referred to as routing domains or autonomous systems, to exchange routing information through a feature called route redistribution. Redistribution is how routers connect different routing domains so that they can exchange and advertise routing information between the different autonomous systems.
Note The term autonomous system (AS), as used here, refers to an internetwork using any one of many routing protocols. The specific routing protocol may be an IGP or exterior gateway protocol (EGP). This is a different use of the term AS than used with Border Gateway Protocol (BGP).
4-44
Defining Route Redistribution

This topic describes the need to exchange routing information between different protocols to allow for complete network convergence.
Using Multiple IP Routing Protocols
ROUTE v1.04-4
Whatever the reason for running multiple protocols, network administrators must conduct migration from one routing protocol to another or redistribution of routing information between them carefully and thoughtfully. It is important for network administrators to understand what must be changed and to create a detailed plan before making any changes. An accurate topology map of the network and an inventory of all network devices are also critical for success. Network administrators must keep in mind the requirements and capabilities of routing protocols when planning redistribution. Link-state routing protocols, such as Open Shortest Path First (OSPF), require a hierarchical network structure. Network administrators need to decide which routers will reside in the backbone area and how to divide the other routers into areas. While EIGRP does not require a hierarchical structure, it operates much more effectively within one. Network administrators must carefully plan the redistribution strategy to avoid disrupting network traffic or causing outages.
4-45
Redistribution
Routes learned by some other means are selectively redistributed into a routing protocol from one of three sources: Another routing protocol Static routes Directly connected routes Routing loop prevention: Only routes used by the router itself are redistributed Double redistribution inside the same router is not allowed
ROUTE v1.04-5
Redistribution is the process of using a routing protocol to advertise routes that are learned by usual means of learning routes, such as by another routing protocol, static routes, or directly connected routes. While it is desirable that you run a single routing protocol throughout your entire IP internetwork, multiprotocol routing is common for a number of reasons. These reasons include company mergers, multiple departments managed by multiple network administrators, and multivendor environments. Running different routing protocols is often part of a network design. In any case, if you have a multiprotocol environment, redistribution a necessity. For you to be able to have a scalable solution and limit the amount of routing update traffic, the redistribution process must selectively insert the routes learned. Redistribution can lead to routing loops, which must be avoided. Only routes used by the router itself should be redistributed and double redistribution inside the same router should not be allowed.
4-46
Redistributing Route Information
ROUTE v1.04-6
Within each AS, the internal routers have complete knowledge about their network. The router that interconnects the autonomous systems is called a boundary router. The boundary router must be running all of the routing protocols that will be exchanging routes. In most cases, route redistribution must be configured in order to redistribute routes from one routing protocol to another routing protocol. The only time that redistribution is automatic in IP routing protocols is between IGRP and EIGRP processes running on the same router and using the same AS number. When a router redistributes routes, it allows a routing protocol to advertise routes that were not learned through that routing protocol. These redistributed routes could have been learned via a different routing protocol, such as when redistributing between EIGRP and OSPF, and they also could have been learned from static routes or by a direct connection to a network. Routers can redistribute static and connected routes, as well as routes from other routing protocols. Redistribution is always performed outbound. The router doing redistribution does not change its routing table. When, for instance, redistribution between OSPF and EIGRP is configured, the OSPF process on the boundary router takes the EIGRP routes in the routing table and advertises them as OSPF routes to its OSPF neighbors. Likewise, the EIGRP process on the boundary router takes the OSPF routes in the routing table and advertises them as EIGRP routes to its EIGRP neighbors. Then both autonomous systems know about the routes of the other system, and each AS can make informed routing decisions for these networks. EIGRP neighbors use the EIGRP external (D EX) listing to route traffic destined for the OSPF AS via the boundary router. The boundary router must have the OSPF routes for that destination network in its routing table to be able to forward the traffic.
4-47
For this reason, routes must be in the routing table for them to be redistributed. This requirement may seem self-evident, but it can also be a source of confusion. For instance, if a router learns about a network via EIGRP and OSPF, only the EIGRP route is put in the routing table because it has a lower administrative distance. Suppose RIP is also running on this router, and you want to redistribute OSPF routes into RIP. That network will not be redistributed into RIP because it is in the routing table as an EIGRP route, not as an OSPF route.
4-48
Default Metrics for Redistributed Routes

This topic describes default metrics used by different routing protocols when redistribution is implemented and identifies the seed metrics that are used by various routing protocols.
Using Seed Metrics

The initial, or seed, metric for a route is derived from the directly connected router interface. Once a compatible metric is established, the metric will increase in increments just like any other route.

Use the default-metric command to establish the seed metric for the route or specify the metric when redistributing.
ROUTE v1.04-7
When a router advertises a link directly connected to one of its interfaces, the initial, or seed metric, also referred to as the default metric, that is used is derived from the characteristics of that interface, and the metric increases in increments as the routing information is passed to other routers. For OSPF, the seed metric is based on the bandwidth of the interface. For EIGRP the seed metric is based on the interface bandwidth and delay. For RIP, the seed metric starts with a hop count of 0 and increases in increments from router to router. Redistributed routes are not physically connected to a router; they are learned from other routing protocols. It is difficult to translate from one metric to another, from hops to bandwidth. If a boundary router is to redistribute information between routing protocols, it must be able to translate the metric of one routing protocol into the metric of the other routing protocol. For example, if a boundary router receives a RIP route, the route will have a hop count as its metric. To redistribute the route into OSPF, the router must translate the hop count into a cost metric that the OSPF routers will understand. This seed metric is defined during redistribution configuration. Once the seed metric for a redistributed route is established, the metric will increase in increments normally within the AS.
Note The exception to the rule that metric increase in normal increments within the AS is for OSPF E2 routes. These routes maintain their initial metric regardless of how far they are propagated across an AS.
4-49
The default-metric command, used in routing process configuration mode, establishes the seed metric for all redistributed routes. Cisco routers also allow the seed metric to be specified as part of the redistribution command, either with the metric option or by using a route map. Whichever way you set the initial seed metric, you should set it to a value larger than the largest metric within the receiving AS, to help prevent suboptimal routing and routing loops. For more details about the default-metric commands for RIP, OSPF, and EIGRP, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-50
Default Seed Metrics
Protocol RIP EIGRP OSPF BGP
Default Seed Metric Inifinity Infinity 20 for all except BGP, which is 1 BGP metric is set to IGP metric value
ROUTE v1.04-8
The table in the slide shows the default seed metric value for redistributed routes for each IP routing protocol. RIP and EIGRP do not advertise a redistributed route unless a seed metric is configured. These protocols interpret the seed metric of 0 as infinity by default. A metric of infinity tells the router that the route is unreachable, and, therefore, should not be advertised. The default metric for redistributing routes into each of the protocols is as follows: The default for RIP and EIGRP is infinityyou must specify a default metric or routes will not be redistributed. For OSPF, the redistributed routes have a default type 2 metric of 20, except for redistributed BGP routes, which have a default type 2 metric of 1. For BGP, the redistributed routes maintain the IGP routing metrics.
4-51
Redistribution with Seed Metric
ROUTE v1.04-9
The figure illustrates a seed metric of 30 implemented by OSPF on the redistributed RIP routes. The link cost of the Serial link to router R4 is 100. So, the cost for networks 1.0.0.0, 2.0.0.0, and 3.0.0.0 in router R4 is the seed metric (30) plus the link cost (100): 130. Notice that the metrics of the three networks in the RIP cloud are irrelevant in the OSPF cloud, because the objective is to have each OSPF router forward traffic for the three networks to the border (redistributing) router. A metric of infinity tells the router that the route is unreachable, and therefore, it should not be advertised. When redistributing routes into RIP and EIGRP, you must specify a default metric. For OSPF, the redistributed routes have a default type 2 metric of 20, except for redistributed BGP routes, which have a default type 2 metric of 1. For BGP, the redistributed routes maintain the IGP routing metrics.
4-52
Determining Where to Redistribute

This topic describes the optimum redistribution process between two protocols, the process for points of distribution in a network, and ways of identifying possible routing loops.
One-Point Redistribution
One-point redistribution One-way; default route or static routes needed Two-way
ROUTE v1. 0 4-10
One-point redistribution defines only one redistribution point between two routing protocols. Routes are redistributed on one router only. The redistribution can be: One-way Two-way Redistribution is one-way if routes from routing protocol A are redistributed into routing protocol B, but not vice versa. Redistribution is two-way if routes from routing protocol A are redistributed into routing protocol B and routes from routing protocol B are also redistributed into routing protocol A. One-way redistribution requires the use of a default route or static routes. If routes are redistributed from routing protocol A into routing protocol B, routing protocol B devices are aware of all the routing information. At the same time, devices in the routing protocol A autonomous system are aware of routing information for their own autonomous system only, and reachability for destinations outside the routing protocol A autonomous system requires the use of a default route or one or more static routes pointing out. One-way or two-way redistribution at one point is always safe because one-point redistribution represents the only exit and the only entrance from one routing protocol to another. Routing loops cannot be inadvertently created.
4-53
One-Way and Two-Way Multipoint Redistribution

Multipoint redistribution One-way Two-way
ROUTE v1. 0 4-11
Multipoint redistribution is redistribution between two routing protocols that takes place on two or more separate devices running both routing protocols. Two possibilities exist: Multipoint one-way redistribution Multipoint two-way redistribution Multipoint redistribution is likely to introduce routing loops. Even one-way multipoint redistribution is dangerous and generic multipoint two-way redistribution is highly problematic. Problems often result from differences in administrative distance between the two protocols, as well as incompatible metrics. Statically assigned metrics are used in redistribution points. Multipoint one-way redistribution only works well if: The receiving routing protocol supports different administrative distances for internal and external routes (Routing protocols that support different administrative distances include EIGRP, BGP and late maintenance releases of OSPF.) The external administrative distance of the receiving routing protocol is higher than administrative distance of the sending routing protocol Multipoint two-way redistribution difficulties include: Suboptimal routing (only part of the total cost is considered in routing decisions) Self-sustained routing loops on route loss In multipoint redistribution scenarios, preventing routing loops is a main concern. The redistribution configuration should insert only internal routes from routing protocol A to B and vice versa. Routes at the redistribution points should be tagged and then filtered based on the tags used when doing redistribution in the other direction. Propagation of the metric from A to B and vice versa is recommended, even though it is not sufficient to prevent loops. The easiest way to avoid loops when using two-way redistribution is to use a default route.
4-54
Redistribution Techniques
ROUTE v1. 0 4-12
The safest way to perform redistribution is to redistribute routes in only one direction, on only one boundary router within the network. To do this, you must first determine which routing protocol is the core routing protocol, and which ones are edge routing protocols. The core routing protocol is the main routing protocol running in the network. During a transition between routing protocols, the core is the new routing protocol and the edge is the old routing protocol. In networks that run multiple routing protocols all the time, the core is usually the more advanced routing protocol. If redistribution must be done in both directions, or on multiple boundary routers, then the redistribution should be tuned to avoid problems like suboptimal routing and routing loops. Depending on your network design, you may use any of the following redistribution techniques: Redistribute a default route about the core AS into the edge AS. In one-way redistribution, routes from the edge routing protocols are redistributed into the core routing protocol, and a default route is sent back to the edge routers. This technique helps prevent route feedback, suboptimal routing, and routing loops. Redistribute multiple static routes about the core AS into the edge AS. The edge routes are still redistributed into the core, but static routes for the core networks are redistributed into the edge protocol and sent to the edge routers. This method works if there is one redistribution point only, but it may cause route feedback if there are multiple points. Redistribute routes from the core AS into the edge AS with filtering to block out inappropriate routes. For example, routes from the edge should not be redistributed back into the edge routers from the core via another redistribution point (when there are multiple boundary routers).
4-55
Redistribute all routes from the core AS into the edge AS and from the edge AS into the core AS, and then modify the administrative distance that is associated with the external routes so that they are not the selected routes when multiple routes exist for the same destination. In some cases, the route learned by the native (local) routing protocol is better, but it may have a higher (less believable) administrative distance. If two routing protocols advertise routes to the same destination, information from the routing protocol with the lowest administrative distance is placed in the routing table. By default, a route redistributed into a routing protocol inherits the default administrative distance of that routing protocol.
4-56
Caveats of Redistribution
This topic describes how to avoid routing loops in the network caused by redistribution and create a distribution and loop map for a given network.
Redistribution Implementation Considerations

Problems: Routing loop Suboptimal path selection Incompatible routing information Inconsistent convergence time Solutions: Administrative distance Route maps Distribution lists Manipulation of metrics
Redistribution of routing information adds to the complexity of a network and increases the potential for routing confusion, so it should be used only when necessary. The key issues that arise when you are using redistribution are the following: Routing feedback (routing loops): Depending on how you employ redistribution, routers may send routing information received from one AS back into that same AS. The feedback is similar to the routing loop problem that occurs in distance vector topologies. Incompatible routing information: Because each routing protocol uses different metrics to determine the best path, path selection using the redistributed route information may be suboptimal. The metric information about a route cannot be translated exactly into a different protocol, so the path that a router chooses may not be the best. To prevent suboptimal routing, as a rule, you should assign to redistributed routes a seed metric that is higher than any routes that are native to the redistributing protocol. For instance, if RIP routes are being redistributed into OSPF and the highest OSPF metric is 50, the redistributed RIP routes should be assigned an OSPF metric higher than 50. Inconsistent convergence time: Different routing protocols converge at different rates. For example, RIP converges more slowly than EIGRP, so if a link goes down, the EIGRP network will learn about it before the RIP network.
Note Good planning will ensure that these issues do not cause problems in your network.
4-57
Good planning can eliminate the majority of issues, but additional configuration might be required. Some issues may be solved by changing the administrative distance, manipulating the metrics, and filtering using route maps and distribute lists.
4-58
One-Way Redistribution Issue
ROUTE v1. 0 4-14
Multipoint one-way redistribution can cause routing confusion if routing protocols are using different administrative distances. It works properly only in the following circumstances: If the receiving routing protocol supports different administrative distances for internal and external routes If the external administrative distance of one routing protocol (OSPF in the figure in the slide) is higher than the administrative distance of the second routing protocol (EIGRP in the figure in the slide). Routing protocols that support different administrative distances include EIGRP, BGP, and OSPF. In the figure in the slide, router R1 from EIGRP is announcing an external route by sending routing updates to routers R2 and R3. Both neighboring routers are running two routing protocols and the redistribution between EIGRP and OSPF takes place on router R2. Router R3 receives routing update information for the same route directly from router R1 and via router R2, which is sending a redistributed route through OSPF updates. The administrative distance of OSPF (110) is lower than the administrative distance of external EIGRP routes (170), so router R3 selects the wrong route. Instead of sending packets directly to router R1, router R3 prefers the path via router R2 and the result is suboptimal routing.
4-59
One-Way Multipoint Redistribution Issue
ROUTE v1. 0 4-15
In the figure in the slide router R1 from EIGRP is announcing routes by sending routing updates to routers R2 and R3. Both neighboring routers are running two routing protocols and redistribution between EIGRP and OSPF takes place. Because multipoint redistribution is configured, routers R2 and R3 receive routing update information for the same route directly from router R1 and via OSPF (router R2 from router R3, and router R3 from router R2). The routing update information they receive via OSPF comes in the form of redistributed routes they receive in OSPF updates. If the administrative distance of OSPF (110) is lower than the administrative distance of EIGRP (170), then router R2 also selects the wrong route. Instead of sending packets directly to router R1, router R2 prefers the path via router R3 and the result is suboptimal routing. It can also result in route flapping, as R2 is also redistributing the same EIGRP route in OSPF. R3 also prefers the OSPF path, and sends packets via router R2. The packet may be bouncing back and forth between R2 and R3 in the OSPF network until its Time to Leave (TTL) value reaches 0, before being discarded. Network 10.0.0.0 is then unreachable.
4-60
Two-Way Multipoint Redistribution Issue
ROUTE v1. 0 4-16
Generic multipoint two-way redistribution is highly problematic and requires careful design and configuration. Routing protocols have incompatible metrics and during redistribution the metric information can be lost. In order to avoid problems associated with incompatible metrics, statically assigned metrics can be used in redistribution points. A number of problems can occur during multipoint two-way redistribution: Suboptimal routing (only part of the total cost is considered in routing decisions) Self-sustained routing loops upon route loss To prevent routing loops in multipoint redistribution scenarios, you should take into account the following recommendations during configuration: Insert only internal routes from routing protocol A to B and vice versa Tag routes in redistribution points and filter based on tags when doing redistribution Propagate metrics from routing protocol A to routing protocol B properly (though this is not sufficient to prevent loops) Use default routes to avoid two-way redistribution The figure in the slide shows a two-way multipoint redistribution issue in which the cost of the internal links in routing protocol A is completely different then the cost of the links in routing protocol B. It is obvious that the best path between router R1 and router R4 is via router R3, but during redistribution from routing protocol B to routing protocol A, the metric is lost and router R1 sends the packets toward router R4 via router R2. The result is suboptimal routing.
4-61
Summary
Summary
Big, complex networks must be adjusted based on factors like political borders, geographical borders, and mergers with other companies. In such complex scenarios, running multiple IP routing protocols is common. Using a routing protocol to advertise routes that are learned by some other means, such as by another routing protocol, static routes, or directly connected routes, is called redistribution. When a router advertises a link directly connected to one of its interfaces, the initial, or seed, metric that is used is derived from the characteristics of that interface. During redistribution the default metric is used; when redistributing routes into RIP and EIGRP, the default metric must be specified.
ROUTE v1. 0 4-17
Summary (Cont.)
Redistribution can be one-point (one-way or two-way) or multipoint (one-way or two-way). One-point redistribution, whether one-way or two-way, is always safe, because it represents the only exit from one routing protocol to another. In contrast, multipoint redistribution is likely to introduce routing loops, so careful design and configuration must be applied. The key issues that arise when you are using redistribution are routing feedback (routing loops), incompatible routing information, and inconsistent convergence time. Solutions to these issues include correct design in terms of the administrative distance, manipulation of metrics, and filtering using route maps and distribution lists.
ROUTE v1. 0 4-18
4-62
Lesson 3
Configuring and Verifying Route Redistribution

Overview
Configuring route redistribution can be simple or complex, depending on the mix of routing protocols that you want to redistribute. The commands that are used to enable redistribution and to assign metrics vary slightly depending on the routing protocols being redistributed. Before configuring the exchange of routing information between routing protocols, you must understand the procedures for and requirements of each routing protocol. Redistribution must be configured correctly for each routing protocol to obtain proper results. This lesson describes how to configure route redistribution between various IGP (interior gateway protocol) routing protocols. The commands for each protocol are covered. These commands differ slightly according to the different routing protocol requirements. In addition, the impact of route redistribution is analyzed.
Objectives
Upon completing this lesson, you will be able to configure route redistribution between multiple IP routing protocols. This ability includes being able to meet these objectives: Define examples of redistribution Define the Administrative Distance attribute Define route redistribution using administrative distance Identify the impact of using administrative distance for route manipulation Identify redistribution using route maps Describe route redistribution using route maps
Examples of Redistribution
This topic describes how to redistribute between RIP, OSPF and EIGRP, as well as the procedures necessary to configure route redistribution.
Redistribution Supports All Protocols
ROUTE v1.04-2
As shown in the figure in the slide, redistribution supports all routing protocols. Additionally, static and connected routes can be redistributed to allow the routing protocol to advertise the routes without using a network statement for them. Routes are redistributed into a routing protocol, so the redistribute command is given under the routing process that is to receive the routes. Before implementing redistribution, consider these points: Only protocols that support the same protocol stack are redistributed. For example, you can redistribute between IP Routing Information Protocol (RIP) and Open Shortest Path First Protocol (OSPF), because they both support the TCP/IP stack. The method used to configure redistribution varies slightly among different routing protocols and combinations of routing protocols. Some routing protocols require a metric to be configured during redistribution, but others do not.
Note IGRP is no longer supported, as of Cisco IOS Software Release 12.3.
The following generic steps apply to all routing protocol combinations; however, the commands that are used to implement these steps may vary. For configuration commands, it is important that you review the Cisco IOS documentation for the specific routing protocols that need to be redistributed.
4-64
Note
In this topic, the terms core and edge are generic terms that are used to simplify the discussion about redistribution.
1. Locate the boundary router that requires configuration of redistribution. Selecting a single router for redistribution minimizes the likelihood of creating routing loops that are caused by feedback. 2. Determine which routing protocol is the core, or backbone, protocol. Typically, this protocol is OSPF or Enhanced Interior Gateway Routing Protocol (EIGRP). 3. Determine which routing protocol is the edge, or short-term (in the case of migration), protocol. Determine whether all routes from the edge protocol need to be propagated into the core. Consider methods that reduce the number of routes. 4. Select a method for injecting the required edge protocol routes into the core. Simple redistribution using summaries at network boundaries minimizes the number of new entries in the routing table of the core routers. When you have planned the edge-to-core redistribution, consider how to inject the core routing information into the edge protocol. Your choice depends on your network. For more details about the redistribute (IP) command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-65
Steps to Configure Redistribution into RIP

Enter router RIP configuration mode

Configure redistribution from another routing protocol; OSPF is used above.

These optional parameters influence redistribution into the RIP routing protocol.
The figure in the slide shows how to configure for redistribution from OSPF process 1 into RIP. The first step is to enter router RIP configuration mode. The router rip command is used to access the routing process into which routes need to be redistributed. In this case, it is the RIP routing process. The next step is to use the redistribute (IP) command inside router configuration mode to specify the routing protocol to be redistributed into RIP. In this case, it is the OSPF routing process number 1. You can use optional keywords to change how distribution is performed. For example, you might modify the default metric or route filtering using route maps.
Note The default metric is infinity, except when you are redistributing a static or connected route. In that case, the default metric is 1.
4-66
Redistributing into RIP

Redistribute into RIP and assign the metric 3 (3 hops) to all OSPF routes.
ROUTE v1.04-4
In the figure in the slide, routes from OSPF process number 1 are being redistributed into RIP and given a seed metric of 3. The default metric is infinity, and a network administrator was required to change it. Because no route type is specified, both internal and external OSPF routes are redistributed into RIP. In the routing table on router R2, you can see that OSPF route 172.16.1.0, which is redistributed into RIP on router R1, is announced as an RIP route in the RIP autonomous system.
4-67
Steps to Configure Redistribution into OSPF

Enter router OSPF configuration mode

Configure redistribution from another routing protocol; EIGRP with AS 10 is used above.

These optional parameters influence redistribution into OSPF routing protocol.

The figure in the slide shows how to configure for redistribution from an EIGRP AS 100 into an OSPF routing process. The first step is to enter router OSPF configuration mode. The router ospf 1 command is used to access the OSPF routing process into which the routes need to be redistributed. In this case, it is OSPF routing process 1. The next step is to use the redistribute (IP) command in router configuration mode to specify the routing protocol to be redistributed into OSPF. In this case, it is the EIGRP routing process for AS 100. You can use optional keywords to change the way distribution is performed. For example, you might modify the default metric or route filtering using route maps. Redistribution into OSPF can also be limited to a defined number of prefixes using the redistribute maximum-prefix router configuration command. The threshold parameter will default to logging a warning at 75 percent of the defined maximum value configured. After the router reaches the defined maximum number of prefixes, it will not redistribute any more routes. Additional parameters can be used to avoid the limitation that is placed on redistribution; the maximum value number simply becomes a second point at which a warning message is logged. This command was introduced in Cisco IOS Release 12.0(25)S. It was integrated into Cisco IOS Release 12.2(18)S and Cisco IOS Release 12.3(4)T and later.
Note The default metric is 20 and the default metric type is 2. Subnets do not redistribute by default.
For more details about the redistribute maximum-prefix command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-68
Redistributing into OSPF

Redistribute from EIGRP AS 100 into OSPF and change the metric type from type 2 to type 1.
ROUTE v1.04-6
In the figure in the slide, routes from EIGRP AS 100 that are being redistributed into OSPF process 1 are given a default metric of 20. The default metric type is external type 2; in the example in the slide, the default metric type was changed to external type 1. This setting means that the metric increases in increments whenever updates are passed through the network. The command contains the subnets option, so subnets are redistributed too. If you look at the routing table on router R2, you can see that EIGRP route 172.16.1.0, which is redistributed into OSPF on router R1, is announced as an OSPF route inside the OSPF autonomous system. It is also apparent that the route is an E1 type.
4-69
Steps to Configure Redistribution into EIGRP

Enter router EIGRP configuration mode

Configure redistribution from another routing protocol; OSPF with process number 1 is used above.

These optional parameters influence redistribution into EIGRP routing protocol.
ROUTE v1.04-7
The figure in the slide shows how to configure redistribution from an OSPF into an EIGRP AS 100 routing process. The first step is to enter router EIGRP configuration mode. The router eigrp 100 command is used to access the EIGRP routing process into which routes need to be redistributed. In this case, it is the EIGRP AS 100 routing process. The next step is to use the redistribute (IP) command inside router configuration mode to specify the routing protocol to be redistributed into EIGRP AS 100. In this case, it is OSPF routing process 1. You can use optional keywords to change the way that distribution is performed. For example, you might modify default metric or route filtering using route maps.
Note The default metric is infinity.
Note
When you are redistributing a static or connected route into EIGRP, the default metric is equal to the metric of the associated interface.
4-70
Default Metric

The default metric is set to: Bandwidth in kilobits = 10000, Delay in tens of microseconds = 100, Reliability = 255 (maximum), Load = 1 (minimum), MTU = 1500 bytes You need to use this command when redistributing from another protocol with incompatible metric into EIGRP. You do not need this command when redistributing: static routes to interface or connected networks between EIGRP processes
ROUTE v1.04-8
You do not need default metrics to redistribute EIGRP into itself. To set metrics for Enhanced IGRP, use this form of the default-metric (EIGRP) router configuration command. EIGRP need five metrics when redistributing other protocols: bandwidth, delay, reliability, load, and MTU. Bandwidth: The minimum bandwidth of the route in kilobits per second. It can be any positive integer. Delay: The route delay in tens of microseconds. It can be 0 or any positive number that is a multiple of 39.1 nanoseconds. Reliability: The likelihood of successful packet transmission expressed as a number between 0 and 255. The value 255 means 100 percent reliability; 0 means no reliability. Loading: The effective bandwidth of the route expressed as a number from 1 to 255 (255 is 100 percent loading). MTU: The minimum maximum transmission unit (MTU) size of the route in bytes. It can be any positive integer. You must use the default-metric (EIGRP) router configuration command when redistributing from another protocol with an incompatible metric into EIGRP, unless you use the redistribute command. The redistribute command is able to set the metric used during the redistribution. You do not need to use the default-metric (EIGRP) router configuration command when redistributing static routes to interface or connected networks between EIGRP processes. For more details about the default-metric (EIGRP) command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-71
Redistributing into EIGRP

Redistribute OSPF 1 routing process updates into EIGRP AS 100 and overwrite the default metric.
ROUTE v1.04-9
In the figure in the slide, routes from OSPF process number 1 are redistributed into EIGRP AS 100. The default metric is infinity, but in order to reflect the normal metric, it must be changed. You can use the default-metric (EIGRP) command, or change the metric and use the redistribution (IP) command. In the figure in the slide, the default metric has been changed with the redistribution command as follows: Bandwidth in kilobits = 10000, Delay in tens of microseconds = 100, Reliability = 255 (maximum), Load = 1 (minimum), MTU = 1500 bytes. You can see from the routing table on router R2 that OSPF route 172.16.1.0, which is redistributed into EIGRP AS 100 on router R1, is announced as an EIGRP route inside the EIGRP AS 100 autonomous system. The redistributed route appears as an external EIGRP (D EX) route. External EIGRP (D EX) routes have a higher administrative distance than internal EIGRP (D) routes, so internal EIGRP routes are preferred over external EIGRP routes.
4-72
Example: Redistributing into OSPF Before Redistribution
ROUTE v1. 0 4-10
The figure in the slide shows the network of a hypothetical company. The network begins with two routing domains, or autonomous systems, one using OSPF and one using RIP version 2 (RIPv2). Router R2 is the boundary routerit connects directly to one router within each routing domain and runs both protocols. Router R1 is in the RIP domain, and is advertising subnets 10.1.0.0, 10.2.0.0, and 10.3.0.0 to router R2. Router R3 is in the OSPF domain and is advertising subnets 10.8.0.0, 10.9.0.0, 10.10.0.0, and 10.11.0.0 to router R2. The configuration of router R2 is shown in the figure. RIP is required to run on the serial 1 interface only; therefore, the passive-interface command is given for interface serial 2. The passive-interface command prevents RIP from sending route advertisements out that interface. OSPF is configured on serial 2. The figure in the slide also shows the routing tables of routers R1, R2, and R3. Each routing domain is separate, and routers within them only recognize routes that are communicated from their own routing protocols. The only router with information on all the routes is router R2. The goal of redistribution in this network is for all routers to recognize all routes within the company. To accomplish this goal, redistribution is planned: Redistribute RIP routes into OSPF. Redistribute OSPF routes into the RIP domain.
4-73
Example: Configuring Redistribution at Router R2
ROUTE v1. 0 4-11
Router R2 is the boundary router, so redistribution is configured on it. This figure shows how router R2 is configured to accomplish the required redistribution. RIP is redistributed under the OSPF process. In this example, the metric is set under the redistribute command. Other options include specifying a default metric or accepting the OSPF default metric of 20. The default-metric command assigns a seed metric to all routes redistributed into OSPF from any origins. If a metric value is configured under a specific redistribute command, this value overrides the default metric value. A value of 300 is selected because it is a worse metric than any of the native OSPF routes. Under the RIP process, routes are redistributed in from OSPF process number 1. These routes are redistributed into RIP with a metric of 5. A value of 5 is selected because it is higher than any metric in the RIP network. This figure in the slide also shows the routing tables of all three routers after redistribution is completed. The goal is accomplished. All routers now have routes to all remote subnets. There is complete reachability within the entire network. Routers R1 and R3 now have many more routes to keep track of than before. Each router is also affected by topology changes in the routing domain of the other router. Depending on network requirements, you may be able to increase efficiency by summarizing the routes before redistributing them. Remember that route summarization hides information. If routers in the other autonomous systems are required to track topology changes within the network, then route summarization should not be performed, because it hides information that the routers need. A more typical case is that the routers need to recognize topology changes only within their own routing domains. In this case, performing route summarization is appropriate.
4-74
Example: Routing Tables After Summarizing Routes and Redistributions
ROUTE v1. 0 4-12
If routes are summarized before redistribution, then the routing tables of each router are significantly smaller. Router R2 benefits the most; it now has only four routes to keep track of instead of nine. Router R1 has five routes instead of eight, and router R3 has six routes to keep track of instead of eight. The following list describes how summarization should be configured in this network: Router R1, RIP: For RIPv2, the summarization command is given at the interface connecting router R2 with router R1. This summary address is advertised out of that interface instead of the individual subnets. One limitation of RIP is that the subnet mask of the summary address must be greater than or equal to the default mask for the major classful network. The ip summary-address rip interface command is used for summarization.
Note This summary includes 10.0.0.0, which is acceptable in this case because it is directly connected with a longer mask.
Router R3, OSPF: You must perform summarization in OSPF at an Area Border Router (ABR) or an Autonomous System Boundary Router (ASBR). Create another OSPF area that includes the four subnets to be summarized. Give the command for summarization under the OSPF process at router R3, which becomes an ABR. The area range router configuration command is used for summarization, as shown in the figure in the slide.
4-75
The Administrative Distance Attribute

Cisco routers use administrative distance when using more than one routing protocol. This topic describes the features of administrative distance in terms of routing protocols.
Administrative Distance
Administrative distance (AD) is a way of ranking the trustworthiness of routing information. A lower administrative distance means a route is more trustworthy.
Route Source Connected interface Static route EIGRP summary route External BGP Internal EIGRP IGRP OSPF IS-IS RIPv1, RIPv2 ODR External EIGRP Internal BGP Unknown
Default Distance 0 1 5 20 90 100 110 115 120 160 170 200 255
ROUTE v1. 0 4-13
Most routing protocols have metric structures and algorithms that are not compatible with other protocols. It is critical for a network using multiple routing protocols to have seamless exchange of route information and the ability to select the best path across multiple protocols. Cisco routers use a value called administrative distance to select the best path when they learn two or more routes to the same destination from different routing protocols. Administrative distance is a way of ranking the trustworthiness of a routing protocol. Cisco has assigned a default administrative distance value to each routing protocol supported on its routers. Each routing protocol is prioritized from most believable to least believable. Some examples of prioritization are as follows: Prefer manually configured routes (static routes) to dynamically learned routes Prefer protocols with sophisticated metrics to protocols with more deterministic metrics Prefer External Border Gateway Protocol (EBGP) to most other dynamic protocols The table in the slide, lists the default administrative distances of the protocols supported by Cisco routers. The administrative distance is a value between 0 and 255. The lower the administrative distance value, the higher the reliability of the protocol.
Note IGRP is no longer supported, as of Cisco IOS Software Release 12.3.
4-76
Administrative Distance Example

From R1 to R6: RIP (AD 120) will choose R1-R4-R6 OSPF (AD 110) will choose R1-R2-R3-R5-R6 EIGRP (AD 90) will choose R1-R2-R3-R5-R6
ROUTE v1. 0 4-14
The figure in the slide has multiple sources of routing information active at the same time. A lower administrative distance value means the source of routing information is more believable. For the best path from R1 to R6, the following route choices are made if all four routing protocols are active on all the routers: RIP (administrative distance 120) chooses R1 to R4 to R6 based on hop count (two hops versus four hops the other way). OSPF (administrative distance 110) calculates the default metric as 100 Mb/s divided by the interface bandwidth, where bandwidth is the speed of each link. The path R1 to R4 to R6 default metric is (100 Mb/s / 64 kb/s) + (100 Mb/s / 1.544 Mb/s) = 1562 + 64, or 1626. The R1 to R2 to R3 to R5 to R6 path default metric is 1544 + 1544 + 1544 + 1544 = 6176; therefore, OSPF chooses the R1 to R2 to R3 to R5 to R6 path. Although OSPF and Intermediate System-to-Intermediate System (IS-IS) are both linkstate routing protocols that converge quickly, OSPF is more trustworthy than IS-IS. This is because OSPF bases its default metric on bandwidth, and is therefore more likely to pick the best path. EIGRP (administrative distance 90) calculates the default metric as (100,000,000 / bandwidth) + delay, where bandwidth is the speed of the slowest link in the path and delay is cumulative across the path. Assuming a uniform link delay of 100, the R1 to R4 to R6 default metric is (108 / 64) + 200 = 1,562,700, and R1 to R2 to R3 to R5 to R6 default metric is (108 / 1544) + 400 = 65,166. EIGRP chooses R1 to R2 to R3 to R5 to R6. Although EIGRP and OSPF routing protocols both converge quickly and consider bandwidth, EIGRP is more trustworthy than OSPF. This is because EIGRP takes more information into account in its calculation. Because EIGRP has the lowest administrative distance of the four protocols, only the EIGRP path is put into the routing table.
4-77
Route Redistribution using Administrative Distance

This topic describes how to manipulate redistributed routes to avoid network loops and instability by using the administrative distance attribute.
Steps to Configure Redistribution Using Administrative Distance

Enter router configuration mode Configure the redistribution from another routing protocol Modify the administrative distance Remember that the configuration is different for different routing protocols
ROUTE v1. 0 4-15
Redistribution using administrative distance requires the following steps:

Step 1 Step 2 Step 3
Enter router configuration mode. Configure redistribution from another routing protocol. Modify the administrative distance.
Keep in mind that the configuration is different for different routing protocols
Note
The steps above need information about the protocols used and their administrative distances.
4-78
Modifying Administrative Distance
Used for OSPF to define the external, interarea, and intra-area distance
Used for EIGRP to define the internal and external distance
Used for BGP to define external, internal, and local distance
ROUTE v1. 0 4-16
The distance (IP) command configures the administrative distance per specific network inserted into routing table, regardless of the IP routing protocol used. The specific, protocoldependent distance commands are used to define the administrative distance for each routing protocol. For OSPF, use the distance ospf command. OSPF assigns different administrative distance values to external, interarea and intra-area routes. The default values are 110 for all of them. For EIGRP, use the distance eigrp command. EIGRP assigns different administrative distance values to routes learned natively through EIGRP and to routes redistributed from other sources. By default, natively learned routes have an administrative distance of 90, but external routes have an administrative distance of 170. For BGP, use the distance bgp command. BGP assigns different administrative distance values to routes learned through External Border Gateway Protocol (EBGP), routes learned through Internal Border Gateway Protocol (IBGP), and local routes. The default values used here are 20, 200, and 200, respectively. For more details about the distance (IP) command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-79
Modifying Administrative Distance (Cont.)

The distance eigrp comand is used for EIGRP protocol. The distance (IP) command is protocol-independent Used to define an administrative distance for routes that are inserted into the routing table Used for all protocols, except for EIGRP, OSPF, and BGP when the dedicated, protocol-specific distance commands are used.
ROUTE v1. 0 4-17
In some cases, a router selects a suboptimal path if it assigns a better administrative distance to a routing protocol with a worse route. Assigning a higher administrative distance to an undesired routing protocol ensures that routers select routes from the desired routing protocol. The figure in the slide illustrates the commands for changing the default administrative distance. The distance command changes the default administrative distance for all protocols. The distance commands dedicated to EIGRP, OSPF and BGP redistribution can also be used. The distance router configuration command is used to specify the administrative distance for particular routes that are inserted into a routing table. In the figure in the slide, the router eigrp global configuration command sets up EIGRP routing in autonomous system number 100. The network router configuration commands specify EIGRP routing on networks 192.168.7.0 and 172.16.0.0. The distance eigrp 80 130 command sets the administrative distance for internal EIGRP routes to 80 and for external EIGRP routes to 130. Additionally, the distance 90 192.168.7.0 0.0.0.255 command sets the administrative distance to 90 for all routers on the Class C network 192.168.7.0 and the distance 120 172.16.1.3 0.0.0.255 command sets the administrative distance to 120 for the router with the address 172.16.1.3. For more details about the distance (IP) and distance eigrp commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-80
Modifying Administrative Distance (Cont.)

The distance ospf comand is used for OSPF protocol. The distance (IP) command is protocol independent. Used to define an administrative distance for routes that are inserted into the routing table. Used for all protocols, except for EIGRP, OSPF ,and BGP when the dedicated, protocol-specific distance commands are used.
ROUTE v1. 0 4-18
In the figure in the slide, the router ospf global configuration command sets up OSPF routing with process number 10. The network router configuration commands specify OSPF routing on networks 192.168.7.0 and 172.16.0.0. The distance ospf external 100 inter-area 100 intraarea 100 command sets the administrative distance for internal, interarea and intra-area OSPF routes to 100 (default values are 110). Additionally, the distance 90 10.0.0.0 0.0.0.255, distance 110 10.11.0.0 0.0.0.255, and distance 130 10.11.12.0 0.0.0.255 commands set the administrative distance to 90, 110, and 130 for the least to the most specific networks, respectively. For more details about the distance (IP) and distance ospf commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
4-81
Impact of using Administrative Distance for Route Manipulation

This topic describes the before and after results of using the administrative distance to modify route redistribution. Assess the impact of administrative distance changes on routing tables.
Example: Redistribution Using Administrative Distance
ROUTE v1. 0 4-19
The figure in the slide shows a network that uses multiple routing protocols. There are a number of ways to correct path selection problems in a redistribution environment. These examples show how problems occur, where they occur, and one possible way to resolve them. Redistribution using administrative distance is presented. The figure in the slide illustrates a network with RIP and OSPF routing domains. Recall that OSPF is more believable than RIP, because it has an administrative distance of 110 and RIP has an administrative distance of 120. If, for example, a boundary router (R1 or R2) learns about network 10.3.3.0 via RIPv2 and also via OSPF, the OSPF route will be used and inserted into the routing table because OSPF has a lower administrative distance than RIPv2, even though the path via OSPF might be the longer (worse) path.
4-82
Example: Redistribution Using Administrative Distance (Cont.)
ROUTE v1. 0 4-20
The figure in the slide illustrates the configurations for router R1 and router R2. These configurations redistribute RIP into OSPF and OSPF into RIP on both routers. The redistribution into OSPF sets a default OSPF metric of 10000 to make these routes less preferred than native OSPF routes and protect against route feedback. The redistribute statement also sets the metric type to E1, so that the route metrics continue to accrue, and the router redistributes subnet information. The redistribution into RIP sets a default RIP metric of 5 to also protect against route feedback.
4-83
ROUTE v1. 0 4-21
The figure in the slide displays the routing table on router R2 after redistribution has occurred. Router R2 learned RIP and OSPF routes, but lists only OSPF routes in the routing table. The first edge router to set up redistribution has a normal routing table and retains the RIP routes. The second edge router chooses the OSPF routes over its RIP routes. The paths to the internal RIP routes are shown as going through the core, because of the dual mutual redistribution points. OSPF is informed about the RIP routes via redistribution. OSPF then advertises the RIP routes via OSPF routes to its neighboring router. The neighbor router is also informed about the same routes via RIP. However, OSPF has a better administrative distance than RIP, so the RIP routes are not put into the routing table. OSPF was configured on router R1 first, and router R2 then received information about the internal (native RIP) routes from both OSPF and RIP. It prefers the OSPF routes, because OSPF has a lower administrative distance. Therefore, none of the RIP routes appear in the table. Refer back to the topology diagram to trace some of the routes. The redistribution has resulted in suboptimal paths to many of the networks. For instance, 10.200.200.34 is a loopback interface on router R4. Router R4 is directly attached to router R2. However, the OSPF path to that loopback interface goes through router R1, then router R3, then router R4 before it reaches its destination. The OSPF path taken is actually a longer (worse) path than the more direct RIP path.
4-84
ROUTE v1. 0 4-22
One of the boundary routers (router R2 in this example) selected the poor paths, because OSPF has a better administrative distance than RIP. You can change the administrative distance of the redistributed RIP routes to ensure that the boundary routers select the native RIP routes, as illustrated in the figure in the slide. The distance command modifies the administrative distance of the OSPF routes to the networks that match ACL 64. ACL 64 is used to match all the native RIP routes. The access-list 64 permit 10.3.1.0 command configures a standard ACL to permit the 10.3.1.0 network. Other similar access-list statements permit the other internal native RIP networks. In the preceding figure, both of the redistributing routers are configured to assign an administrative distance of 125 to OSPF routes that are advertised for the networks that are listed in ACL 64. ACL 64 has permit statements for the internal native RIP networks of 10.3.1.0, 10.3.2.0, and 10.3.3.0, as well as the loopback networks of 10.200.200.31, 10.200.200.32, 10.200.200.33, and 10.200.200.34. When either one of the redistributing routers learns about these networks from RIP, it selects the routes learned from RIP (with a lower administrative distance of 120) over the same routes learned from OSPF (with an administrative distance of 125), and puts only the RIP routes in the routing table. Note that the distance command is part of the OSPF routing process configuration, because the administrative distance should be changed for these routes when they are advertised by OSPF, not by RIP. You need to configure the distance command on both redistributing routers because either one can have suboptimal routes, depending on which redistributing router sends the OSPF updates about the RIP networks to the other redistributing router first.
4-85
ROUTE v1. 0 4-23
The output shows that router R2 now retains the more direct paths to the internal networks by learning them from RIP. However, some routing information is lost with this configuration. For example, depending on the actual bandwidths, the OSPF path may have been better for the 10.3.1.0 network. It may have made sense not to include 10.3.1.0 in the ACL. This example illustrates the importance of knowing your network before you implement redistribution, and of closely examining which routes the routers are selecting after redistribution is enabled. Pay particular attention to routers that can select from a number of possible redundant paths to a network, because they are more likely to select suboptimal paths. The most important benefit of using administrative distance to control route preference is that no path information is lost; the OSPF information is still in the OSPF database. If the primary path is lost, the OSPF path can reassert itself, and the router will maintain connectivity with those networks.
4-86
Redistribution Using Route Maps

This topic describes how to implement route maps with route redistribution to prevent routing loops.
Redistribution to Prevent Routing Loops

Simple redistribution results in a loop after a route is lost. To prevent routing loops use route maps with: Redistribution of internal routes only Route tagging
ROUTE v1. 0 4-24
The figure in the slide represents multipoint two-way redistribution. With this kind of redistribution, it is very likely that routing loops exist. Simple redistribution is configured as follows:

A default metric is needed, because the metrics are not compatible. The example in the slide is of redistribution between the EIGRP and RIP processes. When a route is lost, long-term loops may be introduced. To prevent routing loops, use route maps for: Redistributing internal routes only Route tagging
4-87
Solution With Route Tagging
ROUTE v1. 0 4-25
To avoid routing loops, either use route-maps to redistribute internal routes or to use route tagging. The solution using route maps and tagging is shown in the figure in the slide. Routes redistributed into RIP are tagged with the value 40 during the redistribution process. In the opposite direction, routers redistributed into EIGRP AS 40 process are tagged with the value 20 during the redistribution process. At the same time, redistribution using a route map is also filtering tagged updates. Updates with tag 20 are not allowed to go back to the RIP routing protocol. At the same time, updates with tag 40 are not allowed to go back to the protocol EIGRP AS 40. As visible in the figure in the slide, the route-map command has two statements. One is for tagging and the other one is for filtering updates. Only one part of configuration (for router R1) is shown in the figure in the slide. The same configuration is needed in router R2, as well. If redistribution between two EIGRP routing protocols will be configured, then another solution is also possible. This solution is to redistribute internal routes only. The configuration needed is as follows:

The solution works as long as there are no other redistributions into either EIGRP process.
4-88
Route Redistribution using Route Maps

This topic describes the reasons to use route maps in redistribution, and the effects of doing so.
Redistribution With Tagging Verification
Routing table before tagging
ROUTE v1. 0 4-26
The figure in the slide shows a multipoint two-way redistribution. With this kind of redistribution, it is very likely that routing loops exist. The show ip route command output for a specific network in the figure in the slide shows that redistribution takes place, but there is solution to avoid routing loops. As mentioned in the previous topic, tagging is one of the possible solutions.
4-89
Redistribution With Tagging Verification (Cont.)
Routing table after tagging is applied to router R1

In this second example, tagging is configured between routing protocols during multipoint twoway redistribution. The output of the show ip route command in the figure in the slide shows the tag used.
4-90
Summary
Summary
Redistribution supports all routing protocols. Additionally, static and connected routes can be redistributed to allow the routing protocol to advertise the routes without using a network statement for them. Administrative distance (AD) is a way of ranking the trustworthiness of routing information. A lower administrative distance indicates that a route is more trustworthy. The distance (IP) command configures the administrative distance per specific network inserted into routing table, regardless of the IP routing protocol used. The specific protocol dependent distance commands are used to define administrative distance for a specific routing protocol.
ROUTE v1. 0 4-28
Summary (Cont.)
Redistribution using administrative distance can correct path selection problems in a redistribution environment. It is very likely that routing loops are introduced when you use multipoint two-way redistribution. Two solutions are to redistribute only internal routes and to use route tagging. The show ip route command output for a specific network shows the tagging values added to a network during the redistribution process.
ROUTE v1. 0 4-29
4-91
4-92
Lesson 4
Lab 4-1 Debrief

Overview
In Lab 4-1, students configure route redistribution between multiple IP routing protocols. First they configure the RIPv2, OSPF, and EIGRP routing protocols in order to implement redistribution between them. During the redistribution task, they redistribute static routes and routes between routing protocols. In the last task, they implement filtering for selective redistribution and to avoid routing loops for two-way redistribution.
Objectives
Upon completing this lesson, you will be able to configure redistribution between multiple routing protocols, as well as implement route filtering. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

This topic describes the lab topology and key checkpoints used to create a solution and start with the verification.
Lab Topology
ROUTE v1. 04-2
The figure presents the physical lab topology used for Lab 4-1: Configure route redistribution between multiple IP routing protocols. The topology uses four pod routers and one backbone router. All routers participate in the multiple-routing-protocol configurations. Redistribution is configured between them on various routers based on the routing protocol configuration. Based on the topology, students will identify the required parameters and route redistribution between multiple IP routing protocols. Because two-way redistribution is configured in the network, loop avoidance mechanisms must be usedfiltering or another path-control tool.
4-94

Task 1: Implementing RIP, EIGRP, and OSPF Routing What steps did you take to configure the RIPv2, OSPF, and EIGRP routing protocols? Task 2: Implementing RIP Redistribution What steps did you take to redistribute loopback interfaces into RIP and to redistribute RIP routes into EIGRP? Have you also configured a static route on router R3 to establish connectivity in the opposite direction? Task 2Implementing OSPF Two Way Redistribution What steps did you take to redistribute from OSPF to EIGRP? What steps did you take to redistribute from OSPF to RIP?
ROUTE v1. 04-3
In the first task, you will implement the following routing protocols: RIP on routers R1 and R3 EIGRP on router R1 to exchange the routing protocol information with BBR2 OSPF on routers R1, R2, and R4 For RIP and OSPF routing protocol configuration, all of the parameters must be defined by the network administrator. For the EIGRP routing protocol, the requirements involve gathering the existing EIGRP routing configuration on router BBR2, because EIGRP requires that the same autonomous system number be used among all EIGRP routers in one EIGRP domain. Redistribution for RIP routing protocol involves redistribution of loopback interfaces into the RIP routing protocol and redistribution of the RIP routes into an EIGRP routing protocol. For bidirectional connectivity, the way back from EIGRP to RIP must be defined; static routes are used for this. Two-way redistribution between OSFP and EIGRP, as well as between OSPF and RIP, requires careful implementation of filters, because routing loops should be avoided.
4-95
Verification
Did you have enough information to create an implementation plan? Did you successfully configure the RIPv2, EIGRP, and OSPF routing protocols such that all of the routes are present in the IP routing table? Did you successfully configure redistribution into the RIP routing protocol and verify the presence of the requested route? Did you successfully configure redistribution of RIP into the EIGRP routing protocol and verify the presence of the requested route? Did you successfully configure redistribution from OSPF into RIP and from OSPF into EIGRP?
ROUTE v1. 04-4
A common approach to verifying the implementation process for a routing protocol is to take the following steps: In order to create the implementation plan and implement the solution, gather enough information. Check the routes in the IP routing table belonging to each routing protocol. Successful configuration of the RIPv2, EIGRP, and OSPF routing protocols is important, because the base configuration must be prepared in order to successfully configure route redistribution between the protocols. Configure redistribution into the RIP routing protocol and verify the presence of the routes inside the IP routing table. Configure redistribution from RIPv2 into the EIGRP routing protocol and verify the presence of the routes inside the IP routing table. Configure redistribution from OSPF into RIPv2 and from OSPF into EIGRP and verify the presence of the routes inside the IP routing table.
4-96
Checkpoints
Configure the RIPv2, EIGRP, and OSPF routing protocols. Examine and verify that the routing protocols are up and routes exist inside the IP routing table. Configure redistribution into RIP. Configure redistribution from RIP into EIGRP. Verify the RIP database and IP routing table. Configure two-way redistribution from OSPF into EIGRP. Verify an EIGRP topology and OSPF database. Configure two-way redistribution from OSPF into RIP. Verify the OSPF and RIP databases and IP routing table.
ROUTE v1. 04-5
With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Configure the RIP, EIGRP, and OSPF routing protocols. Examine and verify that the routing protocols are up and routes exist inside the IP routing table. Configure redistribution into RIPv2. Configure redistribution from RIPv2 into EIGRP. Verify the RIP database and IP routing table. Configure two-way redistribution between OSPF and EIGRP Verify the EIGRP topology and OSPF database. Configure two-way redistribution between OSPF and RIP Verify the OSPF and RIP databases and IP routing table.
4-97

Sample Solution
RIPv2, OSPF, and EIGRP are configured on the routers. Redistribution takes place into RIP and from RIP to EIGRP. Static routes are configured. Two-way redistribution is configured from OSPF into EIGRP and from OSPF into RIP.
ROUTE v1. 04-6
The sample solution includes implementation details and details for each task of the implementation plan. Different solutions are possible; the figure points out a few details of a successful configuration. The proper implementation of route redistribution between multiple IP routing protocols includes the following details: The RIP, OSPF, and EIGRP routing protocols are implemented. The existing configuration is taken into account in terms of EIGRP AS number, IP addressing, and subnets used. Keep in mind the OSPF network type for the serial multipoint subinterface. Loopback interfaces are redistributed into RIP and RIP routes into EIGRP. Static routes are configured if two-way redistribution is not implemented, in order to provide reachability back to the source routing protocol as well. Two-way redistribution from OSPF into EIGRP and from OSPF to RIP is configured. Route filtering is applied to avoid redistribution of the wrong routing information and the creation of a routing loop.
4-98
Different routing protocols can be used. Static routes can be used. Different path control tools can be used to manipulate the redistribution. Redistribution can be configured by changing administrative distances and metrics.
ROUTE v1. 04-7
In order to provide reachability in the network, several routing protocols can be used. It is possible to migrate from one routing protocol to another to avoid redistribution or because the second routing protocol provides more optimized path selection and manipulation of routes. Static routes can be used to manipulate the path or to influence the destination. Static routes provide more control over the reachability in the network, but using them is not a scalable solution. This is because for every new destination network, a new static route must be defined. So when the network grows, static routes are rarely used. In our alternative solution, static routes can be used instead of redistribution in order to provide reachability for a few destination networks. All other destinations not specified by the static routes are not reachable if there is no entry in the routing table. Two-way redistribution requires either the use of route filtering or another path manipulation mechanism to avoid routing loops, or the use of filtering to hide destinations from networks. For redistribution, changing the metric and administrative distance is another way to manipulate paths and the reachability of destinations.
4-99
Q and A
Why is routing protocol selection important? Why is changing the administrative distance and metric important? What must be used when configuring two-way redistribution? Why are path control tools important?
ROUTE v1. 04-8
A routing protocol exchanges routing updates and populates the IP routing table, which is used for destination-based forwarding. Different routing protocols process the routing updates in different ways. The administrative distance defines the trustworthiness of the routes provided by a routing protocol. The metric provides the importance, or the quality, of routes within a routing protocol. By manipulating the administrative distance and metric value, you can implement path manipulation. Because two-way redistribution is highly problematic, you must use route filters with it to avoid routing loops. Path control tools are important for filtering routes that are not desired. They can also be used to manipulate the paths of packets to avoid suboptimal paths.
4-100
Summary
Summary
Configure the RIPv2, EIGRP, and OSPF routing protocol to establish reachability in the network and enable destination-based forwarding. Configure redistribution into the RIP protocol and from RIP to EIGRP to maintain the optimum path across the network. Configure two-way redistribution of OSPF into EIGRP and OSPF into the RIP routing protocol, where the last example path control or route filtering must be used.
ROUTE v1. 04-9
4-101
4-102
Module Summary
Module Summary
Common network performance issues including excessive routing updates, incorrectly configured route filters, and the use of different protocols in different areas within the same autonomous system can be controlled using prefix lists, distribution lists, and route maps. The passive-interface command can be used to suppress routing update traffic. Companies with complex networks face the challenges of political borders, geographic borders, and, sometimes, mergers with other companies. Routes are redistributed into a routing protocol by using the redistribute command under the routing process that is to receive the routes.
ROUTE v1. 04-1
This module covered IP route redistribution and the control of redistributed routing updates. It also covered the use of passive interfaces and route maps for this control. Finally, it covered the use of route maps for policy-based routing (PBR). Any two IP routing protocols can be redistributed. However, many types of incorrect information may be propagated. Passive interfaces, distribute lists, and route maps are some of the tools used to control these updates. Route maps may also be used to implement PBR for cost savings, quality of service (QoS), and other purposes driven by enterprise policy.
4-103
4-104
Module Self-Check
Use the questions here to review what you learned in this module. The correct answers and solutions are found in the Module Self-Check Answer Key. Q1) Which two of these are common network performance issues? (Choose two.) (Source: Assessing Network Routing Performance and Security Issues) A) B) C) D) Q2) excessive routing updates low-speed CPU in the router use of different protocols in different areas within the same autonomous system automatic summarization of routing protocols
Which four tools can be used for route filtering? (Choose four.) (Source: Assessing Network Routing Performance and Security Issues) A) B) C) D) E) F) access lists prefix lists summarization distribute lists QoS route maps
Q3)
Which matching method cannot be used with a prefix-list filter? (Source: Assessing Network Routing Performance and Security Issues) A) B) C) D) E) mask filtering using ge using le using ge and le packet length
Q4)
Which two prefixes are matched by the following command: ip prefix-list List2 permit 192.168.0.0/16 ge 18? (Choose two.) (Source: Assessing Network Routing Performance and Security Issues) A) B) C) D) 192.168.0.0/16 192.168.0.0/20 192.168.2.0/24 192.128.0.0/24
Q5)
Which prefix list matches all host routes? (Source: Assessing Network Routing Performance and Security Issues) A) B) C) D) ip prefix-list A permit 0.0.0.0/0 ge 32 ip prefix-list B permit 128.0.0.0/2 ge 17 ip prefix-list C permit 0.0.0.0/0 le 32 ip prefix-list D permit 0.0.0.0/0
Q6)
Which two tools can be used to match traffic controlled by a distribute list? (Choose two.) (Source: Assessing Network Routing Performance and Security Issues) A) B) C) D) access lists prefix lists route maps match lists
Implement an IPv4-based Redistribution Solution
4-105
Q7)
Which three of these are common route map applications? (Choose three.) (Source: Assessing Network Routing Performance and Security Issues) A) B) C) D) redistribution route filtering policy-based routing BGP policy implementation network performance testing
Q8)
Route maps cannot match networks based on access lists and change the metric value and metric type during the redistribution process. (Source: Assessing Network Routing Performance and Security Issues) A) B) true false
Q9)
The passive-interface command is used to suppress the sending of routing updates from an interface. In RIP, routing protocol, it suppresses both the sending and the receiving of routing updates. (Source: Controlling Routing Update Traffic) A) B) true false
Q10)
Which command sets all interfaces as passive by default? (Source: Controlling Routing Update Traffic) A) B) C) D) passive-interface all passive-interface default passive-interface default all passive-interface all default
Q11)
You can use PBR to bypass the default destination-based forwarding of routers and route maps applied to interfaces for the processing of inbound packets. (Source: Controlling Routing Update Traffic) A) B) True. False.
Q12)
What steps must you use to configure policy routing? (Source: Controlling Routing Update Traffic)
Q13)
Which configuration command must be used in order to apply the route map named ChangeIntf to locally originated traffic? (Source: Controlling Routing Update Traffic) A) B) C) D) ip policy route-map ChangeIntf ip local policy route-map ChangeIntf ip policy local route-map ChangeIntf ip policy route-map local ChangeIntf
4-106
Q14)
Redistribution supports BGP, EIGRP, IS-IS, OSPF, RIP, static, and connected routes. (Source: Configuring and Verifying Route Redistribution) A) B) True. False.
Q15)
What does the redistribute eigrp 100 subnets metric-type 1 command do when used in router configuration mode under OSPF process 1? (Source: Configuring and Verifying Route Redistribution) A) B) C) D) Redistributes from EIGRP AS 100 into OSPF and changes the metric type from type 2 to type 1. Redistributes from EIGRP AS 100 into OSPF process 1 and changes the metric value of each subnet. Redistributes only from EIGRP AS 100 subnets of metric type 1. Redistributes from EIGRP and processes the first 100 subnets of metric type 1.
Q16)
All of these statements are true about the default-metric 10000 100 255 1 1500 command used in the EIGRP routing process configuration mode except which one? (Source: Configuring and Verifying Route Redistribution) A) B) C) D) This command is needed when redistributing from another protocol with an incompatible metric into EIGRP. This command is not needed or applied when redistributing static routes to interfaces or connected networks. This command is not needed or applied when redistributing between the EIGRP and IGRP processes. This command is not needed or applied when redistributing between the EIGRP and RIP processes.
Q17)
Administrative distance (AD) is a way of ranking the trustworthiness of routing information. A higher administrative distance means a route is more trustworthy. (Source: Configuring and Verifying Route Redistribution) A) B) true false
Q18)
Which routing protocol has the lowest administrative distance? (Source: Configuring and Verifying Route Redistribution) A) B) C) D) OSPF External EIGRP RIP Internal EIGRP
Q19)
In which two ways can you avoid routing loops that might result from two-way redistribution? (Choose two.) (Source: Configuring and Verifying Route Redistribution) A) B) C) D) Use the passive-interface command to suppress routing updates. Use route maps to redistribute internal routes only. Use route maps to implement route tagging. Use the no-loop keyword when redistributing routes.
Implement an IPv4-based Redistribution Solution
4-107

Q1) Q2) Q3) Q4) Q5) Q6) Q7) Q8) Q9) Q10) Q11) Q12) A, C A, B, D, F E B, C A A, C A, B, C B B B A Create a route map to configure new policy for routing, apply the route map to an incoming interface, or locally originated traffic. B A A D B D B, C
Q13) Q14) Q15) Q16) Q17) Q18) Q19)
4-108
ROUTE

Volume 3
Version 1.0
Student Guide
Student Guide
Table of Contents
Volume 3 Implementing Path Control
5-1
5-1 5-1
Assessing Path Control Network Performance Issues

Overview Objectives Assessing Path Control and Network Performance Using Filters to Determine Path Selection Using PBR to Determine Path Selection Configuring and Verifying PBR Configuring and Verifying PBR Operations on a Cisco Router Summary
5-3
5-3 5-3 5-4 5-6 5-13 5-15 5-18 5-32
Lab 5-1 Debrief

5-33
5-33 5-33 5-34 5-38 5-41
References to Additional Path Control in E-Learning

Overview Objectives Preview of E-Learning on Implementing Path Control Summary Module Summary Module Self-Check Module Self-Check Answer Key
5-43
5-43 5-43 5-44 5-48 5-49 5-51 5-54
Connect an Enterprise Network to an ISP Network

6-1
6-1 6-1
Planning the Enterprise-to-ISP Connection

Overview Objectives Connecting Enterprise Networks to an ISP Exchanging Routing Updates with an ISP Defining the Types of Connections to an ISP Summary
6-3
6-3 6-3 6-4 6-6 6-11 6-16
Considering the Advantages of Using BGP

Overview Objectives Using BGP to Connect to an ISP BGP Multihoming Options BGP Routing Between Autonomous Systems Comparison with IGPs Path Vector Functionality Features of BGP Summary
6-17
6-17 6-17 6-18 6-20 6-26 6-28 6-29 6-32 6-39
Comparing the Functions and Uses of EBGP and IBGP

Overview Objectives BGP Neighbor Relationships Establishing External BGP Neighbor Relationships Establishing Internal BGP Neighbor Relationships Summary
6-41
6-41 6-41 6-42 6-43 6-45 6-46
Configuring and Verifying Basic BGP Operations

Overview Objectives Specifications for Implementing BGP Establishing Internal and External BGP Neighbors Shutting Down a BGP Neighbor BGP Configuration Considerations Identifying BGP Neighbor States BGP Authentication Example of Activating Basic BGP BGP Verification Summary
6-47
6-47 6-47 6-48 6-50 6-58 6-59 6-65 6-72 6-75 6-77 6-88
Lab 6-1 Debrief

6-89
6-89 6-89 6-90 6-94 6-97
Using the BGP Attributes and Path Selection Process

Overview Objectives BGP Path Selection Path Selection with Multihomed Connection Characteristics of BGP Attributes for Path Selection and Path Manipulation Filtering of BGP Routing Updates Summary
6-99
6-99 6-99 6-100 6-104 6-106 6-120 6-127
Lab 6-2 Debrief

6-129
6-129 6-129 6-130 6-134 6-137
E-Learning Training on IPv6 and Routing for Branch Offices and Remote Workers 6-139
Overview 6-139 Objectives 6-139 Preview of E-Learning Modules Implementing IPv6 and Routing Facilities for Branch Offices and Mobile Workers 6-140 Summary 6-146 Module Summary 6-147 References 6-147 Module Self-Check 6-149 Module Self-Check Answer Key 6-157
ii
Module 5
Implementing Path Control

Overview
If you implement redundancy in a network, then multiple paths exist and the network administrator can manipulate or control the path across the network. Path control is not the same as quality of service (QoS) or MPLS traffic engineering (MPLS TE). Path control is a way to change the default packet forwarding across the network. This module explains why it is necessary to manipulate routing information in order to obtain better resiliency, performance, and availability. Path control involves the use of a collection of tools, or set of commands, to manipulate the routing protocol forwarding table and bypass the default packet forwarding. This module will provide an overview of these tools, configuration examples of policy-based routing, and performance issues related to path control.
Module Objectives
Upon completing this module, you will be able to evaluate common network performance issues and identify the tools needed to provide Layer 3 path control that uses Cisco IOS features to control the path. This ability includes being able to meet these objectives: Evaluate common network performance issues caused by inefficient path control selection and; also identify the resources necessary to develop a Layer 3 solution that uses Cisco IOS features to control path selection, given a set of network requirements, and implement Path Control between multiple IP routing protocols. Discuss the lab results for configuring and verifying path control between multiple IP routing protocols. Preview the e-learning products to teach the use of path control through additional methods. Preview the available e-learning training on implementing route control by other methods.
5-2
Lesson 1
Assessing Path Control Network Performance Issues

Overview
This lesson evaluates common network performance factors such as redundancy, resiliency, performance, availability, and adaptability. Issues related to these factors occur when control of path selection is inefficient. Several solutions exist to avoid these issues. This lesson identifies what resources are needed to provide a Layer 3 solution that uses Cisco IOS features to control path selection under a given set of network requirements. This lesson discusses the use of policy-based routing (PBR), filters (prefix lists, distribute lists, offset lists, and so on), Cisco IOS IP SLAs, and route tags as tools for implementing path control in large networks. Policy-based routing is described in detail, because it allows administrators to route traffic along specific paths according to their needs. PBR gives network designers greater flexibility in determining traffic patterns and best routes. Sometimes, simple destination-based routing is not sufficient. In these cases, network designers may route packets based on source address, protocol type, or application type so that they can optimally shape traffic patterns. This lesson discusses how to configure PBR on a Cisco router.
Objectives
Upon completing this lesson, you will be able to explain common network performance issues caused by inefficient path control selection. You will also be able to identify the resources you need to best provide path control, as well as implementation and verification of PBR. This ability includes being able to meet these objectives: Assess path control network performance. Use filters to determine path selection. Use PBR to determine path selection. Configure and verify PBR. Configure and verify PBR operations on a Cisco router.
Assessing Path Control and Network Performance

This topic describes how to assess path control network performance.
Assessing Path Control Network Performance

Multiple paths Suboptimal routing Availability of redundant paths Application-specific traffic path optimization Load sharing
ROUTE v1. 05-2
Networks are designed to provide high availability and redundancy. The use of different routing protocols and different connectivity options may result in inefficient paths for forwarding packets to their destinations. Not only is redundancy implemented, but each routing protocol has a different administrative distance, metric, and convergence time. When more than one routing protocol is implemented, there is high probability of inefficient routing. One major mistake is to implement incorrectly configured two-way multipoint redistribution. Two-way redistribution requires careful planning, not to mention multipoint redistribution, which is highly problematic. Convergence is also important. First, protocols converge in different ways from each other and in different ways for different network designs. Second, slow convergence can result in an application sending traffic time-outs before a backup path is found to a destination. Path control is required to avoid performance issues and to optimize paths. Backup is a high priority in modern networks. However, having redundancy does not guarantee resiliency. For redundancy to be effective, you must configure the network properly. This is true even if you are only a fine-tuning a routing protocol or managing path-by-path control tools. Network engineers should also distinguish between switching all of the traffic to the backup link if there is a primary link failure, and switching some traffic to back up the link if the primary link is congested. Path control mechanisms can improve performance in such a situation as well. Similarly load balancing can divide traffic among parallel paths.
Suboptimal routing can occur after redistribution or simply because different routing protocols use different metrics. Redistribution between two routing protocols, if done based on administrative distance, is likely to result in a suboptimal path. A routing protocol with a lower administrative distance likes its own routes more than routes coming from another routing protocol with a higher administrative distance value. The situation is similar for metrics. Redistribution resets the metric, and the original metric might not be translated correctly. You can use path control tools to change the default destination forwarding and optimize the path of the packets. There is no easy way to solve all of the issues with path control. It is important to establish a global strategy for path control that provides predictable and deterministic control over traffic patterns, taking into account the physical connectivity as well as the services running over the network infrastructure.
5-5
Using Filters to Determine Path Selection

This topic describes how to adjust the path selection process using filters.
Path Selection Process Using Filters

Manipulating path control by manipulating routing protocols and the routing table Tool availability is protocol-dependent: Route maps.... Prefix lists .. Distribute lists.... Administrative distance ... Route tagging Offset lists . Cisco IOS IP SLA PBR Previously covered Not covered yet
Paths are selected using the IP routing table. The contents of the IP routing table are provided by either a routing protocol or static route entries. The forwarding engine uses these contents to switch the packets from the incoming interface to the outgoing interface. You use filters to manipulate the routing protocols and routing table, in order to influence the desired path. Several filters or tools can be used to manipulate the routing table: Route maps Prefix lists Distribute lists Administrative distance Route tagging Offset lists Cisco IOS IP SLA PBR
5-6
Path Control Tools: Offset List

Routers R4 and R5 receive a subset of routes from the ISP. The link between R2 and R5 is slow. How do you make the path toward R4 the primary way out of the EIGRP network for a set of destinations?
ROUTE v1. 05-4
In the figure in the slide, the customer is using RIP and is connected to the Internet Service Provider (ISP) via edge routers R4 and R5. A subset of routes is received from each of the edge routers, and RIP increases the cost at every new hop. The cost between routers R2 and R5 is smaller than that between R4 and R5, because there is only one hop, even though this is very slow link. What configuration should be applied to router R2 in order to prefer the path toward edge router R4, which is must faster? The configuration should take into account that this rule is only valid for a set of destinations.
5-7
Path Control Tools: Offset List (Cont.)

An offset value to incoming and outgoing metrics to routes learned is added Supported protocols: EIGRP RIP
The router applies an offset of 2 to routes learned from the serial 0/0 interface with the match on access list 21.
ROUTE v1. 05-5
In order to configure a route to avoid a slow link on router R2, use an offset list on the router.. The offset-list command adds an offset to incoming and outgoing metrics to routes learned via Enhanced Interior Gateway Routing Protocol (EIGRP) or Routing Information Protocol (RIP). The offset value is added to the routing metric. An offset list with an interface type and interface number is considered extended and takes precedence over an offset list that is not extended. Therefore, if an entry passes an extended offset list and a normal offset list, the offset of the extended offset list is added to the metric. In the figure in the slide, the offset-list 21 in 2 serial 0/0 command is used to apply an offset of 2 to routes learned from serial interface 0/0 with the match on access list 21. The command in the slide is entered into the RIP process configuration mode on router R2. With this command, the cost of a selection of routes coming from the Serial 0/0 interface is increased, effectively making it worse than the path toward router R4. Therefore, for a selection of routes, router R4 becomes the way out from the customer network. For more details, about the offset-list (EIGRP) and offset-list (RIP) commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
5-8
Path Control Tools: Cisco IOS IP Service Level Agreement

End-to-end network performance tests based on clear measurement metrics Can be used for path control Configuration: Define one or more probes Define one or more tracking objects Define the action on the tracking object
ROUTE v1. 05-6
Cisco IOS IP Service Level Agreements (SLAs) perform network performance measurement within Cisco Systems devices. They use active traffic monitoring (the generation of traffic in a continuous, reliable, and predictable manner) for measuring network performance. Cisco IOS IP SLAs actively send data across the network to measure performance between multiple network locations or across multiple network paths. They use timestamp information to calculate performance metrics, such as jitter, latency, network and server response times, packet loss, and mean opinion score. The following steps are required to configure Cisco IOS IP SLA functionality: Define one or more probes Define one or more tracking objects Define the action for each tracking object
Note E-learning training is available for path control topics that provide more information about Cisco IOS IP SLAs.
5-9
Cisco IOS IP SLA Example

Customer A is multihoming to ISP-1 and ISP-2 The link to ISP-1 is the primary link for all traffic Customer A is using the default routes to the ISPs A Cisco IOS IP SLA is used to conditionally announce the default route
ROUTE v1. 05-7
The following example describes the use of Cisco IOS IP SLA functionality for path control. Customer A is multihoming to two service providers and is not using BGP as the routing protocol. Default routes are configured instead. In order to make one link a primary link and the second one a backup link, two static routes with different administrative distances can be configured. The static default route with a lower administrative distance will be preferred and inserted into the IP routing table. However, it is possible that the interface is up and the ISP has problems with the provider edge (PE) router or with the uplink connectivity toward the Internet. In such a case, the active default route sends traffic to the selected ISP, but all of the traffic is lost. The solution to this issue is to use Cisco IOS IP SLA functionality, which can be used to continuously check the reachability of a specific destination (PE interface, ISP, DNS server, or any other trusted destination) and conditionally announce the default route if the connectivity is verified. The configuration required is shown in the next figure.
5-10
Cisco IOS IP SLA Example
Sets the probe to send an ICMP packet every 10 seconds to IP address 10.1.1.1 Starts sending packets now and continues forever
Defines the tracking of object 1 linked to ip sla 11
Announces the default route to 10.1.1.1 with an administrative distance of 2 if tracking object 1 is true
In the figure in the slide, three steps to configure Cisco IOS IP SLA functionality are shown. The first step is needed to define the probe. The probe number 11 is defined by issuing the ip sla monitor 11 command. The test defined with the type echo protocol ipIcmpEcho 10.1.1.1 source-interface FastEthernet0/0 command specifies to send the Internet Control Message Protocol (ICMP) echoes to destination 10.1.1.1 to check the connectivity. The FastEthernet0/0 interface is used as a source. The frequency 10 command schedules the connectivity test to repeat every 10 seconds and, finally, the ip sla monitor schedule 11 life forever start-time now command defines the start and end times of the connectivity test for probe 11. The start time is now and the end time is forever. The second step requires the tracking object, which is linked to the probe from step one. The track 1 ip sla 11 reachability command defines the tracking of object 1, which is linked to probe 11, and the reachability of the 10.1.1.1 is tracked. The last step is an action based on the status of the tracking object. The ip route 0.0.0.0 0.0.0.0 10.1.1.1 2 track 1 command conditionally announces the default route to 10.1.1.1 with an administrative distance of 2 if the result of tracking object 1 is true. For more details about the Cisco IOS IP SLA commands, please check the Cisco IOS IP SLAs Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_01.html
5-11
Cisco IOS IP SLA Example (Cont.)
Sets the probe to send an ICMP packet every 10 seconds to IP address 11.1.1.1 Starts sending packets now and continues forever
Defines the tracking of object 1 linked to ip sla 11
Announces the default route to 11.1.1.1 with an administrative distance of 3 if tracking object 2 is true
This is an example in which Customer A is multihoming to two ISPs. It requires the configuration of two probes, two tracking objects, and two conditionally announced default routes. The configuration in the figure in the slide is almost the same as the configuration in the previous figure. The probe number is different, because the second test condition tests the reachability of the backup ISP destination address. The tracking object number is different, as well, because it is related to the second probe. Finally, the announced default route uses a higher administrative distance (an administrative distance number of 3 is configured in the configuration in the slide) as the backup. The ISP is used only if the primary is not available. Of course, the second tracking object is used as a reference for a conditional announcement for this default route.
5-12
Using PBR to Determine Path Selection

This topic describes how policy-based routing is used to implement path control.
Policy-Based Routing
Allows you to implement policies that selectively cause packets to take different paths. IP routing is destination-based PBR avoids destination-based routing Is applied to incoming packets Makes traffic marking possibility Requires a route map to implement the policy Matched routes are modified by set commands
RO UTE v 1.05-10
PBR offers significant benefits in terms of implementing user-defined policies to control traffic in the internetwork. It provides solutions in cases where legal, contractual, or political constraints dictate that traffic be routed through specific paths. PBR adds flexibility in a difficult-to-manage environment by giving the network administrator the ability to route traffic based on network needs. For network managers who implement routing policies in their networks, PBR provides an extremely powerful, simple, and flexible tool. PBR also provides a mechanism for marking packets. As a result, differentiated preferential service can be provided to different types of traffic in combination with queuing techniques that are available in Cisco IOS software. Policy-based routing is used to bypass the routing table. It allows the network administrator to configure different routing rules beyond the original IP routing table. One of the ways it can be used is to route packets based on the source IP address instead of the destination IP address. PBR is applied to incoming packets and is implemented using route maps, for which match commands are used to match the incoming packets and a subset of the set commands are used to change the default destination-based routing.
5-13
Policy-Based Routing Benefits

Source-based transit provider selection Different users go different ways QoS Sets the precedence or ToS; used with queuing Load sharing Forces load sharing without regard to the routing table Cost savings Distributes traffic economically
RO UTE v 1.05-11
These benefits are achieved by implementing PBR in a network: Source-based transit-provider selection: ISPs and other organizations use PBR to route traffic originating from different sets of users through different Internet connections across the policy routers. Quality of service (QoS): Organizations provide QoS to differentiated traffic using the following two methods: Set the precedence or type of service (ToS) value in each IP packet header at the periphery of the network. Leverage queuing mechanisms to prioritize traffic in the core or backbone of the network.
Cost savings: Organizations achieve cost savings by distributing interactive and batch traffic among low-bandwidth, low-cost, permanent paths and high-bandwidth, high-cost, switched paths. Load sharing: In addition to the dynamic load-sharing capabilities that are offered by destination-based routing that is supported by Cisco IOS software, network managers can implement policies to distribute traffic among multiple paths based on the traffic characteristics.
5-14
Configuring and Verifying PBR

This topic describes how to configure and verify PBR.
Steps to Implement Path Control

Choose the path control tool Match traffic to manipulate the path Define the action for matched traffic Apply path control to traffic To incoming traffic To traffic local to the router Verify path control results
RO UTE v 1.05-12
The figure in the slide shows the steps required to implement path control: Choose the path control tool. Path control tools can manipulate the IP routing table or bypass it. You must select the correct tool in order to fulfill the requirements. When you select the path control tool, implement a traffic-matching configuration to specify which traffic will be manipulated. When traffic is classified and matched, define the action for a specific class of traffic, in order to efficiently control the path of packets. After a successful configuration of path control, apply statements to manipulate the packets for incoming traffic or traffic local to the router. Verify path control. You can use simple connectivity commands and several show commands.
5-15
Requirements for Policy Based Routing

Match packets with the destination network 7.7.7.0 and forward them to the next hop 6.6.6.6 Match packets between 3 and 200 bytes in size and forward them to the interface Ethernet 0 Apply the route map to the incoming interfaces Verify the configuration
RO UTE v 1.05-13
The figure in the slide shows the requirements for PBR implementation. PBR is implemented by using the route maps, for which match commands are used to match the traffic and set commands are used to set desired action to control the path. In the example in the slide, configuration is required to match packets going to the destination network 7.7.7.0 and forward them to the next hop 6.6.6.6 to avoid suboptimal routing. At the same time, packets with sizes between 3 and 200 bytes must be matched and forwarded to interface Ethernet 0. The route map must be applied to the incoming interfaces. Finally, the configuration must be verified.
5-16
Steps to Configure and Verify PolicyBased Routing

Enable PBR by configuring a route map: Match traffic using the match command Define the action for matched traffic using the set command Enable fast-switched PBR or PBR switched by Cisco Express Forwarding (Optional) Apply a route map: To an incoming interface To packets that are generated by the router Verify the PBR configuration
RO UTE v 1.05-14
The requirements from the previous figure are used to create the implementation plan for PBR configuration. The implementation plan includes the following steps to configure and verify PBR on Cisco routers: Enable PBR by configuring the route map. Traffic is matched using the match command. Actions for manipulating path control are defined using set commands. If desired, enable fast-switched PBR or PBR switched by Cisco Express Forwarding. Fastswitched PBR must be enabled manually. For PBR switched by Cisco Express Forwarding, in contrast, is automatically enabled when CEF switching is enabled. Apply the route map created to an incoming interface or to locally generated packets in the router. Verify PBR configuration with basic connectivity and path verification commands, as well as policy routing show commands.
5-17
Configuring and Verifying PBR Operations on a Cisco Router

This topic describes how to configure and verify PBR on a Cisco Router.
Matching the Traffic
Configure a route map
Matches IP addresses for policy routing Access list 10 is used to match the IP address
Matches the Layer 3 length of the packet for policy routing Packets between 3 and 200 bytes long are matched
Use the route-map command to enable policy routing in the router and to enter the match and set commands required. IP standard or extended access lists are used to establish the PBR match criteria using the match ip address command. The match ip address 10 command matches traffic based on standard IP access list number 10. A standard IP access list is used to specify the match criteria for the source address of a packet. Extended access lists are used to specify the match criteria based on source and destination addresses, application, protocol type, ToS, and precedence. The match length command matches packets based on packet length, and can be configured with a minimum and maximum value. For example, a network administrator can use the match length command to distinguish between interactive traffic and file transfer (bulk) traffic, because file transfer traffic typically has larger packet sizes. The match length 3 200 command matches packets between 3 and 200 bytes long. For more details about the route-map and match commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
5-18
Policy Routing set Commands
This command defines where to forward packets that pass a match clause of a route map for policy routing. Packets that pass the match clause are forwarded to the router at IP address 6.6.6.6.
This command also defines where to forward packets that pass a match clause of a route map for policy routing. Packets that pass the match clause are forwarded to the Ethernet 0 interface.
If the match statements are satisfied, one or more of the following set statements are used to specify the criteria for forwarding packets. The router evaluates the four set commands for PBR that are shown in this figure and in the following figure, the order listed. Once you choose a destination address or interface, other set commands for changing the destination address or interface are ignored. Some of these commands affect only packets for which there is an explicit route in the routing table, and others affect only packets for which there is no explicit route in the routing table. A packet that is not affected by any of the set commands in a route map statement is not policyrouted; it is forwarded normally. In other words, destination-based routing is performed. The router uses the four set commands for PBR in the following order: 1. The set ip next-hop command configures a list of IP addresses. The list specifies the adjacent next-hop router in the path toward the destination to which the packets are forwarded. If more than one IP address is specified, then the first IP address that is associated with a currently active interface is used to route the packets.
Note
With the set ip next-hop command, the routing table is checked only to determine if the next hop is reachable. It is not checked to determine if there is an explicit route for the destination address of the packet. This set command affects all packet types and is always used if it is configured.
The set ip next-hop 6.6.6.6 command from the figure in the slide shows that packets that pass a match clause of a route map for policy routing are forwarded to 6.6.6.6. 2. The set interface command configures a list of interfaces through which the packets are routed. If more than one interface is specified, then the first active interface in the list is used for forwarding the packets.
2009 Cisco Systems, Inc. Implementing Path Control 5-19
Note
If there is no explicit route in the routing table for the destination network address of the packet (for example, if the packet is a broadcast packet or is destined to an unknown address), the set interface command has no effect and is ignored. A default route in the routing table will not be considered an explicit route for an unknown destination address.
The set interface ethernet 0 command from the figure in the slide defines that packets that pass a match clause of a route map for policy routing are forwarded to interface Ethernet 0. For more details about the set command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
5-20
Policy Routing set Commands (Cont.)
This command defines where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS Software has no explicit route to a destination.
This command defines where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination. This is recommended only for point-to-point links.
RO UTE v 1.05-17
3. The set ip default next-hop command configures a list of default next-hop IP addresses if there is no explicit route available to the destination address of the packet being considered for PBR. If more than one IP address is specified, then the first next hop specified that appears to be adjacent to the router is used. The optional specified IP addresses are tried in sequential order.
Note A packet is routed to the next hop specified by the set ip default next-hop command if there is no explicit route for the destination address of the packet in the routing table. A default route in the routing table will not be considered an explicit route for an unknown destination address.
The set ip default next-hop 6.6.6.6 command from the figure in the slide defines that packets that pass a match clause of a route map for policy routing and for which the Cisco IOS Software has no explicit route are forwarded to 6.6.6.6. 4. The set default interface command configures a list of default interfaces. If there is no explicit route available to the destination address of the packet that is being considered for PBR, then it is routed to the first active interface in the list of specified default interfaces.
5-21
Note
A packet is routed out of the interface that is specified by the set default interface command only if there is no explicit route for the destination address of the packet in the routing table. A default route in the routing table will not be considered an explicit route for an unknown destination address.
The set default interface ethernet 0 command from the figure in the slide defines that packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route are forwarded to interface Ethernet 0. PBR also provides a mechanism to mark packets using the set ip tos and set ip precedence commands: The set ip tos command is used to set the IP ToS value in the IP packets. The set ip precedence command is used to set the IP precedence in the IP packets. You must specify either the precedence number or name.
Note The set commands can be used in conjunction with each other.
For more details about the set command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
5-22
Apply Route Maps for PBR
This command specifies the route map to use for policy routing on an incoming interface that is receiving packets that need to be policy-routed.
Specifies the route map to use for policy routing of all packets that originate on the router.
RO UTE v 1.05-18
To identify a route map to use for PBR on an interface, use the ip policy route-map interface configuration command. In the figure in the slide, the ip policy route-map PBRmap command applies the route map named PBRmap to the incoming traffic on the interface.
Note PBR is specified on the incoming interface that receives the packets that need to be policyrouted, not on the interface from which the packets are sent.
To identify a route map to use for local policy routing, use the ip local policy route-map global configuration command. In the figure in the slide, the ip local policy route-map PBRmap command applies the route map named PBRmap to packets that originate on the router. Packets that are generated by the router are not normally policy-routed. However, you can use this command to policy-route such packets. You might enable local-policy routing if you want packets that originate at the router to take a route other than the obvious shortest path. For more details about the ip policy route-map and ip local policy route-map commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
5-23
Enable Fast-Switched PBR or PBR Switched by Cisco Express Forwarding

Optional command Fast-switched PBR must be enabled manually Switching of PBR by Cisco Express Forwarding is enabled automatically
Enables fast-switched policy routing
RO UTE v 1.05-19
PBR must be configured before PBR fast switching can be enabled. Fast-switching of PBR is disabled by default. To configure a fast-switched PBR, use the ip route-cache policy command in interface configuration mode. A fast-switched PBR supports all of the match commands and most of the set commands, except for these restrictions: The set ip default next-hop command is not supported. The set interface command is supported over point-to-point links, unless a route cache entry exists that uses the same interface that is specified in the set interface command in the route map. Also, at the process level, usually the routing table is checked to determine if the interface is on an appropriate path to the destination. During fast switching, the software does not make this check. Instead, if the packet matches, the software automatically forwards the packet to the specified interface.
Note Since the release of Cisco IOS Release 12.0, IP PBR can now be fast-switched. Prior to this feature, PBR was process-switched, which meant that on most platforms, the switching rate was approximately 1000 to 10,000 packets per second (p/s). This rate was not fast enough for many applications. Users who require PBR to occur at faster speeds can now implement it without slowing down the router.
Beginning with Cisco IOS Release 12.0, PBR is supported in the Cisco Express Forwarding switching path. PBR switched by Cisco Express Forwarding has better performance than fastswitched PBR and, therefore, is the optimal way to perform PBR on a router. No special configuration is required to enable PBR to be switched by Cisco Express Forwarding. It is on by default as soon as you enable Cisco Express Forwarding and PBR on the router.
5-24
Note
The ip route-cache policy command is strictly for fast-switched PBR; it is not required for a PBR switched by Cisco Express Forwarding.
For more details about the ip route-cache policy command, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
5-25
Verifying Policy-Based Routing
Displays route maps that are configured on the interfaces.
Displays a route map.
RO UTE v 1.05-20
To display the route maps used for PBR on the interfaces of the router, use the show ip policy EXEC command. To display configured route maps, use the show route-map EXEC command. For more details about the show ip policy and show route-map commands, please check the Cisco IOS IP Routing Protocols Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
5-26
Verifying Policy-Based Routing (Cont.)
Enables the display of IP policy routing events.
The extended traceroute command allows for the specification of the source address.
The extended ping allows for the specification of the source address.
Use the debug ip policy EXEC command to display the IP PBR packet activity. This command shows, in detail, the activities that the PBR is performing. It also displays information that indicates whether a packet matches the criteria. If the criteria match, the resulting routing information for the packet is displayed as well.
Note Because the debug ip policy command generates a significant amount of output, use it only when traffic on the IP network is low, so that other activity on the system is not adversely affected.
To discover the routes that packets follow when traveling to their destination from the router, use the traceroute privileged EXEC command. To change the default parameters and invoke an extended traceroute test, enter the command without a destination argument. You will be guided through a dialog to select the required parameters. To check host reachability and network connectivity, use the ping privileged EXEC command. You can use the extended command mode of the ping command to specify the supported header options by entering the command without any arguments. For more details about the debug ip policy command, please check the Cisco IOS Debug Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/debug/command/reference/db_book.html For more details about the ping and traceroute commands, please check the Cisco IOS Configuration Fundamentals Command Reference via the following link: http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_book.html
5-27
Example: PBR Equal Access

All traffic that uses a default route and is sourced from subnet 1.1.0.0 should go through ISP 1. All traffic that uses a default route and is sourced from subnet 1.2.0.0, should go through ISP 2.
RO UTE v 1.05-22
The example in the figure in the slide describes a common scenario in which a private company that is attached to more than one ISP must build a traffic policy. In this figure, router R1 provides Internet access for a private enterprise. Router R1 is connected to two different ISPs. This router advertises a 0.0.0.0 default route into the enterprise network to avoid a large Internet routing table. The problem is that when traffic from the enterprise networks 1.1.0.0 and 1.2.0.0 reaches router R1, the traffic can go to ISP 1 or ISP 2. The company prefers to have ISP 1 and ISP 2 receive approximately equal amounts of traffic. PBR is used to shape or load-balance traffic from router R1 to each of the ISPs. PBR is implemented at router R1. All traffic sourced from the 1.1.0.0 subnet is forwarded to ISP 1 if there is no specific route to the destination in the routing table (the default route is not used). All traffic sourced from the 1.2.0.0 subnet is forwarded to ISP 2 if there is no specific route to the destination in the routing table.
Note Remember, this policy provides for an outbound traffic policy from the enterprise to its ISPs only. It does not determine the inbound traffic policy for router R1. It is possible that traffic from 1.1.0.0 going out to ISP 1 will receive responses from ISP 2.
5-28
Example: PBR Equal Access (Cont.)

RO UTE v 1.05-23
The configuration that is shown in the figure in the slide has been set in router R1. The name of the route map is equal-access. The ip policy route-map equal-access command has been applied to the Ethernet 0 interface, which is the incoming interface that receives the packets to be policy-routed. Sequence number 10 in the route map equal-access is used to match all packets that are sourced from any host in subnet 1.1.0.0. If a packet matches, and if the router has no explicit route for its destination, then the packet is sent to the next-hop address 6.6.6.6 (ISP 1 router). Sequence number 20 in the route map equal-access is used to match all packets that are sourced from any host in subnet 1.2.0.0. If a packet matches, and if the router has no explicit route for its destination, then the packet is sent to the next-hop address 7.7.7.7 (ISP 2 router). Sequence number 30 in the route map equal-access is used to drop all traffic that is not sourced from subnet 1.1.0.0 or 1.2.0.0. The null0 interface is a route to nowhere (thus, the traffic is dropped).
5-29
Verifying Policy-Based Routing: Examples

RO UTE v 1.05-24
In the figure in the slide, the output provides examples of two show commands issued on router R1. The show ip policy command output indicates that the route map called equal-access is used for PBR on the Ethernet0 interface of the router. The show route-map command output indicates that three packets have matched sequence 10 of the route map equal-access.
5-30
Verifying Policy-Based Routing: Examples (Cont.)

RO UTE v 1.05-25
In the figure in the slide, the output provides an example of the debug ip policy command output. The show logging command shows the logging buffer, including the output of the debug command. The output indicates that a packet from 1.1.1.1 destined for 190.168.1.1 has been received on interface Ethernet0 and that it is policy-routed on Serial0 to next hop 6.6.6.6. The source address of 1.1.1.1 matches line 10 of the route map equal-access.
5-31
Summary
Summary
Redundant paths (multiple paths), redistribution, and the selected routing protocol all affect network performance. Path control must be enabled to improve performance and avoid suboptimal routing. A route map with a group of match and set commands is one of the tools that can be used for path control. The path selection process can be accomplished using filters such as: route tagging, prefix lists, distribute lists, administrative distance, offset lists, and Cisco IOS IP SLAs. In order to bypass the routing table destination-based forwarding, policy-based routing is used to determine path selection.
RO UTE v 1.05-26
Summary (Cont.)
Policy-based routing uses route maps for configuration. It can be fast-switched or switched by Cisco Express Forwarding. Path control match commands match incoming traffic. Path control set commands manipulate the path; manipulation can be applied to incoming traffic or to traffic generated by the router.
RO UTE v 1.05-27
5-32
Lesson 2
Lab 5-1 Debrief

Overview
In Lab 5-1, students manipulate the path for a selection of the packets traveling across the network. First they configure the routing protocol to assure reachability and to establish the base for destination-based forwarding. Next they implement path control to manipulate the path for a set of packets. Students define several groups of packets and use policy-based routing (PBR) to manipulate the path across the network. Finally, they verify the configuration.
Objectives
Upon completing this lesson, you will be able to explain destination-based forwarding and configure path control using a PBR tool. This ability includes being able to meet these objectives: Complete the lab overview and verification Describe a sample solution and alternatives

Lab Topology
ROUTE v1. 05-2
This figure shows the physical lab topology used for Lab 5-1: Configure and verify Path Control between multiple IP routing protocols. The topology uses four pod routers and one switch. Routers R1 to R4 build the network where path manipulation is required, and switch SW1 is one source of packets. The other source is locally-originated traffic on router R1. Based on this topology, students will identify the required parameters and configure the EIGRP routing protocol in order to establish Layer-3 reachability in the network. Because some packets use suboptimal paths, they will use PBR as a path, control mechanism to manipulate the path of the packets.
5-34

Task 1: Implementing EIGRP Routing What were the steps you took to configure EIGRP routing protocol? Task 2: Implementing Policy-Based Routing (PBR) Which tools did you use to configure PBR? Where did you apply the PBR configuration for the traffic passing through the router? Where did you apply the PBR configuration for the traffic locally originated in the router?
ROUTE v1. 05-3
In the first task, you implement EIGRP routing protocol on all routers in the lab (from R1 to R4). You establish basic reachability and use verification steps to prove that all of the EIGRP networks are in the IP routing table. Once you finish the configuration, you can identify the path used for forwarding packets. In the second task, you identify the suboptimal path used for a group of packets and use policybased routing (PBR) as a path-control tool to manipulate packet forwarding. You use route maps to match the packets and set the output parameters. Then you apply the route maps to traffic on the incoming interface (for packets passing the router) or to locally generated traffic on routers R1 and R3.
5-35
Verification
Did you have enough information to create the implementation plan? Did you successfully configure the EIGRP routing protocol? Did you check which path the packets took? Did you successfully configure PBR? Did the packets take the same path they took before PBR was applied?
ROUTE v1. 05-4
A common approach to verifying the implementation process for a routing protocol is to follow these steps: In order to create the implementation plan, gather enough information. Check that routes exist in their local IP tables; they will be in the tables after any successful EIGRP configuration. Check the IP routing table for the routes to the destinations. The IP routing table provides all of the information needed to forward incoming packets toward their destinations. Based on the routing protocol used, the path for a packet is defined as the route to its destination, provided that exists in the IP routing table. To meet the requirements for path manipulation, configure the PBR path-control tool. You must specify a path for the selected group of packets within the requirements for path manipulation. You can also perform verification. If PBR is configured, the path for the selection of packets is different.
5-36
Checkpoints
Configure EIGRP. Examine and verify that the EIGRP routing protocol is up and running. Verify the IP routing table. Examine the path of IP packets. Configure PBR. Examine the path of the IP packets after the PBR configuration.
ROUTE v1. 05-5
With different checkpoints, the network operator can verify for proper configuration. The following checkpoints are used for verification: Configure EIGRP. Examine and verify that the EIGRP routing protocol is up and running. Verify the IP routing table for EIGRP routes. Examine the path of IP packets when destination-based forwarding is used (without PBR configuration applied). Configure PBR. Examine the path of IP packets after PBR configuration.
5-37

A Sample Solution
EIGRP is configured on all the routers. EIGRP automatic summarization takes effect. PBR is configured on routers R1 and R3 to manipulate the path selection.
ROUTE v1. 05-6
The sample solution in the slide includes implementation details and details for each task of the implementation plan. Different solutions are possible; the figure points out a few details of a successful configuration. The proper implementation of the routing protocol might include the following details: EIGRP AS 1 is implemented. IP addressing is used with mask /24. Automatic summarization is not desired, as the hiding of subnets might prevent a successful PBR implementation. After successful EIGRP configuration and verification of the path taken for the packets, PBR needs to be configured. Path manipulation is configured in the router where path manipulation is desired. Many times, this router is close to the source.
5-38
Another routing protocol can be used to provide a different path. Static routes can be used. The metric and administrative distance can be changed. Another path control manipulation tool can be used.
ROUTE v1. 05-7
In order to manipulate the path or to influence the destination-based forwarding, another routing protocol can be selected and configured. Instead of a routing protocol, static routes can be configured. This solution is not scalable, but provides control over packet forwarding. Static routes can also be use as a path manipulation mechanism, because a static route has a lower administrative distance value than any routing protocol. A network operator can manipulate the path by changing the metric of the link, the administrative distance of the static routes, or the routing protocol. Instead of using PBR as a path-control tool, a network operator can use one of several other tools, including filtering (prefix lists, distribute lists, administrative distance, route tagging, offset lists, and Cisco IOS IP SLAs).
5-39
Q and A
Why is routing protocol selection important? Why is changing the default destination-based forwarding important? Which tool is used for PBR implementation? How is classification in the route map performed? How is the path between the packet source and destination verified?
ROUTE v1. 05-8
A routing protocol exchanges routing updates and populates the IP routing table, which is used for destination-based forwarding. Sometimes, simple destination-based routing is not sufficient. In these cases, network designers may route packets by source address, protocol type, or application type, so that they can optimally shape traffic patterns. PBR uses route maps to match packets and set where to forward packets that pass a route map match clause. The match commands in route maps are used to match the traffic. Basic connectivity between the source and destination is verified using the ping command. The path is verified hop-by-hop using the traceroute command.
5-40
Summary
Summary
Configure an EIGRP routing protocol to establish reachability in the network and enable destination-based forwarding. Configure policy-based routing to manipulate the path for a specific set of packets and verify the configuration.
ROUTE v1. 05-9
5-41
5-42
Lesson 3
References to Additional Path Control in E-Learning

Overview
The Implementing Cisco IP Routing (ROUTE) v1.0 instructor-led training (ILT) course is a comprehensive learning experience. Among the learning tools it makes available to you are elearning modules, which complement the classroom instructor-led content, as well as self-paced materials and demonstrations. Upon accessing the e-learning content, you will be able to reinforce the knowledge acquired in class and witness real-life scenarios demonstrated in real routers and switches. The content structure is flexible: you can navigate it at your own pace, at the time of your choosing, and at the depth you desire, according to your level of experience. This lesson provides an overview of the Implementing Path Control e-learning module. The content includes demonstrations that cover several topics in path control, such as additional design considerations, route tagging, policy routing, IP SLAs.
Objectives
Upon completing this lesson, you will be able to review the e-learning modules that pertain to path control. This ability includes being able to meet these objectives: Describe the contents of the Implementing Path Control e-learning module. Understand the process of accessing and using e-learning content.
Preview of E-Learning on Implementing Path Control

This topic describes e-learning products that teach the configuration and implementation of path control.
CCNP E-Learning
Cisco CCNP E-Learning allows you to do the following: Complement and enhance your classroom experience Reinforce concepts and their application Learn at your own pace Review advanced topics Experience real-life scenarios through directed demonstrations
ROUTE v1. 05-2
One of the key ideas behind the design of the Cisco CCNP curriculum is the understanding that there is no one "best" method of learning for every student. Some students prefer individual labs, while others prefer one-on-one tutoring, hands-on sessions, self-paced computer-assisted instruction, direct-discovery learning, or cooperative learning, among others. E-learning solutions offer new approaches that complement and enhance classroom-based learning. Designed with flexibility and learning effectiveness in mind, the Implementing Path Control e-learning module is based on knowledge you acquired during your Implementing Cisco IP Routing (ROUTE) v1.0 instructor-led training course.
5-44

Lesson Parallel Processes in Path Control Directed Demo: Procedures to Implement Path Control by other Methods Self-Check Assessment Description
Reinforces design fundamentals through the integration of multiple Cisco IOS tools. Presents advanced topics in path control that you may find useful in certain situations. Demonstrates router configuration for scenarios of redistribution with multiple edge routers and dynamic advertisements using IP SLAs.
Assesses your understanding of the lesson.
ROUTE v1. 05-3
The Implementing Path Control e-learning module covers topics that complement the classroom module you are reviewing. After a brief introductory lesson that discusses design issues and the integrated approach to path control, you will be able to follow a directed demonstration of real-life scenarios that combine multiple Cisco IOS features to accomplish specific objectives. These demonstrations include the use of tools such as administrative distance, route tagging, and IP SLA tracking.
5-45
Where to Find E-Learning Modules

The Implementing Path Control e-learning module is available on a CD as part of your classroom materials. Please contact your instructor with any questions you have about finding and accessing the CD. The objectives of the Implementing Path Control e-learning module are part of your CCNP certification exam. As such, candidates for CCNP certification should review these objectives.
5-46
E-Learning Module Structure
ROUTE v1. 05-5
Utilizing a combination of lecture sessions, animated content, lab demonstrations, and assessments, each e-learning module presents a hierarchical structure of lessons and topics. You can navigate through the structure by using an intuitive GUI that includes playback controls, slide selection, and lesson and topic selection. By using these tools, you will be able to navigate the content at your own pace. The three-panel screen used for directed demonstrations allows you to focus on the device console demonstrations, while still allowing you to look at the command syntax and topology diagram for verification and additional information.
5-47
Summary
Summary
The Implementing Path Control e-learning module complements the current module and is part of the same Cisco certification. You can access e-learning content from the Cisco certifications website, and complete it according to the learning style that is most effective for you.
ROUTE v1. 05-6
5-48
Module Summary
Module Summary
When common network performance issues such as redundancy, resiliency, performance and availability are solved, the proper path control tools must be used for efficient control of path selection. Several solutions exist to avoid these issues. Policy based routing (PBR), filters (prefix lists, distribute lists, offset lists, and so on), Cisco IOS IP SLAs, and route tags can be used to implement path control in large networks.
ROUTE v1. 05-1
This module covered common network performance issues such as redundancy, resiliency, performance, and availability. A solution to these issues frequently results in an inefficient path being selected, and the default destination-based routing is not the best solution. You must change the routing table by manipulating routing updates that are entered in the routing table or by bypassing the routing table. Several tools can be used for efficient path control: Route maps Prefix lists Distribute lists Administrative distance Route tagging Offset lists Cisco IOS IP SLAs Policy based routing All of these tools must first match traffic, then set actions for the matched traffic.
5-49
5-50
Module Self-Check
Use the questions here to review what you learned in this module. The correct answers and solutions are found in the Module Self-Check Answer Key. Q1) Which four issues are the result of multiple paths? (Choose four.) (Source: Assessing Path Control Network Performance Issues) A) B) C) D) E) Q2) suboptimal routing unavailable redundant paths traffic optimized for only one application uneven load sharing incomplete route summarization
Which three tools can be used for path manipulation? (Choose three.) (Source: Assessing Path Control Network Performance Issues) A) B) C) D) E) filters policy-based routing (PBR) redistribution route maps summarization
Q3)
Path control tools can be used to bypass the IP routing table. (Source: Assessing Path Control Network Performance Issues) A) B) true false
Q4)
Which two commands are used inside route maps? (Choose two.) (Source: Assessing Path Control Network Performance Issues) A) B) C) D) E) classify set redistribute match policy
Q5)
Which command is used to match traffic inside route maps based on access list 10? (Source: Assessing Path Control Network Performance Issues) A) B) C) D) match ip address 10 match access-list 10 match ip acl 10 match ip access-list 10
Q6)
Which path control tool uses mask filtering, for which either a defined prefix is matched or part of an address space with a subnet mask longer or shorter than a set number is matched? (Source: Assessing Path Control Network Performance Issues) A) B) C) D) E) F) distribute lists administrative distance route tagging offset lists Cisco IOS IP SLAs prefix lists
Module Self Check
5-51
Q7)
Which tool can be used for end-to-end network performance tests based on clear measurement metrics, as well as for path control? (Source: Assessing Path Control Network Performance Issues) A) B) C) D) E) F) distribute lists administrative distance route tagging offset lists Cisco IOS IP SLAs prefix lists
Q8)
Policy-based routing avoids destination-based routing. (Source: Assessing Path Control Network Performance Issues) A) B) true false
Q9)
To which two of these are path control tools applied? (Choose two.) (Source: Configuring and Verifying Path Control) A) B) C) D) incoming traffic outgoing traffic traffic locally generated in the router MTU-sized packets
Q10)
Which two commands provide a basic connectivity test? (Choose two.) (Source: Configuring and Verifying Path Control) A) B) C) D) show route-map show ip policy ping traceroute
Q11)
Which command defines the interface on which to output packets that pass a route map match clause for policy routing and for which the Cisco IOS software has no explicit route to a destination? (Source: Configuring and Verifying Path Control) A) B) C) D) set ip next-hop 10.1.1.1 set interface ethernet 0 set ip default next-hop 10.1.1.1 set default interface ethernet 0
Q12)
Which command displays route maps that are configured on interfaces? (Source: Configuring and Verifying Path Control) A) B) C) D) show ip policy show route-map map-name show ip routing table show ip interface brief
Q13)
Policy-based routing uses a route map for its configuration and can be fast-switched or switched by Cisco Express Forwarding. (Source: Configuring and Verifying Path Control) A) B) true false
5-52
Q14)
The show ip policy command output shows policy routing matches. (Source: Configuring and Verifying Path Control) A) B) true false
Module Self Check
5-53

Q1) Q2) Q3) Q4) Q5) Q6) Q7) Q8) Q9) Q10) Q11) Q12) Q13) Q14) A, B, C, D A, B, D A B, D A F E A A, C C, D D A A B
5-54
Module 6
Connect an Enterprise Network to an ISP Network

Overview
The Internet has become a vital resource in many organizations, which requires a single connection and frequently redundant connections to multiple Internet service providers (ISPs). With multiple connections, the Border Gateway Protocol (BGP) is an alternative to using default routes to control path selections. BGP provides several alternatives to using default routes. Use of BGP as a routing protocol requires that an administrator understand how to properly configure BGP for scalable internetworking. This module discusses BGP configuration and verification when connecting an enterprise network to ISP networks.
Module Objectives
Upon completing this module, you will be able to implement and verify a Layer 3 solution using BGP to connect an enterprise network to an Internet service provider. This ability includes being able to meet these objectives: Discuss the components and methods used to connect an enterprise network to an ISP. Explain the advantages of using BGP to connect an enterprise network to an ISP, while comparing the functions and uses of EBGP and IBGP. Compare and contrast the requirements for establishing EBGP-to-IBGP neighbor relationships. Implement BGP operations for ISP connections in an enterprise network. Discuss the lab results for configuring BGP operations. Configure and verify BGP operations in a multihomed environment using the BGP attributes and route maps to control all BGP routes to and from the router. .Discuss the lab results for manipulating the EBGP path selections. Discuss the e-learning modules that pertain to additional topics in IPv6 and remote access connectivity.
6-2
Lesson 1
Planning the Enterprise-to-ISP Connection

Overview
Planning needs to be completed before the connection of an enterprise network to an Internet service provider (ISP) can be implemented. To plan the connectivity to an ISP properly, the designer must understand many aspects, including the session origination pointeither from the enterprise network toward the Internet or from the Internet toward the enterprise network; the prerequisites for successfully implementing such connectivity; and the available routing options and which routing option should be used in certain cases. The connectivity redundancy considerations must also be taken into account.
Objectives
Upon completing this lesson, you will be able to justify the components and methods used to connect an enterprise network to an ISP. This ability includes being able to meet these objectives: Connecting enterprise networks to an ISP. Exchanging routing updates with an ISP. Define the types of connections to an ISP.
Connecting Enterprise Networks to an ISP

This topic describes the connectivity requirements between an enterprise network and an ISP.
Session Origin Initiation

Enterprise session initiation requirement:
One-way: Connectivity from an enterprise network toward the Internet is the only connectivity required. Two-way: Connectivity from the Internet to an enterprise network is also required.
Solutions:
One-way: private IP address space with address translation Two-way: public IP address space (in combination with private) and proper routing
ROUTE v1.06-2
Modern corporate IP networks are connected to the global Internet and make use of the Internet for some of their data transport needs. Corporations provide many services via the Internet to customers and business partnerssystems from web servers to mainframes to workstations can be accessible from anywhere in the world. In the rare cases in which only connectivity from the clients to the Internet is required, public addresses with network translation are used to allow clients on a private network to communicate with servers on the public Internet. Typically, not only do clients from an enterprise network need to access external resources located on the public Internet, but clients external to the enterprise network also need to access resources in the enterprise network.
6-4
Enterprise Network-to-ISP Connectivity Requirements

Public IP address space (subpool or whole /24 subnet) Link type and bandwidth availability Routing options Connection redundancy Independency in regard to an ISP: Public IP address space AS number
ROUTE v1.06-3
The first parameter that needs to be determined is the number of public IP addresses, which are used to translate client private addresses for those clients that need to access resources on the Internet. These public IP addresses are also used for those enterprise servers that need to be accessible from the Internet. These servers are either equipped with public addresses or addresses that are statically translated from private to public addresses. In the second parameter, the enterprise network-to-ISP connection link type and speed, which depends on the ISP, needs to be determined. The link types available include leased line, Ethernet over fiber optics or copper, and xDSL. The bandwidth assignment must be done properly to address the enterprise Internet connectivity requirements. In the third parameter, a proper routing protocol must be selected. The selection is typically made between static and dynamic routing. The fourth parameter deals with connectivity redundancy. An evaluation is needed to determine what kind of redundancy is required for the enterprise network-to-ISP connectivity. Redundancy includes edge router redundancy, link redundancy, and ISP redundancy, where the ISP redundancy connects to multiple ISPs. When assessing these parameters, it must be taken into account whether an enterprise network needs to be independent of the selected ISP(s). If independency is required, the public IP address space should not be used from the ISP public address space, but should instead be acquired from the regional Internet authority. Similarly, independency is required for an autonomous system (AS). The AS number must be public and not from the private AS number pool that can be assigned by the ISP.
Connecting an Enterprise Network to an ISP Network
6-5
Exchanging Routing Updates with an ISP

This topic describes the methods for exchanging routing information across an ISP.
Reachability
Circuit emulation Static routes MPLS VPNs BGP
Static routes and BGP are typically selected for Internet connectivity.
Previous ly covered Not c overed yet
ROUTE v1.06-4
Connecting an enterprise network to an ISP requires routing information to be exchanged between the network and the ISP. The selection of the routing means depends on the answers to these questions: Should this routing respond to the changes in a network topology? Does routing need to support one link or multiple links to an ISP? Is traffic load balancing over multiple links required? Will the enterprise network be connected to multiple ISPs? Should the ISP offer merely a transport capability that requires connecting different customer locations, perhaps via certain Layer 2 technologies? What is the amount of routing information that needs to be exchanged with an ISP? What routing options does the ISP offer?
6-6
Using Circuit Emulation

Used to provide different Layer 2 connectivity to customers via the common Layer 3 infrastructure of a service point Ethernet, Frame Relay, PPP, HDLC, ATM, Layer 2 connectivity No routing with the service point from the customer perspective
ROUTE v1.06-5
Sometimes a customer needs Layer 2 connectivity between two or more locations. The following examples illustrate the need for Layer 2 connectivity: The locations might include data centers with geographically distributed clusters that require Layer 2 connectivity in order to properly function. The customer is in a migration process but still requires Layer 2 connectivity. The customer is connecting to another partner and there is a requirement for Layer 2 connectivity. A Layer 2 connection requirement might range from Ethernet, Frame Relay, PPP, High-Level Data Link Control (HDLC), or even ATM. In such cases, modern service providers employ their IP-based core network enhanced with Multiprotocol Label Switching (MPLS) technologies to provide such connectivity. With this connectivity, there is no need for a routing exchange between the ISP and the customer. From the customer, it looks like the ISP is providing a Layer 2 port. From the perspective of the ISP, two ports from distant locations must be connected together.
6-7
Using Static Routes

The customer uses the default route toward the ISP. The service provider uses static route(s) for customer public networks. No automatic adjustment to any changes in the network.
ROUTE v1.06-6
Static routes are the simplest way of exchanging routing information with an ISP. These static routes must agree with the ISP upon routing configuration and they do not change afterward; or if they do change, these changes should not occur very often. Static routes are typically used for Internet connectivity when a customer is connected through a single connection to an ISP. The customer can use the default route towards the ISP and the ISP must deploy a static route or routes that encompass the public networks of the customer. The ISP would typically also redistribute this information into its Border Gateway Protocol (BGP). Although static routes are a simple solution, they also have some drawbacks, especially in terms of flexibility and adaptability. For example, if there were a change in a network topology beyond a directly connected link failure, the static routes would not adapt. If adaptation needs to be achieved, either the static routes need to be combined with an IP service level agreement (SLA) functionality that in turn would indicate that a static route is down if a certain condition is met or dynamic routing is used. Note that using an IP SLA cannot completely substitute dynamic routing because it cannot react to all changes in the topology in the Internet.
6-8
Using MPLS VPN

Used to connect multiple customer locations via a service providers common Layer 3 infrastructure A special VPN can be used to provide Internet connectivity Routing used can be static or dynamic depending on the SP The customer routers are connected to the service provider PE routers
ROUTE v1.06-7
Multiprotocol Label Switching Virtual Private Networks (MPLS VPNs) are used when a customer has multiple locations that need to be interconnected through an ISP and does not want to use expensive Layer 2 technologies such as leased lines. With MPLS VPNs, the ISP uses a common IP-based core network enhanced with MPLS technology to provide secure and manageable connectivity for different customers to their geographically disperse sites. In this way, the traffic from different customers can share the same physical wire, but at the same time, traffic is tagged with the labels in such way that the traffic cannot intermix. When a customer uses MPLS VPN functionality, the routing between the customer and the Internet service provider is required in order to provide connectivity between the customer locations. Routing options range from static to dynamic and include Routing Information Protocol (RIP), Enhanced Interior Gateway Routing Protocol (EIGRP), Open Shortest Path First (OSPF), Intermediate System-to-Intermediate System (IS-IS), or even BGP, depending on what the ISP offers. Different locations could use different routing protocols, though this situation typically would not occur. With an MPLS VPN deployment, the service provider can also offer Internet connectivity through the same MPLS core network either through a special Internet VPN or through a global routing table. To exchange the Internet routing information, either Boarder Gateway Protocol (BGP) or a default routing is used.
6-9
Using BGP
The customer deploys BGP to announce its public networks The ISP announces a default route, a subset of Internet routes, or a complete Internet routing table Typically used for inter-AS routing
CPECustomer to Provider Edge router
ROUTE v1.06-8
A typical option used to provide dynamic routing exchange when Internet connectivity is deployed is BGP. BGP dynamically exchanges routing information and thus reacts to topology changes including those changes beyond a customer-to-ISP link failure. From the routing perspective, three options can be used: An ISP (or multiple ISPs) announces a default route only. If two ISPs are used, one ISP will be primary and the second ISP will serve as the backup. An ISP (or multiple ISPs) announces a default route and a subset of Internet routes, typically its own public address space. This results in the shortest path being used to the directly connected public networks. For public networks that are not directly connected, one of the ISPs is the primary one and the second ISP is the backup. An ISP (or multiple ISPs) announces a complete Internet routing table. The shortest path to any destination will be chosen according to the routing table.
6-10
Defining the Types of Connections to an ISP

This topic describes the types of enterprise-to-ISP connections and their effect on the selection of an exchange method.
Enterprise Network-to-ISP Connection Options

Single-homed Dual-homed Multihomed Dual-multihomed
ROUTE v1.06-9
When connecting an enterprise network to an ISP, redundancy is a big concern. The following different aspects can be addressed in order to achieve connectivity redundancy: Deployment of redundant links Deployment of redundant equipment Use of redundancy within a single router From the connection perspective, a customer can be connected to a single ISP or to multiple ISPs. With a single ISP connection, redundancy can still be achieved if two links toward the same ISP are used effectively, making a customer dual-homed. When no link redundancy is used, the customer is simply single-homed and in case of a failure within an ISP network, the connectivity to the Internet is interrupted. With multiple ISP connections, the redundancy is built into the design because the customer is multihomed and thus resistant to a single ISP failure. To enhance the resiliency further, a customer can have two links toward a single ISP making the solution dual-multihomed.
6-11
Single-homed ISP Connectivity

Link failure results in broken connectivity. Option 1: Routing with static routes
A default route from an enterprise network A static route(s) from an ISP for customer networks
Option 2: Routing with BGP

The customer announces its public network(s) The ISP announces the default route to the customer
ROUTE v 1.06-10
Single-homed ISP connectivity is used in cases when a loss in Internet connectivity is not as vital or problematic to a customer (though these days the Internet typically is a vital resource). In this case, a customer uses a single connection to a single ISP. The type of connection depends on the ISP offering and can include a leased line, xDSL, or an Ethernet connection. Failure of a link results in a no Internet connectivity. Such Internet access to a single ISP does not require BGP. Static routes are typically used to handle the routing. If BGP is used, the customer uses it to dynamically announce its public networks to an ISP and the ISP announces only a default route to the customer, because that is sufficient to provide the connectivity through a single link to the Internet.
6-12
Dual-homed ISP Connectivity

Characteristics:
Connected with two links to the same ISP Can use a single router or two edge routers Can use static routes or BGP
ROUTE v 1.06-11
When a customer is connected to a single ISP only, resiliency can still be achieved by deploying a second link to the same ISP. With a second link being used, the routing must be properly configured to allow usage of such a link. Depending on the SLA signed with the ISP, the routing deployed could achieve these benefits: Primary and backup link functionality where a single primary link is used to forward and receive traffic to and from the ISP, and the secondary link is used only when the first link fails. Load sharing between the links is achieved with Cisco Express Forwarding switching. In both cases, the routing used can be based on either static or dynamic routes, which would typically include BGP. To enhance the resiliency further, the two links can terminate at separate customer routers.
6-13
Multihomed ISP Connectivity

Characteristics:
Connected to two or more different ISPs Can use a single router or multiple edge routers Dynamic routing with BGP
ROUTE v 1.06-12
A proper resiliency is achieved by connecting to two or more different ISPs. The benefits of connecting to two or more different ISPs are the following: Resistance to a failure beyond a directly connected link to a single ISP. Sharing the load for different destination networks between ISPs based on the network proximity. Scaling the solution beyond two ISPs. Achieving a solution independent of an ISP. An ISP change requires an update of routing configuration and change of a link. The public IP address space used remains the same. Connections from different ISPs can terminate on the same router or different routers to further enhance the resiliency. The routing must be capable of reacting to dynamic changes, and BGP is typically used to achieve this flexibility.
6-14
Dual-multihomed ISP Connectivity

Characteristics:
Connected to two or more different ISPs with two links per ISP Typically uses multiple edge routers (one per ISP) Dynamic routing with BGP
ROUTE v 1.06-13
Multihoming exists when an autonomous system has more than one connection to the Internet. Two typical reasons for multihoming are as follows: To increase the reliability of the connection to the Internet If one connection fails, the other connection remains available.
To increase the performance of the connection Better paths can be used to certain destinations.
The benefits of BGP are apparent when an autonomous system has multiple External Border Gateway Protocol (EBGP) connections to either a single autonomous system or multiple autonomous systems. Having multiple connections allows an organization to have redundant connections to the Internet so that if a single path becomes unavailable, connectivity can still be maintained.
6-15
Summary
Summary
Connecting an enterprise network to an ISP requires, at a minimum, a public IP address pool, a proper link to the ISP, consideration of redundancy requirements, and the proper routing protocol. To exchange routing updates with an ISP, the customer can use different options. Static routes and BGP are the options that are most commonly used. The way in which the customer connects to an ISP depends on the redundancy requirements, where a single-homed connectivity has no redundancy, and the dual-multihomed connectivity has the most redundancy built in.
ROUTE v 1.06-14
6-16
Lesson 2
Considering the Advantages of Using BGP

Overview
Border Gateway Protocol (BGP) is an exterior gateway protocol (EGP) and this lesson describes how BGP may be used by enterprises to connect to Internet service providers (ISPs). BGP routes between autonomous systems using path vector attributes upon which routing policy decisions at the autonomous system level are enforced.
Objectives
Upon completing this lesson, you will be able to explain the advantages of using BGP to connect an enterprise network to an ISP, while comparing the functions and uses of EBGP and IBGP. This ability includes being able to meet these objectives: Use BGP to connect to an ISP. Describe BGP multihoming options. Configure BGP routing between autonomous systems. Explain path vector functionality. Identify features of BGP.
Using BGP to Connect to an ISP

This topic describes connectivity between an enterprise network and an ISP that requires the use of BGP, including a description of the issues that arise when an enterprise decides to connect to the Internet through multiple ISPs.
BGP Terminology
Autonomous system (AS): a collection of networks under a single administrative domain Interdomain routing: routing between the customer and the ISP Internal routing: uses IGP protocol (RIP, OSPF, EIGRP, and so on) to exchange routing information inside the AS External routing: uses EGP protocol (BGP) to exchange routes between autonomous systems Two BGP implementations: Internal BGP (IBGP): when BGP is used inside an AS External BGP (EBGP): when BGP is used between autonomous systems
ROUTE v1. 06-2
The Internet is a collection of autonomous systems that are interconnected to allow communication among these autonomous systems. BGP provides the routing between these autonomous systems. Enterprises that want to connect to the Internet do so through one or more ISPs. If your organization has only one connection to one ISP, then you probably do not need to use BGP; instead, you would use a default route. However, if you have multiple connections to one or multiple ISPs, then BGP might be appropriate because it allows manipulation of path attributes, so that the optimal path can be selected. To understand BGP, it is necessary to first understand how it is different from the other protocols discussed so far in this course. One way to categorize routing protocols is by whether the protocols are interior or exterior, as follows: IGP: Interior gateway protocol (IGP) is a routing protocol that exchanges routing information within an autonomous system. Routing Information Protocol (RIP), Open Shortest Path First (OSPF), and Enhanced Interior Gateway Routing Protocol (EIGRP) are examples of IGPs. EGP: Exterior gateway protocol (EGP) is a routing protocol that exchanges routing information between different autonomous systems. BGP is an example of an EGP.
6-18
BGP is an Interdomain Routing Protocol (IDRP), also known as an EGP. BGP version 4 (BGP4) is the latest version of BGP and is defined in RFC 4271. As noted in this RFC, the classic definition of an autonomous system is a set of routers under a single technical administration, using an IGP and common metrics to route packets within the autonomous system, and using an inter-autonomous system routing protocol (also called an EGP) to determine how to route packets to other autonomous systems. Autonomous systems can use more than one IGP, potentially with several sets of metrics. From the point of view of BGP, the most important characteristic of an autonomous system is that it appears to other autonomous systems to have a single coherent interior routing plan and presents a consistent picture of reachable destinations. All parts of an autonomous system must connect to each other. When BGP is running between routers in different autonomous systems, it is called External BGP (EBGP). When BGP is running between routers in the same autonomous system, it is called Internal BGP (IBGP). BGP allows the path that packets take to be manipulated by the autonomous system, as described in this module. It is important to understand how BGP works to avoid creating problems for the autonomous system as a result of running BGP.
6-19
BGP Multihoming Options

This topic describes BGP multihoming options.
Multihoming Options
Multihoming options with respect to connections
Us ing a single connection to an individual ISP Us ing multiple connec tions to an individual ISP
Multihoming options with respect to routing

Default routes from all providers Default routes and partial Internet routing from the providers Full Internet routing from the providers
20 09 Cis co Sy ste ms , I nc. All r igh ts re ser ve d.
RO UT E v1. 0 6- 3
An organization can be multihomed to either a single ISP or to multiple ISPs. A drawback to having all connections homed to a single ISP is that connectivity issues in that single ISP can cause your autonomous system to lose connectivity to the Internet. By having connections to multiple ISPs, an organization gains the following benefits: A redundancy with the multiple connections Not tied into the routing policy of a single ISP More paths to the same networks for better policy manipulation A multihomed autonomous system will run EBGP with its external neighbors and might also run IBGP internally. If an organization has determined that it will perform multihoming with BGP, there are three common ways to do this: Each ISP passes only a default route to the autonomous system. The default route is passed to the internal routers. Each ISP passes only a default route and provider-owned specific routes to the autonomous system. These routes may be passed to internal routers or all internal routers in the transit path can run BGP and pass these routes between them. All internal routers in the transit path run BGP and pass these routes between them.
Each ISP passes all routes to the autonomous system.
These options are described in the following pages.
6-20
Default Routes from Providers

Customer A receives the default route from each ISP.
ROUTE v1. 06-4
The first multihoming option is to receive only a default route from each ISP. This configuration requires the fewest resources within the autonomous system because a default route is used to reach any external destinations. The autonomous system sends all its routes to the ISPs, which process and pass the routes on to other autonomous systems. If a router in the autonomous system learns about multiple default routes, the local interior routing protocol installs the best default route in the routing table. From the perspective of this router, it chooses the default route with the least-cost IGP metric. This IGP default route will route packets destined to the external networks to an edge router of this autonomous system, which is running EBGP with the ISPs. The edge router will use the BGP default route to reach all external networks. The route that inbound packets take to reach the autonomous system is chosen outside the autonomous system (within the ISPs and other autonomous systems). Regional ISPs that have multiple connections to national or international ISPs commonly implement this option. The regional ISPs do not use BGP for path manipulation; however, ISPs require the capability of adding new customers as well as the networks of the customers. If the regional ISP does not use BGP, then each time that the regional ISP adds a new set of networks, the customers must wait until the national ISPs add these networks to their BGP process and place static routes pointing at the regional ISP. By running EBGP with the national or international ISPs, the regional ISP needs to add only the new networks of the customers to its BGP process. These new networks automatically propagate across the Internet with minimal delay. A customer that chooses to receive default routes from all providers must understand the following limitations of this option: Path manipulation cannot be performed because only a single route is being received from each ISP.
6-21
Bandwidth manipulation is extremely difficult and can be accomplished only by manipulating the IGP metric of the default route. Diverting some of the traffic from one exit point to another is challenging because all destinations are using the same default route for path selection.
Default Routes from Providers (cont.)

One of the ISPs is used for sending traffic out of the customer network. Can result in the suboptimal routing of packets.
ROUTE v1. 06-5
In the above figure, AS 65020 and AS 65030 send default routes into AS 65010the Customer A network. Because of the IGP metric in the Customer A network and because of the configuration of routers R1 and R2, the provider edge (PE)1 router from ISP 1 is selected as the default gateway in order to reach any external network outside of the Customer A autonomous system. This procedure can lead to suboptimal routing. For example, if the goal is to reach network 172.17.0.0, the packets will be sent toward ISP 1 to router PE1 because the PE1 router is the preferred way out of the Customer A autonomous system. ISP 1 then forwards the traffic to the final destination to ISP 2.
6-22
Default Routes and Partial Table from Providers

Customer A receives the default route from each ISP. Customer A receives a partial routing table from each ISP.
ROUTE v1. 06-6
In the second design option for multihoming, all ISPs pass default routes plus the selected specific routes to the autonomous system. An enterprise running EBGP with an ISP that wants a partial routing table generally receives the networks that the ISP and its other customers own. The enterprise can also receive the routes from any other autonomous system. Major ISPs are assigned between 2000 and 10,000 classless interdomain routing (CIDR) blocks of IP addresses from the Internet Assigned Numbers Authority (IANA), which the ISPs reassign to their customers. If the ISP passes this information to a customer that wants only a partial BGP routing table, the customer can redistribute these routes into its IGP. The internal routers of the customer (these routers are not running BGP) can then receive these routes via redistribution. The routers can take the nearest exit point based upon the best metric of specific networks instead of taking the nearest exit point based on the default route. Acquiring a partial BGP table from each provider is beneficial because path selection will be more predictable than when using a default route.
6-23
Default Routes and Partial Table from Providers (cont.)

The partial table is used to forward traffic to the correct ISP. If the destination is unknown, then a default route to one of the ISPs is used.
ROUTE v1. 06-7
In the figure above, ISPs in AS 65020 and AS 65030 send default routes and the routes that each ISP owns (partial table) to Customer A (AS 65010). By running IBGP between the internal routers R1 and R2 within AS 65010, AS 65010 can choose the optimal path to reach the destination networks within ISP 1 and ISP 2. If Customer A is sending the traffic to an unknown destination, one of the default routes (from ISP 1 or ISP 2) is used. Again, this process can lead to suboptimal routing as shown in the figure above. The unknown routes to another autonomous system are not shown in the figure because these routes are not specifically advertised to AS 65010 by ISP 1 and ISP 2. The IGP metric that is used to reach the default route within the autonomous system selects the default gateway out of the Customer A network.
6-24
Full Internet Routing from Providers

Customer A receives a full routing table from each ISP. Requires that enough memory and CPU resources are available.
ROUTE v1. 06-8
In the third multihoming option, all ISPs pass all routes to the autonomous system, and IBGP is run on at least the routers in the transit path in this autonomous system. This option allows the internal routers of the autonomous system to take the path through the best ISP for each route. This configuration requires many resources within the autonomous system because it must process all the external routes. The autonomous system sends all its routes to the ISPs, which process the routes and pass the routes to other autonomous systems. In the above figure, AS 65020 and AS 65030 send all routes into AS 65010. The ISP that a specific router within AS 65010 uses to reach the external networks is determined by the BGP protocol. The routers in AS 65010 can be configured to influence the path to certain networks. For example, router R1 and router R2 can influence the outbound traffic from AS 65010.
6-25
BGP Routing Between Autonomous Systems

This topic describes how BGP routes between autonomous systems.
Autonomous System
Autonomous system (AS) a collection of networks under a single technical administration. 16-bit numbers (as of January 2009 32-bit numbers are available) Ranging from 1 to 65535 Private AS: 6451265535 Internet Assigned Numbers Authority (IANA) allocates AS numbers. IGPs operate within an AS. BGP is used between autonomous systems.
ROUTE v1. 06-9
Recall that an autonomous system is a collection of networks under a single technical administration. IGPs operate within an autonomous system, and BGP (specifically BGP4) is used between autonomous systems on the Internet. IANA is the organization responsible for allocating autonomous system numbers. Specifically, the American Registry for Internet Numbers (ARIN) has the jurisdiction to assign numbers for the Americas, the Caribbean, and Africa. Rseaux IP Europennes Network Information Center (RIPENIC) administers autonomous system numbers for Europe, and the Asia Pacific Network Information Center (APNIC) administers the numbers for the Asia Pacific region. Autonomous system numbers are 16-bit numbers ranging from 1 to 65535. RFC 1930 provides guidelines for the use of autonomous system numbers. A range of autonomous system numbers, 64512 through 65535, is reserved for private use, much like private IP addresses. The autonomous system numbers used in this course are all in the private range to avoid publishing autonomous system numbers belonging to organizations.
Note Using an IANA-assigned autonomous system number rather than a private autonomous system number is necessary only if your organization plans to use an EGP such as BGP and connect to a public network such as the Internet.
6-26
BGP Routing Between Autonomous Systems

BGP is used to provide an interdomain routing system. BGP guarantees the exchange of loop-free routing information. BGP works differently than IGPs. BGP is a policy-based routing protocol. Control traffic flow using multiple BGP path attributes.
RO UTE v 1.06-10
The main goal of BGP is to provide an interdomain routing system that guarantees loop-free exchange of routing information between autonomous systems. Routers exchange information about paths to destination networks. BGP is a successor of EGP, which was developed to isolate networks from each other as the Internet grew. There are many RFCs relating to BGP4, which is the current version of BGP. These RFCs include 1772, 1773, 1774, 1930, 1966, 1997, 1998, 2042, 2385, 2439, 2545, 2547, 2796, 2858, 2918, 3065, 3107, 3392, 4223, and 4271. BGP4 has many enhancements over earlier protocols. The Internet uses BGP4 extensively to connect ISPs and to connect enterprises to ISPs. BGP4 and its extensions are the only acceptable versions of BGP available for use on the public-based Internet. BGP4 carries a network mask for each advertised network and supports both variable-length subnet masking (VLSM) and classless interdomain routing (CIDR). BGP4 predecessors did not support these capabilities, which are currently mandatory on the Internet. When using CIDR on a core router for a major ISP, the IP routing table, which is composed mostly of BGP routes, has more than 175,000 CIDR blocks. Not using CIDR at the Internet level would cause the IP routing table to have more than 2,000,000 entries. Using BGP4 and CIDR prevents the Internet routing table from becoming too large to interconnect millions of users.
6-27
Comparison with IGPs

BGP works differently than IGPs. An internal routing protocol looks for the quickest path from one point in a corporate network to another based upon certain metrics. RIP uses hop counts that attempt to cross the least number of Layer 3 devices to reach the destination network. OSPF and EIGRP look for the best speed available according to the bandwidth statement on the interface. All internal routing protocols consider the path cost to get somewhere. In contrast, BGP, an external routing protocol, does not consider speed to determine the best path. Instead, BGP is a policy-based routing protocol that allows an autonomous system to control traffic flow using multiple BGP path attributes. BGP allows a provider to use all its bandwidth by manipulating these path attributes.
6-28
Path Vector Functionality

This topic describes how BGP uses path vector functionality.
Path Vector Functionality

BGP announces: Paths Networks that are reachable at the end of the path The path is described by using attributes. The administrator can define data flow through autonomous systems.
RO UTE v 1.06-11
Internal routing protocols announce a list of networks and the metrics to get to each network. In contrast, BGP routers exchange network reachability information, called path vectors, made up of path attributes (similar to metrics). The path vector information includes a list of the full path of BGP autonomous system numbers (hop by hop) necessary to reach a destination network and the networks that are reachable at the end of the path. Other attributes include the IP address to get to the next autonomous system (the next-hop attribute) and an indication of how the networks at the end of the path were introduced into BGP (the origin code attribute). This autonomous system path information is useful to construct a graph of loop-free autonomous systems and is used to identify routing policies so that restrictions on routing behavior can be enforced based on the autonomous system path. The autonomous system path is always loop-free. A router running BGP does not accept a routing update that already includes the router autonomous system number in the path list because the update has already passed through its autonomous system, and accepting it again would result in a routing loop. An administrator can define policies or rules about how data will flow through the autonomous systems.
6-29
BGP Routing Policies

BGP can support any policy conforming to the hop-by-hop (AS-by-AS) routing paradigm.
RO UTE v 1.06-12
BGP allows routing policy decisions at the autonomous system level to be enforced. These policies can be implemented for all networks owned by an autonomous system, for a certain CIDR block of network numbers (prefixes), or for individual networks or subnetworks. BGP specifies that a BGP router can advertise to neighboring autonomous systems only those routes that it uses itself. This rule reflects the hop-by-hop routing paradigm that the Internet generally uses. The hop-by-hop routing paradigm does not support all possible policies. For example, BGP does not enable one autonomous system to send traffic to a neighboring autonomous system, intending that the traffic take a different route from that taken by traffic that originates in that neighboring autonomous system. In other words, how a neighboring autonomous system routes traffic cannot be influenced, but how traffic gets to a neighboring autonomous system can be influenced. However, BGP supports any policy that conforms to the hop-by-hop routing paradigm. Because the Internet currently uses the hop-by-hop routing paradigm only, and because BGP can support any policy that conforms to that paradigm, BGP is highly applicable as an interautonomous system routing protocol.
6-30
Example: BGP Routing Policies

For example, in the figure above, the following paths are possible for AS 65010 to reach networks in AS 65060 through AS 65020: 65020 65030 65060 65020 65050 65060 65020 65030 65050 65070 65060 65020 65050 65030 65060 65020 65050 65070 65060 AS 65010 does not see all these possibilities. AS 65020 advertises to AS 65010 only its best path of 65020 65030 65060, the same way that IGPs announce only their best least-cost routes. This path is the only path through AS 65020 that AS 65010 sees. All packets that are destined for 65060 through 65020 will take this path. Even though other paths exist, AS 65010 can only use what AS 65020 advertises for the networks in AS 65060. The autonomous system path that is advertised, 65020 65030 65060, is the autonomous system-by-autonomous system (hop-by-hop) path that AS 65020 will use to reach the networks in AS 65060. AS 65020 will not announce another path, such as 65020 65050 65030 65060, because it did not choose that as the best path based on the BGP routing policy in AS 65020. AS 65010 will not learn about the second-best path or any other paths from AS 65020 unless the best path of AS 65020 becomes unavailable. Even if AS 65010 were aware of another path through AS 65020 and wanted to use it, AS 65020 would not route packets along that other path because AS 65020 selected 65020 65030 65060 as its best path and all AS 65020 routers will use that path as a matter of BGP policy. BGP does not let one autonomous system send traffic to a neighboring autonomous system, intending that the traffic take a different route from that taken by traffic originating in the neighboring autonomous system. To reach the networks in AS 65060, AS 65010 can choose to use AS 65020 or it can choose to go through the path that AS 65040 is advertising. AS 65010 selects the best path to take based on its own BGP routing policies.
6-31
Features of BGP
This topic describes the features of BGP in terms of deployment, enhancements over other distance vector routing protocols, and database types.
Features of BGP
BGP is a path vector protocol with the following properties:
Reliable updates: BGP runs on top of TCP (port 179) Incremental, triggered updates only Periodic keepalive messages to verify TCP connectivity Rich metrics (called path vectors or attributes) Designed to scale to huge internetworks (for example, the Internet)
It has enhancements over distance vector protocols.
RO UTE v 1.06-13
BGP is categorized as an advanced distance vector protocol, but it is actually a path vector protocol. BGP is very different from standard distance vector protocols like RIP. BGP uses TCP as its transport protocol, which provides reliable connection-oriented delivery. BGP assumes that its communication is reliable; therefore, it does not have to implement retransmission or error recovery mechanisms. BGP uses TCP port 179. Two routers using BGP form a TCP connection with one another and exchange messages to open and confirm the connection parameters. These two BGP routers are called peer routers, or neighbors. After the connection is made, BGP peers exchange full routing tables. However, because the connection is reliable, BGP peers subsequently send only changes (incremental, or triggered, updates) after that. Reliable links do not require periodic routing updates; therefore, routers use triggered updates instead. BGP sends keepalive messages, similar to the hello messages sent by OSPF, IS-IS, and EIGRP. BGP is the only IP routing protocol to use TCP as its transport layer. OSPF, IGRP, and EIGRP reside directly above the IP layer, and RIP version 1 (RIPv1) and RIP version 2 (RIPv2) use User Datagram Protocol (UDP) for their transport layer.
6-32
OSPF and EIGRP have their own internal function to ensure that update packets are explicitly acknowledged. These protocols use a one-for-one window so that if either OSPF or EIGRP has multiple packets to send, the next packet cannot be sent until OSPF or EIGRP receive an acknowledgment from the first update packet. This process can be very inefficient and cause latency issues if thousands of update packets must be exchanged over relatively slow serial links. OSPF and EIGRP rarely have thousands of update packets to send. EIGRP can hold more than 100 networks in one EIGRP update packet, so 100 EIGRP update packets can hold up to 10,000 networks, and most organizations do not have 10,000 subnets in their corporations. BGP, on the other hand, has more than 175,000 networks (and growing) on the Internet to advertise, and it uses TCP to handle the acknowledgment function. TCP uses a dynamic window, which allows 65,576 bytes to be outstanding before it stops and waits for an acknowledgment. For example, if 1000-byte packets are being sent, there would need to be 65 packets that have not been acknowledged for BGP to stop and wait for an acknowledgment when using the maximum window size. TCP is designed to use a sliding window, where the receiver will acknowledge at the halfway point of the sending window. This method allows any TCP application, such as BGP, to continue to stream packets without having to stop and wait, as would be required with OSPF or EIGRP.
6-33
When to Use BGP

BGP should be used if one of the following is true: An AS is a transit AS An AS is multihomed Inter-AS routing policy must be manipulated BGP should not be used if one of the following is true: Single-homed AS Insufficient memory and processor resources to handle BGP routing Insufficient understanding of route filtering and BGP path selection process
RO UTE v 1.06-14
BGP allows ISPs to communicate and exchange packets. These ISPs have multiple connections to each other and agreements to exchange updates. BGP is used to implement the agreements between two or more autonomous systems. Improper controlling and filtering of BGP updates can potentially allow an outside autonomous system to affect the traffic flow to your autonomous system. It is important to know how BGP operates and how to configure it properly to prevent this situation. For example, if a customer is connected to ISP A and ISP B (for redundancy), the goal is to implement a routing policy to ensure that ISP A does not send traffic to ISP B via the autonomous system of the customer. The customer does not want to waste valuable resources and bandwidth within its autonomous system to route traffic for its ISPs, but will want to be able to receive traffic destined to its autonomous system through each ISP. BGP should be used in the following cases: If an AS is a transit AS, where packets transit the AS to reach other autonomous systems If an AS is multihomed with multiple connections to other autonomous systems If inter-AS routing policy must be manipulated, where path selection for traffic entering and leaving the AS must be influenced
6-34
BGP is not always an appropriate solution to interconnect autonomous systems. There are several cases where BGP should not be used: When the network is single-homed AS with a single connection to the Internet or other AS. An AS with one exit path uses the default route as the most appropriate solution. BGP would unnecessarily use router CPU resources and memory. When there are insufficient memory and processor resources in the network edge router to handle BGP routing. When there is insufficient understanding of route filtering and the BGP path selection process. If the routing policy implemented in an autonomous system is consistent with the policy in the ISP autonomous system, it is not necessary or desirable to configure BGP in that autonomous system.
6-35
BGP Databases
BGP neighbor table List of BGP neighbors BGP table List of all networks learned from each BGP neighbor Multiple paths to same destination network can be present Each path is associated with BGP attributes IP routing table (forwarding database) List of best paths to destination networks used to forward traffic
RO UTE v 1.06-15
A router running BGP keeps its own tables to store BGP information that it receives from and sends to other routers, including a neighbor table, a BGP table (also called a forwarding database or topology database), and an IP routing table. For BGP to establish an adjacency, it must be explicitly configured for each neighbor. BGP forms a TCP relationship with each of the configured neighbors and keeps track of the state of these relationships by periodically sending a BGP/TCP keepalive message.
Note The BGP sends BGP/TCP keepalives by default every 60 seconds.
After establishing an adjacency, the neighbors exchange the BGP routes that are in their IP routing table. Each router collects these routes from each neighbor that successfully establishes an adjacency and then places the routes in its BGP forwarding database. All routes that have been learned from each neighbor are placed into the BGP forwarding database. The best routes for each network are selected from the BGP forwarding database using the BGP route selection process and are then offered to the IP routing table. Each router compares the offered BGP routes to any other possible paths to those networks, and the best route, based on administrative distance, is installed in the IP routing table. EBGP routes (BGP routes learned from an external autonomous system) have an administrative distance of 20. IBGP routes (BGP routes learned from within the autonomous system) have an administrative distance of 200.
6-36
BGP Message Types

BGP defines the following message types:
Open, which includes hold time and BGP router ID Keepalive Update Information for one path only (could be to multiple networks) Includes path attributes and networks Notification When an error is detected BGP connection closed after message is sent
RO UTE v 1.06-16
The four BGP message types are open, keepalive, update, and notification. After a TCP connection is established, the first message sent by each side is an open message. If the open message is acceptable, the side that receives the message sends a keepalive message confirming the open message. After the receiving side confirms the open message and establishes the BGP connection, the BGP peers can exchange any update, keepalive, and notification messages. BGP peers initially exchange their full BGP routing tables. Incremental updates are sent only after topology changes in the network occur. BGP peers send keepalive messages to ensure that the connection between the BGP peers still exists, and send notification packets in response to errors or special conditions. Here are more details about the different types of BGP messages: Open message: An open message includes the following information: Version number: The suggested version number. The highest common version that both routers support is used. Most BGP implementations today use BGP4. AS number: The AS number of the local router. The peer router verifies this information. If it is not the AS number that is expected, the BGP session is ended. Hold time: Maximum number of seconds that can elapse between the successive keepalive and update messages from the sender. On receipt of an open message, the router calculates the value of the hold timer by using whichever is smaller: its configured hold time or the hold time that was received in the open message. BGP router ID: This 32-bit field indicates the BGP ID of the sender. The BGP ID is an IP address that is assigned to that router, and it is determined at startup. The BGP router ID is chosen in the same way that the OSPF router ID is chosenit is the highest active IP address on the router unless a loopback interface with an IP address exists. In this case, the router ID is the highest loopback IP address. The router ID can also be statically configured.
Connecting an Enterprise Network to an ISP Network 6-37
Optional parameters: These parameters are type, length, and value (TLV) encoded. An example of an optional parameter is session authentication.
Keepalive message: BGP keepalive messages are exchanged between BGP peers often enough to keep the hold timer from expiring. If the negotiated hold-time interval is 0, then periodic keepalive messages are not sent. A keepalive message consists of only a message header. Update message: A BGP update message has information on one path only; multiple paths require multiple update messages. All the attributes in the update message refer to that path, and the networks are those that can be reached through that path. An update message can include the following fields: Withdrawn routes: This list displays IP address prefixes for routes that are withdrawn from service, if any. Path attributes: These attributes include the AS path, origin, local preference, and so on (as described later in this module). Each path attribute includes the attribute TLV. The attribute type consists of the attribute flags, followed by the attribute type code. Network-layer reachability information: This field contains a list of IP address prefixes that are reachable by this path.
Notification message: A BGP notification message is sent when an error condition is detected; the BGP connection is closed immediately after this is sent. Notification messages include an error code, an error subcode, and data that are related to the error.
6-38
Summary
Summary
BGP is typically used for interdomain routing. Three common ways to perform multihoming with BGP are as follows: Each ISP passes only a default route. Each ISP passes only a default route and specific providerowned routes. Each ISP passes all routes. BGP is the external routing protocol used between autonomous systems. Forwarding is based on policies and not on best path. BGP routers exchange network reachability information called path vectors, made up of path attributes. A router running BGP keeps its own tables to store BGP information that it receives from and sends to other routers, including a neighbor table, a BGP table, and an IP routing table.
6-39
6-40
Lesson 3
Comparing the Functions and Uses of EBGP and IBGP

Overview
This lesson explains important terminology that is used in establishing Border Gateway Protocol (BGP) peering relationships. This lesson describes and defines External BGP (EBGP) and Internal BGP (IBGP) neighbors as well as the requirements for establishing peering relationships. In addition, this lesson examines the difference between an interior gateway protocol (IGP) and BGP and explains the reason for having all routers in the transit path within an autonomous system (AS) running IBGP. Understanding the relationship between various types of BGP routers and the common terminology that is used when you are discussing these routers is necessary for troubleshooting connectivity issues between BGP neighbors. The following terms are explained: BGP speaker, BGP router, BGP neighbor, and BGP peer.
Objectives
Upon completing this lesson, you will be able to compare and contrast the requirements for establishing EBGP-to-IBGP neighbor relationships. This ability includes being able to meet these objectives: Define BGP neighbor relationships. Establish External BGP neighbor relationships. Establish Internal BGP neighbor relationships.
BGP Neighbor Relationships

This topic describes terms used for BGP routers and their relationships.
BGP Neighbors
A BGP neighbor is also known as a BGP peer TCP connection
ROUTE v1. 06-2
No one router can handle communications with all the routers that run BGP. There are tens of thousands of routers that run BGP and these routers are connected to the Internet, representing more than 21,000 autonomous systems (ASs). A BGP router forms a direct neighbor relationship with a limited number of other BGP routers. Through these BGP neighbors, a BGP router learns of the paths that are available through the Internet to reach any advertised network. Any router that runs BGP is known as a BGP speaker. The term BGP peer has a specific meaningit is a BGP speaker that is configured to form a neighbor relationship with another BGP speaker for the purpose of directly exchanging BGP routing information with each other. A BGP speaker has a limited number of BGP neighbors with which it peers and forms a TCP-based relationship. BGP peers are also known as BGP neighbors and can be either internal or external to the AS. Internal BGP peer or IBGP peer typically forms the neighbor relationship inside the ISP network. External BGP peer or EBGP peer forms the neighbor relationship between the enterprise network and the ISP. External neighbors, as well as internal neighbors, require a TCP connection to be established. The processing of the BGP routes and its attributes is typically different, as is the connection type. External neighbors are directly connected. A network assigned to the link between neighbors, as well as the next-hop IP address, must be reachable for routing purposes.
6-42
Establishing External BGP Neighbor Relationships

This topic describes the requirements for establishing an External BGP (EBGP) neighbor relationship.
External BGP Neighbors

A BGP neighbor in a different AS
ROUTE v1. 06-3
Recall that when BGP is running between routers in different autonomous systems, it is called EBGP. By default, routers running EBGP are directly connected to each other. An EBGP neighbor is a router outside a home AS. An enterprise network can have a connection to one or several ISPs, and the ISPs themselves might be connected to several other ISPs as well. For each such connection between different autonomous systems, there is an EBGP session required between EBGP neighboring routers. EBGP neighbors are directly connected and they establish a TCP session prior exchanging BGP updates. When multiple different autonomous systems are connected to each other and an enterprise network is connected to multiple ISPs, BGP runs between the ISPs and the enterprise network. In the figure above, the Customer A network is connected to two ISPs and an EBGP session is established between routers R3 and R5 as well as between routers R4 and R6. Routers establish neighbor relationships and exchange BGP routing updates with one another. In the figure above, Customer A routers learn the paths to the external autonomous systems from their respective EBGP neighbors.
6-43
Requirements for EBGP

Different AS number Defined neighbors Reachability
ROUTE v1. 06-4
There are several different requirements for establishing an EBGP neighbor relationship: Different AS number: EBGP neighbors must reside in different autonomous systems to be able to form an EBGP relationship. Defined neighbors: A TCP session must be established prior to starting BGP routing update exchanges. Reachability: EBGP neighbors must be directly connected and IP addresses on that link must be reachable inside each AS. IGP is the routing protocol that runs inside an AS. An IGP is not run between the EBGP neighbors residing in different autonomous systems. For two routers to exchange BGP routing updates, the TCP-reliable transport layer on each side must successfully pass the TCP threeway handshake before a BGP session can be established. Therefore, the IP address used in the BGP neighbor command must be reachable without using an IGP, which can be accomplished by pointing at an address that is reachable through a directly connected network or by using static routes to that IP address. Generally, the neighbor address that is used is the address on a network that is directly connected.
6-44
Establishing Internal BGP Neighbor Relationships

This topic describes the requirements for establishing an Internal BGP (IBGP) neighbor relationship.
Internal BGP Neighbors

A BGP neighbor in same AS Requirements: Same AS number Defined neighbors Reachability
ROUTE v1. 06-5
Recall that BGP that runs between routers within the same AS is called IBGP. IBGP runs within an AS to exchange BGP information so that all BGP speakers have the same BGP routing information about outside autonomous systems. When multiple routers in an AS are running BGP, they exchange BGP routing updates with one another. In the figure above, routers R3 and R4 learn the paths to the external autonomous systems from their respective EBGP neighbors (R5 and R6). If the link between R3 and R4 goes down, R3 must learn new routes to the external autonomous systems. Other BGP routers within AS 65010 that were using R3 to get to external networks must also be informed that the path through R3 is not available. Those BGP routers within AS 65010 need to have the alternate paths through router R4 in their BGP forwarding database. IBGP is typically established between the customer-edge (CE) routers inside the enterprise network autonomous system as well as between the routers inside each ISP. There are several different requirements for establishing an IBGP neighbor relationship: Same AS number: IBGP neighbors must reside in the same AS to be able to form an IBGP relationship. Defined neighbors: A TCP session must be established between neighbors prior to exchanging BGP routing updates. Reachability: IBGP neighbors must be reachable, thus IGP typically runs inside an AS.
6-45
Summary
Summary
Every BGP router establishes a neighbor relationship with other BGP neighbors. An External BGP (EBGP) neighbor relationship is established between the routers in different autonomous systems (AS). An Internal BGP (IBGP) neighbor relationship is established between routers in the same AS.
ROUTE v1. 06-6
6-46
Lesson 4
Configuring and Verifying Basic BGP Operations

Overview
This lesson presents the commands and configuration examples to configure Border Gateway Protocol (BGP) properly. After a successful configuration, BGP will be able to establish a neighbor relationship, set the next-hop address, set the source IP address of a BGP update, and announce networks to other BGP routers. A router running BGP goes through several neighbor states through which BGP progresses to establish a BGP session, and offers hints for troubleshooting BGP because the session can be stuck in the stuck-in-active (SIA) or idle state. External BGP (EBGP) and Internal BGP (IBGP) configuration is explained, as well as authentication between neighbors. This lesson also shows how to use the show and debug commands for troubleshooting BGP, providing a baseline for troubleshooting. A thorough understanding of this material is necessary to use BGP.
Objectives
Upon completing this lesson, you will be able to implement BGP operations for ISP connections in an enterprise network. This ability includes being able to meet these objectives: Identify specifications for implementing BGP. Establish internal and external BGP neighbor relationships. Determine how to shut down a BGP neighbor. Understand BGP configuration considerations. Identify BGP neighbor states. Implement authentication in BGP. Create an example of activating basic BGP. Configure BGP verification.
Specifications for Implementing BGP

This topic describes the types of information contained in a typical implementation plan.
Planning for BGP

Define network requirements Define internal connectivity Define external connectivity to ISP Gather required parameters
ROUTE v1.06-2
Prior to BGP configuration, a network administrator must define the network requirements including the internal connectivity for IBGP design and configuration, as well as the external connectivity to the ISP for EBGP design and configuration. The next step is to gather all of the parameters needed to provide enough details for a network operator to start the BGP configuration.
6-48
Requirements for Basic BGP Configuration

AS numbers Neighbors (IP addresses) Networks to be advertised
ROUTE v1.06-3
The requirements to configure basic BGP include the following details: Autonomous system (AS) numbers (your own and all remote AS numbers) All of the neighbors (peers) involved in BGP and IP addressing used among the BGP neighbors Networks that need to be advertised into BGP A typical BGP configuration involves configuring BGP between a customer network and an ISP. This process is called External BGP (EBGP). Many times Internal BGP (IBGP) is required, as well as all the collected details for a complete configuration.
6-49
Establishing Internal and External BGP Neighbors

This topic describes the process of activating a BGP session for external and internal neighboring routers.
Steps to Configure Basic EBGP

Define the BGP process Establish a EBGP neighbor relationship Advertise the networks
ROUTE v1.06-4
Basic EBGP configuration requires three main steps: 1. Define the BGP process. 2. Establish the neighbor relationship. 3. Advertise the networks into BGP. In order to perform the steps above, information is needed about the neighbors, which AS numbers are used, which IP address is used as the IP address on a remote router (neighbor), and which network will be advertised.
6-50
Define BGP Process and Activate EBGP Session
Define the BGP process locally with a local AS number.
Activate EBGP session to the neighbor

Remote router IP Address and AS number
2009 Cis co S y st em s, Inc. A ll right s reserved. ROUTE v1.06-5
The syntax of the basic BGP configuration commands is similar to the syntax for configuring internal routing protocols. However, there are significant differences in how BGP functions. Use the router bgp 65010 command to notify the router that any subsequent subcommands belong to this routing process. This command also identifies the local autonomous system (AS) in which this router belongs. AS 65010 is used as an example. The router needs to be informed of the AS number so it can determine whether the BGP neighbors to be configured next are IBGP or EBGP neighbors. The command enters router configuration mode. The route bgp command alone cannot activate BGP on a router. At least one subcommand must be entered under the router bgp command to activate the BGP process on the router. If the router is placed in AS 65010 and an attempt is then made to configure with a new router bgp 65020 command, the router indicates that it is currently configured for AS 65010. To establish a connection to another AS, insert the AS number with a neighbor command in addition to the router bgp command so that the router can properly identify the relationship between the neighboring router and itself.
Note Only one instance of BGP can be configured on the router at a single time.
Use the neighbor 10.1.1.2 remote-as 65020 command to activate an EBGP session for a neighboring router. This command identifies a peer router with which the local router will establish a session and is mandatory for the establishment of each neighboring router relationship.
6-51
The address that is used in this command is the destination address for all BGP packets going to the neighboring router. For BGP to pass BGP routing information, this address must be reachable because BGP attempts to establish a TCP session and exchange BGP updates with the device at this IP address. An EBGP session is typically established between directly connected neighbors. The AS number that is a part of this command is used to identify whether this neighbor is an EBGP neighbor or an IBGP neighbor. If the AS number is the same as the AS number for this router, that neighbor is an IBGP neighbor and the IP address listed in this neighbor command does not have to be directly connected. If the AS number is different from the AS number for this router, this neighbor is an EBGP neighbor and the address in this neighbor command must be directly connected by default. In the figure above, the AS is different and an EBGP neighbor relationship is established. For more details about the neighbor remote-as and router bgp commands, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-52
Advertise Networks
Option 1:
Configure the local networks to be advertised and include them in BGP
Option 2:
Redistribution from IGP to BGP
ROUTE v1.06-6
Two options exist when advertising networks into the BGP. The first option is using the network command to define the networks required. The second option is the redistribution of IGP routes into the BGP routing process. Redistribution was described in a separate module. The command is explained in the following pages. Use the network 10.2.2.0 mask 255.255.255.0 command to permit BGP to advertise the 10.2.2.0 if it is present in the IP routing table. The network command determines networks that the router originates. This concept is different from using the network command when configuring IGP. Unlike with IGP, the network command does not start BGP on specific interfaces; rather, it indicates to BGP which networks it should originate from this router. The mask parameter indicates that BGP version 4 (BGP4) can handle subnetting and supernetting. The list of network commands must include all networks in the AS that are to be advertised, not just those that are locally connected to the router. Prior to Cisco IOS Software Release 12.0, there was a limit of 200 network commands per BGP router. This limit has been removed. The resources of the router, such as the configured NVRAM or RAM, determine the maximum number of network commands that can be used. The sole purpose of the network command is to notify BGP of the networks that are to be advertised. Without the mask option, this command announces only the classful network number. At least one subnet of the specified major network must be present in the IP routing table to allow BGP to start announcing the classful network as a BGP route. However, if a network mask option is specified, an exact match to the network (both address and mask) must exist in the routing table. Before BGP announces a route, it checks to see whether it can reach it.
6-53
For more details about the network command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-54
BGP network Command Details
The router looks for 192.168.1.1/24 in the routing table, but cannot find it, so it will not announce anything.
The router looks for 192.168.0.0/16 in the routing table. If the exact route is not in the table, you can add a static route to null0 so that the route can be announced.
The router looks for a C class 192.168.1.0 network in the routing table.
ROUTE v1.06-7
For example, if the command network 192.168.1.1 mask 255.255.255.0 is misconfigured, BGP looks for exactly 192.168.1.1/24 in the routing table. It may find 192.168.1.0/24 or 192.168.1.1/32; however, it never finds 192.168.1.1/24. Because the routing table does not contain a specific match to the network, BGP does not announce the 198.168.1.1/24 network to any neighbors. As another example, if network 192.168.0.0 mask 255.255.0.0 is specified to advertise a classless interdomain routing (CIDR) block, BGP looks for 192.168.0.0/16 in the routing table. It may find 192.168.1.0/24 or 192.168.1.1/32; however, if it never finds 192.168.0.0/16, BGP does not announce the 192.168.0.0/16 network to any neighbors. In this case, the following static route can be configured toward the null interface so that BGP can find an exact match in the routing table: ip route 198.1.0.0 255.255.0.0 null0 After finding an exact match in the routing table, BGP announces the 192.168.0.0/16 network to any neighbors. If the network 192.168.1.0 command is specified without the mask keyword, BGP looks for C class 192.168.1.0/24 in the routing table.
Note The BGP auto-summary router configuration command determines how BGP handles redistributed routes. With BGP summarization enabled (with auto-summary), all redistributed subnets are summarized to their classful boundaries in the BGP table. When disabled (with no auto-summary), all redistributed subnets are present in their original form in the BGP table, so only those subnets would be advertised. In Cisco IOS Software Release 12.2(8)T, the default behavior of the auto-summary command was changed to disabled (no auto-summary); prior to that the default was enabled (auto-summary).
6-55
Basic EBGP Configuration
Option 1

Option 2

ROUTE v1.06-8
In option 1, router R2 is configured for EBGP configuration. The local AS number 65010 is used to enter BGP configuration mode. When defining the EBGP, the neighbor remote-as statement defines the relationship to the local AS number. The remote AS is different from the local AS because the neighbor is declared as an EBGP neighbor. Router R2 will establish a TCP session and start exchanging BGP updates. Router R2 is configured to advertise two local networks to its neighbor. The exact network entries (10.2.2.0/24 and 10.4.4.0/24) must exist inside the routing table in order to accept and advertise networks inside the BGP process. In option 2, router R2 is configured for EBGP configuration, but its configuration to advertise the networks is different. The Open Shortest Path First (OSPF) protocol is used as an IGP on router R2, and networks 10.2.2.0 and 10.4.4.0 are advertised in OSPF. In order to advertise the networks into BGP, redistribution from OSPF to BGP is configured.
6-56
Basic IBGP and EBGP Configuration in the Customer A Network
ROUTE v1.06-9
Customer-edge routers (CE-routers) are connected to provider edge (PE) routers. EBGP is configured between CE and PE routers because enterprise networks and ISPs have different AS numbers. If enterprise networks are dual-homed or multihomed, then typically two CE-routers are configured for EBGP. In order to provide reliable connectivity to one or more ISPs, CErouters must exchange BGP routes as well. An IBGP session must be configured between two CE-routers. The figure above shows typical BGP configuration of CE-router R2. The EBGP neighbor relationship to router R5 and IBGP neighbor relationship to router R6 is configured. An IBGP session is established to the neighbor with the same AS number as its local AS number (AS 65010). An EBGP neighbor relationship is established with the neighbor with a different AS number (AS 65020) and local AS number (AS 65010). Network commands are used to advertise two networks. Because network 172.16.0.0 is not directly connected, a static route to the Null0 interface is configured in order to advertise network 172.16.0.0 into BGP.
6-57
Shutting Down a BGP Neighbor

This topic describes the process of administratively shutting down and reenabling a BGP neighbor.
Shutting Down a BGP Neighbor
Administratively brings down a BGP neighbor Used for maintenance/policy changes to prevent route flapping
Reenables a BGP neighbor that has been administratively shut down

2009 Cis co S y st em s, Inc. A ll right s reserved. ROUTE v 1.06-10
Use the neighbor 10.1.1.2 shutdown commands to administratively shut down and reenable a BGP neighbor. If major policy changes are implemented for a neighboring router and multiple parameters are changed, the neighboring router must be administratively shut down, the changes must be implemented, and then the neighboring router must be brought back up with the no neighbor 10.1.1.2 shutdown command. Using the neighbor 10.1.1.2 shutdown command not only terminates the session but removes all associated routing information as well. For more details about the neighbor shutdown command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-58
BGP Configuration Considerations

This topic describes what needs to be considered to correctly configure BGP.
IBGP Peering Issue

An IBGP neighbor relationship is established. What happens if the link between R3 and R4 goes down? Which IP address should be used to establish an IBGP session?
ROUTE v 1.06-11
To establish an IBGP session between routers R3 and R4, as shown in the figure above, which neighbor IP address should be used? The problem is as follows: If router R3 uses the neighbor 10.7.7.2 remote-as 65010 command, but router R4 is sending the BGP packets to router R3 via routers R2 and R1, the source IP address will be different. When router R4 receives this BGP packet via routers R2 and R1, it will not recognize this BGP packet because a different IP address was not configured as a neighbor of router R4; therefore, the IBGP session between router R3 and router R4 cannot be established. A solution to this problem is to establish the IBGP session using a loopback interface when there are multiple paths between the IBGP neighbors.
6-59
BGP Issues with Source IP Address

Create a BGP packet:
The destination IP address defined by the neighbor statement The source IP address defined by the outbound interface
The source address of the received BGP packet is compared to list of neighbor statements:
If a match is found in the list of neighbors, a relationship is established. If no match is found in the list of neighbors, the packet is ignored.
ROUTE v 1.06-12
The BGP neighbor statement informs the router of the destination IP address for each update packet. The router must decide which IP address to use as the source IP address in the BGP routing update. When a router creates a BGP packet for a neighbor, it checks the routing table for the destination network to reach that neighbor. The IP address of the outbound interface, as the routing table indicates, is used as the source IP address of the BGP packet. When a BGP packet is received for a new BGP session, the source address of the packet is compared to the list of neighbor statements. This source IP address must match the address in the corresponding neighbor statement on the other router. Otherwise, the routers will not be BGP peers because they are not able to establish the BGP session.
6-60
IBGP Using Loopback Addresses

A loopback interface can be used as the source and destination IP address of all BGP updates between neighbors. The neighbor update-source command is normally used only with IBGP neighbors.
ROUTE v 1.06-13
Multiple paths can exist to reach each neighbor when peering with IBGP neighboring routers. If the BGP router is using a neighbor address that is assigned to a specific interface on another router, and that interface goes down, the router pointing to this address loses its BGP session with that neighbor. If the router peers instead with the loopback interface of the other router, the loopback interface will always be available as long as the router itself does not fail. This peering arrangement adds resiliency to the IBGP sessions because the routers are not tied into a physical interface, which may go down for any number of reasons. To peer with the loopback of another internal neighbor, the first router would point the neighbor statement at the loopback address of the other internal neighbor. Ensure that both routers have a route to the loopback address of the other neighbor in their routing table. Also ensure that both routers are announcing their loopback addresses into their local routing protocol. The update-source option in the neighbor command overrides the default source IP address used for BGP packets. It is necessary to tell the router which IP address to use as the source address for all BGP packets if a loopback interface is to be used instead of the physical interface. If the update-source option is not used in the neighbor command, an announcement packet going to a neighbor uses the IP address of the exiting interface as the source address for a packet. When a router creates a packet, whether it is a routing update, a ping, or any other type of IP packet, the router does a lookup in the routing table for the destination address. The routing table lists the appropriate interface to get to the destination address. The address of this outbound interface is used as the source address of that packet by default.
6-61
Consider what would happen if a neighboring router uses the loopback interface address in its neighbor command for this router, but the neighbor update-source command is not used on this router. When the neighboring router receives an update packet and looks at the source address of the packet, it sees that it has no neighbor relationship with that source address, so it discards the packet. BGP does not accept unsolicited updates; it must be aware of every neighboring router and have a neighbor statement for it. In the figure above, router R2 has router R1 as an EBGP neighbor and router R3 as an IBGP neighbor. Routers R1 and R2 are directly connected. Router R3 is not directly connected to router R2, and in the figure above, Enhanced Interior Gateway Routing Protocol (EIGRP) is used in order to provide reachability between R2 and R3. Because the neighbor relationship between routers R2 and R3 is not tied to a physical interface, router R2 peers with the loopback interface on router R3 and uses its loopback address as the source IP address, and vice versa. If router R2 instead peered with 10.1.1.2 on router R3 and that interface went down, the BGP neighbor relationship would also go down. The neighbor update-source command should be used on both routers. If router R2 points to loopback address 3.3.3.3 of router R3, and router R3 points at loopback address 2.2.2.2 of router R2, and neither use the neighbor update-source command, the BGP session between these routers will not start. For more details about neighbor update-source command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-62
IBGP Next-Hop Behavior

IBGP does not modify next hop.
ROUTE v 1.06-14
The way in which BGP establishes an IBGP relationship is very different from the way that IGPs behave. BGP is an AS-by-AS routing protocol and not a router-by-router routing protocol. Next hop is the IP address used to reach the next AS. The method that BGP uses to denote its next-hop address is also very different from the way that an IGP performs the same function. The default next hop is as follows: EBGP: IP address of the neighbor router sending the update IBGP: IP address advertised by EBGP should be carried in IBGP In the figure above, the next hop for route 11.0.0.0/8 is always the IP address 10.1.1.2 advertised by the EBGP neighbor. In case a failure occurs on the link between router R3 and R4, and router R4 has no information regarding how to reach the address 10.1.1.2, it will not be able to forward packets toward destination network 11.0.0.0/8. This situation occurs even if the physical path exists (through routers R1 and R2 in the figure above).
6-63
BGP neighbor next-hop-self Command
Forces all updates for neighbor R4 to be advertised with this router as the next hopthe same IP address as for the source of the BGP packet.
It is sometimes necessary to override the default next-hop behavior of a router and force it to advertise itself as the next-hop address for routes sent to a neighboring router. The neighbor next-hop-self command forces BGP to use its own IP address as the next-hop address for each network that it advertises to its IBGP neighbor, rather than letting the protocol choose the next-hop address to use. An internal protocol, such as Routing Information Protocol (RIP), EIGRP, or Open Shortest Path First Protocol (OSPF), always uses the source IP address of a routing update as the nexthop address for each network that is placed in the routing table. The neighbor next-hop-self command forces BGP use the source IP address of the update as the next-hop address for each advertised network. Routers R3 and R4 are IBGP neighbors and router R3 will advertise all the updates toward router R4 with the next hop being the source IP address of the BGP packet going from router R3 to R4. The figure above shows that the next-hop address for the destination network 11.0.0.0 is now loopback interface 0 of router R3. It is reachable via routers R1 and R2 because all the routers in AS 65010 are running the IGP routing protocol providing reachability in the local autonomous system. Static routes can be used as well, but IGP is a more scalable solution. For more details about neighbor next-hop-self command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-64
Identifying BGP Neighbor States

This topic describes BGP neighbor states.
BGP States
When establishing a BGP session, BGP goes through the following states:
1. Idle: Router is searching the routing table to see whether a route exists to reach the neighbor. 2. Connect: Router found a route to the neighbor and has completed the three-way TCP handshake. 3. Open sent: Open message sent, with the parameters for the BGP session. 4. Open confirm: Router received an agreement on the parameters for establishing a session. Alternatively, the router goes into active state if no response to open message 5. Established: Peering is established; routing begins.
ROUTE v 1.06-16
After the TCP handshake is complete, the BGP application tries to set up a session with the neighbor. A number of steps must occur for the session to be established. After the neighbor command is entered in BGP, BGP takes the IP address that is listed and checks the local routing table for a route to this address. At this point, BGP is in the idle state. If BGP does not find a route to the IP address, it stays in the idle state. If it finds a route, it goes to the connect state when the TCP handshaking synchronization-acknowledgment (SYN ACK) packet returns. After the TCP connection is complete, BGP creates a BGP open packet and sends it to the neighbor. Once BGP sends this open packet, the BGP peering session changes to the open sent state. If there is no response for 5 seconds, the state changes to the active state. If a response does come back in a timely manner, BGP goes to the open confirm state and starts scanning (evaluating) the routing table for the paths to send to the neighbor. When those paths have been found, BGP then goes to the established state and begins routing between the neighbors.
Note The states that two BGP routers are going through to establish a session can be observed using debug commands. In Cisco IOS Software Release 12.4, the debug ip bgp ipv4 unicast command can be used to see this process. In earlier Cisco IOS Software releases, the debug ip bgp events command gave similar output. Debugging uses up router resources and should be turned on only when necessary.
6-65
BGP Established and Idle States

Idle: The router cannot find the address of the neighbor in the routing table. Solution: Check for an IGP problem. Is the neighbor announcing the route? Established: Proper state for BGP operations. Output of the show ip bgp summary command has a number in the state column indicating the number of routes learned from this neighbor.
ROUTE v 1.06-17
The idle state is an indication that the router does not know how to reach the IP address that is listed in the neighbor statement. The router is idle because of one of the following scenarios: It is waiting for a static route to that IP address or network to be configured. It is waiting for the local routing protocol (IGP) to learn about this network through an advertisement from another router. The most common reason for a router to enter the idle state is that the neighbor is not announcing the IP address or the network toward which the neighbor statement of the router is pointing. Check these two conditions first to correct this problem: 1. Ensure that the neighbor announces the route in its local routing protocol (IGP). 2. Verify that an incorrect IP address has not been entered in the neighbor statement. The established state is the desired state for the neighbor relationship. This state means that both routers have agreed to exchange BGP updates with one another and routing has begun.
6-66
Example: show ip bgp neighbors Command
ROUTE v 1.06-18
Use the show ip bgp neighbors command to display information about the BGP connections to neighbors. In the figure above, the BGP state is established, which means that the neighbors have established a TCP connection and the two peers have agreed to use BGP to communicate. For more details about show ip bgp neighbors command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-67
BGP Active State Verification

Active: The router has sent an open packet and is waiting for a response.
The state may cycle between active and idle. The neighbor may not know how to get back to this router because of the following reasons: No route to the source IP address of the BGP open packet The neighbor is peering with the wrong address No neighbor statement for this router The AS number is misconfigured
ROUTE v 1.06-19
If the router is in the active state, it has found the IP address in the neighbor statement and has created and sent out a BGP open packet. However, the router has not received a response (open confirm packet). One common problem in this case is that the neighbor may not have a return route to the source IP address. Ensure that the source IP address or network of the packets has been announced to the local routing protocol (IGP). Another common problem associated with the active state occurs when a BGP router attempts to peer with another BGP router that does not have a neighbor statement peering back to the first router, or when the other router is peering with the wrong IP address on the first router. Check to ensure that the other router has a neighbor statement peering to the correct address of the router that is in the active state. If the state toggles between the idle state and the active state, one of the most common problems is AS number misconfiguration.
6-68
Example: BGP Active State Verification

AS number misconfiguration:
At the router with the wrong remote AS number:

At the remote router:

ROUTE v 1.06-20
Example: BGP Active State Verification

If the AS number has been misconfigured, the following console message will be seen at the router with the wrong remote AS number configured in the neighbor statement:

At the remote router, the following message will be displayed:

6-69
Example: BGP Peering
ROUTE v 1.06-21
Example: BGP Peering

The show ip bgp summary command is one way to verify the neighbor relationship. The figure above presents the output from this command. Some of the details of this command output are as follows: BGP router ID: The IP address that all other BGP speakers recognize as representing this router. BGP table version: The version increases in increments when the BGP table changes. Main routing table version: The last version of the BGP database that was injected into the main routing table. Neighbor: The IP address that is used in the neighbor statement with which this router has a relationship. Version (V): The version of BGP that this router is running with the listed neighbor. AS: The AS number of the listed neighbor. Messages received (MsgRcvd): The number of BGP messages that have been received from this neighbor. Messages sent (MsgSent): The number of BGP messages sent to this neighbor. Table version (TblVer): The BGP table version. In queue (InQ): The number of messages waiting to be processed from this neighbor. Out queue (OutQ): The number of messages queued and waiting to be sent to this neighbor. TCP flow control prevents this router from overwhelming a neighbor with a large update.
6-70
Up/Down: The length of time that this neighbor has been in the current BGP state (established, active, or idle). State (established, active, idle, open sent, open confirm, or idle [admin]): The BGP state. A neighbor can be set to administratively shut down (admin state) by using the neighbor shutdown router configuration command. Prefix received (PfxRcd): When the session is in the established state, this value represents the number of BGP network entries received from the listed neighbor. For more details about show ip bgp summary command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-71
BGP Authentication
This topic describes the configuration of Message Digest 5 (MD5) authentication on the BGP TCP connection between two routers.
BGP Neighbor Authentication
BGP authentication uses MD5 Configure a keypassword; router generates a message digest (is sent), or hash, of the key (is not sent) and the message Router generates and checks the MD5 digest of every segment sent on the TCP connection Router authenticates the source of each routing update packet that it receives
BGP neighbor authentication can be configured on a router so that the router authenticates the source of each routing update packet that it receives. This authentication is accomplished by the exchange of an authenticating key (sometimes referred to as a password) that is known to both the sending and the receiving router. BGP supports MD5 neighbor authentication. MD5 sends a message digest (also called a hash) that is created using the key and a message. The message digest is then sent instead of the key. The key itself is not sent to prevent it from being read by an eavesdropper on the line while it is being transmitted. To enable MD5 authentication on a TCP connection between two BGP peers, use the neighbor {ip-address | peer-group-name} password string router configuration command. MD5 authentication can be configured between two BGP peers, which means that each segment sent on the TCP connection between the peers is verified. MD5 authentication must be configured with the same password on both BGP peers; otherwise, the connection between the peers will not be made. Configuring MD5 authentication causes Cisco IOS Software to generate and check the MD5 digest of every segment sent on the TCP connection.
Note If the authentication string is configured incorrectly, the BGP peering session will not be established. It is recommended that the authentication string be entered carefully and verify that the peering session is established after authentication is configured.
6-72
If a BGP peer group is specified by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command. If a router has a password configured for a neighbor, but the neighbor router does not, a message such as the following will appear on the console when the routers attempt to send BGP messages between themselves: Similarly, if the two routers have different passwords configured, a message such as the following will appear on the screen: If the password or key used for MD5 authentication between two BGP peers is configured or changed, the local router will not tear down the existing session after the password is configured. The local router will attempt to maintain the peering session using the new password until the BGP hold-down timer expires. The default time period is 180 seconds. If the password is not entered or changed on the remote router before the hold-down timer expires, the session times out.
Note Configuring a new timer value for the hold-down timer will only take effect after the session has been reset. It is not possible to change the configuration of the hold-down timer to avoid resetting the BGP session.
For more details about neighbor {ip-address | peer-group-name} password string command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-73
Example: BGP Neighbor Authentication
ROUTE v 1.06-23
The example in the figure above configures MD5 authentication for the BGP peering session between routers R1 and R2. The same password must be configured on the remote peer before the hold-down timer expires.
6-74
Example of Activating Basic BGP

This topic describes the configuration of BGP operations in a single-homed environment.
Example: BGP Configuration
ROUTE v 1.06-24
The figure above shows another BGP example, which will take into account several BGP features and conclude the topic of configuring basic BGP configuration steps. Router R1 has one EBGP neighbor, router R2 has one EBGP and one IBGP neighbor, and router R3 has one IBGP neighbor. Showing the configuration of routers R1 and R2 will explain the basic configuration needed to create an EBGP and IBGP neighbor relationship. The configuration for router R1 is as follows: The first command under the router bgp 65020 command establishes that router R1 has the following BGP neighbor: Router R2 in AS 65010 From the perspective of router R1, router R2 is an EBGP neighbor. The neighbor statement on router R1 for router R2 is pointing at the directly connected IP address to reach the EBGP neighbor, router R2. Authentication is enabled toward router R2 to authenticate the source of routing updates for the EBGP neighbor using password wYC1swUget. The network command notifies BGP about which network to advertise. It contains a subnet of a class B address using the mask option. The configuration for router R2 is as follows: The first two commands under the router bgp 65010 command establish that router R2 has the following two BGP neighbors: Router R1 in AS 65020 Router R3 in AS 65010
2009 Cisco Systems, Inc. Connecting an Enterprise Network to an ISP Network 6-75
From the perspective of router R2, router R1 is an EBGP neighbor and router R3 is an IBGP neighbor. The neighbor statement on router R2 for router R1 is pointing at the directly connected IP address to reach the EBGP neighbor, router R1. However, the neighbor statement on router R2 points to the loopback interface of router R3 because router R2 has multiple paths to reach router R3. If router R2 pointed at the 192.168.3.2 IP address of router R3 and that interface went down, router R2 would be unable to reestablish the BGP session until the link came back up. By pointing to the loopback interface of router R3 instead, the link stays established as long as any path to router R3 is available. Router R3 should also point to the loopback address of router R2 in its configuration. Authentication is enabled toward router R1 to authenticate the source of routing updates for the EBGP neighbor using the correct password. The neighbor 192.168.2.2 update-source Loopback 0 command notifies router R2 to always use its loopback 0 address, 192.168.2.1, as the source IP address when sending an update to router R3 (192.168.2.2). Router R2 also changes the next-hop address for networks that are reachable through it. The default next-hop setting for networks from AS 65020 is IP address 10.1.1.2. With the next-hop-self command, router R2 sets the next-hop address to the source IP address of the routing update, which is the router R2 loopback 0 interface, as set by the update-source command. Three network commands notify BGP about which networks to advertise. The first is a subnet of a class B address using the mask option. The next two network statements are used for the two class C networks that connect router R2 and router R3. The default mask is 255.255.255.0, so it does not need to be included in the command.
6-76
BGP Verification
This topic describes the verification of BGP configuration.
Example: show ip bgp Command
ROUTE v 1.06-25
Use the show ip bgp command to display the BGP topology database (BGP table). The figure above is a partial sample output of the show ip bgp command. The status codes are shown at the beginning of each line of output, and the origin codes are shown at the end of each line. In this output, there is an asterisk (*) in most of the entries in the first column. This means that the next-hop address (in the fifth column) is valid. The next-hop address is not always the router that is directly connected to this router. Other options for the first column are as follows: An s, for suppressed, indicates that the specified routes are suppressed (usually because routes have been summarized and only the summary route is being sent). A d, for dampening, indicates that the route is being dampened (penalized) for going up and down too often. Although the route might be up right now, it is not advertised until the penalty has expired. An h, for history, indicates that the route is unavailable and is probably down; historic information about the route exists, but a best route does not exist. An r, for Routing Information Base (RIB) failure, indicates that the route was not installed in the RIB. The reason that the route is not installed can be displayed using the show ip bgp rib-failure command, as shown in the next figure. An S, for stale, indicates that the route is stale (this symbol is used in the nonstop forwarding-aware router). The second column shows > when BGP has selected the path as the best path to a network. The third column is either blank or shows i. If it is blank, BGP learned that route from an external peer. An i indicates that an IBGP neighbor advertised this path to the router.
2009 Cisco Systems, Inc. Connecting an Enterprise Network to an ISP Network 6-77
The fourth column lists the networks that the router learned. The Next Hop column lists all the next-hop addresses for each route. This column may contain the entry 0.0.0.0, which signifies that this router is the originator of the route. The three columns to the left of the Path column list three BGP path attributes that are associated with the path: metric (multi-exit discriminator [MED]), local preference, and weight. The column with the Path header may contain a sequence of autonomous systems in the path. From left to right, the first AS listed is the adjacent AS, from which this network was learned. The last number (the rightmost AS number) is the originating AS of this network. The AS numbers between these two numbers represent the exact path that a packet takes back to the originating AS. If the path column is blank, the route is from the current AS. The last column signifies how this route was entered into BGP on the original router. If the last column has an i in it, the originating router probably used a network statement to introduce this network into BGP. If the character is an e, the originating router learned this network from exterior gateway protocol (EGP), which is the historical predecessor to BGP. A question mark (?) signifies that BGP cannot absolutely verify the availability of this network because it is redistributed from an IGP into BGP.
6-78
Example: show ip bgp rib-failure Command

Displays networks that are not installed in the RIB and the reason that they were not installed.
ROUTE v 1.06-26
Use the show ip bgp rib-failure command to display BGP routes that were not installed in the Routing Information Base (RIB) table and the reason that the routes were not installed. The example in the figure above shows that the displayed routes were not installed because a route or routes with a better administrative distance already exist in the RIB. For more details about show ip bgp rib-failure command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-79
Clearing the BGP Session

When policies change, the change takes effect immediately. The next time that a prefix or path is advertised or received, the new policy is used. This can take a long time for all networks. You must trigger an update for immediate action. Ways to trigger an update: Hard reset Soft reset Route refresh
ROUTE v 1.06-27
BGP can potentially handle huge volumes of routing information. When a policy configuration change occurs, the router cannot go through the huge table of BGP information and recalculate which entry is no longer valid in the local table; nor can the router determine which route or routes, already advertised, should be withdrawn from a neighbor. There is an obvious risk that the first configuration change will be immediately followed by a second, which would cause the whole process to start all over again. To avoid such a problem, Cisco IOS Software applies changes only to those updates that are received or transmitted after the BGP policy configuration change has been performed. The new policy, enforced by the new filters, is applied only on routes that are received or sent after the change. A network administrator who would like the policy change to be applied on all routes must trigger an update to force the router to let all routes pass through the new filter. If the filter is applied on outgoing information, the router has to resend the BGP table through the new filter. If the filter is applied on incoming information, the router needs its neighbor to resend its BGP table so that it passes through the new filters. There are three ways to trigger an update: with a hard reset, soft reset, or route refresh.
6-80
Hard Reset of BGP Sessions

A BGP session makes the transition from established to idle; everything must be relearned.
Resets all BGP connections with this router. The entire BGP forwarding table is discarded.
Resets only a single neighbor. Less severe than a clear ip bgp * command.
ROUTE v 1.06-28
Resetting a session is a method of informing the neighbor or neighbors of a policy change. If BGP sessions are reset, all information received on those sessions is invalidated and removed from the BGP table. Also, the remote neighbor will detect a BGP session down state and will invalidate the routes that were received. After 30 to 60 seconds, the BGP sessions are reestablished automatically and the BGP table is exchanged again, but through the new filters. However, resetting the BGP session disrupts packet forwarding. Both commands that are shown in the figure above cause a hard reset of the BGP neighbors that are involved. A hard reset means that the router issuing either of these commands will close the appropriate TCP connections, reestablish those TCP sessions as appropriate, and resend all information to each of the neighbors affected by the particular command that is used. The clear ip bgp * command causes the BGP forwarding table on the router that issued this command to be completely deleted, and all networks must be relearned from every neighbor. If a router has multiple neighbors, this action is a very dramatic event. This command forces all neighbors to resend their entire tables simultaneously. For example, consider a situation in which router R1 has eight neighbors and each neighbor has a full Internet table of about 32 MB in size. If router R1 issues the clear ip bgp * command, all eight routers resend their 32-MB tables at the same time. To hold all these updates, router R1 would need 256 MB of RAM. Router R1 would also need to be able to process all of this information. Processing 256 MB of updates would take a considerable number of CPU cycles for router R1, further delaying the routing of user data. If the second command, clear ip bgp 10.1.1.2, is used instead, one neighbor is reset at a time. The impact is less severe on the router that is issuing this command; however, it takes longer to change policy for all of the neighbors, because each must be done individually rather than all at once as with the clear ip bgp * command. The clear ip bgp command still performs a hard reset and must reestablish the TCP session with the specified address, but this command affects only a single neighbor at a time.
6-81
For more details about clear ip bgp command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-82
Soft Reset Outbound
Routes learned from this neighbor are not lost. This router resends all BGP information to the neighbor without resetting the connection. This option is highly recommended when you are changing the outbound policy. The soft out option does not help if you are changing an inbound policy.
ROUTE v 1.06-29
The soft out option of the clear ip bgp command causes BGP to do a soft reset for outbound updates. The router issuing the clear ip bgp 10.1.1.2 soft out command does not reset the BGP session; instead, the router creates a new update and sends the whole table to the specified neighbor. This update includes withdrawal commands for the networks that the other neighbor will not see anymore based on the new outbound policy.
Note The soft keyword of this command is optional; clear ip bgp out does a soft reset for outbound updates.
6-83
Inbound Soft Reset
This router stores all updates from this neighbor in case the inbound policy is changed. The command is memory intensive.
Uses the stored information to generate new inbound updates.
ROUTE v 1.06-30
There are two ways to perform an inbound soft reconfiguration: using stored routing update information, as shown in the figure above, and dynamically, as shown in the next figure. Enter the neighbor command that is shown in the figure above to inform BGP to save all updates that were learned from the neighbor specified. The BGP router retains an unfiltered table of what that neighbor has sent. When the inbound policy is changed, use the clear ip bgp command shown in the figure above. The stored unfiltered table is used to generate new inbound updates; the new results are placed in the BGP forwarding database. Thus, if changes are made, the other side does not have to be forced to resend everything.
6-84
Route Refresh: Dynamic Inbound Soft Reset
Routes advertised to this neighbor are not withdrawn Does not store update information locally The connection remains established Introduced in Cisco IOS Software Release 12.0(2)S and 12.0(6)T
ROUTE v 1.06-31
Cisco IOS Software Releases 12.0(2)S and 12.0(6)T introduced a BGP soft reset enhancement feature, also known as route refresh, which provides automatic support for dynamic soft reset of inbound BGP routing table updates, and is not dependent upon stored routing table update information. The clear ip bgp soft in command implements this feature. This method requires no preconfiguration and requires significantly less memory than the previous soft method for inbound routing table updates. The soft in option generates new inbound updates without resetting the BGP session, but it can be memory intensive. BGP does not allow a router to force another BGP speaker to resend its entire table. If the inbound BGP policy is changed and a hard reset is not to be completed, configure the router to perform a soft reconfiguration.
Note To determine whether a BGP router supports this route refresh capability, use the show ip bgp neighbors command. The following message is displayed in the output when the router supports the route refresh capability: If all BGP routers support the route refresh capability, use the clear ip bgp {* | address | peer-group-name} in command. It is not necessary to use the soft keyword because soft reset is automatically assumed when the route refresh capability is supported.
Note
The clear ip bgp soft command performs a soft reconfiguration of both inbound and outbound updates.
6-85
Monitoring Soft Reconfiguration
ROUTE v 1.06-32
When a BGP session is reset and soft reconfiguration is used, several commands exist to monitor the BGP routes that are received, sent, or filtered. The following commands can be used: show ip bgp neighbor address received show ip bgp neighbor address routes show ip bgp show ip bgp neighbor address advertised
6-86
debug ip bgp updates Command
ROUTE v 1.06-33
The figure above shows a partial output from the debug ip bgp updates command on router R1 after the clear ip bgp command is issued to clear the BGP sessions with its IBGP neighbor 10.1.0.2. After the neighbor adjacency is reestablished, router R1 creates and sends updates to 10.1.0.2. The first update highlighted in the figure, 10.1.1.0/24, next 10.1.0.1, is an update about network 10.1.1.0/24, with a next hop of 10.1.0.1, which is the address of router R1. The second update highlighted in the figure, 10.97.97.0/24, next 172.31.11.4, is an update about network 10.97.97.0/24, with a next hop of 172.31.11.4, which is the address of one of the EBGP neighbors of router R1. The EBGP next-hop address is being carried into IBGP. Router R1 later receives updates from 10.1.0.2. The update highlighted in the figure contains a path to two networks, 10.1.2.0/24 and 10.1.0.0/24. The attributes shown in this update are described in the next lesson.
Note Debugging uses up router resources and should be turned on only when necessary.
For more details about debug ip bgp updates command, please check the Cisco IOS Debug Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/debug/command/reference/db_book.html
6-87
Summary
Summary
For a BGP configuration, the following must be defined: BGP requirements, BGP parameters, and connectivity. BGP is configured with the following basic BGP commands: router bgp autonomous-system, neighbor ip-address remoteas autonomous-system, network network-number [mask network-mask] The neighbor shutdown command administratively shuts down a BGP neighbor. When creating a BGP packet, the neighbor statement defines the destination IP address and the outbound interface defines the source IP address.
ROUTE v 1.06-34
Summary (cont.)
When establishing a BGP session, the BGP goes through the following states: idle, connect, open sent, open confirm, and established. You can configure MD5 authentication between two BGP peers, which means that each segment sent on the TCP connection between the peers is verified. One EBGP neighbor exists in a single-homed environment. The show and debug commands are used to troubleshoot the BGP session.
ROUTE v 1.06-35
6-88
Lesson 5
Lab 6-1 Debrief

Overview
In Lab 6-1, students configure Border Gateway Protocol (BGP) operations. Given a routed network, students simulate multihomed Internet service provider (ISP) connections and configure External BGP (EBGP) on the enterprise router to connect to the two ISPs. After completing the lab, the instructor will lead the discussion about lab topology, tasks, verification, and checkpoints, as well as sample solutions and different alternatives. Students will present their implementation plan and solution.
Objectives
Upon completing this lesson, you will be able to explain the lab topology, configure BGP operations, create checkpoints for configuration and verification, and find alternative solutions. This ability includes being able to meet these objectives: Compare your solution, findings, and action log against a set of checkpoints provided by the instructor and identify common and alternative solutions. Consolidate the lessons learned during the review discussions into a set of best practice methods and commands to aid you in future troubleshooting procedures.

This topic describes the lab topology and key checkpoints used to create a solution and begin verification.
Lab Topology
ROUTE v1. 06-2
The figure above presents a logical lab topology used for configuration of a BGP operations lab. The topology uses four pod routers, which are members of an Internal BGP (IBGP) relationship, and two backbone routers, which are members of an EBGP relationship. The lab is preconfigured with addressing, including loopbacks and an IGP routing protocol. Based on the topology, students can create a basic BGP operations configuration, including entering BGP processes, creating neighbors, advertising networks, as well as utilizing additional BGP options including synchronization, peer groups, and authentication.
6-90
Lab Review: What did you accomplish?

Task 1 Cleaning Up
What steps did you take to remove unnecessary configuration? How did you create the initial configuration?
Task 2 Configuring BGP

What is needed to configure basic BGP? What steps did you take to configure neighbors, advertise networks, and verify the configuration?
Task 3 Configuring BGP authentication

Which authentication type did you select? How can you verify MD5 authentication?
ROUTE v1. 06-3
The lab consists of three tasks. Students need an implementation plan to fulfill the lab requirements. In the first task, students need to perform lab cleanup, in which the previous configuration is erased and the lab is prepared with an initial configuration supporting Lab 6-1, Configure BGP Operations. In the second task, students configure basic BGP steps from entering the BGP process to neighbor definition and network advertisements. In the third task, students configure additional BGP configuration options including Message Digest 5 (MD5) authentication, and learn additional commands used for better reachability of next hop between IBGP and EBGP neighbors.
6-91
Verification
Is your solution working? What method did you follow to verify the status of all BGP connections? Which commands did you use to verify the following information? Display information about BGP and TCP connections to neighbors Display the parameters and current state of the active routing protocol process Display entries in the BGP routing table
ROUTE v1. 06-4
After each configuration task, verification takes place where students check their configurations. Several show commands are used during the verification process showing many parameters of the BGP process and neighbor relationship. Verification includes use of the following commands: show ip bgp summary: Displays the status of all BGP connections. show ip bgp neighbors: Displays information about BGP and TCP connections to neighbors. show ip protocols: Displays the parameters and current state of the active routing protocol process. show ip bgp: Displays entries in the BGP routing table.
6-92
Check Points
BGP process and AS number Neighbor relationship status Advertise networks BGP routing information base BGP routes BGP protocol Default route Authentication
ROUTE v1. 06-5
During the configuration and verification phase, a network operator can deal with several checkpoints. After completing all configuration tasks, BGP configuration can be successfully completed or additional verification and troubleshooting is needed. Optionally, a network operator can check the BGP configuration in different stages of the implementation using the checkpoints at each stage. With different checkpoints, a network operator can check for proper configuration with the following steps: Check BGP process and autonomous system (AS) number Check neighbor relationship status Check which networks are advertised Check BGP routing information base Check BGP routes Check BGP protocol Check for default route Check authentication
6-93

Sample Solution
Configure BGP process Define neighbors Advertise networks Define default route Configure authentication
ROUTE v1. 06-6
A sample solution includes configuration steps for each of the tasks. Different solutions are possible and the figure above points out the important tasks needed for a successful configuration. To be able to successfully complete the lab configuration, use the following guidelines: Enter the BGP process using the correct AS number. Define neighbors using a directly connected interface (EBGP) or loopback interface (IBGP). Advertise the local networks into BGP using a network statement with the mask keyword. Define the default route inside IGP that is used inside the AS. Configure authentication on both neighbors.
6-94
BGP process Different AS numbers and connectivity options EBGP/IBGP neighbors update-source command Advertise networks next-hop-self, synchronization
ROUTE v1. 06-7
Same or similar results can be achieved by using different configuration steps. When entering a BGP process, different AS numbers can be used between the neighbors. An EBGP or IBGP neighbor relationship is defined based on which AS number is used among the neighboring routers. EBGP and IBGP relationships have different connectivity rules. An EBGP neighbor relationship is established between the directly connected neighbors and an IBGP neighbor relationship does not have this requirement. Loopbacks are used for IBGP neighbor relationships. Networks are advertised with the next-hop attribute, which is processed in a different way based on an EBGP or IBGP neighbor relationship. The next-hop attribute can be changed, as well as the network advertisement between the EBGP and IBGP neighbors.
6-95
Q and A
1. Why is the AS number important? 2. Why is the neighbor IP address important? 3. Why is authentication necessary?
ROUTE v1. 06-8
The AS number is important when creating neighbors because AS numbers define the EBGP or IBGP relationship. An IP address used during neighbor configuration is important because EBGP neighbors require directly connected neighbors rather than IBGP neighbors where there is no need to be directly connected. The synchronization rule says that a router will not advertise routes in BGP until it learns the routes in an IGP. It is safe to have the synchronization rule off only if all routers in the transit path in the AS are running full-mesh IBGP. Authentication in BGP is used to verify that only trusted neighbors establish the neighbor relationship. If some other routers configured for BGP are added to the system, they cannot attract traffic and establish the neighbor relationship.
6-96
Summary
Summary
Create a good implementation plan and define the BGP requirements before configuring BGP operations. Several solutions exist and alternative solutions give similar or very different results.
ROUTE v1. 06-9
6-97
6-98
Lesson 6
Using the BGP Attributes and Path Selection Process

Overview
Border Gateway Protocol (BGP) is used to perform policy-based routing. In order to manipulate the best paths chosen by BGP, a network administrator must understand the different attributes that BGP uses and how BGP selects the best path based on these attributes. This lesson explains the BGP path selection process and the BGP attributes and their characteristics, and discusses configuration steps using different attributes for selecting a BGP path. Route filtering using route maps and prefix lists is described as well.
Objectives
Upon completing this lesson, you will be able to configure and verify BGP operations in a multihomed environment using the BGP attributes and route maps to control all BGP routes to and from the router. This ability includes being able to meet these objectives: Understand the BGP path selection process. Identify the characteristics of BGP attributes for path selection and path manipulation. Configure filtering of BGP routing updates.
BGP Path Selection

This topic describes the criteria for selecting a BGP path.
BGP Path Selection

The BGP table can have several paths for each network to choose from BGP is not designed to perform load balancing: Paths are chosen because of policy. Paths are not chosen based upon bandwidth. The BGP selection process eliminates any multiple paths until a single best path remains.
ROUTE v1. 06-2
Routers often have several neighbors and receive routing updates from each neighbor. All routing updates enter the BGP forwarding table, and as a result, multiple paths may exist to reach a given network. The whole BGP forwarding table can be displayed using the show ip bgp command. Next, paths for the network are evaluated to determine which path is best. Paths that are not the best are eliminated from the selection criteria but kept in the BGP forwarding table in case the best path becomes inaccessible. If one of the best paths is not accessible, then a new best path must be selected. BGP is not designed to perform load balancing; paths are chosen based on policy, not based on bandwidth. The BGP selection process eliminates any multiple paths until a single best path remains.
6-100
Routing Table Manager

The best path is submitted to the routing table manager process.
The best path is evaluated against the routes of other routing protocols for reaching that network. The route with the lowest administrative distance from the source will be installed in the routing table.
ROUTE v1. 06-3
The best path is submitted to the routing table manager process and is evaluated against any other routing protocols that can also reach that network. The router usually runs BGP and one of the interior gateway protocols (IGP) (such as Routing Information Protocol [RIP], Enhanced Interior Gateway Routing Protocol [EIGRP], Open Shortest Path First [OSPF], and so on), which are sending candidates for the routing table to the routing table manager. The route from the source with the lowest administrative distance is installed in the routing table. The whole routing table can be displayed using the show ip route command.
6-101
Route Selection Decision Process

Consider only (synchronized) routes with no AS loops and a valid next hop. The next steps in the evaluation process are:
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Prefer highest weight (local to router). Prefer highest local preference (global within AS). Prefer route originated by the local router (next hop = 0.0.0.0). Prefer shortest AS path. Prefer lowest origin code (IGP < EGP < incomplete). Prefer lowest MED (exchanged between autonomous systems). Prefer the EBGP path over the IBGP path. Prefer the path through the closest IGP neighbor. Prefer the oldest route for EBGP paths. Prefer the path with the lowest neighbor BGP router ID. Prefer the path with the lowest neighbor IP address.
ROUTE v1. 06-4
After BGP receives updates about different destinations from different autonomous systems, it chooses the single best path to reach a specific destination. The decision process is based on the BGP attributes. When faced with multiple routes to the same destination, BGP chooses the best route for routing traffic toward the destination. BGP considers only synchronized routes with no autonomous system loops and a valid next hop. The following process summarizes how BGP chooses the best route on a Cisco router: 1. Prefer the route with the highest weight. (Recall that the weight is proprietary to Cisco and is local to the router only.) 2. If multiple routes have the same weight, prefer the route with the highest local preference. (Recall that the local preference is used within an autonomous system.) 3. If multiple routes have the same local preference, prefer the route that the local router originated. A locally originated route has a next hop of 0.0.0.0 in the BGP table. 4. If none of the routes were locally originated, prefer the route with the shortest autonomous system path. 5. If the autonomous system path length is the same, prefer the lowest origin code (IGP < EGP < incomplete).
6-102
6. If all origin codes are the same, prefer the path with the lowest multiexit discriminator (MED). (Recall that the MED is exchanged between autonomous systems.) The MED comparison is made only if the neighboring autonomous system is the same for all routes considered, unless the bgp always-compare-med command is enabled.
Note The most recent Internet Engineering Task Force (IETF) decision regarding BGP MED assigns a value of infinity to the missing MED, making the route lacking the MED variable the least preferred. The default behavior of BGP routers running Cisco IOS Software is to treat routes without the MED attribute as having a MED of 0, making the route lacking the MED variable the most preferred. To configure the router to conform to the IETF standard, use the bgp bestpath missing-as-worst command.
7. If the routes have the same MED, prefer external paths (EBGP) to internal paths (Internal BGP, or IBGP). 8. If synchronization is disabled and only internal paths remain, prefer the path through the closest IGP neighbor. This step means that the router will prefer the shortest internal path within the autonomous system to reach the destination (the shortest path to the BGP next hop). 9. For EBGP paths, select the oldest route to minimize the effect of routes going up and down (flapping). 10. Prefer the route with the lowest neighbor BGP router ID value. 11. If the BGP router IDs are the same, prefer the router with the lowest neighbor IP address. Only the best path is entered in the routing table and propagated to the BGP neighbors of the router.
Note The route selection process summarized here does not cover all cases but is sufficient for a basic understanding of how BGP selects routes.
For example, suppose there are seven paths to reach network 10.0.0.0. None of the paths have autonomous system loops and all paths have valid next-hop addresses, so all seven paths proceed to Step 1, which examines the weight of the paths. All seven paths have a weight of 0, so all paths proceed to Step 2, which examines the local preference of the paths. Four of the paths have a local preference of 200, and the other three have local preferences of 100, 100, and 150. The four with a local preference of 200 will continue the evaluation process in the next step. The other three will still be in the BGP forwarding table, but are currently disqualified as the best path. BGP will continue the evaluation process until only a single best path remains. The single best path that remains will be submitted to the IP routing table as the best BGP path.
6-103
Path Selection with Multihomed Connection

An autonomous system rarely implements BGP with only one EBGP connection. This situation generally means that multiple paths exist for each network in the BGP forwarding database. If only one path exists and it is loop-free and synchronized with the IGP for IBGP, and the next hop is reachable, the path is submitted to the IP routing table. There is no path selection taking place because there is only one path and manipulating it will derive no benefit. Only the best path is put in the routing table and propagated to the routers BGP neighbors. Without route manipulation, the most common reason for path selection is Step 4, prefer the shortest autonomous system path. Step 1 looks at weight, which by default is set to 0 for routes that were not originated by this router. Step 2 compares local preference which, by default, is set to 100 for all networks. Both of these steps have an effect only if the network administrator configures the weight or local preference to a nondefault value. Step 3 looks at networks that are owned by this autonomous system. If one of the routes is injected into the BGP table by the local router, the local router prefers it to any routes received from other BGP routers. Step 4 selects the path that has the fewest autonomous systems to cross. This is the most common reason a path is selected in BGP. If a network administrator does not like the path with the fewest autonomous systems, the administrator needs to manipulate the weight or local preference to change which outbound path BGP chooses. Step 5 looks at how a network was introduced into BGP. This introduction is usually either with network statements (i for an origin code) or through redistribution (? for an origin code). Step 6 looks at MED to judge where the neighbor autonomous system wants this autonomous system to send packets for a given network. Cisco sets the MED to 0 by default; therefore, MED does not participate in path selection unless the network administrator of the neighbor autonomous system manipulates the paths using MED. If multiple paths have the same number of autonomous systems to traverse, the second most common decision point is Step 7, which states that an externally learned path from an EBGP neighbor is preferred over a path learned from an IBGP neighbor. A router in an autonomous system prefers to use the bandwidth of the Internet service provider (ISP) to reach a network rather than using internal bandwidth to reach an IBGP neighbor on the other side of its own autonomous system. If the autonomous system path is equal and the router in an autonomous system has no EBGP neighbors for that network (only IBGP neighbors), it makes sense to take the quickest path to the nearest exit point. Step 8 looks for the closest IBGP neighbor; the IGP metric determines what closest means (for example, RIP uses hop count, and OSPF uses the least cost, based on bandwidth).
6-104
If the autonomous system path is equal and the costs via all IBGP neighbors are equal, or if all neighbors for this network are EBGP, the oldest path, Step 9, is the next common reason for selecting one path over another. EBGP neighbors rarely establish sessions at exactly the same time. One session is likely older than another, so the paths through that older neighbor are considered more stable because those paths have been up for a longer period of time. If all of the above criteria are equal, the next most common decision is to choose the neighbor with the lowest BGP router ID, which is Step 10. If the BGP router IDs are all the same (for example, if the paths are to the same BGP router), Step 11 states that the route with the lowest neighbor IP address is used.
6-105
Characteristics of BGP Attributes for Path Selection and Path Manipulation

BGP attributes inform the BGP routers receiving updates about how to treat the paths to the final network. This topic describes the characteristics of the BGP attributes that affect path selection.
Weight Attribute
Weight is an attribute that is proprietary to Cisco. Weight is not sent to any BGP neighbors. It is local to the router only. Paths with the highest weight value are preferred.
ROUTE v1. 06-5
The weight attribute is an attribute that Cisco defines for the path selection process. The weight is configured locally on a router and is not propagated to any other routers. This attribute applies when one router is used with multiple exit points out of an autonomous system, as opposed to the local preference attribute, which is used when two or more routers provide multiple exit points. The weight can have a value from 0 to 65535. Paths that the router originates have a weight of 32768 by default, and other paths have a weight of 0 by default. Routes with a higher weight are preferred when multiple routes exist to the same destination. In the figure above, routers R2 and R4 learn about network 172.20.0.0 from autonomous system (AS) 65020 and propagate the update to router R1. Router R1 has two ways to reach 172.20.0.0, and it must decide which route to takethe path through router R2 or the path through router R4. In the example, router R1 sets the weight of updates coming from router R2 to 200 and the weight of those coming from router R4 to 150. Because the weight for the route pointing to router R2 is higher than the weight for route pointing to router R4, router R1 uses router R2 as a next hop to reach 172.20.0.0.
6-106
Set Weight with Route Map

First BGP path selection criteria Prefer the highest weight (local to router) BGP weight can be specified per neighbor by a complex criteria with route maps
ROUTE v1. 06-6
One way of changing the path selection is to use weights. Weight is an attribute that is locally significant to a router. Weight is a property or parameter. Therefore, it is not seen on any neighboring routers. When designing BGP networks using weights, network administrators should set the weights on every router. If there is more than one path for the same network, a router will choose the one with the highest weight. The default value for weight is 0. When a route map is applied, it is configured on the router. The route map can be arbitrarily complex and select routes based on various selection criteria, such as a network number or AS path. The selected routes can have some altered attributes. The route map can set the weight values of permitted routes. Selection can be done in several route-map statements, giving the opportunity to assign a certain weight value to some routes and another weight value to others. A route map can also completely filter out routes. AS path filters, prefix lists, or other BGP attributes are used to match routes, where any combination can be used. Routes that are not matched are discarded.
6-107
Using Route Maps for Path Selection
Enter route map configuration mode.
Match on the BGP attribute. Set the new value for the BGP attribute.
Apply the route map to the incoming or outgoing updates.
ROUTE v1. 06-7
Three steps are needed when using route maps for path selection. In the first step, a route map must be created. Use the route-map command in global configuration mode to create a route map and to enter route map configuration mode. In the second step a rule for changing the BGP attributes is created. Use the match command in route-map configuration mode to define which incoming or outgoing updates will be affected. Use the set command in route-map configuration mode to change selected BGP attributes. The last step is required to apply a configured route map to incoming or outgoing routes. Use the neighbor route-map command in router configuration mode to apply the route map to BGP updates. For more details about the route-map, match, set, and neighbor route-map commands, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-108
Set Weight with Route Map Example

In the example above, the routing policy dictates the selection of AS 65030 as the primary way out of AS 65040 for the traffic destined to any network originated by AS 65020. This limitation is achieved by placing a high weight of 150 on all incoming announcements from AS65030 (that is, from neighbor 10.0.0.1), which carry the information about the network originated in AS 65020.
6-109
Local Preference Attribute

Used to select the outbound EBGP path Sent to IBGP neighbors only (and only within the AS) Stripped in the outgoing EBGP updates except in the EBGP updates with confederation peers The local preference attribute is well known and discretionary Default value = 100 Paths with the highest local preference value are preferred
ROUTE v1. 06-9
Local preference is a well-known discretionary attribute that provides information to routers in the autonomous system about the path that is preferred for exiting the autonomous system. A path with a higher local preference is preferred. The local preference is an attribute that is configured on a router and exchanged among routers within the same autonomous system only. The default value for local preference on a Cisco router is 100. To change the default local preference value of 100, use the bgp default local-preference command. In the figure above, AS 65050 receives updates about network 172.16.0.0 from two neighbors. Each of the networks is advertising a different path to the destination. The local preference on router R1 for network 172.16.0.0 is set to 200, and the local preference on router R2 for network 172.16.0.0 is set to 150. Because the local preference information is exchanged within AS 65050, all routers are aware of the exit point for network 172.16.0.0 out of AS 65050. In the figure, router R1 is configured with higher local preference than router R2 and all the traffic destined for network 172.16.0.0 will be sent to router R1 as an exit point from AS 65050. For more details about the route bgp default local-preference command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-110
Set Local Preference with Route Map

Second BGP path selection criteria Prefer highest local preference (global within AS) Local preference can be set when processing incoming route updates doing redistribution sending outgoing route updates BGP local preference can be specified per neighbor by complex criteria with route maps
RO UTE v 1.06-10
Using BGP in autonomous systems with a single neighbor relationship usually does not require any advanced features. In multihomed situations however, it is important to ensure that the customer routers choose the correct link. Local preference is the second-strongest criterion in the route selection process. If there are two or more paths available for the same network, a router will first compare weight, and if the weights are equal for all paths, the router will then compare the local preference attributes. The path with the highest local preference value will be preferred. The default value for local preference is 100. Local preference is similar to weight because it is an attribute. It can be set once and can then be viewed on neighboring routers without having to reset it. This attribute has a default value of 100, which the router will apply to locally originated routes and updates that come in from external neighbors. Updates that come from internal neighbors already have the local preference attribute. The local preference attribute is automatically stripped from outgoing updates to External Border Gateway Protocol (EBGP) sessions. This practice means that this attribute can be used only within a single AS to influence the route selection process. BGP local preference can be specified per neighbor by complex criteria using route maps. AS path filters, prefix lists, and other BGP attributes are used to match routes, where any combination can be used. Routes that are not matched are discarded.
6-111
Set Local Preference with Route Map (Cont.)
R1#

In the example above, the routing policy dictates the selection of AS 65030 as the primary way out of the AS 65040. This limitation is achieved by placing a local preference that is higher than the default local preference of 150 on all incoming announcements from AS 65040; that is, from neighbor 10.0.0.1. Updates entering AS 65040 from AS 65030 will be processed by all BGP routers inside AS 65040 and these updates will be preferred to other updates having the default local preference.
6-112
Set AS Path with Route Map

Fourth BGP path selection criteria Prefer shorter AS paths (only length is compared) Influences the outbound path selection in a multihomed AS Manual manipulation of AS path lengthAS path prepending AS path prepending can be specified per neighbor by complex criteria with route maps (AS path filters, prefix lists, or other BGP attributes that match the routes in any combination)
RO UTE v 1.06-12
When connections to multiple providers are required, it is important that BGP selects the optimum route for traffic to use. The optimum, or best, route may not be what the network designer intended based on design criteria, administrative policies, or corporate mandate. It is fairly easy for an AS to select the appropriate path for outgoing traffic. It is much more complicated to influence other autonomous systems to select the appropriate path for traffic that is returning to a specific AS. It is unlikely that the operator of an AS can request changes in router configurations in another AS. This limitation makes it virtually impossible to influence another AS to select the desired path based on the weight and local preference attributes, because both options would require configuration changes in the neighboring AS. If no BGP path selection tools are configured on the route to influence the traffic flow, BGP will use the shortest AS paththe fourth option in the path selection process. If the AS path is not manually manipulated by some administrative means, the path going over the fewest number of autonomous systems is selected by the router regardless of available bandwidth. However, if the AS that is attempting to influence the incoming traffic flow is sending out EBGP updates with a manipulated AS path attribute over that undesired path, the receiver of this update is less likely to select it as the best because the AS path now appears to be longer. AS path prepending potentially allows the customer to influence the route selection of its service providers. The AS path is extended with multiple copies of the AS number of the sender. There is no exact mechanism to calculate the required prepended AS path length. The benefit of manipulating AS paths to influence route selection is that the configuration that is needed is done in the AS that is requesting a desired return path.
6-113
Set AS Path with Route Map (Cont.)
R1#
RO UTE v 1.06-13
AS paths can be manipulated by prepending AS numbers to existing AS paths. Normally, AS path prepending is performed on outgoing EBGP updates over the undesired return path. Because the AS paths sent over the undesired link become longer than the AS path sent over the preferred path, the undesired link is now less likely to be used as the return path. The length of the AS path is extended because additional copies of the AS number of the sender are prepended to the AS path attribute. To avoid clashes with BGP loop prevention mechanisms, no other AS number, except that of the sending AS, should be prepended to the AS path attribute. If another AS number is prepended in the AS path, the routers in the AS that has been prepended will reject the update because of BGP loop prevention mechanisms. Prepending can be configured on a router for all routing updates that are sent to a neighbor or only on a subset of these updates. In the example, all updates sent to neighbor 172.16.1.1 are prepended three times with AS 65040, the AS number of the sender, thus making that path less preferable for the returning traffic. Keep in mind that if any AS on the path also does AS path prepending, the policy may not work.
6-114
MED Attribute
The paths with the lowest MED (also called the metric) value are the most desirable. MED is used to advertise an exit path to be used by EBGP neighbors to reach networks owned by this AS. The MED attribute is optional and nontransitive.
RO UTE v 1.06-14
The MED attribute, also called the metric, is an optional nontransitive attribute. The MED is an indication to EBGP neighbors about the preferred path into an AS. The MED attribute is a dynamic way to influence another AS about which path that it should choose to reach a certain route when multiple entry points into an AS exist. A lower metric is preferred. Unlike local preference, the MED is exchanged between autonomous systems. The MED is sent to EBGP peers. Those routers propagate the MED within their AS, and the routers within the AS use the MED but do not pass it on to the next AS. When the same update is passed on to another AS, the metric is set back to the default of 0. To change this value, use the defaultmetric number command under the BGP process. All routes that are advertised to an EBGP neighbor are set to the value specified using this command. MED influences inbound traffic to an AS, and local preference influences outbound traffic from an AS. By default, a router compares the MED attribute only for paths from neighbors in the same AS.
Note The MED attribute means that BGP is the only protocol that can affect how routes are sent into an AS.
In the figure above, the router R2 MED attribute is set to 150, and the router R3 MED attribute is set to 200. When router R1 receives updates from routers R2 and R3, it picks router R2 as the best next hop because its MED of 150 is less than the router R3 MED of 200. For more details about the default-metric number command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-115
Set MED with Route Map
RO UTE v 1.06-15
This figure is used in the following configurations to demonstrate how to manipulate inbound traffic using route maps to change the BGP MED attribute. The intention of these route maps is to designate router R1 as the preferred path to reach networks 192.168.25.0/24 and 192.168.26.0/24 and to designate router R2 as the preferred path to reach network 192.168.24.0/24. The other networks should still be reachable through each router in case of a link or router failure.
6-116
Route Map for Router R1
RO UTE v 1.06-16
The MED is set outbound when a router is advertising to an EBGP neighbor. In the configuration example for router R1, a route map named med_65020 is linked to neighbor 192.168.28.1 as an outbound route map. When router R1 sends an update to neighbor 192.168.28.1 (router R4), it processes the outbound update through route map med_65020 and uses a set statement to change any values that are specified, as long as the preceding match statement is met in that section of the route map. The first line of the route map is a permit statement with a sequence number of 10 for the route map med_65020; this defines the first route-map statement. The match condition for this statement checks all networks that are permitted by access list 66. The first line of access list 66 permits any networks that start with the first three octets of 192.168.25.0, and the second line of access list 66 permits networks that start with the first three octets of 192.168.26.0. All networks that are permitted by either of these lines are set to a MED of 100. All other networks are denied by this access list (there is an implicit deny all at the end of all access lists), so those networks are not set to a MED of 100; their MED is not changed. These other networks must proceed to the next route map statement in the med_65020 route map. The second statement of the route map is a permit statement with a sequence number of 100 for the route map med_65020. The route map does not have any match statements, just a set metric 200 command. This is a permit all statement for route maps. Because the network administrator does not specify a match condition for this portion of the route map, all networks being processed through this section of the route map (sequence number 100) are permitted, and are set to a MED of 200. If the network administrator did not set the MED to 200, by default it would have been a MED of 0. Because 0 is less than 100, the routes with a MED of 0 would have been the preferred paths to the networks in AS 65010.
6-117
Route Map for Router R2
RO UTE v 1.06-17
Similarly, in the configuration example for router R2, a route map named med_65020 is linked to neighbor 172.20.50.1 (router R5) as an outbound route map. Before router R2 sends an update to neighbor 172.20.50.1, it will process the outbound update through route map med_65020 and use a set statement to change any values that are specified, as long as the preceding match statement is met in that section of the route map. The first line of the route map is a permit statement with a sequence number of 10 for the route map med_65020, which defines the first route-map statement. The match condition for that line checks all networks that are permitted by access list 66. Access list 66 on router R2 permits any networks that start with the first three octets of 192.168.24.0. Any networks that are permitted by this line are set to a MED of 100. All other networks are denied by this access list, and are not set to a MED of 100. These other networks must proceed to the next route map statement in the med_65020 route map. The second statement of the route map is a permit statement with a sequence number of 100 for the route map med_65020, but it does not have any match statements, just a set metric 200 command. This is a permit all statement for route maps. Because the network administrator does not specify a match condition for this portion of the route map, all networks being processed through this second statement of the route-map are permitted, but are set to a MED of 200. If the network administrator did not set the MED to 200, by default it would have been set to a MED of 0. Because 0 is less than 100, the routes with a MED of 0 would have been the preferred paths to the networks in AS 65010. On router R6, there are multiple paths to reach each network from AS 65010. These paths all have valid next-hop addresses, have synchronization disabled, and are loop-free. All networks have a weight of 0 and a local preference of 100, so Steps 1 and 2 do not determine the best path.
None of the routes were originated by this router or any router in AS 65020; all networks came from AS 65010, so Step 3 does not apply. All networks have an AS path of one AS (65010) and were introduced into BGP with network statements (i is the origin code), so Steps 4 and 5 are equal. Step 6 states that BGP chooses the lowest MED if all preceding steps are equal or do not apply. For network 192.168.24.0, the next hop of 172.20.50.2 has a lower MED than the next hop of 192.168.28.2. Therefore, for network 192.168.24.0, the path through 172.20.50.2 is the preferred path. For networks 192.168.25.0 and 192.168.26.0, the next hop of 192.168.28.2 has a lower MED of 100 compared to the MED of 200 through the next hop of 172.20.50.2; therefore, 192.168.28.2 is the preferred path for those networks.
6-119
Filtering of BGP Routing Updates

BGP is receiving a high number of routing updates. In order to optimize the BGP configuration, route filtering must be applied. This topic describes the steps needed to configure filtering of routing updates.
Steps to Configure BGP Route Filtering Using IP Prefix Lists

Define traffic filtering requirements: Filtering updates Controlling redistribution Configure matching statements using: mask filtering, ge, le Apply a prefix list to filter inbound or outbound updates
RO UTE v 1.06-18
When planning filter configuration using prefix lists, the following steps are required and an implementation plan must be created for these steps: Define the traffic filtering requirements: Filtering updates Controlling redistribution
Configure the matching statements: Use mask filtering, ge, le
Apply a prefix list to filter inbound or outbound updates
6-120
Configuring Filtering of BGP Routing Updates

Configure a matching statement to match all networks with the mask from /8 to /24.

Applies an inbound prefix list filter to prevent distribution of subnets /8 to /24. The prefix list is applied to incoming advertisements from the 172.16.1.2 neighbor.
RO UTE v 1.06-19
Prefix-list entries where the ge and le option are specified match any prefix within the address range that are specified using the ge and le parameters. In the example above, the prefix list named ANY-8to25-NET is configured to match routes from any network that has a mask length from 8 to 24 bits. The 0.0.0.0/0 network/length combination does not match a specific network, but is used to define any network. The combination of ge 8 le 24 parameters specifies that any network with a mask length between 8 and 24 is a match. A prefix list must be applied to inbound or outbound updates. In the figure above, the prefix list ANY-8to25-NET is applied to the inbound traffic to prevent distribution of BGP neighbor information. The prefix list is applied to incoming advertisements from the BGP neighbor 172.16.1.2, which prevents distribution of routes from any network that has a mask length from 8 to 24 bits. For more details about the neighbor prefix-list command, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-121
Verify Filtering of BGP Routing Updates

Configure a matching statement to match all networks with the mask from /8 to /24.
RO UTE v 1.06-20
To display information about a prefix list or prefix list entries, use the show ip prefix-list command. The show ip prefix-list command output shows the count of packets being matched. The clear ip prefix-list command is used to clear the prefix list hit counters. The hit count is a value indicating the number of matches to a specific prefix list entry. For more details about the show ip prefix-list and clear ip prefix-list commands, please check the Cisco IOS IP Routing Protocols Command Reference on the following link: http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
6-122
Steps to Configure Route Filtering with a Route Map

Define the route map Define match statements Define set statements Define route filtering using a route map
RO UTE v 1.06-21
When planning filter configuration using route maps, the following steps are required and an implementation plan must be created for these steps: Define the route map

Define the match statements Define the set statements
Define the route filtering using route-maps
6-123
Using Route Maps for Filtering Routing Updates
Applies a route map RouteFilter to incoming BGP updates from neighbor 172.16.1.2 Filtering can be applied to outgoing updates. Prefixes that are not permitted by the route map are discarded. Route maps can also change the BGP attributes of incoming or outgoing updates.
RO UTE v 1.06-22
To apply a route map to filter incoming or outgoing BGP routes, use the neighbor route-map command in router configuration mode. The routes that are permitted can have their attributes set or changed by the set clauses in the route-map command. Setting attributes on routes is useful when attempting to influence route selection. Route map permit statements can be written to change the attributes of the permitted routes or to leave the attributes unchanged. When BGP performs route selection, the attribute values indicate that one route is preferred more than the other. Similar route filtering could be performed for the OSPF or EIGRP routing process. In this case, the distribute-list in or distribute-list out commands are used together with the route-map command, which defines which updates are dropped and which updates are accepted.
6-124
Using Route Maps as BGP Filters

Requirement: The customer will accept only a default route and use the primary link for outbound traffic.
RO UTE v 1.06-23
In this example, the customer will accept only a default route from the ISPs, and will use the link to AS 387 as the primary link for outbound traffic. The customer router in AS 213 is configured for BGP with two neighbors using the neighbors remote-as command. Both neighbors are configured with the neighbor route-map command to filter the incoming routing update traffic according to the route map named filter. Routemap filter allows a default route into the customer network, and with careful setting of the BGP weight attribute, the primary link becomes preferred. A higher value for weight is preferred and the default route coming from the ISP in AS 387 gets a weight value of 150 and the secondary default route gets a weight value of 100.
6-125
RO UTE v 1.06-24
As an option, filter lists, prefix lists, and route maps can be applied on either incoming or outgoing information, or in any combination in BGP. The incoming prefix list, the incoming filter list, and the incoming route map must all permit the routes that are received from a neighbor before they will be accepted into the BGP table. Outgoing routes must pass the outgoing filter list, the outgoing prefix list, and the outgoing route map before they will be transmitted to the neighbor. When a router is configured to redistribute routing information from IGP into BGP, the routes must successfully pass any prefix list or route map applied to the redistribution process before the route is injected into the BGP table.
6-126
Summary
Summary
After BGP receives updates about multiple destinations from different autonomous systems, it follows a multiple-step process for selecting the best route to reach a destination; the best route is a candidate for the routing table. BGP metrics are called path attributes and describe the paths to reach each network. BGP is receiving a high number of routing updates. In order to optimize the BGP configuration, route filtering with prefix-lists must be applied Route maps are used to set selected attributes for selected routes to control the outbound EBGP path selection.
RO UTE v 1.06-25
Summary (cont.)
The local preference attribute is a well-known discretionary attribute that provides an indication to routers in the AS about which path is preferred to exit the AS. The weight attribute is an attribute that Cisco defines for the path selection process; routes with a higher weight are preferred when multiple routes exist to the same destination.
RO UTE v 1.06-26
6-127
6-128
Lesson 7
Lab 6-2 Debrief

Overview
In Lab 6-2, students manipulate the BGP path selection with route maps using local preference and MED. Students use different BGP path selection methods and compare these methods in a routed network. After completing the lab, the instructor will lead a discussion about the lab topology, tasks, verification, and checkpoints and discuss a sample solution and different alternatives. Students will present their implementation plans and solutions.
Objectives
Upon completing this lesson, you will be able to explain the lab topology, configure the BGP path manipulation using a local preference and the MED BGP attributes, create check points for configuration, verification, and find alternative solutions. This ability includes being able to meet these objectives: Identify the implementation and verification tasks to establish BGP adjacency in the network and manipulate the BGP path using local preference and MED BGP attributes. Present the sample solution and identify possible alternative solutions .

This topic describes the lab topology and key checkpoints used to create a solution and to start the verification.
Lab Topology
ROUTE v1. 06-2
This figure presents the lab topology used for the configuration of BGP path manipulation lab. The topology uses four pod routers, which are members of a full Internal BGP (IBGP) relationship and two backbone routers, which are members of an External BGP (EBGP) relationship. The lab is preconfigured with addressing including loopbacks and an IGP routing protocol. Based on the topology, students can create a BGP path manipulation configuration including a full IBGP process, advertising next hop, synchronization, and path manipulation configuration.
6-130
Lab Review: What did you accomplish?

Task 1: Configure fully meshed IBGP What steps did you take to configure fully meshed IBGP? How did you deal with loopback interfaces? Task 2: Use the MED and local preference (LP) with route maps for BGP path manipulation What is the difference between a MED and an LP implementation? In what order did you execute your plan and why? How did you apply a new policy to the BGP neighbor?
ROUTE v1. 06-3
In the first task, students are asked to clean up previous router configurations and establish a full-mesh IBGP. When configuring the full-mesh IBGP, next hop and loopback reachability must be achieved. Because of the full-mesh IBGP, there is no need for synchronization. In the second task, MED and local preference are used to manipulate the path. Each time the policy is changed there is a need to perform a soft reconfiguration to see the results of the new configuration.
6-131
Verification
Is your solution working? What method did you follow to verify that BGP path manipulation is working correctly? Which commands did you use to verify the proper operation of different BGP policies?
ROUTE v1. 06-4
A common approach to verify the proper BGP path manipulation would be to take the following steps: Verify that all IBGP peering sessions are operational. The following commands can be used for this verification: show ip bgp summary: Displays the status of all BGP connections show ip bgp neighbors: Displays information about the BGP and TCP connections to neighbors
Verify what the MED and local preference values are and which routes are inside the BGP table. The following command can be used for this verification: show ip bgp: Displays entries in the BGP routing table
Verify which BGP routes were entered in the routing table. The following command can be used for this verification: show ip route: Displays entries in the IP routing table
6-132
Check Points
Full-mesh BGP Check IP routing table Loopbacks and next hop Path used to reach the remote networks Why a different path is used Soft reconfiguration
ROUTE v1. 06-5
During the configuration and verification phase, the network operator uses several checkpoints. After completing all of the configuration tasks, the BGP configuration can be successfully completed or additional verification and troubleshooting will be needed. Optionally, the network operator can check the BGP configuration in different stages of the implementation using checkpoints to verify each stage. With different checkpoints, the network operator can check for proper configuration using the following steps:
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6
Check the full-mesh BGP. Check the IP routing table. Check the loopbacks and next hop. Check the path used to reach the remote networks. Check why a different path is used. Check the soft reconfiguration.
6-133

Sample Solution
Configure full-mesh IBGP. Use loopbacks for BGP sessions. Advertise loopbacks and next hop. Disable synchronization. Manipulate the path using MED and LP. Perform a soft reconfiguration.
ROUTE v1. 06-6
This sample solution includes the configuration steps necessary for each of the tasks. Different solutions are possible. However, this figure points out the important tasks required for successful configuration. To be able to complete the lab configuration successfully, complete the following steps:
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6
Configure a full-mesh IBGP. Use loopbacks for the BGP sessions. Advertise the loopbacks and next hop. Disable synchronization. Manipulate the path using MED and local preference. Perform a soft reconfiguration.
6-134
IBGP processfull mesh or partial mesh Use loopbacks or other interfaces for BGP session Install routes into the IP routing table or advertise next hop BGP synchronization ON or OFF Using other BGP attributes (beside MED or LP) for path manipulation How to trigger an update of BGP table after policy change
The same or similar results can be achieved by using different configuration steps. When configuring an IBGP neighbor relationship, it can be either a full-mesh IBGP or partial mesh. There is no mechanism in IBGP to detect whether there is an update loop. For that reason, the IBGP neighbor never sends updates to another IBGP neighbor. If there is a need for all of the IBGP neighbors to be aware of all the BGP updates, then there is a need for a fullmesh IBGP. The IBGP next-hop address is reachable by running an IGP routing protocol inside an autonomous system (AS). Loopbacks are always on if the router is operational, and it is very convenient to establish IBGP sessions between the loopback interfaces. Loopbacks must be advertised inside an IP routing table as well as other next-hop IP addresses. When a BGP is advertising networks to other peers, the route must be present in the IP routing table or synchronization must be turned off. If running a full-mesh IBGP, there is no need for synchronization to be turned on. MED and local preferences can be used to manipulate the path selection. MED is used to influence the inbound EBGP path selection. Local preference can be used to influence the outbound EBGP path selection. There are other BGP attributes that can be used to influence the path selection: AS Path, weight, and others. When the BGP policy changes, there is a need to refresh the BGP and IP routing table. Resetting the BGP session is not an elegant solution. A soft reset is available to trigger an update of the BGP table.
6-135
Q and A
What is the advantage of full-mesh IBGP? Why is the next hop IP address important? When is synchronization needed? What are different reconfiguration options? What is the difference between MED and LP?
ROUTE v1. 06-8
Because IBGP peers are not sending BGP updates to other IBGP neighbors, within an AS there is a need to run a full-mesh IBGP in order to have a complete BGP table. Next hop is used when forwarding the packets toward their destination. Every BGP update has information about the remote networks together with the next-hop address used for forwarding the packets. The next-hop address must be reachable in order to forward the packets. The synchronization rule says that a router will not advertise routes in BGP until it learns them from an IGP. It is safe to have it off only if all routers in the transit path within the AS are running a full-mesh IBGP. To update the BGP table, the operator can clear the BGP session or trigger the neighbor to resend the complete BGP table again. This last option is called a soft reconfiguration and requires more resources. At the same time, it is not as aggressive as a BGP session staying up all of the time. MED is used to manipulate the inbound path to the AS and local preference is used to manipulate the outbound path from the AS.
6-136
Summary
Summary
Create a good implementation plan and define the BGP requirements before configuring a BGP path manipulation. Several solutions exist and alternative solutions give similar or very different results.
ROUTE v1. 06-9
6-137
6-138
Lesson 8
E-Learning Training on IPv6 and Routing for Branch Offices and Remote Workers
Overview
The Implementing Cisco IP Routing (ROUTE) v1.0 instructor-led training (ILT) course is a comprehensive learning experience. Among the learning tools available are e-learning modules that complement the classroom instructor-led content and help complete your experience with self-paced materials and demonstrations. Upon accessing the e-learning content, you will be able to reinforce the knowledge acquired in class, and witness real-life scenarios demonstrated in real routers and switches. The content structure is flexible, and you can navigate it at your own pace, at the time of your choosing, and at the depth you desire according to your level of experience. This lesson presents the topics of IPv6 and remote access connectivity. A total of two elearning modules are reviewed: Implementing IPv6 and Implementing Routing Facilities for Branch Offices and Mobile Workers. The content includes demonstrations that cover critical topics in both areas.
Objectives
Upon completing this lesson, you will be able to discuss the e-learning modules that pertain to additional topics in IPv6 and remote access connectivity. This ability includes being able to meet these objectives: Describe the content of the Implementing IPv6 e-learning module. Describe the content of the Implementing Routing Facilities for Branch Offices and Mobile Workers e-learning module. Understand the structure and the process of accessing and using e-learning content.
Preview of E-Learning Modules Implementing IPv6 and Routing Facilities for Branch Offices and Mobile Workers
This topic describes two e-learning products that pertain to additional topics in IPv6 and remote access connectivity.
CCNP E-Learning
Complement and enhance your classroom experience. Reinforce concepts and their application. Learn at your own pace. Review advanced topics. Experience real-life scenarios through directed demonstrations.
ROUTE v1. 06-2
One of the key ideas behind the design of the Cisco CCNP curriculum is the understanding that there is no one "best" method of learning for every student. Some students prefer individual labs, while others prefer one-on-one tutoring, hands-on sessions, self-paced computer-assisted instruction, direct discovery learning or cooperative learning, and other methods. E-learning solutions offer new approaches that complement and enhance classroom-based learning. Designed with flexibility and learning effectiveness in mind, the Implementing IPv6 and Implementing Routing Facilities for Branch Offices and Mobile Workers e-learning modules are based on knowledge you acquired during your Implementing Cisco IP Routing (ROUTE) v1.0 instructor-led training course. Both modules include new concepts and describe these concepts starting with the fundamentals and going into more depth through directed demonstrations.
6-140
Implementing IPv6
Lesson IPv6 Addressing and Unicast Description
Learn the fundamentals of IPv6 technologies, focusing on static and stateless address planning and configuration, and unicast connectivity in pointto-point and multipoint links. Demonstrate router configuration in scenarios of IPv6 routing, including the integration and redistribution of multiple routing protocols such as RIPng, OSPFv3, EIGRP, and BGP. Understand the transition path to IPv6, using techniques such as manual IPv6 tunnels, 6to4 tunnels, and ISATAP tunnels. Implement static and dynamic NAT-PT.
IPv6 with RIPng, OSPFv3, EIGRP and Redistribution IPv6 Transition Techniques NAT and PAT with IPv6
ROUTE v1. 06-3
The Implementing IPv6 e-learning module covers topics that enhance Module 6, Connection of an Enterprise Network to an ISP Network, of the Implementing Cisco IP Routing (ROUTE) v1.0 course. It starts with an introductory lesson that discusses the benefits of the protocol and structural and operational fundamentals, such as addressing. Directed demonstrations will guide subsequent lessons on IPv6 routing and routing protocols, IPv4-to-IPv6 transition techniques including IPv6, 6to4 and Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunnels and Network Address Translation (NAT) as well as Port Address Translation (PAT) in IPv6 scenarios. IPv6 is supported by RIP named RIP next generation (RIPng), OSPF version3 (OSPFv3) and EIGRP routing protocols.
6-141
Implementing Routing Facilities for Branch Offices and Mobile Workers

Lesson Analyzing Branch Office Designs and Planning for Branch Office Installations Directed Demo on How to Implement Special Facilities for Branch Offices Lab Debrief Description
Watch a discussion on design fundamentals and trends for the branch office. Overview the design scenarios that will be demonstrated in the next lesson. Demonstrate router configurations in scenarios of branch office connectivity, including verification of existing services, routing around IPSec tunnels using GRE, and other routing facilities. Gather conclusions, sample configurations, and alternative methods related to the demonstrations in the previous lesson.
ROUTE v1. 06-4
The Implementing Routing Facilities for Branch Offices and Mobile Workers e-learning module also covers topics that enhance Module 6, Connection of an Enterprise Network to an ISP Network, of the Implementing Cisco IP Routing (ROUTE) v1.0 course. It is structured in two major topics: branch office scenarios and mobile worker scenarios. Branch office designs are analyzed through an introductory lesson that discusses trends and factors to consider in the implementation plan of new installations and upgrades. The directed demonstrations focus on scenarios involving backup connectivity, alternative routing across IPv6 tunnels using Generic Routing Encapsulation (GRE), load sharing, and other situation.
6-142
Implementing Routing Facilities for Branch Offices and Mobile Workers (cont.)
Lesson Analyzing Mobile Workers Designs and Planning for Mobile Workers Installations Directed Demo: Implement Special Facilities for Mobile Workers. Lab Debrief Description
Review design fundamentals and trends for the mobile worker. Overview the design scenarios that will be demonstrated in the next lesson.
Demonstrate router configurations in scenarios of mobile worker connectivity, including verification of existing services, IP address, and routing facilities provision for mobile workers. Gather conclusions, sample configurations, and alternative methods related to the demonstrations in the previous lesson.
ROUTE v1. 06-5
The mobile worker topic is approached in a similar way. An introductory lesson will describe trends and design considerations. This lesson is followed by a directed demonstration of remote access connectivity for mobile users, including addressing and routing considerations around the use of IP Security (IPsec) tunnels as a connectivity option.
6-143
Where to find E-Learning Modules

The E-Learning Training on IPv6 and Routing for Branch Offices and Remote Workers elearning modules are available on a CD as part of your classroom materials. Please contact your instructor with questions about finding and accessing the CD. The objectives of the E-Learning Training on IPv6 and Routing for Branch Offices and Remote Workers e-learning modules are part of your CCNP certification exam, and as such, candidates for the CCNP certification should review these objectives.
6-144
E-Learning Module Structure
ROUTE v1. 06-7
Utilizing a combination of lecture sessions, animated content, lab demonstrations, and assessments, each e-learning module presents a hierarchical structure of lessons and topics. You can navigate through that structure by using an intuitive GUI that includes playback controls, slide selection, and lesson and topic selection. Using these tools, you will be able to navigate the content at your own pace. The three-panel screen presented in the directed demonstrations allows you to focus on the device console demonstrations, while having the command syntax and the topology diagram available for verification and additional information.
6-145
Summary
Summary
The content of the Implementing IPv6 e-learning module was described. The content of the Implementing Routing Facilities for Branch Offices and Mobile Workers e-learning module was described. The structure and process of accessing and using e-Learning content was reviewed.
ROUTE v1. 06-8
6-146
Module Summary
Module Summary
BGP is a path-vector routing protocol that allows routing policy decisions at the AS level to be enforced. BGP is a policy-based routing protocol and controls traffic flow using multiple BGP path attributes. BGP forms EBGP relationships with external neighbors and IBGP with internal neighbors. All routers in the transit path within an AS must run fully meshed IBGP. When BGP is properly configured, it will establish a neighbor relationship and announce the networks with a next-hop and source IP address to other BGP routers. BGP performs a multistep process when selecting the best path to reach a destination. BGP can manipulate path selection to affect the inbound and outbound traffic policies of an AS using route maps and BGP attributes.
The Internet has proven to be a valuable tool to many companies, resulting in multiple redundant connections to many different Internet service providers (ISPs). The function of Border Gateway Protocol (BGP) is to provide alternatives to using default routes to control path selections.
References
For additional information, refer to these resources: RFCs 1772, 1773, 1774, 1930, 1966, 1997, 1998, 2042, 2385, 2439, 2545, 2547, 2796, 2858, 2918, 3065, 3107, 3392, 4223, and 4271. RFC 1518, An Architecture for IP Address Allocation with CIDR. RFC 1519, Classless Inter-Domain Routing (CIDR): An Address Assignment and Aggregation Strategy. RFC 2050, Internet Registry IP Allocation Guidelines.
6-147
6-148
Module Self-Check
Use the questions here to review what you learned in this module. The correct answers and solutions are found in the Module Self-Check Answer Key. Q1) Which type of connectivity is typically expected to and from an enterprise network? (Source: Planning the Enterprise-to-ISP Connection) A) B) C) D) Q2) one-way two-way unidirectional connectivity from the clients to the Internet
What is not a requirement of enterprise network-to-ISP connectivity? (Source: Planning the Enterprise-to-ISP Connection) A) B) C) D) public IP address space link type and bandwidth availability AS routing policy connection redundancy
Q3)
List five routing update exchange options for enterprise network-to-ISP connectivity. (Source: Planning the Enterprise-to-ISP Connection) ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________
Q4)
Which one of these statements is not the reason for using BGP as a routing update exchange mechanism? (Source: Planning the Enterprise-to-ISP Connection) A) B) C) D) A customer deploys BGP to announce its public networks. A BGP is typically used for inter-AS routing. Customer routers are connected to SPs PE routers. Customer network implementation requires a complete Internet routing table.
Q5)
What are four enterprise network-to-ISP connection options? (Source: Planning the Enterprise-to-ISP Connection) ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________
Q6)
Which is a characteristic of dual-multihomed ISP connectivity? (Source: Planning the Enterprise-to-ISP Connection) A) B) C) D) a connection to two or more different ISPs with two links per ISP a connection to multiple ISPs with one link per ISP the default route points to each ISP from an enterprise network each ISP announces a default route with a different metric to the enterprise network
6-149
Q7)
What are three common ways to perform multihoming? (Choose three.) (Source: Planning the Enterprise-to-ISP Connection) A) B) C) D) Each ISP passes only a default route to the AS. Each ISP passes a default route and provider-owned specific routes to the AS. Each ISP passes selected provider-owned routes but no default routes to the AS. Each ISP passes all routes to the AS.
Q8)
Which statement is true about the autonomous system (AS)? (Source: Considering the Advantages of Using BGP) A) B) C) D) The AS is a collection of networks under single administrative domain. The AS is a collection of networks that belong to one enterprise network. The AS requires IGP protocol to exchange routing information between autonomous systems. EBGP neighbors must be configured within the same AS.
Q9)
What are the two typical reasons for multihoming? (Choose two.) (Source: Considering the Advantages of Using BGP) A) B) C) D) To increase the reliability of the connection to the Internet. To increase the performance of the connection. To increase the bandwidth of the connection. To simplify the IGP protocol configuration.
Q10)
What is a drawback of having all of your connections to a single ISP? (Source: Considering the Advantages of Using BGP) A) B) C) D) It has redundancy with the multiple connections. Connectivity issues in that single ISP can cause your autonomous system to lose connectivity to the Internet. It is not tied into the routing policy of a single connection. It has more paths to the same networks for better policy manipulation.
Q11)
An enterprise network is configured as a multihoming network and only receives a default route from each ISP. (Source: Considering the Advantages of Using BGP) A) B) true false
Q12)
Which two conditions are valid reasons to run BGP in an AS? (Choose two.) (Source: Considering the Advantages of Using BGP) A) B) C) D) The AS has only a single connection to another AS. Path and packet flow manipulation is required in this AS. You have a limited understanding of BGP routing and route filtering. The AS is an ISP.
Q13)
Which routing method best describes BGP? (Source: Considering the Advantages of Using BGP) A) B) C) D) distance vector link-state path-vector hybrid of link-state and distance vector
6-150
Q14)
Which protocol does BGP use? (Source: Considering the Advantages of Using BGP) A) B) C) D) IP protocol number 88 IP protocol number 89 UDP port 520 TCP port 179
Q15)
Which four message types are defined by BGP? (Source: Considering the Advantages of Using BGP) ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________
Q16)
Which two terms refer to routers that are configured to exchange BGP information with one another? (Choose two.) (Source: Comparing the Functions and Uses of EBGP and IBGP) A) B) C) D) BGP peer BGP speaker BGP router BGP neighbor
Q17)
By default, what are two conditions for routers to be EBGP neighbors? (Choose two.) (Source: Comparing the Functions and Uses of EBGP and IBGP) A) B) C) D) routers must be in the same AS routers must be in different autonomous systems routers are running an IGP between them to establish an adjacency routers are directly connected
Q18)
What are three ways to form an adjacency between IBGP neighbors by default? (Choose three.) (Source: Comparing the Functions and Uses of EBGP and IBGP) A) B) C) D) The neighbors can be directly connected. The neighbors can be reachable from one another by static routes. The neighbors can be reachable from one another by a dynamic internal routing protocol. The neighbors can be in different autonomous systems.
Q19)
Which statement about IBGP is true? (Source: Comparing the Functions and Uses of EBGP and IBGP) A) B) C) D) Routes learned via IBGP are never sent to EBGP peers. All the routers between IBGP neighbors must not be running IGP instead of BGP. Routes learned via IBGP are never propagated to other IBGP peers. Routes are never learned via IBGP.
6-151
Q20)
Test your understanding of BGP terminology by matching statements with terms. Write the letter of the statement in front of the term that the statement describes. A statement can describe more than one term. Each term can match multiple statements, but choose only the statement that best describes the term. (Source: Explaining EBGP and IBGP) Statement: A) B) C) D) Term: _____ 1. _____ 2. _____ 3. _____ 4. IBGP neighbors BGP neighbors EBGP neighbors BGP routers These routers never advertise BGP routing information to IBGP neighbors. This is a set of BGP routers that are explicitly configured to exchange BGP information. This is a set of BGP routers that have a neighbor relationship with BGP routers in the same and different autonomous systems. This is a set of BGP routers that, by default, must be directly connected and must be in different autonomous systems.
Q21)
What does BGP use during the best path selection process? (Source: Explaining EBGP and IBGP) A) B) C) D) speed AS routing policy bandwidth plus delay number of routers to reach a destination network
Q22)
Which parameters are required for a basic BGP configuration? (Source: Configuring and Verifying Basic BGP Operations) ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________
Q23)
Which command indicates to a BGP router whether an IP address belongs to an IBGP or an EBGP neighbor? (Source: Configuring and Verifying Basic BGP Operations) A) B) C) D) neighbor 10.1.1.1 shutdown neighbor 10.1.1.1 update-source Loopback0 neighbor 10.1.1.1 remote-as 65010 neighbor 10.1.1.1 next-hop-self
Q24)
Which command sets the source IP address of a BGP update to be the IP address of a specific interface? (Source: Configuring and Verifying Basic BGP Operations) A) B) C) D) neighbor 10.2.2.2 shutdown neighbor 10.2.2.2 update-source Loopback0 neighbor 10.2.2.2 remote-as 65020 neighbor 10.2.2.2 next-hop-self
6-152
Q25)
What is the result of using this command: router bgp 65010? (Source: Configuring and Verifying Basic BGP Operations) A) B) C) D) The BGP process starts in the router. The BGP process starts on the interface. The neighboring router AS is defined. The router enters into BGP configuration mode with AS number 65010 used locally.
Q26)
The network command that is used in the router BGP process identifies the interfaces from which to advertise BGP updates. (Source: Configuring and Verifying Basic BGP Operations) A) B) true false
Q27)
What is the result of using this command: neighbor 10.3.3.3 shutdown? (Source: Configuring and Verifying Basic BGP Operations) A) B) C) D) BGP neighbor 10.3.3.3 is administratively disabled. It prevents BGP neighbor 10.3.3.3 from receiving BGP updates. The BGP process on the neighbor 10.3.3.3 is disabled. The command also requires the AS number in order to shut down the neighbor.
Q28)
Which command must be used if an EBGP neighbor is not directly connected? (Source: Configuring and Verifying Basic BGP Operations) A) B) C) D) neighbor 10.4.4.4 ebgp-multihop neighbor 10.4.4.4 update-source Loopback0 neighbor 10.4.4.4 remote-as 65020 neighbor 10.4.4.4 next-hop-self
Q29)
What are two benefits of using BGP peer groups? (Choose two.) (Source: Configuring and Verifying Basic BGP Operations) A) B) C) D) Peer groups simplify the BGP configuration. Peer groups make BGP updates more efficient. Peer groups are able to find a more optimal way out of the AS. Peer groups change BGP attributes for more BGP neighbors at a time.
Q30)
What states does BGP go through during the establishment of a BGP session? (Source: Configuring and Verifying Basic BGP Operations) ________________________________________________________________ ________________________________________________________________ ________________________________________________________________
Q31)
Which state indicates that the router does not have a path to the neighbor IP address? (Source: Configuring and Verifying Basic BGP Operations) A) B) C) D) active idle established open confirm
6-153
Q32)
If you configure or change the password or key used for MD5 authentication between two BGP peers, the local router will not tear down the existing session after you configure the password. (Source: Configuring and Verifying Basic BGP Operations) A) B) true false
Q33)
Which clear ip bgp command is the least intrusive for resetting a BGP session after changing outbound policy for neighbor 10.5.5.5? (Source: Configuring and Verifying Basic BGP Operations) A) B) C) D) clear ip bgp * clear ip bgp 10.5.5.5 soft out clear ip bgp 10.5.5.5 clear ip bgp 10.5.5.5 soft in
Q34)
Place the BGP selection criteria in order from the first step to the last step evaluated to select the BGP path that is submitted to the IP routing table. (Source: Selecting an Outbound EBGP Path) A) B) C) D) E) F) G) H) I) J) K) _____ prefer the path with the lowest neighbor BGP router ID _____ prefer the lowest MED _____ prefer the shortest AS path _____ prefer the oldest route for EBGP paths _____ prefer the lowest origin code (IGP < EGP < incomplete) _____ prefer the highest weight _____ prefer the path through the closest IGP neighbor _____ prefer the highest local preference _____ prefer the route that was originated by the local router _____ prefer an EBGP path over IBGP path _____ prefer the lowest neighbor IP address
Q35)
Which description applies to the AS path attribute? (Source: Selecting an Outbound EBGP Path) A) B) C) D) well-known mandatory well-known discretionary optional transitive optional nontransitive
Q36)
Which description applies to the next-hop attribute? (Source: Selecting an Outbound EBGP Path) A) B) C) D) well-known mandatory well-known discretionary optional transitive optional nontransitive
Q37)
Which description applies to the origin attribute? (Source: Selecting an Outbound EBGP Path) A) B) C) D) well-known mandatory well-known discretionary optional transitive optional nontransitive
6-154
Q38)
Which description applies to the local preference attribute? (Source: Selecting an Outbound EBGP Path) A) B) C) D) well-known mandatory well-known discretionary optional transitive optional nontransitive
Q39)
Which description applies to the MED attribute? (Source: Selecting an Outbound EBGP Path) A) B) C) D) well-known mandatory well-known discretionary optional transitive optional nontransitive
Q40)
Which description applies to the weight attribute? (Source: Selecting an Outbound EBGP Path) A) B) C) D) well-known mandatory well-known discretionary optional transitive proprietary to Cisco and not advertised to other BGP routers
Q41)
Which two statements are true regarding local preference? (Choose two.) (Source: Selecting an Outbound EBGP Path) A) B) C) D) The higher value for local preference is preferred. Local preference is used only between EBGP neighbors. The lower value for local preference is preferred. Local preference is used only between IBGP neighbors.
Q42)
Which two statements are true regarding weight? (Choose two.) (Source: Selecting an Outbound EBGP Path) A) B) C) D) The lower value for weight is preferred. The higher value for weight is preferred. Weight is used only between IBGP neighbors. Weight is used only locally inside the router.
Q43)
Which two statements are true regarding the MED? (Choose two.) (Source: Manipulating Inbound EBGP Paths Selection) A) B) C) D) The higher value for the MED is preferred. The lower value for the MED is preferred. The MED is exchanged between autonomous systems. The MED is local to an AS.
Q44)
Which two statements are true regarding the AS Path? (Choose two.) (Manipulating Inbound EBGP Paths Selection) A) B) C) D) The shorter AS path is preferred. The longer AS path is preferred. The AS path is prepended and exchanged between autonomous systems. The AS path is local to an AS.
6-155
Q45)
Which command changes the MED for all routes? (Source: Manipulating Inbound EBGP Paths Selection) A) B) C) D) bgp med number default-metric number bgp default-metric number set med number
Q46)
The MED is used to decide how to enter an AS from neighboring autonomous systems, when multiple paths exist between two autonomous systems. (Source: Manipulating Inbound EBGP Paths Selection) A) B) true false
Q47)
The MED is set inbound when a router is receiving router updates from an EBGP neighbor. (Source: Manipulating Inbound EBGP Paths Selection) A) B) true false
Q48)
The length of the AS path is extended because additional copies of the AS number of the sender are prepended to the original AS path attribute. To avoid clashes with BGP loop prevention mechanisms, no other AS number, except that of the neighboring AS, should be prepended to the AS path attribute. (Source: Manipulating Inbound EBGP Paths selection) A) B) true false
6-156

Q1) Q2) Q3) Q4) Q5) Q6) Q7) Q8) Q9) Q10) Q11) Q12) Q13) Q14) Q15) Q16) Q17) Q18) Q19) Q20) B C Static routes, Common IGP, MPLS VPNs, Circuit Emulation, BGP C Single-homed, Dual-homed, Multihomed, Dual-multihomed A A, B, D A A, B B A B, D C D Open, Keepalive, Update, Notification A, D B, D A, B, C C 1-A 2-C 3-D 4-B B neighbors (peers) involved, AS numbers used, IP Addresses used and Networks, which need to be advertised C B D B A A A, B Idle, Connect, Open sent, Open confirm, Established B A
Q21) Q22)
Q23) Q24) Q25) Q26) Q27) Q28) Q29) Q30) Q31) Q32)
6-157
Q33) Q34)
B 1-F 2-H 3-I 4-C 5-E 6-B 7-J 8-G 9-D 10-A 11-K A A A B D D A, D B, D B, C A, C B A B B
Q35) Q36) Q37) Q38) Q39) Q40) Q41) Q42) Q43) Q44) Q45) Q46) Q47) Q48)
6-158
ROUTE

Version 1.0
Lab Guide
Lab Guide
Table of Contents
Lab Guide 1
Overview 1 Outline 1 Lab 1-1: Assess Skills for Implementing Complex Networks 3 Activity Objective 3 Information Packet 3 Implementation Policy 4 Device Information 5 Required Resources 5 Job Aids 6 Task 1: Identify the Network Requirements 7 Task 2: Identify and Gather the Required Information 8 Task 3: Create an Implementation and Verification Plan 10 Alternate Resources and Solutions 12 Hints 13 Lab 1-1 Hint Sheet: Assess Skills for Implementing Complex Networks 13 Lab 2-1: Configure and Verify EIGRP Operations 19 Activity Objective 19 Information Packet 19 Implementation Policy 20 Device Information 21 Command List 22 Required Resources 22 Job Aids 23 Task 1: Establish an Implementation Requirements List 25 Task 2: Create an Implementation and Verification Plan 26 Task 3: Implement and Verify 28 Alternate Resources and Solutions 30 Hints 33 Lab 2-1 Hint Sheet: Configure and Verify EIGRP Operations 33 Lab 2-2: Configure and Verify EIGRP Circuit Emulation and Frame Relay Operations 47 Activity Objective 47 Information Packet 47 Implementation Policy 48 Device Information 49 Command List 50 Required Resources 50 Job Aids 51 Task 1: Establish an Implementation Requirements List 53 Task 2: Create an Implementation and Verification Plan 54 Task 3: Implement and Verify 56 Alternate Resources and Solutions 58 Hints 61 Lab 2-2 Hint Sheet: Configure and Verify EIGRP Circuit Emulation and Frame Relay Operations 61 Lab 2-3: Configure and Verify EIGRP Authentication 80 Activity Objective 80 Information Packet 80 Implementation Policy 81 Device Information 81 Command List 82 Required Resources 82 Job Aids 82 Task 1: Establish an Implementation Requirements List 83 Task 2: Create an Implementation and Verification Plan 84 Task 3: Implement and Verify 86 Alternate Resources and Solutions 88
Hints 91 Lab 2-3 Hint Sheet: Configure and Verify EIGRP Authentication 91 Lab 2-4: Implement and Troubleshoot EIGRP Operations 100 Activity Objective 100 Information Packet 100 Troubleshooting Policy 100 Device Information 101 Command List 102 Required Resources 102 Job Aids 103 Task 1: Create an Troubleshooting and Verification Plan 104 Task 2: Troubleshooting Log 106 Hints 108 Lab 2-4 Hint Sheet: Implement and Troubleshoot EIGRP Operations 108 Lab 3-1: Configure and Verify OSPF to Improve Routing Performance 112 Activity Objective 112 Information Packet 112 Implementation Policy 113 Device Information 114 Command List 114 Required Resources 115 Job Aids 115 Task 1: Establish an Implementation Requirements List 116 Task 2: Create an Implementation and Verification Plan 117 Task 3: Implement and Verify 119 Alternate Resources and Solutions 121 Hints 124 Lab 3-1 Hint Sheet: Configure and Verify OSPF to Improve Routing Performance 124 Lab 3-2: Implement and Verify OSPF Multiarea Routing 137 Activity Objective 137 Information Packet 137 Implementation Policy 138 Device Information 139 Command List 139 Required Resources 140 Job Aids 140 Task 1: Establish an Implementation Requirements List 141 Task 2: Create an Implementation and Verification Plan 143 Task 3: Implement and Verify 145 Alternate Resources and Solutions 147 Hints 149 Lab 3-2 Hint Sheet: Implement and Verify OSPF Multiarea Routing 149 Lab 3-3: Configure and Verify OSPF Route Summarization for Interarea and External Routes 164 Activity Objective 164 Information Packet 164 Implementation Policy 165 Device Information 166 Command List 166 Required Resources 166 Job Aids 167 Task 1: Establish an Implementation Requirements List 168 Task 2: Create an Implementation and Verification Plan 170 Task 3: Implement and Verify 172 Alternate Resources and Solutions 174 Hints 176 Lab 3-3 Hint Sheet: Configure and Verify OSPF Route Summarization for Interarea and External Routes 176
ii
Lab 3-4: Configure and Verify OSPF Special Area Types 190 Activity Objective 190 Information Packet 190 Implementation Policy 191 Device Information 192 Command List 193 Required Resources 193 Job Aids 193 Task 1: Establish an Implementation Requirements List 194 Task 2: Create an Implementation and Verification Plan 196 Task 3: Implement and Verify 198 Alternate Resources and Solutions 200 Hints 202 Lab 3-4 Hint Sheet: Configure and Verify OSPF Special Area Types 202 Lab 3-5: Configure and Verify OSPF Authentication 220 Activity Objective 220 Information Packet 220 Implementation Policy 221 Device Information 221 Command List 222 Required Resources 222 Job Aids 222 Task 1: Establish an Implementation Requirements List 223 Task 2: Create an Implementation and Verification Plan 225 Task 3: Implement and Verify 227 Alternate Resources and Solutions 229 Hints 231 Lab 3-5 Hint Sheet: Configure and Verify OSPF Authentication 231 Lab 4-1: Configure Route Redistribution Between Multiple IP Routing Protocols 246 Activity Objective 246 Information Packet 246 Implementation Policy 247 Device Information 248 Command List 249 Required Resources 250 Job Aids 250 ------- The page intentionally left blank. --------Task 1: Establish an Implementation Requirements List 251 Task 1: Establish an Implementation Requirements List 252 Task 2: Create an Implementation and Verification Plan 254 Task 3: Implement and Verify 256 Alternate Resources and Solutions 257 Hints 258 Lab 4-1 Hint Sheet: Configure Route Redistribution Between Multiple IP Routing Protocols 258 Lab 5-1: Configure and Verify Path Control Between Multiple IP Routing Protocols 271 Activity Objective 271 Information Packet 271 Implementation Policy 272 Device Information 272 Command List 273 Required Resources 273 Job Aids 273 Task 1: Establish an Implementation Requirements List 275 Task 2: Create an Implementation and Verification Plan 277 Task 3: Implement and Verify 279 Alternate Resources and Solutions 281 Hints 283 Lab 5-1 Hint Sheet: Configure and Verify Path Control Between Multiple IP Routing Protocols283
iii
Lab 6-1: Configure BGP Operations 291 Activity Objective 291 Information Packet 291 Implementation Policy 292 Device Information 292 Command List 293 Required Resources 293 Job Aids 294 Task 1: Establish an Implementation Requirements List 295 Task 2: Create an Implementation and Verification Plan 297 Task 3: Implement and Verify 299 Alternate Resources and Solutions 301 Hints 303 Lab 6-1 Hint Sheet: Configure BGP Operations 303 Lab 6-2: Manipulate EBGP Path Selections 317 Activity Objective 317 Information Packet 317 Implementation Policy 317 Device Information 318 Command List 319 Required Resources 319 Job Aids 319 Task 1: Establish an Implementation Requirements List 321 Task 2: Create an Implementation and Verification Plan 322 Task 3: Implement and Verify 323 Alternate Resources and Solutions 325 Hints 327 Lab 6-2 Hint Sheet: Manipulate EBGP Path Selections 327 Answer Key 339 Lab 1-1 Answer Key: Assess Skills for Implementing Complex Networks 339 Lab 2-1 Answer Key: Configure and Verify EIGRP Operations 339 Lab 2-2 Answer Key: Configure and Verify EIGRP Circuit Emulation and Frame Relay Operations 344 Lab 2-3 Answer Key: Configure and Verify EIGRP Authentication 349 Lab 2-4 Answer Key: Implement and Troubleshoot EIGRP Operations 355 Lab 3-1 Answer Key: Configure and Verify OSPF to Improve Routing Performance 360 Lab 3-2 Answer Key: Implement and Verify OSPF Multiarea Routing 366 Lab 3-3 Answer Key: Configure and Verify OSPF Route Summarization for Interarea and External Routes 371 Lab 3-4 Answer Key: Configure and Verify OSPF Special Area Types 377 Lab 3-5 Answer Key: Configure and Verify OSPF Authentication 383 Lab 4-1 Answer Key: Configure Route Redistribution Between Multiple IP Routing Protocols 388 Lab 5-1 Answer Key: Configure and Verify Path Control Between Multiple IP Routing Protocols 394 Lab 6-1 Answer Key: Configure BGP Operations 400 Lab 6-2 Answer Key: Manipulate EBGP Path Selections 405
iv
ROUTE
Lab Guide
Overview
This guide presents the instructions and other information concerning the lab activities for the Implementing Cisco IP Routing (ROUTE) v1.0 course. You can find the solutions in the lab activity Answer Key.
Outline
This guide includes these activities: Lab 1-1: Assess Skills for Implementing Complex Networks Lab Hints
Lab 2-1: Configure and Verify EIGRP Operations Lab Hints
Lab 2-2: Configure and Verify EIGRP Circuit Emulation and Frame Relay Operations Lab Hints
Lab 2-3: Configure and Verify EIGRP Authentication Lab Hints
Lab 2-4: Implement and Troubleshoot EIGRP Operations Lab Hints
Lab 3-1: Configure and Verify OSPF to Improve Routing Performance Lab Hints
Lab 3-2: Implement and Verify OSPF Multiarea Routing Lab Hints
Lab 3-3: Configure and Verify OSPF Route Summarization for Interarea and External Routes Lab Hints
Lab 3-4: Configure and Verify OSPF Special Area Types Lab Hints
Lab 3-5: Configure and Verify OSPF Authentication Lab Hints
Lab 4-1: Configure Route Redistribution Between Multiple IP Routing Protocols Lab Hints
Lab 5-1: Configure and Verify Path Control Between Multiple IP Routing Protocols Lab Hints
Lab 6-1: Configure BGP Operations Lab Hints
Lab 6-2: Manipulate EBGP Path Selections Lab Hints
Answer Key
Lab 1-1: Assess Skills for Implementing Complex Networks

Complete this lab activity to confirm and refresh your Layer 2 and Layer 3 skills from Interconnecting Cisco Networking Devices Part 2 (ICND2).
Activity Objective
In this activity, you will put together a network implementation plan for an complex enterprise network. This lab activity is designed to reinforce the skills necessary to build a network implementation plan for complex networks. You will need to identify network requirements, acquire required information, and create a network implementation plan for one part of the complex enterprise network. One campus network will be implemented. After completing this activity, you will be able to meet these objectives: Identify the requirements the network has to provide Identify the required information Identify the tasks necessary for the implementation and create an implementation plan Verify the activity
Information Packet
The figures illustrate what you will accomplish in this activity.
Visual Objective
Visual Objective for Lab 1-1: Assess Skills for Implementing Complex Networks
ROUTE v1.0LG-4
Lab Guide
Visual Objective for Lab 1-1: Campus Network To Be Implemented
ROUTE v1.0LG-5
Implementation Policy
You were hired by No-route, Inc. to implement their Layer 3 enterprise network. They provided you with a cabling plan and asked you to help them implement routing in their network. As you were collecting information about their network infrastructure, they provided the following diagrams and list of equipment. The first figure in the Visual Objective diagrams represents an enterprise network. The second figure represents network at No-route, Inc., which is simplified in order to create the implementation plan as part of Lab 1-1. Their infrastructure includes these submodules: Access Distribution Backbone The equipment is not installed yet. At the beginning typical requirements for a network must be identified. A quick call to the local administrator results in identification of the following requirements: Functionality: The enterprise network must support the applications and data flows required within the required time frames. Performance: Performance includes three primary metrics: responsiveness, throughput (volume), and utilization. Scalability: Networks must provide scalability for future growth including new users and the amount of data and applications that the network must support.
Availability: Nearly 100 percent availability is required for most enterprise data networks. (Critical applications may be required to meet a standard of availability approaching 99.999 percent [five nines]). Manageability: A network must be manageable across the entire infrastructure. Cost-effectiveness: Cost-effectiveness is a key concern for most enterprises, given limited budgets. Based on the important parameters above, determine what network information must be identified. The detailed requirements for the implementation plan to employ routing in a customer network must be collected. Collect all of the required parameters in order to correctly implement the network. All of the details needed for the configuration must be provided by the customer. When all details are defined and documented, you can plan the implementation and create the implementation plan, which describes the steps required to implement routing in the customer network. Planning means deciding on a starting point and determining the progression of steps necessary to configure the network and make it operational. Spend some time discussing the best course of action with your pod partner to allow for the most efficient way of configuring the network.
Device Information
The table provides the information specific to each switch in the network:
Device name R1 R2 R3 R4 SW1 BBR1 BBR2 Role POD router POD router POD router POD router POD switch Backbone router Backbone router IP address Gateway VLAN
Required Resources
These are the resources and equipment that are required to complete this activity: A PC that is connected to an on-site laboratory or a PC with an Internet connection if remote laboratory equipment must be accessed A terminal server that is connected to the console port of each laboratory device, if using a remote laboratory Core and access switches in your pod
Lab Guide
Job Aids
These are the job aids for this lab activity:
Value Blank network device requirements list Blank implementation requirements list Blank implementation and verification plan form Debrief alternate solutions form Implementation requirement hints Implementation hints Verification hints Location Task 1 Task 2 Task 3 End of this lab Hints section at the end of this lab Hints section at the end of this lab Hints section at the end of this lab
Task 1: Identify the Network Requirements

The first step in your configuration deployment is to identify the requirements of each device according to the customer network requirements.. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
Device Implementation Requirement
Lab Guide
Task 2: Identify and Gather the Required Information

The second step in your configuration deployment is to gather and document all the detailed information that will be used to create an implementation and verification plan. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
Complete Device Implementation Order Values and Items to Implement
Complete
Device
Implementation Order
Values and Items to Implement
Lab Guide
Task 3: Create an Implementation and Verification Plan

The beginning of any successful implementation is the creation of the implementation and verification plan. Create a list of steps needed to implement and verify the routing in the customer network. For the purpose of Lab 1-1, there is no need to use configuration commands. The implementation plan should define the general steps required to implement and verify routing in the customer network. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
Complete Device Feature Verification Method and Expected Results
10
Complete
Device
Feature
Verification Method and Expected Results
Lab Guide
11
Alternate Resources and Solutions

Other groups may have implemented a solution that is different from yours. These will be discussed during the debriefing period that will follow this lab. Use the following space to document other possible solutions for your reference. __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
12 Implementing Cisco IP Routing (ROUTE) v1.0 2009 Cisco Systems, Inc.
Hints
You are encouraged to complete the labs using your knowledge. However, this section contains a series of hints to aid your completion of the lab.
Lab 1-1 Hint Sheet: Assess Skills for Implementing Complex Networks
Identify the Requirements the Network Must Provide To facilitate the configuration of your network, the first task asks you to identify the requirements of the networkthe things that the network must provide according to the customer specifications. This list details the elements you need in order to develop an implementation plan. The following is an example of such a list:
No. 1. 2. 3. 4. 5. 6. Implementation Requirement Application and data requirements Existing equipment and software version Existing topology (logical and physical) IP addressing plan Select routing protocols Scalability configuration (summarization, stub areas, and so on)
Implementation Requirements The second task asks you to create an implementation requirements list. This list details the elements you need in order to develop an implementation plan. The following is an example of such a list with details: Application and data requirements
Lab Guide
13
Name of Application
Building or Location
Type of Application
Number of Users
Number of Servers
Bandwidth/ Delay Tolerance/ Loss Characteristics High bandwidth High delay tolerance Low loss
Marketing DSS
Building 1
Database (OLAP)
137
Corporate email
Building 2
Email
65
Low bandwidth Low delay tolerance Low loss
File server
Building 3
File sharing (FTP)
48
Low bandwidth Medium delay tolerance Low loss
Existing equipment and software version

Device CLT1 CLT2 SW1 R1 R2 R3 R4 BBR1 BBR2 Role Client station Client station Access switch Distribution router Distribution router Distribution router Distribution router Core router Core router Software Version Mac OS Windows OS Advanced IP service 12.2-46 Advanced IP service 12.4(10) Advanced IP service 12.4(10) Advanced IP service 12.4(10) Advanced IP service 12.4(10) Advanced IP service 12.4(10) Advanced IP service 12.4(10)
Existing topology (logical and physical)
14
Visual Objective for Lab 1-1: Physical Topology
ROUTE v1.0LG-6
IP addressing plan
Link R1 to R2 R1 LAN, R3 LAN R3 to R4 R2 AN, R4 LAN R1 to BBR1 R2 to BBR2 Network 10.1.112.0/24 172.30.13.0/24 10.1.134.0/24 172.30.24.0/24 10.1.115.0/24 10.1.116.0/24
Select routing protocols EIGRP is selected as the interior gateway protocol because the following network characteristics are required for the customer: supports large network size, has very high speed of convergence, and supports VLSM. BGP is selected as the exterior gateway protocol because complex enterprise networks support redundant connectivity to ISPs and the customer has its own public IP addresses and public BGP autonomus system number. Scalability configuration (summarization, stub areas, and so on ) The network design uses IP addressing, which supports summarization on every distribution router. Some branch offices are configured as stub networks. The default route is sent inside the stub network and only summary IP addresses are propagated outside of the stub network.
Lab Guide
15
Implementation Plan In Task 3 you need to create an implementation and verification plan and document the plan. There are several possible ways to accomplish this task. One possible way is to group items that are common to all devices in a template, and then apply this template to all of the devices. You can then configure each device with items that are unique to each device, such as IP addresses or gateway. The implementation steps are specified in the following list: Document network information. Prepare the required resources. Connect the PC to the equipment. Select specific tools and equipment. Select and reserve resources (project contact list).
Configure the IP addressing on all devices in the network. Enable all of the interfaces. Configure the IP routing protocol where needed. Configure summarization and stub areas. Verify proper operation of IP routing protocol; check the connectivity in the network. Measure the performance and document the results. Create a backup of the configuration. Document the implementation plan, baseline, performance, and recommendations. Verification Plan
Complete Device Feature Verification Method and Expected Results Hint
ALL ALL
All Interfaces must be enabled. Configuration of the routing protocol must be done and the verification must prove that the routing protocol is running. Required networks must be advertised. Summary route to Null0 must appear on every customer edge router. Preferred path must be selected by the routing protocol.
ALL R1, R2
ALL
16
Complete
Device
Feature
Hint
Lab Guide
17
-------- This page intentionally left blank. --------
18
Lab 2-1: Configure and Verify EIGRP Operations

Complete this lab activity to practice what you learned in the related module.
Activity Objective
In this activity, you will use correct commands, tools, and steps to configure and verify a basic EIGRP implementation. After completing this activity, you will be able to meet these objectives: Configure and verify basic EIGRP operation over WAN and LAN interfaces Select the required tools and commands to configure basic EIGRP operations Configure EIGRP on the LAN interfaces using a secondary IP address on one router Influence the path selection for EIGRP by changing the metric Optimize EIGRP operation to prevent unnecessary hellos from being sent Optimize EIGRP operation by minimizing the routing table size using summarization Make a list of the configuration and implementation steps Write a verification and test plan to verify the proper implementation and operation according to the expected performance criteria Verify the configuration and operation by using the proper show and debug commands
Information Packet
The figure illustrates what you will accomplish in this activity.
Visual Objective
Visual Objective for Lab 2-1: Configure and Verify Basic EIGRP Operations
ROUTE v1.0LG-7
Lab Guide
19
The following lists the detailed configuration requirements for all devices in the company network: Set the proper initial configuration on all devices in your lab. The instructor will provide the necessary information on how to set the initial configuration on all devices. First, a basic EIGRP configuration is required on each of the routers in your network routers R1, R2, R3, and R4. The EIGRP will be used to exchange routing information in order to achieve IP connectivity between the subnets deployed on your routers and backbone BBR1 router as well. The EIGRP configuration should be so specific that if an additional network is added to the router, such a network is not automatically advertised. The IP routing tables on all your routers should be populated with all of the specific IP subnets in your network. Automatic summarization must be disabled. Basic EIGRP configuration must be verified in order to see if it meets requirements. Verify that the proper EIGRP adjacencies have been set up between the routers in your pod and between routers R1 and BBR1. Router R1 should have established three adjacencies and routers R2, R3, and R4 should have established two adjacencies. Examine each router and make sure that EIGRP has been set up to advertise the IP subnets present on WAN and LAN interfaces with the correct mask, without examining the IP routing table and EIGRP topology database. Verify the EIGRP topology database and compare it against the EIGRP information that was put into the IP routing table on router R1. You should be able to see that all of the networks acquired via EIGRP were put into the routing table and that the metric related to an individual route corresponds to the value present in the topology table. Examine the EIGRP topology table and IP routing table on router R4 also. Keep in mind that R4 has two paths in the topology and IP routing table for the networks that are external to your pod. If you look at the metric either in the topology table or in the IP routing table for the network 192.168.1.0/24, you can see that the metric is the same for both sources. Therefore there are equal cost paths for the same destination being installed in the routing table. Examine the EIGRP in action: enable EIGRP event debugging on router R4 and disable the interface between routers R1 and R2. When the debug output is observed, you should see EIGRP packets being exchanged, and that for network 10.1.112.0/24 (the one used between R1 and R2), router R4 responds with an infinite metric to an EIGRP query. EIGRP can install multiple equal cost paths into the routing table, which is what happens on router R4. Tis router has two possible paths to the destination networks that are external to your pod. For the metric calculation, EIGRP uses multiple parameters such as delay and bandwidth. In this task, you will influence EIGRP path selection by changing the metric of the routes to eliminate equal cost paths from the router R4 routing table, but still preserve the EIGRP fast convergence in a case of topology change. Verify the path selection process by examining the router R4 EIGRP topology table and verify that two paths still exist for the 192.168.x.0/24 subnets, with the path via router R3 being the secondary option. Verify on the router R4 routing table that only the best path to destination networks 192.168.x.0/24 exists, the path through router R2. Verify that the secondary path through router R3 is put into the routing table of router R4 in case of a primary path failure without an FD change. When a network statement is used under EIGRP, EIGRP not only starts to advertise that subnet but also tries to form an adjacency through that interface. EIGRP does so by sending hello packets. Sometimes this is not desired; thus, the adjacency formation should be prevented by suppressing the hello packets. Disable the unnecessary EIGRP adjacencies to preserve the interface bandwidth and the CPU resources of the router. The configuration will be added to routers R1 and R3.
20
Verify that you have disabled EIGRP between routers R1 and R3 on the LAN segment and that hello packets are suppressed and not being sent over the LAN interface on routers R1 and R3. An EIGRP adjacency between routers R1 and R3 over the LAN interface must not be present. At the same time, the IP routing table on router R4 still has information on how to access the network 172.30.13.0/24 used on the LAN interface between routers R1 and R3. As a last step, you must enable the EIGRP route summarization for the networks external to your pod, that is, the 192.168.x.0/24 networks. This configuration will add to the stability and speed of the convergence for the network by controlling the scope of queries, minimizing update traffic, and minimizing routing table size. Verify that manual route summarization for subnets 192.168.x.0/24 is applied on router R1, the more specific 192.168.x.0/24 subnets, and the 192.168.0.0/16 summary route pointing to the Null0 interface in the router R1 routing table. Routing tables on routers R2, R3, and R4 must have a summary route 192.168.0.0/16 and no specific 192.168.x.0/24 subnets. You do not have to apply summarization on the LAN interface because an EIGRP adjacency is disabled there. Keep in mind that you also do not have to enable summarization on Serial0/0/0.2 toward router BBR1 because the subnets are received from router BBR1.
Device Information
The table provides information specific to each switch in the network:
Device Name R1 R2 R3 R4 BBR1 Role POD router POD router POD router POD router Backbone router IP Address Gateway VLAN
Lab Guide
21
Command List
The table describes the commands that are used in this activity.
Command (no) auto-summary (no) shutdown debug ip eigrp delay tens-of-microsec interface type slot/port ip summary-address eigrp asnumber network mask network x.x.x.x passive-interface interface router eigrp as-number show ip eigrp neighbors show ip eigrp topology [prefix] [mask] show ip protocols show ip route [eigrp] undebug all Description Enables (disables) automatic summarization of classless subnets Administratively disables (enables) the interface Enables EIGRP event debugging Specifies the delay on interfaces (used for routing processes) Enters the interface configuration mode Configures manual EIGRP summarization on an interface Enables EIGRP on interfaces belonging to a specified network Disables EIGRP hellos to be sent on an interface Starts an EIGRP routing process with the given AS number Lists the EIGRP neighbors and relevant information on EIGRP neighbor adjacencies Displays the EIGRP topology table (whole, or only per prefix/mask) Shows the information about the configured IP protocols Displays the whole IP routing table or EIGRP routes only Disables debugging on the router
Required Resources
22
Job Aids
Value Blank implementation requirements list Blank implementation and verification plan form Blank verification notes form Alternate resources and solutions form Implementation requirements hints Implementation and verification form hints Implementation and verification hints Solution configuration answer key (step-by-step procedure) Location Task 1 Task 2
Task 3 End of this lab Hints section at the end of this lab Hints section at the end of this lab Hints section at the end of this lab End of the Hints section at the end of this lab
Lab Guide
23
24
Task 1: Establish an Implementation Requirements List

The first step in your configuration deployment is to establish a list of what you need in order to configure each device; for example, device names, trunk encapsulation types, and so on. Use the following table, the visual objective at the beginning of this lab, the implementation policy, and the device information to create your implementation requirements list. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
Lab Guide
25

The second step in your configuration deployment is to establish a task list of the items that must be configured on each device, and in what order. You can use the following table, the visual objective at the beginning of this lab, the implementation policy, and the device information to create your implementation and verification plan. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
Complete Device Order Values and Items to Implement Verification Method and Expected Results
26
Complete
Device
Order
Lab Guide
27
Task 3: Implement and Verify

Now that you have collected all the requirements and planned your implementation, you are ready to connect to the remote lab and implement your solution. Do not forget to save. Once you implement your solution, you need to verify that your configuration is working and fulfills all of the requirements specified by the customer. Keep in mind that once you leave the customer location, a network specialist will verify your configuration. Your ability to implement the solution according to the specifications provided by the customer will determine whether you get the job or not. Use the following area to record your notes and document the verifications you conducted to ensure that your solution is complete. If you are unsure of the verification steps, use the information provided in the Hints section at the end of this lab. Student Notes: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
29

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
31
------- This page intentionally left blank. --------
32
Hints
Lab 2-1 Hint Sheet: Configure and Verify EIGRP Operations

Implementation Requirements To facilitate the configuration of your network, the first task asks you to create an implementation requirements list. This list details the elements you need in order to develop an implementation plan. The following is an example of such a list:
Device ALL Implementation Requirement Define EIGRP AS number used in the lab. Hint Check AS number used in the BBR1 router Visual Objective diagrams Lab
ALL
Define which networks are used in the lab in order to advertise all specific networks. Examine and write down the metric for 192.168.x.0/24 subnets for both possible paths by looking into the EIGRP topology table. Examine and write down the current delay value of the FastEthernet0/0 interfaces. Check for the specific 192.168.x.0/24 subnets in order to apply manual summarization.
R4
R1, R3
Lab
R4
Lab
Lab Guide
33
Implementation and Verification Plan In Task 2, you will create an implementation and verification plan. Although there are several ways to set up this plan, the following tasks must be completed:
Complete Device Order Values and Items to Implement Verification Method and Expected Results Step
R1R4
Load initial configuration
All pod routers must be preloaded with the initial configuration for the lab. Verify that the proper EIGRP adjacencies have been set up between the routers in your pod and between routers R1 and BBR1.
Step 1
R1
Enable EIGRP routing protocol on router R1 on the WAN interfaces Serial 0/0.1, Serial0/0.2, and on the LAN interface FastEthernet0/0. Router BBR1 is preconfigured with EIGRP AS 1. Apply the configuration in a way that EIGRP does not automatically advertise any additional network that is added to the router. Enable EIGRP routing protocol on routers R2, R3, and R4, on the WAN interface Serial 0/0.1, and on the LAN interface FastEthernet0/0. Apply the configuration in a way that EIGRP does not automatically advertise any additional networks that are added to the router.
Step 2
R1R4
Verify that router R1 has established three adjacencies, and routers R2, R3, and R4 have two adjacencies. Also examine how long the adjacencies have been set up and whether there is any problem with neighbor communication, such as routing packets remaining in the queue.
Step 3
R1, R4
Verify on routers R1 and R4 that the EIGRP has been set up to advertise the IP subnets present on the WAN and LAN interfaces with the correct mask without examining the IP routing table and EIGRP topology database.
Step 4
34
Complete
Device
Order
Step
R1
Verify the EIGRP topology database and compare it to the EIGRP information that was put into the IP routing table on router R1. You should be able to see that all networks acquired via EIGRP were put into the routing table and that the metric related to an individual route corresponds to the value present in the topology table.
Step 4
R4
Examine the EIGRP topology table and IP routing table on router R4. Keep in mind that R4 has two paths in the topology and the IP routing table for the networks that are external to your pod. If you look at the metric either in the topology table or in the IP routing table for the network 192.168.1.0/24, you can see that the metric is the same for both sources, thus we have equal cost paths for the same destination being installed in the routing table. Examine the EIGRP in action; that is, enable EIGRP event debugging on router R4 and disable the interface between routers R1 and R2. Observing the debug output, you should see EIGRP packets being exchanged and that for network 10.1.112.0/24 (the one used between R1 and R2), R4 responds with an infinite metric to an EIGRP query.
Step 4
R1, R2, R4
Step 5
Lab Guide
35
Complete
Device
Order
Step
R1, R3, R4
Change the delay parameter on the LAN segment between routers R1 and R3 so that the preferred path to the 192.168.x.0/24 subnets for router R4 is through router R2. Enable the interfaces that were disabled in order to simulate the failure.
Examine the EIGRP topology table for router R4 and verify that two paths still exist for the 192.168.x.0/24 subnets, with the path via R3 being the secondary option. Examine the routing table for router R4 to verify that only the best path to destination networks 192.168.x.0/24 exist, the one through router R2. Verify that the secondary path through router R3 is put into the routing table of router R4 in case of a primary path failure without the FD being changed.
Step 6
R4
The configuration should not prevent router R4 from using the second path in case of a primary path failure; that is, the secondary path should become a successor. Prevent routers R1 and R3 from forming an EIGRP adjacency over the LAN network to preserve the interface bandwidth and CPU resources on the routers. The configuration you apply should prevent the routers from sending EIGRP hello packets over the FastEthernet0/0 interface. You should not apply other types of filtering. Enable the interfaces that were disabled in order to simulate the failure.
Step 7
R1, R3, R4
10
Verify that EIGRP between routers R1 and R3 on the LAN segment is disabled, hello packets are suppressed from being sent over the LAN interface on routers R1 and R3, and the EIGRP adjacency between R1 and R3 over the LAN interface is not present.
Step 8
36
Complete
Device
Order
Step
R4
11
Verify that the IP routing table on router R4 still has the information on how to access the network 172.30.13.0/24, which is used on the LAN interface between routers R1 and R3, and that R4 still knows how to reach the network 172.30.12.0/24 on the LAN segment between routers R1 and R3. Verify that you can see the individual 192.168.x.0/24 networks in the IP routing table on router R4.
Step 8
R1R4
12
Enable manual summarization of the 192.168.x.0/24 networks on router R1 to advertise only 192.168.0.0/16 to the rest of the routers in your pod.
Verify that the routing table on router R1 holds the specific 192.168.x.0/24 subnets and 192.168.0.0/16 summary route pointing to the Null0 interface. Verify that the routing tables on routers R2, R3, and R4 have summary route 192.168.0.0/16 and no specific 192.168.x.0/24 subnets.
Step 9
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide the guidelines for changing the initial configuration. 2. Configure EIGRP on router R1 in your pod. 2.1. Use the following example to configure router R1 in this lab:

2.2. Verify the EIGRP configuration on router R1.

Lab Guide
37
3. Configure EIGRP on routers R2 through R4 in your pod. 3.1. Use the following example to configure the routers in this lab:

3.2. Verify the EIGRP adjacencies on your pod router.

4. Verify that the EIGRP topology and IP routing table appear on the routers in your pod.


2009 Cisco Systems, Inc. Lab Guide 39


5. Examine the EIGRP in action on router R4 in your pod. Simulate a WAN failure:
Note In order to simulate a WAN failure, you can shut down the interface between routers R1 and R2 on router R1. There are also other ways to simulate a WAN failure.
5.2. Examine the results after the WAN failure:

42
6. Configure EIGRP path selection. 6.1. Use the following example to configure the routers in this lab:
Note Interfaces, which were disabled in order to simulate WAN failure, are now enabled.
Lab Guide
43
6.2. Verify the configuration on router R4.

7. Examine EIGRP in action on router R4 in your pod. 7.1 Simulate a WAN failure:
Note In order to simulate WAN failure, you can shut down the interface between routers R1 and R2 on router R1. There are also other ways to simulate a WAN failure.
44
7.2 Examination after a WAN failure:

8. Configure EIGRP optimization on the LAN interface. 8.1. Use the following example to configure the routers in this lab:
8.2. Verify the EIGRP adjacencies and configuration the routers in your pod.

Lab Guide
45
9. Configure an EIGRP summarization. 9.1. Use the following example to configure router R1 in this lab:

9.2. Verify the IP routing table on the routers in your pod.

46
Lab 2-2: Configure and Verify EIGRP Circuit Emulation and Frame Relay Operations
Complete this lab activity to confirm and refresh your Layer 2 and Layer 3 skills from Interconnecting Cisco Networking Devices Part 2 (ICND2).
Activity Objective
In this activity, you will use the correct commands, tools, and steps to configure and verify EIGRP operation over circuit emulation and Frame Relay. After completing this activity, you will be able to meet these objectives: Configure and verify EIGRP operation over the WAN interfaces (circuit emulation and Frame Relay) Organize the tasks into an implementation plan to implement EIGRP functions Use Cisco IOS commands and applications, applied in the correct order, to the selected devices and portions of the network Verify the correct implementation and operation according to the expected performance criteria Verify the configuration and operation by using the proper show commands Document the implementation, operation, and maintenance
Information Packet
Visual Objective
Visual Objective for Lab 2-2: Configure and Verify EIGRP Circuit Emulation and Frame Relay Operations
ROUTE v1.0LG-8
Lab Guide
47
The following list details the configuration requirements for all devices in the company network: Set proper initial configuration on all devices in your lab. Your instructor will provide the necessary information on how to set the initial configuration on all devices. Configure the EIGRP operation over WAN point-to-point interfaces toward routers BBR1 and BBR2. By deploying EIGRP toward the pod, external routers will receive IP routing information about distant networks. Additionally, you must enable EIGRP over the pointto-point WAN interface between routers R3 and R4 to announce the routers directly connected LAN segments. The EIGRP configuration should be applied in such way that additional subnet(s) from the used IP addressing pool are automatically advertised if they are added. The EIGRP configuration should allow all the networks to be reachable from any router in the network. After a successful configuration, verify that the EIGRP adjacencies have been set up between routers R1 and BBR1, R1 and BBR2, and R3 and R4. Verify the EIGRP topology database and compare it against the EIGRP information that was put into the IP routing table on router R1. You should be able to see that all the networks acquired via EIGRP were put into the routing table and that the metric related to an individual route corresponds to the value present in the topology table. Router R1 is receiving external networks from router BBR1; that is, 192.168.x.0/24 subnets and external network 172.30.10.0/24 from router BBR2. The next configuration step will be to configure EIGRP operation over the WAN multipoint interface on router R1 toward router R2 through R4. By deploying EIGRP toward the internal routers in the pod, you will allow IP routing information exchange between all of the routers in the pod. Verify that the EIGRP adjacencies have been set up between the routers R1 and R2, R1 and R3, and R1 and R4. Verify the EIGRP topology database and compare it against the EIGRP information that was put into the IP routing table on routers R1, R3, and R4. You should be able to see that all the networks acquired via EIGRP were put into the routing table and that the metric related to an individual route corresponds to the value present in the topology table. Simulate a WAN connectivity failure between routers R3 and R4 and examine the consequences. Verify that router R3 no longer has routing information about network 172.30.24.0/24, and that routers R2 and R4 no longer have routing information about network 172.30.13.0/24. Additional configuration is required in order to adjust the EIGRP operation over the WAN multipoint interface on router R1 so that routers R3 and R4 will still have the information necessary to access each others LAN segments through the path via router R1, even in case of a WAN connectivity failure between routers R3 and R4. Verify that the EIGRP adjacencies between routers R1 and R2, R1 and R3, and R1 and R4 are up and running. Verify the EIGRP topology database and compare it against the EIGRP information that was put into the IP routing table on routers R1, R2, R3, and R4. You should be able to see that all the networks acquired via EIGRP were put into the routing table and that the metric related to an individual route corresponds to the value present in the topology table. Simulate a WAN connectivity failure between routers R3 and R4 and examine the consequences. Verify that router R3 still can access other networks, and that routers R2 and R4 have routing information about network 172.30.13.0/24 via the R1 WAN connection.
48
The last requirement is to adjust the EIGRP operation in a way that the path via R1 will be treated as a feasible successor. This adjustment will require that the delay parameter between the WAN connection and routers R3 and R4 be changed. You will also change the default EIGRP path selection to allow router R3 to install two routes to the destination network 172.30.24.0/24 while the routers are not of equal cost. Verify that the path via router R1 to network 172.30.24.0/24 is a feasible successor on router R3, whereas the path via router R4 is the primary path and is also used in the IP routing table on router R3. Verify if the configuration results changed the EIGRP path selection behavior on router R3 to treat the secondary path as a valid option for the IP routing table along with the path via router R4. Finally, verify that you have connectivity to the destination network 172.30.24.0/24 from the router R3 LAN segment.
Device Information
Device Name R1 R2 R3 R4 BBR1 BBR2 Role POD router POD router POD router POD router Backbone router Backbone router
Lab Guide
49
Command List
Command (no) auto-summary (no) shutdown delay tens-of-microsec interface type slot/port network x.x.x.x router eigrp as-number show ip eigrp neighbors show ip eigrp topology [prefix] [mask] show ip route [eigrp] ip address ip mask secondary [no] ip split-horizon eigrp AS variance number show interfaces serial Description Enables (disables) automatic summarization of classless subnets Administratively disables (enables) the interface Specifies the delay on interfaces (used for routing processes) Enters the interface configuration mode Enables EIGRP on interfaces belonging to a specified network Starts an EIGRP routing process with the given AS number Lists the EIGRP neighbors and relevant information on EIGRP neighbor adjacencies Displays the EIGRP topology table (whole, or only per prefix/mask) Displays the whole IP routing table or EIGRP routes only Sets the secondary ip address on the interface Disables/enables EIGRP split-horizon on an interface Sets the EIGRP metric variance multipler Displays the statistics for all interfaces configured on the router
Required Resources
50
Job Aids
Value Blank implementation requirements list Blank implementation and verification plan form Blank verification notes form Alternate resources and solutions form Implementation requirements hints Implementation and verification plan hints Solution configuration answer key (step-by step procedure) Location Task 1 Task 2
Task 3 End of this lab Hints section at the end of this lab Hints section at the end of this lab Configuration section at the end of this lab
Lab Guide
51
52

The first step in your configuration deployment is to establish a list of what is needed in order for you to configure each device; for example, device names, trunk encapsulation types, and so on. Use the following table, the visual objective at the beginning of this lab, the implementation policy, and the device information to create your implementation requirement list. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
Lab Guide
53

The second step in your configuration deployment is to establish a task list of the items that must be configured on each device, and in what order. Use the following table and the visual objective at the beginning of this lab to create your implementation and verification plan. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
54
Complete
Device
Order
Lab Guide
55

Now that you have collected all the requirements and planned your implementation, you are ready to connect to the remote lab and implement your solution. Do not forget to save. Once your solution is implemented, you need to verify that your configuration is working and fulfills all of the requirements specified by the customer. Keep in mind that once you leave the company, a network specialist will verify your configuration. Your ability to implement the solution according to the customer specifications will determine whether you get the job or not. Use the following area to record your notes and document the verifications you conducted to ensure that your solution is complete. If you are unsure about the verification steps, use the information provided in the Hints section at the end of this lab. Student Notes: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
57

Other groups may have implemented a solution that is different from yours. These will be discussed during the debriefing period that follows this lab. Use the following space to document other possible solutions for your reference. __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
59
60
Hints
Lab 2-2 Hint Sheet: Configure and Verify EIGRP Circuit Emulation and Frame Relay Operations
Device ALL Implementation Requirement Define an EIGRP AS number used in the lab. Hint Check the AS number used in the BBR1 and BBR2 router Visual Objective diagrams Visual Objective diagrams, Lab Visual Objective diagrams, Lab
ALL
Define which networks are used in the lab in order to advertise all major networks used in the pod. Identify the multipoint interfaces in order to disable split horizon under the EIGRP routing process for the correct routers. Examine and write down the current delay value of the Serial pointto-point subinterfaces.
ALL
R3, R4
Implementation and Verification Plan In Task 2, you will create an implementation and verification plan. Although there are several ways to set up this plan, the following tasks must be completed::
R1R4
All pod routers must be preloaded with the initial configuration for the lab.
Step 1
Lab Guide
61
Complete
Device
Order
Step
R1
Enable the EIGRP routing protocol on router R1 on WAN interfaces Serial 0/0/0.4 and Serial0/0.4. Routers BBR1 and BBR2 are preconfigured with the EIGRP AS 1. Apply the configuration so that EIGRP automatically advertises any additional network that is added to the router. Enable the EIGRP routing protocol on routers R3 and R4 on the WAN interface Serial 0/0.1 and advertise LAN segments. Apply the configuration in a way that EIGRP automatically advertises any additional network that is added to the router. Apply the configuration so that you will be capable of adding an EIGRP adjacency to R1 without a major reconfiguration. Add a secondary IP address 10.255.255.1/24 to the router R3 LAN interface. Verify that the EIGRP adjacencies have been set up between routers R1 and BBR1, R1 and BBR2, and R3 and R4. Verify the EIGRP topology database and compare it against the EIGRP information that was put into the IP routing table on router R1. You should be able to see that all of the networks acquired via EIGRP were put into a routing table and that the metric related to an individual route corresponds to the value present in the topology table. Router R1 receives external networks from router BBR1; that is, 192.168.x.0/24 subnets and external network 172.30.10.0/24 from router BBR2.
Step 2
R3, R4
Step 3
R3
Step 3
R1, R3, R4
Step 3
R1, R3, R4
Step 3
62
Complete
Device
Order
Step
R1
Enable the EIGRP routing protocol on the router R1 WAN interface, Serial 0/0/0.1. Use the proper EIGRP AS number to achieve seamless connectivity. Apply the configuration so that EIGRP automatically advertises any additional network that is added to the router. Enable the EIGRP routing protocol on the router R2, R3, and R4 WAN interface, Serial 0/0/0.1. Use the proper EIGRP AS number to achieve connectivity. Apply the configuration so that EIGRP automatically advertises any additional network that is added to the router. Verify that the EIGRP adjacencies have been set up between routers R1 and R2, R1 and R3, and R1 and R4.
Step 4
R2, R3, R4
Step 4
R1R4
Verify the EIGRP topology database and compare it against the EIGRP information that was put into the IP routing table on routers R1 through R4. You should be able to see that all of the networks acquired via EIGRP were put into the routing table and that the metric related to an individual route corresponds to the value present in the topology table Simulate a WAN connectivity failure between routers R3 and R4. Create a WAN connectivity failure between routers R3 and R4, and examine the consequences. Verify that router R3 no longer has routing information about network 172.30.24.0/24, and that routers R2 and R4 no longer have routing information about network 172.30.13.0/24.
Step 4
R3, R4
10
Step 5
Lab Guide
63
Complete
Device
Order
Step
R1
11
Change the EIGRP split-horizon behavior on the WAN multipoint interface on router R1 so that the LAN segment information for routers R2, R3, and R4 is also exchanged via that interface. Enable the interfaces that were disabled in order to simulate the failure.
Verify that the EIGRP adjacencies between the routers R1 and R2, R1 and R3, and R1 and R4 are up and running.
Step 6
R1R4
12
Adjust the delay parameter on the WAN interfaces for connectivity between routers R3 and R4 so that R3 load balances between R1 and R4 in order to reach network 172.30.24.0/24.
Verify the EIGRP topology database and compare it against the EIGRP information that was put into the IP routing table on routers R1 through R4. You should be able to see that all the networks acquired via EIGRP were put into the routing table and that the metric related to an individual route corresponds to the value present in the topology table. Create a WAN connectivity failure between routers R3 and R4 and examine the consequences. Verify that router R3 still can access other networks, and that routers R2 and R4 have routing information about network 172.30.13.0/24 via the router R1 WAN connection. At first, the path via router R1 to the network 172.30.24.0/24 is a feasible successor on router R3, whereas the path via router R4 is the primary path and is also used in the IP routing table on router R3.
Step 7
R1, R3
13
Simulate a WAN connectivity failure between routers R1 and R3.
Step 8
14
Change the delay parameter on the Serial 0/0/0.3 interface on routers R3 and R4 so that the path via R1 to network 172.30.24.0/24 becomes a feasible successor, while the path via router R3 to R4 is the primary one that is installed in the routing table on router R3. Enable the interfaces that were disabled in order to simulate the failure.
Step 9
64
Complete
Device
Order
Step
15
Change the EIGRP path selection behavior on router R3 so that R3 selects both the primary path via router R4 and the secondary path via router R1 to the destination network 172.30.24.0/24. Both paths should be present in the routing table.
EIGRP path selection behavior is changed on router R3 to treat the secondary path as a valid option for the IP routing table along with the path via router R4.
Step 10
16
Verify that you have connectivity to destination network 172.30.24.0/24 from the router R3 LAN segment.
Step 10
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration. 2. Configure EIGRP on router R1. 2.1. Use the following example to configure router R1 in this lab:

3. Configure EIGRP on routers R3 and R4 and verify the configuration. 3.1. Use the following example to configure the routers in this lab:

3.2. Use the following example to configure router R3 in this lab.

3.3. Verify the EIGRP configuration.

Lab Guide

65


4. Configure EIGRP on routers R3 and R4 and verify the configuration. 4.1. Use the following example to configure the routers in this lab:
Note Routers R1, R3, and R4 do not require any additional configuration because EIGRP is already enabled on those routers.
4.2. Verify the EIGRP configuration:

68


5. Simulate a WAN failure and verify routers R2, R3, and R4 after the WAN failure. 5.1. To simulate a WAN failure, run these commands:
Note In order to simulate WAN failure, you can shut down the interface on router R3. There are also other ways to simulate a WAN failure.
5.2. Verification after a WAN failure:

Lab Guide 71
6. Configure EIGRP on router R1 and verify the configuration. 6.1. Use the following example to configure router R1 in this lab:

72
7. Configure EIGRP on routers R3 and R4 and verify the configuration. 7.1. Use the following example to configure routers R3 and R4 in this lab:




8. Simulate a WAN failure and verify routers R2, R3, and R4 after the WAN failure. 8.1. To simulate a WAN failure, run these commands:
Note In order to simulate a WAN failure, you can shut down the interface on router R3. There are also other ways to simulate a WAN failure.
8.2. Verification after a WAN failure:


9. Configure EIGRP on routers R3 and R4 and verify the configuration. 9.1. Use the following example to configure routers R3 and R4 in this lab:

78
10. Configure EIGRP on router R3 and verify the configuration. 10.1. Use the following example to configure router R3 in this lab:

10.2.
Verify the EIGRP configuration:

Lab Guide
79
Lab 2-3: Configure and Verify EIGRP Authentication

Activity Objective
In this activity, you will use the correct commands, tools, and steps to configure and verify EIGRP authentication. After completing this activity, you will be able to meet these objectives: Select the required tools and commands to configure basic EIGRP authentication Organize the tasks into an implementation plan to implement EIGRP authentication Implement the identified EIGRP solution to configure basic EIGRP authentication in the provided network according to the implementation plan, using Cisco IOS commands and applications in the correct order to the selected devices and portions of the network Write a verification and test plan to verify the correct implementation and operation according to expected performance criteria Verify the implementation according to the verification plan, using the appropriate show and debug commands and applications to verify the correct operation, and document implementation, operation, and maintenance
Information Packet
Visual Objective
Visual Objective for Lab 2-3: Configure and Verify EIGRP Authentication
ROUTE v1.0LG-9
80
The following list details the configuration requirements for all devices in the company network: First, you will configure EIGRP authentication over the LAN interfaces between the routers in your pod. The authentication should use a safe password exchange. Passwords that will be used to authenticate the routers should never expire. Once the authentication configuration on the LAN interfaces is done, you must verify if the proper key chain is defined on each pods routers, and that the correct keys are used, which never expire. A successful configuration results in a neighbor relationship being formed over the LAN interfaces, and you can see all of the networks advertised by the EIGRP routing process in the IP routing table of every router in the pod. After a successful LAN authentication, you will configure EIGRP authentication over the WAN interfaces between the routers in your pod. The authentication should use a safe password exchange. Passwords that are used to authenticate the routers should never expire. Once the authentication configuration on the WAN interfaces is done, you must verify if the proper key chain is defined on each pod router and that correct keys are used, which never expire. A successful configuration results in a neighbor relationship being formed over the WAN interfaces, and you can see all of the networks advertised by the EIGRP routing process in the IP routing table of every router in the pod.
Device Information
Device Name R1 R2 R3 R4 Role POD router POD router POD router POD router
Lab Guide
81
Command List
Command interface type slot/port show ip eigrp neighbors show ip route [eigrp] key-chain name key id key-string string accept-lifetime from till send-lifetime from till ip authentication mode eigrp AS md5 ip authentication key-chain eigrp AS key-chain show key-chain show ip eigrp interfaces detail interface Description Enters the interface configuration mode Lists EIGRP neighbors and relevant information on EIGRP neighbor adjacencies Displays the whole IP routing table or EIGRP routes only Configures the key chain Define a key Defines a shared secret for a key Defines an acceptable lifetime for a key Defines the lifetime that is advertised for a key Enables EIGRP MD5 authentication Sets the key chain used for the EIGRP authentication Shows the configured key chains and parameters Shows EIGRP configuration details for an interface
Required Resources
Job Aids
Value Blank implementation requirements list Blank implementation and verification plan form Blank verification notes form Alternate resources and solutions form Implementation requirements hints Implementation and verification plan hints Solution configuration answer key (step-by-step procedure) Location Task 1 Task 2 Task 3 End of this lab Hints section at the end of this lab Hints section at the end of this lab Configuration section at the end of this lab
82

The first step in your configuration deployment is to establish a list of what is needed in order for you to configure each device; for example, device names, trunk encapsulation types, and so on. Use the following table, the visual objective at the beginning of this lab, the implementation policy, and the device information to create your implementation requirements list. If you are unsure, use the information provided in the Hints section at the end of this lab.
Lab Guide
83

The second step in your configuration deployment is to establish a task list of the items that must be configured on each device, and in what order. Use the following table and the visual objective at the beginning of this lab to create your implementation and verification plan. If you are unsure, use the information provided in the Hints section at the end of this lab.
84
Complete
Device
Order
Lab Guide
85

Now that you have collected all of the requirements and planned your implementation, you are ready to connect to the remote lab and implement your solution. Do not forget to save. Once your solution is implemented, you need to verify that your configuration is working and fulfills all of the requirements specified by the customer. Keep in mind that once you leave the company, a network specialist will verify your configuration. Your ability to implement the solution according to the customer specifications will determine whether you get the job or not. Use the following area to record your notes and document the verifications you conducted to ensure that your solution is complete. If you are unsure of the verification steps, use the information provided in the Hints section at the end of this lab.
Student Notes: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
87

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
89
------- This page intentionally left blank. --------
90
Hints
Lab 2-3 Hint Sheet: Configure and Verify EIGRP Authentication

Device ALL Implementation Requirement Define the keys used for authentication and their validity Hint Implementation Policy
Implementation and Verification Plan In Task 2, you need to create an implementation plan. There are, of course, several possible ways to accomplish this task. The following steps need to be completed:
R1R4
All pod routers must be preloaded with the initial configuration for the lab. Verify that the proper key chain is defined on each of the pod routers by inspecting the key chain configuration.
Step 1
R1R4
Configure a key chain on the routers that will be used for authentication on the LAN segments. Keys in the key chain used for authentication must never expire. Enable secure authentication on the LAN segments between routers and use the defined key chain for authentication.
Step 2
R1R4
Verify that secure authentication is configured on each of the pod routers by inspecting the configuration on each router.
Step 3
Lab Guide
91
Complete
Device
Order
Step
R1R4
Verify that the EIGRP adjacencies have been set up between the pod routers after you have applied the EIGRP authentication. Verify that the anticipated EIGRP routes are present in the routing tables of all routers. Verify that the anticipated EIGRP routers have authentication enabled on the LAN interfaces. Configure another key chain on the routers that will be used for authentication on the WAN segments. Keys in the key chain used for authentication must never expire. Enable secure authentication on the WAN segments between routers and use the defined key chain for authentication. Verify that the EIGRP adjacencies have been set up between the pod routers after you have applied the EIGRP authentication. Verify that the anticipated EIGRP routes are present in the routing tables of all routers. Verify that anticipated EIGRP routers have authentication enabled on LAN interfaces.
Verify that the routers form the neighbor relationship through LAN interfaces.
Step 4
R1R4
Verify the routing tables on every router for the EIGRP routes for involved networks. Verify the EIGRP details on every LAN interface involved in the authentication process. Verify that the proper key chain is defined on each of the pod routers by inspecting the key chain configuration.
Step 5
R1R4
Step 6
R1R4
Step 7
R1R4
Verify that secure authentication is configured on each of the pod routers by inspecting the configuration on each router. Verify that routers form the neighbor relationship through LAN interfaces.
Step 8
R1R4
Step 9
R1R4
10
Verify the routing table on every router for the EIGRP routes for involved networks. Verify EIGRP details on every LAN interface involved in the authentication process.
Step 10
R1R4
11
Step 11
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration. 2. Configure a key chain and keys used for authentication. 2.1. Use the following example to configure the routers in this lab:


Note The same commands are also used on routers R2, R3, and R4
2.2. Verify that the proper key chain is defined on each of the pod routers.

Note
The same command must also be used on routers R2, R3, and R4, and the command output will be the same as well.
3. Enable secure authentication on the LAN segments. 3.1. Use the following example to configure the routers in this lab:

Note The same commands are used also on routers R2, R3, and R4.
3.2. Verify that secure authentication is configured and the correct key chain is used.

Note The same command must also be used on routers R2, R3, and R4, and the command output will be the same as well.
4. Verify that the EIGRP adjacencies have been set up and that each router forms a neighbor relationship over the LAN interface.

Lab Guide 93
5. Verify that the LAN and WAN segments are advertised on all routers.

6. Verify that detailed EIGRP interface information shows you that secure LAN authentication is enabled on the LAN interfaces on all routers in your lab.

94
Lab Guide
95
7. Configure a key chain and keys used for authentication. 7.1. Use the following example to configure the routers in this lab:
Note The same commands are also used on routers R2, R3, and R4.
7.2. Verify that the proper key chain is defined on each of the pod routers.

Note
The same command must also be used on routers R2, R3, and R4, and the command output will be the same as well.
8. Enable secure authentication on WAN segments. 8.1. Use the following example to configure the routers in this lab:

Note
The same commands used on router R1 are also used on router R2.
Note
The same commands used on router R3 are also used on router R4.
8.2. Verify that secure authentication is configured and that the correct key chain is used.

Note The same command used on router R1 must also be used on router R2, and the command output will be the same as well.
Note The same command used on router R3 must also be used on router R4, and the command output will be the same as well.
9. Verify that the EIGRP adjacencies have been set up and that each router forms a neighbor relationship over the LAN interface.

10. Verify that LAN and WAN segments are advertised on all routers.

11. Verify that detailed EIGRP interface information shows that secure LAN authentication is enabled on the LAN interfaces on all routers in your lab.

98 Implementing Cisco IP Routing (ROUTE) v1.0
Lab Guide
99
Lab 2-4: Implement and Troubleshoot EIGRP Operations

Activity Objective
In this activity, you must analyze, locate, and fix EIGRP-related problems in your network that are caused by a misconfiguration or poor design. After this activity, you will be able to meet these objectives: Develop a work plan to troubleshoot configuration and security issues related to the EIGRP Isolate the causes of the problems Correct all of the identified EIGRP issues Document and report the troubleshooting findings and recommendations
Information Packet
Visual Objective
Visual Objective for Lab 2-4: Verify EIGRP Operations
ROUTE v 1. 0LG-10
Troubleshooting Policy
The following lists details troubleshooting requirements and issues for all devices in the company network:
100
Trouble Ticket A: EIGRP Adjacency Issues You were absent for a short period of time, and during your absence a junior engineer substituted foryou. There was a demand for additional IP subnet deployment on a LAN segment between routers R2 and R4. The junior engineer deployed additional IP subnets, but the connectivity beyond that segment to the new IP subnet is not available. You have been asked to examine and correct the issue, so that the new IP subnet will be accessible from any part of the network. There is also an issue with the EIGRP adjacency to router BBR1. During your absence, the junior engineer was asked to improve routing security related to router BBR1. An adjacency with router BBR1 cannot be formed and you are asked to correct that problem. Tthe engineer was also asked to optimize EIGRP operation. He applied a configuration that improved the metric calculation on R4, which broke the connectivity from that router. In addition to that, he tried to optimize the routing tables on the routers and implemented summarization to accomplish this goal, which is not working as expected. You are asked to address this issue too. Trouble Ticket B: Limited Connectivity Your assistant reports that there is no connectivity to the LAN subnets attached to routers R2 and R4 from a newly deployed spoke location where router R3 was deployed. Router R3 has limited connectivityall other IP subnets in the network are accessible via router R1. You must locate and correct the issue with EIGRP routing. Instructions Together with your team members, create a troubleshooting and verification plan to divide the work. Assign each team member appropriate roles and coordinate device access among the team members. Together, work on Trouble Tickets A and B to resolve the issues. Document your progress in the Troubleshooting Log provided below as part of Task 2 in order to help facilitate efficient communication within the team and to have an overview of your troubleshooting process for reference during the lab debriefing discussions.
Device Information
Device Name R1 R2 R3 R4 BBR1 BBR2 Role POD router POD router POD router POD router Backbone router Backbone router
Lab Guide
101
Command List
Command interface type slot/port show ip eigrp neighbors show ip route [eigrp] key-chain name key id key-string string accept-lifetime from till send-lifetime from till show key-chain show ip eigrp interfaces detail interface debug eigrp packets debug ip eigrp neighbor AS ip address [no] metric weights 0 k1 k2 k3 k4 k5 ip address ip mask [secondary] Description Enters the interface configuration mode Lists the EIGRP neighbors and relevant information on EIGRP neighbor adjacencies Displays the entire IP routing table or EIGRP routes only Configures a key chain Defines a key Defines a shared secret for a key Defines a key's acceptable lifetime Defines a key's lifetime that is advertised Shows the configured key chains and parameters Shows the EIGRP configuration details for an interface Enables EIGRP packet debugging Enables EIGRP debugging per neighbor Sets EIGRP K values Sets the IP address on an interface
Required Resources
102
Job Aids
Value Blank troubleshoouting and verification plan Blank troubleshooting log Troubleshooting and verification plan hints Trouble Ticket Hints List Configuration sample after trouble tickets Location Task 1 Task 2 Hints section at the end of this lab Hints section at the end of this lab Configuration section at the end of this lab
Lab Guide
103
Task 1: Create an Troubleshooting and Verification Plan

The first step is to establish a troubleshooting and verification plan. This is a task list of the items that must be checked and corrected in order to establish working conditions in the EIGRP network. Use the following table and the visual objective at the beginning of this lab to create your troubleshooting and verification plan. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
104
Complete
Device
Order
Lab Guide
105
Task 2: Troubleshooting Log

Use this log to document your actions and results during the troubleshooting process.
Trouble Ticket Actions and Results
106
Trouble Ticket
Actions and Results
Lab Guide
107
Hints
Lab 2-4 Hint Sheet: Implement and Troubleshoot EIGRP Operations

Troubleshooting and Verification Plan In Task 1, you will create a troubleshooting and verification plan. Although there are several ways to set up this plan, the following tasks must be completed::
R1R4
Load initial configuration.
All pod routers must be preloaded with the initial configuration for the LAB. Use the show ip eigrp neighbor command in order to see if neighbors are adjacent. Verify the IP address configuration on all routers and establish a working configuration by using the show running-configuration command.
R1R4
On all the routers, examine the EIGRP adjacency tables and write down the information. Observe the messages that appear on the routers because they might indicate that there is some kind of IP address mismatch and that the metric calculation is not in sync on all the routers. Verify how a secondary IP subnet is applied on the LAN segment.
R1, R2, R4
R2, R4
Verify the secondary IP address configuration on the LAN segments by issuing the show running-configuration command. Debug the EIGRP packets in order to identify the source of the connectivity issues. Use the following commands: debug eigrp packets and debug eigrp neighbors. Identify the presence of EIGRP routes inside the IP routing table using the show ip route eigrp command. Verify if all IP subnets from the pod are present.
R1
Verify IP connectivity toward router BBR1. Enable EIGRP packet debugging and debugging for neighbor BBR1 to explore the problem toward that neighbor.
R1R4
Examine the IP routing tables on the routers in your pod and verify whether specific IP subnet information is present.
108
Complete
Device
Order
R1, R3
Verify the neighbor relationship between routers R1 and R3.
Use the show ip eigrp neighbors command to verify if the neighbor relationship is established between the routers. Use the show ip route eigrp and show ip eigrp topology commands to verify that the IP routing table reflecting the correct EIGRP topology and costs. Use the debug eigrp neighbors command in order to see what information is advertised to router R3.
R1, R3
Examine the IP routing table and the EIGRP topology table on routers R1 and R3.
R3
Enable EIGRP debugging for the neighbor and observe what information is advertised to router R3.
Trouble Ticket Hint List On all routers, examine the EIGRP adjacency tables and write down the information. Observe the messages that appear on routers R1, R2, and R4they indicate that there is some kind of IP address mismatch and that the metric calculation is not in sync with all routers. Verify how a secondary IP subnet is applied on the LAN segment on routers R2 and R4. Verify IP connectivity toward router BBR1. Enable EIGRP packet debugging and debugging for neighbor BBR1 to explore the problem toward that neighbor. Examine the IP routing tables on routers in your pod and determine whether specific IP subnet information is present. Verify the neighbor relationship between routers R1 and R3. Examine the IP routing table and the EIGRP topology table on routers R1 and R3. Enable EIGRP debugging for the neighbor and observe what information is advertised to router R3. Configuration Sample After Trouble Tickets

Lab Guide
109
110
------- The page intentionally left blank. --------
Lab Guide
111
Lab 3-1: Configure and Verify OSPF to Improve Routing Performance

Activity Objective
In this activity, you will use the correct commands, tools, and steps to configure and verify OSPF implementation. After completing this activity, you will be able to meet these objectives: Configure and verify OSPF operation over LAN interfaces Configure and verify OSPF operation over Frame Relay using a point-to-multipoint OSPF network type Configure and verify OSPF operation over Frame Relay using a point-to-point network type Select the required tools and commands to configure OSPF operations Make a list of configuration and implementation steps Write a verification and test plan to verify the proper implementation and operation according to the expected performance criteria Verify the configuration and operation by using the proper show and debug commands
Information Packet
Visual Objective
Visual Objective for Lab 3-3: Configure and Verify OSPF Route Summarization for Interarea and External Routes
ROUTE v 1. 0LG-13
112
The following list details the configuration requirements for all devices in the company network: In this task you, will configure OSPF on each of the routers in your networkrouters R1, R2, R3, and R4. OSPF will be used to exchange routing information in order to achieve IP connectivity over the LAN interfaces. All of the routers should be members of the OSPF backbone area. The OSPF configuration should be so specific that if an additional network is added to the router, that network is not automatically advertised. The IP routing tables on all your routers should be populated with all of the specific IP subnets in your network. Verify that the proper OSPF adjacencies have been set up on the LAN segments between the routers in your pod (between routers R1 and R3 and between R2 and R4). Also examine how long the adjacencies have been set up and whether there is any problem in neighbor communications;, such as routing packets remaining in the queue. Verify whether the OSPF has been set up to advertise the IP subnets present on the loopback and LAN interfaces with the correct mask without examining the IP routing table and OSPF topology database. Verify the OSPF link-state database and compare it against the OSPF information that was put into the IP routing table on router R1. You should be able to see that the router R3 loopback network, acquired via OSPF, was put into the routing table, and that the metric related to the route corresponds to the value present in the link-state database.Verify that router R1 is the DR on the LAN segment between R1 and R3. As a next step, you will configure OSPF on the WAN segment between routers R3 and R4 to exchange IP routing information about the loopback and LAN. The OSPF configuration must reflect the point-to-point representation of the Frame Relay interface. Routers will be members of the same OSPF area as LAN segments. The OSPF configuration should be so specific that if an additional network is added to the router, that network is not automatically advertised. The IP routing tables on all your routers should be populated with all of the specific IP subnets in your network. Verify that the proper OSPF adjacencies have been set up on the WAN segment between routers R3 and R4 in your pod. Also examine how long the adjacencies have been set up and whether there is any problem with neighbor communications, such as routing packets remaining in the queue. Verify on the routers in your pod that OSPF has been set up to advertise the IP subnets present on the loopback, LAN interfaces, and the WAN segment from router R3 to R4 with the correct mask without examining the IP routing table and OSPF topology database.Verify the OSPF link-state database and compare it against the OSPF information that was put into the IP routing table on router R1. You should be able to see that the router R3 loopback network, acquired via OSPF, was put into the routing table, and that the metric related to the route corresponds to the value present in the link-state database. In the last step you will configure OSPF on a WAN segment between routers R1, R2, and R4 to exchange IP routing information. OSPF configuration must reflect the point-tomultipoint representation of the Frame Relay interface. Routers will be members of the same OSPF area as LAN segments. The OSPF configuration should be so specific that if an additional network is added to the router, that network is not automatically advertised. The IP routing tables on all of your routers should be populated with all of the specific IP subnets in your network.
Lab Guide
113
Verify that the proper OSPF adjacencies have been set up on the WAN segment between the routers R1, R2, and R4 in your pod. Examine also how long the adjacencies have been set up and whether there is any problem with neighbor communications, such as routing packets remaining in the queue. Verify for the routers in your pod that the OSPF is advertising all of the IP subnets on your routers and that the information is present in the OSPF link-state database as well as in the IP routing table.
Device Information
Device Name R1 R2 R3 R4 Role POD router POD router POD router POD router
Command List
Command Description Turns on OSPF; the process number is not communicated to other routers Creates a subinterface (either point-to-multipoint or point-topoint) Forces OSPF to treat this interface as point-to-multipoint; the default is NBMA Specifies the interfaces on which OSPF will run, in Area 0 Displays information about interfaces configured for OSPF Displays a list of OSPF neighbors Displays information about the OSPF database Displays the entire IP routing table or OSPF routes only Sets the router priority Configures the router to send a syslog message when an OSPF neighbor goes up or down Specifies the interval between hello packets that are sent on the interface by the Cisco IOS software Clears the Open Shortest Path First (OSPF) routing process
router ospf 1 interface s0/0/0.1 multipoint | point-to-point ip ospf network point-tomultipoint network 172.31.x.0 0.0.0.255 area 0 show ip ospf interface show ip ospf neighbor show ip ospf database show ip route [ospf]
ip ospf priority log-adjacency-changes ip ospf hello-interval clear ip ospf 1 process
114
Required Resources
Job Aids
Value Blank implementation requirements list Blank implementation and verification plan form Blank verification notes form Alternate resources and solutions form Implementation requirements hints Implementation and verification plan hints Solution configuration answer key (step-bystep procedure) Location Task 1 Task 2
Lab Guide
115

The first step in your configuration deployment is to establish a list of what is needed in order for you to configure each device; for example, the device names, trunk encapsulation types, and so on. Use the following table, the visual objective at the beginning of this lab, the implementation policy, and the device information to create your implementation requirement list. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
116

Lab Guide
117
Complete
Device
Order
118

Now that you gave collected all of the requirements and planned your implementation, you are ready to connect to the remote lab and implement your solution. Do not forget to save. Once your solution is implemented, you need to verify that your configuration is working and that it fulfills all of the requirements specified by the customer. Keep in mind that once you leave the company, a network specialist will verify your configuration. Your ability to implement the solution according to the customer specifications will determine whether you get the job or not. Use the following area to record your notes and document the verifications you conducted to ensure that your solution is complete. If you are unsure about the verification steps, use the information provided in the Hints section at the end of this lab.
Student Notes: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
120

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
122
-------- The page intentionally left blank. --------
Lab Guide
123
Hints
Lab 3-1 Hint Sheet: Configure and Verify OSPF to Improve Routing Performance
Implementation Requirements To facilitate the configuration of your network, Task 1 asks you to create an implementation requirements list. This list details the elements you need in order to develop an implementation plan. The following is an example of such a list:
Device ALL ALL Implementation Requirement Define which specific subnets OSPF must announce Decide which OSPF area will be used Hint Visual Objective Implementation Policy
R1R4
Load initial configuration.
All pod routers must be preloaded with the initial configuration for the lab. Verify that the proper OSPF adjacencies have been set up on LAN segments between the routers. Verify on each router that the OSPF has been set up to advertise the IP subnets present on the loopback and LAN interfaces with the correct mask, without examining the IP routing table and OSPF topology database. Verify the OSPF link-state database and compare it to the OSPF information that was put into the IP routing table. You should be able to see that the loopback network acquired via OSPF was put into the routing table, and that the metric related to the route corresponds to the value present in the link-state database.
Step 1
R1, R3
Enable OSPF routing protocol on the LAN interface. Apply the configuration so that OSPF does not automatically advertise any additional network that is added to the router. Announce only LAN and loopback networks. Both routers should be members of the backbone area.
Step 2
124
Complete
Device
Order
Step
R2, R4
Enable the OSPF routing protocol on the LAN interface. Apply the configuration so that OSPF does not automatically advertise any additional network that is added to the router. Announce only the LAN and loopback networks. Both routers should be members of the backbone area.
Verify that the proper OSPF adjacencies have been set up on the LAN segments between the routers. Verify on each router that OSPF has been set up to advertise the IP subnets present on the loopback and LAN interfaces with the correct mask, without examining the IP routing table and OSPF topology database. Verify the OSPF link-state database and compare it to the OSPF information that was put into the IP routing table. You should be able to see that the loopback network acquired via OSPF was put into the routing table, and that the metric related to the route corresponds to the value present in the link-state database.
Step 3
R1, R3
Change the default OSPF DR/BDR selection on the LAN segment between routers R1 and R3, and force OSPF to choose R1 to become a DR. Change the OSPF configuration on router R3 and include the WAN segment that connects router R3 to router R4. The OSPF configuration that you add should be so specific that no additional networks are advertised. Place the segment in the OSPF area you have used for the LAN segment and loopbacks. The OSPF network representation for the WAN segment should reflect the Frame Relay network type.
Verify that router R1 is the DR on the LAN segment between R1 and R3.
Step 4
R3
Step 5
Lab Guide
125
Complete
Device
Order
Step
R4
Change the OSPF configuration on router R3 and include the WAN segment that connects router R3 to router R4. The OSPF configuration that you add should be so specific that no additional networks are advertised. Place the segment in the OSPF area you have used for the LAN segment and loopbacks. The OSPF network representation for the WAN segment should reflect the Frame Relay network type.
Verify that the proper OSPF adjacencies have been set up on the WAN segment between routers R3 and R4 in your pod. Also examine how long the adjacencies have been set up and whether there is any problem with neighbor communications, such as routing packets remaining in the queue. On all of the pod routers, verify the OSPF link-state database and compare it against the OSPF information that was put into the IP routing table. You should be able to see that the loopback network acquired via OSPF was put into the routing table, and that the metric related to the route corresponds to the value present in the link-state database.
Step 5
R1
Include the WAN segment on router R1 in OSPF and enable the OSPF adjacency over the serial interface toward routers R2 and R4. The OSPF configuration that you add should be so specific that no additional networks are advertised. Place the segment in the same OSPF area you have used so far. The OSPF network representation for the WAN segment should reflect the Frame Relay multipoint network type.
Step 6
126
Complete
Device
Order
Step
R2, R4
Add the OSPF configuration on routers R2 and R4. Include WAN segment toward router R1 in the OSPF. The OSPF configuration should also advertise any additional networks from a major network if added later. The OSPF interface network type should reflect the Frame Relay WAN segment representation.
Verify that the proper OSPF adjacencies have been set up on the WAN segment between routers R1, R2, and R4 in your pod. Examine how long the adjacencies have been set up and whether there is any problem with neighbor communications, such as routing packets remaining in the queue. Verify for the routers in your pod that OSPF is advertising all the IP subnets on your routers and that the information is present in the OSPF link-state database as well as in the IP routing table.
Step 6
Step-by-Step Procedure for Implementation and Verification 1. Load an initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration. 2. Configure OSPF over the LAN interfaces on routers R1 and R3. 2.1. Use the following example to configure the routers in this lab:

2.2. Verify that the proper adjacencies are set up between neighbors on the LAN segment.

2.3. Verify that the proper interfaces are involved in the OSPF process, and that networks are advertised.

2.4. Examine the OSPF link-state database and verify that the loopback network acquired via OSPF was put into the routing table.

128
3. Configure OSPF over the LAN interfaces on routers R2 and R4. 3.1. Use the following example to configure the routers in this lab:

3.2. Verify that the proper adjacencies are set up between neighbors on the LAN segment.

3.3. Verify that proper interfaces are involved in the OSPF process and that networks are advertised.

3.4. Examine the OSPF link-state database and verify that the loopback network acquired via OSPF was put into the routing table.

4. Change the default OSPF DR/BDR selection on the LAN segment between routers R1 and R3. 4.1. Use the following example to configure the routers in this lab:

4.2. Verify that router R1 is the DR on the LAN segment between R1 and R3.
5. Configure OSPF over Frame Relay using a point-to-point OSPF network type. 5.1. Use the following example to configure router R3 in this lab:

5.2. Use the following example to configure router R4 in this lab:

5.3. Verify the configuration on routers R1, R2, R3, and R4.


132

6. Configure OSPF over Frame Relay using a point-to-multipoint OSPF network type. 6.1. Use the following example to configure router R1 in this lab:

6.2. Use the following example to configure routers R2 and R4 in this lab:

6.3. Verify the configuration on routers R1, R2, and R4.




Lab Guide 135
136
Lab 3-2: Implement and Verify OSPF Multiarea Routing

Activity Objective
In this activity, you will use the correct commands, tools, and steps to configure and verify OSPF multiarea routing. After completing this activity, you will be able to meet these objectives: Configure and verify the OSPF operation over LAN and WAN interfaces Configure and verify the OSPF operation using multiple areas Select the required tools and commands to configure OSPF operations Influence the path selection for OSPF by changing the cost Optimize the OSPF operation to prevent the transmission of unnecessary hellos Make a list of configuration and implementation steps Write a verification and test plan to verify the proper implementation and operation according to the expected performance criteria Verify the configuration and operation by using the proper show and debug commands
Information Packet
Visual Objective
Visual Objective for Lab 3-2: Implement and Verify OSPF Multiarea Routing
ROUTE v 1. 0LG-12
Lab Guide
137
The following list details the configuration requirements for all devices in the company network: First you will configure OSPF on the WAN segment between routers R1 and BBR2. BBR2 is preconfigured with OSPF routing in Area 0. Router R1 will be configured in OSPF Area 0 with a WAN interface toward router BBR2 and should receive IP routing information about network 172.30.10.0/24 from router BBR2. Verify that the OSPF adjacency has been set up on the WAN segment between routers R1 and BBR2. Examine the OSPF link-state database on router R1 and compare it to the IP routing table to verify the correctness of the received information. Examine the IP routing table on router R1 and verify that it is populated with the expected OSPF routes. Verify that you have connectivity to the BBR2 LAN segment 172.30.10.0/24. In this task you will complete the OSPF routing configuration in your pod. You will configure OSPF routing on routers R2, R3, and R4. Router R3 will be a member of OSPF Area 3 with all of its interfaces. Routers R2 and R4 will be members of Area 24. All of the router R2 and R4 interfaces will be part of that area. Routers in your pod should exchange and receive IP routing information about all of the subnets available. Verify that the OSPF adjacency has been set up between routers R1 and R3 in OSPF Area 3. Examine the OSPF link-state database on router R3 and compare it against its routing table to verify that the correct information was put into the IP routing table. Verify that router R3 has all the necessary IP subnets in its routing table and that it can access all the IP subnets in the network. Verify that the OSPF adjacency has been set up between routers R1 and R2 and between routers R1 and R4 in OSPF Area 24. Examine the OSPF link-state database on routers R2 and R4 and compare them against their routing tables to verify that the correct information was put into the IP routing table. Verify that routers R2 and R4 have all the necessary IP subnets in their routing tables and that they can access all the IP subnets in the network, including the subnets that have been announced by BBR2. Verify that you have connectivity to the BBR2 LAN segment 172.30.10.0/24 from all routers in your pod. In this task you will precisely adjust the OSPF operation on your routers. You will change the default path cost calculation in Area 24 and persuade router R1 to prefer the path via router R2 to the 172.30.24.0/24 LAN segment. Next you will have to make the OSPF routing in Area 0 more stable by forcing router R1 to administratively define the router ID. Finally, you will optimize the OSPF operation in Area 3 on router R3 to preserve CPU resources on that router by eliminating unnecessary OSPF traffic on the LAN segment. Verify that all the necessary OSPF adjacencies in the network are up and running. Router R1 should have an OSPF adjacency set up with BBR2 in Area 0, with router R3 in Area 3, and with routers R2 and R4 in Area 24. Verify that router R1 is using a stable router ID for the OSPF process you have configured. Examine the IP routing table on router R1 and confirm that it prefers the path via router R2 toward the 172.30.24.0/24 segment. Verify that R1 selects R2 as the next hop for IP packets destined to segment 172.30.24.0/24. Examine the OSPF adjacencies on router R3 and verify that the adjacency with router R1 is the only adjacency that is up and running. Verify that router R3 is not trying to set up an OSPF adjacency via the LAN segment.
138
Device Information
Device Name R1 R2 R3 R4 BBR2 Role POD router POD router POD router POD router Backbone router
Command List
Command router ospf 1 neighbor 10.1.110.2 cost 10 interface s0/0/0.1 multipoint | pointto-point ip ospf network point-to-multipoint network 172.31.x.0 0.0.0.255 area 0 show ip ospf interface show ip ospf neighbor show ip ospf database show ip route [ospf] ip ospf priority log-adjacency-changes ip ospf hello-interval clear ip ospf 1 process router-id passive-interface Ping Trace Description Turns on OSPF; the process number is not communicated to other routers Assigns a cost to the neighbor Creates a subinterface (either point-to-multipoint or point-topoint) Forces OSPF to treat this interface as point-to-multipoint; the default is NBMA Specifies the interfaces on which OSPF will run, in Area 0 Displays information about interfaces configured for OSPF Displays a list of OSPF neighbors Displays information about the OSPF database Displays a whole IP routing table or OSPF routes only Sets the router priority Configures the router to send a syslog message when an OSPF neighbor goes up or down Specifies the interval between hello packets that are sent on the interface by the Cisco IOS software Clears the Open Shortest Path First (OSPF) routing process Sets a fixed router ID Disables the sending of routing updates on an interface Diagnoses basic network connectivity Discovers the routes that packets will actually take when traveling to their destination
Lab Guide
139
Required Resources
Job Aids
140

Lab Guide
141
142

The second step in your configuration deployment is to establish a task list of the items that must be configured on each device, and in what order. Use the following table and the visual objective at the beginning of this lab to create your implementation and verification plan. If you are unsure, you use the information provided in the Hints section at the end of this lab.
Lab Guide
143
Complete
Device
Order
144

Now that you have collected all the requirements and planned your implementation, you are ready to connect to the remote lab and implement your solution. Do not forget to save. Once your solution is implemented, you need to verify that your configuration is working and fulfills all the requirements specified by the customer. Keep in mind that once you leave the company, a network specialist will verify your configuration. Your ability to implement the solution according to the customer specifications will determine whether you get the job or not. Use the following area to record your notes and document the verifications you conducted to ensure that your solution is complete. If you are unsure about the verification steps, use the information provided in the Hints section at the end of this lab. Student Notes: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
146

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
148
Hints
Lab 3-2 Hint Sheet: Implement and Verify OSPF Multiarea Routing
Device ALL Implementation Requirement Define the interfaces and networks used in the network in order to correctly implement OSPF. Observe the costs on the links. Hint Visual Objective and lab Lab
ALL
R1R4
Load the initial configuration.
Step 1
Lab Guide
149
Complete
Device
Order
Step
R1
Configure OSPF routing protocol on router R1. Enable the logging of OSPF neighbor changes on router R1. Include the router R1 WAN interface toward router BBR2 in the OSPF routing process. Remember that router BBR2 is already configured with the OSPF routing protocol toward router R1 in OSPF Area 0
Verify that the OSPF adjacency has been set up on the WAN segment between routers R1 and BBR2. Examine the OSPF link-state database on router R1 and compare it against the IP routing table to verify the correctness of the received information. Examine the IP routing table on router R1 and verify that it is populated with the expected OSPF routes. Verify that you have connectivity to the BBR2 LAN segment 172.30.10.0/24.
Step 2
R3
Enable the OSPF routing protocol on router R3 and enable the logging of OSPF adjacency changes. Set up an OSPF adjacency with router R1. Configure router R3 to be part of Area 3 with all its interfaces. On router R1, add the OSPF configuration to enable adjacency with router R3. Router R1 should announce its networks and networks received via the backbone OSPF area to router R3. Configure the OSPF routing protocol on routers R2 and R4, and enable the logging of adjacency changes. Routers should set up an OSPF adjacency with router R1 and between each other. The LAN and WAN interfaces of routers R2 and R4 should be part of OSPF Area 24. Add a configuration on router R1 to allow the creation of OSPF adjacencies with routers R2 and R4. Router R1 should announce its network and networks received via the backbone area to routers R2 and R4. Verify that the OSPF adjacency has been set up between routers R1 and R3 in OSPF Area 3.
Step 3
R1
Step 3
R1, R2, R4
Verify that the OSPF adjacency has been set up between routers R1 and R2 and between routers R1 and R4 in OSPF Area 24. Examine the OSPF link-state database on routers R2 and R4 and compare it to the router R2 and R4 routing tables to verify that the correct information was put into the IP routing table, including the subnets that were announced by BBR2.
Step 4
150
Complete
Device
Order
Step
R1, R3, R4
Examine the OSPF link-state database on router R3 and compare it against its routing table to verify that the correct information was put into the IP routing table, including the subnets that were announced by BBR2. Verify that you have connectivity to the router BBR2 LAN segment 172.30.10.0/24 from routers R1 and R4.
Step 5
R1
Examine the routing information for the LAN segment 172.30.24.0/24 on router R1 to verify which path is used to reach the destinations on that segment. Adjust the cost parameter used for OSPF path calculation on routers in Area 24 so that router R1 prefers the path via router R2 to the 172.30.24.0/24 destination subnet. Examine the OSPF configuration on router R1 to inspect what OSPF router ID is used for the OSPF process. Then change the OSPF router ID on router R1 and force the router to use the administratively defined value for the router ID. Examine the OSPF adjacencies on router R3. Verify that there are no neighbors seen on the LAN segment, but despite that, router R3 is constantly trying to set up OSPF adjacency. Change the OSPF configuration on router R3 so that it stops trying to set up OSPF adjacency via the LAN interface, which will preserve CPU cycles. The configuration should prevent the sending of OSPF hello packets out of that interface.
Examine the IP routing table on router R1 and confirm that it prefers the path via router R2 toward the 172.30.24.0/24 segment.
Step 6
R1
Verify that router R1 is using a stable router ID for the OSPF process you have configured. Router R1 should have OSPF adjacency set up with BBR2 in Area 0, with router R3 in Area 3, and with routers R2 and R4 in Area 24. Verify that router R3 stopped trying to set up an OSPF adjacency via the LAN segment.
Step 7
R3
10
Step 8
11 12
Lab Guide
151
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration. 2. Configure the OSPF backbone area. 2.1. Use the following example to configure the routers in this lab:

2.2. Verify OSPF configuration and reachability using different commands on router R1.

3. Configure the OSPF nonbackbone areas. 3.1. Use the following example to configure router R3 in this lab:


3.3. Verify the adjacency between routers R1 and R3:

4. Configure OSPF nonbackbone areas. 4.1. Use the following example to configure routers R2 and R4 in this lab:


4.3. Verify the OSPF configuration on routers R1, R2, and R4.


Lab Guide
155

5. Verify the OSPF configuration on router R3 and connectivity to the BBR2 LAN segment 172.30.10.0/24 from routers R1 and R4.

Lab Guide
157
6. Tuning OSPF operation. 6.1. Use the following example to configure router R1 in this lab:

6.2. Verify that router R1 prefers the path via router R2 toward the 172.30.24.0/24 segment:

7. Manipulate the router ID. 7.1. Use the following example to configure router R1 in this lab:

7.2. Verify that router R1 prefers the path via router R2 toward the 172.30.24.0/24 segment:


8. Manipulation using OSPF adjacencies. 8.1. Use the following example to configure router R3 in this lab:

8.2. Verify that router R3 did not establish adjacency, and that router R3 stopped trying to establish adjacency, on the LAN segment:
Lab Guide
161
162
Lab Guide
163
Lab 3-3: Configure and Verify OSPF Route Summarization for Interarea and External Routes
Activity Objective
In this activity, you will use correct commands, tools, and steps to configure and verify OSPF multiarea routing and optimize OSPF routing by implementing summarization. After completing this activity, you will be able to meet these objectives: Configure and verify the OSPF operation over LAN and WAN interfaces Configure and verify the OSPF operation using multiple areas Select the required tools and commands to configure OSPF operations Optimize the OSPF operation by implementing route summarization for the internal OSPF routes Optimize the OSPF operation by implementing route summarization for the external OSPF routes Make a list of the configuration and implementation steps Write a verification and test plan to verify the proper implementation and operation according to the expected performance criteria. Verify the configuration and operation by using the proper show and debug commands
Information Packet
Visual Objective
Visual Objective for Lab 3-3: Configure and Verify OSPF Route Summarization for Interarea and External Routes
ROUTE v 1. 0LG-13
164
The following list details the configuration requirements for all devices in the company network: In this task you will examine IP routing information exchanged by routers configured with the OSPF routing protocol. Routers R1, R2, R3, and R4 are configured with the OSPF routing protocol and are announcing their directly attached networks. Router R4 is also announcing some external OSPF networks into the OSPF routing domain. Learn about the current OSPF configuration, which includes information about the networks that are included in the OSPF routing domain, interfaces where OSPF is enabled, OSPF adjacencies, link-state databases, and OSPF area design. Verify that all the routers have IP connectivity to the advertised networks. Examine the IP routing table, write down the IP networks that are advertised, and determine the IP addressing scheme. Use the information about the OSPF routing configuration and design that you collected in the previous task to optimize OSPF operation. You will optimize the OSPF link-state database, and consequently the IP routing table, by making them smaller using summarization of the 172.30.x.0/24 subnets from router BBR2. Verify that all relevant OSPF adjacencies are still up and running for routers R1, R2, R3, and R4. Router R1 should have running OSPF adjacencies to routers R2, R3, R4, and BBR2. Router R3 should have running OSPF adjacency with router R1 only, whereas routers R2 and R4 should have OSPF adjacency running between themselves and toward router R1. Examine the OSPF link-state databases on routers R1, R2, R3, and R4 and verify that the relevant information is in the databases. Verify that the best path information has been put into the router IP routing tables. Examine the OSPF link-state database and IP routing table on relevant routers to see that the OSPF internal route summarization for the pod IP subnets 172.30.x.0/24 has been applied. Further optimize OSPF routing operation by summarizing the OSPF external routes. Router R3 is redistributing certain 192.168.x.0/24 subnets into the OSPF routing domain. Because it is the only source of that IP routing information, there is no need for other routers to learn and keep information about individual 192.68.x.0/24 subnets. You also know that in the future, additional 192.168.x.0/24 subnets will be added. Verify that all relevant OSPF adjacencies are still up and running for routers R1, R2, R3, and R4. Router R1 should have running OSPF adjacencies to routers R2, R3, R4, and BBR2. Router R3 should have running OSPF adjacency with router R1 only, whereas routers R2 and R4 should have OSPF adjacency running between them and toward router R1. Examine the OSPF link-state databases on routers R1, R2, R3, and R4 and verify that the relevant information is in the databases. Verify that the best path information has been put into the router IP routing tables. Verify that the routing information for the external networks 192.168.x.0/24 is presented as summary information in the OSPF link-state database and in the IP routing tables on relevant routers; in other words, verify that the OSPF required information is really minimized. Verify that all the routers have IP connectivity to the pod external networks 192.268.x.0/24, which were redistributed on router R4.
Lab Guide
165
Device Information
Command List
Command router ospf 1 show ip ospf interface show ip ospf neighbor show ip ospf database show ip route [ospf] area range summary-address (OSPF) Ping Description Turns on OSPF; the process number is not communicated to other routers Displays information about interfaces configured for OSPF Displays a list of OSPF neighbors Displays information about the OSPF database Displays the entire IP routing table or OSPF routes only Consolidates and summarizes routes at an area boundary Creates an aggregate address for OSPF Diagnoses basic network connectivity
Required Resources
166
Job Aids
Lab Guide
167

The first step in your configuration deployment is to establish a list of what is needed in order for you to configure each device; for example, device names, trunk encapsulation types, and so on. Use the following table, the visual objective at the beginning of this lab, the implementation policy, and the device information to create your implementation requirements list. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
168
Lab Guide
169

170
Complete
Device
Order
Lab Guide
171

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
173

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
175
Hints
Lab 3-3 Hint Sheet: Configure and Verify OSPF Route Summarization for Interarea and External Routes
Device ALL ALL ALL Implementation Requirement Identify the networks that are advertised by all routers. Identify the existing OSPF configuration. Identify the subnets that can be summarized and define a summary address. Lab Lab Lab Hint
R1R4
All pod routers must be preloaded with the initial configuration for the lab. Examine the OSPF routing configuration on all routers. First explore the OSPF adjacencies to gain insight into how OSPF is deployed in the network. Also observe the OSPF area configuration in order to learn the OSPF architecture and topology. Verify the router R1, R2, R3, and R4 IP routing tables to see whether the correct information was put into the routing tables.
Step 1
R1R4
Step 2.1
R1R4
2.2
176
Complete
Device
Order
Step
R1
Apply OSPF internal route summarization for the IP subnet 172.30.10.0/24 received from router BBR1. Summarize the networks in summary route 172.30.0.0/16, which is announced into nonbackbone OSPF areas. Apply the appropriate OSPF configuration to summarize the external 192.168.x.0/24 subnets, which are redistributed and injected into the OSPF domain. Because you know that additional 192.168.x.0/24 subnets will be added in the future, apply the summarization so that all 192.168.x.0/24 subsets are summarized with one command only and that the OSPF routing optimization is maximized.
Examine the OSPF link-state databases on all routers and verify that the relevant information is in the databases. Verify that the OSPF internal route summarization is applied for the pod IP 172.30.x.0/24 subnets.
Step 3
R3
Examine the OSPF link-state database and IP routing table on all routers to verify that the relevant information is present. The routing information for the external 192.168.x.0/24 networks is presented as summary information in the OSPF link-state database and therefore in the IP routing tables on relevant routers. Verify that all the external 192.268.x.0/24 networks, which are redistributed on router R3, are reachable from router R4.
Step 4
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration. 2. Examine the OSPF routing information. 2.1. Examine the OSPF adjacencies and OSPF link-state database to gain insight into how OSPF is deployed in the network.


Lab Guide 177

178


Lab Guide 179
2.2. Verify that the correct information was added to the router R1, R2, R3, and R4 IP routing tables.

3. Summarizing the OSPF internal routes. 3.1. Use the following example to configure router R1 in this lab:

3.2. Verify the OSPF link-state databases and IP routing tables.

Lab Guide
181

182


4. Summarizing OSPF external routes. 4.1. Use the following example to configure router R3 in this lab:

4.2. Verify the OSPF link-state databases and IP routing tables.

184



186


188
Lab Guide
189
Lab 3-4: Configure and Verify OSPF Special Area Types

Activity Objective
In this activity, you will use the correct commands, tools, and steps to configure and verify OSPF multiarea routing and optimize OSPF routing by implementing different OSPF special area types. After completing this activity, you will be able to meet these objectives: Configure and verify the OSPF operation over LAN and WAN interfaces in multiple OSPF areas Optimize the OSPF operation by implementing OSPF database optimization using special OSPF area types. Select the required tools and commands to configure OSPF operations Make a list of configuration and implementation steps Write a verification and test plan to verify the proper implementation and operation according to the expected performance criteria. Verify the configuration and operation by using the proper show and debug commands
Information Packet
Visual Objective
Visual Objective for Lab 3-4: Configure and Verify OSPF Special Area Types
ROUTE v 1. 0LG-14
190
The following list details the configuration requirements for all devices in the company network: In this task you will examine IP routing information exchanged by routers configured with the OSPF routing protocol. Routers R1, R2, R3, and R4 are configured with the OSPF routing protocol and announce their directly attached networks. Router R4 also announces some external OSPF networks into the OSPF routing domain. Learn about the current OSPF configuration, which includes the information about the networks that are included in the OSPF routing domain, interfaces where OSPF is enabled, OSPF adjacencies, link-state databases, and OSPF area design. Verify that all the routers have IP connectivity to the advertised networks. Examine the IP routing table, write down the IP networks that are advertised, and determine the IP addressing scheme. In this task, you must optimize OSPF routing inside Area 24. Routers R2 and R4 have insufficient CPU and memory resources to cope with the amount of routing information that is advertised in the OSPF domain. You must reduce the size of the OSPF link-state database on routes R2 and R4 to preserve their resources. Verify that OSPF adjacencies in the OSPF domain are operational. Router R1 should have OSPF adjacency with routers R2, R3, R4, and BBR2. Routers R2 and R4 should also have adjacency set between them. Examine the OSPF database on routers R1 and R3 and verify that they still have all the specific information about OSPF internal and external routes of your OSPF domain. Also verify that the IP routing tables are populated with the best paths to all destination networks. Examine the OSPF database on routers R2 and R4 and verify that the size of the database is smaller because they do not hold the specific information about the IP subnets that are external to the OSPF domain; in other words, those that are redistributed somewhere in the OSPF domain. Verify that routers R2 and R4 have the information necessary to reach the external networks. Verify that routers R2 and R4 have IP connectivity to the destinations from the IP subnets that are external to the OSPF domain. In this task you must minimize OSPF link-state database information inside Area 24. Although you optimized OSPF Area 24 operation in the previous task to preserve R2 and R4 resources, you have seen that they still cannot hold all the information that is advertised in the OSPF domain. Therefore, you must further reduce the amount of OSPF information on those routers while preserving the IP connectivity to the destinations located on all networks that are not attached to routers R2 and R4. Verify that OSPF adjacencies in the OSPF domain are operational. Router R1 should have OSPF adjacency with routers R2, R3, R4, and BBR2. Routers R2 and R4 should have additional adjacency set between them. Examine the OSPF database on routers R1 and R3 and verify that they still have all the specific information about OSPF internal and external routes of your OSPF domain. Also verify that the IP routing tables are populated with the best paths to all destination networks. Examine the OSPF databases on routers R2 and R4 and verify that the size of the databases is smaller because they do not hold the specific information about the IP subnets that are external to OSPF Area 24; in other words, those IP networks that are redistributed somewhere in the OSPF domain and those IP networks that are internal to OSPF but are part of other OSPF areas. Verify that routers R2 and R4 have the information necessary to reach all the networks. Verify that routers R2 and R4 have IP connectivity to the destinations from all the IP subnets that are announced in the OSPF domain.
Lab Guide
191
In this task you will have to minimize the OSPF and IP routing information inside Area 3. You have noticed that router R3 does not have sufficient memory capacity to store all the OSPF an IP routing information. In other words, the OSPF link-state database, and consequently the IP routing table, cannot store all the dynamically acquired IP routing information. Verify that OSPF adjacencies in the OSPF domain are operational. Router R1 should have an OSPF adjacency with routers R2, R3, R4, and BBR2. Routers R2 and R4 should have an additional adjacency set between them. Examine the OSPF database on router R1 and verify that it still has all the specific information about the OSPF internal and external routes of your OSPF domain. Also verify that the IP routing table is populated with the best paths to all destination networks. Verify that router R1 can access all the networks that are announced in the OSPF domain. Examine the OSPF databases on routers R2 and R4 and verify that they still have all the specific information about the OSPF internal routes from Area 24, while the information about the other networks is not present, and external routes of your OSPF domain. Also verify that the IP routing table is populated with the proper IP routing information. Verify that routers R2 and R4 can access all the networks that are advertised in the OSPF domain. Examine the OSPF database on router R3 and verify that the database size has been reduced. Verify that the router has the information about all the OSPF Area 3 internal router as well as the external routes that are redistributed in the area. At the same time, the router should not have any information about the routes that are external to OSPF Area 3. Verify that you still have IP connectivity to all networks announced that are announced by OSPF from router R3.
Device Information
Device name R1 R2 R3 R4 BBR2 Role POD router POD router POD router POD router Backbone router
192
Command List
Command router ospf 1 show ip ospf database show ip route [ospf] show ip ospf area stub area nssa Ping Description Turns on OSPF; the process number is not communicated to other routers Displays information about OSPF database Displays whole IP routing table or OSPF routes only Displays general information about OSPF routing processes Defines an area as a stub area Configures an area as a not-so-stubby area (NSSA) Diagnoses basic network connectivity
Required Resources
Job Aids
Lab Guide
193

The first step in your configuration deployment is to establish a list of what is needed in order for you to configure each device; for example, the device names and trunk encapsulation types. Use the following table, the visual objective at the beginning of this lab, the implementation policy, and the device information to create your implementation requirements list. If you are unsure, you can use the information provided in the Hints section at the end of this lab.
194
Lab Guide
195

196
Complete
Device
Order
Lab Guide
197

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
199

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
201
Hints
Lab 3-4 Hint Sheet: Configure and Verify OSPF Special Area Types
Device ALL Implementation Requirement Identify the networks that are advertised by all routers. Find internal as well as external networks. Identify the existing OSPF configuration. Lab Hint
ALL
Lab
R1R4
All pod routers must be preloaded with the initial configuration for the lab. Examine the OSPF routing configuration on all routers. First explore the OSPF link-state database to gain insight into how OSPF is deployed in the network. Also observe the OSPF area configuration to learn the OSPF architecture and topology. Verify the IP routing tables for routers R1, R2, R3, and R4 to see whether the correct information was put into the routing tables and that external networks are in the IP routing table.
Step 1
R1R4
Step 2.1
R1R4
Step 2.2
202
Complete
Device
Order
Step
R1, R2, R4
Prevent OSPF from announcing information about the OSPF external routers into Area 24. Connectivity to external routes 192.168.x.0/24 should be preserved and routers R2 and R4 should still be able to access those networks. Remember that routers R2 and R4 should have specific information about those networks that are internal to the OSPF domain regardless of where they are injected into the OSPF domain.
Examine the OSPF database on routers R2 and R4 and verify that the size of the database is smaller than before because they do not hold specific information about the IP subnets that are external to the OSPF domain; that is, those that are redistributed somewhere in the OSPF domain. Verify that routers R2 and R4 have the necessary information on how to reach the external networks. Verify that routers R2 and R4 have IP connectivity to the destinations from the IP subnets that are external to the OSPF domain. Examine the OSPF database on routers R2 and R4 and verify that the size of the database is smaller than before because they do not hold the specific information about the IP subnets that are interarea and external to the OSPF domain. Verify that routers R2 and R4 have the necessary information on how to reach the interarea and external networks. Verify that routers R2 and R4 have IP connectivity to the destinations from the IP subnets that are external to the OSPF domain.
Step 3
R1, R2, R4
Prevent OSPF from announcing information about the OSPF internal routers from other OSPF areas into Area 24. Connectivity to all external routes 192.168.x.0/24 and internal routes from other areas should be preserved; that is,routers R2 and R4 should still be able to access those networks. Remember that routers R2 and R4 should have specific information about those networks that are internal to the OSPF Area 24.
Step 4
Lab Guide
203
Complete
Device
Order
Step
R1, R3
Minimize the OSPF link-state database and IP routing table on router R3 inside Area 3. The router R3 OSPF database, and consequently the IP routing table, should have information only about the OSPF Area 3 announced routes, whether internal or external. Preserve the redistribution of external routes 192.1658.x.0/24 on router R3; that is, the router should still announce those networks into the OSPF domain. Remember that router R3 should also preserve connectivity to all subsets announced by OSPF.
Examine the OSPF database on router R1 and verify that it still has all the specific information about the internal and external OSPF routes of your OSPF domain. Also verify that the IP routing table is populated with the best paths to all destination networks. Examine the OSPF database and IP routing table on router R3 and verify that the database size and the size of the IP routing table have been reduced. The router should not have any information about the routes that are external to OSPF Area 3. Verify that you still have IP connectivity from router R3 to the LAN segment between routers R2 and R4.
Step 5
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration. 2. Examine the OSPF routing information. 2.1. Examine the OSPF link-state database to gain insight into how OSPF is deployed in the network.

204


Lab Guide 205

206

2.2. Verify the IP routing table.

Lab Guide
207
3. Optimize OSPF routing for Area 24 using stub area type. 3.1. Use the following example to configure routers R1, R2, and R4 in this lab:

3.2. Verify the OSPF database, IP routing table, and check for connectivity to external networks.


210
Lab Guide
211
4. Optimize OSPF routing for Area 24 using stub area type. 4.1. Use the following example to configure router R1 in this lab:

4.2. Verify the OSPF database, IP routing table, and check for connectivity to external networks.



Lab Guide
215
5. Reduce the OSPF information in Area 3. 5.1. Use the following example to configure router R1 in this lab:

5.2. Verify the OSPF database, IP routing table, and check for connectivity to the external networks.



Lab Guide 217
218
Lab Guide
219
Lab 3-5: Configure and Verify OSPF Authentication

Activity Objective
Complete this lab activity to practice what you learned in the related module. In this activity, you will use correct commands, tools, and steps to configure and verify basic OSPF authentication implementation. After completing this activity, you will be able to meet these objectives: Select the required tools and commands to configure basic OSPF authentication Organize the tasks into an implementation plan to implement OSPF authentication Implement the identified OSPF solution to configure basic OSPF authentication in the provided network according to the implementation plan, using Cisco IOS commands and applications in the correct order to the selected devices and portions of the network Write a verification and test plan to verify correct implementation and operation according to the expected performance criteria Verify the implementation according to the verification plan, using the appropriate show and debug commands and applications to verify correct operation document implementation, operations, and maintenance
Information Packet
Visual Objective
Visual Objective for Lab 3-5: Configure and Verify OSPF Authentication
ROUTE v 1. 0LG-15
220
The following list details the configuration requirements for all devices in the company network: Set proper initial configuration on all devices in your lab. The instructor will provide the necessary information on how to set the initial configuration on all devices. When an existing topology needs to be fine tuned, the administrator first needs to review the existing routing configuration and policy. This requires that you review the router configuration and examine the routing behavior. Examine IP routing information exchanged by routers configured with OSPF routing protocol. Routers R1, R2, R3, and R4 are configured with the OSPF routing protocol and announce their directly attached networks. Router R4 also announces some external OSPF networks into the OSPF routing domain. Once the existing topology and operation is discovered, the administrator can address and adjust the operation so that it is more precise. The security of the routing information must be properly addressed. The administrator should deploy a configuration that prevents traffic hijacking and black-hole routing caused by counterfeit routing information that is injected into the routing domain by a malicious attacker. This is achieved by deploying routing authentication, and OSPF can be affected. OSPF authentication offers very granular authentication, which is deployed on a per-interface basis. Address the OSPF routing security in OSPF Areas 3 and 24. You have decided to apply simple OSPF authentication between routers R3 and R1 to examine how authentication is working. At the same time you are concerned with the LAN segment between routers R2 and R4 and have decided to implement link authentication on that segment also. The most secure OSPF authentication should be deployed. OSPF authentication configuration and deployment can be eased by deploying area-based authentication. The area-based authentication mechanism utilizes the OSPF deployment specific the routing topology deployed in areas. In this task you will address the OSPF routing security in OSPF Area 24. You have decided to scale the authentication in that area by deploying authentication on the LAN segment between routers R2 and R4 and on other Area 24 interfaces and segments. Verify the IP routing table, OSPF routing domain, interfaces where OSPF is enabled, OSPF adjacencies, link-state databases, and OSPF area design after each task in order to verify proper configuration.
Device Information
Lab Guide
221
Command List
Command ip ospf authentication ip ospf authentication-key Description Specifies the authentication type for an interface Assigns a password to be used by neighboring routers that use Open Shortest Path First (OSPF) simple password authentication Enables Open Shortest Path First (OSPF) Message Digest 5 (MD5) authentication Enables authentication for an OSPF area Displays general information about Open Shortest Path First (OSPF) routing processes Displays lists of information related to the Open Shortest Path First (OSPF) database for a specific router Displays whole IP routing table or OSPF routes only Displays Open Shortest Path First (OSPF) neighbor information on a per-interface basis Displays Open Shortest Path First (OSPF)-related interface information
ip ospf message-digest-key md5 area authentication show ip ospf show ip ospf database show ip route [ospf] show ip ospf neighbor
show ip ospf interface
Required Resources
Job Aids
Value Blank implementation requirements list Blank implementation and verification plan form Blank verification notes form Alternate resources and solutions form Implementation requirements hints Implementation and verification plan hints Solution configuration answer key (step-bystep procedure) Location Task 1 Task 2 Task 3 End of this lab Hints section at the end of this lab Hints section at the end of this lab Configuration section at the end of this lab
222

Lab Guide
223
224

Lab Guide
225
Complete
Device
Order
226

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
228

Other groups may have implemented a solution different from yours. These will be discussed during the debriefing period that will follow this lab. Use the following space to document other possible solutions for your reference. __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
230
Hints
Lab 3-5 Hint Sheet: Configure and Verify OSPF Authentication

Device ALL ALL ALL Implementation Requirement Interfaces involved in OSPF authentication Authentication type used on the interface Authentication key used for authentication Hint Visual Objective Implementation Policy Implementation Policy
R1R4
All pod routers must be preloaded with the initial configuration for the lab. Examine the OSPF routing configuration on all routers. First explore the OSPF linkstate database to gain insight into how OSPF is deployed in the network. Also observe the OSPF area configuration to determine the OSPF architecture and topology. Verify the IP routing tables for routers R1, R2, R3, and R4 to see whether the correct information was put into the routing tables and that external networks are inside the IP routing table.
Step 1
R1R4
Step 2
Lab Guide
231
Complete
Device
Order
Step
R1, R3
Deploy OSPF link authentication between routers R1 and R3 on the WAN segment. Remember that router R3 should not use encrypted keys for the OSPF authentication. Deploy OSPF link authentication between routers R2 and R4 on the LAN segment. Deploy the most secure OSPF authentication. Examine OSPF adjacencies and verify that all the adjacencies that were up before implementing OSPF link authentication are still up and running. Router R1 should have OSPF adjacencies to routers R2, R3, R4, and BBR2. Routers R2 and R4 should have an additional adjacency between them.
Step 3
R2, R4
Step 3
R2, R4
Change the OSPF authentication on routers R2 and R4 so that they enforce the OSPF authentication on all OSPF-enabled interfaces. Remember that the configuration must be implemented with a minimum number of commands, and that if an additional interface is added to Area 24, the OSPF authentication should automatically be enforced on that interface also without having to apply additional commands. Deploy OSPF authentication on router R1 for Area 24 also. The authentication should use the most secure method available. Examine OSPF adjacencies and interfaces in order to verify that all the adjacencies that were up before implementing OSPF link authentication are still up and running. Router R1 should have OSPF adjacencies to routers R2, R3, R4, and BBR2. Routers R2 and R4 should have an additional adjacency between them.
Step 4
R1
Step 4
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration.
232
2. Examine the OSPF routing information by verifying the OSPF link-state database to gain insight into how OSPF is deployed in the network, and to check the OSPF process and IP routing table.

Lab Guide
233

Lab Guide
235
236

Lab Guide 237

3. Enable OSPF link authentication. 3.1. Use the following example to configure the routers in this lab:

3.2. Verify that the authentication is successfully configured.

4. Enable OSPF area authentication. 4.1. Use the following example to configure routers R2 and R4 in this lab:


4.3. Verify that the authentication is successfully configured.



244
Lab Guide
245
Lab 4-1: Configure Route Redistribution Between Multiple IP Routing Protocols

Activity Objective
In this activity, you will use correct commands, tools, and steps to configure and verify route redistribution between multiple IP routing protocols. After completing this activity, you will be able to meet these objectives: Configure and verify different routing protocols in the network Select the required tools and commands to configure redistribution between different routing protocols Make a list of configuration and implementation steps Write a verification and test plan to verify the proper implementation and operation according to the expected performance criteria. Verify the configuration and operation by using the proper show and debug commands
Information Packet
Visual Objective
Visual Objective for Lab 4-1: Configure Route Redistribution Between Multiple IP Routing Protocols
ROUTE v 1. 0LG-16
246
The following list details the configuration requirements for all devices in the company network: Set proper initial configuration on all devices in your lab. The instructor will provide the necessary information on how to set initial the configuration on all devices. Multiple routing protocols must be deployed in your network. RIPv2, EIGRP, and OSPF must be configured in order to start the redistribution. Routers R3 and R1 will use the RIPv2 routing protocol to exchange routing information. Routers R1, R2, and R4 will use the OSPF routing protocol to exchange routing information, and router R1 will use EIGRP to exchange routing information with router BBR2. Configuration must be verified in order to proceed to the next step. Verify that the RIPv2 protocol is running between routers R1 and R3. Make sure that router R1 can access the RIPv2-announced routes from router R1. Verify that the EIGRP routing protocol is up and running between routers R1 and BBR2. Make sure that router R1 receives routes announced by BBR2 and that these routes are accessible. Examine and verify that the OSPF routing protocol is up and running between routers R1, R2, and R4. Make sure that routers have established the adjacencies and that R1has received the IP subnet from the LAN segment between routers R2 and R4. Verify that R1 has connectivity to the networks. After successful configuration of the routing protocols, redistribution must take place. Redistribute connected loopback interfaces in RIP to announce them to router R1. Configure the RIP-to-EIGRP redistribution with filtering to allow access to only one of the loopback interfaces. Because the RIP-to-EIGRP redistribution will be in one direction only (one way), you must configure a static default route on router R3 to provide connectivity to selected RIPv2 routing domain routes. Examine the RIPv2 database on routers R1 and R3 and verify that the R3 loopback networks are present in the RIP table as a result of redistribution. Add an additional loopback network to router R3 and verify that the network is not redistributed into RIPv2, and that router R1 does not receive that information. Verify that you have connectivity from router R3 to the BBR2 LAN segment. The next task to be preformed is the configuration of the redistribution between the OSPF and EIGRP domains. You will deploy two-way redistribution to achieve full IP connectivity between the routing domains. Additionally you will configure two-way redistribution between the OSPF and RIP routing domains. Examine the RIP routing information on router R3 and verify that the routes from the OSPF routing domain are present in the RIP database and IP routing table. The EIGRP topology table on router R1 must contain routes that originated in OSPF. Verify that the OSPF database and IP routing table on routers R2 and R4 hold the information about the RIP and EIGRP redistributed routes. Verify that you have connectivity from the R2 LAN segment to the BBR2 LAN segment, and that there is connectivity from the R3 LAN segment to the R2 LAN segment.
Lab Guide
247
Device Information
248
Command List
Command router rip version network (RIP) [no] auto-summary (RIP) Description Configures the RIP routing process Specifies a RIP version used globally by the router Specifies a list of networks for the RIP routing process Restores the default behavior of automatic summarization of subnet routes into network-level routes Displays summary address entries in the RIP routing database entries; if relevant, displays whether routes are being summarized based upon a summary address Displays whole IP routing table Configures an OSPF routing process Configures the OSPF network type to a type other than the default for a given medium Specifies the interval between hello packets that the Cisco IOS software sends on the interface Configures the router to send a syslog message when an OSPF neighbor goes up or down Defines the interfaces on which OSPF runs and defines the area ID for those interfaces Display lists of information related to the OSPF database for a specific router Displays OSPF neighbor information on a per-interface basis Configures the EIGRP process Specifies the network for an EIGRP routing process Displays neighbors discovered by EIGRP Displays entries in the EIGRP topology table Redistributes routes from one routing domain into another routing domain Filters networks received in updates Suppresses networks from being advertised in updates Creates a prefix list or adds a prefix list entry Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing Sets metrics for the EIGRP Establishes static routes Diagnoses basic network connectivity Configures an OSPF routing process
show ip rip database show ip route Router ospf ip ospf network point-tomultipoint ip ospf hello-interval log-adjacency-changes network area Show ip ospf database Show ip ospf neighbor Router eigrp network (EIGRP) Show ip eigrp neighbors Show ip eigrp topology redistribute (IP) distribute-list in (IP) distribute-list out (IP) ip prefix-list route-map default-metric (eigrp) ip route ping router ospf 1
Lab Guide
249
Required Resources
Job Aids
250
Lab Guide
251

252
Lab Guide
253

254
Complete
Device
Order
Lab Guide
255

Now that you have collected all the requirements and planned your implementation, you are ready to connect to the remote lab and implement your solution. Do not forget to save. Once your solution is implemented, you need to verify that your configuration is working and fulfills all the requirements specified by the customer. Keep in mind that once you leave the company, a network specialist will verify your configuration. Your ability to implement the solution according to the customer specifications will determine whether you get the job or not. Use the following area to record your notes and document the verifications you conducted to ensure that your solution is complete. If you are unsure about the verification steps, use the information provided in the Hints section at the end of this lab. Student Notes: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
256

Other groups may have implemented a solution that is different from yours. These will be discussed during the debriefing period that will follow this lab. Use the following space to document other possible solutions for your reference. __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
257
Hints
Lab 4-1 Hint Sheet: Configure Route Redistribution Between Multiple IP Routing Protocols
Device ALL ALL ALL Implementation Requirement Interfaces involved in routing protocol configuration Where redistribution takes place What needs to be redistributed Hint Visual Objective Implementation Policy Implementation Policy
R1R4
All pod routers must be preloaded with the initial configuration for the lab. Examine and verify that the RIPv2 protocol is running between routers R1 and R3. Make sure that router R1 can access the RIPv2-announced routes from router R1. Examine and verify that the EIGRP routing protocol is up and running between routers R1 and BBR2. Make sure that router R1 receives routes announced by BBR2 and that these routes are accessible.
Step 1
Configure the RIPv2 routing protocol on routers R1 and R3 and advertise the R3 LAN segment. Routers should exchange RIPv2 only over the WAN segment that interconnects them.
Step 2
Configure routers R1, R2, and R4 to exchange routing information using OSPF. On router R1, the process should include only the WAN segment that connects router R1 to routers R2 and R4. Routers R2 and R4 should also include the LAN segment in the OSPF process. Only a single area should be deployed.
Step 3
258
Complete
Device
Order
Step
Configure the EIGRP routing protocol on router R1 and include only the interface that connects router R1 to router BBR2. BBR2 is preconfigured with EIGRP AS 1.
Examine and verify that the OSPF routing protocolsis up and running between routers R1, R2, and R4. Make sure that the routers have established adjacencies and that R1 has received the IP subnet from the LAN segment between routers R2 and R4. Verify that R1 has connectivity to the networks. Examine the RIPv2 database on routers R1 and R3 and verify that R3 loopback networks are present in the RIP table as a result of redistribution.
Step 4
Redistribute the IP subnets configured on the loopback interfaces on router R3 into the RIPv2 routing domain. Only IP subnets that are currently configured on the existing loopback interfaces should be redistributed, even if new subnets are added in the future. Do not use an access list or route maps to accomplish filtering. Redistribute RIPv2 routes to the EIGRP routing domain on router R1. Make sure that after the redistribution, only the 192.168.1.0/24 loopback networks is redistributed into the EIGRP routing domain and not any other R3-deployed loopback network. You cannot use distribute lists to provide filtering upon redistribution.
Step 5
Add an additional loopback network to router R3 and verify that the network is not redistributed into RIPv2 and that router R1 does not receive that information. Examine the IP routing tables on routers R1 and R3 and confirm that the requested routes are present. Verify that you have connectivity from router R3 to the router BBR2 LAN segment. Examine the EIGRP topology table on router R1 and confirm that OSPF-originated routes are present.
Step 6
Configure a static route on router R3 to establish connectivity in the opposite direction. Redistribute routing information from OSPF to the EIGRP routing domain and vice versa on router R1.
Step 7
Step 8
Lab Guide
259
Complete
Device
Order
Step
Redistribute from the OSPF to the RIP routing domain and vice versa. Make sure that only RIP-originated routes are redistributed into the OSPF domain and that only OSPF-originated routes are redistributed into the RIP routing domain.
Examine the RIP routing information on router R3 and verify that routes from the OSPF routing domain are present in the RIP database and IP routing table. Verify that the OSPF database and IP routing table on routers R2 and R4 contain the information about the RIP and EIGRP redistributed routes. Verify that you have connectivity from the R2 LAN segment to the BBR2 LAN segment. Verify that you have connectivity from the R3 LAN segment to the R2 LAN segment.
Step 9
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration. 2. Enable the RIP routing protocol. 2.1. Use the following example to configure the routers in this lab:

2.2. Verify that RIP is successfully configured.

3. Enable the OSPF routing protocol. 3.1. Use the following example to configure the routers in this lab:

3.2. Verify that OSPF is successfully configured.

262


4. Enable the EIGRP routing protocol. 4.1. Use the following example to configure the routers in this lab:

4.2. Verify that EIGRP is successfully configured.

5. Enable redistribution into the RIP routing protocol.

5.1. Use the following example to configure the routers in this lab:

5.2. Verify that redistribution is successfully configured.

6. Enable redistribution into the EIGRP routing protocol. 6.1. Use the following example to configure the routers in this lab:


7. Enable additional connectivity. 7.1. Use the following example to configure router R3 in this lab:


8. Configure redistribution between OSPF and EIGRP. 8.1. Use the following example to configure router R1 in this lab:


Lab Guide 267
9. Configure redistribution between OSPF and RIP. 9.1. Use the following example to configure router R1 in this lab:


Lab Guide
269
270
Lab 5-1: Configure and Verify Path Control Between Multiple IP Routing Protocols
Activity Objective
In this activity, you will use correct commands, tools, and steps to configure and verify path control between multiple routing protocols. After completing this activity, you will be able to meet these objectives: Configure and verify policy-based routing Select the required tools and commands to configure PBR operations Make a list of configuration and implementation steps Write a verification and test plan to verify the proper implementation and operation according to the expected performance criteria. Verify the configuration and operation by using the proper show and debug commands
Information Packet
Visual Objective
Visual Objective for Lab 5-1: Configure and Verify Path Control Between Multiple IP Routing Protocols
ROUTE v 1. 0LG-17
Lab Guide
271
The following list details the configuration requirements for all devices in the company network: Begin by deploying the EIGRP routing protocol in your network to achieve full IP connectivity. Routers R1, R2, R3, and R4 will form EIGRP adjacencies and exchange IP routing information to achieve a converged IP routing topology. Examine and verify that the EIGRP routing protocol is up and running between routers R1, R2, R3, and R4. Verify that the router R1, R2, R3, and R4 routing tables are populated with the required networks. Examine the path of IP packets sourced from SW1 destined to networks 192.168.1.0/24 and 192.168.2.0/24. Examine the path of IP packets sourced locally from router R2 destined to network 192.168.3.0/24. The destination-based forwarding and reachability provided by EIGRP is not sufficient for all traffic. You will deploy source-based IP routing using policy-based routing. You will change default IP routing decisions based on the EIGRP-acquired routing information for selected IP source to IP destination flows and apply a different next hop router. Change the policy on router R3 so that IP traffic that is sourced from switch SW1 IP address 172.30.13.11 and sent to networks 192.168.1.0/24 and 192.168.2.0/24 will select R1 as a next hop. Change the policy on router R1 so that locally originated traffic sent to network 192.168.3.0/24 will select router R3 as the next hop rather than router R2. Examine and verify that traffic originated from switch SW1 that is sent to networks 192.168.1.0/24 and 192.168.2.0/24 takes the path R3-R1-R2-R4 using policy-based routing. Examine and verify that policy-based routing is in effect on router R3. Verify that traffic originated from switch SW1 that is sent to other networks is not policy routed and takes the path governed by the EIGRP-selected best path. Verify that locally originated traffic on router R1 that is sent to 192.168.3.0/24 travels on the path R3-R4 instead of the path R2R4. Verify that policy-based routing is in effect on router R1 for locally originated traffic sent to network 192.168.3.0/24 only, and that for the other type of traffic, the normal EIGRP-governed path is selected.
Device Information
272
Command List
Command show ip route Router eigrp network (EIGRP) [no] auto-summary (EIGRP) debug ip policy route-map ip policy route-map trace (privileged) ping Description Displays whole IP routing table Configures the EIGRP process Specifies the network for an EIGRP routing process Allows automatic summarization of subnet routes into networklevel routes Displays IP policy routing packet activity Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing Identifies a route map to use for policy routing on an interface Discovers the routes that packets will actually take when traveling to their destination Diagnoses basic network connectivity
Required Resources
Job Aids
Lab Guide
273
274

Lab Guide
275
276

Lab Guide
277
Complete
Device
Order
278

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
280

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
282
Hints
Lab 5-1 Hint Sheet: Configure and Verify Path Control Between Multiple IP Routing Protocols
Device ALL ALL ALL Implementation Requirement Define the EIGRP autonomous system number and the interfaces that must be part of the EIGRP Define networks advertised Define the preferred path for the packets Hint Implementation Policy Implementation Policy Implementation Policy
R1R4
All pod routers must be preloaded with the initial configuration for the lab. Examine and verify that the EIGRP routing protocol is up and running between routers R1, R2, R3, and R4 by verifying that the routers have their IP routing tables populated with the required networks. Examine the path of IP packets sourced from SW1 that are sent to networks 192.168.1.0/24 and 192.168.2.0/24. Verify reachability. Examine the path of IP packets sourced locally from router R2 that are sent to network 192.168.3.0/24.
Step 1
R1R4
Configure the EIGRP routing protocol on routers R1, R2, R3, and R4, and on all WAN, LAN, and loopback interfaces.
Step 2
Step 3
Lab Guide
283
Complete
Device
Order
Step
R3
Change the routing policy on router R3 for the IP traffic sourced from switch SW1 IP address 172.30.13.11 that is sent to networks 192.168.1.0/24 and 192.168.2.0/24 so that router R1 is selected as a next hop.
Examine and verify that traffic originated from switch SW1 that is sent to networks 192.168.1.0/24 and 192.168.2.0/24 takes the path R3-R1R2-R4 and uses policy-based routing. Examine and verify that policy-based routing is in effect on router R3. Examine and verify that locally originated traffic on router R1 that is sent to network 192.168.3.0/24 travels via router path R3-R4 instead of path R2-R4. Verify that policy-based routing is in effect on router R1 for locally originated traffic destined to network 192.168.3.0/24 only, and that for the other type of traffic, the normal EIGRPgoverned path is selected.
Step 4
R1
Change the routing policy on router R1 to force the locally originated traffic that is sent to network 192.168.3.0/24 to select router R3 as a next hop instead of router R2.
Step 5
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration. 2. Implement EIGRP routing. 2.1. Use the following example to configure the EIGRP routing protocol in the lab.

284
2.2. Verify that the EIGRP routing protocol is up and running between routers.

Lab Guide 285
3. Examine the path of the IP packets.

4. Implement PBR on router R3. 4.1. Use the following example to configure PBR on router R3 in the lab.

4.2. Verify the traffic flow from switch SW1 and PBR on R3.

Note Enable debugging in order to see the policy macth following the ping commands on pod switch SW1.

5. Implement PBR on router R1. 5.1. Use the following example to configure PBR on router R1 in the lab.

5.2. Verify the traffic flow and PBR on R1.

Note Enable debugging in order to see the policy match following the ping commands on pod router R1.
288
Lab Guide
289
290
Lab 6-1: Configure BGP Operations

Activity Objective
In this activity, you will use correct commands, tools, and steps to configure and verify BGP operations. After completing this activity, you will be able to meet these objectives: Configure and verify multihomed ISP connections Configure EBGP on the enterprise router to connect to the two ISPs Select the required tools and commands to configure EBGP operations Make a list of configuration and implementation steps Write a verification and test plan to verify the proper implementation and operation according to the expected performance criteria Verify the configuration and operation by using the proper show and debug commands
Information Packet
Visual Objective
Visual Objective for Lab 6-1: Configure BGP Operations
ROUTE v 1. 0LG-18
Lab Guide
291
The following list details the configuration requirements for all devices in the company network: Your first task will be to deploy the EBGP routing protocol in your pod. The network topology should consist of the following BGP autonomous systems: AS 130 with router R3 and switch SW1 as members AS 100 with router R1 as a member AS 200 with router R2 as a member AS 400 with router R4 as a member
AS 130 will have EBGP sessions to AS 100 and AS 200 in order to receive IP information about the networks in AS 200. Examine and verify that EBGP sessions have been set up and that the neighbors are ready to exchange IP routing information. Examine and verify that the EBGP session between router R3, R1, and R4 uses strong authentication. Configure the routers to announce selected networks via the BGP routing protocol to exchange IP routing information. The following should be done in order to announce the required routing information: Announce the 172.30.13.0/24 network from router R3 Announce the 10.3.3.3/32 network from router R3 Announce the 192.168.1.0/24, 192.168.2.0/24, and 192.168.3.0/24 networks from router R2
Device Information
292
Command List
Command router bgp [no] synchronization bgp log-neighbor-changes [no]auto-summary (BGP) neighbor remote-as neighbor password Show ip bgp summary show ip bgp neighbors show ip bgp network (BGP and multiprotocol BGP) redistribute (IP) route-map aggregate-address Description Configures the BGP routing process Enables the synchronization between BGP and the Interior Gateway Protocol (IGP) system Enables logging of BGP neighbor resets Configures automatic summarization of subnet routes into network-level routes Adds an entry to the BGP or multiprotocol BGP neighbor table Enables Message Digest 5 (MD5) authentication on a TCP connection between two BGP peers Displays the status of all BGP connections Displays information about BGP and TCP connections to neighbors Displays entries in the Border Gateway Protocol (BGP) routing table Specifies the networks to be advertised by the BGP and multiprotocol BGP routing processes Redistributes routes from one routing domain into another routing domain Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing Creates an aggregate entry in a BGP database
Required Resources
Lab Guide
293
Job Aids
Value Blank implementation requirements list Blank implementation and verification plan form Blank verification notes form Alternate resources and solutions form Implementation requirements hints Implementation and verification plan hints Solution configuration answer key (step-bystep procedure) Location Task 1 Task 2 Task 3 End of this lab Hints section at the end of this lab Hints section at the end of this lab Configuration section at the end of this lab
294

Lab Guide
295
296

Lab Guide
297
Complete
Device
Order
298

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
300

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
302
Hints
Lab 6-1 Hint Sheet: Configure BGP Operations

Device ALL Implementation Requirement Define BGP autonomous system numbers and assign them to routers Hint Implementation Policy Implementation Policy Visual Objective
ALL
Define the networks that will be advertised
Complete Device Order Values and items to Implement Verification Method and Expected Results Step
R1R4
Step 1
Lab Guide
303
Complete
Device
Order
Values and items to Implement
Step
R1R4
Enable BGP routing protocol on routers R1, R2, R3, and R4 and configure the following EBGP sessions: AS 130 to AS 100 between routers R3 and R1 AS 130 to AS 400 between routers R3 and R4 AS 200 to AS 100 between routers R2 and R1 AS 200 to AS 400 between routers R2 and R4 The BGP sessions between AS 130, AS 100, and AS 400 should be authenticated using the strongest possible authentication.
Examine and verify that EBGP sessions have been set up and that the neighbors are ready to exchange IP routing information. Examine and verify that the EBGP session between router R3, R1, and R4 uses strong authentication.
Step 2
R3
Enable router R3 to announce the connected network 172.30.13.0/24 to the neighboring autonomous systems via the EBGP sessions you set up in the previous task. The network should not be redistributed into BGP. Configure router R3 to announce the loopback network 10.3.3.3/32 to the neighboring autonomous systems 100 and 200 via the EBGP network. The network should be redistributed into BGP.
Step 3
R2
Configure router R2 to announce the 192.168.x.0/24 subnets to the neighboring autonomous systems via BGP. Instead of announcing individual 192.168.x.0/24 subnets, announce the 192.168.0.0/16 major network. The summary route should be advertised if at least one of the 192.168.x.0/24 subnets are present in the IP routing table of router R2.
Verify that routers R1, R2, and R4 have information about the 172.30.13.0/24 and 10.3.3.3/32 networks in their BGP and IP routing tables. Verify that routers R1, R3, and R4 have information about the 192.168.0.0/16 summary route in their BGP and IP routing tables.
Step 3
304
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration on all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration. 2. Configure EBGP. 2.1. Use the following example to configure the routers in this lab:

2.2. Verify that EBGP sessions have been set up.


306 Implementing Cisco IP Routing (ROUTE) v1.0

Lab Guide
307



Lab Guide 309




3. Announce networks into BGP. 3.1. Use the following example to configure router R3 in this lab:

3.2. Use the following example to configure router R2 in this lab.

3.3. Verify the BGP table in order to see announced routes.


Lab Guide 315
316
Lab 6-2: Manipulate EBGP Path Selections

Activity Objective
In this activity, you will use correct commands, tools, and steps to manipulate EBGP path selections. After completing this activity, you will be able to meet these objectives: Configure and verify policy-based routing Select the required tools and commands to configure PBR operations Make a list of configuration and implementation steps Write a verification and test plan to verify the proper implementation and operation according to the expected performance criteria. Verify the configuration and operation by using the proper show and debug commands
Information Packet
Visual Objective
Visual Objective for Lab 6-2: Manipulate EBGP Path Selections
ROUTE v 1. 0LG-19
The following list details the configuration requirements for all devices in the company network: In this task you will deploy the EBGP routing protocol in your pod. The network topology should consist of the following BGP autonomous systems:
AS 130 with router R3 and switch SW1 as members AS 100 with router R1 as a member AS 200 with router R2 as a member AS 400 with router R4 as a member
AS 130 will have EBGP sessions to AS 100 in order to receive IP information about the networks in AS 200. AS 200 should have EBGP sessions to AS 100 and AS 400 to exchange IP routing information. Change the default BGP path selection for the traffic from AS 103 that are sent to networks originated from AS 200. Change the primary path for the traffic that is returning to AS 130. Examine the EBGP adjacencies and verify that adjacencies are set up between the routers R1, R2, R3, and R4. Verify that the router IP routing tables are populated with the required networks. Examine the path of IP packets sourced from AS 130 that are sent to networks in AS 200. Examine the path of IP packets returning to AS 130 from AS 200. Deploy additional EBGP sessions in your pod. Establish the following additional EBGP adjacencies: AS 130 to AS 100 between switch SW1 and router R1 AS 130 to AS 400 between routers R3 and R4 AS 130 between router R3 and switch SW1
Delete the following EBGP sessions: AS 130 to AS 100 between routers R3 and R1
Influence AS 130 path selection to select the primary path out of the AS via router R4 in AS 400. Influence the path of the traffic coming into AS 130 from AS 200. The path via router R1 should be preferred. Examine the EBGP adjacencies and verify they are set up between the routers. Verify that the routers have their IP routing tables populated with the required networks. Examine the primary path out of AS 130. Examine and verify the path of IP packets coming into AS 130.
Device Information
318
Command List
Command router bgp [no] synchronization bgp log-neighbor-changes [no]auto-summary (BGP) neighbor remote-as show ip bgp summary show ip bgp network (BGP and multiprotocol BGP) show ip route neighbor route-map route-map Description Configures the BGP routing process Enables the synchronization between BGP and your Interior Gateway Protocol (IGP) system Enables logging of BGP neighbor resets Configures automatic summarization of subnet routes into network-level routes Adds an entry to the BGP or multiprotocol BGP neighbor table Displays the status of all BGP connections Displays entries in the Border Gateway Protocol (BGP) routing table Specifies the networks to be advertised by the BGP and multiprotocol BGP routing processes Displays whole IP routing table Applys a route map to incoming or outgoing routes Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing
Required Resources
Job Aids
Lab Guide
319
320

Lab Guide
321

322

__________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
324

Other groups may have implemented a solution different from yours. These will be discussed during the debriefing period that will follow this lab. Use the following space to document other possible solutions for your reference. __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________
Lab Guide
325
326
Hints
Lab 6-2 Hint Sheet: Manipulate EBGP Path Selections

Device ALL ALL Implementation Requirement Define BGP autonomous system numbers and assign them to routers Define the networks that will be advertised Hint Implementation Policy Implementation Policy Visual Objective ALL Define path manipulation rules Implementation Policy
R1R4
All pod routers must be preloaded with the initial configuration for the lab. Examine the EBGP adjacencies and verify they are set up correctly between the routers.
Step 1
R1R4
Establish the following EBGP adjacencies: AS 130 to AS 100 two EBGP sessions between routers R3 and R1 AS 100 to AS 200 between routers R1 and R2 AS 400 to AS 200 between routers R4 and R2
Step 2
Lab Guide
327
Complete
Device
Order
Step
The following networks should be announced: Announce the 172.30.13.0/24 network from router R3. Announce the 192.168.1.0/24, 192.168.2.0/24, and 192.168.3.0/24 networks from router R2. Change the default BGP path selection for the traffic from AS 103 that is sent to networks originated from AS 200. The path via 10.1.131.1 should be preferred over the second option, via 10.1.113.1. For the traffic that is returning to AS 130, the path via 10.1.131.1 should be the primary path. Establish the following additional EBGP adjacencies: AS 130 to AS 100 between switch SW1 and router R1 AS 130 to AS 400 between routers R3 and R4 AS 130 between router R3 and switch SW1 Delete the following EBGP sessions: AS 130 to AS 100 between routers R3 and R1 Influence AS 130 path selection to select the primary path out of the AS via router R4 in AS 400. Influence the path of the traffic coming into AS 130 from AS 200. The path via router R1 should be preferred.
Verify the BGP table to verify that all networks are announced.
Step 3
Verify the IP routing table and BGP table in order to see the advertised networks and the preferred path for the packets.
Step 4
Examine the EBGP adjacencies and verify that they are set up correctly between the routers.
Step 5
Verify the IP routing table and BGP table in order to see the advertised networks and the preferred path for the packets.
Step 6
Step-by-Step Procedure for Implementation and Verification 1. Load the initial configuration to all devices in your lab. 1.1. The instructor will provide guidelines for changing the initial configuration.
328
2. Establish EBGP adjacencies. 2.1. Use the following example to configure the routers in this lab:

2.2. Verify that the adjacencies are established.

Lab Guide
329
3. Announce the networks in BGP. 3.1. Use the following example to configure the routers in this lab:

3.2. Verify the BPG table for the announced networks:

4. Change the default BGP path selection. 4.1. Use the following example to configure the routers in this lab:

4.2. Verify the routing table for the preferred path of the packets.


332
5. Establish additional adjacencies and remove a few of them. 5.1. Use the following example to configure the routers in this lab:

5.2. Verify the preferred path of the packets.

6. Manipulate BGP path selection with local preference and AS path prepending. 6.1. Use the following example to configure the routers in this lab:

6.2. Verify the preferred path of the packets.

Lab Guide
335

336

Lab Guide
337
338
Answer Key
The correct answers and expected solutions for the activities that are described in this guide appear here.
Lab 1-1 Answer Key: Assess Skills for Implementing Complex Networks
When you complete this activity, your lab configuration will be similar to the results in the Hints section of Lab 1-1.
Lab 2-1 Answer Key: Configure and Verify EIGRP Operations

When you complete this activity, your lab configuration will be similar to the results here, with differences that are specific to your device or workgroup:





Lab 2-2 Answer Key: Configure and Verify EIGRP Circuit Emulation and Frame Relay Operations





Lab 2-3 Answer Key: Configure and Verify EIGRP Authentication







Lab 2-4 Answer Key: Implement and Troubleshoot EIGRP Operations


356



Lab 3-1 Answer Key: Configure and Verify OSPF to Improve Routing Performance






Lab 3-2 Answer Key: Implement and Verify OSPF Multiarea Routing





Lab 3-3 Answer Key: Configure and Verify OSPF Route Summarization for Interarea and External Routes






Lab 3-4 Answer Key: Configure and Verify OSPF Special Area Types






Lab 3-5 Answer Key: Configure and Verify OSPF Authentication



Lab Guide
385


Lab 4-1 Answer Key: Configure Route Redistribution Between Multiple IP Routing Protocols






Lab 5-1 Answer Key: Configure and Verify Path Control Between Multiple IP Routing Protocols






Lab 6-1 Answer Key: Configure BGP Operations






Lab 6-2 Answer Key: Manipulate EBGP Path Selections





Lab Guide
409



Lab Guide 411

Lab Guide
413

Implementing Cisco IP Routing

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Implementing Cisco IP Routing

Caricato da

Copyright:

Formati disponibili

ROUTE

Implementing Cisco IP Routing

2009 Cisco Systems, Inc. All Rights Reserved.

Students, this letter describes important course evaluation access information!

Planning Routing Services to Requirements

Assessing Complex Enterprise Network Requirements

Creating an Implementation Plan and Documenting the Implementation

Lab 1-1 Debrief

Implementing an EIGRP-Based Solution

Planning Routing Implementations with EIGRP

Lab 2-1 Debrief

Configuring and Verifying EIGRP for the Enterprise WAN Architecture

Lab 2-2 Debrief

Implementing Cisco IP Routing (ROUTE) v1.0

2009 Cisco Systems, Inc.

Implementing and Verifying EIGRP Authentication

Lab 2-3 Debrief

Advanced EIGRP Features in an Enterprise Network

Lab 2-4 Debrief

2009 Cisco Systems, Inc.

Implementing Cisco IP Routing (ROUTE) v1.0

Implementing Cisco IP Routing (ROUTE) v1.0

2009 Cisco Systems, Inc.

Student Skills and Knowledge

Learner Skills and Knowledge

2009 Cis co S y st em s, Inc. A ll right s reserved.

ROUTE v1. 00-3

Implementing Cisco IP Routing (ROUTE) v1.0

2009 Cisco Systems, Inc.

Course Goal and Objectives

Implementing Cisco IP Routing (ROUTE) v1.0

2009 Cis co S y st em s, Inc. A ll right s reserved.

ROUTE v1. 00-4

2008 Cisco Systems, Inc.

Module 1: Planning Routing Services to Requirements

Module 5: Implement Path Control

2009 Cis co S y st em s, Inc. A ll right s reserved.

ROUTE v1. 00-5

Implementing Cisco IP Routing (ROUTE) v1.0

2009 Cisco Systems, Inc.

ROUTE E-learning Modules

2009 Cis co S y st em s, Inc. A ll right s reserved.

ROUTE v1. 00-6

2008 Cisco Systems, Inc.

Cisco Icons and Symbols

2009 Cis co S y st em s, Inc. A ll right s reserved.

ROUTE v1. 00-7

Cisco Glossary of Terms

Implementing Cisco IP Routing (ROUTE) v1.0

2009 Cisco Systems, Inc.

Your Training Curriculum

Cisco Career Certifications

2008 Cisco Systems, Inc.

Cisco Career Certifications

2009 Cis co S y st em s, Inc. A ll right s reserved.

ROUTE v1. 00-9

Implementing Cisco IP Routing (ROUTE) v1.0

2009 Cisco Systems, Inc.

Cisco Career Certifications (cont.)

Additional Recommended Cisco Curriculum:

Related Cisco Career Certification:

Implement and troubleshoot IBGP solutions in your enterpri se network

CCIP CCNA-Wireless CCNA-Security

2009 Cis co S y st em s, Inc. A ll right s reserved.