{"id":37066,"date":"2019-10-31T22:15:33","date_gmt":"2019-10-31T19:15:33","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-vlan\/"},"modified":"2019-10-31T22:15:33","modified_gmt":"2019-10-31T19:15:33","slug":"trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-vlan","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-vlan","title":{"rendered":"Tr\u00e9nink Cisco 200-125 CCNA v3.0. Den 14. VTP, Pruning a Native VLAN.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dnes se budeme pokra\u010dovat v diskusi o VLAN a prob\u00edrat protokol VTP, stejn\u011b jako pojmy VTP Pruning a Native VLAN. V jednom z p\u0159edchoz\u00edch vide\u00ed jsme ji\u017e hovo\u0159ili o VTP a prvn\u00ed, co v\u00e1s napadne, kdy\u017e usly\u0161\u00edte o VTP, je, \u017ee to nen\u00ed protokol pro trunking, i kdy\u017e se naz\u00fdv\u00e1 'protokolem trunkingu VLAN'.<\/p>\n

\"Tr\u00e9nink
\n
\nJak v\u00edte, existuj\u00ed dva popul\u00e1rn\u00ed protokoly trunkingu \u2013 dnes ji\u017e nepou\u017e\u00edvan\u00fd propriet\u00e1rn\u00ed protokol Cisco ISL a protokol 802.q, kter\u00fd se pou\u017e\u00edv\u00e1 v s\u00ed\u0165ov\u00fdch za\u0159\u00edzen\u00edch r\u016fzn\u00fdch v\u00fdrobc\u016f pro inkapsulaci trunkingov\u00e9ho provozu. Tento protokol se rovn\u011b\u017e pou\u017e\u00edv\u00e1 ve switch\u00edch Cisco. Ji\u017e jsme zm\u00ednili, \u017ee VTP je protokol pro synchronizaci VLAN, to znamen\u00e1, \u017ee je ur\u010den pro synchronizaci datab\u00e1ze VLAN ve v\u0161ech switchech v s\u00edti. <\/p>\n

\"Tr\u00e9nink
\n
\nZmi\u0148ovali jsme r\u016fzn\u00e9 re\u017eimy VTP \u2013 server, klient, transparentn\u00ed. Pokud za\u0159\u00edzen\u00ed pracuje v re\u017eimu serveru, umo\u017e\u0148uje to prov\u00e1d\u011bt zm\u011bny, p\u0159id\u00e1vat nebo odstra\u0148ovat VLAN. Re\u017eim klienta neumo\u017e\u0148uje prov\u00e1d\u011bt zm\u011bny v nastaven\u00ed switche, datab\u00e1zi VLAN m\u016f\u017eete nastavit pouze prost\u0159ednictv\u00edm VTP serveru a ta bude replikov\u00e1na na v\u0161ech VTP klientech. Switch v transparentn\u00edm re\u017eimu neprov\u00e1d\u00ed zm\u011bny ve sv\u00e9 vlastn\u00ed datab\u00e1zi VLAN, ale pouze propou\u0161t\u00ed a p\u0159en\u00e1\u0161\u00ed zm\u011bny dal\u0161\u00edmu za\u0159\u00edzen\u00ed, kter\u00e9 je v re\u017eimu klienta. Tento re\u017eim je podobn\u00fd vypnut\u00ed protokolu VTP na konkr\u00e9tn\u00edm za\u0159\u00edzen\u00ed, co\u017e ho m\u011bn\u00ed na p\u0159epravce informac\u00ed o zm\u011bn\u00e1ch VLAN. <\/a><\/noindex><\/p>\n

Vra\u0165me se k programu Packet Tracer a k topologii s\u00edt\u011b, kterou jsme probrali v p\u0159edchoz\u00ed lekci. Nastavili jsme s\u00ed\u0165 VLAN10 pro odd\u011blen\u00ed prodeje a s\u00ed\u0165 VLAN20 pro marketingov\u00e9 odd\u011blen\u00ed, spojuj\u00edc\u00ed je t\u0159emi switche. <\/p>\n

\"Tr\u00e9nink
\n
\nMezi switche SW0 a SW1 prob\u00edh\u00e1 komunikace p\u0159es s\u00ed\u0165 VLAN20, a mezi SW0 a SW2 \u2013 spojen\u00ed p\u0159es s\u00ed\u0165 VLAN10 d\u00edky tomu, \u017ee jsme p\u0159idali VLAN10 do datab\u00e1ze VLAN switche SW1.
\nAbychom prozkoumali fungov\u00e1n\u00ed protokolu VTP, pou\u017eijme jeden ze switch\u016f jako VTP server, nech\u0165 je to SW0. Pokud si pamatujete, v\u0161echny switche pracuj\u00ed ve v\u00fdchoz\u00edm nastaven\u00ed v re\u017eimu VTP serveru. P\u0159ihl\u00e1s\u00edme se do termin\u00e1lu p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku switche a zad\u00e1me p\u0159\u00edkaz show vtp status. Vid\u00edte aktu\u00e1ln\u00ed verzi protokolu VTP \u2013 2 a \u010d\u00edslo revize konfigurace 4. Pokud si pamatujete, poka\u017ed\u00e9, kdy\u017e do datab\u00e1ze VTP provedete zm\u011bny, \u010d\u00edslo revize se zv\u00fd\u0161\u00ed o jednu. <\/p>\n

\"Tr\u00e9nink
\n
\nMaxim\u00e1ln\u00ed po\u010det podporovan\u00fdch s\u00edt\u00ed VLAN je 255. Toto \u010d\u00edslo z\u00e1vis\u00ed na typu konkr\u00e9tn\u00edho switch Cisco, proto\u017ee r\u016fzn\u00e9 switche mohou podporovat r\u016fzn\u00e9 po\u010dty lok\u00e1ln\u00edch virtu\u00e1ln\u00edch s\u00edt\u00ed. Po\u010det existuj\u00edc\u00edch s\u00edt\u00ed VLAN je 7, za minutu se pod\u00edv\u00e1me, co to jsou za s\u00edt\u011b. Re\u017eim spr\u00e1vy VTP je server, n\u00e1zev dom\u00e9ny nen\u00ed nastaven, re\u017eim VTP Pruning je vypnut, k tomu se vr\u00e1t\u00edme pozd\u011bji. Tak\u00e9 jsou deaktivov\u00e1ny re\u017eimy VTP V2 a VTP Traps Generation. Pro slo\u017een\u00ed zkou\u0161ky 200-125 CCNA nen\u00ed nutn\u00e9 zn\u00e1t posledn\u00ed dva re\u017eimy, tak\u017ee si s t\u00edm m\u016f\u017eete ned\u011blat starosti. <\/p>\n

Pod\u00edvejme se na datab\u00e1zi VLAN, k tomu pou\u017eijeme p\u0159\u00edkaz show vlan. Jak jsme vid\u011bli v p\u0159edchoz\u00edm videu, m\u00e1me 4 nepodporovan\u00e9 s\u00edt\u011b: 1002, 1003, 1004 a 1005.<\/p>\n

\"Tr\u00e9nink
\n
\nZde jsou tak\u00e9 vyjmenov\u00e1ny 2 n\u00e1mi vytvo\u0159en\u00e9 s\u00edt\u011b VLAN10 a 20 a v\u00fdchoz\u00ed s\u00ed\u0165 VLAN1. Nyn\u00ed p\u0159ejdeme k jin\u00e9mu switchi a zad\u00e1me stejn\u00fd p\u0159\u00edkaz, abychom si prohl\u00e9dli status VTP. Vid\u00edte, \u017ee \u010d\u00edslo revize tohoto switche je 3, je v re\u017eimu VTP-server a v\u0161echny ostatn\u00ed informace jsou podobn\u00e9 prvn\u00edmu switchi. Kdy\u017e zad\u00e1m p\u0159\u00edkaz show VLAN, uvid\u00edm, \u017ee jsme provedli 2 zm\u011bny v nastaven\u00edch, o jednu m\u00e9n\u011b ne\u017e u switche SW0, pr\u00e1v\u011b proto je \u010d\u00edslo revize SW1 3. Provedli jsme 3 zm\u011bny ve v\u00fdchoz\u00edch nastaven\u00edch prvn\u00edho switche, proto se jeho \u010d\u00edslo revize zv\u00fd\u0161ilo na 4. <\/p>\n

\"Tr\u00e9nink
\n
\nNyn\u00ed se pod\u00edv\u00e1me na status SW2. \u010c\u00edslo revize zde je 1, a to je divn\u00e9. M\u011bli bychom m\u00edt druhou revizi, proto\u017ee bylo provedeno 1 zm\u011bna nastaven\u00ed. Pod\u00edvejme se na datab\u00e1zi VLAN.<\/p>\n

\"Tr\u00e9nink
\n
\nProvedli jsme jednu zm\u011bnu vytvo\u0159en\u00edm s\u00edt\u011b VLAN10 a nev\u00edm, pro\u010d se tyto informace neaktualizovaly. Mo\u017en\u00e1 je to zp\u016fsobeno t\u00edm, \u017ee nem\u00e1me skute\u010dnou s\u00ed\u0165, ale softwarov\u00fd simul\u00e1tor s\u00edt\u011b, ve kter\u00e9m mohou b\u00fdt chyby. Kdy\u017e budete m\u00edt mo\u017enost pracovat se skute\u010dn\u00fdmi za\u0159\u00edzen\u00edmi b\u011bhem praxe ve spole\u010dnosti Cisco, pom\u016f\u017ee v\u00e1m to v\u00edc ne\u017e simul\u00e1tor Packet Tracer. Dal\u0161\u00ed u\u017eite\u010dnou v\u011bc\u00ed p\u0159i absenci skute\u010dn\u00fdch za\u0159\u00edzen\u00ed bude GNC3, tedy grafick\u00fd simul\u00e1tor s\u00edt\u011b Cisco. To je emul\u00e1tor, kter\u00fd pou\u017e\u00edv\u00e1 skute\u010dn\u00fd opera\u010dn\u00ed syst\u00e9m za\u0159\u00edzen\u00ed, nap\u0159\u00edklad routeru. Mezi simul\u00e1torem a emul\u00e1torem je rozd\u00edl \u2013 prvn\u00ed p\u0159edstavuje program, kter\u00fd vypad\u00e1 jako skute\u010dn\u00fd router, ale nen\u00ed j\u00edm. Emul\u00e1tor programov\u011b vytv\u00e1\u0159\u00ed pouze samo za\u0159\u00edzen\u00ed, ale pro jeho fungov\u00e1n\u00ed pou\u017e\u00edv\u00e1 skute\u010dn\u00fd software. Ale pokud nem\u00e1te mo\u017enost pracovat se skute\u010dn\u00fdm softwarem Cisco IOS, nejlep\u0161\u00edm \u0159e\u0161en\u00edm bude Packet Tracer. <\/p>\n

Tak\u017ee pot\u0159ebujeme nastavit SW0 jako VTP server. Za\u010dnu vstupem do glob\u00e1ln\u00ed konfigura\u010dn\u00ed re\u017eimu a zad\u00e1m p\u0159\u00edkaz vtp version 2. Jak jsem \u0159\u00edkal, m\u016f\u017eete nastavit verzi protokolu, kterou pot\u0159ebujeme \u2013 1 nebo 2, v tomto p\u0159\u00edpad\u011b pot\u0159ebujeme druhou verzi. Pot\u00e9 pomoc\u00ed p\u0159\u00edkazu vtp mode ur\u010dujeme VTP re\u017eim p\u0159ep\u00edna\u010de \u2013 server, klient nebo transparentn\u00ed. V tomto p\u0159\u00edpad\u011b pot\u0159ebujeme re\u017eim serveru a po zad\u00e1n\u00ed p\u0159\u00edkazu vtp mode server syst\u00e9m vyd\u00e1 zpr\u00e1vu, \u017ee za\u0159\u00edzen\u00ed je ji\u017e v re\u017eimu serveru. D\u00e1le mus\u00edme nastavit VTP dom\u00e9nu, k \u010demu\u017e pou\u017eijeme p\u0159\u00edkaz vtp domain nwking.org. Pro\u010d je to pot\u0159eba? Pokud v s\u00edti existuje jin\u00e9 za\u0159\u00edzen\u00ed s vy\u0161\u0161\u00edm \u010d\u00edslem revize, v\u0161echna ostatn\u00ed za\u0159\u00edzen\u00ed s ni\u017e\u0161\u00edm \u010d\u00edslem za\u010dnou replikovat datab\u00e1zi VLAN z tohoto za\u0159\u00edzen\u00ed. To se v\u0161ak d\u011bje pouze tehdy, kdy\u017e maj\u00ed za\u0159\u00edzen\u00ed stejn\u00e9 dom\u00e9nov\u00e9 jm\u00e9no. Nap\u0159\u00edklad pokud pracujete v nwking.org, uvedete tuto dom\u00e9nu; pokud v Cisco, tak dom\u00e9nu cisco.com a tak d\u00e1le. Dom\u00e9nov\u00e9 jm\u00e9no za\u0159\u00edzen\u00ed va\u0161\u00ed spole\u010dnosti slou\u017e\u00ed k jejich odli\u0161en\u00ed od za\u0159\u00edzen\u00ed jin\u00e9 spole\u010dnosti nebo jin\u00fdch extern\u00edch za\u0159\u00edzen\u00ed v s\u00edti. Pokud za\u0159\u00edzen\u00ed p\u0159i\u0159ad\u00edte dom\u00e9nov\u00e9 jm\u00e9no spole\u010dnosti, u\u010din\u00edte jej sou\u010d\u00e1st\u00ed s\u00edt\u011b t\u00e9to spole\u010dnosti. <\/p>\n

Dal\u0161\u00ed krok je nastaven\u00ed VTP hesla. To je d\u016fle\u017eit\u00e9, aby hacker, kter\u00fd m\u00e1 za\u0159\u00edzen\u00ed s vy\u0161\u0161\u00edm revizn\u00edm \u010d\u00edslem, nemohl zkop\u00edrovat sv\u00e1 VTP nastaven\u00ed do va\u0161eho switche. Vkl\u00e1d\u00e1m heslo cisco pomoc\u00ed p\u0159\u00edkazu vtp password cisco. Po tomto kroku bude replikace dat VTP mezi switchemi mo\u017en\u00e1 pouze p\u0159i shod\u011b hesel. Pokud bude pou\u017eito nespr\u00e1vn\u00e9 heslo, aktualizace datab\u00e1ze VLAN nenastane. <\/p>\n

Zkusme vytvo\u0159it je\u0161t\u011b n\u011bkolik VLAN. K tomu pou\u017e\u00edv\u00e1m p\u0159\u00edkaz config t, p\u0159\u00edkaz vlan 200 pro vytvo\u0159en\u00ed s\u00edt\u011b s \u010d\u00edslem 200, p\u0159i\u0159azuji j\u00ed n\u00e1zev TEST a zm\u011bny ulo\u017e\u00edm p\u0159\u00edkazem exit. Pot\u00e9 vytv\u00e1\u0159\u00edm je\u0161t\u011b jednu s\u00ed\u0165 vlan 500 a naz\u00fdv\u00e1m ji TEST1. Pokud nyn\u00ed zad\u00e1me p\u0159\u00edkaz show vlan, v tabulce virtu\u00e1ln\u00edch s\u00edt\u00ed switche uvid\u00edme tyto dv\u011b nov\u00e9 s\u00edt\u011b, ke kter\u00fdm nen\u00ed p\u0159i\u0159azen \u017e\u00e1dn\u00fd port. <\/p>\n

\"Tr\u00e9nink
\n
\nP\u0159ejd\u011bme na SW1 a pod\u00edvejme se na jeho VTP status. Vid\u00edme, \u017ee se zde nic nezm\u011bnilo, krom\u011b jm\u00e9na dom\u00e9ny, po\u010det VLAN z\u016fstal na 7. Nevid\u00edme \u017e\u00e1dn\u00fd v\u00fdskyt s\u00edt\u00ed, kter\u00e9 jsme vytvo\u0159ili, proto\u017ee VTP heslo se neshoduje. Nastavme VTP heslo na tomto switche postupn\u011b zad\u00e1n\u00edm p\u0159\u00edkaz\u016f conf t, vtp pass a vtp password cisco. Syst\u00e9m vyhodil zpr\u00e1vu, \u017ee datab\u00e1ze VLAN za\u0159\u00edzen\u00ed nyn\u00ed pou\u017e\u00edv\u00e1 heslo cisco. Znovu se pod\u00edvejme na status VTP a ov\u011b\u0159me, zda do\u0161lo k replikaci informac\u00ed. Jak vid\u00edte, po\u010det existuj\u00edc\u00edch VLAN automaticky vzrostl na 9. <\/p>\n

Pokud se pod\u00edv\u00e1te na datab\u00e1zi VLAN tohoto switche, je jasn\u00e9, \u017ee se tam automaticky objevily na\u0161e vytvo\u0159en\u00e9 s\u00edt\u011b VLAN200 a VLAN500. <\/p>\n

Tot\u00e9\u017e je pot\u0159eba prov\u00e9st s posledn\u00edm switchem SW2. Zadejte p\u0159\u00edkaz show vlan \u2013 vid\u00edte, \u017ee se v n\u011bm nijak nezm\u011bnila. Podobn\u011b nejsou \u017e\u00e1dn\u00e9 zm\u011bny ve stavu VTP. Aby tento switch aktualizoval informace, je tak\u00e9 nutn\u00e9 nastavit heslo, tedy zadat ty sam\u00e9 p\u0159\u00edkazy jako pro SW1. Po tomto kroku se zv\u00fd\u0161\u00ed po\u010det VLAN v statusu SW2 na 9.<\/p>\n

Toto je d\u016fvod, pro\u010d je protokol VTP u\u017eite\u010dn\u00fd. Je to skv\u011bl\u00fd n\u00e1stroj, kter\u00fd zaji\u0161\u0165uje automatickou aktualizaci informac\u00ed ve v\u0161ech klientsk\u00fdch s\u00ed\u0165ov\u00fdch za\u0159\u00edzen\u00edch po proveden\u00ed zm\u011bn na za\u0159\u00edzen\u00ed-serveru. Nen\u00ed pot\u0159eba ru\u010dn\u011b prov\u00e1d\u011bt zm\u011bny v datab\u00e1zi VLAN v\u0161ech p\u0159ep\u00edna\u010d\u016f \u2013 replikace prob\u00edh\u00e1 automaticky. Pokud m\u00e1te 200 s\u00ed\u0165ov\u00fdch za\u0159\u00edzen\u00ed, proveden\u00e9 zm\u011bny se najednou ulo\u017e\u00ed na v\u0161ech dvaceti za\u0159\u00edzen\u00edch. Pro jistotu se mus\u00edme ujistit, \u017ee SW2 je tak\u00e9 VTP klient, a proto p\u0159ejdeme do nastaven\u00ed pomoc\u00ed p\u0159\u00edkazu config t a zad\u00e1me p\u0159\u00edkaz vtp mode client. <\/p>\n

Tak\u017ee v na\u0161\u00ed s\u00edti je pouze prvn\u00ed p\u0159ep\u00edna\u010d v re\u017eimu VTP Server, zb\u00fdvaj\u00edc\u00ed dva funguj\u00ed v re\u017eimu VTP Client. Pokud te\u010f vstoup\u00edm do nastaven\u00ed SW2 a zad\u00e1m p\u0159\u00edkaz vlan 1000, zobraz\u00ed se mi zpr\u00e1va: \u201enastaven\u00ed VTP VLAN nen\u00ed povoleno, kdy\u017e je za\u0159\u00edzen\u00ed v re\u017eimu klient\u201c. Tak\u017ee nemohu prov\u00e1d\u011bt \u017e\u00e1dn\u00e9 zm\u011bny v datab\u00e1zi VLAN, pokud je p\u0159ep\u00edna\u010d v re\u017eimu VTP klienta. Pokud chci prov\u00e9st n\u011bjak\u00e9 zm\u011bny, mus\u00edm p\u0159ej\u00edt na p\u0159ep\u00edna\u010d-server. <\/p>\n

Vstupuji do nastaven\u00ed termin\u00e1lu SW0 a zad\u00e1v\u00e1m p\u0159\u00edkazy vlan 999, name IMRAN a exit. Tato nov\u00e1 s\u00ed\u0165 se objevila v datab\u00e1zi VLAN tohoto p\u0159ep\u00edna\u010de, a pokud nyn\u00ed p\u0159ejdu do datab\u00e1ze p\u0159ep\u00edna\u010de-klienta SW2, uvid\u00edm, \u017ee informace jsou zde shodn\u00e9, tedy do\u0161lo k replikaci. <\/p>\n

Jak jsem \u0159ekl, VTP je skv\u011bl\u00e1 sou\u010d\u00e1st softwaru, ale p\u0159i nespr\u00e1vn\u00e9m pou\u017eit\u00ed tento protokol m\u016f\u017ee naru\u0161it \u010dinnost cel\u00e9 s\u00edt\u011b. Proto mus\u00edte b\u00fdt velmi opatrn\u00ed p\u0159i spr\u00e1v\u011b s\u00edt\u011b spole\u010dnosti, pokud nen\u00ed nastavena dom\u00e9nov\u00e9 jm\u00e9no a heslo VTP. V tomto p\u0159\u00edpad\u011b v\u0161e, co hackera pot\u0159ebuje, je zapojit kabel sv\u00e9ho p\u0159ep\u00edna\u010de do s\u00ed\u0165ov\u00e9 z\u00e1suvky na zdi, p\u0159ipojit se k jak\u00e9mukoliv kancel\u00e1\u0159sk\u00e9mu p\u0159ep\u00edna\u010di pomoc\u00ed protokolu DTP a pot\u00e9, vyu\u017e\u00edt vytvo\u0159en\u00fd trunk, aktualizovat v\u0161echny informace protokolem VTP. Tak m\u016f\u017ee hacker smazat v\u0161echny d\u016fle\u017eit\u00e9 s\u00edt\u011b VLAN, proto\u017ee \u010d\u00edslo revize jeho za\u0159\u00edzen\u00ed je vy\u0161\u0161\u00ed ne\u017e \u010d\u00edslo revize ostatn\u00edch p\u0159ep\u00edna\u010d\u016f. V t\u00e9to situaci p\u0159ep\u00edna\u010de spole\u010dnosti automaticky nahrad\u00ed v\u0161echny informace datab\u00e1ze VLAN informacemi replikovan\u00fdmi z \u0161kodliv\u00e9ho p\u0159ep\u00edna\u010de a cel\u00e1 va\u0161e s\u00ed\u0165 se zhrout\u00ed. <\/p>\n

Tohoto je d\u016fsledkem toho, \u017ee po\u010d\u00edta\u010de jsou pomoc\u00ed s\u00ed\u0165ov\u00e9ho kabelu p\u0159ipojeny k ur\u010dit\u00e9mu portu switche, ke kter\u00e9mu je p\u0159i\u0159azena s\u00ed\u0165 VLAN 10 nebo s\u00ed\u0165 VLAN 20. Pokud budou tyto s\u00edt\u011b odstran\u011bny z datab\u00e1ze LAN switche, automaticky se port, kter\u00fd pat\u0159\u00ed k neexistuj\u00edc\u00ed s\u00edti, deaktivuje. Obvykle m\u016f\u017ee firma zkolabovat pr\u00e1v\u011b proto, \u017ee switche jednodu\u0161e vypnou porty spojen\u00e9 s VLAN, kter\u00e9 byly odstran\u011bny p\u0159i posledn\u00ed aktualizaci. <\/p>\n

Aby se p\u0159ede\u0161lo vzniku takov\u00e9ho probl\u00e9mu, je nutn\u00e9 nastavit dom\u00e9nov\u00e9 jm\u00e9no a heslo VTP, nebo vyu\u017e\u00edt funkci Cisco Port Security, kter\u00e1 umo\u017e\u0148uje \u0159\u00eddit MAC adresy port\u016f switch\u016f zav\u00e1d\u011bn\u00edm r\u016fzn\u00fdch omezen\u00ed jejich pou\u017e\u00edv\u00e1n\u00ed. Nap\u0159\u00edklad, pokud se n\u011bkdo pokus\u00ed zm\u011bnit MAC adresu, port se okam\u017eit\u011b deaktivuje. Brzy se podrobn\u011bji sezn\u00e1m\u00edme s touto funkc\u00ed switch\u016f Cisco, ale nyn\u00ed je dobr\u00e9 v\u011bd\u011bt, \u017ee Port Security zaji\u0161\u0165uje, \u017ee VTP je chr\u00e1n\u011bn p\u0159ed \u00fato\u010dn\u00edky.<\/p>\n

Shrneme, co p\u0159edstavuje nastaven\u00ed VTP. Je to v\u00fdb\u011br verze protokolu \u2013 1 nebo 2, p\u0159i\u0159azen\u00ed re\u017eimu VTP \u2013 server, klient nebo transparentn\u00ed. Jak jsem ji\u017e zm\u00ednil, posledn\u00ed re\u017eim neaktualizuje datab\u00e1zi VLAN samotn\u00e9ho za\u0159\u00edzen\u00ed, ale pouze p\u0159ed\u00e1v\u00e1 v\u0161echny zm\u011bny sousedn\u00edm za\u0159\u00edzen\u00edm. N\u00e1sleduj\u00ed p\u0159\u00edkazy pro nastaven\u00ed dom\u00e9nov\u00e9ho jm\u00e9na a hesla: vtp domain <jm\u00e9no dom\u00e9ny> a vtp password <heslo>. <\/p>\n

\"Tr\u00e9nink
\n
\nNyn\u00ed se pod\u00edv\u00e1me na nastaven\u00ed VTP Pruning. Pokud se pod\u00edv\u00e1te na topologii s\u00edt\u011b, m\u016f\u017eete vid\u011bt, \u017ee v\u0161echny t\u0159i switche maj\u00ed stejnou datab\u00e1zi VLAN, co\u017e znamen\u00e1, \u017ee s\u00edt\u011b VLAN10 a VLAN20 jsou sou\u010d\u00e1st\u00ed v\u0161ech 3 switch\u016f. Technicky switch SW2 nepot\u0159ebuje s\u00ed\u0165 VLAN20, proto\u017ee nem\u00e1 \u017e\u00e1dn\u00e9 porty, kter\u00e9 by k t\u00e9to s\u00edti pat\u0159ily. Nicm\u00e9n\u011b, ve\u0161ker\u00fd provoz, kter\u00fd sm\u011b\u0159uje z po\u010d\u00edta\u010de Laptop0 p\u0159es s\u00ed\u0165 VLAN20, proch\u00e1z\u00ed switchem SW1 a od n\u011bj je po trunku p\u0159en\u00e1\u0161en na porty SW2. Va\u0161\u00edm hlavn\u00edm \u00fakolem jako s\u00ed\u0165ov\u00e9ho specialisty je zajistit, aby po s\u00edti prob\u00edhalo co nejm\u00e9n\u011b nadbyte\u010dn\u00fdch dat. Mus\u00edte zajistit p\u0159enos pot\u0159ebn\u00fdch dat, ale jak omezit p\u0159enos informac\u00ed, kter\u00e9 dan\u00e9 za\u0159\u00edzen\u00ed nepot\u0159ebuje?<\/p>\n

Mus\u00edte zajistit, aby provoz ur\u010den\u00fd pro za\u0159\u00edzen\u00ed v s\u00edti VLAN20 nedoch\u00e1zel k port\u016fm SW2 p\u0159es trunk, pokud to nen\u00ed pot\u0159eba. To znamen\u00e1, \u017ee provoz z Laptop0 by m\u011bl dorazit k SW1 a pot\u00e9 k po\u010d\u00edta\u010d\u016fm v s\u00edti VLAN20, ale nem\u011bl by p\u0159esahovat na prav\u00fd trunk port SW1. Toho lze dos\u00e1hnout pomoc\u00ed VTP Pruning. <\/p>\n

K tomu se mus\u00edme dostat do nastaven\u00ed VTP serveru SW0, proto\u017ee, jak ji\u017e bylo zm\u00edn\u011bno, nastaven\u00ed VTP lze prov\u00e1d\u011bt pouze prost\u0159ednictv\u00edm serveru. Vstoup\u00edme do glob\u00e1ln\u00edch nastaven\u00ed konfigurace a zad\u00e1me p\u0159\u00edkaz vtp pruning. Vzhledem k tomu, \u017ee Packet Tracer je pouze simula\u010dn\u00ed program, v jeho n\u00e1pov\u011bd\u00e1ch pro p\u0159\u00edkazov\u00fd \u0159\u00e1dek nen\u00ed takov\u00fd p\u0159\u00edkaz. Kdy\u017e v\u0161ak zad\u00e1m vtp pruning a stisknu \"Enter\", syst\u00e9m ozn\u00e1m\u00ed, \u017ee re\u017eim vtp pruning nen\u00ed k dispozici.<\/p>\n

Pou\u017eit\u00edm p\u0159\u00edkazu show vtp status uvid\u00edme, \u017ee re\u017eim VTP Pruning je ve stavu disabled, a proto ho mus\u00edme zp\u0159\u00edstupnit p\u0159epnut\u00edm do polohy enable. T\u00edmto aktivujeme re\u017eim VTP Pruning na v\u0161ech t\u0159ech switchech na\u0161\u00ed s\u00edt\u011b v r\u00e1mci s\u00ed\u0165ov\u00e9 dom\u00e9ny.
\nDovolte mi p\u0159ipomenout, co je VTP Pruning. Kdy\u017e tento re\u017eim zapneme, switch-server SW0 informuje switch SW2, \u017ee na jeho portech je nastaven\u00e1 pouze s\u00ed\u0165 VLAN10. Pot\u00e9 switch SW2 informuje switch SW1, \u017ee nepot\u0159ebuje \u017e\u00e1dn\u00fd provoz krom\u011b provozu ur\u010den\u00e9ho pro s\u00ed\u0165 VLAN10. Nyn\u00ed d\u00edky VTP Pruning m\u00e1 switch SW1 informaci, \u017ee nemus\u00ed pos\u00edlat provoz VLAN20 p\u0159es trunk SW1-SW2. <\/p>\n

Pro v\u00e1s jako spr\u00e1vce s\u00edt\u011b je to velmi pohodln\u00e9. Nemus\u00edte ru\u010dn\u011b zad\u00e1vat p\u0159\u00edkazy, proto\u017ee switch je dost chytr\u00fd na to, aby pos\u00edlal pouze to, co pot\u0159ebuje konkr\u00e9tn\u00ed s\u00ed\u0165ov\u00e9 za\u0159\u00edzen\u00ed. Pokud z\u00edtra um\u00edst\u00edte v sousedn\u00ed budov\u011b dal\u0161\u00ed odd\u011blen\u00ed marketingu a p\u0159ipoj\u00edte jeho s\u00ed\u0165 VLAN20 k switchi SW2, tento switch okam\u017eit\u011b informuje switch SW1, \u017ee nyn\u00ed m\u00e1 s\u00edt\u011b VLAN10 a VLAN20, a po\u017e\u00e1d\u00e1 o p\u0159enos provozu pro ob\u011b s\u00edt\u011b. Tyto informace se neust\u00e1le aktualizuj\u00ed na v\u0161ech za\u0159\u00edzen\u00edch, co\u017e \u010din\u00ed komunikaci efektivn\u011bj\u0161\u00ed. <\/p>\n

\"Tr\u00e9nink
\n
\nExistuje je\u0161t\u011b jeden zp\u016fsob, jak konkretizovat p\u0159enos provozu \u2013 pou\u017e\u00edt p\u0159\u00edkaz, kter\u00fd povoluje p\u0159enos dat pouze pro danou VLAN. P\u0159ejdu do nastaven\u00ed switche SW1, kde m\u011b zaj\u00edm\u00e1 port Fa0\/4, a zad\u00e1m p\u0159\u00edkazy int fa0\/4 a switchport trunk allowed vlan. Jeliko\u017e u\u017e v\u00edm, \u017ee SW2 m\u00e1 pouze VLAN10, mohu switchem SW1 ur\u010dit, aby jeho trunkov\u00fd port propou\u0161t\u011bl pouze provoz pro tuto s\u00ed\u0165 aplikov\u00e1n\u00edm p\u0159\u00edkazu allowed vlan. T\u00edmto zp\u016fsobem jsem naprogramoval trunkov\u00fd port Fa0\/4 na p\u0159enos provozu pouze pro VLAN10. To znamen\u00e1, \u017ee tento port nepust\u00ed d\u00e1l provoz VLAN1, VLAN20 nebo jak\u00e9koli jin\u00e9 s\u00edt\u011b krom\u011b uveden\u00e9. <\/p>\n

M\u016f\u017eete se pt\u00e1t, co je lep\u0161\u00ed pou\u017e\u00edt \u2013 VTP Pruning nebo p\u0159\u00edkaz allowed vlan. Odpov\u011b\u010f je subjektivn\u00ed, proto\u017ee v n\u011bkter\u00fdch p\u0159\u00edpadech d\u00e1v\u00e1 smysl pou\u017e\u00edt prvn\u00ed zp\u016fsob, v jin\u00fdch druh\u00fd. Jako s\u00ed\u0165ov\u00fd administr\u00e1tor byste si m\u011bli vybrat optim\u00e1ln\u00ed \u0159e\u0161en\u00ed. V n\u011bkter\u00fdch p\u0159\u00edpadech m\u016f\u017ee b\u00fdt dobr\u00e9 naprogramovat port na propou\u0161t\u011bn\u00ed provozu ur\u010dit\u00e9 VLAN, v jin\u00fdch ne. V p\u0159\u00edpad\u011b na\u0161\u00ed s\u00edt\u011b m\u016f\u017ee b\u00fdt pou\u017eit\u00ed p\u0159\u00edkazu allowed vlan opodstatn\u011bn\u00e9, pokud nem\u00e1me v pl\u00e1nu m\u011bnit topologii s\u00edt\u011b. Ale pokud n\u011bkdo v budoucnu pl\u00e1nuje p\u0159idat k SW2 skupinu za\u0159\u00edzen\u00ed vyu\u017e\u00edvaj\u00edc\u00edch VLAN20, bylo by rozumn\u011bj\u0161\u00ed pou\u017e\u00edt m\u00f3d VTP Pruning. <\/p>\n

\"Tr\u00e9nink
\n
\nTak\u017ee konfigurace VTP Pruning spo\u010d\u00edv\u00e1 v pou\u017e\u00edv\u00e1n\u00ed n\u00e1sleduj\u00edc\u00edch p\u0159\u00edkaz\u016f. P\u0159\u00edkaz vtp pruning zaji\u0161\u0165uje automatick\u00e9 pou\u017eit\u00ed tohoto re\u017eimu. Pokud v\u0161ak chcete ru\u010dn\u011b nakonfigurovat VTP Pruning trunkov\u00e9ho portu na propou\u0161t\u011bn\u00ed provozu ur\u010dit\u00e9 VLAN, pou\u017eijete p\u0159\u00edkaz pro v\u00fdb\u011br \u010d\u00edsla trunkov\u00e9ho portu interface , zapnut\u00ed trunkov\u00e9ho re\u017eimu switchport mode trunk a povol\u00edte p\u0159enos provozu konkr\u00e9tn\u00ed s\u00edt\u011b pomoc\u00ed p\u0159\u00edkazu switchport trunk allowed vlan .<\/p>\n

V posledn\u00edm p\u0159\u00edkazu lze pou\u017e\u00edt 5 parametr\u016f. All znamen\u00e1, \u017ee je povolen p\u0159enos provozu v\u0161ech VLAN, none \u2013 p\u0159enos provozu pro v\u0161echny VLAN je zak\u00e1z\u00e1n. Pokud pou\u017eijete parametr add, m\u016f\u017eete p\u0159idat propou\u0161t\u011bn\u00ed provozu pro dal\u0161\u00ed s\u00ed\u0165. Nap\u0159\u00edklad, m\u00e1me povolen\u00fd provoz VLAN10 a pomoc\u00ed p\u0159\u00edkazu add m\u016f\u017eeme tak\u00e9 povolit propou\u0161t\u011bn\u00ed provozu s\u00edt\u011b VLAN20. P\u0159\u00edkaz remove umo\u017e\u0148uje odstranit jednu z VLAN, nap\u0159\u00edklad pokud pou\u017eijete parametr remove 20, z\u016fstane pouze p\u0159enos provozu VLAN10. <\/p>\n

Nyn\u00ed se pod\u00edv\u00e1me na native VLAN. Ji\u017e jsme zm\u00ednili, \u017ee native VLAN p\u0159edstavuje virtu\u00e1ln\u00ed s\u00ed\u0165 pro p\u0159enos netegovan\u00e9ho provozu p\u0159es konkr\u00e9tn\u00ed trunk port. <\/p>\n

\"Tr\u00e9nink
\n
\nP\u0159ejdu do nastaven\u00ed konkr\u00e9tn\u00edho portu, co\u017e ukazuje hlavi\u010dka p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku SW(config-if)#, a pou\u017eiji p\u0159\u00edkaz switchport trunk native vlan , nap\u0159\u00edklad VLAN10. Nyn\u00ed ve\u0161ker\u00fd provoz s\u00edt\u011b VLAN10 bude proch\u00e1zet p\u0159es trunk bez tag\u016f. <\/p>\n

Vra\u0165me se k logick\u00e9 topologii s\u00edt\u011b v okn\u011b Packet Tracer. Pokud pou\u017eiji p\u0159\u00edkaz switchport trunk native vlan 20 pro port switche Fa0\/4, ve\u0161ker\u00fd provoz s\u00edt\u011b VLAN20 projde trunkem Fa0\/4 \u2013 SW2 netegovan\u011b. Kdy\u017e switch SW2 obdr\u017e\u00ed tento provoz, pomysl\u00ed si: \u201eto je netegovan\u00fd provoz, tak\u017ee bych ho m\u011bl nasm\u011brovat do s\u00edt\u011b native VLAN\u201c. Pro tento switch je native VLAN s\u00ed\u0165 VLAN1. S\u00edt\u011b 1 a 20 nejsou nijak propojen\u00e9, ale proto\u017ee je pou\u017eit re\u017eim native VLAN, m\u00e1me mo\u017enost sm\u011brovat provoz VLAN20 do zcela jin\u00e9 s\u00edt\u011b. Tento provoz v\u0161ak bude nekapslovan\u00fd, a samotn\u00e9 s\u00edt\u011b mus\u00ed st\u00e1le odpov\u00eddat. <\/p>\n

Pod\u00edvejme se na to na p\u0159\u00edkladu. Vstoup\u00edm do nastaven\u00ed SW1 a pou\u017eiji p\u0159\u00edkaz switchport trunk native vlan 10. Nyn\u00ed ve\u0161ker\u00fd provoz VLAN10 bude vych\u00e1zet z trunk portu netegovan\u011b. A\u017e doraz\u00ed k trunk portu SW2, switch pochop\u00ed, \u017ee by ho m\u011bl nasm\u011brovat do VLAN1. V d\u016fsledku tohoto rozhodnut\u00ed nebude provoz schopen dos\u00e1hnout po\u010d\u00edta\u010d\u016f PC2, 3 a 4, kter\u00e9 jsou p\u0159ipojeny k access port\u016fm switche ur\u010den\u00fdm pro VLAN10. <\/p>\n

Technicky to vyvol\u00e1 zobrazen\u00ed zpr\u00e1vy syst\u00e9mu, \u017ee native VLAN portu Fa0\/4, kter\u00fd je sou\u010d\u00e1st\u00ed VLAN10, se neshoduje s portem Fa0\/1, kter\u00fd je sou\u010d\u00e1st\u00ed VLAN1. To znamen\u00e1, \u017ee uveden\u00e9 porty nebudou moci pracovat v re\u017eimu trunk kv\u016fli neshod\u011b native VLAN. <\/p>\n

\"Tr\u00e9nink
\n
\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 \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0438\u043c \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043d\u0438\u0435 VLAN \u0438 \u043e\u0431\u0441\u0443\u0434\u0438\u043c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b VTP, \u0430 \u0442\u0430\u043a\u0436\u0435 \u043f\u043e\u043d\u044f\u0442\u0438\u044f VTP Pruning \u0438 Native VLAN. \u0412 \u043e\u0434\u043d\u043e\u043c \u0438\u0437 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0445 \u0432\u0438\u0434\u0435\u043e \u043c\u044b \u0443\u0436\u0435 \u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438 \u043e VTP, \u0438 \u043f\u0435\u0440\u0432\u043e\u0435, \u0447\u0442\u043e \u0434\u043e\u043b\u0436\u043d\u043e \u043f\u0440\u0438\u0439\u0442\u0438 \u0432\u0430\u043c \u043d\u0430 \u0443\u043c, \u043a\u043e\u0433\u0434\u0430 \u0432\u044b \u0441\u043b\u044b\u0448\u0438\u0442\u0435 \u043e VTP, \u044d\u0442\u043e \u0442\u043e, \u0447\u0442\u043e \u043e\u043d \u043d\u0435 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u043c \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430, \u043d\u0435\u0441\u043c\u043e\u0442\u0440\u044f \u043d\u0430 \u0442\u043e, \u0447\u0442\u043e \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u00ab\u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u043c \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27786,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37066","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 14. VTP, Pruning a Native VLAN | ProHoster","description":"Dnes budeme pokra\u010dovat v prozkoum\u00e1v\u00e1n\u00ed VLAN a diskutovat o protokolu VTP, stejn\u011b jako o pojmech VTP Pruning a Native VLAN.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-vlan","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 14. VTP, Pruning \u0438 Native VLAN | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0438\u043c \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043d\u0438\u0435 VLAN \u0438 \u043e\u0431\u0441\u0443\u0434\u0438\u043c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b VTP, \u0430 \u0442\u0430\u043a\u0436\u0435 \u043f\u043e\u043d\u044f\u0442\u0438\u044f VTP Pruning \u0438 Native VLAN.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-vlan","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:15:33+00:00","article:modified_time":"2019-10-31T19:15:33+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37066","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-22 05:57:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:34:24","updated":"2026-01-22 05:57: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\/37066","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=37066"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37066\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/27786"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=37066"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=37066"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=37066"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}