400-007 practice question 26 of 35

Company XYZ is running OSPF in their network. They have merged with another company that is running EIGRP as the routing protocol. Company XYZ now needs the two domains to talk to each other with redundancy, while maintaining a loop free environment. The solution must scale when new networks are added into the network in the near future. Which technology can be used to meet these requirements?

Full set: 397 questions
Answer options
A: multipoint route-redistribution with route filtering using ACLs
B: DUMP multipoint route-redistribution with route filtering using route tags Correct answer
C: DUMPS single point route-redistribution with route filtering using route tags
D: DUMPS single point route-redistribution with route filtering using ACLs
Correct Answer:
B. DUMP multipoint route-redistribution with route filtering using route tags
Explanation

The scenario requires a redundant, loop-free, and scalable solution for mutual redistribution between OSPF and EIGRP. Multipoint redistribution is necessary to meet the redundancy requirement. To prevent routing loops in a scalable manner during mutual redistribution, route tags are the preferred method. When routes are redistributed from one protocol (e.g., EIGRP) into another (e.g., OSPF), they are "tagged." On another redistribution point, a route map is used to check for this tag and prevent the route from being redistributed back into its original domain (EIGRP), thus avoiding loops. This method is highly scalable as it does not require updating prefix lists or ACLs when new networks are added.

Why Incorrect

A. Using ACLs for filtering is not scalable. Each time a new network is added, the ACLs on all redistribution routers would need to be manually updated, increasing administrative overhead and the risk of errors.
C. Single-point redistribution creates a single point of failure, which violates the redundancy requirement of the design.
D. This option fails on two counts: single-point redistribution does not provide redundancy, and using ACLs for filtering is not a scalable solution for a growing network.

References

1. Cisco IOS XE IP Routing: OSPF Configuration Guide

"Redistributing Routing Protocols" Section: This guide details the process of redistribution and the tools available. It explains the use of route maps

which are essential for implementing tag-based filtering. The set tag and match tag commands within a route map are the mechanisms for this solution.

Reference: Cisco IOS XE IP Routing: OSPF Configuration Guide

Release 3S

"How to Redistribute Routing Protocols" -> "Examples: Route Map" section. This section demonstrates the configuration of route maps which are used to set and match tags.

2. Cisco IOS IP Routing: Protocol-Independent Configuration Guide

"Configuring Route Maps for Redistribution" Section: This document explicitly describes using route maps to control redistribution. It states

"A route map is used to control and modify routing information... For example

you can implement a policy to permit or deny routes from being redistributed based on a specific tag." This directly supports using tags for filtering.

Reference: Cisco IOS IP Routing: Protocol-Independent Configuration Guide

"Route Maps" chapter

section on "Route-Map Use Case for IP Routing".

3. Cisco Press

"Interdomain Multicast Routing: Practical Juniper and Cisco Solutions" by B. Fenner

et al. (Although a book

it's a peer-reviewed

highly technical publication often used in advanced networking curricula): While focused on multicast

the principles of inter-domain routing and loop prevention are universal. Chapter 3 discusses redistribution and the common pitfalls

including routing loops in multi-homed environments

advocating for mechanisms like route tagging over static prefix-lists for scalability and manageability.

Reference: Chapter 3

"Interdomain IP Multicast

" section on "Redistribution and Routing Loops."

Scroll to Top