CCNP experiment: using a tunnel to expand the frame relay switch simulated by the router

[Experimental environment] veryhuo.com

C3640-IK9O3S-M Version 12.4 (10) veryhuo.com

[Tutorial Objective] Lie's Fire Network

The tunnel technology is used to expand the frame relay switch simulated by the router to make up for the insufficient frame relay interface caused by limited router interfaces. Lie-fire-network

[Experiment topology]

Liehuo.net

Veryhuo.com

[Experiment description] liehuo.net

In the experimental environment, because frame relay switches are expensive, we use routers to simulate frame relay switches. in the real environment, sometimes the serial interfaces of routers are insufficient, therefore, we need to use two or more routers to simulate the interface expansion of the frame relay switch. In this case, we need to use the tunneling technology. Veryhuo.com

Routers R1 and R2 serve as frame relay switches. R1 only has two serial interfaces. Therefore, you need to use the Fast Ethernet interface to connect to R3 for expansion of the serial interface.

Veryhuo.com

For details about how to configure a vro as a frame relay switch, refer to CCNP experiment: configure a Cisco vro as a frame relay switch. Here, we will not describe it too much and record the use of the tunnel. Therefore, the configuration is only performed on R1 and R2. After the internal configuration of the frame relay cloud is complete, it is transparent to users. Liehuo.net

[Tutorial] liehuo.net

1. Basic configuration of R1: only the frame relay route between R3 and R4 is configured: veryhuo.com

Frame-relay switching
!
Interface Serial1/0
No ip address
Encapsulation frame-relay
Clock rate 64000
Frame-relay lm-type cisco
Frame-relay intf-type dce
Frame-relay route 304 interface Serial1/1 403
!
Interface Serial1/1
No ip address
Encapsulation frame-relay
Clock rate 64000
Frame-relay lm-type ansi
Frame-relay intf-type dce
Frame-relay route 403 interface Serial1/0 304
!
Interface FastEthernet0/0
Ip address 12.0.0.1 255.255.255.0
Duplex auto
Speed auto
! Liehuo.net

2. R2 is basically configured. At this time, R2 does not configure any Frame Relay route: gwang.com

Frame-relay switching
!
Interface Serial1/0
No ip address
Encapsulation frame-relay
Clock rate 64000
Frame-relay lm-type q933a
Frame-relay intf-type dce
!
Interface FastEthernet0/0
Ip address 12.0.0.2 255.255.255.0
Duplex auto
Speed auto
! Powerful fireworks

3. Configure the tunnel veryhuo.com with R2 on R1

Interface Tunnel1
Tunnel source 12.0.0.1
Tunnel destination 12.0.0.2

Veryhuo.com

4. Configure the liehuo.net tunnel between R2.

Interface Tunnel1
Tunnel source 12.0.0.2
Tunnel destination 12.0.0.1

Liehuo.net

Note: The tunnel is used for p2p. You do not need to configure an IP address. You only need to set the physical address liehuo.net of the source and target interfaces.

5. Configure the relay route liehuo.net of R3-> R5 on R1

Interface Serial1/0
Frame-relay route 305 interface Tunnel1 101

Veryhuo.com

6. Configure R5-> R3's frame relay route liehuo.net on R2

Interface Serial1/0
Frame-relay route 503 interface Tunnel1 101 veryhuo.com

Note: The "305" and "503" and "" cannot be used for the peer DLCI numbers. A unique tunnel number must be used to distinguish multiple pvcs transmitted through the tunnel, "101" can be defined at Will (the two sides are the same), and "102" and "103" can be used when other PVC exists.

Liehuo.net

7. Verification (use the "sh fr ro" command on R1 to view the Frame Relay forwarding table, and see all active instances to prove that the configuration is successful) liehuo.net

Liehuo.net