{"id":37271,"date":"2019-10-31T22:16:41","date_gmt":"2019-10-31T19:16:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii\/"},"modified":"2019-10-31T22:16:41","modified_gmt":"2019-10-31T19:16:41","slug":"trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","title":{"rendered":"Training Cisco 200-125 CCNA v3.0. Ziua 18. Bazele rut\u0103rii","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ast\u0103zi vom \u00eencepe studiul routerelor. Dac\u0103 a\u021bi urmat cursul meu video de la lec\u021bia 1 p\u00e2n\u0103 la 17, atunci a\u021bi studiat deja bazele switch-urilor. Acum trecem la urm\u0103toarea device \u2013 routerul. A\u0219a cum \u0219ti\u021bi din lec\u021bia video anterioar\u0103, unul dintre subiectele cursului CCNA se nume\u0219te astfel \u2013 Cisco Switching & Routing.<\/p>\n

\u00cen aceast\u0103 serie nu vom studia routerele Cisco, ci vom explora conceptul de rutare \u00een general. Vor fi trei subiecte. Primul \u2013 este o prezentare general\u0103 a ceea ce \u0219ti\u021bi deja despre routere \u0219i o discu\u021bie despre modul \u00een care acest lucru poate fi aplicat \u00eempreun\u0103 cu cuno\u0219tin\u021bele dob\u00e2ndite \u00een cadrul studiului switch-urilor. Trebuie s\u0103 \u00een\u021belegem \u00een ce const\u0103 colaborarea dintre switch-uri \u0219i routere.<\/p>\n

\"Training
\n
\nApoi vom explora ce reprezint\u0103 rutarea, ce \u00eenseamn\u0103 \u0219i cum func\u021bioneaz\u0103, dup\u0103 care vom trece la tipurile de protocoale de rutare. Ast\u0103zi folosesc topologia pe care deja a\u021bi v\u0103zut-o \u00een lec\u021biile anterioare. <\/a><\/noindex><\/p>\n

Am discutat despre cum datele se deplaseaz\u0103 \u00een re\u021bea \u0219i cum se desf\u0103\u0219oar\u0103 str\u00e2ngerea de m\u00e2ini \u00een trei etape TCP. Primul mesaj trimis \u00een re\u021bea reprezint\u0103 un pachet SYN. S\u0103 examin\u0103m cum se desf\u0103\u0219oar\u0103 str\u00e2ngerea de m\u00e2ini \u00een trei etape atunci c\u00e2nd un computer cu adresa IP 10.1.1.10 dore\u0219te s\u0103 se conecteze la un server 30.1.1.10, adic\u0103 \u00eencearc\u0103 s\u0103 stabileasc\u0103 o conexiune FTP.
\nPentru a \u00eencepe conexiunea, computerul creeaz\u0103 un port surs\u0103 cu un num\u0103r aleator 25113. Dac\u0103 a\u021bi uitat cum se desf\u0103\u0219oar\u0103 acest proces, v\u0103 sf\u0103tuiesc s\u0103 reviziona\u021bi lec\u021biile video anterioare \u00een care am discutat acest subiect. <\/p>\n

\"Training
\n
\nApoi, el plaseaz\u0103 \u00een cadrul num\u0103rul portului destina\u021biei, deoarece \u0219tie c\u0103 trebuie s\u0103 se conecteze la portul 21, apoi adaug\u0103 informa\u021biile de nivelul 3 OSI, adic\u0103 adresa sa IP \u0219i adresa IP a destina\u021biei. Datele, eviden\u021biate cu puncte, nu se schimb\u0103 p\u00e2n\u0103 c\u00e2nd nu ajung la destina\u021bie. Odat\u0103 ajunse la server, ele de asemenea nu se schimb\u0103, dar serverul adaug\u0103 informa\u021bii de nivelul 2 \u00een cadrul, adic\u0103 adresa MAC. Acest lucru se datoreaz\u0103 faptului c\u0103 switch-urile percep doar informa\u021biile de nivelul 2 OSI. \u00cen acest scenariu, routerul este singurul dispozitiv de re\u021bea care consider\u0103 informa\u021biile de nivelul 3, \u00een mod natural, \u0219i computerul lucreaz\u0103 cu aceste informa\u021bii. A\u0219adar, switch-ul lucreaz\u0103 doar cu informa\u021biile de nivelul 2, iar routerul \u2013 cu cele de nivelul 3. <\/p>\n

Switchul cunoa\u0219te adresa MAC ini\u021bial\u0103 XXXX:XXXX:1111 \u0219i dore\u0219te s\u0103 afle adresa MAC a serverului la care se conecteaz\u0103 computerul. Compar\u0103 adresa IP ini\u021bial\u0103 cu adresa de destina\u021bie, \u00een\u021beleg\u00e2nd c\u0103 aceste dispozitive se afl\u0103 \u00een subnete diferite, \u0219i decide s\u0103 utilizeze gateway-ul pentru a ie\u0219i \u00een alt\u0103 subre\u021bea.<\/p>\n

Adesea, mi se pune \u00eentrebarea cine decide care ar trebui s\u0103 fie adresa IP a gateway-ului. \u00cen primul r\u00e2nd, acest lucru este decis de administratorul re\u021belei care creeaz\u0103 re\u021beaua \u0219i furnizeaz\u0103 adrese IP fiec\u0103rui dispozitiv. Ca administrator, pute\u021bi atribui routerului orice adres\u0103 din intervalul de adrese permise ale subre\u021belei dumneavoastr\u0103. De obicei, aceasta este prima sau ultima adres\u0103 valid\u0103, dar nu exist\u0103 reguli stricte cu privire la atribuire. \u00cen cazul nostru, administratorul a atribuit adresa gateway-ului, sau routerului, 10.1.1.1 \u0219i i-a asociat-o portului F0\/0. <\/p>\n

C\u00e2nd configura\u021bi o re\u021bea pe un computer cu o adres\u0103 IP static\u0103 de 10.1.1.10, atribui\u021bi o masc\u0103 de subre\u021bea 255.255.255.0 \u0219i un gateway implicit de 10.1.1.1. Dac\u0103 nu utiliza\u021bi o adres\u0103 static\u0103, atunci computerul utilizeaz\u0103 DHCP, care atribuie o adres\u0103 dinamic\u0103. Indiferent de adresa IP pe care o folose\u0219te computerul, static\u0103 sau dinamic\u0103, pentru a ie\u0219i \u00eentr-o alt\u0103 re\u021bea trebuie s\u0103 existe adresa unui gateway. <\/p>\n

Astfel, computerul 10.1.1.10 \u0219tie c\u0103 trebuie s\u0103 trimit\u0103 un cadru routerului 10.1.1.1. Aceast\u0103 transmitere are loc \u00een interiorul re\u021belei locale, unde adresa IP nu conteaz\u0103, ci doar adresa MAC. S\u0103 presupunem c\u0103 computerul nu a interac\u021bionat niciodat\u0103 cu routerul \u0219i nu cunoa\u0219te adresa lui MAC, astfel c\u0103 trebuie mai \u00eent\u00e2i s\u0103 trimit\u0103 o solicitare ARP, \u00eentreb\u00e2nd toate dispozitivele din subre\u021bea: \u201ehei, cine dintre voi are adresa 10.1.1.1? V\u0103 rog s\u0103-mi comunica\u021bi adresa voastr\u0103 MAC!\u201d. Deoarece ARP este un mesaj de difuzare, el ajunge la toate porturile tuturor dispozitivelor, inclusiv routerul. <\/p>\n

Computer 10.1.1.12 receives an ARP and thinks: \"No, my address is not 10.1.1.1,\" and discards the request; similarly, computer 10.1.1.13 does the same. The router, upon receiving the request, understands that it is being asked and sends the MAC address of port F0\/0 \u2013 all ports have different MAC addresses \u2013 to computer 10.1.1.10. Now, knowing the gateway address XXXX:AAAA, which in this case is the destination address, the computer adds it to the end of the frame addressed to the server. At the same time, it sets the frame's FCS\/CRC header, which is an error-checking mechanism for transmission. <\/p>\n

\"Training
\n
\nAfter this, the frame from computer 10.1.1.10 is sent over the wires to router 10.1.1.1. Upon receiving the frame, the router removes the FCS\/CRC, using the same algorithm for verification as the computer. The data consists of nothing more than a series of zeros and ones. If the data is corrupted, meaning a 1 becomes a 0 or a 0 becomes a 1, or there is data leakage, which often occurs when using a hub, then the device must resend the frame. <\/p>\n

If the FCS\/CRC check is successful, the router looks at the source and destination MAC addresses and removes them since this information is at Layer 2, and moves on to the frame body, which contains Layer 3 information. From it, it learns that the information contained in the frame is intended for the device with IP address 30.1.1.10. <\/p>\n

The router somehow knows where this device is located. We did not discuss this question when we examined how switches work, so let's consider it now. The router has 4 ports, so I have added a few more connections to it. So, how does the router know that the data for the device with IP address 30.1.1.10 needs to be sent through port F0\/1? Why doesn't it send it through port F0\/3 or F0\/2?<\/p>\n

The thing is that the router works with a routing table. Every router has such a table that helps it decide which port to send a specific frame through. <\/p>\n

\"Training
\n
\n\u00cen acest caz, portul F0\/0 este configurat cu adresa IP 10.1.1.1, ceea ce \u00eenseamn\u0103 c\u0103 este conectat la re\u021beaua 10.1.1.10\/24. \u00cen mod similar, portul F0\/1 este configurat cu adresa 20.1.1.1, adic\u0103 este conectat la re\u021beaua 20.1.1.0\/24. Routerul cunoa\u0219te aceste re\u021bele deoarece sunt conectate direct la porturile sale. Astfel, informa\u021bia c\u0103 traficul pentru re\u021beaua 10.1.1.0\/24 trebuie s\u0103 treac\u0103 prin portul F0\/0, iar pentru re\u021beaua 20.1.1.0\/24 - prin portul F0\/1, este cunoscut\u0103 \u00een mod implicit. Dar de unde \u0219tie routerul prin ce porturi s\u0103 func\u021bioneze cu celelalte re\u021bele?<\/p>\n

Observ\u0103m c\u0103 re\u021beaua 40.1.1.0\/24 este conectat\u0103 la portul F0\/2, re\u021beaua 50.1.1.0\/24 - la portul F0\/3, iar re\u021beaua 30.1.1.0\/24 leag\u0103 al doilea router de server. Al doilea router are, de asemenea, o tabel\u0103 de rutare, care indic\u0103 faptul c\u0103 re\u021beaua 30. este conectat\u0103 la portul s\u0103u, pe care \u00eel denumim 0\/1, iar cu primul router este conectat prin portul 0\/0. Acest router \u0219tie c\u0103 portul s\u0103u 0\/0 este conectat la re\u021beaua 20., iar portul 0\/1 este conectat la re\u021beaua 30., \u0219i nu \u0219tie nimic mai mult.<\/p>\n

Similar, primul router cunoa\u0219te re\u021belele 40. \u0219i 50., care sunt conectate la porturile 0\/2 \u0219i 0\/3, dar nu \u0219tie nimic despre re\u021beaua 30. Protocolul de rutare ofer\u0103 routerelor informa\u021bia pe care nu o de\u021bin \u00een mod implicit. Mecanismul prin care aceste routere interac\u021bioneaz\u0103 \u00eentre ele constituie baza rut\u0103rii, exist\u00e2nd rutare dinamic\u0103 \u0219i static\u0103. <\/p>\n

Rutarea static\u0103 const\u0103 \u00een faptul c\u0103 primul router prime\u0219te informa\u021bia: dac\u0103 trebuie s\u0103 se conecteze la re\u021beaua 30.1.1.0\/24, atunci trebuie s\u0103 foloseasc\u0103 portul F0\/1. Totu\u0219i, c\u00e2nd al doilea router prime\u0219te trafic de la server destinat computerului 10.1.1.10, nu \u0219tie ce s\u0103 fac\u0103, deoarece \u00een tabela sa de rutare are doar informa\u021bii despre re\u021belele 30. \u0219i 20. Deci, acestui router trebuie s\u0103 \u00eei fie configurat\u0103 \u0219i rutarea static\u0103: dac\u0103 prime\u0219te trafic pentru re\u021beaua 10., trebuie s\u0103-l trimit\u0103 prin portul 0\/0. <\/p>\n

Problema rut\u0103rii statice este c\u0103 trebuie s\u0103 configurez manual primul router s\u0103 func\u021bioneze cu re\u021beaua 30., iar al doilea router s\u0103 func\u021bioneze cu re\u021beaua 10. Este simplu dac\u0103 am doar 2 routere, dar c\u00e2nd am 10 routere, configurarea rut\u0103rii statice consum\u0103 o mul\u021bime de timp. \u00cen acest caz, are sens s\u0103 folosim rutarea dinamic\u0103.
\nAstfel, dup\u0103 ce a primit un cadru de la computer, primul router verific\u0103 tabela sa de rutare \u0219i decide s\u0103-l trimit\u0103 prin portul F0\/1. \u00cen acest proces, adaug\u0103 la cadru adresa MAC a sursei XXXX.BBBB \u0219i adresa MAC a destina\u021biei XXXX.CCCC. <\/p>\n

\"Training
\n
\nDup\u0103 ce a primit acest cadru, al doilea router \u00abtaie\u00bb adresele MAC care \u021bin de nivelul doi OSI \u0219i trece la informa\u021biile de nivel trei. Observ\u0103 c\u0103 adresa IP a destina\u021biei 30.1.1.10 apar\u021bine acelea\u0219i re\u021bele ca portul 0\/1 al routerului, adaug\u0103 adresa MAC a sursei \u0219i adresa MAC a dispozitivului de destina\u021bie \u0219i trimite cadrul serverului. <\/p>\n

\"Training
\n
\nA\u0219a cum am men\u021bionat, procesul similar se repet\u0103 \u00een direc\u021bia invers\u0103, adic\u0103 are loc a doua etap\u0103 de handshake, \u00een care serverul trimite \u00eenapoi un mesaj SYN ACK. \u00cenainte de aceasta, elimin\u0103 toat\u0103 informa\u021bia inutil\u0103 \u0219i p\u0103streaz\u0103 doar pachetul SYN.<\/p>\n

\"Training
\n
\nDup\u0103 ce a primit acest pachet, al doilea router analizeaz\u0103 informa\u021biile primite, le completeaz\u0103 \u0219i le trimite mai departe. <\/p>\n

Deci, \u00een lec\u021biile anterioare am studiat cum func\u021bioneaz\u0103 un switch, iar acum am \u00eenv\u0103\u021bat cum func\u021bioneaz\u0103 routerele. S\u0103 r\u0103spundem la \u00eentrebarea ce reprezint\u0103 rutarea \u00een sens global. S\u0103 presupunem c\u0103 ai \u00eent\u00e2lnit un indicator de drum a\u0219ezat la o intersec\u021bie cu circula\u021bie rotund\u0103. Vezi c\u0103 prima ramifica\u021bie duce la baza For\u021belor Aeriene Regale Fairfax, a doua la aeroport, a treia la sud. Dac\u0103 alegi ie\u0219irea a patra, ajungi la un impas, iar prin a cincea po\u021bi trece prin centrul ora\u0219ului spre castelul Braxby. <\/p>\n

\"Training
\n
\n\u00cen general, rutarea este ceea ce determin\u0103 routerul s\u0103 ia decizii cu privire la direc\u021bia \u00een care s\u0103 direc\u021bioneze traficul. \u00cen acest caz, tu, ca \u0219ofer, trebuie s\u0103 iei o decizie cu privire la ie\u0219irea de la intersec\u021bie pe care s\u0103 o folose\u0219ti. \u00cen re\u021bele, routerele trebuie s\u0103 ia decizii despre unde s\u0103 trimit\u0103 pachete sau cadre. Trebuie s\u0103 \u00een\u021belegi c\u0103 rutarea permite crearea de tabele pe baza c\u0103rora routerele iau aceste decizii. <\/p>\n

A\u0219a cum am spus, exist\u0103 rutare static\u0103 \u0219i dinamic\u0103. S\u0103 examin\u0103m rutarea static\u0103, pentru care voi desena 3 dispozitive conectate \u00eentre ele, primul \u0219i al treilea dispozitiv fiind conectate la re\u021bele. S\u0103 presupunem c\u0103 o re\u021bea 10.1.1.0 dore\u0219te s\u0103 se conecteze la re\u021beaua 40.1.1.0, iar \u00eentre routere se afl\u0103 re\u021belele 20.1.1.0 \u0219i 30.1.1.0.<\/p>\n

\"Training
\n
\n\u00cen acest caz, porturile routerelor trebuie s\u0103 apar\u021bin\u0103 unor subre\u021bele diferite. Routerul 1 \u0219tie implicit doar despre re\u021belele 10. \u0219i 20. \u0219i nu \u0219tie nimic despre celelalte re\u021bele. Routerul 2 \u0219tie doar despre re\u021belele 20. \u0219i 30., deoarece acestea sunt conectate la el, iar routerul 3 \u0219tie doar despre re\u021belele 30. \u0219i 40. Dac\u0103 re\u021beaua 10. vrea s\u0103 comunice cu re\u021beaua 40., trebuie s\u0103 \u00eei spun routerului 1 despre re\u021beaua 30. \u0219i c\u0103, dac\u0103 vrea s\u0103 transmit\u0103 un pachet din re\u021beaua 40., trebuie s\u0103 foloseasc\u0103 interfa\u021ba pentru re\u021beaua 20. \u0219i s\u0103 trimit\u0103 pachetul prin re\u021beaua 20.<\/p>\n

Pentru al doilea router, trebuie s\u0103 \u00eei aloc 2 rute: dac\u0103 vrea s\u0103 transmit\u0103 un pachet din re\u021beaua 40. \u00een re\u021beaua 10., trebuie s\u0103 foloseasc\u0103 portul re\u021belei 20., iar pentru a transmite un pachet din re\u021beaua 10. \u00een re\u021beaua 40. \u2013 portul re\u021belei 30. \u00cen mod similar, trebuie s\u0103-i ofer routerului 3 informa\u021bii despre re\u021belele 10. \u0219i 20.<\/p>\n

Dac\u0103 ave\u021bi re\u021bele mici, configurarea rut\u0103rii statice este foarte simpl\u0103. Totu\u0219i, pe m\u0103sur\u0103 ce re\u021beaua cresc, apar tot mai multe probleme cu rutarea static\u0103. S\u0103 presupunem c\u0103 a\u021bi creat o nou\u0103 conexiune care leag\u0103 direct routerele \u00eent\u00e2i \u0219i trei. \u00cen acest caz, protocolul de rutare dinamic va actualiza automat tabela de rutare a routerului 1, indic\u00e2nd urm\u0103toarele: \u201edac\u0103 trebuie s\u0103 comunica\u021bi cu routerul 3, folosi\u021bi ruta direct\u0103\u201d!<\/p>\n

\"Training
\n
\nExist\u0103 dou\u0103 tipuri de protocoale de rutare: protocolul de gateway intern IGP \u0219i protocolul de gateway extern EGP. Primul protocol opereaz\u0103 cu un sistem autonom, cunoscut sub numele de domeniu de rutare. S\u0103 presupunem c\u0103 ave\u021bi o organiza\u021bie mic\u0103, cu doar 5 routere. Dac\u0103 discut\u0103m doar despre comunicarea \u00eentre aceste routere, ne referim la IGP; dac\u0103 utiliza\u021bi re\u021beaua dumneavoastr\u0103 pentru a comunica cu internetul, a\u0219a cum fac furnizorii de servicii ISPs, atunci utiliza\u021bi EGP. <\/p>\n

\"Training
\n
\nIGP utilizeaz\u0103 3 protocoale populare: RIP, OSPF \u0219i EIGRP. Curriculumul CCNA men\u021bioneaz\u0103 doar ultimele dou\u0103 protocoale, deoarece RIP este \u00eenvechit. Acesta este cel mai simplu dintre protocoalele de rutare, care este \u00eenc\u0103 utilizat \u00een anumite cazuri, totu\u0219i nu ofer\u0103 securitatea necesar\u0103 \u00een re\u021bea. Aceasta este una dintre motivele pentru care Cisco a exclus RIP din curriculum. Totu\u0219i, voi vorbi \u00een continuare despre el, deoarece studiul s\u0103u contribuie la \u00een\u021belegerea conceptelor de baz\u0103 ale rut\u0103rii. <\/p>\n

\"Training
\n
\nClasificarea protocoalelor EGP utilizeaz\u0103 dou\u0103 protocoale: BGP \u0219i protocolul EGP propriu-zis. \u00cen cursul CCNA, ne vom concentra doar pe BGP, OSPF \u0219i EIGRP. Discu\u021bia despre RIP poate fi considerat\u0103 informa\u021bie suplimentar\u0103, care va fi reflectat\u0103 \u00eentr-unul dintre videoclipurile noastre.
\nExist\u0103 \u00eenc\u0103 dou\u0103 tipuri de protocoale de rutare: protocoalele de rutare prin vector de distan\u021b\u0103 Distance Vector \u0219i protocoalele de rutare cu starea leg\u0103turii Link State. <\/p>\n

\"Training
\n
\nPrimul protocol examineaz\u0103 vectorii de distan\u021b\u0103 \u0219i direc\u021bie. De exemplu, pot stabili o conexiune direct\u0103 \u00eentre routerul R1 \u0219i R4, sau pot realiza conexiunea pe calea R1-R2-R3-R4. C\u00e2nd vorbim despre protocoalele de rutare care folosesc metoda vectorului de distan\u021b\u0103, \u00een acest caz, conexiunea se va realiza \u00eentotdeauna pe cel mai scurt drum. De asemenea, nu conteaz\u0103 c\u0103 aceast\u0103 conexiune va avea o vitez\u0103 minim\u0103. \u00cen cazul nostru, este de 128 kbit\/s, ceea ce este mult mai lent dec\u00e2t conexiunea pe traseul R1-R2-R3-R4, unde viteza este de 100 mbit\/s. <\/p>\n

S\u0103 analiz\u0103m protocolul de rutare prin vector de distan\u021b\u0103 RIP. Voi ad\u0103uga \u00een fa\u021ba routerului R1 re\u021beaua 10., iar \u00een spatele routerului R4 \u2013 re\u021beaua 40. S\u0103 presupunem c\u0103 \u00een aceste re\u021bele se afl\u0103 multe computere. Dac\u0103 vreau s\u0103 stabilesc o conexiune \u00eentre re\u021beaua 10. R1 \u0219i re\u021beaua 40. R4, voi desemna R1 o rutare static\u0103 de tip: \u201edac\u0103 trebuie s\u0103 te conectezi la re\u021beaua 40., folose\u0219te conexiunea direct\u0103 cu routerul R4\u201d. Astfel, pe toate cele 4 routere va trebui s\u0103 configurez manual RIP. Apoi, tabela de rutare R1 va informa automat c\u0103, dac\u0103 re\u021beaua 10. dore\u0219te s\u0103 se conecteze la re\u021beaua 40., trebuie s\u0103 foloseasc\u0103 conexiunea direct\u0103 R1-R4. Chiar dac\u0103 ocolirea ar putea fi mai rapid\u0103, protocolul Distance Vector va alege \u00eentotdeauna cel mai scurt drum cu cea mai mic\u0103 distan\u021b\u0103 de transfer. <\/p>\n

OSPF este un protocol de rutare cu starea leg\u0103turii, care \u00eentotdeauna verific\u0103 starea sec\u021biunilor de re\u021bea. \u00cen acest caz, el evalueaz\u0103 viteza canalelor \u0219i, dac\u0103 observ\u0103 c\u0103 viteza de transfer a traficului pe canalul R1-R4 este foarte sc\u0103zut\u0103, va alege calea cu o vitez\u0103 mai mare R1-R2-R3-R4, chiar dac\u0103 lungimea acesteia dep\u0103\u0219e\u0219te cea mai scurt\u0103 cale. Astfel, dac\u0103 voi configura protocolul OSPF pe toate routerele, atunci c\u00e2nd re\u021beaua 40. \u00eencearc\u0103 s\u0103 se conecteze la re\u021beaua 10., traficul va fi trimis pe traseul R1-R2-R3-R4. A\u0219adar, RIP este un protocol de rutare prin vector de distan\u021b\u0103, iar OSPF este un protocol de rutare cu starea leg\u0103turii.<\/p>\n

Exist\u0103 un alt protocol \u2013 EIGRP, un protocol de rutare proprietar Cisco. Dac\u0103 vorbim despre echipamentele de re\u021bea ale altor produc\u0103tori, cum ar fi Juniper, acestea nu suport\u0103 EIGRP. Este un protocol de rutare excelent, care este mult mai eficient dec\u00e2t RIP \u0219i OSPF, dar poate fi folosit doar \u00een re\u021bele bazate pe echipamente Cisco. Mai t\u00e2rziu voi explica \u00een detaliu de ce este at\u00e2t de bun acest protocol. P\u00e2n\u0103 atunci, observ c\u0103 EIGRP combin\u0103 tr\u0103s\u0103turi ale protocoalelor de rutare de tip vector \u0219i ale celor de tip stare de leg\u0103tur\u0103, reprezent\u00e2nd un protocol hibrid. <\/p>\n

\u00cen urm\u0103torul videoclip de lec\u021bie, ne vom apropia de routerele Cisco, iar eu v\u0103 voi spune c\u00e2teva lucruri despre sistemul de operare Cisco IOS, care este destinat at\u00e2t switch-urilor, c\u00e2t \u0219i routerelor. Sper c\u0103 \u00een lec\u021biile din zilele 19 sau 20 vom \u00eencepe studiul detaliat al protocoalelor de rutare, iar eu, folosind exemple de re\u021bele mici, v\u0103 voi ar\u0103ta cum s\u0103 configura\u021bi routerele Cisco.<\/p>\n

\r\n \"Reda\u021bi\r\n
<\/div>\r\n <\/div><\/center>
\nV\u0103 mul\u021bumim c\u0103 r\u0103m\u00e2ne\u021bi cu noi. V\u0103 plac articolele noastre? Dori\u021bi s\u0103 vede\u021bi mai multe materiale interesante? Sus\u021bine\u021bi-ne f\u0103c\u00e2nd o comand\u0103 sau recomand\u00e2ndu-ne prietenilor. 30% reducere pentru utilizatorii Habr pentru un server entry-level unic, creat special pentru tine:<\/b> Adev\u0103rul despre VPS (KVM) E5-2650 v4 (6 nuclee) 10GB DDR4 240GB SSD 1Gbps de la 20$ sau cum s\u0103 \u00eemp\u0103r\u021bim corect un server?<\/a><\/noindex> (sunt disponibile op\u021biuni cu RAID1 \u0219i RAID10, p\u00e2n\u0103 la 24 nuclee \u0219i p\u00e2n\u0103 la 40GB DDR4).<\/p>\n

Dell R730xd la jum\u0103tate de pre\u021b?<\/b> Numai la noi 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB de la 199 $<\/a><\/noindex> \u00een Olanda! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 de la 99 $!<\/b><\/b> Citi\u021bi despre Cum s\u0103 construi\u021bi o infrastructur\u0103 de clas\u0103 enterprise folosind servere Dell R730xd E5-2650 v4 la pre\u021buri foarte mici de 9000 \u20ac?<\/a><\/noindex>
\n
Sursa: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u044e \u0440\u043e\u0443\u0442\u0435\u0440\u043e\u0432. \u0415\u0441\u043b\u0438 \u0432\u044b \u043f\u0440\u043e\u0448\u043b\u0438 \u043c\u043e\u0439 \u0432\u0438\u0434\u0435\u043e\u043a\u0443\u0440\u0441 \u0441 \u043f\u0435\u0440\u0432\u043e\u0433\u043e \u043f\u043e 17-\u0439 \u0443\u0440\u043e\u043a, \u0442\u043e \u0443\u0436\u0435 \u0438\u0437\u0443\u0447\u0438\u043b\u0438 \u043e\u0441\u043d\u043e\u0432\u044b \u0441\u0432\u0438\u0442\u0447\u0435\u0439. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0438\u043c \u043a \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u043c\u0443 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0443 \u2013 \u0440\u043e\u0443\u0442\u0435\u0440\u0443. \u041a\u0430\u043a \u0432\u044b \u0437\u043d\u0430\u0435\u0442\u0435 \u0438\u0437 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0433\u043e \u0432\u0438\u0434\u0435\u0443\u0440\u043e\u043a\u0430, \u043e\u0434\u043d\u0430 \u0438\u0437 \u0442\u0435\u043c \u043a\u0443\u0440\u0441\u0430 CCNA \u0442\u0430\u043a \u0438 \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u2013 Cisco Switching & Routing. \u0412 \u044d\u0442\u043e\u0439 \u0441\u0435\u0440\u0438\u0438 \u043c\u044b \u043d\u0435 \u0441\u0442\u0430\u043d\u0435\u043c \u0438\u0437\u0443\u0447\u0430\u0442\u044c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27956,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37271","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Antrenament Cisco 200-125 CCNA v3.0. Ziua 18. Bazele rut\u0103rii | ProHoster","description":"Ast\u0103zi vom \u00eencepe studiul routerelor. Dac\u0103 a\u021bi parcurs cursul meu video de la lec\u021bia 1 p\u00e2n\u0103 la lec\u021bia 17, atunci deja a\u021bi \u00eenv\u0103\u021bat bazele switch-urilor. Acum trecem la urm\u0103torul dispozitiv \u2013 routerul.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0422\u0440\u0435\u043d\u0438\u043d\u0433 Cisco 200-125 CCNA v3.0. \u0414\u0435\u043d\u044c 18. \u041e\u0441\u043d\u043e\u0432\u044b \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u044e \u0440\u043e\u0443\u0442\u0435\u0440\u043e\u0432. \u0415\u0441\u043b\u0438 \u0432\u044b \u043f\u0440\u043e\u0448\u043b\u0438 \u043c\u043e\u0439 \u0432\u0438\u0434\u0435\u043e\u043a\u0443\u0440\u0441 \u0441 \u043f\u0435\u0440\u0432\u043e\u0433\u043e \u043f\u043e 17-\u0439 \u0443\u0440\u043e\u043a, \u0442\u043e \u0443\u0436\u0435 \u0438\u0437\u0443\u0447\u0438\u043b\u0438 \u043e\u0441\u043d\u043e\u0432\u044b \u0441\u0432\u0438\u0442\u0447\u0435\u0439. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0438\u043c \u043a \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u043c\u0443 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0443 \u2013 \u0440\u043e\u0443\u0442\u0435\u0440\u0443.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:16:41+00:00","article:modified_time":"2019-10-31T19:16:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37271","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 17:03:35","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:30:00","updated":"2026-01-23 17:03:35","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37271","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=37271"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37271\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/27956"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=37271"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=37271"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=37271"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}