Table of Contents
Module 2 - Design the Network Structure
Section 5 - Select Routing and Bridging Protocols
Solution
The correct answers are selected in the pull-down menus.
1. This protocol sends routing updates every 10 seconds, which
can consume a large percentage of the
bandwidth on slow serial links.
2. This protocol limits the number of networks in a routing table
update to 50, which means in a large
internetwork many packets are required
to send the routing table.
3. This protocol does not support discontiguous subnets or variable-length
subnet masks.
4. This protocol can advertise seven services per packet, which causes
many packets on enterprise
internetworks with hundreds of services.
5. This protocol uses 14 bytes to define a route entry, so it
can send 104 routes in a 1500-byte packet.
6. This protocol should be recommended in hub-and-spoke topologies
with low bandwidth even though it
can be hard to maintain because it is not
dynamic.
7. This protocol is similar to OSI's IS-IS protocol except that
a hierarchical topology was not defined until
Version 1.1 of the routing protocol was specified
(which is supported in Cisco IOS Release 11.1).
8. This protocol supports route summarization but it must be
configured. It is not automatic. When route
summarization is not configured, if link flapping
occurs, a stream of updates is generated, causing
serious traffic and router CPU overhead.
9. If a customer is looking for ways to reduce WAN routing traffic
and is also considering tunneling in IP, you
could recommend this protocol.
10. This protocol can be compromised because the routing updates are easy
to read with a protocol analyzer
and an unsophisticated hacker can send
invalid routing updates that routers will accept.
11. Cisco refined the implementation of this protocol in May 1996 to increase
stability in environments with
many low-speed links in
NBMA WANs such as Frame Relay, ATM, or X.25 backbones, and in highly
redundant dense router-router peering
configurations.
12. If a customer wants a protocol with fast convergence that can scale
to hundreds of networks, and that will
fit well with a hierarchical topology,
you should recommend this protocol.
If you want to view the solutions at the same time, open a new browser
window, so you can view two windows at the same time.
Click on the Back button in your browser to review Section 5 of Module
2. If you are finished with that section, click
here if you are ready to advance to the case studies.
Copyright Cisco Systems, Inc. -- Version 2.0 7/98