CCNA(Stand-ALONE)Lab 26-Frame Relay Full Mesh Topology

简介:
Objective: Learn to configure a full mesh topology.
Lab Equipment: Router 1, Router 2, Router 3, and Router 4 from the eRouters menu
Background Reading: Lab Primer Lesson 9: Frame Relay
Again, the company’s corporate office is in Dallas and its sales offices are in San Francisco, New York, and Tampa. The sales offices should be able to access all company resources. You want to establish a full mesh topology in which a point-to-point Frame Relay connection links the corporate office to each sales office and links each sales office to every other sales office.
The difference between the Frame Relay hub-and-spoke topology and the full mesh topology is that, with a full mesh topology, every sales office has a direct connection to every other sales office and the corporate office. This is a very redundant topology so if one of the connections fails,data can still be transferred to every site by using a different path.

1. First, assign the host names of Dallas, San_Francisco, New_York, and Tampa to Router 1, Router 2, Router 3, and Router 4, respectively.
Dallas:
San_Francisco:
New_York:
Tampa:

2. Now, enter interface configuration mode for the serial 0 interface on Dallas, and set the encapsulation type to Frame Relay. Be sure to enable the interface.
Dallas(config)#interface serial 0
Dallas(config-if)#encapsulation frame-relay
Dallas(config-if)#no shutdown

3. Next, create a subinterface for the connection between Dallas and the San Francisco sales office.
Dallas(config-if)#exit
Dallas(config)#interface serial 0.100 point-to-point
Dallas(config-subif)#

4. Assign the subinterface the DLCI number for the connection from Dallas to San_Francisco, and configure the subinterface with the appropriate IP address. Remember to enable the subinterface.
Dallas(config-subif)#frame-relay interface-dlci 102
Dallas(config-subif)#ip address 172.16.1.1 255.255.255.0
Dallas(config-subif)#no shutdown

5. Create a subinterface for the connection from Dallas to the sales office in New York.
Dallas(config-subif)#exit
Dallas(config)#interface serial 0.200 point-to-point
Dallas(config-subif)#

6. Add the correct DLCI for the connection from Dallas to New_York, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
Dallas(config-subif)#frame-relay interface-dlci 103
Dallas(config-subif)#ip address 172.16.2.1 255.255.255.0
Dallas(config-subif)#no shutdown

7. Create a subinterface for the connection from Dallas to the sales office in Tampa.
Dallas(config-subif)#exit
Dallas(config)#interface serial 0.300 point-to-point
Dallas(config-subif)#

8. Add the correct DLCI for the connection from Dallas to Tampa, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
Dallas(config-subif)#frame-relay interface-dlci 104
Dallas(config-subif)#ip address 172.16.3.1 255.255.255.0
Dallas(config-subif)#no shutdown

9. Access the serial 0 interface of San_Francisco, set the encapsulation to Frame Relay, and enable the interface.
San_Francisco(config)#interface serial 0
San_Francisco(config-if)#encapsulation frame-relay
San_Francisco(config-if)#no shutdown

10. Create the first subinterface for the connection from San_Francisco to the corporate office in Dallas.
San_Francisco(config-if)#interface serial 0.100 point-to-point
San_Francisco(config-subif)#

11. Add the correct DLCI for the connection from San_Francisco to Dallas, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
San_Francisco(config-subif)#frame-relay interface-dlci 201
San_Francisco(config-subif)#ip address 172.16.1.2 255.255.255.0
San_Francisco(config-subif)#no shutdown

12. Create a subinterface for the connection from San_Francisco to New_York.
San_Francisco(config-subif)#exit
San_Francisco(config)#interface serial 0.200 point-to-point

13. Add the correct DLCI value for the connection from San_Francisco to New_York, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
San_Francisco(config-subif)#frame-relay interface-dlci 203
San_Francisco(config-subif)#ip address 172.16.4.1 255.255.255.0
San_Francisco(config-subif)#no shutdown

14. Create the subinterface for the connection from San_Francisco to Tampa.
San_Francisco(config-subif)#exit
San_Francisco(config)#interface serial 0.300 point-to-point

15. Add the correct DLCI value for the San_Francisco to Tampa connection, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
San_Francisco(config-subif)#frame-relay interface-dlci 204
San_Francisco(config-subif)#ip address 172.16.6.1 255.255.255.0
San_Francisco(config-subif)#no shutdown

16. Access the serial 0 interface of New_York, set the encapsulation to Frame Relay, and enable the interface.
New_York(config)#interface serial 0
New_York(config-if)#encapsulation frame-relay
New_York(config-if)#no shutdown

17. Create the fi rst subinterface for the connection from New_York to the corporate office in Dallas.
New_York(config-if)#exit
New_York(config)#interface serial 0.100 point-to-point

18. Add the correct DLCI value for the connection from New_York to Dallas, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
New_York(config-subif)#frame-relay interface-dlci 301
New_York(config-subif)#ip address 172.16.2.2 255.255.255.0
New_York(config-subif)#no shutdown

19. Create the subinterface for the connection from New_York to San_Francisco.
New_York(config-subif)#exit
New_York(config)#interface serial 0.200 point-to-point

20. Add the correct DLCI value for the connection from New_York to San_Francisco, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
New_York(config-subif)#frame-relay interface-dlci 302
New_York(config-subif)#ip address 172.16.4.2 255.255.255.0
New_York(config-subif)#no shutdown

21. Create the subinterface for the connection from New_York to Tampa.
New_York(config-subif)#exit
New_York(config)#interface serial 0.300 point-to-point

22. Add the correct DLCI value for the New_York to Tampa connection, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
New_York(config-subif)#frame-relay interface-dlci 304
New_York(config-subif)#ip address 172.16.5.1 255.255.255.0
New_York(config-subif)#no shutdown

23. Access the serial 0 interface on Tampa, set the encapsulation to Frame Relay, and enable the interface.
Tampa(config)#interface serial 0
Tampa(config-if)#encapsulation frame-relay
Tampa(config-if)#no shutdown

24. Create the first subinterface for the connection from Tampa to the corporate office in Dallas.
Tampa(config-if)#exit
Tampa(config)#interface serial 0.100 point-to-point

25. Add the correct DLCI value for the Tampa to Dallas connection, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
Tampa(config-subif)#frame-relay interface-dlci 401
Tampa(config-subif)#ip address 172.16.3.2 255.255.255.0
Tampa(config-subif)#no shutdown

26. Create the subinterface for the connection from Tampa to San_Francisco.
Tampa(config-subif)#exit
Tampa(config)#interface serial 0.200 point-to-point

27. Add the correct DLCI value for the Tampa to San_Francisco connection, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
Tampa(config-if)#frame-relay interface-dlci 402
Tampa(config-subif)#ip address 172.16.6.2 255.255.255.0
Tampa(config-subif)#no shutdown

28. Create the subinterface for the connection from Tampa to New_York.
Tampa(config-subif)#exit
Tampa(config)#interface serial 0.300 point-to-point

29. Add the correct DLCI value for the Tampa to New_York connection, and configure the appropriate IP address for the subinterface. Remember to enable the subinterface.
Tampa(config-subif)#frame-relay interface-dlci 403
Tampa(config-subif)#ip address 172.16.5.2 255.255.255.0
Tampa(config-subif)#no shutdown

30. Now, all interfaces should be up and up. To test the configuration, connect to Dallas and try to ping each of the three sales offices.
Dallas(config-subif)#exit
Dallas(config)#exit
Dallas#ping 172.16.1.2
Dallas#ping 172.16.2.2
Dallas#ping 172.16.3.2

31. Connect to San_Francisco, and try to ping the other three offices.
San_Francisco(config-subif)#exit
San_Francisco(config)#exit
San_Francisco#ping 172.16.1.1
San_Francisco#ping 172.16.4.2
San_Francisco#ping 172.16.6.2
*************************************************



本文转自redking51CTO博客,原文链接:http://blog.51cto.com/redking/72726 ,如需转载请自行联系原作者
相关文章
|
2天前
|
弹性计算 关系型数据库 微服务
基于 Docker 与 Kubernetes(K3s)的微服务:阿里云生产环境扩容实践
在微服务架构中,如何实现“稳定扩容”与“成本可控”是企业面临的核心挑战。本文结合 Python FastAPI 微服务实战,详解如何基于阿里云基础设施,利用 Docker 封装服务、K3s 实现容器编排,构建生产级微服务架构。内容涵盖容器构建、集群部署、自动扩缩容、可观测性等关键环节,适配阿里云资源特性与服务生态,助力企业打造低成本、高可靠、易扩展的微服务解决方案。
1078 0
|
11天前
|
人工智能 运维 安全
|
10天前
|
人工智能 测试技术 API
智能体(AI Agent)搭建全攻略:从概念到实践的终极指南
在人工智能浪潮中,智能体(AI Agent)正成为变革性技术。它们具备自主决策、环境感知、任务执行等能力,广泛应用于日常任务与商业流程。本文详解智能体概念、架构及七步搭建指南,助你打造专属智能体,迎接智能自动化新时代。
|
2天前
|
弹性计算 Kubernetes jenkins
如何在 ECS/EKS 集群中有效使用 Jenkins
本文探讨了如何将 Jenkins 与 AWS ECS 和 EKS 集群集成,以构建高效、灵活且具备自动扩缩容能力的 CI/CD 流水线,提升软件交付效率并优化资源成本。
265 0
|
9天前
|
人工智能 异构计算
敬请锁定《C位面对面》,洞察通用计算如何在AI时代持续赋能企业创新,助力业务发展!
敬请锁定《C位面对面》,洞察通用计算如何在AI时代持续赋能企业创新,助力业务发展!
|
10天前
|
机器学习/深度学习 人工智能 自然语言处理
B站开源IndexTTS2,用极致表现力颠覆听觉体验
在语音合成技术不断演进的背景下,早期版本的IndexTTS虽然在多场景应用中展现出良好的表现,但在情感表达的细腻度与时长控制的精准性方面仍存在提升空间。为了解决这些问题,并进一步推动零样本语音合成在实际场景中的落地能力,B站语音团队对模型架构与训练策略进行了深度优化,推出了全新一代语音合成模型——IndexTTS2 。
758 23
|
2天前
|
缓存 供应链 监控
VVIC seller_search 排行榜搜索接口深度分析及 Python 实现
VVIC搜款网seller_search接口提供服装批发市场的商品及商家排行榜数据,涵盖热销榜、销量排名、类目趋势等,支持多维度筛选与数据分析,助力选品决策、竞品分析与市场预测,为服装供应链提供有力数据支撑。
|
2天前
|
缓存 监控 API
Amazon item_review 商品评论接口深度分析及 Python 实现
亚马逊商品评论接口(item_review)可获取用户评分、评论内容及时间等数据,支持多维度筛选与分页调用,结合Python实现情感分析、关键词提取与可视化,助力竞品分析、产品优化与市场决策。