{"id":37940,"date":"2019-10-31T22:20:41","date_gmt":"2019-10-31T19:20:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp\/"},"modified":"2019-10-31T22:20:41","modified_gmt":"2019-10-31T19:20:41","slug":"trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp","title":{"rendered":"\u0160kolenie Cisco 200-125 CCNA v3.0. De\u0148 35. Dynamick\u00fd protokol trunkovania DTP","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dnes sa pozrieme na dynamick\u00fd protokol trunkovania DTP a VTP \u2013 protokol trunkovania VLAN. Ako som povedal na poslednej hodine, budeme sledova\u0165 t\u00e9my sk\u00fa\u0161ky ICND2 v porad\u00ed, v akom s\u00fa uveden\u00e9 na str\u00e1nke Cisco.<\/p>\n

\"\u0160kolenie
\n
\nMinul\u00fd raz sme sa zaoberali bodom 1.1, a dnes sa pozrieme na 1.2 \u2013 konfigur\u00e1cia, overovanie a rie\u0161enie probl\u00e9mov s pripojeniami sie\u0165ov\u00fdch prep\u00edna\u010dov: prid\u00e1vanie a odstra\u0148ovanie VLAN z trunku a protokoly DTP a VTP verzi\u00ed 1 a 2.<\/a><\/noindex><\/p>\n

V\u0161etky porty prep\u00edna\u010da s\u00fa \u201ez krabice\u201c predvolene nastaven\u00e9 na pou\u017e\u00edvanie re\u017eimu Dynamic Auto protokolu DTP. To znamen\u00e1, \u017ee pri pripojen\u00ed dvoch portov r\u00f4znych prep\u00edna\u010dov sa medzi nimi automaticky vytvor\u00ed trunk, ak je jeden z portov v re\u017eime trunk alebo desirable. Ak s\u00fa porty oboch prep\u00edna\u010dov v re\u017eime Dynamic Auto, trunk sa nevytvor\u00ed. <\/p>\n

\"\u0160kolenie
\n
\nTak\u017ee v\u0161etko z\u00e1vis\u00ed od nastavenia re\u017eimov pr\u00e1ce ka\u017ed\u00e9ho z 2 prep\u00edna\u010dov. Pre pohodlie porozumenia som vypracoval tabu\u013eku mo\u017en\u00fdch kombin\u00e1ci\u00ed re\u017eimov DTP dvoch prep\u00edna\u010dov. Vid\u00edte, \u017ee ak oba prep\u00edna\u010de pou\u017e\u00edvaj\u00fa Dynamic Auto, nevytv\u00e1raj\u00fa trunk a zost\u00e1vaj\u00fa v re\u017eime Access. Preto ak chcete, aby medzi dvoma prep\u00edna\u010dmi bol vytvoren\u00fd trunk, mus\u00edte naprogramova\u0165 aspo\u0148 jeden z prep\u00edna\u010dov do re\u017eimu Trunk, alebo naprogramova\u0165 trunk-port na pou\u017eitie re\u017eimu Dynamic Desirable. Ako vidno z tabu\u013eky, ka\u017ed\u00fd z portov prep\u00edna\u010da m\u00f4\u017ee by\u0165 v jednom zo 4 re\u017eimov: Access, Dynamic Auto, Dynamic Desirable alebo Trunk. <\/p>\n

Ak s\u00fa oba porty nastaven\u00e9 na Access, pripojen\u00e9 prep\u00edna\u010de bud\u00fa pou\u017e\u00edva\u0165 re\u017eim Access. Ak je jeden port nastaven\u00fd na Dynamic Auto a druh\u00fd na Access, oba bud\u00fa fungova\u0165 v re\u017eime Access. Ak je jeden port v re\u017eime Access a druh\u00fd v re\u017eime Trunk, prepoji\u0165 prep\u00edna\u010de sa nepodar\u00ed, tak\u017ee tak\u00fato kombin\u00e1ciu re\u017eimov nemo\u017eno pou\u017ei\u0165. <\/p>\n

Tak\u017ee na spr\u00e1vnu funkciu trunkovania je potrebn\u00e9, aby jeden z portov prep\u00edna\u010dov bol naprogramovan\u00fd na Trunk a druh\u00fd \u2013 na Trunk, Dynamic Auto alebo Dynamic Desirable. Trunk sa vytvor\u00ed aj v pr\u00edpade, ak s\u00fa oba porty nastaven\u00e9 na Dynamic Desirable. <\/p>\n

Rozdiel medzi Dynamic Desirable a Dynamic Auto spo\u010d\u00edva v tom, \u017ee v prvom re\u017eime port iniciuje trunk, a to odosielan\u00edm DTP r\u00e1mcov portu druh\u00e9ho prep\u00edna\u010da. V druhom re\u017eime port prep\u00edna\u010da \u010dak\u00e1, k\u00fdm sa niekto neza\u010dne s n\u00edm komunikova\u0165, a ak s\u00fa porty oboch prep\u00edna\u010dov nastaven\u00e9 na Dynamic Auto, medzi nimi nikdy nevznikne trunk. V pr\u00edpade Dynamic Desirable je situ\u00e1cia opa\u010dn\u00e1 \u2013 ak s\u00fa oba porty nastaven\u00e9 na tento re\u017eim, medzi nimi sa trunk ur\u010dite vytvor\u00ed. <\/p>\n

Odpor\u00fa\u010dam v\u00e1m zapam\u00e4ta\u0165 si t\u00fato tabu\u013eku, preto\u017ee v\u00e1m pom\u00f4\u017ee spr\u00e1vne nastavi\u0165 prep\u00edna\u010de, ktor\u00e9 s\u00fa navz\u00e1jom prepojen\u00e9. Pozrime sa na tento aspekt v programe Packet Tracer. Postupne som prepojil 3 prep\u00edna\u010de a teraz zobraz\u00edm na obrazovke okn\u00e1 konzoly CLI pre ka\u017ed\u00fd z t\u00fdchto zariaden\u00ed. <\/p>\n

\"\u0160kolenie
\n
\nAk zad\u00e1m pr\u00edkaz show int trunk, neuvid\u00edme \u017eiadny trunk, \u010do je \u00faplne prirodzen\u00e9 v pr\u00edpade ch\u00fdbaj\u00facich potrebn\u00fdch nastaven\u00ed, ke\u010f\u017ee v\u0161etky prep\u00edna\u010de s\u00fa nastaven\u00e9 na re\u017eim Dynamic Auto. Ak po\u017eiadam o zobrazenie parametrov rozhrania f0\/1 stredn\u00e9ho prep\u00edna\u010da, uvid\u00edte, \u017ee v re\u017eime administrat\u00edvneho nastavenia je uveden\u00fd parameter dynamic auto.<\/p>\n

\"\u0160kolenie
\n
\nPodobn\u00e9 nastavenia m\u00e1 aj tret\u00ed a prv\u00fd prep\u00edna\u010d \u2013 port f0\/1 m\u00e1 tie\u017e re\u017eim dynamic auto. Ak si pam\u00e4t\u00e1te tabu\u013eku, na trunkovanie musia by\u0165 v\u0161etky porty nastaven\u00e9 na re\u017eim trunk alebo aspo\u0148 jeden z portov mus\u00ed by\u0165 v re\u017eime Dynamic Desirable. <\/p>\n

Po\u010fme sa pozrie\u0165 do nastaven\u00ed prv\u00e9ho prep\u00edna\u010da SW0 a nastavme port f0\/1. Po zadan\u00ed pr\u00edkazu switchport mode syst\u00e9m poskytne n\u00e1vrhy mo\u017en\u00fdch parametrov re\u017eimu: access, dynamic alebo trunk. Pou\u017e\u00edvam pr\u00edkaz switchport mode dynamic desirable, pri\u010dom si m\u00f4\u017eete v\u0161imn\u00fa\u0165, ako trunk-port f0\/1 druh\u00e9ho prep\u00edna\u010da po zadan\u00ed tohto pr\u00edkazu najprv pre\u0161iel do stavu down a potom, po prijat\u00ed r\u00e1mca DTP prv\u00e9ho prep\u00edna\u010da, pre\u0161iel do stavu up. <\/p>\n

\"\u0160kolenie
\n
\nAk teraz v konzole CLI prep\u00edna\u010da SW1 zadajte pr\u00edkaz show int trunk, uvid\u00edme, \u017ee port f0\/1 je v stave trunkovania. Zadajem ten ist\u00fd pr\u00edkaz v konzole prep\u00edna\u010da SW1 a vid\u00edm t\u00fa ist\u00fa inform\u00e1ciu, to znamen\u00e1, \u017ee teraz je medzi prep\u00edna\u010dmi SW0 a SW1 vytvoren\u00fd trunk. Pri\u010dom port prv\u00e9ho prep\u00edna\u010da je v re\u017eime desirable a port druh\u00e9ho v re\u017eime auto. <\/p>\n

\"\u0160kolenie
\n
\nMedzi druh\u00fdm a tret\u00edm prep\u00edna\u010dom nie je \u017eiadne spojenie, preto prech\u00e1dzam do nastaven\u00ed tretieho prep\u00edna\u010da a zad\u00e1vam pr\u00edkaz switchport mode dynamic desirable. Vid\u00edte, \u017ee v druhom prep\u00edna\u010di do\u0161lo k rovnak\u00fdm zmen\u00e1m stavu down-up, len teraz sa t\u00fdkaj\u00fa portu f0\/2, ku ktor\u00e9mu je pripojen\u00fd tret\u00ed prep\u00edna\u010d. Teraz m\u00e1 druh\u00fd prep\u00edna\u010d dva trunky: jeden na rozhran\u00ed f0\/1, druh\u00fd na f0\/2. M\u00f4\u017eete to vidie\u0165, ak pou\u017eijete pr\u00edkaz show int trunk. <\/p>\n

\"\u0160kolenie
\n
\nObe porty druh\u00e9ho prep\u00edna\u010da s\u00fa v stave auto, to znamen\u00e1, \u017ee na trunkovanie so susedn\u00fdmi prep\u00edna\u010dmi je potrebn\u00e9, aby ich porty boli v re\u017eime trunk alebo desirable, preto\u017ee v tomto pr\u00edpade existuj\u00fa iba 2 re\u017eimy na nastavenie trunku. Pomocou tabu\u013eky m\u00f4\u017eete v\u017edy nastavi\u0165 porty prep\u00edna\u010dov tak, aby ste medzi nimi vytvorili trunk. O tom je podstata pou\u017eitia dynamick\u00e9ho protokolu trunkovania DTP. <\/p>\n

Po\u010fme sa pozrie\u0165 na protokol trunkovania VLAN, alebo VTP. Tento protokol zabezpe\u010duje synchroniz\u00e1ciu datab\u00e1z VLAN r\u00f4znych sie\u0165ov\u00fdch zariaden\u00ed, pri\u010dom pren\u00e1\u0161a aktualizovan\u00fa datab\u00e1zu VLAN z jedn\u00e9ho zariadenia na druh\u00e9. Vr\u00e1\u0165me sa k na\u0161ej sch\u00e9me zo 3 prep\u00edna\u010dov. VTP m\u00f4\u017ee pracova\u0165 v 3 re\u017eimoch: server, klient a transparentn\u00fd. VTP v3 m\u00e1 e\u0161te jeden re\u017eim nazvan\u00fd Off, av\u0161ak v t\u00e9me sk\u00fa\u0161ky Cisco sa sk\u00fama iba VTP prvej a druhej verzie. <\/p>\n

\"\u0160kolenie
\n
\nRe\u017eim server sa pou\u017e\u00edva na vytv\u00e1ranie nov\u00fdch VLAN, ich odstra\u0148ovanie alebo \u00fapravy siet\u00ed cez pr\u00edkazov\u00fd riadok prep\u00edna\u010da. V re\u017eime klienta nie je mo\u017en\u00e9 vykon\u00e1va\u0165 \u017eiadne oper\u00e1cie s VLAN, v tomto re\u017eime doch\u00e1dza iba k aktualiz\u00e1cii datab\u00e1zy VLAN zo servera. Re\u017eim transparentn\u00fd funguje tak, akoby bol protokol VTP vypnut\u00fd, to znamen\u00e1, \u017ee prep\u00edna\u010d nevyd\u00e1va vlastn\u00e9 spr\u00e1vy VTP, ale pren\u00e1\u0161a aktualiz\u00e1cie z in\u00fdch prep\u00edna\u010dov \u2013 ak aktualiz\u00e1cia pri\u0161la na jeden z portov prep\u00edna\u010da, prep\u00edna\u010d ju prepust\u00ed a po\u0161le \u010falej cez in\u00fd port. V transparentnom re\u017eime prep\u00edna\u010d jednoducho sl\u00fa\u017ei ako prena\u0161a\u010d cudz\u00edch spr\u00e1v, pri\u010dom neaktualizuje vlastn\u00fa datab\u00e1zu VLAN.
\nNa tomto slajde vid\u00edte pr\u00edkazy na nastavenie protokolu VTP, ktor\u00e9 sa zad\u00e1vaj\u00fa v re\u017eime glob\u00e1lnej konfigur\u00e1cie. Prv\u00fdm pr\u00edkazom m\u00f4\u017eete zmeni\u0165 pou\u017eit\u00fa verziu protokolu. Druh\u00fd pr\u00edkaz vyber\u00e1 re\u017eim \u010dinnosti VTP.<\/p>\n

\"\u0160kolenie
\n
\nAk chcete vytvori\u0165 VTP dom\u00e9nu, pou\u017eite pr\u00edkaz vtp domain , a na nastavenie VTP hesla zadajte pr\u00edkaz vtp password . Prejdime k CLI konzole prv\u00e9ho prep\u00edna\u010da a pozrime sa na stav VTP zadan\u00edm pr\u00edkazu show vtp status.<\/p>\n

\"\u0160kolenie
\n
\nVid\u00edte verziu protokolu VTP \u2013 druh\u00fa, maxim\u00e1lny po\u010det podporovan\u00fdch VLAN \u2013 255, po\u010det existuj\u00facich VLAN \u2013 5 a re\u017eim prev\u00e1dzky VLAN \u2013 server. Toto s\u00fa v\u0161etko predvolen\u00e9 parametre. U\u017e sme hovorili o VTP na lekcii \u201eDe\u0148 30\u201c, tak\u017ee ak ste nie\u010do zabudli, m\u00f4\u017eete sa vr\u00e1ti\u0165 a e\u0161te raz si pozrie\u0165 toto video. <\/p>\n

Aby som videl datab\u00e1zu VLAN, zad\u00e1vam pr\u00edkaz show vlan brief. Tu s\u00fa zobrazen\u00e9 VLAN1 a VLAN1002-1005. K prvej sieti s\u00fa predvolene pripojen\u00e9 v\u0161etky vo\u013en\u00e9 rozhrania prep\u00edna\u010da \u2013 23 porty Fast Ethernet a 2 porty Gigabit Ethernet, ostatn\u00e9 4 VLAN nie s\u00fa podporovan\u00e9. Datab\u00e1zy VLAN dvoch \u010fal\u0161\u00edch prep\u00edna\u010dov vyzeraj\u00fa presne rovnako, s v\u00fdnimkou toho, \u017ee na SW1 zostalo vo\u013en\u00fdch pre VLAN nie 23, ale 22 portov Fast Ethernet, preto\u017ee f0\/1 a f0\/2 s\u00fa obsaden\u00e9 trunkami. E\u0161te raz pripom\u00ednam, o \u010dom sme hovorili na lekcii \u201eDe\u0148 30\u201c \u2013 protokol VTP podporuje iba aktualiz\u00e1ciu datab\u00e1z VLAN. <\/p>\n

Tak\u017ee ak nastav\u00edm nieko\u013eko portov na pr\u00e1cu so sie\u0165ami VLAN pr\u00edkazmi switchport access a switchport mode access VLAN10, VLAN20 alebo VLAN30, konfigur\u00e1cia t\u00fdchto portov nebude replikovan\u00e1 pomocou VTP, preto\u017ee VTP aktualizuje iba datab\u00e1zu VLAN.
\nAk teda bude jeden z portov SW1 nastaven\u00fd na pr\u00e1cu s VLAN20, ale t\u00e1to sie\u0165 nebude v datab\u00e1ze VLAN, port bude deaktivovan\u00fd. Na druhej strane, aktualiz\u00e1cia datab\u00e1z prebieha iba pri pou\u017eit\u00ed protokolu VTP. <\/p>\n

Pomocou pr\u00edkazu show vtp status vid\u00edm, \u017ee v\u0161etky 3 prep\u00edna\u010de s\u00fa teraz v re\u017eime server. Prevediem stredn\u00fd prep\u00edna\u010d SW1 do transparentn\u00e9ho re\u017eimu pr\u00edkazom vtp mode transparent a tret\u00ed prep\u00edna\u010d SW2 do re\u017eimu klienta pr\u00edkazom vtp mode client. <\/p>\n

Teraz sa vr\u00e1\u0165me k prv\u00e9mu prep\u00edna\u010du SW0 a vytvorme dom\u00e9nu nwking.org pomocou pr\u00edkazu vtp domain . Ak sa teraz pozrieme na stav VTP druh\u00e9ho prep\u00edna\u010da, ktor\u00fd je v transparentnom re\u017eime, vid\u00edme, \u017ee nijako nereagoval na vytvorenie dom\u00e9ny \u2013 pole VTP Domain Name zostalo pr\u00e1zdne. Av\u0161ak tret\u00ed prep\u00edna\u010d, ktor\u00fd je v re\u017eime klienta, aktualizoval svoju datab\u00e1zu a m\u00e1 dom\u00e9nov\u00e9 meno VTP - nwking.org. Tak\u017ee, aktualiz\u00e1cia datab\u00e1zy prep\u00edna\u010da SW0 pre\u0161la cez SW1 a odrazila sa na SW2. <\/p>\n

Teraz sa pok\u00fasim zmeni\u0165 zadan\u00e9 dom\u00e9nov\u00e9 meno, na \u010do sa prihl\u00e1sim do nastaven\u00ed SW0 a zad\u00e1m pr\u00edkaz vtp domain NetworKing. Ako vid\u00edme, tentokr\u00e1t nedo\u0161lo k aktualiz\u00e1cii - dom\u00e9nov\u00e9 meno VTP na tre\u0165om prep\u00edna\u010di zostalo rovnak\u00e9. D\u00f4vodom je, \u017ee toto aktualizovanie dom\u00e9nov\u00e9ho mena nast\u00e1va iba raz, ke\u010f sa men\u00ed dom\u00e9na predvolene. Ak sa po tom dom\u00e9nov\u00e9 meno VTP men\u00ed e\u0161te raz, na ostatn\u00fdch prep\u00edna\u010doch ho bude potrebn\u00e9 zmeni\u0165 manu\u00e1lne. <\/p>\n

Teraz v konzole CLI prv\u00e9ho prep\u00edna\u010da vytvor\u00edm nov\u00fa sie\u0165 VLAN100 a nazvem ju menom IMRAN. Objavila sa v datab\u00e1ze VLAN prv\u00e9ho prep\u00edna\u010da, ale neobjavila sa v datab\u00e1ze tretieho prep\u00edna\u010da, preto\u017ee ide o r\u00f4zne dom\u00e9ny. Zapam\u00e4tajte si, \u017ee aktualiz\u00e1cia datab\u00e1zy VLAN nast\u00e1va len v pr\u00edpade, ak oba prep\u00edna\u010de maj\u00fa rovnak\u00fa dom\u00e9nu, alebo, ako som u\u017e uk\u00e1zal, ak sa nov\u00e9 dom\u00e9nov\u00e9 meno nastav\u00ed namiesto mena predvolene. <\/p>\n

Prejdem do nastaven\u00ed 3. prep\u00edna\u010da a postupne zad\u00e1m pr\u00edkazy vtp mode a vtp domain NetworKing. V\u0161imnite si, \u017ee zad\u00e1vanie mena je citliv\u00e9 na ve\u013ek\u00e9 p\u00edsmen\u00e1, tak\u017ee p\u00edsanie dom\u00e9nov\u00e9ho mena mus\u00ed presne zodpoveda\u0165 pre oba prep\u00edna\u010de. Teraz znova prech\u00e1dzam SW2 do re\u017eimu klienta pomocou pr\u00edkazu vtp mode client. Pozrime sa, \u010do sa stane. Ako vid\u00edte, teraz, pri zhode dom\u00e9nov\u00e9ho mena, sa datab\u00e1za SW2 aktualizovala a objavila sa v nej nov\u00e1 sie\u0165 VLAN100 IMRAN; tieto zmeny sa nijako neodrazili na strednom prep\u00edna\u010di, preto\u017ee sa nach\u00e1dza v re\u017eime transparent. <\/p>\n

Ak sa chcete ochr\u00e1ni\u0165 pred neopr\u00e1vnen\u00fdm pr\u00edstupom, m\u00f4\u017eete vytvori\u0165 heslo VTP. Malo by v\u0161ak by\u0165 zabezpe\u010den\u00e9, \u017ee zariadenie na druhej strane bude ma\u0165 presne tak\u00e9 ist\u00e9 heslo, preto\u017ee len v tomto pr\u00edpade bude m\u00f4c\u0165 prij\u00edma\u0165 aktualiz\u00e1cie VTP. <\/p>\n

\u010eal\u0161ou z\u00e1le\u017eitos\u0165ou, ktor\u00fa zv\u00e1\u017eime, je VTP pruning, alebo 'rezanie' nepou\u017e\u00edvan\u00fdch VLAN. Ak m\u00e1te v sieti 100 zariaden\u00ed pou\u017e\u00edvaj\u00facich protokol VTP, automaticky sa replikuje aktualiz\u00e1cia datab\u00e1zy VLAN jedn\u00e9ho zariadenia na ostatn\u00fdch 99 zariadeniach. Av\u0161ak nie v\u0161etky tieto zariadenia maj\u00fa siete VLAN spomenut\u00e9 v aktualiz\u00e1cii, preto m\u00f4\u017ee by\u0165 inform\u00e1cia o nich nepotrebn\u00e1. <\/p>\n

\"\u0160kolenie<\/p>\n

Odkaz na aktualiz\u00e1cie datab\u00e1zy VLAN pre zariadenia pou\u017e\u00edvaj\u00face VTP znamen\u00e1, \u017ee v\u0161etky porty v\u0161etk\u00fdch zariaden\u00ed dostan\u00fa inform\u00e1cie o pridan\u00fdch, odstr\u00e1nen\u00fdch a zmenen\u00fdch VLAN, na ktor\u00e9 nemusia ma\u0165 nijak\u00fd vz\u0165ah. Pri tom sa sie\u0165 zap\u013a\u0148a zbyto\u010dn\u00fdm prenosom. Aby sa tomu predi\u0161lo, pou\u017e\u00edva sa koncept \u201eprerez\u00e1vania\u201c VTP. Na to, aby sa na prep\u00edna\u010di aktivoval re\u017eim \u201eprerez\u00e1vania\u201c neaktu\u00e1lnych VLAN, sa pou\u017e\u00edva pr\u00edkaz vtp pruning. Po tomto bud\u00fa prep\u00edna\u010de automaticky informova\u0165 jeden druh\u00e9ho o tom, ktor\u00e9 VLAN skuto\u010dne pou\u017e\u00edvaj\u00fa, a t\u00fdm p\u00e1dom varova\u0165 susedov, \u017ee nemusia posiela\u0165 aktualiz\u00e1cie siet\u00ed, ktor\u00e9 nie s\u00fa k nim pripojen\u00e9.<\/p>\n

Napr\u00edklad, ak SW2 nem\u00e1 \u017eiadne porty VLAN10, nepotrebuje, aby mu SW1 posielal prenos pre t\u00fato sie\u0165. Z\u00e1rove\u0148 prep\u00edna\u010d SW1 potrebuje prenos VLAN10, preto\u017ee jeden z jeho portov je pripojen\u00fd k tejto sieti, iba mu nie je potrebn\u00e9 posiela\u0165 tento prenos prep\u00edna\u010du SW2.
\nPreto, ak SW2 pou\u017e\u00edva re\u017eim vtp pruning, informuje SW1: \u201epros\u00edm, neposielajte mi prenos pre VLAN10, preto\u017ee t\u00e1to sie\u0165 nie je pripojen\u00e1 a ani jeden z mojich portov nie je nastaven\u00fd na pr\u00e1cu s touto sie\u0165ou\u201c. Toto je v\u00fdhoda pou\u017e\u00edvania pr\u00edkazu vtp pruning. <\/p>\n

Existuje e\u0161te jeden sp\u00f4sob filtrovania prenosu pre konkr\u00e9tne rozhranie. Umo\u017e\u0148uje nastavi\u0165 port na trunk s konkr\u00e9tnou sie\u0165ou VLAN. Nev\u00fdhodou tohto sp\u00f4sobu je potreba manu\u00e1lneho nastavenia ka\u017ed\u00e9ho trunk portu, ktor\u00e9mu bude potrebn\u00e9 ur\u010di\u0165, ktor\u00e9 VLAN s\u00fa povolen\u00e9 a ktor\u00e9 zak\u00e1zan\u00e9. Na to sa pou\u017e\u00edva sekvencia 3 pr\u00edkazov. Prv\u00fd uv\u00e1dza rozhranie, ktor\u00e9ho sa tieto obmedzenia t\u00fdkaj\u00fa, druh\u00fd men\u00ed toto rozhranie na trunk-port, a tret\u00ed \u2014 switchport trunk allowed vlan \u2014 ukazuje, ktor\u00e1 VLAN je na danom porte povolen\u00e1: v\u0161etky, \u017eiadna, prid\u00e1van\u00e1 VLAN alebo odstra\u0148ovan\u00e1 VLAN. <\/p>\n

V z\u00e1vislosti od konkr\u00e9tnej situ\u00e1cie si vyber\u00e1te, \u010do pou\u017ei\u0165: VTP pruning alebo Trunk allowed. Niektor\u00e9 organiz\u00e1cie uprednost\u0148uj\u00fa nepou\u017e\u00edva\u0165 VTP z bezpe\u010dnostn\u00fdch d\u00f4vodov, a preto si vyberaj\u00fa manu\u00e1lne nastavenie trunkingu. Ke\u010f\u017ee pr\u00edkaz vtp pruning nefunguje v Packet Tracer, uk\u00e1\u017eem ho v emul\u00e1tor GNS3. <\/p>\n

Ak sa dostanete do nastaven\u00ed SW2 a zad\u00e1te pr\u00edkaz vtp pruning, syst\u00e9m okam\u017eite ozn\u00e1mi, \u017ee tento re\u017eim je zapnut\u00fd: Pruning switched on, teda \u201eobrez\u00e1vanie\u201c VLAN sa aktivuje jedn\u00fdm pr\u00edkazom. <\/p>\n

Ak zad\u00e1te pr\u00edkaz show vtp status, uvid\u00edme, \u017ee re\u017eim vtp pruning je povolen\u00fd. <\/p>\n

\"\u0160kolenie
\n
\nAk nastavujete tento re\u017eim na switchi-serveri, prejdite do jeho nastaven\u00ed a zadajte pr\u00edkaz vtp pruning. To znamen\u00e1, \u017ee pripojen\u00e9 zariadenia k serveru za\u010dn\u00fa automaticky pou\u017e\u00edva\u0165 vtp pruning, aby minimalizovali prenos transakci\u00ed pre neaktu\u00e1lne VLAN. <\/p>\n

Ak nechcete pou\u017e\u00edva\u0165 tento re\u017eim, mus\u00edte vojs\u0165 do konkr\u00e9tneho rozhrania, napr\u00edklad e0\/0, a potom zada\u0165 pr\u00edkaz switchport trunk allowed vlan. Syst\u00e9m v\u00e1m poskytne n\u00e1povede mo\u017en\u00fdch parametrov tohto pr\u00edkazu: <\/p>\n

\u2014 WORD \u2014 \u010d\u00edslo VLAN, ktor\u00e1 bude povolen\u00e1 na tomto rozhran\u00ed v re\u017eime trunk;
\n \u2014 add \u2014 VLAN, ktor\u00fa treba prida\u0165 do zoznamu datab\u00e1zy VLAN;
\n \u2014 all \u2014 povoli\u0165 v\u0161etky VLAN;
\n \u2014 except \u2014 povoli\u0165 v\u0161etky VLAN, okrem uveden\u00fdch;
\n \u2014 none \u2013 zak\u00e1za\u0165 v\u0161etky VLAN;
\n \u2014 remove \u2013 odstr\u00e1ni\u0165 VLAN zo zoznamu datab\u00e1zy VLAN. <\/p>\n

Napr\u00edklad, ak m\u00e1me povolen\u00fd trunk pre VLAN10 a chceme ho povoli\u0165 pre sie\u0165 VLAN20, mus\u00edme zada\u0165 pr\u00edkaz switchport trunk allowed vlan add 20. <\/p>\n

\"\u0160kolenie
\n
\nChcem v\u00e1m uk\u00e1za\u0165 e\u0161te nie\u010do, preto pou\u017eijem pr\u00edkaz show interface trunk. V\u0161imnite si, \u017ee predvolene boli pre trunk povolen\u00e9 v\u0161etky VLAN 1-1005, a teraz sa k nim pridala aj VLAN10. <\/p>\n

\"\u0160kolenie
\n
\nAk pou\u017eijem pr\u00edkaz switchport trunk allowed vlan add 20 a znova po\u017eiadam o zobrazenie stavu trunkovania, uvid\u00edme, \u017ee teraz s\u00fa pre trunk povolen\u00e9 dve siete \u2013 VLAN10 a VLAN20. <\/p>\n

\"\u0160kolenie
\n
\nPri tom \u017eiaden in\u00fd prenos, okrem ur\u010den\u00e9ho pre dan\u00e9 siete, nem\u00f4\u017ee prech\u00e1dza\u0165 cez tento trunk. Povolen\u00edm prenosu iba pre VLAN 10 a VLAN 20 sme zak\u00e1zali prenos pre v\u0161etky ostatn\u00e9 VLAN. Takto je mo\u017en\u00e9 manu\u00e1lne nastavi\u0165 parametre trunkovania pre konkr\u00e9tnu VLAN na konkr\u00e9tnom rozhran\u00ed switche. <\/p>\n

V\u0161imnite si, \u017ee do konca d\u0148a 17. novembra 2017 m\u00e1me na na\u0161ej str\u00e1nke z\u013eavu 90% na cenu s\u0165ahovania laborat\u00f3rnej pr\u00e1ce na t\u00fato t\u00e9mu. <\/p>\n

\"\u0160kolenie
\n
\n\u010eakujem za pozornos\u0165 a te\u0161\u00edm sa na stretnutie na \u010fal\u0161om video kurze!<\/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 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 DTP \u0438 VTP \u2013 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 VLAN. \u041a\u0430\u043a \u044f \u0433\u043e\u0432\u043e\u0440\u0438\u043b \u043d\u0430 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0435\u043c \u0443\u0440\u043e\u043a\u0435, \u043c\u044b \u0431\u0443\u0434\u0435\u043c \u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u044c \u0442\u0435\u043c\u0430\u043c \u044d\u043a\u0437\u0430\u043c\u0435\u043d\u0430 ICND2 \u0432 \u0442\u043e\u043c \u043f\u043e\u0440\u044f\u0434\u043a\u0435, \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u043e\u043d\u0438 \u043f\u0440\u0438\u0432\u0435\u0434\u0435\u043d\u044b \u043d\u0430 \u0441\u0430\u0439\u0442\u0435 Cisco. \u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0439 \u0440\u0430\u0437 \u043c\u044b \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043b\u0438 \u043f\u0443\u043d\u043a\u0442 1.1, \u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c 1.2 \u2013 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430, \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u0438 \u043d\u0435\u043f\u043e\u043b\u0430\u0434\u043a\u0438 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0439 \u0441\u0435\u0442\u0435\u0432\u044b\u0445 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u043e\u0432: \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u0435 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28471,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37940","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 35. Dynamick\u00fd protokol trunkingu DTP | ProHoster","description":"Dnes sa pozrieme na dynamick\u00fd protokol trunkingu DTP a VTP \u2013 protokol trunkingu VLAN.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp","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 35. \u0414\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 DTP | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 DTP \u0438 VTP \u2013 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 VLAN.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp","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:41+00:00","article:modified_time":"2019-10-31T19:20:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37940","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:51:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:18:22","updated":"2026-01-23 19:51: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\/37940","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=37940"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/37940\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/28471"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=37940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=37940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=37940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}