Frame Relay switch configuration instance

Source: Internet
Author: User

Lab environment:

1. the topology is simple, but classic. The experiment is completed using the GNS simulator.

2. Four 36XX routers, one of which is configured as FR-SW. The router is directly connected to the frame relay switch.

Lab requirements:

1. configure a vro as a frame relay switch

2. The other three routers are directly connected to the frame relay switch, and IP addresses are configured on the direct connection interface to achieve network connectivity.

Purpose:

1. Master how to configure a router to a frame relay switch.

2. Understand the General setting method and working principle of DLCI

Tutorial topology:

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0220195394-0.jpg "/>

Experiment Configuration:

The core of this experiment is to configure R4 as Frame-Relay. The configuration process is as follows:

R4 --- "Fr-sw)

The basic configuration is omitted !!!!

Fr-sw (config) # frame-relay switching //Required to enable the frame relay switch function)
Fr-sw (config) # int s0/0 // enter the interface
Fr-sw (config-if) # no ip add // as the frame relay switch, the interface does not require an ip address
Fr-sw (config-if) # encapsulation frame-relay // encapsulate the interface as frame relay
Fr-sw (config-if) # frame-relay lm-type cisco // The encapsulation type is CISCO.

There are three types of encapsulation:

Cisco // needless to say, you can understand it at a glance. This is used by Cisco devices by default.
Ansi // This is a general standard supported by all vendors
Q933a // This is rarely used. Just take a look!

As long as the devices at both ends adopt the same encapsulation, no problem occurs. Not much to mention!
Fr-sw (config-if) # frame-relay intf-type dce // set the interface type to DCE.
Fr-sw (config-if) # frame-relay route 102 int s0/1 201 // frame relay route. if it comes from 102, go out from interface s0/1 and convert it to 201

102, from R1 --> R2. 201, from R2 --> R1. We strongly recommend that you use regular numbers to facilitate your memory !)
Fr-sw (config-if) # frame-relay route 103 int s0/2 301 // from 103, go out from s0/2 and convert it to 301
Fr-sw (config-if) # no sh // open the interface
Fr-sw (config-if) # exit

-------------------------------------------------------------
Fr-sw (config) # int s0/1

Fr-sw (config-if) # no ip add
Fr-sw (config-if) # encapsulation frame-relay
Fr-sw (config-if) # frame-relay lm-type cisco
Fr-sw (config-if) # frame-relay intf-type dce
Fr-sw (config-if) # frame-relay route 201 int s0/0 102
Fr-sw (config-if) # frame-relay route 203 int s0/2 302
Fr-sw (config-if) # no sh
Fr-sw (config-if) # exit

--------------------------------------------------------------
Fr-sw (config) # int s0/2

Fr-sw (config-if) # no ip add
Fr-sw (config-if) # encapsulation frame-relay
Fr-sw (config-if) # frame-relay lm-type cisco
Fr-sw (config-if) # frame-relay intf-type dce
Fr-sw (config-if) # frame-relay route 301 int s0/0 103
Fr-sw (config-if) # frame-relay route 302 int s0/1 203
Fr-sw (config-if) # no sh
Fr-sw (config-if) # exit
After the configuration is complete, view the Frame Relay Configuration:
Fr-sw (config) # do sh fram route

650) this. width = 650; "border =" 0 "alt =" "width =" 578 "height =" 100 "src =" http://www.bkjia.com/uploads/allimg/131227/0220195511-1.jpg "/> from the information above, all entries are matched one by one. However, we found that all Frame Relay Links are inactive. Why? Don't worry, because we haven't configured the other three routers, and the link is definitely disconnected.

R1 ---"

R1 (config) # int s0/0 // enter the interface. Refer to the topology)
R1 (config-if) # ip add 192.168.14.1 255.255.255.0 // specify the IP address.
R1 (config-if) # encapsulation frame-relay // The interface is encapsulated as frame relay.
R1 (config-if) # no sh // open the interface

R2 (config-if) # exit

R2 ---"

R2 (config) # int s0/0
R2 (config-if) # ip add 192.168.14.2 255.255.0
R2 (config-if) # enca fram
R2 (config-if) # no sh
R2 (config-if) # exit

R3 ---"

R3 (config) # int s0/0
R3 (config-if) # ip add 192.168.14.3 255.255.255.0
R3 (config-if) # enc fram
R3 (config-if) # no sh
R3 (config-if) # exit

Note: When you configure the IP address of the preceding vro, the IP address must be in the same CIDR block without enabling the routing protocol !!!!!

Good, the other three router configuration is also completed, next to the FR-SW to view the route information of Frame Relay:

650) this. width = 650; "border =" 0 "alt =" "width =" 593 "height =" 135 "src =" http://www.bkjia.com/uploads/allimg/131227/0220193G3-2.jpg "/>

Look! All statuses have become active.

The following shows the connectivity of the entire network:

R1 ---"

650) this. width = 650; "border =" 0 "alt =" "width =" 604 "height =" 204 "src =" http://www.bkjia.com/uploads/allimg/131227/02201964C-3.jpg "/>

R2 ---"

650) this. width = 650; "style =" width: 592px; height: 178px "border =" 0 "alt =" "width =" 611 "height =" 183 "src =" http://www.bkjia.com/uploads/allimg/131227/02201923P-4.jpg "/>

R3 ---"

650) this. width = 650; "border =" 0 "alt =" "width =" 600 "height =" 194 "src =" http://www.bkjia.com/uploads/allimg/131227/0220196225-5.jpg "/>

OK! No problem. The experiment is complete!

In addition, it is strongly recommended that "static Frame Relay" be used in frame relay to facilitate management.

Manual intervention is required to adopt static Frame Relay. The command usage is as follows: This experiment topology is used as an example)

R1 --->

R1 (config) # int s0/0
R1 (config-if) # shut // close the interface
R1 (config-if) # no frame-relay inverse-arp // disable reverse ARP
R1 (config-if) # no arp frame-relay // disable forward ARP
R1 (config-if) # frame-relay map ip 192.168.14.2 102 broadcast // tell the router to go to 192.168.14.2. Please go to DLCI 102 and allow you to broadcast.
R1 (config-if) # frame-relay map ip 192.168.14.3 103 broadcast // same as above

R1 (config-if) # no sh // open the interface again
R1 (config-if) # exit

The operations of R2 and R3 are the same as those of R1, so we will not list them here !!!

This article is from the "YYJCWXF sanmao)" blog!

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.