没有合适的资源?快使用搜索试试~ 我知道了~
首页路由TCP/IP第二卷:专业发展指南
"《Routing TCP/IP》第二卷是Cisco专业发展系列的一部分,由Jeff Doyle(CCIE#1919)和Jennifer DeHaven Carroll(CCIE#1402)合著,于2001年4月11日出版。本书的ISBN号为1-57870-089-2,共976页,适合深入研究者使用,分两部分讲解。第一部分强调了内部网关协议的复杂性,如TCP连接、消息状态、路径属性以及与内部路由协议的协作,这些都是网络扩展时必备的路由器操作知识。 本书的核心内容涵盖了高级主题,包括BGP-4(边界网关协议第四版)的深入理解与实施,多播路由、网络地址转换(NAT)技术的应用,以及IPv6(互联网协议版本6)的策略和部署。Jeff Doyle以其实践导向的方法,结合易读的格式和全面的主题覆盖,使得这本书成为网络专业人员必备的经典参考书,无论对于初学者还是经验丰富的从业者,都能从中获益匪浅。 不同于第一卷专注于内部网关协议,第二卷进一步扩展,探讨了自治系统之间的路由策略,特别是外部网关协议的细节,以及如何处理不同网络间的路由选择和流量管理。此外,作者还讨论了有效的路由器管理和维护技术,这对于网络管理员来说是极其重要的,因为随着网络规模的增长,如何保持系统的稳定性和效率成为关键挑战。 总而言之,《Routing TCP/IP》第二卷不仅巩固了读者对TCP/IP路由的基础知识,还提供了处理现代网络复杂性所需的专业技能,是网络工程师和管理员不可或缺的工具书,有助于他们在面对日益增长的网络需求时做出明智决策并实现高效运维。"
资源详情
资源推荐
Command Syntax Conventions
The conventions used to present command syntax in this book are the same conventions used in the
IOS Command Reference. The Command Reference describes these conventions as follows:
● Vertical bars (|) separate alternative, mutually exclusive elements.
● Square brackets [ ] indicate optional elements.
● Braces { } indicate a required choice.
● Braces within brackets [{ }] indicate a required choice within an optional element.
● Boldface indicates commands and keywords that are entered literally as shown. In actual
configuration examples and output (not general command syntax), boldface indicates
commands that are manually input by the user (such as a show command).
● Italics indicates arguments for which you supply actual values.
Chapter 1. Exterior Gateway Protocol
This chapter covers the following key topics:
● The Origins of EGP— This section discusses the history of the development of the Exterior
Gateway Protocol, presented in RFC 827 (1982).
● Operation of EGP— This section explores the fundamental mechanics of EGP with a focus on
EGP topology issues, EGP functions, and EGP message formats.
● Shortcomings of EGP— This section explores some of the reasons why EGP is no longer
pursued as a viable external gateway protocol solution.
● Configuring EGP— This section presents four separate case studies—EGP stub gateway, EGP
core gateway, indirect neighbors, and default routes—to demonstrate different types of EGP
configuration.
● Troubleshooting EGP— This section examines how to interpret an EGP neighbor table and
presents a case study on the slow convergence speed of an EGP network to show why EGP is
no longer a popular option.
The first question knowledgeable readers will (and should) ask is "Why kill a few trees publishing a
chapter about an obsolete protocol such as the Exterior Gateway Protocol (EGP)?" After all, EGP has
been almost universally replaced by the Border Gateway Protocol (BGP). This question has two
answers.
First, although EGP is rarely used these days, it is still occasionally encountered. As of this writing,
for instance, you can still find EGP in a few U.S. military internetworks. As a CCIE, you should
understand EGP for such rare encounters.
Second, this chapter serves as something of a history lesson. Examining the motives for developing
an external gateway protocol and the shortcomings of the original external protocol provides a
prologue for the following two chapters. BGP will make more sense to you if you are familiar with the
roots from which it evolved.
The Origins of EGP
In the early 1980s, the routers (gateways) that made up the ARPANET (predecessor of the modern
Internet) ran a distance vector routing protocol known as the Gateway-to-Gateway Protocol (GGP).
Every gateway knew a route to every reachable network, at a distance measured in gateway hops.
As the ARPANET grew, its architects foresaw the same problem that administrators of many growing
internetworks encounter today: Their routing protocol did not scale well.
Eric Rosen, in RFC 827[1], chronicles the scalability problems:
● With all gateways knowing all routes, "the overhead of the routing algorithm becomes
excessively large." Whenever a topology change occurs, the likelihood of which increases with
the size of the internetwork, all gateways have to exchange routing information and
recalculate their tables. Even when the internetwork is in a steady state, the size of the
routing tables and routing updates becomes an increasing burden.
● As the number of GGP software implementations increases, and the hardware platforms on
which they are implemented become more diverse, "it becomes impossible to regard the
Internet as an integrated communications system." Specifically, maintenance and
troubleshooting become "nearly impossible."
● As the number of gateways grows, so does the number of gateway administrators. As a
result, resistance to software upgrades increases: "[A]ny proposed change must be made in
too many different places by too many different people."
The solution proposed in RFC 827 was that the ARPANET be migrated from a single internetwork to a
system of interconnected, autonomously controlled internetworks. Within each internetwork, known
as an autonomous system (AS), the administrative authority for that AS is free to manage the
internetwork as it chooses. In effect, the concept of autonomous systems broadens the scope of
internetworking and adds a new layer of hierarchy. Where there was a single internetwork—a
network of networks—there is now a network of autonomous systems, each of which is itself an
internetwork. And just as a network is identified by an IP address, an AS is identified by an
autonomous system number. An AS number is a 16-bit number assigned by the same addressing
authority that assigns IP addresses.
NOTE
Also like IP addresses, some AS numbers are reserved for private use. These
numbers range from 64512 to 65535. See RFC 1930 (www.isi.edu/in-
notes/rfc1930.txt) for more information.
Chief among the choices the administrative authority of each AS is free to make is the routing
protocol that its gateways run. Because the gateways are interior to the AS, their routing protocols
are known as interior gateway protocols (IGPs). Because GGP was the routing protocol of the
ARPANET, it became by default the first IGP. However, interest in the more modern (and simpler)
Routing Information Protocol (RIP) was building in 1982, and it was expected that this and other as-
yet-unplanned protocols would be used in many autonomous systems. These days, GGP has been
completely replaced by RIP, RIP-2, Interior Gateway Routing Protocol (IGRP), Enhanced IGRP
(EIGRP), Open Shortest Path First (OSPF), and Integrated Intermediate System-to-Intermediate
System (IS-IS).
剩余1067页未读,继续阅读
hpjack
- 粉丝: 0
- 资源: 3
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- JDK 17 Linux版本压缩包解压与安装指南
- C++/Qt飞行模拟器教员控制台系统源码发布
- TensorFlow深度学习实践:CNN在MNIST数据集上的应用
- 鸿蒙驱动HCIA资料整理-培训教材与开发者指南
- 凯撒Java版SaaS OA协同办公软件v2.0特性解析
- AutoCAD二次开发中文指南下载 - C#编程深入解析
- C语言冒泡排序算法实现详解
- Pointofix截屏:轻松实现高效截图体验
- Matlab实现SVM数据分类与预测教程
- 基于JSP+SQL的网站流量统计管理系统设计与实现
- C语言实现删除字符中重复项的方法与技巧
- e-sqlcipher.dll动态链接库的作用与应用
- 浙江工业大学自考网站开发与继续教育官网模板设计
- STM32 103C8T6 OLED 显示程序实现指南
- 高效压缩技术:删除重复字符压缩包
- JSP+SQL智能交通管理系统:违章处理与交通效率提升
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功