Hub and Spoke

简介:
本文出自Simmy的个人blog:西米在线   http://simmyonline.com/archives/542.html
 
The Enhanced Interior Gateway Routing Protocol (EIGRP) Stub Routing feature
improves network stability, reduces resource utilization, and simplifies stub router
configuration.
 
Stub routing is commonly used in a hub and spoke network topology. In a hub and spoke
network, one or more end (stub) networks are connected to a remote router (the spoke)
that is connected to one or more distribution routers (the hub). The remote router is
adjacent only to one or more distribution routers. The only route for IP traffic to follow
into the remote router is through a distribution router. This type of configuration is
commonly used in WAN topologies where the distribution router is directly connected to
a WAN. The distribution router can be connected to many more remote routers. Often,
the distribution router will be connected to 100 or more remote routers. In a hub and
spoke topology, the remote router must forward all nonlocal traffic to a distribution
router, so it becomes unnecessary for the remote router to hold a complete routing table.

Generally, the distribution router need not send anything more than a default route to the
remote router.

When using the EIGRP Stub Routing feature, you need to configure the distribution and
remote routers to use EIGRP, and to configure only the remote router as a stub. Only
specified routes are propagated from the remote (stub) router. The router responds to
queries for summaries, connected routes, redistributed static routes, external routes, and
internal routes with the message "inaccessible." A router that is configured as a stub will
send a special peer information packet to all neighboring routers to report its status as a
stub router.

















本文转simmy51CTO博客,原文链接:http://blog.51cto.com/helpdesk/187889 ,如需转载请自行联系原作者
相关文章
|
存储 搜索推荐 API
传说中很厉害的SitecoreContent Hub到底是什么?
大热的CMS系统Sitecore,它其中有一项功能一直为人津津乐道,那就是Sitecore Content Hub(Sitecore 内容中心),它将企业的内容集中管理,尽可能地提高了全渠道互动和参与的机会,让企业多部门可以协同工作,不再处于信息的孤岛。
161 1
|
存储 JavaScript 前端开发
15个你应该知道的Github仓库
15个你应该知道的Github仓库
181 1
15个你应该知道的Github仓库
|
开发工具 数据安全/隐私保护 git
【Github】Git管理远程仓库
【Github】Git管理远程仓库
93 0
|
Shell 开发工具 数据安全/隐私保护
Git之使用GitHub搭建远程仓库
在上一节中,我们学习了如何使用Git,构建我们的本地仓库,轻松的实现了版本控制以及代码还原,修改日志查看等;读者肯定不满足与本地是吧,假如是多个人一起来开发一个程序呢?我们需要一个作为服务器的远程仓库!当然搭建一个服务器是需要成本的,为什么不把项目托管到Github上呢?作为开源代码库以及版本控制系统,Github拥有140多万开发者用户。随着越来越多的应用程序转移到了云上,Github已经成为了管理软件开发以及发现已有代码的首选方法,不需要任何成本,为何不使用呢?本节就来学习如何把我们的代码托管到Github上!
143 0
|
开发工具 数据安全/隐私保护 git
【Git&GitHub - 6】:Git推送本地仓库到远程Github仓库(git remote命令、git push推送到远程、获取GitHub的token)
【Git&GitHub - 6】:Git推送本地仓库到远程Github仓库(git remote命令、git push推送到远程、获取GitHub的token)
412 0
【Git&GitHub - 6】:Git推送本地仓库到远程Github仓库(git remote命令、git push推送到远程、获取GitHub的token)
|
网络安全 开发工具 git
【Git&GitHub - 4】:Git克隆远程仓库到本地(GitHub远程仓库、GitHub的仓库链接、git clone命令)
【Git&GitHub - 4】:Git克隆远程仓库到本地(GitHub远程仓库、GitHub的仓库链接、git clone命令)
332 0
【Git&GitHub - 4】:Git克隆远程仓库到本地(GitHub远程仓库、GitHub的仓库链接、git clone命令)
|
存储 JavaScript 前端开发
推荐几个最近Star过的Github仓库
平时逛Github的时候,总是顺手对一些自己认为好的仓库给个 Star,一是对作者的鼓励,二来推荐给关注自己的人(首页动态可见)。 下面列举了一些我平时 Star 过的仓库,顺便也推荐给我的读者。
172 0
推荐几个最近Star过的Github仓库
|
网络安全 开发工具 git
Git - 本地 Git 绑定 Github 仓库
Git - 本地 Git 绑定 Github 仓库
263 0
Git - 本地 Git 绑定 Github 仓库
|
网络安全 开发工具 git
Git 系列教程(4)- 获取 Git 仓库
Git 系列教程(4)- 获取 Git 仓库
656 0
Git 系列教程(4)- 获取 Git 仓库
|
安全 Ubuntu Linux
Kali中搭建vulhub时镜像git失败
Kali中搭建vulhub时镜像git失败
301 0
Kali中搭建vulhub时镜像git失败

热门文章

最新文章

相关实验场景

更多