{"id":37511,"date":"2019-10-31T22:18:02","date_gmt":"2019-10-31T19:18:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-marshrutizatsii\/"},"modified":"2019-10-31T22:18:02","modified_gmt":"2019-10-31T19:18:02","slug":"trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-marshrutizatsii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-marshrutizatsii","title":{"rendered":"Tr\u00e9ning Cisco 200-125 CCNA v3.0. D\u0148a 23. Rafinovan\u00e9 technol\u00f3gie smerovania","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dnes podrobnej\u0161ie presk\u00famame niektor\u00e9 aspekty smerovania. Predt\u00fdm, ako za\u010dneme, chcem zodpoveda\u0165 na ot\u00e1zku \u0161tudentov o mojich str\u00e1nkach na soci\u00e1lnych sie\u0165ach. Na\u013eavo som umiestnil odkazy na str\u00e1nky na\u0161ej spolo\u010dnosti, a napravo \u2013 na moje osobn\u00e9 str\u00e1nky. Upozor\u0148ujem, \u017ee na Facebooku neprid\u00e1vam do svojich priate\u013eov nikoho, koho osobne nepozn\u00e1m, tak\u017ee mi, pros\u00edm, neposielajte \u017eiadosti o priate\u013estvo. <\/p>\n

\"Tr\u00e9ning
\n
\nJednoducho sa m\u00f4\u017eete prihl\u00e1si\u0165 na moju str\u00e1nku na Facebooku a by\u0165 informovan\u00ed o v\u0161etk\u00fdch udalostiach. Odpoved\u00e1m na spr\u00e1vy vo svojom \u00fa\u010dte LinkedIn, tak\u017ee mi tam m\u00f4\u017eete p\u00edsa\u0165, a samozrejme, maxim\u00e1lne sa anga\u017eujem na Twitteri. Pod t\u00fdmto video kurzom s\u00fa odkazy na v\u0161etk\u00fdch 6 soci\u00e1lnych siet\u00ed, tak\u017ee ich m\u00f4\u017eete vyu\u017ei\u0165. <\/a><\/noindex><\/p>\n

Ako obvykle, dnes presk\u00famame tri t\u00e9my. Prv\u00e1 je vysvetlenie podstaty smerovania, kde v\u00e1m vysvetl\u00edm smerovacie tabu\u013eky, statick\u00e9 smerovanie a tak \u010falej. Potom sa pozrieme na medzi-switche smerovanie, teda ako prebieha smerovanie medzi dvoma switche. Na konci lekcie sa obozn\u00e1mime s konceptom Inter-VLAN smerovania, ke\u010f jeden switch komunikuje s viacer\u00fdmi VLAN a ak\u00fdm sp\u00f4sobom sa zabezpe\u010duje spojenie medzi t\u00fdmito sie\u0165ami. Toto je ve\u013emi zauj\u00edmav\u00e1 t\u00e9ma a mo\u017eno ju budete chcie\u0165 nieko\u013ekokr\u00e1t si pozrie\u0165 znova. Existuje e\u0161te jedna zauj\u00edmav\u00e1 t\u00e9ma, ktor\u00e1 sa naz\u00fdva Router-on-a-Stick, alebo 'smerova\u010d na pali\u010dke'. <\/p>\n

\u010co teda je smerovacia tabu\u013eka? Je to tabu\u013eka, na z\u00e1klade ktorej smerova\u010de prij\u00edmaj\u00fa rozhodnutia o smerovan\u00ed. Vid\u00edte, ako vyzer\u00e1 typick\u00e1 smerovacia tabu\u013eka smerova\u010dov Cisco. Ka\u017ed\u00fd po\u010d\u00edta\u010d so syst\u00e9mom Windows tie\u017e m\u00e1 smerovaciu tabu\u013eku, ale to je u\u017e in\u00e1 t\u00e9ma. <\/p>\n

P\u00edsmeno R na za\u010diatku riadku znamen\u00e1, \u017ee cesta do siete 192.168.30.0\/24 je zabezpe\u010den\u00e1 protokolom RIP, C znamen\u00e1, \u017ee sie\u0165 je priamo pripojen\u00e1 k rozhraniu smerova\u010da, S znamen\u00e1 statick\u00e9 smerovanie a bod za t\u00fdmto p\u00edsmenom nazna\u010duje, \u017ee t\u00e1to trasa je kandid\u00e1tom default, alebo kandid\u00e1tom pre vykon\u00e1vanie statick\u00e9ho smerovania. Existuje nieko\u013eko typov statick\u00fdch tr\u00e1s a dnes sa s nimi obozn\u00e1mime. <\/p>\n

\"Tr\u00e9ning
\n
\nZv\u00e1\u017eme pre pr\u00edklad prv\u00fa sie\u0165 192.168.30.0\/24. V riadku vid\u00edte dve \u010d\u00edsla v zlo\u017een\u00fdch z\u00e1tvork\u00e1ch, rozdelen\u00e9 lom\u00edtkom, o ktor\u00fdch sme u\u017e hovorili. Prv\u00e9 \u010d\u00edslo 120 \u2013 to je administrat\u00edvna vzdialenos\u0165, ktor\u00e1 charakterizuje mieru d\u00f4very k tejto trase. Predpokladajme, \u017ee v tabu\u013eke existuje \u010fal\u0161ia trasa k tejto sieti, ozna\u010den\u00e1 p\u00edsmenami C alebo S s men\u0161ou administrat\u00edvnou vzdialenos\u0165ou, napr\u00edklad 1, ako pri statickej smerovan\u00ed. V tejto tabu\u013eke nen\u00e1jdete dve rovnak\u00e9 siete, ak nepou\u017eijeme mechanizmus, ako je rozlo\u017eenie z\u00e1\u0165a\u017ee, ale predpokladajme, \u017ee m\u00e1me 2 z\u00e1znamy pre jednu a t\u00fa ist\u00fa sie\u0165. Tak\u017ee, ak uvid\u00edte men\u0161ie \u010d\u00edslo, to znamen\u00e1, \u017ee t\u00e1to trasa zasl\u00fa\u017ei v\u00e4\u010d\u0161iu d\u00f4veru, a naopak, \u010d\u00edm v\u00e4\u010d\u0161ia je hodnota administrat\u00edvnej vzdialenosti, t\u00fdm men\u0161ej d\u00f4very sa t\u00e1to trasa te\u0161\u00ed. \u010ealej je v riadku uveden\u00e9, cez ktor\u00fd rozhranie by sa mal posiela\u0165 traffic \u2013 v na\u0161om pr\u00edpade je to port 192.168.20.1 FastEthernet0\/1. Z \u010doho sa skladaj\u00fa komponenty smerovacej tabu\u013eky. <\/p>\n

Teraz sa porozpr\u00e1vajme o tom, ako router prij\u00edma rozhodnutia o smerovan\u00ed. Vy\u0161\u0161ie som spomenul kandid\u00e1ta pre predvolen\u00e9 smerovanie a teraz poviem, \u010do to znamen\u00e1. Predpokladajme, \u017ee do routera prich\u00e1dza traffic pre sie\u0165 30.1.1.1, z\u00e1znam o ktorej ch\u00fdba v smerovacej tabu\u013eke. V be\u017enom pr\u00edpade router jednoducho odmietne tento traffic, ale ak v tabu\u013eke existuje z\u00e1znam o kandid\u00e1tovi pre predvolen\u00e9 smerovanie, to znamen\u00e1, \u017ee v\u0161etko, o \u010dom router nevie, bude smerovan\u00e9 na kandid\u00e1ta pre predvolen\u00e9 smerovanie. V tomto pr\u00edpade z\u00e1znam uv\u00e1dza, \u017ee traffic prich\u00e1dzaj\u00faci pre nezn\u00e1mu sie\u0165 routera by mal by\u0165 odoslan\u00fd \u010falej cez port 192.168.10.1. Takto traffic pre sie\u0165 30.1.1.1 prejde smerovan\u00edm, ktor\u00e9 je kandid\u00e1tom pre predvolen\u00e9 smerovanie. <\/p>\n

Ke\u010f router prijme po\u017eiadavku na nadviazanie spojenia s nejakou IP adresou, najprv sa pozrie, \u010di sa t\u00e1to adresa nenach\u00e1dza v nejakom preddefinovanom route. Preto, ke\u010f z\u00edska traffic pre sie\u0165 30.1.1.1, najprv skontroluje, \u010di je jej adresa obsiahnut\u00e1 v konkr\u00e9tnej z\u00e1znamu routingovej tabu\u013eky. Ak router z\u00edska traffic pre 192.168.30.1, po pre\u0161tudovan\u00ed v\u0161etk\u00fdch z\u00e1znamov zist\u00ed, \u017ee t\u00e1to adresa patr\u00ed do rozsahu IP adries siete 192.168.30.0\/24, a potom po\u0161le traffic t\u00fdmto smerom. Ak nen\u00e1jde \u017eiadne konkr\u00e9tne z\u00e1znamy pre sie\u0165 30.1.1.1, router po\u0161le traffic ur\u010den\u00fd pre \u0148u pod\u013ea predvolen\u00e9ho kandid\u00e1tskeho route. Takto sa prij\u00edmaj\u00fa rozhodnutia: najprv sa prezeraj\u00fa z\u00e1znamy konkr\u00e9tnych routes a potom sa pou\u017eije predvolen\u00fd kandid\u00e1tsky route.
\nTeraz si pozrime r\u00f4zne typy statick\u00fdch routes. Prv\u00fd typ je default route, alebo predvolen\u00fd route. <\/p>\n

\"Tr\u00e9ning
\n
\nAko u\u017e bolo spomenut\u00e9, ak router prijme traffic, ktor\u00fd je ur\u010den\u00fd nezn\u00e1mej sieti, po\u0161le ho po predvolenom route. O tom, \u017ee je nastaven\u00fd predvolen\u00fd route, informuje z\u00e1znam Gateway of last resort is 192.168.10.1 to network 0.0.0.0, \u010do znamen\u00e1 \u201e\u0160tandardn\u00e1 br\u00e1na pre sie\u0165 0.0.0.0 m\u00e1 IP adresu 192.168.10.1\u201c. Tento route je uveden\u00fd v poslednom riadku routingovej tabu\u013eky, ozna\u010denej p\u00edsmenom S s bodkou. <\/p>\n

Tento parameter m\u00f4\u017eete nastavi\u0165 z glob\u00e1lneho konfigura\u010dn\u00e9ho re\u017eimu. Pre be\u017en\u00fd route pod\u013ea protokolu RIP je potrebn\u00e9 zada\u0165 pr\u00edkaz ip route, uvies\u0165 identifik\u00e1tor pr\u00edslu\u0161nej siete, v na\u0161om pr\u00edpade 192.168.30.0, a masku podsiete 255.255.255.0, a potom uvies\u0165 192.168.20.1 ako nasleduj\u00faci hop. Av\u0161ak pri nastavovan\u00ed predvolen\u00e9ho route nepotrebujete uv\u00e1dza\u0165 identifik\u00e1tor siete a masku, jednoducho zad\u00e1te ip route 0.0.0.0 0.0.0.0, \u010do znamen\u00e1, \u017ee miesto adresy masky podsiete op\u00e4\u0165 zad\u00e1vate \u0161tyri nuly, a na konci riadku uv\u00e1dzate adresu 192.168.20.1, ktor\u00e1 bude predstavova\u0165 predvolen\u00fd route.
\n\u010eal\u0161\u00ed typ statick\u00e9ho route je Network Route, alebo sie\u0165ov\u00fd route. Na nastavenie sie\u0165ov\u00e9ho route je potrebn\u00e9 uvies\u0165 cel\u00fa sie\u0165, teda pou\u017ei\u0165 pr\u00edkaz ip route 192.168.30.0 255.255.255.0, kde 0 na konci masky podsiete znamen\u00e1 cel\u00fd rozsah 256 adries siete \/24, a uvies\u0165 IP adresu nasleduj\u00faceho hopu.<\/p>\n

Teraz nakresl\u00edm \u0161abl\u00f3nu, ktor\u00e1 zn\u00e1zor\u0148uje pr\u00edkaz na nastavenie predvolen\u00e9ho smerovania a smerovacieho pravidla. Vyzer\u00e1 to takto:<\/p>\n

ip route prv\u00e1 \u010das\u0165 adresy druh\u00e1 \u010das\u0165 adresy . <\/p>\n

Pre predvolen\u00e9 smerovanie bud\u00fa prv\u00e1 a druh\u00e1 \u010das\u0165 adresy pozost\u00e1va\u0165 z 0.0.0.0, a pre smerovanie siete bude prv\u00e1 \u010das\u0165 predstavova\u0165 identifik\u00e1tor siete a druh\u00e1 - masku podsiete. \u010ealej bude uveden\u00e1 IP-adresa siete, do ktorej sa router rozhodol uskuto\u010dni\u0165 nasleduj\u00faci skok. <\/p>\n

\"Tr\u00e9ning
\n
\nNa nastavenie smeru hostite\u013ea (host route) sa pou\u017e\u00edva IP-adresa konkr\u00e9tneho hostite\u013ea. V \u0161abl\u00f3ne pr\u00edkazu to bude prv\u00e1 \u010das\u0165 adresy, v na\u0161om pr\u00edpade 192.168.30.1, ktor\u00e1 ozna\u010duje konkr\u00e9tne zariadenie. Druh\u00e1 \u010das\u0165 predstavuje masku podsiete 255.255.255.255, ktor\u00e1 tie\u017e ukazuje na IP-adresu konkr\u00e9tneho hostite\u013ea, nie celej siete \/24. Potom je potrebn\u00e9 ur\u010di\u0165 IP-adresu nasleduj\u00faceho skoku. Takto je mo\u017en\u00e9 nastavi\u0165 smer hostite\u013ea. <\/p>\n

S\u00fahrnn\u00e1 trasa (summary route) je agregovan\u00e1 trasa. Pam\u00e4t\u00e1te si, \u017ee sme u\u017e diskutovali o ot\u00e1zke zhr\u0148ovania tr\u00e1s, ke\u010f m\u00e1me ur\u010dit\u00fd rozsah IP-adres. Zoberme si prv\u00fa sie\u0165 192.168.30.0\/24 a predpokladajme, \u017ee m\u00e1me router R1, ku ktor\u00e9mu je pripojen\u00e1 sie\u0165 192.168.30.0\/24 so \u0161tyrmi IP adresami: 192.168.30.4, 192.168.30.5, 192.168.30.6 a 192.168.30.7. Lomka 24 znamen\u00e1, \u017ee v tejto sieti je celkovo 256 platn\u00fdch adries, av\u0161ak v tomto pr\u00edpade m\u00e1me iba 4 IP adresy. <\/p>\n

\"Tr\u00e9ning
\n
\nAk by som povedal, \u017ee v\u0161etok prenos pre sie\u0165 192.168.30.0\/24 by mal by\u0165 smerovan\u00fd cez t\u00fato trasu, bola by to lo\u017e, preto\u017ee tak\u00e1 IP adresa ako 192.168.30.1 nemus\u00ed by\u0165 dostupn\u00e1 cez toto rozhranie. Preto v tomto pr\u00edpade nem\u00f4\u017eeme pou\u017ei\u0165 ako prv\u00fa \u010das\u0165 adresy 192.168.30.0, ale mus\u00edme uvies\u0165, ktor\u00e9 konkr\u00e9tne adresy bud\u00fa dostupn\u00e9. V tomto pr\u00edpade 4 konkr\u00e9tne adresy bud\u00fa dostupn\u00e9 cez prav\u00e9 rozhranie a ostatn\u00e9 adresy siete cez \u013eav\u00e9 rozhranie routera. Preto potrebujeme nastavi\u0165 s\u00fahrnn\u00fa, alebo agregovan\u00fa trasu.<\/p>\n

Z princ\u00edpov sumariz\u00e1cie tr\u00e1s si pam\u00e4t\u00e1me, \u017ee v jednej podsieti prv\u00e9 tri oktety adresy zost\u00e1vaj\u00fa nezmenen\u00e9 a mus\u00edme vytvori\u0165 podsiet, ktor\u00e1 by sp\u00e1jala v\u0161etky 4 adresy. Na to mus\u00edme uvies\u0165 v prvej \u010dasti adresy 192.168.30.4 a v druhej \u010dasti pou\u017ei\u0165 masku podsiete 255.255.255.252, kde 252 znamen\u00e1, \u017ee v tejto podsieti je 4 IP adresy: .4, .5, .6 a .7.<\/p>\n

Ak bud\u00fa vo va\u0161ej routingovej tabu\u013eke pr\u00edtomn\u00e9 dve z\u00e1znamy: RIP route pre sie\u0165 192.168.30.0\/24 a sumarizovan\u00e1 trasa 192.168.30.4\/252, potom pod\u013ea princ\u00edpov routovania bude prioritn\u00fdm trasom pre konkr\u00e9tny traffic pr\u00e1ve sumarizovan\u00e1 trasa. V\u0161etko, \u010do nebude patri\u0165 k tomuto konkr\u00e9tnemu trafficu, za\u010dne pou\u017e\u00edva\u0165 sie\u0165ov\u00fa trasu. <\/p>\n

\"Tr\u00e9ning
\n
\nTu je, \u010do predstavuje sumarizovan\u00e1 trasa \u2013 zhrniete nieko\u013eko konkr\u00e9tnych IP adries a vytvor\u00edte pre nich samostatn\u00fa trasu. <\/p>\n

V skupine statick\u00fdch tr\u00e1s existuje aj takzvan\u00e1 \u201epl\u00e1vaj\u00faca trasa\u201c, alebo Floating Route. Je to rezervn\u00e1 trasa. Pou\u017e\u00edva sa v pr\u00edpade probl\u00e9mov s fyzick\u00fdm pripojen\u00edm cez statick\u00fa trasu, ktor\u00e1 m\u00e1 administrat\u00edvnu vzdialenos\u0165 rovnu 1. V na\u0161om pr\u00edklade je to trasa cez IP adresu 192.168.10.1 v poslednom riadku routingovej tabu\u013eky, a ke\u010f sa t\u00e1to trasa preru\u0161\u00ed na fyzickej \u00farovni, pou\u017e\u00edva sa rezervn\u00e1 pl\u00e1vaj\u00faca trasa. <\/p>\n

Aby ste aktivovali rezervn\u00fa trasu, na konci pr\u00edkazu namiesto IP adresy nasleduj\u00faceho skoku, ktor\u00e1 je zvy\u010dajne rovn\u00e1 1, uvediete in\u00fa hodnotu skokov, napr\u00edklad 5. Pl\u00e1vaj\u00faca trasa nie je uveden\u00e1 v routingovej tabu\u013eke, preto\u017ee sa aktivuje len v pr\u00edpade, ke\u010f je statick\u00e1 trasa nedostupn\u00e1 kv\u00f4li poruche. <\/p>\n

Ak ste nie\u010do nepochopili z toho, \u010do som pr\u00e1ve povedal, prezrite si toto video e\u0161te raz. Ak v\u00e1m aj tak zostan\u00fa ot\u00e1zky, m\u00f4\u017eete mi posla\u0165 e-mail a v\u0161etko v\u00e1m vysvetl\u00edm. <\/p>\n

A teraz sa pozrime na medzi-switchov\u00fa routingu. Na\u013eavo na sch\u00e9me je switch, ktor\u00fd spravuje modr\u00fa sie\u0165 oddelenia predaja. Napravo je \u010fal\u0161\u00ed switch, ktor\u00fd pracuje iba so zelenou sie\u0165ou oddelenia marketingu. V tomto pr\u00edpade sa pou\u017e\u00edvaj\u00fa dva nez\u00e1visl\u00e9 switche, ktor\u00e9 obsluhuj\u00fa r\u00f4zne oddelenia, preto\u017ee v tejto topol\u00f3gii nie je pou\u017eit\u00e1 spolo\u010dn\u00e1 sie\u0165 VLAN. <\/p>\n

\"Tr\u00e9ning
\n
\nAk potrebujete nadviaza\u0165 spojenie medzi t\u00fdmito dvoma switchmi, teda medzi dvoma r\u00f4znymi sie\u0165ami 192.168.1.0\/24 a 192.168.2.0\/24, je potrebn\u00e9 pou\u017ei\u0165 router. Potom bud\u00fa tieto siete schopn\u00e9 vymie\u0148a\u0165 si pakety a pripoji\u0165 sa na internet prostredn\u00edctvom routera R1. Keby sme pou\u017eili predvolen\u00e9 VLAN1 pre oba switche a prepojili ich fyzick\u00fdm k\u00e1blom, mohli by si navz\u00e1jom komunikova\u0165. Ale preto\u017ee to technicky nie je mo\u017en\u00e9 kv\u00f4li rozdeleniu siet\u00ed patriacich r\u00f4znym vysielac\u00edm dom\u00e9nam, na ich komunik\u00e1ciu je potrebn\u00fd router.<\/p>\n

Predpokladajme, \u017ee ka\u017ed\u00fd zo switchov m\u00e1 16 portov. V na\u0161om pr\u00edpade nepou\u017e\u00edvame 14 portov, preto\u017ee v ka\u017edom oddelen\u00ed s\u00fa iba 2 po\u010d\u00edta\u010de. Preto je v tomto pr\u00edpade optim\u00e1lne pou\u017e\u00edva\u0165 VLAN, ako je zn\u00e1zornen\u00e9 na nasleduj\u00facej sch\u00e9me. <\/p>\n

\"Tr\u00e9ning
\n
\nV tomto pr\u00edpade m\u00e1 modr\u00e1 sie\u0165 VLAN10 a zelen\u00e1 sie\u0165 VLAN20 svoju vlastn\u00fa vysielaciu dom\u00e9nu. Sie\u0165 VLAN10 je pripojen\u00e1 k\u00e1blom k jedn\u00e9mu portu routera a sie\u0165 VLAN20 k druh\u00e9mu portu, pri\u010dom oba k\u00e1ble vych\u00e1dzaj\u00fa z r\u00f4znych portov switche. Zd\u00e1 sa, \u017ee v\u010faka tomuto skvel\u00e9mu rie\u0161eniu sme nadviazali spojenie medzi sie\u0165ami. Av\u0161ak preto\u017ee m\u00e1 router obmedzen\u00fd po\u010det portov, ve\u013emi neefekt\u00edvne vyu\u017e\u00edvame mo\u017enosti tohto zariadenia tak\u00fdmto sp\u00f4sobom. <\/p>\n

Existuje efekt\u00edvnej\u0161ie rie\u0161enie \u2013 \u201erouter na palici\u201c. Pri tomto spoj\u00edme port switche s jedn\u00fdm z portov routera pomocou trunku. U\u017e sme spomenuli, \u017ee router predpoklad\u00e1, \u017ee nepozn\u00e1 enkapsul\u00e1ciu pod\u013ea \u0161tandardu .1Q, preto na jeho spojenie je potrebn\u00e9 pou\u017ei\u0165 trunk. Pri tomto sa deje nasleduj\u00face.<\/p>\n

Modr\u00e1 sie\u0165 VLAN10 posiela prev\u00e1dzku cez prep\u00edna\u010d do rozhrania F0\/0 smerova\u010da. Toto portov\u00e9 rozhranie je rozdelen\u00e9 na sub-intefce (podrozhrania), z ktor\u00fdch ka\u017ed\u00e9 m\u00e1 jednu IP adresu nach\u00e1dzaj\u00facu sa v rozsahu adries bu\u010f siete 192.168.1.0\/24, alebo siete 192.168.2.0\/24. Tu sa vyskytuje ur\u010dit\u00e1 nejasnos\u0165 \u2013 pre dve r\u00f4zne siete potrebujeme ma\u0165 dve r\u00f4zne IP adresy. Preto, aj ke\u010f trunk medzi prep\u00edna\u010dom a smerova\u010dom je vytvoren\u00fd na jednom fyzickom rozhran\u00ed, mus\u00edme vytvori\u0165 dve podrozhrania pre ka\u017ed\u00fa VLAN. Tak\u017ee jedno podrozhranie bude obsluhova\u0165 sie\u0165 VLAN10 a druh\u00e9 VLAN20. Pre prv\u00e9 podrozhranie potrebujeme zvoli\u0165 IP adresu z rozsahu adries 192.168.1.0\/24 a pre druh\u00e9 z rozsahu 192.168.2.0\/24. Ke\u010f VLAN10 za\u0161le paket, br\u00e1nou bude jedna IP adresa, a ke\u010f paket za\u0161le VLAN20, druh\u00e1 IP adresa sa pou\u017eije ako br\u00e1na. Pri tom \u201esmerova\u010d na pali\u010dke\u201c bude rozhodova\u0165 o prev\u00e1dzke od ka\u017ed\u00e9ho z dvoch po\u010d\u00edta\u010dov, ktor\u00e9 patria k r\u00f4znym VLAN. Jednoducho povedan\u00e9, del\u00edme jedno fyzick\u00e9 rozhranie smerova\u010da na dve alebo viac logick\u00fdch rozhran\u00ed. <\/p>\n

\"Tr\u00e9ning
\n
\nPozrime sa, ako to vyzer\u00e1 v programe Packet Tracer. <\/p>\n

\"Tr\u00e9ning
\n
\nTrochu som zjednodu\u0161il sch\u00e9mu, tak\u017ee m\u00e1me jeden po\u010d\u00edta\u010d PC0 s IP adresou 192.168.1.10 a druh\u00fd po\u010d\u00edta\u010d PC1 s adresou 192.168.2.10. Pri konfigur\u00e1cii prep\u00edna\u010da vy\u010dle\u0148ujem jedno rozhranie pre VLAN10 a druh\u00e9 pre VLAN20. Vst\u00fapim do konzoly CLI a zad\u00e1m pr\u00edkaz show ip interface brief, aby som sa uistil, \u017ee rozhrania FastEthernet0\/2 a 0\/3 s\u00fa zapnut\u00e9. Potom preh\u013ead\u00e1vam datab\u00e1zu VLAN a vid\u00edm, \u017ee v\u0161etky rozhrania prep\u00edna\u010da s\u00fa moment\u00e1lne s\u00fa\u010das\u0165ou predvolenej VLAN. Potom postupne zad\u00e1m pr\u00edkazy config t a int f0\/2, aby som aktivoval port, ku ktor\u00e9mu je pripojen\u00e1 VLAN oddelenia predaja. <\/p>\n

\u010ealej pou\u017eijem pr\u00edkaz switchport mode access. Re\u017eim access je predvolen\u00fd, preto len zad\u00e1m tento pr\u00edkaz. Potom zad\u00e1m switchport access VLAN10 a syst\u00e9m odpovie, \u017ee ke\u010f\u017ee tak\u00e1to sie\u0165 neexistuje, vytvor\u00ed VLAN10 s\u00e1m. Ak chcete vytvori\u0165 sie\u0165 VLAN manu\u00e1lne, napr\u00edklad VLAN20, mus\u00edte zada\u0165 pr\u00edkaz vlan 20, po \u010dom sa pr\u00edkazov\u00fd riadok prepn\u00fa na nastavenia virtu\u00e1lnej siete, meniac svoj n\u00e1zov z Switch(config) # na Switch(config-vlan) #. Potom je potrebn\u00e9 priradi\u0165 vytvorenej sieti n\u00e1zov MARKETING pomocou pr\u00edkazu name . N\u00e1sledne nastav\u00edme rozhranie f0\/3. Postupne zad\u00e1m pr\u00edkazy switchport mode access a switchport access vlan 20, po \u010dom je sie\u0165 pripojen\u00e1 k tomuto portu. <\/p>\n

Takto m\u00f4\u017eete nastavi\u0165 prep\u00edna\u010d dvoma sp\u00f4sobmi: prv\u00fd \u2013 pomocou pr\u00edkazu switchport access vlan 10, po \u010dom sa sie\u0165 automaticky vytvor\u00ed na tomto porte; druh\u00fd \u2013 ke\u010f najsk\u00f4r vytvor\u00edte sie\u0165 a potom ju prirad\u00edte k konkr\u00e9tnemu portu.
\nRovnako tak sa d\u00e1 postupova\u0165 aj s VLAN10. Vr\u00e1time sa sp\u00e4\u0165 a zopakujem proces ru\u010dn\u00e9ho nastavenia pre t\u00fato sie\u0165: prejdeme do glob\u00e1lneho konfigura\u010dn\u00e9ho re\u017eimu, zad\u00e1me pr\u00edkaz vlan 10, potom jej prirad\u00edm n\u00e1zov name SALES a tak \u010falej. Teraz v\u00e1m uk\u00e1\u017eem, \u010do sa stane, ak to neurob\u00edte, teda nech\u00e1te syst\u00e9m, aby sie\u0165 VLAN vytvoril s\u00e1m. <\/p>\n

\"Tr\u00e9ning
\n
\nVid\u00edte, \u017ee m\u00e1me obe siete, ale druh\u00e1, ktor\u00fa sme vytvorili manu\u00e1lne, m\u00e1 svoje vlastn\u00e9 meno MARKETING, zatia\u013e \u010do prv\u00e1 sie\u0165 VLAN10 dostala predvolen\u00e9 meno VLAN0010. M\u00f4\u017eem to opravi\u0165, ak teraz v glob\u00e1lnom konfigura\u010dnom re\u017eime zad\u00e1m pr\u00edkaz name SALES. Teraz vid\u00edte, \u017ee po tomto prv\u00e1 sie\u0165 zmenila svoje n\u00e1zov na SALES. <\/p>\n

Teraz sa vr\u00e1time do Packet Tracer a over\u00edme, \u010di m\u00f4\u017ee po\u010d\u00edta\u010d PC0 komunikova\u0165 s po\u010d\u00edta\u010dom PC1. Na to otvor\u00edm termin\u00e1l pr\u00edkazov\u00e9ho riadku prv\u00e9ho po\u010d\u00edta\u010da a po\u0161lem ping na adresu druh\u00e9ho po\u010d\u00edta\u010da. <\/p>\n

Vid\u00edme, \u017ee pingovanie zlyhalo. D\u00f4vodom je, \u017ee PC0 odoslalo ARP po\u017eiadavku na adresu 192.168.2.10 cez br\u00e1nu 192.168.1.1. Po\u010d\u00edta\u010d sa vlastne p\u00fdtal prep\u00edna\u010da, kto je tento 192.168.1.1. Prep\u00edna\u010d v\u0161ak m\u00e1 iba jeden port pre sie\u0165 VLAN10, a prijat\u00e1 po\u017eiadavka nem\u00f4\u017ee od\u00eds\u0165 nikam \u2013 skon\u010d\u00ed na tomto porte a tu uhynie. Po\u010d\u00edta\u010d nedostane odpove\u010f, a preto je d\u00f4vodom zlyhania pingu uveden\u00e9 prekro\u010denie \u010dasu. Odpove\u010f nebola prijat\u00e1, preto\u017ee v sieti VLAN10 nie je \u017eiadne in\u00e9 zariadenie okrem PC0. Navy\u0161e, aj keby boli oba po\u010d\u00edta\u010de s\u00fa\u010das\u0165ou tej istej siete, aj tak by sa nemohli spoji\u0165, preto\u017ee maj\u00fa odli\u0161n\u00fd rozsah IP adries. Aby sme t\u00fato sch\u00e9mu rozbehli, potrebujeme pou\u017ei\u0165 router. <\/p>\n

Predt\u00fdm, ako uk\u00e1\u017eem, ako zapoji\u0165 router, urob\u00edm mal\u00e9 odbo\u010denie. Spoj\u00edm port Fa0\/1 prep\u00edna\u010da a port routera Gig0\/0 jedn\u00fdm k\u00e1blom, a potom prid\u00e1m \u010fal\u0161\u00ed k\u00e1bel, ktor\u00fd bude pripojen\u00fd k portu Fa0\/4 prep\u00edna\u010da a portu Gif0\/1 routera. <\/p>\n

\"Tr\u00e9ning
\n
\nPrirad\u00edm sie\u0165 VLAN10 k portu f0\/1 prep\u00edna\u010da, na \u010do zad\u00e1m pr\u00edkazy int f0\/1 a switchport access vlan10, a sie\u0165 VLAN20 k portu f0\/4, pou\u017e\u00edvaj\u00fac pr\u00edkazy int f0\/4 a switchport access vlan 20. Ak sa teraz pozrieme na datab\u00e1zu VLAN, vid\u00edme, \u017ee sie\u0165 SALES je priraden\u00e1 k rozhraniam Fa0\/1, Fa0\/2, zatia\u013e \u010do sie\u0165 MARKETING je priraden\u00e1 k portom Fa0\/3, Fa0\/4. <\/p>\n

Vr\u00e1\u0165me sa op\u00e4\u0165 k routeru a vst\u00fapme do nastaven\u00ed rozhrania g0\/0, zadajme pr\u00edkaz no shutdown a prirad\u00edme mu IP adresu: ip add 192.168.1.1 255.255.255.0.<\/p>\n

Podobne nastav\u00edme rozhranie g0\/1, prirad\u00edme mu adresu ip add 192.168.2.1 255.255.255.0. N\u00e1sledne po\u017eiadame o zobrazenie na\u0161ej smerovacej tabu\u013eky, v ktorej s\u00fa teraz z\u00e1znamy o sie\u0165ach 1.0 a 2.0. <\/p>\n

\"Tr\u00e9ning
\n
\nPozrime sa, \u010di t\u00e1to sch\u00e9ma funguje. Po\u010dk\u00e1me, k\u00fdm sa oba porty prep\u00edna\u010da a routera nezafarbia na zeleno, a zopakujeme pingovanie IP adresy 192.168.2.10. Ako vid\u00edte, v\u0161etko funguje!<\/p>\n

\"Tr\u00e9ning
\n
\nPo\u010d\u00edta\u010d PC0 posiela po\u017eiadavku cez protokol ARP prep\u00edna\u010du, ktor\u00fd ju adresuje routeru, a ten posiela po\u010d\u00edta\u010du sp\u00e4\u0165 svoju MAC adresu. Potom po\u010d\u00edta\u010d odosiela pingov\u00fd paket rovnakou cestou. Router vie, \u017ee sie\u0165 VLAN20 je pripojen\u00e1 k jeho portu g0\/1, a preto ho posiela prep\u00edna\u010du, ktor\u00fd paket doru\u010duje adres\u00e1tovi \u2013 PC1. <\/p>\n

Toto sch\u00e9ma funguje, ale nie je efekt\u00edvne, preto\u017ee zaber\u00e1 2 rozhrania routera, teda neefekt\u00edvne vyu\u017e\u00edvame technick\u00e9 mo\u017enosti routera. Preto uk\u00e1\u017eem, ako to ist\u00e9 mo\u017eno dosiahnu\u0165 pomocou jedn\u00e9ho rozhrania. <\/p>\n

Odstr\u00e1nim sch\u00e9mu so zverejnen\u00fdmi dvoma k\u00e1blami a obnov\u00edm predch\u00e1dzaj\u00face spojenie switche a routera jedn\u00fdm k\u00e1blom. Rozhranie f0\/1 switche zostane trunk portom, preto sa vraciam do nastaven\u00ed switche a pre toto port pou\u017eijem pr\u00edkaz switchport mode trunk. Port f0\/4 u\u017e nepou\u017e\u00edvame. \u010ealej pou\u017eijeme pr\u00edkaz show int trunk, aby sme skontrolovali, \u010di je port spr\u00e1vne nastaven\u00fd. <\/p>\n

\"Tr\u00e9ning
\n
\nVid\u00edme, \u017ee port Fa0\/1 funguje v re\u017eime trunk pod\u013ea protokolu enkapsul\u00e1cie 802.1q. Pozrime sa na tabu\u013eku VLAN \u2013 vid\u00edme, \u017ee rozhranie F0\/2 je obsaden\u00e9 pod sie\u0165 oddelenia predaja VLAN10, zatia\u013e \u010do rozhranie f0\/3 je pod sie\u0165ou marketingu VLAN20. <\/p>\n

\"Tr\u00e9ning
\n
\nS\u00fa\u010dasne je switch pripojen\u00fd k portu g0\/0 routera. V nastaveniach routera pou\u017e\u00edvam pr\u00edkazy int g0\/0 a no ip address, aby som odstr\u00e1nil IP adresu tohto rozhrania. Ale toto rozhranie st\u00e1le funguje, nie je v stave shutdown. Ak si pam\u00e4t\u00e1te, router by mal prij\u00edma\u0165 prev\u00e1dzku z oboch siet\u00ed \u2013 1.0 a 2.0. Ke\u010f\u017ee je switch pripojen\u00fd k routeru trunkom, prev\u00e1dzka z oboch siet\u00ed sa dost\u00e1va k routeru. Ale ak\u00fa IP adresu by sme mali priradi\u0165 rozhraniu routera v tomto pr\u00edpade? <\/p>\n

G0\/0 predstavuje fyzick\u00e9 rozhranie, ktor\u00e9 pod\u013ea predvolieb nem\u00e1 \u017eiadnu IP adresu. Preto pou\u017e\u00edvame koncept logick\u00e9ho podrozhrania. Ke\u010f zad\u00e1m do riadku int g0\/0, syst\u00e9m vyd\u00e1 dve mo\u017en\u00e9 varianty pr\u00edkazu: lom\u00edtko \/ alebo bodku. Lom\u00edtko sa pou\u017e\u00edva pri modul\u00e1rnom nastaven\u00ed rozhran\u00ed typu 0\/0\/0, zatia\u013e \u010do bodka sa pou\u017e\u00edva, ak m\u00e1te podrozhranie.<\/p>\n

Ke\u010f zad\u00e1m do riadku int g0\/0. ?, syst\u00e9m mi poskytne rozsah mo\u017en\u00fdch \u010d\u00edsel logick\u00e9ho podrozhrania GigabitEthernet, ktor\u00e9 s\u00fa uveden\u00e9 za bodkou: . Tento rozsah obsahuje viac ako 4 miliardy \u010d\u00edsel, teda je mo\u017en\u00e9 vytvori\u0165 tak\u00e9 mno\u017estvo logick\u00fdch podrozhran\u00ed. <\/p>\n

\"Tr\u00e9ning
\n
\nUvediem \u010d\u00edslo 10 za bodkou, ktor\u00e9 bude ozna\u010dova\u0165 VLAN10. Teraz sme pre\u0161li do nastaven\u00ed podrozhrania, \u010do dokazuj\u00fa zmeny v hlavi\u010dke CLI nastaven\u00ed na Router (config-subif) #, v tomto pr\u00edpade sa to t\u00fdka podrozhrania g0\/0.10. Teraz mu mus\u00edm priradi\u0165 IP adresu, na \u010do pou\u017eijem pr\u00edkaz ip add 192.168.1.1 255.255.255.0. Predt\u00fdm, ako nastav\u00edm t\u00fato adresu, mus\u00ed sa vykona\u0165 enkapsul\u00e1cia, aby novo vytvoren\u00e9 podrozhranie vedelo, ak\u00fd protokol enkapsul\u00e1cie pou\u017ei\u0165 - 802.1q alebo ISL. Do riadku zad\u00e1m slovo encapsulation a syst\u00e9m zobraz\u00ed mo\u017en\u00e9 varianty parametrov pre tento pr\u00edkaz. <\/p>\n

\"Tr\u00e9ning
\n
\nPou\u017e\u00edvam pr\u00edkaz encapsulation dot1Q. Technicky nie je potrebn\u00e9 tento pr\u00edkaz zad\u00e1va\u0165, ale ja ho zad\u00e1vam, aby som smerova\u010du ozn\u00e1mil, ak\u00fd protokol je potrebn\u00e9 pou\u017ei\u0165 na pr\u00e1cu s VLAN, preto\u017ee v s\u00fa\u010dasnosti funguje ako prep\u00edna\u010d, ktor\u00fd obsluhuje trunking VLAN. T\u00fdmto pr\u00edkazom oznamujeme smerova\u010du, \u017ee cel\u00fd prenos by sa mal enkapsulova\u0165 pomocou protokolu dot1Q. \u010ealej v pr\u00edkazovom riadku mus\u00edm uvies\u0165, \u017ee t\u00e1to enkapsul\u00e1cia sa t\u00fdka siete VLAN10. Syst\u00e9m n\u00e1m ukazuje pou\u017e\u00edvan\u00fa IP adresu a rozhranie pre sie\u0165 VLAN10 za\u010d\u00edna fungova\u0165. <\/p>\n

\"Tr\u00e9ning
\n
\nPodobn\u00fdm sp\u00f4sobom nastavujem rozhranie g0\/0.20. Vytv\u00e1ram nov\u00e9 podrozhranie, nastavujem protokol enkapsul\u00e1cie a prira\u010fujem IP adresu pr\u00edkazom ip add 192.168.2.1 255.255.255.0.<\/p>\n

\"Tr\u00e9ning
\n
\nMus\u00edm nevyhnutne odstr\u00e1ni\u0165 IP adresu fyzick\u00e9ho rozhrania, preto\u017ee moment\u00e1lne maj\u00fa fyzick\u00e9 rozhranie a logick\u00e9 podrozhranie rovnak\u00fa adresu pre sie\u0165 VLAN20. Na to postupne zad\u00e1m pr\u00edkazy int g0\/1 a no ip address. Potom toto rozhranie vyp\u00ednam, preto\u017ee ho u\u017e nepotrebujeme. <\/p>\n

\"Tr\u00e9ning
\n
\nPotom sa op\u00e4\u0165 vraciam k rozhraniu g0\/0.20 a prira\u010fujem mu IP adresu pr\u00edkazom ip add 192.168.2.1 255.255.255.0. Teraz to ur\u010dite bude fungova\u0165. <\/p>\n

Teraz pou\u017e\u00edvam pr\u00edkaz show ip route, aby som si pozrel tabu\u013eku smerovania. <\/p>\n

\"Tr\u00e9ning
\n
\nVid\u00edme, \u017ee sie\u0165 192.168.1.0\/24 je priamo pripojen\u00e1 k podrozhraniu GigabitEthernet0\/0.10, zatia\u013e \u010do sie\u0165 192.168.2.0\/24 je priamo pripojen\u00e1 k podrozhraniu GigabitEthernet0\/0.20. Teraz sa vr\u00e1tim do pr\u00edkazov\u00e9ho riadka PC0 a pok\u00fasim sa pingn\u00fa\u0165 PC1. Pri tom prich\u00e1dza prev\u00e1dzka na port routera, ktor\u00fd ju presmeruje na pr\u00edslu\u0161n\u00e9 podrozhranie a odo\u0161le sp\u00e4\u0165 cez prep\u00edna\u010d k po\u010d\u00edta\u010du PC1. Ako vid\u00edte, ping bol \u00faspe\u0161n\u00fd. Dva prv\u00e9 pakety boli zahoden\u00e9, preto\u017ee prechod medzi rozhraniami routera trv\u00e1 ur\u010dit\u00fd \u010das, navy\u0161e zariadenia sa musia nau\u010di\u0165 MAC adresy, ale \u010fal\u0161ie dva pakety \u00faspe\u0161ne dosiahli cie\u013e. Takto funguje koncept \u201eroutera na pali\u010dke\u201c.<\/p>\n

\r\n \"Prehrajte\r\n
<\/div>\r\n <\/div><\/center>
\n\u010eakujeme, \u017ee s nami zost\u00e1vate. P\u00e1\u010dia sa v\u00e1m na\u0161e \u010dl\u00e1nky? Chcete vidie\u0165 viac zauj\u00edmav\u00fdch materi\u00e1lov? Podporte n\u00e1s objednan\u00edm alebo odpor\u00fa\u010dan\u00edm priate\u013eom, 30% z\u013eava pre pou\u017e\u00edvate\u013eov Chabra na unik\u00e1tny ekvivalent entry-level serverov, ktor\u00fd sme pre v\u00e1s vytvorili:<\/b> V\u0161etky pravdy o VPS (KVM) E5-2650 v4 (6 jadier) 10GB DDR4 240GB SSD 1Gbps od 20 dol\u00e1rov alebo ako spr\u00e1vne rozdeli\u0165 server?<\/a><\/noindex> (k dispoz\u00edcii varianty s RAID1 a RAID10, a\u017e 24 jadier a a\u017e 40GB DDR4).<\/p>\n

Dell R730xd za polovicu?<\/b> Len u n\u00e1s 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB od 199 dol\u00e1rov<\/a><\/noindex> v Holandsku! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 dol\u00e1rov!<\/b><\/b> Pre\u010d\u00edtajte si o tom Ako vybudova\u0165 infra\u0161trukt\u00faru korpor\u00e1tneho typu s pou\u017eit\u00edm serverov Dell R730xd E5-2650 v4 s cenou 9000 eur za zlomok ceny?<\/a><\/noindex>
\n
Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0431\u043e\u043b\u0435\u0435 \u043e\u0441\u043d\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0430\u0441\u043f\u0435\u043a\u0442\u044b \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438. \u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043d\u0430\u0447\u0430\u0442\u044c, \u044f \u0445\u043e\u0447\u0443 \u043e\u0442\u0432\u0435\u0442\u0438\u0442\u044c \u043d\u0430 \u0432\u043e\u043f\u0440\u043e\u0441 \u0441\u0442\u0443\u0434\u0435\u043d\u0442\u043e\u0432 \u043e \u043c\u043e\u0438\u0445 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0430\u0445 \u0432 \u0441\u043e\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0445 \u0441\u0435\u0442\u044f\u0445. \u0421\u043b\u0435\u0432\u0430 \u044f \u043f\u043e\u043c\u0435\u0441\u0442\u0438\u043b \u0441\u0441\u044b\u043b\u043a\u0438 \u043d\u0430 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0438 \u043d\u0430\u0448\u0435\u0439 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u0430 \u0441\u043f\u0440\u0430\u0432\u0430 \u2013 \u043d\u0430 \u043c\u043e\u0438 \u043f\u0435\u0440\u0441\u043e\u043d\u0430\u043b\u044c\u043d\u044b\u0435 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0438. \u0417\u0430\u043c\u0435\u0447\u0443, \u0447\u0442\u043e \u044f \u043d\u0435 \u0434\u043e\u0431\u0430\u0432\u043b\u044f\u044e \u0447\u0435\u043b\u043e\u0432\u0435\u043a\u0430 \u0432 \u0441\u0432\u043e\u0438 \u0434\u0440\u0443\u0437\u044c\u044f \u043d\u0430 Facebook, \u0435\u0441\u043b\u0438 \u043d\u0435 \u0437\u043d\u0430\u044e \u0435\u0433\u043e \u043b\u0438\u0447\u043d\u043e, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28149,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37511","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\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\udd47Cisco \u0161kolenie 200-125 CCNA v3.0. De\u0148 23. Pokro\u010dil\u00e9 technol\u00f3gie smerovania | ProHoster","description":"Dnes sa bli\u017e\u0161ie pozrieme na niektor\u00e9 aspekty smerovania. Predt\u00fdm, ne\u017e za\u010dneme, chcem odpoveda\u0165 na ot\u00e1zku \u0161tudentov t\u00fdkaj\u00facu sa mojich str\u00e1nok na soci\u00e1lnych sie\u0165ach.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-marshrutizatsii","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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 23. \u041f\u0435\u0440\u0435\u0434\u043e\u0432\u044b\u0435 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0438 \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 \u0431\u043e\u043b\u0435\u0435 \u043e\u0441\u043d\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0430\u0441\u043f\u0435\u043a\u0442\u044b \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438. \u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043d\u0430\u0447\u0430\u0442\u044c, \u044f \u0445\u043e\u0447\u0443 \u043e\u0442\u0432\u0435\u0442\u0438\u0442\u044c \u043d\u0430 \u0432\u043e\u043f\u0440\u043e\u0441 \u0441\u0442\u0443\u0434\u0435\u043d\u0442\u043e\u0432 \u043e \u043c\u043e\u0438\u0445 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0430\u0445 \u0432 \u0441\u043e\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0445 \u0441\u0435\u0442\u044f\u0445.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-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:18:02+00:00","article:modified_time":"2019-10-31T19:18:02+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37511","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 18:09:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:25:27","updated":"2026-01-23 18:09:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/37511","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=37511"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/37511\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/28149"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=37511"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=37511"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=37511"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}