Summary
In summary, we’ve looked at elements of advanced routing design, and we also touched on the merits of a well-planned IP addressing scheme. The IP addressing scheme is the foundation for greater efficiency in operating and maintaining a network. Without proper planning in advance, networks might not be able to benefit from route summarization features inherent to many routing protocols.
The general advanced routing design discussion can be encapsulated in the following key points that were discussed previously:
-
Route summarization and default routing are important in scaling routing designs.
-
Route filtering can be used to manage traffic flows in the network, avoiding inappropriate transit traffic and as a defense against inappropriate routing updates.
-
Redistribution can be useful for manipulating and managing routing updates, but needs to be designed properly to prevent routing loops or other problems.
EIGRP converges quickly as long as it has a feasible successor. With no feasible successor, EIGRP sends queries out to its neighbors. To limit the scope of these queries, use route summarization and filtering. By limiting EIGRP query scope, you can speed up EIGRP convergence and increase stability. In addition, large numbers of neighbors should be avoided for any one router. Multiple autonomous systems may be used with EIGRP providing that you understand that they do not directly limit EIGRP query scope. You would use them to support migration strategies, different administrative groups, or very large network design.
OSPF scaling depends on summarization and controlling how much LSA flooding is needed. Simple, stub, summarized designs scale most effectively. Several techniques speed up convergence for OSPF, including fast hellos, iSPF, and BFD.
Finally, IBGP requires a full mesh of all IBGP routers, but full-mesh peering does not scale gracefully. Route reflectors pass along routing information to and from their clients. The route reflector clients are relieved of the burden of most IBGP peering. Confederations allow an autonomous system to be divided into sub-autonomous systems, where the sub-autonomous system border routers peer with each other and then pass along routes on behalf of the other sub-autonomous system routers. Confederation sequences are used to prevent information loops. Sub-autonomous systems can have different BGP polices from each other.
Key points to remember include the following:
-
IP address design allows for route summarization that supports network scaling, stability, and fast convergence.
-
Route summarization, route filtering, and appropriate redistribution help minimize routing information in the network.
-
EIGRP converges quickly as long as it has a feasible successor. Multiple autonomous systems with EIGRP may be used, with care, to support special situations, including migration strategies and very large network design.
-
Simple, stub, summarized OSPF designs scale most effectively. Several techniques speed up convergence for OSPF, including fast hellos, iSPF, and BFD.
-
IBGP designs can be scaled using route reflectors to pass routing information to and from their clients and confederations to allow an autonomous system to be divided into sub-autonomous systems.
References
-
Cisco Systems, Inc. “Designing Large-Scale IP Internetworks,” at http://www.cisco.com/en/US/docs/internetworking/design/guide/nd2003.html
-
Cisco Systems, Inc. “Cisco IOS IP Routing Protocols Command Reference,” at http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_book.html
-
The Internet Engineering Task Force. RFC 1793: Extending OSPF to Support Demand Circuits, at http://www.ietf.org/rfc/rfc1793.txt
-
The Internet Engineering Task Force. RFC 2328: OSPF Version 2, at http://www.ietf.org/rfc/rfc2328.txt
-
The Internet Engineering Task Force. RFC 2796: BGP Route Reflection—An Alternative to Full Mesh IBGP, at http://www.ietf.org/rfc/rfc2796.txt
-
The Internet Engineering Task Force. RFC 3065: Autonomous System Confederations for BGP, at http://www.ietf.org/rfc/rfc3065.txt
-
The Internet Engineering Task Force. RFC 4136: OSPF Refresh and Flooding Reduction in Stable Topologies, at http://www.ietf.org/rfc/rfc4136.txt
Review Questions
Answer the following questions, and then refer to Appendix A, “Answers to Review Questions,” for the answers.
Answers
B, C. | |
A, B. | |
C. | |
A, D. | |
C. | |
A, B, D. | |
B. | |
A, C, D. |
0 comments
Post a Comment