Ccnp second-day Frame Relay comprehensive experiment

Lab question: it is required that the whole network can reach R5 as the fast Ethernet interface between R6 and r1 of the frame relay switch

The topology used is the ccna standard topology, as shown below:

 

Else ---------------------------------------------------------------------------------------------------------------------------------

1. First, connect each PVC

Frsw # conf t
Frsw (config) # No IP routing// Disable the router routing function
Frsw (config) # frame-relay Switching// Enable the Frame Relay switching function
Frsw (config) # int S1/0
Frsw (config-If) # encapsulation frame-relay
Frsw (config-If) # frame-relay INTF-type DCE
Frsw (config-If) # frame-relay route 102 interface S1/1 201
Frsw (config-If) # frame-relay route 103 interface S1/2 301
Frsw (config-If) # frame-relay route 104 interface S1/3 401

Frsw (config-If) # int S1/1
Frsw (config-If) # encapsulation frame-relay
Frsw (config-If) # frame-relay INTF-type DCE
Frsw (config-If) # frame-relay route 201 interface S1/0 102

Frsw (config-If) # int S1/2
Frsw (config-If) # encapsulation frame-relay
Frsw (config-If) # frame-relay INTF-type DCE
Frsw (config-If) # frame-relay route 301 interface S1/0 103
Frsw (config-If) # frame-relay route 304 interface S1/3 403

Frsw (config-If) # int S1/3
Frsw (config-If) # encapsulation frame-relay
Frsw (config-If) # frame-relay INTF-type DCE
Frsw (config-If) # frame-relay route 403 interface S1/2 304
Frsw (config-If) # frame-relay route 401 interface S1/0 104

So far, the PVC on frame relay has been connected, and the client configuration is as follows:
-------------------------------------------------------------------------

2. configuration of various client interfaces

R1 (config) # int S1/2
R1 (config-If) # encapsulation frame-relay
R1 (config-If) # No Shutdown

R1 (config) # int S1/2.1 multipoint// Multi-point interface
R1 (config-subif) # IP add 123.1.1.1 255.255.255.0
R1 (config-subif) # frame-relay interface-dlci 102
R1 (config-fr-dlci) # frame-relay interface-dlci 103

R1 (config) # int S1/2.2 point-to-point// Point-to-point interface
R1 (config-subif) # IP add 14.1.1.1 255.255.255.0
R1 (config-subif) # frame-relay interface-dlci 104

R2 (config) # int S1/2
R2 (config-If) # encapsulation frame-relay
R2 (config-If) # IP add 123.1.1.2 255.255.255.0
R2 (config-If) # No Shutdown

R3 (config) # int S1/2
R3 (config-If) # encapsulation frame-relay
R3 (config-If) # No Shutdown

R3 (config) # int S1/2.1 point-to-point
R3 (config-subif) # IP add 123.1.1.3 255.255.255.0
R3 (config-subif) # frame-relay interface-dlci 301

R3 (config) # int S1/2.2 multipoint
R3 (config-subif) # IP add 34.1.1.1 255.255.255.0
R3 (config-subif) # frame-relay interface-dlci 304

R4 (config) # int S1/2
R4 (config-If) # encapsulation frame-relay
R4 (config-If) # No Shutdown

R4 (config) # int S1/2.1 point-to-point
R4 (config-subif) # IP add 34.1.1.2 255.255.255.0
R4 (config-subif) # frame-relay interface-dlci 403

R4 (config) # int S1/2.2 point-to-point
R4 (config-subif) # IP add 14.1.1.2 255.255.255.0
R4 (config-subif) # frame-relay interface-dlci 401

So far, all the client interface sub-interfaces have been configured. The following is a test
Ping R2 R3 R4 with r1
You can ping R4 using R3. If not, check whether the previous configuration and interfaces are enabled.

PS: It is recommended that you manually map multiple point interfaces and physical interfaces. Because the automatic generation of map by multiple point interfaces and physical interfaces is too slow, point-to-point sub-interfaces cannot write map manually, it does not work, because point-to-point does not focus on the layer-3 IP address.
Bytes -----------------------------------------------------------------------------------

Then, configure each vro with a ring-up of the OSPF protocol.

1. loopback

R1's loopback 1.1.1.1 R2's loopback 2.2.2.2 ......

2. Start the OSPF protocol on each vro respectively.

R1 (config) # router VPN 90
R1 (config-router) # No auto-Summary
R1 (config-router) # network 123.0.0.0
R1 (config-router) # network 1.0.0.0
R1 (config-router) # network 14.0.0.0

R2 (config) # router VPN 90
R2 (config-router) # No auto-Summary
R2 (config-router) # network 123.0.0.0
R2 (config-router) # network 2.0.0.0

R3 (config) # router VPN 90
R3 (config-router) # No auto-Summary
R3 (config-router) # network 123.0.0.0
R3 (config-router) # network 34.0.0.0
R3 (config-router) # network 3.0.0.0

R4 (config) # router VPN 90
R4 (config-router) # No auto-Summary
R4 (config-router) # network 14.0.0.0
R4 (config-router) # network 34.0.0.0

So far, after the route entry convergence is complete, the route entries of R1 R3 R4 should be fully converged (except R6)
While R2 does not have vro entries for the 34.0.0.0/24 and 3.0.0.0/24 days.
-----------------------------------------------------------------------

Intranet access to the Internet by default and Nat

1. Default
R1 (config) # IP Route 0.0.0.0 0.0.0.0 16.1.1.2
R1 (config) # router VPN 90
R1 (config-router) # redistribute static // republish

2. Nat
R1 (config) # access-List 1 permit any
R1 (config) # ip nat inside source list 1 interface F0/0 overload

R1 (config) # int F0/0
R1 (config-If) # ip nat outside

R1 (config) # int S1/2.1
R1 (config-subif) # ip nat inside

R1 (config) # int S1/2.2
R1 (config-subif) # ip nat inside

PS: 1.ip Nat inside, each sub-interface must be treated as a physical interface instead of S1/2 as inside

2. There are default and summary of the time for security, should prevent the emergence of the routing black hole, so it is necessary to write an empty interface routing entry on all the router R2-R6 has been summarized

Eg: R2 (config) # IP router 192.168.1.0 255.255.255.240 null 0

......

R6 (config) # IP router 192.168.1.0 255.255.255.0 null 0// Because R6 has done a summary of/24 bits on the R2-R6 on S1/1

 

You have worked hard here. Thank you :)

 

-----------------------------------------------------------------------------

Statement:

This article aims to organize and implement the knowledge learned by Yi Ba Lang.

You are welcome to reprint this document, but please make sure that this document is complete or noted. This document shall not be used for commercial purposes without the consent of big Yi Ba Lang. Finally, if you can get some help from this simple document, big Yi Ba Lang will be very happy with his own efforts. Due to the limited level of the author, if the errors in this document cause inconvenience, I am sorry in advance.

Wish you good health and smooth work.