{"id":37888,"date":"2019-10-31T22:20:23","date_gmt":"2019-10-31T19:20:23","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-vlan\/"},"modified":"2019-10-31T22:20:23","modified_gmt":"2019-10-31T19:20:23","slug":"trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-vlan","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-vlan","title":{"rendered":"\u0160kolenie Cisco 200-125 CCNA v3.0. De\u0148 34. Roz\u0161\u00edren\u00e1 koncepcia VLAN","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

U\u017e sme sa zaoberali lok\u00e1lnymi sie\u0165ami VLAN vo videolekci\u00e1ch D\u0148a 11, 12 a 13 a dnes budeme pokra\u010dova\u0165 v ich \u0161t\u00fadiu v s\u00falade s t\u00e9mou ICND2. Pred nieko\u013ek\u00fdmi mesiacmi som nahr\u00e1val predch\u00e1dzaj\u00face video, ktor\u00e9 znamenalo koniec pr\u00edpravy na sk\u00fa\u0161ku ICND1, a od tej doby som bol ve\u013emi zanepr\u00e1zdnen\u00fd. Mysl\u00edm, \u017ee mnoh\u00ed z v\u00e1s \u00faspe\u0161ne zvl\u00e1dli t\u00fato sk\u00fa\u0161ku, t\u00ed, ktor\u00ed odlo\u017eili testovanie, sa m\u00f4\u017eu do\u010dka\u0165 ukon\u010denia druhej \u010dasti kurzu a pok\u00fasi\u0165 sa urobi\u0165 komplexn\u00fa sk\u00fa\u0161ku CCNA 200-125.<\/p>\n

Dne\u0161n\u00fdm videolekciou 'De\u0148 34' za\u010d\u00edname t\u00e9mu kurzu ICND2. Mnoh\u00ed sa ma p\u00fdtaj\u00fa, pre\u010do sme neprebrali OSPF a EIGRP. D\u00f4vodom je, \u017ee tieto protokoly nie s\u00fa s\u00fa\u010das\u0165ou t\u00e9my kurzu ICND1 a \u0161tuduj\u00fa sa pri pr\u00edprave na sk\u00fa\u0161ku ICND2. Od dne\u0161n\u00e9ho d\u0148a za\u010dneme pokrytie t\u00e9m druhej \u010dasti kurzu a samozrejme presk\u00famame protokoly OSPF a EIGRP. Predt\u00fdm, ako za\u010dneme dne\u0161n\u00fa t\u00e9mu, chcem poveda\u0165 p\u00e1r slov o \u0161trukt\u00fare na\u0161ich videolekci\u00ed. Pri v\u00fdklade t\u00e9m kurzu ICND1 som sa nedr\u017eal zau\u017e\u00edvan\u00fdch \u0161abl\u00f3n a jednoducho logicky vysvet\u013eoval materi\u00e1l, preto\u017ee som si myslel, \u017ee tento sp\u00f4sob je menej zlo\u017eit\u00fd na pochopenie. Teraz v\u0161ak, pri \u0161t\u00fadiu ICND2, na po\u017eiadanie posluch\u00e1\u010dov budem predklada\u0165 u\u010debn\u00fd materi\u00e1l v s\u00falade s u\u010debn\u00fdm pl\u00e1nom a programom kurzu Cisco.<\/a><\/noindex><\/p>\n

Ak nav\u0161t\u00edvite web spolo\u010dnosti, uvid\u00edte tento pl\u00e1n a to, \u017ee cel\u00fd kurz je rozdelen\u00fd na 5 hlavn\u00fdch \u010dast\u00ed: <\/p>\n

\u2014 Technol\u00f3gie prep\u00ednania lok\u00e1lnych siet\u00ed (26% u\u010debn\u00e9ho materi\u00e1lu);
\n \u2014 Technol\u00f3gie smerovania (29%);
\n \u2014 Technol\u00f3gie glob\u00e1lnych siet\u00ed (16%);
\n \u2014 Slu\u017eby infra\u0161trukt\u00fary (14%);
\n \u2014 \u00dadr\u017eba infra\u0161trukt\u00fary (15%).<\/p>\n

Za\u010dnem s prvou \u010das\u0165ou. Ak kliknete na rozba\u013eovacie menu vpravo, m\u00f4\u017eete vidie\u0165 podrobn\u00fa tematiku tejto sekcie. Dne\u0161n\u00fd videolekcia pokryje t\u00e9mu sekcie 1.1: 'Nastavenie, kontrola a odstra\u0148ovanie probl\u00e9mov s VLAN sie\u0165ami (be\u017en\u00fd \/ roz\u0161\u00edren\u00fd rozsah), pokr\u00fdvaj\u00facich nieko\u013eko prep\u00edna\u010dov' a podsekci\u00ed 1.1a 'Pr\u00edstupov\u00e9 porty (d\u00e1tov\u00e9 a hlasov\u00e9 spr\u00e1vy)' a 1.1.b 'Predvolen\u00e1 VLAN'.<\/p>\n

\u010ealej sa budem sna\u017ei\u0165 dodr\u017eiava\u0165 tento ist\u00fd princ\u00edp v\u00fdkladu, teda ka\u017ed\u00fd video tutori\u00e1l bude venovan\u00fd jednej sekcii s podsekciami, a ak bude materi\u00e1lu m\u00e1lo, spoj\u00edm do jedn\u00e9ho lekcie t\u00e9my viacer\u00fdch sekci\u00ed, napr\u00edklad 1.2 a 1.3. Ak v\u0161ak materi\u00e1lu v sekcii bude ve\u013ea, rozdel\u00edm ho na dve vide\u00e1. V ka\u017edom pr\u00edpade budeme sledova\u0165 program kurzu, a vy si m\u00f4\u017eete \u013eahko porovna\u0165 zhodu va\u0161ich pozn\u00e1mok s aktu\u00e1lnym u\u010debn\u00fdm pl\u00e1nom Cisco. <\/p>\n

\"\u0160kolenie
\n
\nNa obrazovke vid\u00edte moju nov\u00fa pracovn\u00fa plochu, je to Windows 10. Ak chcete vylep\u0161i\u0165 svoju pracovn\u00fa plochu pomocou r\u00f4znych widgetov, m\u00f4\u017eete sa pozrie\u0165 na moje video s n\u00e1zvom \u201ePimp Your Desktop\u201c, kde vysvet\u013eujem, ako nastavi\u0165 pracovn\u00fa plochu po\u010d\u00edta\u010da pod\u013ea va\u0161ich potrieb. Vide\u00e1 tohto druhu zverej\u0148ujem na in\u00fdch kan\u00e1loch, ExplainWorld, tak\u017ee m\u00f4\u017eete vyu\u017ei\u0165 odkaz v pravom hornom rohu a obozn\u00e1mi\u0165 sa s jeho obsahom.<\/p>\n

Pred za\u010diatkom lekcie v\u00e1s pros\u00edm, aby ste nezab\u00fadali zdie\u013ea\u0165 moje vide\u00e1 a d\u00e1va\u0165 im palce hore. Chcem tie\u017e pripomen\u00fa\u0165 na\u0161e kontakty na soci\u00e1lnych sie\u0165ach a odkazy na moje osobn\u00e9 str\u00e1nky. M\u00f4\u017eete mi p\u00edsa\u0165 na email a, ako som u\u017e povedal, prioritu v z\u00edskan\u00ed mojej osobnej odpovede bud\u00fa ma\u0165 \u013eudia, ktor\u00ed urobili darovanie na na\u0161ej str\u00e1nke. <\/p>\n

Ak ste neurobili \u017eiadne darovanie, ni\u010d sa nedeje, m\u00f4\u017eete zanecha\u0165 svoje koment\u00e1re pod video tutori\u00e1lmi na kan\u00e1li YouTube a ja na ne budem odpoveda\u0165 pod\u013ea mo\u017enosti. <\/p>\n

Dnes, pod\u013ea rozvrhu Cisco, sa budeme zaobera\u0165 3 ot\u00e1zkami: porovn\u00e1me Default VLAN, alebo VLAN pod\u013ea predvolen\u00fdch nastaven\u00ed, s Native VLAN, alebo \u201adomovskou\u2018 VLAN, zist\u00edme, \u010d\u00edm sa l\u00ed\u0161i Normal VLAN (\u0161tandardn\u00fd rozsah VLAN) od roz\u0161\u00edren\u00e9ho rozsahu siet\u00ed Extended VLAN a presk\u00famame rozdiel medzi Data VLAN (VLAN d\u00e1t) a Voice VLAN (hlasov\u00e1 VLAN). Ako som povedal, u\u017e sme t\u00fato t\u00e9mu preberali v predch\u00e1dzaj\u00facich epiz\u00f3dach, ale dos\u0165 povrchne, tak\u017ee dodnes mnoh\u00ed \u0161tudenti maj\u00fa \u0165a\u017ekosti s ur\u010den\u00edm rozdielu medzi typmi VLAN. Dnes to vysvetl\u00edm tak, aby to bolo jasn\u00e9 v\u0161etk\u00fdm. <\/p>\n

Pozrime sa na to, v \u010dom spo\u010d\u00edva rozdiel medzi Default VLAN a Native VLAN. Ak vezmete \u00faplne nov\u00fd switch Cisco s tov\u00e1rensk\u00fdmi nastaveniami, bude ma\u0165 5 VLAN \u2013 VLAN1, VLAN1002, VLAN1003, VLAN1004 a VLAN1005. <\/p>\n

\"\u0160kolenie
\n
\nVLAN1 je predvolen\u00fd VLAN pre v\u0161etky zariadenia Cisco, zatia\u013e \u010do VLAN 1002-1005 s\u00fa rezervovan\u00e9 pre Token Ring a FDDI. Sie\u0165 VLAN1 nie je mo\u017en\u00e9 odstr\u00e1ni\u0165 alebo premenova\u0165, nemo\u017eno k nej prida\u0165 rozhrania a v\u0161etky porty switche patria do tejto siete, pokia\u013e nie s\u00fa nastaven\u00e9 inak. Predvolene si v\u0161etky switche m\u00f4\u017eu medzi sebou komunikova\u0165, preto\u017ee v\u0161etky s\u00fa s\u00fa\u010das\u0165ou VLAN1. Toto je v\u00fdznam \u201epredvolen\u00e9ho VLAN\u201c alebo Default VLAN.<\/p>\n

Ak vojdete do nastaven\u00ed switche SW1 a prirad\u00edte dve rozhrania k sieti VLAN20, stan\u00fa sa s\u00fa\u010das\u0165ou siete VLAN20. Predt\u00fdm, ako za\u010dneme dne\u0161n\u00fa lekciu, d\u00f4razne v\u00e1m odpor\u00fa\u010dam prejs\u0165 si vy\u0161\u0161ie uveden\u00e9 s\u00e9rie 11, 12 a 13 dn\u00ed, preto\u017ee nebudem opakova\u0165, \u010do je VLAN a ako funguj\u00fa. <\/p>\n

\"\u0160kolenie
\n
\nLen si pripom\u00ednam, \u017ee nie je mo\u017en\u00e9 automaticky priradi\u0165 rozhrania k sieti VLAN20, pokia\u013e ju nevytvor\u00edte, tak\u017ee najprv mus\u00edte prejs\u0165 do glob\u00e1lneho konfigura\u010dn\u00e9ho re\u017eimu switche a vytvori\u0165 VLAN20. M\u00f4\u017eete sa pozrie\u0165 na konzolu nastaven\u00ed CLI a pochopi\u0165, \u010do m\u00e1m na mysli. Po priraden\u00ed t\u00fdchto 2 portov na pr\u00e1cu s VLAN20 bud\u00fa po\u010d\u00edta\u010de PC1 a PC2 m\u00f4c\u0165 medzi sebou komunikova\u0165, preto\u017ee obidva bud\u00fa patri\u0165 do tej istej siete VLAN20. Av\u0161ak po\u010d\u00edta\u010d PC3 bude st\u00e1le s\u00fa\u010das\u0165ou VLAN1 a preto nebude m\u00f4c\u0165 komunikova\u0165 s po\u010d\u00edta\u010dmi v sieti VLAN20. <\/p>\n

M\u00e1me druh\u00fd switch SW2, jedno z jeho rozhran\u00ed je priraden\u00e9 pre pr\u00e1cu s VLAN20 a k tomuto portu je pripojen\u00fd po\u010d\u00edta\u010d PC5. Pri takomto zapojen\u00ed PC5 nem\u00f4\u017ee komunikova\u0165 s PC4 a PC6, ale tieto dva po\u010d\u00edta\u010de m\u00f4\u017eu medzi sebou komunikova\u0165, preto\u017ee patria do tej istej siete VLAN1. <\/p>\n

Oba switche s\u00fa prepojen\u00e9 trunkom cez spr\u00e1vne nakonfigurovan\u00e9 porty. Nebudem sa opakova\u0165, len poviem, \u017ee v\u0161etky porty switche s\u00fa predvolene nastaven\u00e9 na trunk re\u017eim podle protokolu DTP. Ak pripoj\u00edte po\u010d\u00edta\u010d k nejak\u00e9mu portu, tento port bude pou\u017e\u00edva\u0165 access mode. Ak chcete previes\u0165 do tohto re\u017eimu port, ku ktor\u00e9mu je pripojen\u00fd PC3, mus\u00edte zada\u0165 pr\u00edkaz switchport mode access. <\/p>\n

Tak\u017ee, ak prepoj\u00edte dva switche navz\u00e1jom, vytvor\u00ed sa trunk. Dva horn\u00e9 porty SW1 bud\u00fa pren\u00e1\u0161a\u0165 iba VLAN20 traffic, doln\u00fd port iba VLAN1 traffic, ale trunkov\u00e9 pripojenie bude pren\u00e1\u0161a\u0165 v\u0161etok traffic, ktor\u00fd prech\u00e1dza cez switch. T\u00fdm p\u00e1dom bude na SW2 prich\u00e1dza\u0165 traffic ako VLAN1, tak VLAN20. <\/p>\n

Ako si pam\u00e4t\u00e1te, siete VLAN maj\u00fa lok\u00e1lny v\u00fdznam. Preto SW2 vie, \u017ee prev\u00e1dzka, ktor\u00e1 pri\u0161la na port VLAN1 od PC4, m\u00f4\u017ee by\u0165 odoslan\u00e1 na PC6 iba cez port, ktor\u00fd patr\u00ed tie\u017e do VLAN1. Av\u0161ak ke\u010f jeden prep\u00edna\u010d posiela prev\u00e1dzku druh\u00e9mu prep\u00edna\u010du cez trunk, mus\u00ed pou\u017ei\u0165 mechanizmus, ktor\u00fd vysvetl\u00ed druh\u00e9mu prep\u00edna\u010du, o ak\u00fa prev\u00e1dzku ide. Ako tak\u00fd mechanizmus sa pou\u017e\u00edva sie\u0165 Native VLAN, ktor\u00e1 je pripojen\u00e1 k trunk-portu a prep\u00fa\u0161\u0165a cez seba ozna\u010den\u00fa prev\u00e1dzku. <\/p>\n

\"\u0160kolenie<\/p>\n

Ako som u\u017e povedal, prep\u00edna\u010d m\u00e1 iba jednu sie\u0165, ktor\u00e1 nie je podliehaj\u00faca zmen\u00e1m \u2013 to je sie\u0165 predvolen\u00e1 VLAN1. Ale predvolene je Native VLAN pr\u00e1ve VLAN1. \u010co je to Native VLAN? Je to sie\u0165, ktor\u00e1 prep\u00fa\u0161\u0165a neozna\u010den\u00fa prev\u00e1dzku VLAN1, ale hne\u010f ako na trunk-port pr\u00edde prev\u00e1dzka z akejko\u013evek inej siete, v na\u0161om pr\u00edpade VLAN20, mus\u00ed by\u0165 v\u017edy ozna\u010den\u00e1. Ka\u017ed\u00fd r\u00e1mec m\u00e1 adresu cie\u013ea DA, adresu zdroja SA a tag VLAN, ktor\u00fd obsahuje identifik\u00e1tor siete VLAN ID. V na\u0161om pr\u00edpade tento identifik\u00e1tor ukazuje, \u017ee t\u00e1to prev\u00e1dzka patr\u00ed do VLAN20, a preto m\u00f4\u017ee by\u0165 odoslan\u00e1 iba cez port VLAN20 a je ur\u010den\u00e1 pre PC5. M\u00f4\u017eeme poveda\u0165, \u017ee Native VLAN rozhoduje, \u010di m\u00e1 by\u0165 prev\u00e1dzka ozna\u010den\u00e1, alebo nie. <\/p>\n

Pam\u00e4tajte, \u017ee VLAN1 je predvolene Native VLAN, preto\u017ee predvolene v\u0161etky porty pou\u017e\u00edvaj\u00fa VLAN1 ako Native VLAN na prenos neozna\u010denej prev\u00e1dzky. Av\u0161ak sie\u0165ou Default VLAN je iba VLAN1, jedin\u00e1 sie\u0165, ktor\u00e1 nem\u00f4\u017ee by\u0165 zmenen\u00e1. Ak prep\u00edna\u010d dostane neozna\u010den\u00e9 r\u00e1my na trunk-port, automaticky ich prira\u010fuje k Native VLAN. <\/p>\n

Jednoducho povedan\u00e9, v prep\u00edna\u010doch Cisco m\u00f4\u017ee by\u0165 ak\u00e1ko\u013evek VLAN pou\u017eit\u00e1 ako Native VLAN, napr\u00edklad VLAN20, a ako Default VLAN m\u00f4\u017ee by\u0165 pou\u017eit\u00e1 iba VLAN1. <\/p>\n

M\u00f4\u017ee sa vyskytn\u00fa\u0165 probl\u00e9m. Ak zmen\u00edme Native VLAN na trunk porte prv\u00e9ho switche na VLAN20, port si pomysl\u00ed: \u201eke\u010f\u017ee je to Native VLAN, jej traffic netreba ozna\u010dova\u0165\u201c a po\u0161le neozna\u010den\u00fd traffic siete VLAN20 po trunku druh\u00e9mu switchu. Switch SW2, ke\u010f prijme tento traffic, povie: \u201ev\u00fdborne, tento traffic nem\u00e1 \u0161t\u00edtok. Pod\u013ea mojich nastaven\u00ed je moja Native VLAN VLAN1, tak\u017ee mus\u00edm tento neozna\u010den\u00fd traffic posla\u0165 po sieti VLAN1\u201c. Takto SW2 nasmeruje prijat\u00fd traffic iba na PC4 a PC6, hoci je ur\u010den\u00fd pre PC5. To sp\u00f4sob\u00ed v\u00e1\u017eny bezpe\u010dnostn\u00fd probl\u00e9m, preto\u017ee zjednot\u00ed traffic VLAN. Preto je potrebn\u00e9 na oboch trunk portoch v\u017edy nastavi\u0165 rovnak\u00fa Native VLAN; to znamen\u00e1, ak je Native VLAN pre trunk port SW1 VLAN20, potom t\u00e1 ist\u00e1 VLAN20 by mala by\u0165 nastaven\u00e1 ako Native VLAN na trunk porte SW2. <\/p>\n

To je rozdiel medzi Native VLAN a Default VLAN, a mus\u00edte pam\u00e4ta\u0165, \u017ee v\u0161etky Native VLAN v trunku musia s\u00fahlasi\u0165 (pozn\u00e1mka prekladate\u013ea: preto je lep\u0161ie pou\u017ei\u0165 sie\u0165 in\u00fa ako VLAN1 ako Native VLAN). <\/p>\n

Pozrime sa na to z poh\u013eadu switche. M\u00f4\u017eete prejs\u0165 do switche a zada\u0165 pr\u00edkaz show vlan brief, po ktorom uvid\u00edte, \u017ee v\u0161etky porty switche s\u00fa pripojen\u00e9 k Default VLAN1.<\/p>\n

\"\u0160kolenie
\n
\nNi\u017e\u0161ie s\u00fa uveden\u00e9 \u010fal\u0161ie 4 siete VLAN: 1002, 1003, 1004 a 1005. Tieto s\u00fa tie\u017e Default VLAN, \u010do vid\u00edte z ich ozna\u010denia. S\u00fa to siete predvolen\u00e9, preto\u017ee s\u00fa vyhraden\u00e9 pre konkr\u00e9tne siete \u2014 Token Ring a FDDI. Ako vid\u00edte, s\u00fa v akt\u00edvnom stave, ale nie s\u00fa podporovan\u00e9, preto\u017ee k switche nie s\u00fa pripojen\u00e9 siete uveden\u00fdch \u0161tandardov. <\/p>\n

Ozna\u010denie 'default' pre sie\u0165 VLAN 1 nemo\u017eno zmeni\u0165, preto\u017ee je to predvolen\u00e1 sie\u0165. Ke\u010f\u017ee v\u0161etky porty switche s\u00fa predvolene priraden\u00e9 k tejto sieti, v\u0161etky switche m\u00f4\u017eu vz\u00e1jomne komunikova\u0165 predvolene, teda bez potreby \u010fal\u0161ieho nastavenia portov. Ak chcete pripoji\u0165 switch k inej sieti, prejdete do glob\u00e1lneho re\u017eimu nastaven\u00ed a vytvor\u00edte t\u00fato sie\u0165, napr\u00edklad VLAN20. Po stla\u010den\u00ed 'Enter' prejdete k nastaveniam vytvorenej siete a m\u00f4\u017eete jej priradi\u0165 n\u00e1zov, napr\u00edklad Management, po \u010dom m\u00f4\u017eete opusti\u0165 nastavenia.<\/p>\n

Ak teraz pou\u017eijete pr\u00edkaz show vlan brief, uvid\u00edte, \u017ee sa objavila nov\u00e1 sie\u0165 VLAN20, ktorej nevyhovuje \u017eiadny port prep\u00edna\u010da. Aby ste priradili tejto sieti konkr\u00e9tny port, je potrebn\u00e9 vybra\u0165 rozhranie, napr\u00edklad int e0\/1, prejs\u0165 do nastaven\u00ed tohto portu a zada\u0165 pr\u00edkazy switchport mode access a switchport access vlan20. <\/p>\n

\"\u0160kolenie
\n
\nAk po\u017eiadate syst\u00e9m, aby zobrazil stav siet\u00ed VLAN, uvid\u00edme, \u017ee port Ethernet 0\/1 je ur\u010den\u00fd pre sie\u0165 Management, teda bol automaticky premiestnen\u00fd sem z oblasti portov, ktor\u00e9 s\u00fa predvolene ur\u010den\u00e9 pre VLAN1.<\/p>\n

\"\u0160kolenie
\n
\nZapam\u00e4tajte si, \u017ee ka\u017ed\u00fd access-port m\u00f4\u017ee ma\u0165 len jednu Data VLAN, tak\u017ee nem\u00f4\u017ee naraz obsluhova\u0165 dve siete VLAN. <\/p>\n

Teraz sa pozrime na Native VLAN. Pou\u017e\u00edvam pr\u00edkaz show int trunk a vid\u00edm, \u017ee port Ethernet0\/0 je vyhraden\u00fd pre trunk. <\/p>\n

\"\u0160kolenie
\n
\nNemusel som to robi\u0165 \u0161peci\u00e1lne, preto\u017ee protokol DTP automaticky priradil toto rozhranie pre trunkovanie. Port je v re\u017eime desirable, enkapsul\u00e1cia typu n-isl, stav portu \u2013 trunking, sie\u0165 \u2013 Native VLAN1. <\/p>\n

\u010ealej je uveden\u00fd prijate\u013en\u00fd pre trunking rozsah \u010d\u00edsel siet\u00ed VLAN 1-4094 a je uveden\u00e9, \u017ee n\u00e1m funguj\u00fa siete VLAN1 a VLAN20. Teraz prejdeme do re\u017eimu glob\u00e1lnej konfigur\u00e1cie a zad\u00e1m pr\u00edkaz int e0\/0, v\u010faka ktor\u00e9mu prejdeme do nastaven\u00ed tohto rozhrania. Sna\u017e\u00edm sa manu\u00e1lne naprogramova\u0165 tento port na pr\u00e1cu v re\u017eime trunk pr\u00edkazom switchport mode trunk, av\u0161ak syst\u00e9m neprij\u00edma pr\u00edkaz a odpoved\u00e1, \u017ee: \u201erozhranie s automatick\u00fdm re\u017eimom enkapsul\u00e1cie trunk nem\u00f4\u017ee by\u0165 prelo\u017een\u00e9 do re\u017eimu trunk. <\/p>\n

Preto mus\u00edm najprv nastavi\u0165 typ enkapsul\u00e1cie trunk, na \u010do pou\u017e\u00edvam pr\u00edkaz switchport trunk encapsulation. Syst\u00e9m poskytol n\u00e1povedy s mo\u017en\u00fdmi parametrami tohto pr\u00edkazu:<\/p>\n

dot1q \u2013 po\u010das trunkovania port pou\u017e\u00edva enkapsul\u00e1ciu trunk \u0161tandardu 802.1q;
\nisl \u2013 po\u010das trunkovania port pou\u017e\u00edva enkapsul\u00e1ciu trunk iba propriet\u00e1rneho protokolu Cisco ISL;
\nnegotiate \u2013 zariadenie vykon\u00e1va enkapsul\u00e1ciu trunk s ak\u00fdmko\u013evek zariaden\u00edm pripojen\u00fdm k tomuto portu.<\/p>\n

\"\u0160kolenie
\n
\nNa ka\u017edom konci trunku sa mus\u00ed vybra\u0165 ten ist\u00fd typ enkapsul\u00e1cie. Predvolene switch \u201ez krabice\u201c podporuje iba trunking typu dot1q, ke\u010f\u017ee tento \u0161tandard podporuj\u00fa prakticky v\u0161etky sie\u0165ov\u00e9 zariadenia. Naprogramujem na\u0161e rozhranie na enkapsul\u00e1ciu trunkingu pod\u013ea tohto \u0161tandardu pr\u00edkazom switchport trunk encapsulation dot1q, po \u010dom pou\u017eijem predt\u00fdm odmietnut\u00fd pr\u00edkaz switchport mode trunk. Teraz je n\u00e1\u0161 port naprogramovan\u00fd na re\u017eim trunk. <\/p>\n

Ak je trunk vytvoren\u00fd dvoma switchmi Cisco, predvolene sa pou\u017eije propriet\u00e1rny protokol ISL. Ak jeden switch podporuje dot1q a ISL, a druh\u00fd iba dot1q, trunk sa automaticky prekonfiguruj\u00fa do re\u017eimu enkapsul\u00e1cie dot1q. Ak sa op\u00e4\u0165 pozrieme na parametre trunkingu, uvid\u00edme, \u017ee re\u017eim enkapsul\u00e1cie trunkingu rozhrania Et0\/0 sa zmenil z n-isl na 802.1q.<\/p>\n

\"\u0160kolenie
\n
\nAk zad\u00e1me pr\u00edkaz show int e0\/0 switchport, uvid\u00edme v\u0161etky parametre stavu tohto portu. <\/p>\n

\"\u0160kolenie
\n
\nVid\u00edte, \u017ee predvolene VLAN1 je pre trunking \u201erodnou sie\u0165ou\u201c Native VLAN a v tomto re\u017eime je mo\u017en\u00e9 ozna\u010dovanie prev\u00e1dzky Native VLAN. Potom pou\u017eijem pr\u00edkaz int e0\/0, prejdeme do nastaven\u00ed tohto rozhrania a zad\u00e1m switchport trunk, po ktorom syst\u00e9m poskytne n\u00e1povedu mo\u017en\u00fdch parametrov tohto pr\u00edkazu. <\/p>\n

\"\u0160kolenie
\n
\nAllowed znamen\u00e1, \u017ee ak je port v re\u017eime trunku, bud\u00fa nastaven\u00e9 povolen\u00e9 charakteristiky VLAN. Encapsulation aktivuje enkapsul\u00e1ciu trunkingu, ak je port v re\u017eime trunku. Pou\u017e\u00edvam parameter native, ktor\u00fd znamen\u00e1, \u017ee v re\u017eime trunku bud\u00fa pre port nastaven\u00e9 native-charakteristiky, a zad\u00e1m pr\u00edkaz switchport trunk native VLAN20. T\u00fdm p\u00e1dom, v re\u017eime trunku VLAN20 bude Native VLAN pre tento port prv\u00e9ho switcha SW1.<\/p>\n

M\u00e1me in\u00fd switch, SW2, pre trunk-port ktor\u00e9ho sa ako Native VLAN pou\u017e\u00edva VLAN1. Teraz vid\u00edte, \u017ee protokol CDP vyd\u00e1va spr\u00e1vu o tom, \u017ee bolo zisten\u00e9 nes\u00falad Native VLAN na oboch koncoch trunku: trunk-port prv\u00e9ho switcha Ethernet0\/0 pou\u017e\u00edva Native VLAN20, zatia\u013e \u010do trunk-port druh\u00e9ho \u2014 Native VLAN1. To ilustruje, v \u010dom spo\u010d\u00edva rozdiel medzi Native VLAN a Default VLAN. <\/p>\n

Po\u010fme sa pozrie\u0165 na be\u017en\u00fd a roz\u0161\u00edren\u00fd rozsah siet\u00ed VLAN.<\/p>\n

\"\u0160kolenie
\n
\nDlh\u00fd \u010das spolo\u010dnos\u0165 Cisco podporovala iba rozsah VLAN \u010d\u00edsel od 1 do 1005, pri\u010dom rozsah od 1002 do 1005 bol predvolene rezervovan\u00fd pre Token Ring a FDDI VLAN. Tieto siete sa naz\u00fdvali be\u017en\u00fdmi VLAN. Ak si pam\u00e4t\u00e1te, VLAN ID je zna\u010dkov\u00fd identifik\u00e1tor ve\u013ekosti 12 bitov, ktor\u00fd umo\u017e\u0148uje nastavi\u0165 \u010d\u00edslo a\u017e do 4096, av\u0161ak z d\u00f4vodov kompatibility spolo\u010dnos\u0165 Cisco pou\u017e\u00edvala \u010d\u00edsla iba do 1005. <\/p>\n

Roz\u0161\u00edren\u00fd rozsah VLAN zah\u0155\u0148a \u010d\u00edsla od 1006 do 4095. M\u00f4\u017ee sa pou\u017e\u00edva\u0165 na star\u0161\u00edch zariadeniach len ak podporuj\u00fa VTP v3. Ak pou\u017e\u00edvate VTP v3 a roz\u0161\u00edren\u00fd rozsah VLAN, mus\u00edte vypn\u00fa\u0165 podporu VTP v1 a v2, preto\u017ee prv\u00e1 a druh\u00e1 verzia nem\u00f4\u017eu pracova\u0165 s VLAN, ktor\u00e9 maj\u00fa \u010d\u00edslo vy\u0161\u0161ie ako 1005. <\/p>\n

Tak\u017ee ak pou\u017e\u00edvate Extended VLAN pre star\u00e9 prep\u00edna\u010de, VTP by mal by\u0165 v stave \u201edesable\u201c a mus\u00edte ho nastavi\u0165 manu\u00e1lne pre VLAN, inak nebude mo\u017en\u00e9 aktualizova\u0165 datab\u00e1zu VLAN. Ak pl\u00e1nujete pou\u017e\u00edva\u0165 Extended VLAN s VTP, potrebujete tretiu verziu VTP.<\/p>\n

Pozrime sa na stav VTP pomocou pr\u00edkazu show vtp status. Vid\u00edte, \u017ee prep\u00edna\u010d pracuje v re\u017eime VTP v2, pri\u010dom je mo\u017en\u00e1 podpora verzi\u00ed 1 a 3. Priradil som mu dom\u00e9nov\u00e9 meno nwking.org.<\/p>\n

Tu je d\u00f4le\u017eit\u00fd re\u017eim spr\u00e1vy VTP \u2013 server. Vid\u00edte, \u017ee maxim\u00e1lny po\u010det podporovan\u00fdch VLAN siet\u00ed je 1005. T\u00fdm p\u00e1dom m\u00f4\u017eeme pochopi\u0165, \u017ee tento prep\u00edna\u010d predvolene podporuje iba be\u017en\u00fd rozsah VLAN. <\/p>\n

\"\u0160kolenie
\n
\nTeraz zad\u00e1m pr\u00edkaz show vlan brief a uvid\u00edte VLAN20 Management, ktor\u00e1 sa tu spom\u00edna, preto\u017ee je s\u00fa\u010das\u0165ou datab\u00e1zy VLAN.<\/p>\n

\"\u0160kolenie
\n
\nAk teraz po\u017eiadam o zobrazenie aktu\u00e1lnej konfigur\u00e1cie zariadenia pr\u00edkazom show run, neuvid\u00edme \u017eiadne spomenutie VLAN, preto\u017ee s\u00fa obsiahnut\u00e9 iba v datab\u00e1ze VLAN.
\nPotom pou\u017eijem pr\u00edkaz vtp mode na nastavenie re\u017eimu VTP. Prep\u00edna\u010de star\u0161\u00edch modelov mali pre tento pr\u00edkaz iba tri parametre: client, ktor\u00fd prepne prep\u00edna\u010d do re\u017eimu klienta, server, ktor\u00fd aktivuje re\u017eim servera, a transparent, ktor\u00fd prepne prep\u00edna\u010d do 'prieh\u013eadn\u00e9ho' re\u017eimu. Ke\u010f\u017ee na star\u0161\u00edch prep\u00edna\u010doch nebolo mo\u017en\u00e9 \u00faplne vypn\u00fa\u0165 VTP, v tomto re\u017eime prep\u00edna\u010d, zost\u00e1vaj\u00faci v dom\u00e9ne VTP, jednoducho prestal prij\u00edma\u0165 aktualiz\u00e1cie datab\u00e1zy VLAN siet\u00ed prich\u00e1dzaj\u00face na jeho porty cez protokol VTP.<\/p>\n

V nov\u00fdch switchoch sa objavil parameter off, ktor\u00fd umo\u017e\u0148uje \u00faplne vypn\u00fa\u0165 re\u017eim VTP. Prejdime na transparentn\u00fd re\u017eim pr\u00edkazom vtp mode transparent a e\u0161te raz si pozrime aktu\u00e1lnu konfigur\u00e1ciu. Ako vid\u00edte, teraz sa do nej pridala polo\u017eka o VLAN20. Tak\u017ee ak prid\u00e1me nejak\u00fa sie\u0165 VLAN, ktorej \u010d\u00edslo sa nach\u00e1dza v be\u017enom rozsahu VLAN od 1 do 1005, a pri tom bude VTP v re\u017eime transparent alebo off, v s\u00falade s vn\u00fatorn\u00fdmi politikami VLAN, t\u00e1to sie\u0165 sa prid\u00e1 do aktu\u00e1lnej konfigur\u00e1cie a do datab\u00e1zy virtu\u00e1lnych lok\u00e1lnych siet\u00ed.<\/p>\n

Sk\u00fasime prida\u0165 VLAN 3000 a uvid\u00edte, \u017ee v transparentnom re\u017eime sa tie\u017e objavila v aktu\u00e1lnej konfigur\u00e1cii. Zvy\u010dajne, ak chceme prida\u0165 sie\u0165 z roz\u0161\u00edren\u00e9ho rozsahu VLAN, mus\u00edme pou\u017ei\u0165 pr\u00edkaz vtp version 3. Ako vid\u00edte, obidve siete VLAN20 a VLAN3000 sa zobrazuj\u00fa v aktu\u00e1lnej konfigur\u00e1cii.<\/p>\n

Ak vyst\u00fapime z re\u017eimu transparent a zapneme re\u017eim servera pomocou pr\u00edkazu vtp mode server, a potom sa op\u00e4\u0165 pozrieme na aktu\u00e1lnu konfigur\u00e1ciu, vid\u00edme, \u017ee z\u00e1znamy o VLAN \u00faplne zmizli. To sa stalo preto, \u017ee v\u0161etky inform\u00e1cie o VLAN sa ukladaj\u00fa iba v datab\u00e1ze VLAN a m\u00f4\u017eu sa prezera\u0165 iba v transparentnom re\u017eime VTP. Preto\u017ee som zapol re\u017eim VTP v3, po pou\u017eit\u00ed pr\u00edkazu show vtp status je vidie\u0165, \u017ee maxim\u00e1lny po\u010det podporovan\u00fdch VLAN sa zv\u00fd\u0161il na 4096. <\/p>\n

Tak\u017ee datab\u00e1za VTP v1 a VTP v2 podporuje iba be\u017en\u00e9 VLAN s \u010d\u00edslami od 1 do 1005, zatia\u013e \u010do datab\u00e1za VTP v3 obsahuje z\u00e1znamy o roz\u0161\u00edren\u00fdch VLAN s \u010d\u00edslami od 1 do 4096. Ak pou\u017e\u00edvate re\u017eim VTP transparent alebo VTP off, inform\u00e1cie o VLAN bud\u00fa pridan\u00e9 do aktu\u00e1lnej konfigur\u00e1cie. Ak chcete pou\u017e\u00edva\u0165 roz\u0161\u00edren\u00fd rozsah VLAN, zariadenie mus\u00ed by\u0165 v re\u017eime VTP v3. Toto je rozdiel medzi be\u017en\u00fdmi a roz\u0161\u00edren\u00fdmi VLAN.<\/p>\n

A teraz porovn\u00e1me VLAN pre d\u00e1ta a VLAN pre hlasov\u00fd prenos. Ak si pam\u00e4t\u00e1te, povedal som, \u017ee ka\u017ed\u00fd port m\u00f4\u017ee s\u00fa\u010dasne patri\u0165 iba jednej VLAN. <\/p>\n

\"\u0160kolenie
\n
\nV mnoh\u00fdch pr\u00edpadoch potrebujeme nastavi\u0165 port na pr\u00e1cu s IP telef\u00f3nom. Modern\u00e9 IP telef\u00f3ny Cisco obsahuj\u00fa svoj vlastn\u00fd switch, tak\u017ee m\u00f4\u017eete jednoducho pripoji\u0165 telef\u00f3n k\u00e1blom k stenovej z\u00e1suvke a patch cordom k svojmu po\u010d\u00edta\u010du. Probl\u00e9m spo\u010d\u00edval v tom, \u017ee stenov\u00e1 z\u00e1suvka, ku ktorej je pripojen\u00fd port telef\u00f3nu, mala ma\u0165 dve r\u00f4zne VLAN. U\u017e sme v video lekci\u00e1ch 11 a 12 hovorili o tom, \u010do treba robi\u0165, aby sme predi\u0161li slu\u010dk\u00e1m v prev\u00e1dzke, ako pou\u017e\u00edva\u0165 koncept \u201enativnej\u201c VLAN, ktor\u00e1 prep\u00fa\u0161\u0165a netegovan\u00fd provoz, ale to v\u0161etko boli obch\u00e1dzkov\u00e9 met\u00f3dy. Kone\u010dn\u00fdm rie\u0161en\u00edm probl\u00e9mu sa stal koncept rozdelenia VLAN na siete pre d\u00e1tov\u00fa prev\u00e1dzku a siete pre hlasov\u00fa prev\u00e1dzku. <\/p>\n

V tomto pr\u00edpade sp\u00e1jate v\u0161etky telef\u00f3nne linky do hlasovej VLAN. Na obr\u00e1zku je zn\u00e1zornen\u00e9, \u017ee po\u010d\u00edta\u010de PC1 a PC2 m\u00f4\u017eu patri\u0165 \u010dervenej sieti VLAN20, po\u010d\u00edta\u010d PC3 patr\u00ed zelenej sieti VLAN30, ale v\u0161etky s nimi s\u00favisiace IP telef\u00f3ny bud\u00fa patri\u0165 do jednej a tej istej \u017eltej hlasovej siete VLAN50. <\/p>\n

V skuto\u010dnosti bude ka\u017ed\u00fd port switche SW1 ma\u0165 s\u00fa\u010dasne 2 siete VLAN \u2013 pre d\u00e1ta a pre hlas. <\/p>\n

\"\u0160kolenie
\n
\nAko som povedal, access VLAN m\u00e1 v\u017edy jednu VLAN, nem\u00f4\u017eete ma\u0165 dve VLAN na jednom porte. Nem\u00f4\u017eete s\u00fa\u010dasne pou\u017ei\u0165 na jednom rozhran\u00ed pr\u00edkazy switchport access vlan 10, switchport access vlan 20 a switchport access vlan 50. Ale m\u00f4\u017eete pou\u017ei\u0165 pre to ist\u00e9 rozhranie dva pr\u00edkazy: pr\u00edkaz switchport access vlan 10 a pr\u00edkaz switchport voice vlan 50. Tak\u017ee, ke\u010f\u017ee IP telef\u00f3n obsahuje vo vn\u00fatri switch, m\u00f4\u017ee enkapsulova\u0165 a posiela\u0165 hlasov\u00fa prev\u00e1dzku VLAN50 a s\u00fa\u010dasne prij\u00edma\u0165 a odosiela\u0165 v re\u017eime switchport access prev\u00e1dzku d\u00e1tovej siete VLAN20 switche SW1. Pozrime sa, ako sa nastavuje tento re\u017eim. <\/p>\n

Najprv vytvor\u00edme sie\u0165 VLAN50 a potom prejdeme k nastaveniam rozhrania Ethernet 0\/1 a naprogramujeme ho do re\u017eimu switchport mode access. Potom postupne zad\u00e1vam pr\u00edkazy switchport access vlan 10 a switchport voice vlan 50.<\/p>\n

Zabudol som nastavi\u0165 rovnak\u00fd re\u017eim VLAN pre trunk, preto prejdem k nastaveniam portu Ethernet 0\/0 a zad\u00e1m pr\u00edkaz switchport trunk native vlan 1. Teraz po\u017eiadam, aby sa zobrazili parametre VLAN, a vid\u00edte, \u017ee teraz na porte Ethernet 0\/1 m\u00e1me obe siete \u2013 VLAN 50 a VLAN20.<\/p>\n

\"\u0160kolenie
\n
\nAk vid\u00edte, \u017ee na jednom porte s\u00fa umiestnen\u00e9 dve VLAN, znamen\u00e1 to, \u017ee jedna z nich je hlasov\u00e1 sie\u0165 Voice VLAN. Nem\u00f4\u017ee to by\u0165 trunk, preto\u017ee ak sa pozriete na nastavenia trunku pomocou pr\u00edkazu show int trunk, uvid\u00edte, \u017ee trunk-port obsahuje v\u0161etky VLAN siete vr\u00e1tane predvolenej siete VLAN1. <\/p>\n

\"\u0160kolenie
\n
\nTechnicky povedan\u00e9, ke\u010f vytv\u00e1rate d\u00e1tov\u00fa sie\u0165 a hlasov\u00fa sie\u0165, ka\u017ed\u00fd z t\u00fdchto portov sa spr\u00e1va ako polotrunk: pre jednu sie\u0165 funguje ako trunk, pre druh\u00fa ako access-port. <\/p>\n

Ak zad\u00e1te pr\u00edkaz show int e0\/1 switchport, m\u00f4\u017eete vidie\u0165, \u017ee niektor\u00e9 charakteristiky vyhovuj\u00fa dvom re\u017eimom fungovania: m\u00e1me statick\u00fd access aj inkapsul\u00e1ciu trunkovania. Tento re\u017eim access mode zodpoved\u00e1 d\u00e1tovej sieti VLAN 20 Management a z\u00e1rove\u0148 je pr\u00edtomn\u00e1 hlasov\u00e1 sie\u0165 VLAN 50. <\/p>\n

\"\u0160kolenie
\n
\nM\u00f4\u017eete sa pozrie\u0165 na aktu\u00e1lnu konfigur\u00e1ciu, ktor\u00e1 tie\u017e uk\u00e1\u017ee, \u017ee na danom porte s\u00fa pr\u00edtomn\u00e9 siete access vlan 20 a voice vlan 50. <\/p>\n

\"\u0160kolenie
\n
\nTu spo\u010d\u00edva rozdiel medzi sie\u0165ami Data VLAN a Voice VLAN. D\u00fafam, \u017ee ste pochopili v\u0161etko, o \u010dom som hovoril; ak nie, jednoducho si tento video kurz pozrite znova. <\/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":"

\u041c\u044b \u0443\u0436\u0435 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u043b\u0438 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u044b\u0435 \u0441\u0435\u0442\u0438 VLAN \u0432 \u0432\u0438\u0434\u0435\u043e\u0443\u0440\u043e\u043a\u0430\u0445 \u0414\u0435\u043d\u044c 11, 12 \u0438 13 \u0438 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0438\u043c \u0438\u0445 \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u0435 \u0432 \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0438\u0438 \u0441 \u0442\u0435\u043c\u0430\u0442\u0438\u043a\u043e\u0439 ICND2. \u042f \u0437\u0430\u043f\u0438\u0441\u0430\u043b \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0435 \u0432\u0438\u0434\u0435\u043e, \u043a\u043e\u0442\u043e\u0440\u043e\u0435 \u043e\u0437\u043d\u0430\u043c\u0435\u043d\u043e\u0432\u0430\u043b\u043e \u043e\u043a\u043e\u043d\u0447\u0430\u043d\u0438\u0435 \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u043a\u0438 \u043a \u0441\u0434\u0430\u0447\u0435 \u044d\u043a\u0437\u0430\u043c\u0435\u043d\u0430 ICND1, \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043c\u0435\u0441\u044f\u0446\u0435\u0432 \u043d\u0430\u0437\u0430\u0434 \u0438 \u0432\u0441\u0435 \u044d\u0442\u043e \u0432\u0440\u0435\u043c\u044f \u0434\u043e \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0433\u043e \u0434\u043d\u044f \u0431\u044b\u043b \u043e\u0447\u0435\u043d\u044c \u0437\u0430\u043d\u044f\u0442. \u0414\u0443\u043c\u0430\u044e, \u043c\u043d\u043e\u0433\u0438\u0435 \u0438\u0437 \u0432\u0430\u0441 \u0443\u0441\u043f\u0435\u0448\u043d\u043e \u0441\u0434\u0430\u043b\u0438 \u044d\u0442\u043e\u0442 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28433,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37888","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\udd47Tr\u00e9ning Cisco 200-125 CCNA v3.0. De\u0148 34. Roz\u0161\u00edren\u00e1 koncepcia VLAN | ProHoster","description":"U\u017e sme sa zaoberali lok\u00e1lnymi sie\u0165ami VLAN vo video kurzoch De\u0148 11, 12 a 13 a dnes budeme pokra\u010dova\u0165 v ich \u0161t\u00fadiu v s\u00falade s t\u00e9mou ICND2.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-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 34. \u0420\u0430\u0441\u0448\u0438\u0440\u0435\u043d\u043d\u0430\u044f \u043a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f VLAN | ProHoster","og:description":"\u041c\u044b \u0443\u0436\u0435 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u043b\u0438 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u044b\u0435 \u0441\u0435\u0442\u0438 VLAN \u0432 \u0432\u0438\u0434\u0435\u043e\u0443\u0440\u043e\u043a\u0430\u0445 \u0414\u0435\u043d\u044c 11, 12 \u0438 13 \u0438 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0438\u043c \u0438\u0445 \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u0435 \u0432 \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0438\u0438 \u0441 \u0442\u0435\u043c\u0430\u0442\u0438\u043a\u043e\u0439 ICND2.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-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:20:23+00:00","article:modified_time":"2019-10-31T19:20:23+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37888","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 19:38:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:19:21","updated":"2026-01-23 19:38:19","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\/37888","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=37888"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/37888\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/28433"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=37888"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=37888"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=37888"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}