Demonstration: configuration of a Cisco device based on the physical interface Frame relay (fame-relay)

Demonstration: configuration of a Cisco device based on the physical interface frame relay fame-relay

Corresponding Teaching Video in: http://edu.51cto.com/lecturer/user_id-7648423.html

9.9 release, which can be viewed after the Administrator's 24-hour review. The course name is Cisco CCNA-certified Frame Relay analysis 200-120) 9 lessons.

Demonstration target: Configure Frame Relay Based on the semi-mesh physical interface.

Demo environment:The experiment environment is shown in Figure 8.53.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S44M2-0.png "title =" 1.png"/>

Demo tool:Three Cisco routers and one frame relay switch.

Demonstration Background:Router R1 is the access device of the headquarters of the frame relay network, and routers R2 and R3 are remote branches. They establish virtual circuits with R1 through the frame relay switch, respectively, connect remote branches to the headquarters. Note: first, a semi-mesh frame relay network is established. There is no traffic exchange between the routers R2 and R3, and the traffic of all remote branches is exchanged with the headquarters.

Demo steps:

Step 1:Configure the frame relay switch. Here, a router with four synchronous serial interfaces is used to simulate the frame relay switch. Therefore, you must first understand the configuration of the first frame following the switch.

Configuration of the frame relay switch:

Fr-switching (config) # frame-relayswitching

Enable Frame Relay switching.

Fr-switching (config) # intes1/0

Enter the S1/0 interface configuration mode of the frame relay switch.

Fr-switching (config-if) # encapsulationframe-relay

Encapsulate the Frame Relay protocol for this interface.

Fr-switching (config-if) # frame-relayintf-type dce

Indicates that the interface type is DCE.

Fr-switching (config-if) # clockrate 56000

For the DCE end to encapsulate the clock frequency, the DCE must configure the clock frequency because it needs to provide the Clock Synchronization for the synchronous serial link.

Fr-switching (config-if) # frame-relayroute 102 interface s1/1 201

Configure the frame relay route, indicating that S1/0 will reach the PVC 201 of R2 through the S1/1 interface. In fact, the frame relay switch instructs the router R1 to reach the Frame Relay path of the router R2.

Fr-switching (config-if) # frame-relayroute 103 interface s1/2 301

Configure the frame relay route, indicating that S1/0 will reach the PVC 301 of R3 through the S1/2 interface. In fact, the frame relay switch instructs the router R1 to reach the Frame Relay path of router R3.

Fr-switching (config-if) # noshutdown

Activate this interface.

Note: In the above configuration, the concept of Frame Relay routing should be described in particular. The so-called Frame Relay routing is not a network-layer route, but a two-layer path of Frame Relay.

The configurations under interfaces S1/1 and S1/2 on the frame relay switch are basically the same as those under interfaces S1/0, except that the DLCI Number of the frame relay is different from that of the interface, therefore, the commands are not repeated. The configurations of S1/1 and S1/2 are as follows:

Fr-switching (config) # intes1/1

Fr-switching (config-if) # encapsulationframe-relay

Fr-switching (config-if) # frame-relayintf-type dce

Fr-switching (config-if) # clockrate 56000

Fr-switching (config-if) # frame-relayroute 201 interface s1/0 102

Fr-switching (config-if) # noshutdown

Fr-switching (config) # intes1/2

Fr-switching (config-if) # encapsulationframe-relay

Fr-switching (config-if) # frame-relayintf-type dce

Fr-switching (config-if) # clockrate 56000

Fr-switching (config-if) # frame-relayroute 301 interface s1/0 103

Fr-switching (config-if) # noshutdown

Step 2:Configure the access device DTE Of The Frame Relay Network), routers R1, R2, and R3.

VroR1Configuration:

R1 (config) # inte s1/0

Enter the S1/0 interface configuration mode of router R1.

R1 (config-if) # encapsulationframe-relay

Encapsulate the Frame Relay protocol for this interface.

R1 (config-if) # ip address192.168.1.1 255.255.0

Configure an IP address for this interface.

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

Configure a static Frame Relay ing to vror2 R2 on this interface. This so-called static ing is the static ing between the L2 DLCI Number of the frame relay and the L3 IP address. The command keyword IP address is the IP address of the target device router R2. The command keyword DLCI number is the local DLCI Number of router R1, the two keywords are combined to indicate that router R1 uses the local DLCI Number 102 to reach the destination 192.168.1.2, and the command keyword broadcast indicates to broadcast when multicast fails to work normally.

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

In this interface, configure a static Frame Relay ing to router R3. Its directive meaning is described above.

R1 (config-if) # noshutdown

Activate this interface.

Note: The following figure shows the frame relay configurations of routers R2 and R3. The configuration commands are basically the same as those of router R1, except that their IP addresses and DLCI numbers are different, so the instructions are not repeated.

VroR2Configuration:

R2 (config) # inte s1/0

R2 (config-if) # encapsulationframe-relay

R2 (config-if) # ipaddress 192.168.1.2 255.255.255.0

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

R2 (config-if) # noshutdown

Vror3 R3 Configuration:

R3 (config) # inte s1/0

R3 (config-if) # encapsulationframe-relay

R3 (config-if) # ipaddress 192.168.1.3 255.255.255.0

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

R3 (config-if) # noshutdown

Step 3:Check the connectivity between router R1 and router R2192.168.1.2) and R3192.168.1.2. As shown in Figure 8.54, the router R1 successfully communicates with R2 and R3.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S45241-1.png "title =" 2.png"/>

Step 4:Use show frame-relay pvc to view the virtual circuits R2 and R3 on router R1, as shown in Figure 8.55. The STATUS of vrouters R2 and R3 102 and 103 is displayed) the status is ACTIVE, indicating that the two virtual circuits are working normally. PVC generally has three states:

NActive: indicates that the link is active, and the frame relay link works normally.

NInactive: The local connection to the frame relay switch is normal, but the link from the peer Frame Relay router to the frame relay switch is faulty.

NDeleted: indicates that the frame relay access device does not receive any LCM signaling about frame relay from the frame relay switch, or no service exists.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S42218-2.png "title =" 3.png"/>

Step 5:Use the showframe-relay LMS command on router R1 to view the TYPE of the LMS, as shown in Figure 8.56. the lms type = CISCO uses the lms type.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S415A-3.png "title =" 4.png"/>

Step 6:Use the showframe-relay map command on the router R1 to view the ing status of the frame relay virtual circuit, as shown in Figure 8.57. This shows the dling between the router R1 and the router R2 and R3 DLCI and the layer-3 IP address, its type is static ing. When a dling relationship between a frame relay DLCI number and a layer-3 IP address is formed, another ing scheme is called dynamic ing. The principle of dynamic ing is described in "Understanding the reverse ARP of Frame Rate relay.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S41113-4.png "title =" 5.png"/>

Step 7:The preceding steps verify the communication between routers R1, R2, and R3. Now the connectivity with vror2 R3 is detected on vror2 R2, as shown in Figure 8.58. Vror2 R2 cannot communicate with R3, because Frame Relay in this experiment environment is a semi-mesh Frame Relay Network. From the VC plan, vrouters R2 and R3 each have only one virtual circuit that reaches R1. You can run the show frame relay pvc command on R2 and R3 to view their respective virtual circuit states, as shown in Figure 8.59 and figure 8.60, therefore, it can communicate with router R1 respectively, while R2 and R3 have no virtual circuit plans for each other, so the communication between them cannot be completed.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S441F-5.png "title =" 6.png"/>

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S46252-6.png "title =" 7.png"/>

Step 8:If there are two schemes for communication between router R2 and router R3 to solve this problem, one solution is to use router R1 as the Failover point for communication and exchange between R2 and router R3, that is to say, all traffic between R2 and R3 must be forwarded through router R1. If this scheme is used without the need to create an independent virtual circuit for R2 and R3 on the frame relay switch of the telecom operator, the investment cost will be lower, however, because router R1 needs to transfer traffic between R2 and R3, the traffic pressure on router R1 will increase. Another solution is to plan a full-mesh frame relay, which will be provided during subsequent demonstration, now, we need to implement the first solution to use router R1 as the Failover point for communication between R2 and R3 to complete communication between R2 and R3.

Configurations on vror2 R2:

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

Configuration on vror3 R3:

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

Understanding of the above configuration: according to the above configuration, we can see that the routers R2 and R3 do not use any new DLCI number, but use the original DLCI number that arrived at the router R1, it only adds a frame relay ing to each other's IP addresses. In other words, router R2 now uses the DLCI Number 201 to reach R1, and also uses the DLCI Number 201 to reach R3. The same is true for router R3.

Step 9:Check the connectivity between vror2 R2 and R3 again. ping R3 on vror2 R2, as shown in Figure 8.61 below. You can see that the communication is successfully completed, and then run the traceroute 192.168.1.3 Path Tracking command on vror2 R2, as shown in figure 8.62, we can know that the traffic from vror2 R2 to R3 is forwarded through 192.168.1.1R1.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S41343-7.png "title =" 8.png"/>

Demonstration: Physical Interface-based full-mesh Frame Relay Configuration

Demonstration objectives:In the previous demonstration, frame relay is configured based on a semi-mesh physical interface. In this demonstration, a full-mesh Frame Relay Network is configured.

Demo environment:As shown in figure 8.63.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S4Na-8.png "title =" 9.png"/>

Demo tool:Three Cisco routers and one frame relay switch.

Demonstration Background:The only difference between the background and "Demonstration: half-mesh Frame Relay configuration based on physical interfaces" is that a new virtual circuit is planned between router R2 and router R3 to form a fully-mesh frame relay, the vro uses the local DLCI Number 104 to reach R3. The vror3 uses the local DLCI number 401 to reach R2. Therefore, you need to add a frame relay route on the frame relay switch during the demonstration process.

Demo steps:

Step 1:In order to more intuitively demonstrate the configuration of a full-mesh frame relay, you must first Delete the router R2 and R3 In the previous demonstration and use R1 as the traffic transfer station to complete the communication configuration, and restore the frame relay network environment to the State that R2 and R3 cannot complete communication because they do not have a virtual circuit. The specific life of deleting related configurations is as follows:

R2 (config-if) # no frame-relaymap ip 192.168.1.3 201 broadcast

R3 (config-if) # no frame-relaymap ip 192.168.1.2 301 broadcast

Step 2:In the environment shown in Figure 8.63, configure the frame relay switch and add a virtual circuit for the routers R2 and R3 to complete the configuration of the Full-mesh Frame Relay. The configuration of the frame relay switch is as follows.

Configuration in S1/1 interface mode of the frame relay switch:

Fr-switching (config) # interfaces1/1

Fr-switching (config-if) # frame-relayroute 104 interface s1/2 401

Add configuration so that vror2 R2 can use the 104 DLCI number to reach vror3 R3

Configuration in S1/2 interface mode of the frame relay switch:

Fr-switching (config) # interfaces1/2

Fr-switching (config-if) # frame-relayroute 401 interface s1/1 104

Add configuration so that vror3 can use the 401 DLCI number to reach vror2 R2

Step 3:Configure the static ing between the new DLCI number and the IP address for Routers R2 and R3 to complete the access configuration of the Full-mesh frame relay.

PVC ing record added to R3 on vror2 R2:

R2 (config) # interfaces1/0

R2 (config-if) # frame-relaymap ip 192.168.1.3 104 broadcast

Add the PVC ing record to R2 on vror3 R3:

R3 (config) # interfaces1/0

R3 (config-if) # frame-relaymap ip 192.168.1.2 401 broadcast

Step 4:After completing the preceding configuration, check the connectivity between vror2 R2 and R3, as shown in Figure 8.64. The communication is successful. The network path of the route to the target is tracked. The result is shown in Figure 8.65. You can find that the traffic between the router R2 and R3 does not pass through R1, but directly reaches R3, because it is a fully-mesh frame relay, there is already a PVC link for direct communication between the router R2 and R3.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S43L7-9.png "title =" 10.png"/>

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S4AA-10.png "title =" 11.png"/>

Step 5:In this case, you can run the show frame-relay pvc command on vror2 R2 to view the status of the virtual circuit that exists on R2. as shown in Figure 8.66, two independent PVC instances exist on R2, if DLCI number is 104, it is used to arrive at router R3, And if DLCI number is 201, it is used to arrive at router R1. You can also run the show frame-relay map command to view the frame relay ing status of router R2, as shown in Figure 8.67 in the following figure.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/004S4N07-11.png "title =" 12.png"/>

This article is from the "unknown Christ" blog. For more information, contact the author!