{"id":37049,"date":"2019-10-31T22:15:29","date_gmt":"2019-10-31T19:15:29","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-13-nastrojka-vlan\/"},"modified":"2019-10-31T22:15:29","modified_gmt":"2019-10-31T19:15:29","slug":"trening-cisco-200-125-ccna-v3-0-den-13-nastrojka-vlan","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-13-nastrojka-vlan","title":{"rendered":"Tr\u00e9ning Cisco 200-125 CCNA v3.0. De\u0148 13. Nastavenie VLAN","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dne\u0161n\u00e1 lekcia bude venovan\u00e1 nastaveniam VLAN, teda sa pok\u00fasime uskuto\u010dni\u0165 v\u0161etko, o \u010dom sme hovorili v predch\u00e1dzaj\u00facich lekci\u00e1ch. Teraz sa budeme zaobera\u0165 3 ot\u00e1zkami: vytv\u00e1ranie VLAN, prira\u010fovanie portov VLAN a preh\u013ead datab\u00e1zy VLAN.<\/p>\n

Otvor\u00edme okno programu Cisco Packet Tracer s logickou topol\u00f3giou na\u0161ej siete, ktor\u00fa som nakreslil. <\/p>\n

\"Tr\u00e9ning
\n
\nK prv\u00e9mu swit\u010du SW0 s\u00fa pripojen\u00e9 2 po\u010d\u00edta\u010de PC0 a PC1, ktor\u00e9 s\u00fa zjednoten\u00e9 do siete VLAN10 s rozsahom IP adries 192.168.10.0\/24. Prisl\u00fachaj\u00face IP adresy t\u00fdchto po\u010d\u00edta\u010dov bud\u00fa 192.168.10.1 a 192.168.10.2. \u013dudia zvy\u010dajne identifikuj\u00fa \u010d\u00edslo VLAN pod\u013ea tretieho oktetu IP adresy, v na\u0161om pr\u00edpade je to 10, av\u0161ak toto nie je povinn\u00e9 ozna\u010denie siet\u00ed, m\u00f4\u017eete priradi\u0165 ak\u00fdko\u013evek identifik\u00e1tor VLAN, no tento poriadok je prijat\u00fd vo ve\u013ek\u00fdch spolo\u010dnostiach, preto\u017ee u\u013eah\u010duje konfigur\u00e1ciu siete. <\/p>\n

\u010falej je umiestnen\u00fd swit\u010d SW1, ktor\u00fd je pripojen\u00fd k sieti VLAN20 s IP adresou 192.168.20.0\/24 a dvoma laptopmi Laptop1 a Laptop2.<\/a><\/noindex><\/p>\n

VLAN10 sa nach\u00e1dza na 1. poschod\u00ed kancel\u00e1rie spolo\u010dnosti a predstavuje sie\u0165 vedenia oddelenia predaja. Tento ist\u00fd swit\u010d SW0 m\u00e1 pripojen\u00fd laptop Laptop0 marketingov\u00e9ho pracovn\u00edka, ktor\u00fd patr\u00ed do VLAN20. T\u00e1to sie\u0165 sa roz\u0161iruje na 2. poschodie, kde s\u00fa umiestnen\u00ed \u010fal\u0161\u00ed zamestnanci, a je spojen\u00ed s oddelen\u00edm predaja, ktor\u00e9 m\u00f4\u017ee by\u0165 umiestnen\u00e9 v inej budove alebo na 3. poschod\u00ed tej istej kancel\u00e1rie. Tu s\u00fa in\u0161talovan\u00e9 \u010fal\u0161ie 3 po\u010d\u00edta\u010de \u2013 PC2, PC3 a PC4, ktor\u00e9 s\u00fa s\u00fa\u010das\u0165ou siete VLAN10.<\/p>\n

Sie\u0165 VLAN10, rovnako ako VLAN20, mus\u00ed zabezpe\u010di\u0165 nepretr\u017eit\u00fa komunik\u00e1ciu v\u0161etk\u00fdch zamestnancov bez oh\u013eadu na to, \u017ee sa nach\u00e1dzaj\u00fa na r\u00f4znych poschodiach alebo v r\u00f4znych budov\u00e1ch. Tak\u00fato koncepciu siete dnes preberieme. <\/p>\n

Po\u010fme za\u010da\u0165 s jej nastaven\u00edm a za\u010dnime s po\u010d\u00edta\u010dom PC0. Kliknut\u00edm na ikonu sa dostaneme do sie\u0165ov\u00fdch nastaven\u00ed po\u010d\u00edta\u010da a zad\u00e1me IP adresu 192.168.10.1 a masku siete 255.255.255.0. Nezad\u00e1vam adresu predvolen\u00e9ho br\u00e1ny, preto\u017ee t\u00e1 je potrebn\u00e1 na pr\u00edstup z jednej lok\u00e1lnej siete do druhej, a v na\u0161om pr\u00edpade sa nebudeme zaobera\u0165 nastaveniami 3. \u00farovne OSI, zauj\u00edma n\u00e1s len 2. \u00farove\u0148 a nepl\u00e1nujeme sa zaobera\u0165 smerovan\u00edm prev\u00e1dzky do inej siete. <\/p>\n

\"Tr\u00e9ning
\n
\nPripravujeme sa na nastavenie intranetu a iba t\u00fdch hostite\u013eov, ktor\u00ed do neho patr\u00ed. Potom prejdeme na po\u010d\u00edta\u010d PC2 a vykon\u00e1me to ist\u00e9, \u010do pre prv\u00fd po\u010d\u00edta\u010d. Teraz skontrolujeme, \u010di dok\u00e1\u017eem pingn\u00fa\u0165 PC1 z po\u010d\u00edta\u010da PC0. Ako vid\u00edte, ping prech\u00e1dza a po\u010d\u00edta\u010d s IP adresou 192.168.10.2 spo\u013eahlivo vracia pakety. Takto sme \u00faspe\u0161ne ustanovili spojenie medzi PC0 a PC1 cez switch. <\/p>\n

Aby sme pochopili, pre\u010do sa n\u00e1m to podarilo, pozrime sa do nastaven\u00ed switche a skontrolujme tabu\u013eku VLAN.<\/p>\n

\"Tr\u00e9ning
\n
\nTechnicky m\u00e1 tento switch 5 VLAN: VLAN1 predvolene, a tie\u017e 1002, 1003, 1004 a 1005. Ak sa pozriete na posledn\u00e9 \u0161tyri siete, m\u00f4\u017eete vidie\u0165, \u017ee nie s\u00fa podporovan\u00e9 a s\u00fa ozna\u010den\u00e9 ako unsupported. Toto s\u00fa virtu\u00e1lne siete star\u0161ej technol\u00f3gie \u2013 fddi, fddinet, trnet. V s\u00fa\u010dasnosti sa nepou\u017e\u00edvaj\u00fa, ale pod\u013ea technick\u00fdch po\u017eiadaviek s\u00fa st\u00e1le zapracovan\u00e9 do nov\u00fdch zariaden\u00ed. Tak\u017ee n\u00e1\u0161 switch m\u00e1 v skuto\u010dnosti predvolene iba jednu virtu\u00e1lnu sie\u0165 \u2013 VLAN1, a preto s\u00fa v\u0161etky porty ktor\u00e9hoko\u013evek switche Cisco \u201ez krabice\u201c nastaven\u00e9 na t\u00fato sie\u0165. To je 24 portov Fast Ethernet a 2 porty Gigabit Ethernet. To v\u00fdrazne zjednodu\u0161uje kompatibilitu nov\u00fdch switche, preto\u017ee predvolene s\u00fa v\u0161etky s\u00fa\u010das\u0165ou tej istej VLAN1.<\/p>\n

Mus\u00edme preassignova\u0165 porty, ktor\u00e9 s\u00fa predvolene nastaven\u00e9 na pr\u00e1cu s VLAN1, aby pracovali s VLAN10. Packet Tracer ukazuje, \u017ee v na\u0161om pr\u00edpade s\u00fa to porty Fa0 a Fa0\/2. <\/p>\n

\"Tr\u00e9ning
\n
\nVr\u00e1time sa k switchu SW0 a nastav\u00edme tieto dva porty. Na to pou\u017e\u00edvam pr\u00edkaz configure terminal, aby som pre\u0161iel do re\u017eimu glob\u00e1lnej konfigur\u00e1cie, a zad\u00e1m pr\u00edkaz na nastavenie tohto rozhrania \u2013 int fastEthernet 0\/1. Mus\u00edm nastavi\u0165 pre tento port re\u017eim pr\u00edstupu, preto\u017ee je to access-port, a pou\u017e\u00edvam pr\u00edkaz switchport mode access. <\/p>\n

\"Tr\u00e9ning
\n
\nTento port sa konfiguruje ako statick\u00fd access-port, ale ak k nemu pripoj\u00edm in\u00fd switch, v\u010faka pou\u017eitiu protokolu DTP prejde do dynamick\u00e9ho re\u017eimu trunk. Predvolene patr\u00ed tento port VLAN1, preto mus\u00edm pou\u017ei\u0165 pr\u00edkaz switchport access vlan 10. Syst\u00e9m n\u00e1m pritom zobraz\u00ed spr\u00e1vu, \u017ee VLAN10 neexistuje a \u017ee ju mus\u00edme vytvori\u0165. Ak si pam\u00e4t\u00e1te, v datab\u00e1ze VLAN m\u00e1me iba jednu sie\u0165 \u2013 VLAN1, a \u017eiadnu sie\u0165 VLAN10 tam nie je. Ale po\u017eiadali sme switch, aby poskytol pr\u00edstup k VLAN10, a preto sme dostali chybov\u00e9 hl\u00e1senie.<\/p>\n

Preto je potrebn\u00e9 vytvori\u0165 VLAN10 a priradi\u0165 jej tento access-port. Potom, ak sa pozriete do datab\u00e1zy VLAN, uvid\u00edte pr\u00e1ve vytvoren\u00fa VLAN0010, ktor\u00e1 je v akt\u00edvnom stave a jej s\u00fa\u010das\u0165ou je port Fa0\/1. <\/p>\n

\"Tr\u00e9ning
\n
\nNeuskuto\u010dnili sme \u017eiadne zmeny na po\u010d\u00edta\u010di, len sme nastavili port switche, ku ktor\u00e9mu je pripojen\u00fd. Teraz sa pok\u00fasime o ping na IP adresu 192.168.10.2, \u010do sa n\u00e1m pred p\u00e1r min\u00fatami podarilo. Ni\u010d sa n\u00e1m nepodarilo, preto\u017ee port, ku ktor\u00e9mu je pripojen\u00fd PC0, teraz patr\u00ed do siete VLAN10, zatia\u013e \u010do port pripojen\u00fd k po\u010d\u00edta\u010du PC1 st\u00e1le patr\u00ed do VLAN1, a medzi t\u00fdmito dvoma sie\u0165ami neexistuje \u017eiadna komunik\u00e1cia. Aby sme zabezpe\u010dili spojenie medzi t\u00fdmito po\u010d\u00edta\u010dmi, je potrebn\u00e9 nastavi\u0165 oba porty na pr\u00e1cu s VLAN10. Op\u00e4\u0165 sa dost\u00e1vam do glob\u00e1lneho konfigura\u010dn\u00e9ho re\u017eimu a vykon\u00e1vam podobn\u00e9 kroky pre switchport f0\/2.<\/p>\n

\"Tr\u00e9ning
\n
\nPozrime sa znova na tabu\u013eku VLAN. Teraz vid\u00edme, \u017ee sie\u0165 VLAN10 je nastaven\u00e1 na portoch Fa0\/1 a Fa0\/2. Ako vid\u00edme, ping teraz prech\u00e1dza \u00faspe\u0161ne, preto\u017ee oba porty switche SW0, ku ktor\u00fdm s\u00fa pripojen\u00e9 zariadenia, patria do tej istej siete. Sk\u00fasme zmeni\u0165 n\u00e1zov siete, aby sme ozna\u010dili jej \u00fa\u010del. Ak chceme vykona\u0165 nejak\u00e9 zmeny v VLAN, mus\u00edme sa dosta\u0165 do nastaven\u00ed tejto siete. <\/p>\n

Na to zad\u00e1vam pr\u00edkaz vlan 10 a vid\u00edte, \u017ee v\u00fdzva pr\u00edkazov\u00e9ho riadku sa zmenila z Switch (config) # na Switch (config-vlan) #. Ak zad\u00e1m ot\u00e1znik, syst\u00e9m n\u00e1m zobraz\u00ed iba 3 mo\u017en\u00e9 pr\u00edkazy: exit, name a no. M\u00f4\u017eem priradi\u0165 n\u00e1zov siete pomocou pr\u00edkazu name, vr\u00e1ti\u0165 pr\u00edkazy do predch\u00e1dzaj\u00faceho stavu pomocou no, alebo ulo\u017ei\u0165 vykonan\u00e9 zmeny pr\u00edkazom exit. Preto zad\u00e1vam pr\u00edkazy name SALES a exit.<\/p>\n

\"Tr\u00e9ning
\n
\nAk sa pozrieme na datab\u00e1zu VLAN, m\u00f4\u017eeme sa presved\u010di\u0165, \u017ee na\u0161e \u00falohy boli vykonan\u00e9 a b\u00fdval\u00e1 VLAN10 teraz nesie n\u00e1zov SALES \u2013 oddelenie predaja. Tak\u017ee sme pripojili 2 po\u010d\u00edta\u010de na\u0161ej kancel\u00e1rie k vytvorenej sieti oddelenia predaja. Teraz je potrebn\u00e9 vytvori\u0165 sie\u0165 pre oddelenie marketingu. Aby sme pripojili k tejto sieti notebook Laptop0, mus\u00edme vst\u00fapi\u0165 do jeho sie\u0165ov\u00fdch nastaven\u00ed a zada\u0165 IP adresu 192.168.20.1 a masku podsiete 255.255.255.0, predvolen\u00e1 br\u00e1na n\u00e1m nie je potrebn\u00e1. Potom sa mus\u00edme vr\u00e1ti\u0165 k nastaveniam prep\u00edna\u010da, vst\u00fapi\u0165 do nastaven\u00ed portu pr\u00edkazom int fa0\/3 a zada\u0165 pr\u00edkaz switchport mode access. Nasleduj\u00faci pr\u00edkaz bude switchport access vlan 20. <\/p>\n

Znova dost\u00e1vame spr\u00e1vu, \u017ee tak\u00fd VLAN neexistuje a je potrebn\u00e9 ho vytvori\u0165. M\u00f4\u017eeme \u00eds\u0165 inou cestou \u2013 v\u00fdjdem z nastavenia portu Switch (config-if), vst\u00fapim do Switch (config) a zad\u00e1m pr\u00edkaz vlan 20, \u010d\u00edm vytvor\u00edm sie\u0165 VLAN20. To znamen\u00e1, \u017ee najsk\u00f4r m\u00f4\u017eeme vytvori\u0165 sie\u0165 VLAN20, priradi\u0165 jej meno MARKETING, ulo\u017ei\u0165 zmeny pr\u00edkazom exit, a potom nastavova\u0165 port pre \u0148u. <\/p>\n

Ak vst\u00fapime do datab\u00e1zy VLAN pr\u00edkazom sh vlan, m\u00f4\u017eeme vidie\u0165 vytvoren\u00fa na\u0161u sie\u0165 MARKETING a zodpovedaj\u00faci port Fa0\/3. Nem\u00f4\u017eem pingi\u0165 po\u010d\u00edta\u010de z tohto notebooku z dvoch d\u00f4vodov: m\u00e1me r\u00f4zne VLAN a na\u0161e zariadenia patria do r\u00f4znych podsiet\u00ed. Ke\u010f\u017ee patria do r\u00f4znych VLAN, prep\u00edna\u010d bude zahadzova\u0165 pakety notebooku smeruj\u00face do inej siete, preto\u017ee nem\u00e1 port, ktor\u00fd patr\u00ed VLAN20. <\/p>\n

Ako som u\u017e spom\u00ednal, spolo\u010dnos\u0165 sa roz\u0161iruje, mal\u00e1 kancel\u00e1ria na prvom poschod\u00ed nesta\u010d\u00ed, preto umiest\u0148uje oddelenie marketingu na 2. poschodie budovy, in\u0161taluje tam po\u010d\u00edta\u010de pre 2 zamestnancov a chce zabezpe\u010di\u0165 spojenie s oddelen\u00edm marketingu na prvom poschod\u00ed. Na to je potrebn\u00e9 najprv vytvori\u0165 trunk medzi dvoma prep\u00edna\u010dmi \u2013 portom Fa0\/4 prv\u00e9ho prep\u00edna\u010da a portom Fa0\/1 druh\u00e9ho prep\u00edna\u010da. Preto vst\u00fapim do nastaven\u00ed SW0 a zad\u00e1m pr\u00edkazy int f0\/4 a switchport mode trunk. <\/p>\n

Existuje pr\u00edkaz na enkapsul\u00e1ciu switchport trunk enc, av\u0161ak v nov\u00fdch prep\u00edna\u010doch sa nepou\u017e\u00edva, preto\u017ee predvolene pou\u017e\u00edvaj\u00fa technol\u00f3giu enkapsul\u00e1cie pod\u013ea protokolu 802.1q. Av\u0161ak star\u0161ie modely prep\u00edna\u010dov Cisco pou\u017e\u00edvali propriet\u00e1rny protokol ISL, ktor\u00fd sa u\u017e nepou\u017e\u00edva, preto\u017ee teraz v\u0161etky prep\u00edna\u010de rozumej\u00fa protokolu .1Q. T\u00fdm p\u00e1dom u\u017e nem\u00e1te potrebu pou\u017e\u00edva\u0165 pr\u00edkaz switchport trunk enc.<\/p>\n

Ak sa teraz pozriete do datab\u00e1zy VLAN, m\u00f4\u017eete vidie\u0165, \u017ee port Fa0\/4 zmizol. Je to preto, \u017ee v tejto tabu\u013eke s\u00fa uveden\u00e9 iba access porty, ktor\u00e9 sa t\u00fdkaj\u00fa konkr\u00e9tnej VLAN. Aby ste videli trunk porty switche, je potrebn\u00e9 pou\u017ei\u0165 pr\u00edkaz sh int trunk. <\/p>\n

\"Tr\u00e9ning
\n
\nVo vzorke pr\u00edkazov\u00e9ho riadku vid\u00edme, \u017ee port Fa0\/4 je zapnut\u00fd, vykon\u00e1va inkapsul\u00e1ciu pod\u013ea protokolu 802.1q a patr\u00ed do native VLAN 1. Ako vieme, ak tento trunk port prijme netegovan\u00fd prenos, automaticky ho nasmeruje do siete native VLAN 1. Na nasleduj\u00facej lekcii sa budeme zaobera\u0165 nastaven\u00edm native VLAN, zatia\u013e si len zapam\u00e4tajte, ako vyzeraj\u00fa nastavenia trunku pre toto zariadenie.<\/p>\n

Teraz prech\u00e1dzam na druh\u00fd switch SW1, prech\u00e1dzam do re\u017eimu nastaven\u00ed int f0\/1 a opakujem postup konfigur\u00e1cie portu podobne ako v predch\u00e1dzaj\u00facom pr\u00edpade. Dva porty Fa0\/2 a Fa0\/3, ku ktor\u00fdm s\u00fa pripojen\u00e9 notebooky zamestnancov marketingov\u00e9ho oddelenia, je potrebn\u00e9 nastavi\u0165 do re\u017eimu access a priradi\u0165 ich k sieti VLAN20. <\/p>\n

V predch\u00e1dzaj\u00facom pr\u00edpade sme individu\u00e1lne nastavovali ka\u017ed\u00fd port switche, ale teraz chcem uk\u00e1za\u0165, ako ur\u00fdchli\u0165 tento proces pomocou \u0161abl\u00f3ny pr\u00edkazov\u00e9ho riadku. M\u00f4\u017eete zada\u0165 pr\u00edkaz na nastavenie rozsahu rozhran\u00ed int range f0\/2-3, \u010d\u00edm sa pr\u00edkazov\u00fd riadok zmen\u00ed na Switch (config-if-range)#, a m\u00f4\u017eete zada\u0165 rovnak\u00fd parameter alebo aplikova\u0165 ten ist\u00fd pr\u00edkaz na ur\u010den\u00fd rozsah portov, napr\u00edklad s\u00fa\u010dasne pre 20 portov. <\/p>\n

V predch\u00e1dzaj\u00facom pr\u00edklade sme nieko\u013ekokr\u00e1t pou\u017eili rovnak\u00e9 pr\u00edkazy switchport mode access a switchport access vlan 10 pre nieko\u013eko portov switche. Tieto pr\u00edkazy je mo\u017en\u00e9 zada\u0165 jednorazovo, ak pou\u017eijete rozsah portov. Teraz zad\u00e1m pr\u00edkazy switchport mode access a switchport access vlan 20 pre vybran\u00fd rozsah portov. <\/p>\n

\"Tr\u00e9ning
\n
\nKe\u010f\u017ee sie\u0165 VLAN20 zatia\u013e neexistuje, syst\u00e9m ju automaticky vytvor\u00ed. Zadajem exit na ulo\u017eenie vykonan\u00fdch zmien a po\u017eiadam o zobrazenie tabu\u013eky VLAN. Ako vid\u00edte, porty Fa0\/2 a Fa0\/3 s\u00fa teraz s\u00fa\u010das\u0165ou pr\u00e1ve vytvorenej VLAN20. <\/p>\n

Teraz nastav\u00edm IP adresy prenosn\u00fdch po\u010d\u00edta\u010dov na druhom poschod\u00ed na\u0161ej kancel\u00e1rie: Laptop1 dostane adresu 192.168.20.2 a masku podsiete 255.255.255.0, zatia\u013e \u010do Laptop2 dostane IP adresu 192.168.20.3. Skontrolujeme funk\u010dnos\u0165 siete t\u00fdm, \u017ee pingneme prv\u00fd prenosn\u00fd po\u010d\u00edta\u010d zo druh\u00e9ho. Ako vid\u00edte, ping pre\u0161iel \u00faspe\u0161ne, preto\u017ee oba zariadenia s\u00fa s\u00fa\u010das\u0165ou jednej VLAN a pripojen\u00e9 k rovnak\u00e9mu prep\u00edna\u010du. <\/p>\n

\"Tr\u00e9ning
\n
\nAv\u0161ak prenosn\u00e9 po\u010d\u00edta\u010de oddelenia marketingu na prvom a druhom poschod\u00ed s\u00fa pripojen\u00e9 k r\u00f4znym prep\u00edna\u010dom, hoci sa nach\u00e1dzaj\u00fa v jednej sieti VLAN. Skontrolujeme, ako je zabezpe\u010den\u00e1 komunik\u00e1cia medzi nimi, a preto pingnem z Laptop2 prenosn\u00fd po\u010d\u00edta\u010d na prvom poschod\u00ed, ktor\u00fd m\u00e1 IP adresu 192.168.20.1. Ako vid\u00edte, v\u0161etko funguje bez probl\u00e9mov, napriek tomu, \u017ee prenosn\u00e9 po\u010d\u00edta\u010de s\u00fa pripojen\u00e9 k r\u00f4znym prep\u00edna\u010dom. Komunik\u00e1cia sa zabezpe\u010duje v\u010faka tomu, \u017ee oba prep\u00edna\u010de s\u00fa prepojen\u00e9 trunkom. <\/p>\n

M\u00f4\u017eem nadviaza\u0165 spojenie medzi Laptop2 a po\u010d\u00edta\u010dom PC0? Nie, nem\u00f4\u017eem, preto\u017ee patria do r\u00f4znych VLAN. Teraz nastav\u00edme sie\u0165 pre po\u010d\u00edta\u010de PC2,3,4, pri\u010dom najprv vytvor\u00edme trunk medzi druh\u00fdm prep\u00edna\u010dom Fa0\/4 a tret\u00edm prep\u00edna\u010dom Fa0\/1. <\/p>\n

Vstupujem do nastaven\u00ed SW1 a p\u00ed\u0161em pr\u00edkaz config t, potom vyvol\u00e1m int f0\/4, n\u00e1sledne zad\u00e1m pr\u00edkazy switchport mode trunk a exit. Podobne nastavujem aj tret\u00ed prep\u00edna\u010d SW2. Vytvorili sme trunk a vid\u00edte, \u017ee po tom, \u010do sa nastavenia uplatnili, farba portov sa zmenila z oran\u017eovej na zelen\u00fa. Teraz je potrebn\u00e9 nastavi\u0165 porty Fa0\/2,0\/3,0\/4, ku ktor\u00fdm s\u00fa pripojen\u00e9 po\u010d\u00edta\u010de oddelenia predaja, patriacej do siete VLAN10. Na to vst\u00fapim do nastaven\u00ed prep\u00edna\u010da SW2, vyberiem rozsah portov f0\/2-4 a aplikujem na ne pr\u00edkazy switchport mode access a switchport access vlan 10. Ke\u010f\u017ee na t\u00fdchto portoch sie\u0165 VLAN10 ch\u00fdba, je automaticky vytvoren\u00e1 syst\u00e9mom. Ak sa pozriete na datab\u00e1zu VLAN tohto prep\u00edna\u010da, m\u00f4\u017eete vidie\u0165, \u017ee porty Fa0\/2,0\/3,0\/4 teraz patria do siete VLAN10. <\/p>\n

Potom je potrebn\u00e9 nastavi\u0165 sie\u0165 pre ka\u017ed\u00fd z t\u00fdchto 3 po\u010d\u00edta\u010dov zadan\u00edm IP adries a masiek podsiete. PC2 dostane adresu 192.168.10.3, PC3 \u2013 adresu 192.168.10.4, a PC4 \u2013 IP adresu 192.168.10.5. <\/p>\n

\"Tr\u00e9ning
\n
\nAby sme odpovedali na ot\u00e1zku, \u010di na\u0161a sie\u0165 funguje, pingneme po\u010d\u00edta\u010d PC0 na prvom poschod\u00ed z po\u010d\u00edta\u010da PC4, ktor\u00fd sa nach\u00e1dza na 3. poschod\u00ed alebo v inom budove. Pingovanie bolo ne\u00faspe\u0161n\u00e9, tak sa pok\u00fasime zisti\u0165, pre\u010do sa n\u00e1m to nepodarilo.<\/p>\n

Ke\u010f sme sa sna\u017eili pingova\u0165 Laptop0 z notebooku Laptop2, v\u0161etko fungovalo bez probl\u00e9mov, aj ke\u010f boli pripojen\u00e9 k r\u00f4znym prep\u00edna\u010dom. Pre\u010do teraz, ke\u010f s\u00fa po\u010d\u00edta\u010de na\u0161ich obchodn\u00edkov rovnako pripojen\u00e9 k r\u00f4znym prep\u00edna\u010dom cez trunk, ping neprejde? Aby sme pochopili pr\u00ed\u010dinu probl\u00e9mu, mus\u00edme si spomen\u00fa\u0165, ako prep\u00edna\u010d funguje. <\/p>\n

Ke\u010f posielame paket z po\u010d\u00edta\u010da PC4 na prep\u00edna\u010d SW2, vid\u00ed, \u017ee paket prich\u00e1dza na port Fa0\/4. Prep\u00edna\u010d kontroluje svoju datab\u00e1zu a zist\u00ed, \u017ee port Fa0\/4 patr\u00ed do siete VLAN10. Potom prep\u00edna\u010d ozna\u010d\u00ed r\u00e1mec \u010d\u00edslom siete, teda pripoj\u00ed k paketu trafiku hlavi\u010dku VLAN10 a po\u0161le ho trunkom druh\u00e9mu prep\u00edna\u010du SW1. Tento prep\u00edna\u010d \"\u010d\u00edta\" hlavi\u010dku a vid\u00ed, \u017ee paket je ur\u010den\u00fd pre sie\u0165 VLAN10, pozrie sa do svojej datab\u00e1zy VLAN a zist\u00ed, \u017ee tam \u017eiadna VLAN10 nie je, a paket odmietne. Tak\u017ee zariadenia PC2, 3 a 4 m\u00f4\u017eu bez probl\u00e9mov komunikova\u0165 medzi sebou, ale pokus o nadviazanie spojenia s po\u010d\u00edta\u010dmi PC0 a PC1 zlyh\u00e1, preto\u017ee prep\u00edna\u010d SW1 nevie ni\u010d o sieti VLAN10. <\/p>\n

Tento probl\u00e9m m\u00f4\u017eeme \u013eahko vyrie\u0161i\u0165 t\u00fdm, \u017ee sa prihl\u00e1sime do nastaven\u00ed SW1, vytvor\u00edme sie\u0165 VLAN10 pr\u00edkazom vlan 10 a d\u00e1me jej n\u00e1zov MARKETING. Sk\u00fasime znovu pingova\u0165 \u2013 uvid\u00edte, \u017ee prv\u00e9 tri pakety s\u00fa odmietnut\u00e9, zatia\u013e \u010do \u0161tvrt\u00fd prejde \u00faspe\u0161ne. To je sp\u00f4soben\u00e9 t\u00fdm, \u017ee prep\u00edna\u010d najprv kontroloval IP adresy a ur\u010doval MAC adresy, \u010do trvalo ur\u010dit\u00fd \u010das, a preto boli prv\u00e9 tri pakety odmietnut\u00e9 \u010dasov\u00fdm limitom. Teraz je spojenie vytvoren\u00e9, preto\u017ee prep\u00edna\u010d doplnil svoju tabu\u013eku MAC adries a smeruje pakety priamo na po\u017eadovan\u00fa adresu.
\nV\u0161etko, \u010do som urobil na odstr\u00e1nenie probl\u00e9mu, bolo, \u017ee som sa prihl\u00e1sil do nastaven\u00ed medzi prep\u00edna\u010da a vytvoril tam sie\u0165 VLAN10. Tak\u017ee aj ke\u010f sie\u0165 nie je priamo spojen\u00e1 s prep\u00edna\u010dom, tento by mal vedie\u0165 o v\u0161etk\u00fdch sie\u0165ach, ktor\u00e9 sa podie\u013eaj\u00fa na sie\u0165ov\u00fdch pripojeniach. Ak v\u0161ak m\u00e1te v sieti stovky prep\u00edna\u010dov, fyzicky nebudete schopn\u00ed prihl\u00e1si\u0165 sa do nastaven\u00ed ka\u017ed\u00e9ho z nich a manu\u00e1lne nakonfigurova\u0165 identifik\u00e1tory VLAN. Preto pou\u017e\u00edvame protokol VTP, ktor\u00e9ho nastavenie si uk\u00e1\u017eeme v \u010fal\u0161om videon\u00e1vode. <\/p>\n

Dnes sme pre\u0161li v\u0161etk\u00fdm, \u010do sme pl\u00e1novali: ako vytv\u00e1ra\u0165 VLAN-y, ako priradi\u0165 porty VLAN a ako prezera\u0165 datab\u00e1zu VLAN. Na vytvorenie siet\u00ed vstupujeme do glob\u00e1lneho konfigura\u010dn\u00e9ho re\u017eimu prep\u00edna\u010da a pou\u017e\u00edvame pr\u00edkaz vlan , tie\u017e m\u00f4\u017eeme priradi\u0165 n\u00e1zov vytvorenej siete pomocou pr\u00edkazu name . <\/p>\n

\"Tr\u00e9ning
\n
\nVLAN m\u00f4\u017eeme vytvori\u0165 aj in\u00fdm sp\u00f4sobom, vstupom do re\u017eimu rozhrania a pou\u017eit\u00edm pr\u00edkazu switchport access vlan . V pr\u00edpade, \u017ee sie\u0165 s t\u00fdmto \u010d\u00edslom neexistuje, syst\u00e9m ju automaticky vytvor\u00ed. Nezabudnite pou\u017ei\u0165 pr\u00edkaz exit po vykonan\u00ed zmien v po\u010diato\u010dn\u00fdch nastaveniach, inak sa neulo\u017eia do datab\u00e1zy VLAN. \u010ealej m\u00f4\u017eete priradi\u0165 porty k konkr\u00e9tnym sie\u0165am VLAN pomocou zodpovedaj\u00facich pr\u00edkazov.<\/p>\n

\"Tr\u00e9ning
\n
\nPr\u00edkaz switchport mode access premen\u00ed rozhranie na statick\u00fd re\u017eim access-port, po \u010dom sa \u010d\u00edslo zodpovedaj\u00facej VLAN prirad\u00ed portu pr\u00edkazom switchport access vlan . Na prezretie datab\u00e1zy VLAN sa pou\u017e\u00edva pr\u00edkaz show vlan, ktor\u00fd je potrebn\u00e9 zada\u0165 v u\u017e\u00edvate\u013eskom re\u017eime EXEC. Na zobrazenie zoznamu trunk-portov je potrebn\u00e9 pou\u017ei\u0165 pr\u00edkaz show int trunk. <\/p>\n

\"Tr\u00e9ning
\n
\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\u0448\u043d\u0438\u0439 \u0443\u0440\u043e\u043a \u043c\u044b \u043f\u043e\u0441\u0432\u044f\u0442\u0438\u043c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430\u043c VLAN, \u0442\u043e \u0435\u0441\u0442\u044c \u043f\u043e\u043f\u0440\u043e\u0431\u0443\u0435\u043c \u043f\u0440\u043e\u0434\u0435\u043b\u0430\u0442\u044c \u0432\u0441\u0451 \u0442\u043e, \u043e \u0447\u0435\u043c \u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438 \u043d\u0430 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0445 \u0443\u0440\u043e\u043a\u0430\u0445. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c 3 \u0432\u043e\u043f\u0440\u043e\u0441\u0430: \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u0435 VLAN, \u043f\u0440\u0438\u0441\u0432\u0430\u0438\u0432\u0430\u043d\u0438\u0435 \u043f\u043e\u0440\u0442\u043e\u0432 VLAN \u0438 \u043f\u0440\u043e\u0441\u043c\u043e\u0442\u0440 \u0431\u0430\u0437\u044b \u0434\u0430\u043d\u043d\u044b\u0445 VLAN. \u041e\u0442\u043a\u0440\u043e\u0435\u043c \u043e\u043a\u043d\u043e \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u044b Cisco Packer tracer \u0441 \u043d\u0430\u0440\u0438\u0441\u043e\u0432\u0430\u043d\u043d\u043e\u0439 \u043c\u043d\u043e\u044e \u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0442\u043e\u043f\u043e\u043b\u043e\u0433\u0438\u0435\u0439 \u043d\u0430\u0448\u0435\u0439 \u0441\u0435\u0442\u0438. \u041a \u043f\u0435\u0440\u0432\u043e\u043c\u0443 \u0441\u0432\u0438\u0442\u0447\u0443 SW0 \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0435\u043d\u044b 2 \u043a\u043e\u043c\u043f\u044c\u044e\u0442\u0435\u0440\u0430 PC0 \u0438 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27773,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37049","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\udd47\u0160kolenie Cisco 200-125 CCNA v3.0. De\u0148 13. Nastavenie VLAN | ProHoster","description":"Dne\u0161n\u00e1 lekcia bude venovan\u00e1 nastaveniam VLAN, teda sa pok\u00fasime vykona\u0165 v\u0161etko, o \u010dom sme hovorili na predch\u00e1dzaj\u00facich lekci\u00e1ch.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-13-nastrojka-vlan","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 13. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 VLAN | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0438\u0439 \u0443\u0440\u043e\u043a \u043c\u044b \u043f\u043e\u0441\u0432\u044f\u0442\u0438\u043c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430\u043c VLAN, \u0442\u043e \u0435\u0441\u0442\u044c \u043f\u043e\u043f\u0440\u043e\u0431\u0443\u0435\u043c \u043f\u0440\u043e\u0434\u0435\u043b\u0430\u0442\u044c \u0432\u0441\u0451 \u0442\u043e, \u043e \u0447\u0435\u043c \u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438 \u043d\u0430 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0445 \u0443\u0440\u043e\u043a\u0430\u0445.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-13-nastrojka-vlan","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:15:29+00:00","article:modified_time":"2019-10-31T19:15:29+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37049","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-22 05:51:33","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:34:24","updated":"2026-01-22 05:51:33","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\/37049","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=37049"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/37049\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/27773"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=37049"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=37049"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=37049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}