PingingLab-4.7 Frame-Relay & Static Rout

4.7 Frame-Relay & Static Route

Purpose:

1. Master the Static Routing Technology deployed on frame relay.

2. Achieve communication between different branches through static routing.

Tutorial topology:

650) this. width = 650; "src =" http://img1.51cto.com/attachment/201308/172518838.png "title =" 4.7.png "/>

Tutorial steps:

1. Based on the topology shown in the figure, simulate the frame relay switch through the router. The configuration is as follows:

① Enable the Frame Relay switching function

FW-SW (config) # frame-relay switching

② The interface enables Frame Relay encapsulation and is defined as the DCE Interface

FW-SW (config) # int s0/0

FW-SW (config-if) # no shutdown

FW-SW (config-if) # encapsulation frame-relay

FW-SW (config-if) # frame-relay intf-type dce

FW-SW (config-if) # exit

FW-SW (config) # int s0/1

FW-SW (config-if) # no shutdown

FW-SW (config-if) # encapsulation frame-relay

FW-SW (config-if) # frame-relay intf-type dce

FW-SW (config-if) # exit

FW-SW (config) # int s0/2

FW-SW (config-if) # no shutdown

FW-SW (config-if) # encapsulation frame-relay

FW-SW (config-if) # frame-relay intf-type dce

FW-SW (config-if) # exit

③ Write a frame relay forwarding entry

FW-SW (config) # int s0/0

FW-SW (config-if) # frame-relay route 102 interface s0/1 201

FW-SW (config-if) # frame-relay route 201 interface s0/0 102

FW-SW (config-if) # exit

FW-SW (config) # int s0/1

FW-SW (config-if) # frame-relay route 201 interface s0/0 102

FW-SW (config-if) # exit

FW-SW (config) # int s0/2

FW-SW (config-if) # frame-relay route 301 interface s0/0 102

FW-SW (config-if) # exit

2. By deploying Frame Relay Technology, each site is connected directly. R1 is the center point, R2 and R3 are the pivot points, and the configuration is as follows:

On R1

R1 (config) # int s0/0

R1 (config-if) # no shutdown

R1 (config-if) # encapsulation frame-relay

R1 (config-if) # no frame-relay inverse-arp

R1 (config-if) # frame-relay map ip 192.168.1.2 102 broadcast

R1 (config-if) # frame-relay map ip 192.168.1.3 103 broadcast

R1 (config-if) # exit

On R2

R2 (config) # int s0/0

R2 (config-if) # no shutdown

R2 (config-if) # encapsulation frame-relay

R2 (config-if) # no frame-relay inverse-arp

R2 (config-if) # frame-relay map ip 192.168.1.1 201 broadcast

R2 (config-if) # frame-relay map ip 192.168.1.3 201 broadcast

R2 (config-if) # exit

On R3

R3 (config) # int s0/0

R3 (config-if) # no shutdown

R3 (config-if) # encapsulation frame-relay

R3 (config-if) # no frame-relay inverse-arp

R3 (config-if) # frame-relay map ip 192.168.1.1 301 broadcast

R3 (config-if) # frame-relay map ip 192.168.1.2 301 broadcast

R3 (config-if) # exit

Test the direct connection connectivity as follows:

R1 # ping 192.168.1.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 36/42/60 MS

R1 # ping 192.168.1.3

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.3, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 16/31/52 MS

R2 # ping 192.168.1.3

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.3, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 44/68/96 MS

As you can see, direct connection is normal.

3. Deploy the Static Routing technology so that different branches can communicate with each other. The configuration is as follows:

R1 (config) # ip route 2.2.2.2 255.255.255.255 192.168.1.2 [PL1]

R1 (config) # ip route 3.3.3.3 255.255.255.255 192.168.1.3

R2 (config) # ip route 1.1.1.1 255.255.255.255 192.168.1.1

R2 (config) # ip route 3.3.3.3 255.255.255.255 192.168.1.3

R3 (config) # ip route 1.1.1.1 255.255.255.255 192.168.1.1

R3 (config) # ip route 2.2.2.2 255.255.255.255 192.168.1.2

In this case, test whether the network segments behind different branches can communicate with each other, as shown below:

R1 # ping 2.2.2.2 source 1.1.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:

Packet sent with a source address of 1.1.1.1

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 24/45/64 MS

R1 # ping 3.3.3.3 source 1.1.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds:

Packet sent with a source address of 1.1.1.1

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 40/42/52 MS

R2 # ping 3.3.3.3 source 2.2.2.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds:

Packet sent with a source address of 2.2.2.2

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 48/59/80 MS

The test is successful. This experiment is complete.

[PL1]In the frame relay environment, the next hop is required for Static Routing. If the output interface is used, the ing information cannot be found and the encapsulation fails, resulting in communication failure. If the next hop is used, the ing information can be found after recursive routing. Generally, static routes in point-to-point environments use the output interface method and the next hop method in multi-channel access environments.

========================================================== =

PingingLab· High quality ITEducation provider

CCIELab-ITProject Practice · customization of high-end Talents

Shenzhen pinke Information Technology Co., Ltd. · waihuan West Road Station, Guangzhou University City

Sina Weibo :@PingingLab@ PingingLab-Chen xinjie

PingingLabPublic Account: pinginglab

PingingLabTechnical Exchange Group: 240920680

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/061HBE8-1.jpg "title =" pinginglab .bmp "/>

This article from the "Chen xinjie network" blog, please be sure to keep this source http://chenxinjie.blog.51cto.com/7749507/1274484