Demonstration: configuration of Cisco sub-interface type Frame Relay

Demonstration: configuration of Cisco sub-interface type Frame Relay

Demo videos matching blog posts in http://edu.51cto.com/lecturer/user_id-7648423.html

Course name: Cisco CCNA-certified Frame Relay analysis 200-120) 9 lessons)

In this section, we will describe the subinterface type and sub-interface configuration of Frame Relay. The first thing we need to know is: Why does the concept of the subinterface of Frame Relay occur? What is its role? There are several types of Frame Relay subinterfaces. What are the meanings and differences of each type?

Understand the subinterface type of Frame Relay:

As shown in figure 8.68, sub-interfaces of the point-to-point type and multi-point multipoint sub-interfaces; point-to-point) A type of sub-interface is a link interface that simulates the characteristics of a leased line on a multi-channel access network. It is usually used when an enterprise connects to certain financial institutions, third-party access points are not allowed on the link, but traditional leased lines are too expensive. Therefore, point-to-point Frame Relay Links are used to replace traditional leased lines. Multi-Point multipoint) subinterfaces are usually used to connect two or more remote frame relay communication sites. A typical application is to connect the headquarters to multiple remote branches.

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

Why do we need to use the Frame Relay subinterface:

The frame relay sub-interface is actually a more adequate solution for hardware assets. For example, a central router, as shown in Figure 8.68 in the preceding figure, has only one physical interface. It connects two branches and one financial institution. solution 1: two physical interfaces and one physical interface are used to connect financial institutions, A physical interface is used to connect to the other two branches, which undoubtedly increases the hardware cost. You can also think about the problem. If the R1 of the central router has exhausted the WAN module slots, what if no redundant modules are available? Solution 2: Use a physical interface to draw a molecular interface on the physical interface. One point-to-point sub-interface is used to connect to the financial institution, and the other multiple point-to-point interface is used to connect to other remote branches, in this way, the hardware usage is higher, and there is only one cable introduced from the telecom operation, and the line management is simpler. The above is the reason for using the Frame Relay subinterface.

NOTE: If two types of sub-interfaces are used on a physical interface at the same time, the links connected by these two sub-interfaces will use an IP subnet independently.

Demonstration: configuration of Cisco sub-interface type Frame Relay

Demonstration objectives:Configure the subinterface of Frame Relay

Demo environment:The demo environment is shown in Figure 8.69.

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

Demonstration Background:Router R1 uses s1/0.1 Multi-Point frame relay subinterfaces to connect remote branches R2 and R3. They use an independent sub-interface 192.168.99.0/24; router R1 uses s1/0.2 point-to-point Frame Relay subinterfaces to connect to the financial institution's router R4, which is equivalent to a simulated leased line and uses an independent subnet.

Demo steps:

Step 1:Configure a frame relay switch to support the frame relay route from router R1 to each remote access point. The configuration of the frame relay switch is as follows:

Configuration of the frame relay switch:

Fr_switching (config) # frame-relay switching

Fr_switching (config) # interface s1/0

Fr_switching (config-if) # encapsulation frame-relay

Fr_switching (config-if) # frame-relay intf-type dce

Fr_switching (config-if) # clock rate 403200

Fr_switching (config-if) # frame-relay route 102 interface s1/1201

Fr_switching (config-if) # frame-relay route 103 interface s1/2301

Fr_switching (config-if) # frame-relay route 104 interface s1/3401

Fr_switching (config-if) # no shutdown

Fr_switching (config-if) # exit

Fr_switching (config) # interface s1/1

Fr_switching (config-if) # encapsulation frame-relay

Fr_switching (config-if) # frame-relay intf-type dce

Fr_switching (config-if) # clock rate 403200

Fr_switching (config-if) # frame-relay route 201 interface s1/0102

Fr_switching (config-if) # no shutdown

Fr_switching (config-if) # exit

Fr_switching (config) # interface s1/2

Fr_switching (config-if) # encapsulation frame-relay

Fr_switching (config-if) # frame-relay intf-type dce

Fr_switching (config-if) # clock rate 403200

Fr_switching (config-if) # frame-relay route 301 interface s1/0103

Fr_switching (config-if) # no shutdown

Fr_switching (config-if) # exit

Fr_switching (config) # interface s1/3

Fr_switching (config-if) # encapsulation frame-relay

Fr_switching (config-if) # frame-relay intf-type dce

Fr_switching (config-if) # clock rate 403200

Fr_switching (config-if) # frame-relay route 401 interface s1/0104

Fr_switching (config-if) # no shutdown

Fr_switching (config-if) # exit

!

Step 2:The configuration center router R1 uses different types of sub-interfaces for Frame Relay. The specific configuration is as follows:

VroR1Configuration:

R1 (config) # interface s1/0

R1 (config-if) # encapsulation frame-relay * must encapsulate the frame relay protocol on the physical interface.

R1 (config-if) # no shutdown * activates the physical interface.

R1 (config-if) # exit

R1 (config) # interface s1/0.1 multipoint * creates a multi-point Frame Relay subinterface.

R1 (config-subif) # ip address192.168.99.1 255.255.255.0 * write IP addresses for multiple idea interfaces.

R1 (config-subif) # frame-relay map ip192.168.99.2 102 broadcast * ing to r2.

R1 (config-subif) # frame-relay map ip 192.168.99.3 103 broadcast * ing configured to R3.

R1 (config-subif) # no shutdown

R1 (config-subif) # exit

R1 (config) # interface s1/0.2point-to-point * creates a point-to-point type frame relay subinterface.

R1 (config-subif) # ip address192.168.100.1 255.255.255.252 * writes IP addresses to point-to-point subinterfaces.

R1 (config-subif) # frame-relayinterface-dlci 104 * declares the DLCI number used by the point-to-point sub-interface.

R1 (config-subif) # no shutdown

R1 (config-subif) # exit

Note: In the preceding configuration, you must use frame-relay interface-dlci to declare the DLCI number that the sub-interface is using, instead of using the frame-relay map ip command to perform static ing, because there are only two points in the point-to-point frame relay link and no ing declaration is required. On the contrary, in the frame relay of multiple point-to-point interfaces, you do not need to use frame-relay interface-dlci to declare the DLCI number that the sub-interface is using. You need to use the frame-relay map ip command to perform static ing and to determine the remote connection.

Step 3:Now, the configuration of the multi-point interface connecting routers R2 and R3 to the central router R1 through the physical interface is as follows, because the configurations of the routers R2 and R3 are similar, therefore, no more instructions are provided.

Vror2 R2 Configuration:

R2 (config) # interface s1/0

R2 (config-if) # encapsulation frame-relay

R2 (config-if) # ip address 192.168.99.2 255.255.0

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

R2 (config-if) # no shutdown

R2 (config-if) # exit

Vror3 R3 Configuration:

R3 (config) # interface s1/0

R3 (config-if) # encapsulation frame-relay

R3 (config-if) # ip address 192.168.99.3 255.255.255.0

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

R3 (config-if) # no shutdown

R3 (config-if) # exit

Step 4:Vror4 uses point-to-point subinterfaces to connect to the point-to-point subinterfaces of the central router R1. The configuration on vror4 is as follows:

Vror4 R4 Configuration:

R4 (config) # interface s1/0

R4 (config-if) # encapsulation frame-relay

R4 (config-if) # no shutdown

R4 (config-if) # exit

R4 (config) # interface s1/0.1 point-to-point

R4 (config-subif) # ip address 192.168.100.2 255.255.255.252

R4 (config-subif) # frame-relayinterface-dlci 401

R4 (config-subif) # no shutdown

R4 (config-subif) # exit

Step 5:Now, you can view the status of the virtual circuits of each remote branch through show frame-relay pvc on the central router R1, as shown in Figure 8.70, it can be seen that all the three PVCs with the DLCI Number 102, 103, and 104 are active; then, you can run the show frame-relay map command to view the frame relay ing of each remote branch, as shown in Figure 8.71. You can clearly see the types and ing of each sub-interface; finally, the connectivity problem with each branch can be detected on the center router R1, as shown in Figure 8.72. It can be seen that the center router successfully communicates with each branch.

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/04513R3R-2.png "style =" float: none; "title =" 3.png"/>

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/04513R1V-3.png "style =" float: none; "title =" 4.png"/>

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