{"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\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp","title":{"rendered":"Tr\u00e9nink Cisco 200-125 CCNA v3.0. Den 35. Dynamick\u00fd protokol trunkingu DTP","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dnes se pod\u00edv\u00e1me na dynamick\u00fd trunkovac\u00ed protokol DTP a VTP \u2013 protokol trunkov\u00e1n\u00ed VLAN. Jak jsem uvedl v posledn\u00ed lekci, budeme se \u0159\u00eddit t\u00e9maty zkou\u0161ky ICND2 v po\u0159ad\u00ed, jak jsou uvedena na str\u00e1nk\u00e1ch Cisco.<\/p>\n

\"Tr\u00e9nink
\n
\nMinule jsme probrali bod 1.1, a dnes se zam\u011b\u0159\u00edme na 1.2 \u2013 konfigurace, kontrola a odstra\u0148ov\u00e1n\u00ed probl\u00e9m\u016f s p\u0159ipojen\u00edm s\u00ed\u0165ov\u00fdch switch\u016f: p\u0159id\u00e1n\u00ed a odstran\u011bn\u00ed VLAN z trunku a protokoly DTP a VTP verze 1 a 2.<\/a><\/noindex><\/p>\n

V\u0161echny porty switche jsou \u201ez krabice\u201c ve v\u00fdchoz\u00edm nastaven\u00ed nastaveny na pou\u017e\u00edv\u00e1n\u00ed re\u017eimu Dynamic Auto protokolu DTP. To znamen\u00e1, \u017ee p\u0159i spojen\u00ed dvou port\u016f r\u016fzn\u00fdch switch\u016f se mezi nimi automaticky aktivuje trunk, pokud je jeden z port\u016f nastaven v re\u017eimu trunk nebo desirable. Pokud jsou porty obou switch\u016f nastaveny na re\u017eim Dynamic Auto, trunk se nevytvo\u0159\u00ed. <\/p>\n

\"Tr\u00e9nink
\n
\nZ toho vypl\u00fdv\u00e1, \u017ee v\u0161e z\u00e1vis\u00ed na nastaven\u00ed pracovn\u00edch re\u017eim\u016f ka\u017ed\u00e9ho z 2 switch\u016f. Pro lep\u0161\u00ed pochopen\u00ed jsem vytvo\u0159il tabulku mo\u017en\u00fdch kombinac\u00ed re\u017eim\u016f DTP dvou switch\u016f. Vid\u00edte, \u017ee pokud oba switche pou\u017e\u00edvaj\u00ed Dynamic Auto, nevytvo\u0159\u00ed trunk, ale z\u016fstanou v re\u017eimu Access. Proto pokud chcete, aby mezi dv\u011bma switchemi byl vytvo\u0159en trunk, mus\u00edte alespo\u0148 jeden ze switch\u016f nastavit na re\u017eim Trunk nebo nastavit trunkov\u00fd port na pou\u017eit\u00ed re\u017eimu Dynamic Desirable. Jak ukazuje tabulka, ka\u017ed\u00fd z port\u016f switche m\u016f\u017ee b\u00fdt v jednom ze 4 re\u017eim\u016f: Access, Dynamic Auto, Dynamic Desirable nebo Trunk. <\/p>\n

Pokud jsou oba porty nastaveny na Access, spojen\u00e9 switche budou pou\u017e\u00edvat re\u017eim Access. Pokud je jeden port nastaven na Dynamic Auto a druh\u00fd na Access, oba budou fungovat v re\u017eimu Access. Pokud jeden port pracuje v re\u017eimu Access a druh\u00fd v re\u017eimu Trunk, switche nebude mo\u017en\u00e9 propojit, proto tuto kombinaci re\u017eim\u016f nelze pou\u017e\u00edt. <\/p>\n

Tak\u017ee pro spr\u00e1vnou funkci trunkingu je nezbytn\u00e9, aby jeden z port\u016f switch\u016f byl nastaven na Trunk a druh\u00fd na Trunk, Dynamic Auto nebo Dynamic Desirable. Trunk se tak\u00e9 vytv\u00e1\u0159\u00ed, pokud jsou oba porty nastaveny na Dynamic Desirable. <\/p>\n

Rozd\u00edl mezi Dynamic Desirable a Dynamic Auto spo\u010d\u00edv\u00e1 v tom, \u017ee v prvn\u00edm re\u017eimu port s\u00e1m iniciuje trunk, odesl\u00e1n\u00edm DTP r\u00e1mc\u016f portu druh\u00e9ho switche. Ve druh\u00e9m re\u017eimu port switche \u010dek\u00e1, a\u017e n\u011bkdo za\u010dne komunikovat, a pokud jsou porty obou switch\u016f nastaveny na Dynamic Auto, mezi nimi nikdy nevznikne trunk. V p\u0159\u00edpad\u011b Dynamic Desirable je situace opa\u010dn\u00e1 \u2013 pokud jsou oba porty nastaveny na tento re\u017eim, mezi nimi se trunk v\u017edy vytvo\u0159\u00ed. <\/p>\n

Doporu\u010duji si tuto tabulku zapamatovat, proto\u017ee v\u00e1m pom\u016f\u017ee spr\u00e1vn\u011b nastavit switche navz\u00e1jem. Pod\u00edvejme se na tento aspekt v programu Packet Tracer. Postupn\u011b jsem spojil dohromady 3 switche a nyn\u00ed zobraz\u00edm na obrazovce okna konzol\u00ed CLI pro ka\u017ed\u00e9 z t\u011bchto za\u0159\u00edzen\u00ed. <\/p>\n

\"Tr\u00e9nink
\n
\nPokud zad\u00e1m p\u0159\u00edkaz show int trunk, neuvid\u00edme \u017e\u00e1dn\u00fd trunk, co\u017e je zcela p\u0159irozen\u00e9 p\u0159i absenci pot\u0159ebn\u00fdch nastaven\u00ed, proto\u017ee v\u0161echny switche jsou nastaveny na re\u017eim Dynamic Auto. Pokud v\u00e1s po\u017e\u00e1d\u00e1m, abyste zobrazili parametry rozhran\u00ed f0\/1 prost\u0159edn\u00edho switche, uvid\u00edte, \u017ee v re\u017eimu administrativn\u00edch nastaven\u00ed je uveden parametr dynamic auto.<\/p>\n

\"Tr\u00e9nink
\n
\nPodobn\u00e1 nastaven\u00ed maj\u00ed t\u0159et\u00ed a prvn\u00ed switche \u2013 port f0\/1 tak\u00e9 maj\u00ed v re\u017eimu dynamic auto. Pokud si pamatujete tabulku, pro trunkov\u00e1n\u00ed mus\u00ed b\u00fdt v\u0161echny porty v re\u017eimu trunk nebo jeden z port\u016f mus\u00ed b\u00fdt v re\u017eimu Dynamic Desirable. <\/p>\n

Poj\u010fme se pod\u00edvat do nastaven\u00ed prvn\u00edho switche SW0 a nastav\u00edme port f0\/1. Po zad\u00e1n\u00ed p\u0159\u00edkazu switchport mode syst\u00e9m zobraz\u00ed n\u00e1pov\u011bdu mo\u017en\u00fdch parametr\u016f re\u017eimu: access, dynamic nebo trunk. Pou\u017e\u00edv\u00e1m p\u0159\u00edkaz switchport mode dynamic desirable, p\u0159i\u010dem\u017e si m\u016f\u017eete v\u0161imnout, jak trunk-port f0\/1 druh\u00e9ho switche po zad\u00e1n\u00ed tohoto p\u0159\u00edkazu nejprve p\u0159e\u0161el do stavu down a pot\u00e9, po p\u0159ijet\u00ed DTP r\u00e1mce prvn\u00edho switche, p\u0159e\u0161el do stavu up. <\/p>\n

\"Tr\u00e9nink
\n
\nPokud nyn\u00ed v konzoli CLI switche SW1 zad\u00e1me p\u0159\u00edkaz show int trunk, uvid\u00edme, \u017ee port f0\/1 je v stavu trunkov\u00e1n\u00ed. Zad\u00e1v\u00e1m stejn\u00fd p\u0159\u00edkaz v konzoli switche SW1 a vid\u00edm stejn\u00e9 informace, tj. nyn\u00ed je mezi switche SW0 a SW1 nastaven trunk. P\u0159i\u010dem\u017e port prvn\u00edho switche je v re\u017eimu desirable a port druh\u00e9ho ve re\u017eimu auto. <\/p>\n

\"Tr\u00e9nink
\n
\nMezi druh\u00fdm a t\u0159et\u00edm switchem nen\u00ed \u017e\u00e1dn\u00e9 spojen\u00ed, proto p\u0159ech\u00e1z\u00edm do nastaven\u00ed t\u0159et\u00edho switche a zad\u00e1v\u00e1m p\u0159\u00edkaz switchport mode dynamic desirable. Vid\u00edte, \u017ee na druh\u00e9m switche do\u0161lo k t\u011bmto zm\u011bn\u00e1m stavu down-up, p\u0159i\u010dem\u017e se to nyn\u00ed t\u00fdk\u00e1 portu f0\/2, ke kter\u00e9mu je p\u0159ipojen t\u0159et\u00ed switch. Nyn\u00ed m\u00e1 druh\u00fd switch dva trunky: jeden na rozhran\u00ed f0\/1, druh\u00fd na f0\/2. To lze vid\u011bt, pokud pou\u017eijete p\u0159\u00edkaz show int trunk. <\/p>\n

\"Tr\u00e9nink
\n
\nOba porty druh\u00e9ho switche jsou v re\u017eimu auto, to znamen\u00e1, \u017ee pro trunking se sousedn\u00edmi switchemi je nutn\u00e9, aby jejich porty byly v re\u017eimu trunk nebo desirable, proto\u017ee v tomto p\u0159\u00edpad\u011b existuj\u00ed jen dva re\u017eimy pro nastaven\u00ed trunku. Pomoc\u00ed tabulky m\u016f\u017eete v\u017edy nakonfigurovat porty switch\u016f tak, aby byla mezi nimi zorganizov\u00e1na trunk. O tom je podstata pou\u017eit\u00ed dynamick\u00e9ho protokolu trunkingu DTP. <\/p>\n

Poj\u010fme se pod\u00edvat na protokol trunkingu VLAN, nebo VTP. Tento protokol zaji\u0161\u0165uje synchronizaci datab\u00e1z\u00ed VLAN r\u016fzn\u00fdch s\u00ed\u0165ov\u00fdch za\u0159\u00edzen\u00ed t\u00edm, \u017ee p\u0159en\u00e1\u0161\u00ed aktualizovanou datab\u00e1zi VLAN z jednoho za\u0159\u00edzen\u00ed na jin\u00e9. Vra\u0165me se k na\u0161\u00ed sch\u00e9m\u011b se t\u0159emi switchemi. VTP m\u016f\u017ee fungovat ve t\u0159ech re\u017eimech: server, klient a transparentn\u00ed. VTP v3 m\u00e1 je\u0161t\u011b jeden re\u017eim nazvan\u00fd Off, av\u0161ak v t\u00e9matu zkou\u0161ky Cisco se zva\u017euj\u00ed pouze verze VTP prvn\u00ed a druh\u00e9. <\/p>\n

\"Tr\u00e9nink
\n
\nRe\u017eim Server se pou\u017e\u00edv\u00e1 k vytv\u00e1\u0159en\u00ed nov\u00fdch VLAN, odstra\u0148ov\u00e1n\u00ed nebo m\u011bn\u011bn\u00ed s\u00edt\u00ed prost\u0159ednictv\u00edm p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku switche. V klientsk\u00e9m re\u017eimu nelze prov\u00e1d\u011bt \u017e\u00e1dn\u00e9 operace s VLAN, v tomto re\u017eimu doch\u00e1z\u00ed pouze k aktualizaci datab\u00e1ze VLAN ze serveru. Re\u017eim transparentn\u00ed funguje tak, jako by byl protokol VTP vypnut\u00fd, to znamen\u00e1, \u017ee switch nevyd\u00e1v\u00e1 vlastn\u00ed zpr\u00e1vy VTP, ale p\u0159en\u00e1\u0161\u00ed aktualizace od jin\u00fdch switch\u016f \u2013 pokud aktualizace doraz\u00ed na jeden z port\u016f switche, p\u0159ed\u00e1v\u00e1 ji d\u00e1l po s\u00edti p\u0159es jin\u00fd port. V transparentn\u00edm re\u017eimu switch pouze slou\u017e\u00ed jako p\u0159ena\u0161e\u010d ciz\u00edch zpr\u00e1v, ani\u017e by aktualizoval svou vlastn\u00ed datab\u00e1zi VLAN.
\nNa tomto sn\u00edmku vid\u00edte p\u0159\u00edkazy pro nastaven\u00ed protokolu VTP, kter\u00e9 se zad\u00e1vaj\u00ed v re\u017eimu glob\u00e1ln\u00ed konfigurace. Prvn\u00edm p\u0159\u00edkazem lze zm\u011bnit pou\u017e\u00edvanou verzi protokolu. Druh\u00fd p\u0159\u00edkaz vyb\u00edr\u00e1 re\u017eim pr\u00e1ce VTP.<\/p>\n

\"Tr\u00e9nink
\n
\nPokud chcete vytvo\u0159it VTP dom\u00e9nu, pou\u017eijte p\u0159\u00edkaz vtp domain , a pro nastaven\u00ed VTP hesla je t\u0159eba zadat p\u0159\u00edkaz vtp password . P\u0159ejdeme k CLI konzoli prvn\u00edho switche a pod\u00edv\u00e1me se na stav VTP zad\u00e1n\u00edm p\u0159\u00edkazu show vtp status.<\/p>\n

\"Tr\u00e9nink
\n
\nVid\u00edte verzi protokolu VTP \u2013 druhou, maxim\u00e1ln\u00ed po\u010det podporovan\u00fdch VLAN \u2013 255, po\u010det existuj\u00edc\u00edch VLAN \u2013 5 a re\u017eim VLAN \u2013 server. To v\u0161e jsou v\u00fdchoz\u00ed parametry. O VTP jsme ji\u017e diskutovali v lekci \u201eDen 30\u201c, tak\u017ee pokud jste n\u011bco zapomn\u011bli, m\u016f\u017eete se vr\u00e1tit a znovu si toto video prohl\u00e9dnout. <\/p>\n

Abych vid\u011bl datab\u00e1zi VLAN, zad\u00e1m p\u0159\u00edkaz show vlan brief. Zde jsou zobrazeny VLAN1 a VLAN1002-1005. Prvn\u00ed s\u00ed\u0165 je v\u00fdchoz\u00edm zp\u016fsobem p\u0159ipojena na v\u0161echny voln\u00e9 porty switche \u2013 23 porty Fast Ethernet a 2 porty Gigabit Ethernet, ostatn\u00ed 4 VLAN nejsou podporov\u00e1ny. Datab\u00e1ze VLAN dvou dal\u0161\u00edch switch\u016f vypad\u00e1 \u00fapln\u011b stejn\u011b, s t\u00edm rozd\u00edlem, \u017ee u SW1 z\u016fstalo voln\u00fdch pro VLAN pouze 22 port\u016f Fast Ethernet, proto\u017ee f0\/1 a f0\/2 jsou obsazeny trunky. Je\u0161t\u011b jednou p\u0159ipom\u00edn\u00e1m to, o \u010dem bylo \u0159e\u010deno v lekci \u201eDen 30\u201c \u2013 protokol VTP podporuje pouze aktualizaci datab\u00e1z\u00ed VLAN. <\/p>\n

Pokud nastav\u00edm n\u011bkolik port\u016f na pr\u00e1ci se s\u00edt\u011bmi VLAN pomoc\u00ed p\u0159\u00edkaz\u016f switchport access a switchport mode access VLAN10, VLAN20 nebo VLAN30, konfigurace t\u011bchto port\u016f nebude replikov\u00e1na pomoc\u00ed VTP, proto\u017ee VTP aktualizuje pouze datab\u00e1zi VLAN.
\nTak\u017ee pokud je jeden z port\u016f SW1 nastaven na VLAN20, ale tato s\u00ed\u0165 nebude v datab\u00e1zi VLAN, port bude zak\u00e1z\u00e1n. Aktualizace datab\u00e1z\u00ed prob\u00edh\u00e1 pouze p\u0159i pou\u017eit\u00ed protokolu VTP. <\/p>\n

Pomoc\u00ed p\u0159\u00edkazu show vtp status vid\u00edm, \u017ee v\u0161echny 3 switche jsou nyn\u00ed v re\u017eimu server. P\u0159epnu prost\u0159edn\u00ed switch SW1 do transparentn\u00edho re\u017eimu pomoc\u00ed p\u0159\u00edkazu vtp mode transparent, a t\u0159et\u00ed switch SW2 do re\u017eimu klienta pomoc\u00ed p\u0159\u00edkazu vtp mode client. <\/p>\n

Nyn\u00ed se vr\u00e1t\u00edme k prvn\u00edmu switchi SW0 a vytvo\u0159\u00edme dom\u00e9nu nwking.org pomoc\u00ed p\u0159\u00edkazu vtp domain . Pokud se nyn\u00ed pod\u00edv\u00e1te na stav VTP druh\u00e9ho switche, kter\u00fd je v transparentn\u00edm re\u017eimu, je z\u0159ejm\u00e9, \u017ee nijak nereagoval na vytvo\u0159en\u00ed dom\u00e9ny \u2013 pole VTP Domain Name z\u016fstalo pr\u00e1zdn\u00e9. T\u0159et\u00ed switch, kter\u00fd je v re\u017eimu klienta, v\u0161ak aktualizoval svou datab\u00e1zi a nyn\u00ed m\u00e1 dom\u00e9nov\u00e9 jm\u00e9no VTP - nwking.org. Tak\u017ee aktualizace datab\u00e1ze switche SW0 pro\u0161la p\u0159es SW1 a odrazila se na SW2. <\/p>\n

Te\u010f se pokus\u00edm zm\u011bnit zadan\u00e9 dom\u00e9nov\u00e9 jm\u00e9no, k \u010demu\u017e p\u0159ejdu do nastaven\u00ed SW0 a zad\u00e1m p\u0159\u00edkaz vtp domain NetworKing. Jak vid\u00edte, tentokr\u00e1t k \u017e\u00e1dn\u00e9 aktualizaci nedo\u0161lo \u2013 dom\u00e9nov\u00e9 jm\u00e9no VTP na t\u0159et\u00edm p\u0159ep\u00edna\u010di z\u016fstalo stejn\u00e9. Je to proto, \u017ee takov\u00e1 aktualizace dom\u00e9nov\u00e9ho jm\u00e9na prob\u00edh\u00e1 pouze jednou, kdy\u017e se zm\u011bn\u00ed dom\u00e9na v\u00fdchoz\u00ed. Pokud se dom\u00e9nov\u00e9 jm\u00e9no VTP zm\u011bn\u00ed znovu, na ostatn\u00edch p\u0159ep\u00edna\u010d\u00edch je t\u0159eba ho zm\u011bnit ru\u010dn\u011b. <\/p>\n

Te\u010f vytvo\u0159\u00edm v konzoli CLI prvn\u00edho p\u0159ep\u00edna\u010de novou s\u00ed\u0165 VLAN100 a nazvu ji jm\u00e9nem IMRAN. Objevila se v datab\u00e1zi VLAN prvn\u00edho p\u0159ep\u00edna\u010de, ale neobjevila se v datab\u00e1zi t\u0159et\u00edho p\u0159ep\u00edna\u010de, proto\u017ee to jsou r\u016fzn\u00e9 dom\u00e9ny. Pamatujte si, \u017ee aktualizace datab\u00e1ze VLAN prob\u00edh\u00e1 pouze v p\u0159\u00edpad\u011b, \u017ee oba p\u0159ep\u00edna\u010de maj\u00ed stejnou dom\u00e9nu, nebo jak jsem uk\u00e1zal d\u0159\u00edve, nov\u00e9 dom\u00e9nov\u00e9 jm\u00e9no je nastaveno m\u00edsto v\u00fdchoz\u00edho jm\u00e9na. <\/p>\n

P\u0159ech\u00e1z\u00edm do nastaven\u00ed 3. p\u0159ep\u00edna\u010de a postupn\u011b zad\u00e1v\u00e1m p\u0159\u00edkazy vtp mode a vtp domain NetworKing. V\u0161imn\u011bte si, \u017ee zad\u00e1v\u00e1n\u00ed jm\u00e9na je citliv\u00e9 na velikost p\u00edsmen, tak\u017ee naps\u00e1n\u00ed n\u00e1zvu dom\u00e9ny mus\u00ed p\u0159esn\u011b odpov\u00eddat pro oba p\u0159ep\u00edna\u010de. Te\u010f znovu p\u0159ev\u00e1d\u00edm SW2 do re\u017eimu klienta pomoc\u00ed p\u0159\u00edkazu vtp mode client. Pod\u00edvejme se, co se stane. Jak vid\u00edte, nyn\u00ed, p\u0159i shod\u011b n\u00e1zvu dom\u00e9ny, se datab\u00e1ze SW2 aktualizovala a objevila se v n\u00ed nov\u00e1 s\u00ed\u0165 VLAN100 IMRAN, a tyto zm\u011bny nijak neovlivnily st\u0159edn\u00ed p\u0159ep\u00edna\u010d, proto\u017ee je v re\u017eimu transparentn\u00ed. <\/p>\n

Pokud se chcete chr\u00e1nit proti neopr\u00e1vn\u011bn\u00e9mu p\u0159\u00edstupu, m\u016f\u017eete vytvo\u0159it heslo VTP. Mus\u00edte si b\u00fdt jisti, \u017ee za\u0159\u00edzen\u00ed na druh\u00e9 stran\u011b bude m\u00edt p\u0159esn\u011b stejn\u00e9 heslo, proto\u017ee pouze v tomto p\u0159\u00edpad\u011b m\u016f\u017ee p\u0159ij\u00edmat aktualizace VTP. <\/p>\n

Dal\u0161\u00ed, co si uk\u00e1\u017eeme, je VTP pruning, nebo \u201eod\u0159\u00edznut\u00ed\u201c nevyu\u017eit\u00fdch VLAN. Pokud m\u00e1te v s\u00edti 100 za\u0159\u00edzen\u00ed pou\u017e\u00edvaj\u00edc\u00edch protokol VTP, aktualizace datab\u00e1ze VLAN jednoho za\u0159\u00edzen\u00ed se automaticky replikuje na ostatn\u00edch 99 za\u0159\u00edzen\u00edch. Nicm\u00e9n\u011b ne v\u0161echna tato za\u0159\u00edzen\u00ed maj\u00ed v\u00fd\u0161e zm\u00edn\u011bn\u00e9 s\u00edt\u011b VLAN, tak\u017ee informace o nich nemus\u00ed b\u00fdt pot\u0159ebn\u00e9. <\/p>\n

\"Tr\u00e9nink<\/p>\n

Odkaz na aktualizace datab\u00e1ze VLAN za\u0159\u00edzen\u00ed vyu\u017e\u00edvaj\u00edc\u00ed VTP znamen\u00e1, \u017ee v\u0161echny porty v\u0161ech za\u0159\u00edzen\u00ed obdr\u017e\u00ed informace o p\u0159idan\u00fdch, odstran\u011bn\u00fdch a zm\u011bn\u011bn\u00fdch VLAN, k nim\u017e se nemus\u00ed nijak vztahovat. T\u00edm se s\u00ed\u0165 zapl\u0148uje zbyte\u010dn\u00fdm provozem. Aby se tomu zabr\u00e1nilo, pou\u017e\u00edv\u00e1 se koncept '\u0159ez\u00e1n\u00ed' VTP. Pro aktivaci re\u017eimu '\u0159ez\u00e1n\u00ed' neaktu\u00e1ln\u00edch VLAN na swit\u010di se pou\u017e\u00edv\u00e1 p\u0159\u00edkaz vtp pruning. Po jeho proveden\u00ed budou switche automaticky informovat navz\u00e1jem o tom, kter\u00e9 VLAN skute\u010dn\u011b pou\u017e\u00edvaj\u00ed, a t\u00edm varuj\u00ed sousedy, \u017ee nemaj\u00ed pos\u00edlat aktualizace pro s\u00edt\u011b, kter\u00e9 k nim nejsou p\u0159ipojeny.<\/p>\n

Nap\u0159\u00edklad pokud SW2 nem\u00e1 \u017e\u00e1dn\u00e9 porty VLAN10, nen\u00ed pot\u0159eba, aby mu SW1 pos\u00edlal provoz pro tuto s\u00ed\u0165. P\u0159itom switch SW1 pot\u0159ebuje provoz VLAN10, proto\u017ee jeden z jeho port\u016f je p\u0159ipojen k t\u00e9to s\u00edti; pouze mu nen\u00ed pot\u0159eba pos\u00edlat tento provoz switchem SW2.
\nPokud SW2 pou\u017e\u00edv\u00e1 re\u017eim vtp pruning, informuje SW1: 'pros\u00edm, nezas\u00edlejte mi provoz pro VLAN10, proto\u017ee tato s\u00ed\u0165 ke mn\u011b nen\u00ed p\u0159ipojena a \u017e\u00e1dn\u00fd z m\u00fdch port\u016f nen\u00ed nastaven na tuto s\u00ed\u0165'. To je v\u00fdhoda pou\u017e\u00edv\u00e1n\u00ed p\u0159\u00edkazu vtp pruning. <\/p>\n

Existuje tak\u00e9 jin\u00fd zp\u016fsob filtrov\u00e1n\u00ed provozu pro konkr\u00e9tn\u00ed rozhran\u00ed. Ten umo\u017e\u0148uje nastavit port na trunk s konkr\u00e9tn\u00ed VLAN. Nev\u00fdhodou tohoto zp\u016fsobu je pot\u0159eba ru\u010dn\u00edho nastaven\u00ed ka\u017ed\u00e9ho trunk portu, kter\u00e9mu se mus\u00ed ur\u010dit, kter\u00e9 VLAN jsou povolen\u00e9 a kter\u00e9 zak\u00e1zan\u00e9. K tomu se pou\u017e\u00edv\u00e1 sekvence t\u0159\u00ed p\u0159\u00edkaz\u016f. Prvn\u00ed ur\u010duje rozhran\u00ed, kter\u00e9ho se tato omezen\u00ed t\u00fdkaj\u00ed, druh\u00fd prom\u011bn\u00ed toto rozhran\u00ed na trunk-port a t\u0159et\u00ed \u2014 switchport trunk allowed vlan \u2014 ukazuje, kter\u00e1 VLAN je na tomto portu povolen\u00e1: v\u0161echno, nic, p\u0159id\u00e1van\u00e1 VLAN nebo odstra\u0148ovan\u00e1 VLAN. <\/p>\n

V z\u00e1vislosti na konkr\u00e9tn\u00ed situaci si vyb\u00edr\u00e1te, co pou\u017e\u00edt: VTP pruning nebo Trunk allowed. N\u011bkter\u00e9 organizace se rozhodnou nepou\u017e\u00edvat VTP z bezpe\u010dnostn\u00edch d\u016fvod\u016f, a proto preferuj\u00ed ru\u010dn\u00ed nastaven\u00ed trunkingu. Proto\u017ee p\u0159\u00edkaz vtp pruning nefunguje v Packet Tracer, uk\u00e1\u017eu ho v emul\u00e1toru GNS3. <\/p>\n

Pokud otev\u0159ete nastaven\u00ed SW2 a zad\u00e1te p\u0159\u00edkaz vtp pruning, syst\u00e9m okam\u017eit\u011b ozn\u00e1m\u00ed, \u017ee tento re\u017eim je aktivov\u00e1n: Pruning switched on, co\u017e znamen\u00e1, \u017ee \"pruning\" VLAN je aktivov\u00e1no jedn\u00edm p\u0159\u00edkazem. <\/p>\n

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

\"Tr\u00e9nink
\n
\nPokud tento re\u017eim nastavujete na serverov\u00e9m switchi, p\u0159ejd\u011bte do jeho nastaven\u00ed a zadejte p\u0159\u00edkaz vtp pruning. To znamen\u00e1, \u017ee za\u0159\u00edzen\u00ed p\u0159ipojen\u00e1 k serveru za\u010dnou automaticky pou\u017e\u00edvat vtp pruning, aby minimalizovala trunkov\u00fd provoz pro neaktu\u00e1ln\u00ed VLAN. <\/p>\n

Pokud tento re\u017eim nechcete pou\u017e\u00edvat, mus\u00edte vstoupit do konkr\u00e9tn\u00edho rozhran\u00ed, nap\u0159\u00edklad e0\/0, a pot\u00e9 zadat p\u0159\u00edkaz switchport trunk allowed vlan. Syst\u00e9m v\u00e1m poskytne n\u00e1vrhy mo\u017en\u00fdch parametr\u016f tohoto p\u0159\u00edkazu: <\/p>\n

\u2014 WORD \u2014 \u010d\u00edslo VLAN, kter\u00e1 bude povolena na tomto rozhran\u00ed v trunkov\u00e9m re\u017eimu;
\n \u2014 add \u2014 VLAN, kterou je t\u0159eba p\u0159idat do datab\u00e1ze VLAN;
\n \u2014 all \u2014 povolit v\u0161echny VLAN;
\n \u2014 except \u2014 povolit v\u0161echny VLAN krom\u011b uveden\u00fdch;
\n \u2014 none \u2013 zak\u00e1zat v\u0161echny VLAN;
\n \u2014 remove \u2013 odstranit VLAN ze seznamu datab\u00e1ze VLAN. <\/p>\n

Nap\u0159\u00edklad, pokud m\u00e1me povolen\u00fd trunk pro VLAN10 a chceme ho povolit pro s\u00ed\u0165 VLAN20, mus\u00edme zadat p\u0159\u00edkaz switchport trunk allowed vlan add 20. <\/p>\n

\"Tr\u00e9nink
\n
\nChci v\u00e1m uk\u00e1zat je\u0161t\u011b n\u011bco, tak\u017ee pou\u017eiji p\u0159\u00edkaz show interface trunk. V\u0161imn\u011bte si, \u017ee standardn\u011b byly pro trunk povoleny v\u0161echny VLAN 1-1005, a nyn\u00ed byla p\u0159id\u00e1na i VLAN10. <\/p>\n

\"Tr\u00e9nink
\n
\nPokud pou\u017eiji p\u0159\u00edkaz switchport trunk allowed vlan add 20 a znovu po\u017e\u00e1d\u00e1m o zobrazen\u00ed stavu trunkov\u00e1n\u00ed, uvid\u00edme, \u017ee nyn\u00ed jsou pro trunk povoleny dv\u011b s\u00edt\u011b \u2013 VLAN10 a VLAN20. <\/p>\n

\"Tr\u00e9nink
\n
\nP\u0159i\u010dem\u017e \u017e\u00e1dn\u00fd jin\u00fd provoz, krom\u011b toho ur\u010den\u00e9ho pro uveden\u00e9 s\u00edt\u011b, nebude moci proch\u00e1zet t\u00edmto trunkem. Povolen\u00edm provozu pouze pro VLAN 10 a VLAN 20 jsme zak\u00e1zali provoz pro v\u0161echny ostatn\u00ed VLAN. Takto lze ru\u010dn\u011b nastavit parametry trunkov\u00e1n\u00ed pro konkr\u00e9tn\u00ed VLAN na konkr\u00e9tn\u00edm rozhran\u00ed switche. <\/p>\n

V\u0161imn\u011bte si, \u017ee do konce dne 17. listopadu 2017 plat\u00ed na na\u0161em webu 90% sleva na cenu sta\u017een\u00ed laboratorn\u00ed pr\u00e1ce na toto t\u00e9ma. <\/p>\n

\"Tr\u00e9nink
\n
\nD\u011bkuji za pozornost a t\u011b\u0161\u00edm se na setk\u00e1n\u00ed v p\u0159\u00ed\u0161t\u00edm videoz\u00e1znamu!<\/p>\n

\r\n \"P\u0159ehr\u00e1t\r\n
<\/div>\r\n <\/div><\/center>
\nD\u011bkujeme, \u017ee s n\u00e1mi z\u016fst\u00e1v\u00e1te. L\u00edb\u00ed se v\u00e1m na\u0161e \u010dl\u00e1nky? Chcete vid\u011bt v\u00edce zaj\u00edmav\u00fdch materi\u00e1l\u016f? Podpo\u0159te n\u00e1s objedn\u00e1vkou nebo doporu\u010den\u00edm zn\u00e1m\u00fdm, 30 % sleva pro u\u017eivatele Habra na jedine\u010dn\u00fd analog entry-level server\u016f, kter\u00fd jsme pro v\u00e1s vymysleli:<\/b> Ve\u0161ker\u00e1 pravda o VPS (KVM) E5-2650 v4 (6 jader) 10GB DDR4 240GB SSD 1Gbps od 20 $ nebo jak spr\u00e1vn\u011b rozd\u011blit server?<\/a><\/noindex> (k dispozici varianty s RAID1 a RAID10, a\u017e 24 jader a a\u017e 40GB DDR4).<\/p>\n

Dell R730xd za polovinu ceny?<\/b> Jen u n\u00e1s 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB od 199 $<\/a><\/noindex> v Nizozemsku! Dell R420 \u2014 2x E5-2430 2.2GHz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 $!<\/b><\/b> \u010ct\u011bte o tom Jak postavit infrastrukturu podnikov\u00e9 t\u0159\u00eddy s pou\u017eit\u00edm server\u016f Dell R730xd E5-2650 v4 v hodnot\u011b 9000 eur za pakatel?<\/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\udd47Tr\u00e9nink Cisco 200-125 CCNA v3.0. Den 35. Dynamick\u00fd protokol trunkov\u00e1n\u00ed DTP | ProHoster","description":"Dnes se zam\u011b\u0159\u00edme na dynamick\u00fd protokol trunkov\u00e1n\u00ed DTP a VTP \u2013 protokol trunkov\u00e1n\u00ed VLAN.","canonical_url":"https:\/\/prohoster.info\/cs\/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":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/37940","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=37940"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37940\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/28471"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=37940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=37940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=37940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}