CCNA Study Notes (11)--Frame Relay (FR)

This section lets us learn the next Frame Relay

Frame Relay in CCNA's exams and daily work are seldom useful, but we still want to know, it is after all a CCNA in the focus.

Frame Relay (Frames relay)

Also referred to as FR

Frame Relay is an important WAN technology, its main function is to connect two or more long-distance LAN. Frame Relay is mainly a packet switching technology, usually we just want to know how to connect LAN through Frame Relay and long-distance LAN connection is OK, do not know the connection, these are ISP things, but now here is learning, so it is not the same.

Frame Relay provides an object-oriented transport service, two of users before transmitting data, first through the network to establish a logical virtual link, we call this a virtual circuit .

1, the virtual circuit of frame relay is divided into two kinds:

PVC (Permanent virtual circuit): Permanently established circuit, by the ISP vendor on the frame Relay switch with static exchange table defined, regardless of whether the user is used, has always existed.

SCV (Switching virtual circuit): is temporarily established, when the user is used to establish, when not used, automatically disconnected.

But we have encountered the most permanent virtual circuit (PCV), so the following are permanent virtual circuits.

Frame Relay is mainly owned by:

1, large transmission bandwidth (this can be negotiated with the ISP, the larger the more expensive)

2, with congestion control function (when the line congestion, will give the device notification, request to reduce the transmission rate of data sent)

2, the package configuration of Frame Relay:

Router (config) #int s0/0 enter port mode

Router (config-if) #encapsulation Frame-relay package type is Cisco

By default, we use the above configuration directly, that is, Cisco's package mode.

Router (config) #int s0/0 enter port mode

Router (config-if) #encapsulation frame-relay ITEF Package Type: Itef

This is the ITEF package mode.

3. Frame Relay Terminology (DLCI):

DLCI (data link connection identifier) Link link identification.

A, typically assigned by a Frame Relay service provider. (e.g. telecommunications)

B, DLCI only have local views.

C, DLCI 0-15 and 1008--1023 are reserved for special purposes. The DLCI range assigned by the frame Relay service provider is from----1007.

Note: In the daily experiment, the average is the hundred and the digit is the route number, 10 bits is zero or 1

Such as:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/56/C6/wKioL1SNscfjGxbZAAGXwWJXfx8502.jpg "title=" 2.png " alt= "Wkiol1snscfjgxbzaagxwwjxfx8502.jpg"/>

4. LMI (local management Infterface)

Local Management interface:

is the signaling standard between the customer's front-end device and the frame Relay switch. It mainly manages the connection between the devices and maintains the connection status between the devices.

Cisco's devices support three types:

Ansi

Cisco

q933a

Note: Cisco devices are used by default: Cisco but ANSI & Q933A are public

5. Reverse arp (inverse arp)

Reverse address Interpretation protocol (inverse ARP), after using the Reverse address Interpretation protocol, the device can dynamically learn to the end of the address protocol to establish a peer-to-side and local DLCI mapping relationship.

Note: The default is to turn on reverse ARP.

Ways to turn off reverse ARP:

Router (config) #int S1/1

Router (config-if) #no frame-relay ARP

6. Assign DLCI number

Router (config) #int s1/1

Router (config-if) #frame-relay Route came in the DLCI out interface DLCI number out interface

7, the configuration of Frame Relay:

Topology diagram:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/57/0A/wKioL1SP8A7yBk6NAACX7JpBM4Q247.jpg "title=" 1.png " Width= "718" height= "283" border= "0" hspace= "0" vspace= "0" style= "width:718px;height:283px;" alt= " Wkiol1sp8a7ybk6naacx7jpbm4q247.jpg "/>

1, r1:192.168.134.1 (s2/0) Dlci:102/1o3

r3:192.168.134.2 (s2/0) dlci:201

r4:192.168.134.3 (s2/0) dlci:301

2, requirements: R1, R2, R3 interoperability.

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

Then we'll start configuring the routers for each node:

Router (config) #int s1/0

Router (config-if) #ip add 192.168.123.1 255.255.255.0

Router (config-if) #encapsulation Frame-relay

Router (config-if) #frame-relay interface-dlci XX (DLCI)

Router (config-if) #no sh

The configuration of the three nodes is similar, but the IP, DLCI number a little different.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/57/0D/wKiom1SP8E-zv5Z9AAIq2HLqamU628.jpg "title=" 4.png " Width= "718" height= "236" border= "0" hspace= "0" vspace= "0" style= "width:718px;height:236px;" alt= " Wkiom1sp8e-zv5z9aaiq2hlqamu628.jpg "/>

Here we start to configure our Frame Relay switch, because it is using a router instead of a Frame relay switch, so the first thing we want to do is when:

1.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/56/C9/wKioL1SOTe_Sm4VpAACWSPEApqg860.jpg "title=" 3.png " Width= "718" height= "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" wkiol1sote_sm4vpaacwspeapqg860.jpg "style=" width:718px ; height:62px; "/>

2, enter the port mode: (The following several steps, respectively)

Router (config) #int s1/1

A, change the data packaging method (the serial port by default, the package is: HDLC Ethernet: ARPA)

Router (config-if) #encapsulation Frame-relay

B, sealing and binding relay

C, Binding Relay interface type

Router (config-if) #frame-relay intf-type DCE

D. Define the Frame Relay interface management type

E, define the clock rate

Router (config-if) #clock rate 64000

F, set Frame Relay Exchange, specify the DLCI interchange between two synchronization ports

Router (config-if) #frame-relay route local DLCI number interface data out of interface to end of DLCI number

G, start the interface

Router (config-if) #no sh

Configuration of the R1:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/57/10/wKiom1SQKrixPaRDAAFBDxZHzVk833.jpg "style=" width : 718px;height:119px; "title=" 5.png "width=" 718 "height=" 119 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1sqkrixpardaafbdxzhzvk833.jpg "/>

Configuration of the R2:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/57/10/wKiom1SQKriT2rlMAAErM5eEJkA315.jpg "style=" width : 718px;height:140px; "title=" 6.png "width=" 718 "height=" "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1sqkrit2rlmaaerm5eejka315.jpg "/>

Configuration of the R3:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/57/0D/wKioL1SQK1jy5eXgAAEm9DX1cu0030.jpg "style=" width : 718px;height:125px; "title=" 7.png "width=" 718 "height=" "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1sqk1jy5exgaaem9dx1cu0030.jpg "/>

Let's configure it in detail on the Frame Relay switch .

S1/1 Interface Configuration:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/57/10/wKiom1SQLUug1lxcAAQOvsAf4QI067.jpg "style=" width : 718px;height:318px; "title=" 10.png "width=" 718 "height=" 318 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1sqluug1lxcaaqovsaf4qi067.jpg "/>

S1/2 Interface Configuration:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/57/0E/wKioL1SQLeuDzNiwAAL994TxaO4138.jpg "style=" width : 718px;height:210px; "title=" 9.png "width=" 718 "height=" "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1sqleudzniwaal994txao4138.jpg "/>

S1/3 Interface Configuration:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/57/0E/wKioL1SQLevyN3tWAAL8OyudeyU636.jpg "style=" width : 718px;height:214px; "title=" 8.png "width=" 718 "height=" 214 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1sqlevyn3twaal8oyudeyu636.jpg "/>

Let's test the following:

R1---ping----r2/r1---ping---R3

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/57/10/wKiom1SQLhWSLK3eAAK-i9hFxS4651.jpg "title=" 11.png "Width=" 718 "height=" 222 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:718px;height:222px; "alt=" Wkiom1sqlhwslk3eaak-i9hfxs4651.jpg "/>

By the above we can see that the communication can be normal. But R2--ping--r3 temporarily not yet normal communication.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/57/13/wKioL1SQ8YuQl50cAAHec9MDARE854.jpg "title=" 12.png "Width=" 718 "height=" 185 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:718px;height:185px; "alt=" Wkiol1sq8yuql50caahec9mdare854.jpg "/>

We found the map table above, the way to learn is: dynamic learning, to achieve full-network communication, the dynamic learning map to turn off.

To switch off the inverse ARP method:

Router (config-if) #no ARP Frame-relay

Clears the cache information for the frame-relay.

Router (config) #clear frame-relay counter

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/57/16/wKioL1SRMMuj-5OrAAFfrdexPa8790.jpg "title=" 13.png "Width=" 718 "height=" "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:718px;height:105px; "alt=" Wkiol1srmmuj-5oraaffrdexpa8790.jpg "/>

The above settings on the R2/R3 are as follows:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/57/19/wKiom1SRMraju1qOAAJJnz4N-P0056.jpg "title=" 14.png "Width=" 718 "height=" "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:718px;height:200px; "alt=" Wkiom1srmraju1qoaajjnz4n-p0056.jpg "/>

The following is the manual configuration of the map table, so that we can directly interoperability,:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/57/17/wKioL1SROG6zFw20AAKADSjMj7E337.jpg "style=" width : 718px;height:235px; "title=" 15.png "width=" 718 "height=" 235 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1srog6zfw20aakadsjmj7e337.jpg "/>

Router (config) #int s1/0

Router (config) #frame-relay map IP address of the other party B's DLCI number broadcast

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/57/1A/wKiom1SRN82hafenAAIyljnd3_Q040.jpg "style=" width : 718px;height:200px; "title=" 16.png "width=" 718 "height=" "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1srn82hafenaaiyljnd3_q040.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/57/17/wKioL1SROG7CK7GLAAI-nrUgWgU692.jpg "style=" width : 718px;height:216px; "title=" 17.png "width=" 718 "height=" 216 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1srog7ck7glaai-nrugwgu692.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/57/1A/wKiom1SRN82gcgjXAAHjOZGm6Jo446.jpg "style=" width : 718px;height:213px; "title=" 18.png "width=" 718 "height=" 213 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1srn82gcgjxaahjozgm6jo446.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/57/17/wKioL1SROG6Dyd0xAALWNpklVGI729.jpg "style=" width : 718px;height:216px; "title=" 19.png "width=" 718 "height=" 216 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1srog6dyd0xaalwnpklvgi729.jpg "/>

By now, it can be seen that R1 R2 R3 can communicate with each other.

Now we have another problem is: R1 R2 R3 How can ping through itself?

Now Test yourself and ping yourself first.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/57/1A/wKiom1SROk2wQcttAAF7M-IfDcA235.jpg "style=" width : 718px;height:215px; "title=" 20.png "width=" 718 "height=" 215 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1srok2wqcttaaf7m-ifdca235.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/57/17/wKioL1SROu6DNukfAAIAssmebIE433.jpg "style=" width : 718px;height:218px; "title=" 21.png "width=" 718 "height=" 218 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1srou6dnukfaaiassmebie433.jpg "/>

Here's how to configure it:

Router (config) #int s1/0

Router (config-if) #frame-relay map IP own IP address own DLCI number

Test results:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/57/1A/wKiom1SROk2zPZguAAHb_0ZGtS4066.jpg "style=" width : 718px;height:213px; "title=" 22.png "width=" 718 "height=" 213 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1srok2zpzguaahb_0zgts4066.jpg "/>

R2 R3 in accordance with the above method to manually configure their own map, then you can ping himself.

This is the day!! If you think of something else later, add it again!

The following link to find the relevant information sent to everyone to find:

1, Frame Relay configuration.

2, black tea Three Cups

3, Baidu (Frame Relay) detailed

Good luck to you all!!!

This article is from the "Last Bus" blog, so be sure to keep this source http://hznethome.blog.51cto.com/722914/1591107

CCNA Study Notes (11)--Frame Relay (FR)