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 ,如需转载请自行联系原作者
  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
资源包主要包含以下内容: ASP项目源码:每个资源包中都包含完整的ASP项目源码,这些源码采用了经典的ASP技术开发,结构清晰、注释详细,帮助用户轻松理解整个项目的逻辑和实现方式。通过这些源码,用户可以学习到ASP的基本语法、服务器端脚本编写方法、数据库操作、用户权限管理等关键技术。 数据库设计文件:为了方便用户更好地理解系统的后台逻辑,每个项目中都附带了完整的数据库设计文件。这些文件通常包括数据库结构图、数据表设计文档,以及示例数据SQL脚本。用户可以通过这些文件快速搭建项目所需的数据库环境,并了解各个数据表之间的关系和作用。 详细的开发文档:每个资源包都附有详细的开发文档,文档内容包括项目背景介绍、功能模块说明、系统流程图、用户界面设计以及关键代码解析等。这些文档为用户提供了深入的学习材料,使得即便是从零开始的开发者也能逐步掌握项目开发的全过程。 项目演示与使用指南:为帮助用户更好地理解和使用这些ASP项目,每个资源包中都包含项目的演示文件和使用指南。演示文件通常以视频或图文形式展示项目的主要功能和操作流程,使用指南则详细说明了如何配置开发环境、部署项目以及常见问题的解决方法。 毕业设计参考:对于正在准备毕业设计的学生来说,这些资源包是绝佳的参考材料。每个项目不仅功能完善、结构清晰,还符合常见的毕业设计要求和标准。通过这些项目,学生可以学习到如何从零开始构建一个完整的Web系统,并积累丰富的项目经验。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值