{"id":35830,"date":"2019-10-31T22:06:40","date_gmt":"2019-10-31T19:06:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-11-osnovy-vlan\/"},"modified":"2019-10-31T22:06:40","modified_gmt":"2019-10-31T19:06:40","slug":"trening-cisco-200-125-ccna-v3-0-den-11-osnovy-vlan","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-11-osnovy-vlan","title":{"rendered":"Tr\u00e9nink Cisco 200-125 CCNA v3.0. Den 11. Z\u00e1klady VLAN","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ne\u017e za\u010dneme s z\u00e1klady VLAN, pros\u00edm, pozastavte toto video, klikn\u011bte na ikonu v lev\u00e9m doln\u00edm rohu, kde je naps\u00e1no Networking consultant, p\u0159ejd\u011bte na na\u0161i Facebook str\u00e1nku a dejte n\u00e1m tam like. Pot\u00e9 se vra\u0165te k videu a klikn\u011bte na ikonu Kr\u00e1le v prav\u00e9m doln\u00edm rohu, abyste se p\u0159ihl\u00e1sili k na\u0161emu ofici\u00e1ln\u00edmu kan\u00e1lu na YouTube. Pravideln\u011b p\u0159id\u00e1v\u00e1me nov\u00e9 s\u00e9rie, aktu\u00e1ln\u011b se jedn\u00e1 o kurz CCNA, pot\u00e9 pl\u00e1nujeme zah\u00e1jit kurz video lekc\u00ed CCNA Security, Network+, PMP, ITIL, Prince2 a publikovat tyto \u00fa\u017easn\u00e9 s\u00e9rie na na\u0161em kan\u00e1lu. <\/p>\n

Tak\u017ee dnes si pov\u00edme o z\u00e1kladech VLAN a odpov\u00edme na t\u0159i ot\u00e1zky: co je VLAN, pro\u010d pot\u0159ebujeme VLAN a jak ji nastavit. Douf\u00e1m, \u017ee po shl\u00e9dnut\u00ed t\u00e9to video lekce budete schopni odpov\u011bd\u011bt na v\u0161echny t\u0159i ot\u00e1zky.<\/a><\/noindex><\/p>\n

Co je VLAN? VLAN je zkratka pro \"virtu\u00e1ln\u00ed lok\u00e1ln\u00ed s\u00ed\u0165\". B\u011bhem na\u0161eho lekce si vysv\u011btl\u00edme, pro\u010d je tato s\u00ed\u0165 virtu\u00e1ln\u00ed, ale ne\u017e se dostaneme k VLAN, mus\u00edme pochopit, jak funguje switch. Je\u0161t\u011b jednou si zopakujeme n\u011bkter\u00e9 z ot\u00e1zek, kter\u00e9 jsme prob\u00edrali v p\u0159edchoz\u00edch lekc\u00edch. <\/p>\n

\"Tr\u00e9nink
\n
\nNejprve si pov\u00edme, co to je Multiple Collision Domain, nebo dom\u00e9na koliz\u00ed. V\u00edme, \u017ee tento switch s 48 porty m\u00e1 48 dom\u00e9n koliz\u00ed. To znamen\u00e1, \u017ee ka\u017ed\u00fd z t\u011bchto port\u016f nebo za\u0159\u00edzen\u00ed p\u0159ipojen\u00fdch k t\u011bmto port\u016fm m\u016f\u017ee komunikovat s jin\u00fdm za\u0159\u00edzen\u00edm na jin\u00e9m portu nez\u00e1visle na sob\u011b, ani\u017e by na sebe navz\u00e1jem m\u011bly vliv.<\/p>\n

V\u0161ech 48 port\u016f tohoto switche je sou\u010d\u00e1st\u00ed jedn\u00e9 \u0161irokop\u00e1smov\u00e9 dom\u00e9ny Broadcast Domain. To znamen\u00e1, \u017ee pokud je n\u011bkolik za\u0159\u00edzen\u00ed p\u0159ipojeno k n\u011bkolika port\u016fm a jedno z nich prov\u00e1d\u00ed \u0161irokop\u00e1smov\u00fd p\u0159enos, tak se tento p\u0159enos objev\u00ed na v\u0161ech portech, ke kter\u00fdm jsou p\u0159ipojena ostatn\u00ed za\u0159\u00edzen\u00ed. Takto funguje switch.<\/p>\n

To je jako kdyby lid\u00e9 sed\u011bli v jedn\u00e9 m\u00edstnosti bl\u00edzko sebe, a kdy\u017e jeden z nich n\u011bco nahlas \u0159\u00edk\u00e1, sly\u0161\u00ed ho v\u0161ichni ostatn\u00ed. Nicm\u00e9n\u011b, to je naprosto neefektivn\u00ed \u2013 \u010d\u00edm v\u00edce lid\u00ed se v m\u00edstnosti objev\u00ed, t\u00edm hlu\u010dn\u011bj\u0161\u00ed bude a p\u0159\u00edtomn\u00ed p\u0159estanou sly\u0161et jeden druh\u00e9ho. Podobn\u00e1 situace nast\u00e1v\u00e1 s po\u010d\u00edta\u010di \u2013 \u010d\u00edm v\u00edce za\u0159\u00edzen\u00ed se p\u0159ipojuje k jedn\u00e9 s\u00edti, t\u00edm v\u011bt\u0161\u00ed se st\u00e1v\u00e1 \"hlasitost\" \u0161irokop\u00e1smov\u00e9ho vys\u00edl\u00e1n\u00ed, co\u017e br\u00e1n\u00ed efektivn\u00ed komunikaci. <\/p>\n

V\u00edme, \u017ee pokud je jedno z t\u011bchto za\u0159\u00edzen\u00ed p\u0159ipojeno k s\u00edti 192.168.1.0\/24, v\u0161echna ostatn\u00ed za\u0159\u00edzen\u00ed jsou sou\u010d\u00e1st\u00ed t\u00e9\u017ee s\u00edt\u011b. Switch by m\u011bl b\u00fdt tak\u00e9 p\u0159ipojen ke stejn\u00e9 s\u00edti s t\u00edmto IP adresou. Ale zde m\u016f\u017ee switch jako za\u0159\u00edzen\u00ed druh\u00e9 \u00farovn\u011b OSI narazit na probl\u00e9m. Pokud jsou dv\u011b za\u0159\u00edzen\u00ed p\u0159ipojena k jedn\u00e9 s\u00edti, mohou snadno komunikovat navz\u00e1jem. P\u0159edstavme si, \u017ee v na\u0161\u00ed firm\u011b pracuje '\u0161patn\u00fd kluk', hacker, kter\u00e9ho jsem nakreslil naho\u0159e. Dole pod n\u00edm je m\u016fj po\u010d\u00edta\u010d. Tento hacker se m\u016f\u017ee snadno dostat do m\u00e9ho po\u010d\u00edta\u010de, proto\u017ee na\u0161e po\u010d\u00edta\u010de jsou sou\u010d\u00e1st\u00ed jedn\u00e9 s\u00edt\u011b. To je probl\u00e9m. <\/p>\n

\"Tr\u00e9nink
\n
\nPokud jsem sou\u010d\u00e1st\u00ed administrativy a tento nov\u00fd kluk bude m\u00edt p\u0159\u00edstup k soubor\u016fm na m\u00e9m po\u010d\u00edta\u010di, nebude to v\u016fbec dobr\u00e9. Samoz\u0159ejm\u011b, \u017ee na m\u00e9m po\u010d\u00edta\u010di je firewall, kter\u00fd chr\u00e1n\u00ed p\u0159ed mnoha hrozbami, ale hackerovi nebude d\u011blat probl\u00e9m ho obej\u00edt. <\/p>\n

Druh\u00e1 hrozba, kter\u00e1 existuje pro v\u0161echny \u010dleny t\u00e9to vys\u00edlac\u00ed dom\u00e9ny, spo\u010d\u00edv\u00e1 v tom, \u017ee pokud n\u011bkdo za\u017eije pot\u00ed\u017ee s vys\u00edl\u00e1n\u00edm, tento ru\u0161iv\u00fd sign\u00e1l ovlivn\u00ed ostatn\u00ed za\u0159\u00edzen\u00ed v s\u00edti. A\u010dkoli m\u016f\u017ee b\u00fdt v\u0161ech 48 port\u016f p\u0159ipojeno k r\u016fzn\u00fdm hostitel\u016fm, selh\u00e1n\u00ed jednoho hostitele ovlivn\u00ed zbyl\u00fdch 47, co\u017e rozhodn\u011b nechceme.
\nPro vy\u0159e\u0161en\u00ed tohoto probl\u00e9mu pou\u017e\u00edv\u00e1me koncept VLAN, neboli virtu\u00e1ln\u00ed lok\u00e1ln\u00ed s\u00ed\u0165. Funguje to velmi jednodu\u0161e, rozd\u011bluje tento velk\u00fd 48-portov\u00fd switch na n\u011bkolik men\u0161\u00edch switch\u016f. <\/p>\n

\"Tr\u00e9nink
\n
\nV\u00edme, \u017ee pods\u00edt\u011b d\u011bl\u00ed jednu velkou s\u00ed\u0165 na n\u011bkolik mal\u00fdch s\u00edt\u00ed, a VLAN funguje podobn\u011b. Rozd\u011bluje 48-portov\u00fd switch nap\u0159\u00edklad na 4 switche po 12 portech, z nich\u017e ka\u017ed\u00fd je sou\u010d\u00e1st\u00ed nov\u00e9 p\u0159ipojen\u00e9 s\u00edt\u011b. T\u00edmto zp\u016fsobem m\u016f\u017eeme pou\u017e\u00edt 12 port\u016f pro spr\u00e1vu, 12 port\u016f pro IP telefonii a tak d\u00e1le, tedy rozd\u011blit switch ne fyzicky, ale logicky, virtu\u00e1ln\u011b. <\/p>\n

Vybral jsem t\u0159i porty horn\u00edho switche ozna\u010den\u00e9 modrou barvou pro modrou s\u00ed\u0165 VLAN10 a t\u0159i oran\u017eov\u00e9 porty jsem ur\u010dil pro VLAN20. Takto ve\u0161ker\u00fd provoz z jednoho z t\u011bchto modr\u00fdch port\u016f bude sm\u011b\u0159ovat pouze na dal\u0161\u00ed modr\u00e9 porty, ani\u017e by se dot\u00fdkal ostatn\u00edch port\u016f tohoto switche. Podobn\u011b se bude \u0161\u00ed\u0159it provoz z oran\u017eov\u00fdch port\u016f, jakoby se pou\u017e\u00edvaly dva r\u016fzn\u00e9 fyzick\u00e9 switche. VLAN tedy slou\u017e\u00ed k rozd\u011blen\u00ed switche na n\u011bkolik switch\u016f pro r\u016fzn\u00e9 s\u00edt\u011b. <\/p>\n

Nakreslil jsem naho\u0159e dva switche, zde m\u00e1me situaci, kdy na lev\u00e9m switche jsou pou\u017e\u00edv\u00e1ny pouze modr\u00e9 porty pro jednu s\u00ed\u0165, a na prav\u00e9m pouze oran\u017eov\u00e9 pro jinou s\u00ed\u0165, a tyto switche nejsou nijak spojeny. <\/p>\n

P\u0159edpokl\u00e1dejme, \u017ee chcete vyu\u017e\u00edt v\u00edce port\u016f. P\u0159edstavme si, \u017ee m\u00e1me dv\u011b budovy, z nich\u017e ka\u017ed\u00e1 m\u00e1 sv\u016fj vlastn\u00ed spr\u00e1vn\u00ed t\u00fdm, a dva oran\u017eov\u00e9 porty doln\u00edho switche jsou pou\u017e\u00edv\u00e1ny pro spr\u00e1vu. Proto pot\u0159ebujeme, aby tyto porty byly spojeny se v\u0161emi oran\u017eov\u00fdmi porty ostatn\u00edch switch\u016f. Podobn\u00e1 situace plat\u00ed pro modr\u00e9 porty \u2013 v\u0161echny modr\u00e9 porty horn\u00edho switche mus\u00ed m\u00edt spojen\u00ed s ostatn\u00edmi porty stejn\u00e9 barvy. K tomu je pot\u0159eba fyzicky propojit tyto dva switche v r\u016fzn\u00fdch budov\u00e1ch samostatnou komunika\u010dn\u00ed linkou, na obr\u00e1zku je to linka mezi dv\u011bma porty zelen\u00e9 barvy. Jak v\u00edme, pokud jsou dva switche fyzicky propojeny, vznik\u00e1 n\u00e1m trunk. <\/p>\n

Jak\u00fd je tedy rozd\u00edl mezi b\u011b\u017en\u00fdm a VLAN switch? Rozd\u00edl nen\u00ed velk\u00fd. Kdy\u017e si koup\u00edte nov\u00fd switch, v\u0161echny porty jsou ve v\u00fdchoz\u00edm nastaven\u00ed nastaveny na re\u017eim VLAN a jsou sou\u010d\u00e1st\u00ed jedn\u00e9 s\u00edt\u011b, ozna\u010dovan\u00e9 jako VLAN1. Proto, kdy\u017e p\u0159ipoj\u00edte za\u0159\u00edzen\u00ed k jednomu portu, je spojeno se v\u0161emi ostatn\u00edmi porty, proto\u017ee v\u0161ech 48 port\u016f pat\u0159\u00ed do jedn\u00e9 virtu\u00e1ln\u00ed s\u00edt\u011b VLAN1. Pokud v\u0161ak nastav\u00edme modr\u00e9 porty na pr\u00e1ci v s\u00edti VLAN10, oran\u017eov\u00e9 \u2013 ve s\u00edti VLAN20 a zelen\u00e9 \u2013 VLAN1, z\u00edsk\u00e1me 3 r\u016fzn\u00e9 switche. Pou\u017eit\u00ed re\u017eimu virtu\u00e1ln\u00ed s\u00edt\u011b n\u00e1m tedy umo\u017e\u0148uje logicky seskupit porty pod konkr\u00e9tn\u00ed s\u00edt\u011b, rozd\u011blit rozhlasov\u00fd p\u0159enos na \u010d\u00e1sti a vytv\u00e1\u0159et pods\u00edt\u011b. Ka\u017ed\u00fd z port\u016f konkr\u00e9tn\u00ed barvy pat\u0159\u00ed do samostatn\u00e9 s\u00edt\u011b. Pokud modr\u00e9 porty budou fungovat v s\u00edti 192.168.1.0 a oran\u017eov\u00e9 porty budou fungovat v s\u00edti 192.168.1.0, i kdy\u017e maj\u00ed stejnou IP adresu, nebudou spojeny, proto\u017ee logicky pat\u0159\u00ed k r\u016fzn\u00fdm switch\u016fm. A jak v\u00edme, r\u016fzn\u00e9 fyzick\u00e9 switche si mezi sebou nekomunikuj\u00ed, pokud nejsou spojeny spole\u010dnou linkou. T\u00edmto zp\u016fsobem vytv\u00e1\u0159\u00edme r\u016fzn\u00e9 pods\u00edt\u011b pro r\u016fzn\u00e9 VLAN. <\/p>\n

\"Tr\u00e9nink
\n
\nChci zd\u016fraznit, \u017ee koncept VLAN se vztahuje pouze na switche. Ten, kdo zn\u00e1 protokoly enkapsulace, jako jsou .1Q nebo ISL, v\u00ed, \u017ee ani routery, ani po\u010d\u00edta\u010de nemaj\u00ed \u017e\u00e1dn\u00e9 VLAN. Kdy\u017e p\u0159ipoj\u00edte sv\u016fj po\u010d\u00edta\u010d nap\u0159\u00edklad k jednomu z modr\u00fdch port\u016f, nic na po\u010d\u00edta\u010di nem\u011bn\u00edte, v\u0161echny zm\u011bny se odehr\u00e1vaj\u00ed pouze na druh\u00e9 \u00farovni OSI, na \u00farovni switche. Kdy\u017e nastav\u00edme porty pro pr\u00e1ci s konkr\u00e9tn\u00ed s\u00edt\u00ed VLAN10 nebo VLAN20, switch vytv\u00e1\u0159\u00ed datab\u00e1zi VLAN. \"Zap\u00ed\u0161e\" si do pam\u011bti, \u017ee porty 1, 3 a 5 pat\u0159\u00ed do VLAN10, porty 14, 15 a 18 jsou sou\u010d\u00e1st\u00ed s\u00edt\u011b VLAN20 a ostatn\u00ed zapojen\u00e9 porty pat\u0159\u00ed do s\u00edt\u011b VLAN1. Proto, pokud n\u011bjak\u00fd traffic poch\u00e1z\u00ed z modr\u00e9ho portu 1, dost\u00e1v\u00e1 se pouze na porty 3 a 5 ve stejn\u00e9 s\u00edti VLAN10. Switch \"kouk\u00e1\" do sv\u00e9 datab\u00e1ze a vid\u00ed, \u017ee pokud traffic poch\u00e1z\u00ed z jednoho z oran\u017eov\u00fdch port\u016f, m\u011bl by b\u00fdt sm\u011brov\u00e1n pouze na oran\u017eov\u00e9 porty s\u00edt\u011b VLAN20. <\/p>\n

Po\u010d\u00edta\u010d v\u0161ak o t\u011bchto VLAN s\u00edt\u00edch nic nev\u00ed. Kdy\u017e spoj\u00edme 2 switche, mezi zelen\u00fdmi porty vznik\u00e1 trunk. Term\u00edn \u201etrunk\u201c je relevantn\u00ed pouze pro za\u0159\u00edzen\u00ed spole\u010dnosti Cisco, ostatn\u00ed v\u00fdrobci s\u00ed\u0165ov\u00fdch za\u0159\u00edzen\u00ed, jako je Juniper, pou\u017e\u00edvaj\u00ed term\u00edn Tag port, neboli \u201eozna\u010den\u00fd port\u201c. Domn\u00edv\u00e1m se, \u017ee n\u00e1zev Tag port je vhodn\u011bj\u0161\u00ed. Kdy\u017e z t\u00e9to s\u00edt\u011b vych\u00e1z\u00ed provoz, trunk ho p\u0159ed\u00e1v\u00e1 na v\u0161echny porty n\u00e1sleduj\u00edc\u00edho switche, tedy spojujeme dva 48-portov\u00e9 switche a z\u00edsk\u00e1v\u00e1me jeden 96-portov\u00fd switch. P\u0159i\u010dem\u017e, kdy\u017e pos\u00edl\u00e1me provoz z VLAN10, st\u00e1v\u00e1 se ozna\u010den\u00fdm, tedy je opat\u0159en \u0161t\u00edtkem, kter\u00fd ukazuje, \u017ee je ur\u010den pouze pro porty s\u00edt\u011b VLAN10. Druh\u00fd switch, p\u0159ijat\u00fd tento provoz, \u0161t\u00edtek p\u0159e\u010dte a pochop\u00ed, \u017ee jde o provoz pr\u00e1v\u011b pro s\u00ed\u0165 VLAN10 a m\u011bl by b\u00fdt sm\u011brov\u00e1n pouze na modr\u00e9 porty. Stejn\u011b tak je \u201eoran\u017eov\u00fd\u201c provoz pro VLAN20 opat\u0159en \u0161t\u00edtkem, kter\u00fd nazna\u010duje, \u017ee je ur\u010den pro porty VLAN20 druh\u00e9ho switche. <\/p>\n

Tak\u00e9 jsme se zm\u00ednili o enkapsulaci a zde existuj\u00ed dva metody enkapsulace. Prvn\u00ed je .1Q, co\u017e znamen\u00e1, \u017ee kdy\u017e organizujeme trunk, mus\u00edme zajistit enkapsulaci. Protokol enkapsulace .1Q je otev\u0159en\u00fd standard popisuj\u00edc\u00ed proceduru ozna\u010dov\u00e1n\u00ed provozu. Existuje tak\u00e9 jin\u00fd protokol s n\u00e1zvem ISL, Inter-Switch link, vyvinut\u00fd spole\u010dnost\u00ed Cisco, kter\u00fd ukazuje na p\u0159\u00edslu\u0161nost provozu k ur\u010dit\u00e9 VLAN. V\u0161echny modern\u00ed switche pracuj\u00ed s protokolem .1Q, proto, kdy\u017e dod\u00e1te nov\u00fd switch z krabice, nemus\u00edte pou\u017e\u00edvat \u017e\u00e1dn\u00e9 p\u0159\u00edkazy pro enkapsulaci, proto\u017ee defaultn\u011b je prov\u00e1d\u011bna protokolem .1Q. Tak\u017ee po vytvo\u0159en\u00ed trunku prob\u00edh\u00e1 enkapsulace provozu automaticky, co\u017e umo\u017e\u0148uje \u010dten\u00ed \u0161t\u00edtk\u016f. <\/p>\n

Nyn\u00ed p\u0159istupme k nastavov\u00e1n\u00ed s\u00edt\u011b VLAN. Vytvo\u0159\u00edme s\u00ed\u0165, ve kter\u00e9 budou 2 switche a dv\u011b koncov\u00e1 za\u0159\u00edzen\u00ed \u2013 po\u010d\u00edta\u010de PC1 a PC2, kter\u00e9 spoj\u00edme kabely se switchem #0. Za\u010dneme s z\u00e1kladn\u00edmi nastaven\u00edmi switche Basic Configuration.<\/p>\n

\"Tr\u00e9nink
\n
\nPro to klikneme na swit\u010d a dostaneme se do rozhran\u00ed p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku, kde nastav\u00edme n\u00e1zev hostitele a pojmenujeme tento swit\u010d sw1. Nyn\u00ed p\u0159ejdeme k nastaven\u00ed prvn\u00edho po\u010d\u00edta\u010de a p\u0159i\u0159ad\u00edme mu statickou IP adresu 192.168.1.1 a masku pods\u00edt\u011b 255.255.255.0. Adresa v\u00fdchoz\u00ed br\u00e1ny nen\u00ed pot\u0159eba, proto\u017ee v\u0161echna na\u0161e za\u0159\u00edzen\u00ed jsou ve stejn\u00e9 s\u00edti. Pot\u00e9 provedeme tot\u00e9\u017e pro druh\u00fd po\u010d\u00edta\u010d a p\u0159i\u0159ad\u00edme mu IP adresu 192.168.1.2. <\/p>\n

Nyn\u00ed se vr\u00e1t\u00edme k prvn\u00edmu po\u010d\u00edta\u010di, abychom pingovali druh\u00fd po\u010d\u00edta\u010d. Jak vid\u00edme, pingov\u00e1n\u00ed prob\u011bhlo \u00fasp\u011b\u0161n\u011b, proto\u017ee oba po\u010d\u00edta\u010de jsou p\u0159ipojeny k jednomu swit\u010di a jsou sou\u010d\u00e1st\u00ed stejn\u00e9 s\u00edt\u011b ve v\u00fdchoz\u00edm VLAN1. Pokud se nyn\u00ed pod\u00edv\u00e1me na rozhran\u00ed switche, uvid\u00edme, \u017ee v\u0161echny porty FastEthernet od 1 do 24 a dva porty GigabitEthernet jsou nastaveny na VLAN #1. Takov\u00e1 nadm\u011brn\u00e1 dostupnost v\u0161ak nen\u00ed pot\u0159eba, proto vstoup\u00edme do nastaven\u00ed switche a zad\u00e1me p\u0159\u00edkaz show vlan, abychom se pod\u00edvali na datab\u00e1zi virtu\u00e1ln\u00edch s\u00edt\u00ed. <\/p>\n

\"Tr\u00e9nink
\n
\nVid\u00edte zde n\u00e1zev s\u00edt\u011b VLAN1 a to, \u017ee v\u0161echny porty switche pat\u0159\u00ed do t\u00e9to s\u00edt\u011b. To znamen\u00e1, \u017ee se m\u016f\u017eete p\u0159ipojit k libovoln\u00e9mu portu a v\u0161echny budou schopny \u201ekomunikovat\u201c mezi sebou, proto\u017ee jsou sou\u010d\u00e1st\u00ed jedn\u00e9 s\u00edt\u011b.<\/p>\n

Zm\u011bn\u00edme tuto situaci, a to tak, \u017ee nejprve vytvo\u0159\u00edme dv\u011b virtu\u00e1ln\u00ed s\u00edt\u011b, tedy p\u0159id\u00e1me VLAN10. K vytvo\u0159en\u00ed virtu\u00e1ln\u00ed s\u00edt\u011b se pou\u017e\u00edv\u00e1 p\u0159\u00edkaz typu \u201evlan \u010d\u00edslo s\u00edt\u011b\u201c.
\nJak vid\u00edte, p\u0159i pokusu o vytvo\u0159en\u00ed s\u00edt\u011b syst\u00e9m vydal zpr\u00e1vu se seznamem p\u0159\u00edkaz\u016f konfigurace VLAN, kter\u00e9 je t\u0159eba pou\u017e\u00edt pro tuto akci: <\/p>\n

exit \u2013 aplikovat zm\u011bny a opustit nastaven\u00ed;
\nname \u2013 zadat u\u017eivatelsk\u00fd n\u00e1zev VLAN;
\nno \u2013 zru\u0161it p\u0159\u00edkaz nebo nastavit jej na v\u00fdchoz\u00ed hodnotu. <\/p>\n

To znamen\u00e1, \u017ee p\u0159ed t\u00edm, ne\u017e zad\u00e1te p\u0159\u00edkaz pro vytvo\u0159en\u00ed VLAN, je pot\u0159eba zadat p\u0159\u00edkaz name, kter\u00fd p\u0159epne do re\u017eimu spr\u00e1vy n\u00e1zv\u016f, a pot\u00e9 p\u0159ej\u00edt k vytvo\u0159en\u00ed nov\u00e9 s\u00edt\u011b. Syst\u00e9m p\u0159itom vyd\u00e1 n\u00e1pov\u011bdu, \u017ee \u010d\u00edslo s\u00edt\u011b VLAN m\u016f\u017ee b\u00fdt v rozmez\u00ed od 1 do 1005.
\nTe\u010f tedy zad\u00e1v\u00e1me p\u0159\u00edkaz pro vytvo\u0159en\u00ed s\u00edt\u011b VLAN \u010d\u00edslo 20 \u2013 vlan 20 a pak p\u0159i\u0159ad\u00edme u\u017eivatelsk\u00e9 jm\u00e9no, kter\u00e9 ukazuje, co to je za s\u00ed\u0165. V na\u0161em p\u0159\u00edpad\u011b pou\u017eijeme p\u0159\u00edkaz name Employees, nebo s\u00ed\u0165 pro zam\u011bstnance spole\u010dnosti. <\/p>\n

\"Tr\u00e9nink
\n
\nNyn\u00ed mus\u00edme p\u0159i\u0159adit konkr\u00e9tn\u00ed port t\u00e9to VLAN. Vstupujeme do re\u017eimu nastaven\u00ed p\u0159ep\u00edna\u010de int f0\/1, pot\u00e9 ru\u010dn\u011b nastav\u00edme port na re\u017eim Access pomoc\u00ed p\u0159\u00edkazu switchport mode access a ur\u010d\u00edme, kter\u00fd port m\u00e1 b\u00fdt do tohoto re\u017eimu p\u0159eveden \u2013 to je port pro s\u00ed\u0165 VLAN10. <\/p>\n

\"Tr\u00e9nink
\n
\nVid\u00edme, \u017ee po t\u00e9to zm\u011bn\u011b barva spojen\u00ed PC0 a p\u0159ep\u00edna\u010de, barva portu, zm\u011bnila z zelen\u00e9 na oran\u017eovou. Op\u011bt se stane zelenou, jakmile se zm\u011bny nastaven\u00ed projev\u00ed. Pokus\u00edme se prov\u00e9st ping na druh\u00fd po\u010d\u00edta\u010d. Neprov\u00e1d\u011bli jsme \u017e\u00e1dn\u00e9 zm\u011bny v nastaven\u00ed s\u00edt\u011b pro po\u010d\u00edta\u010de, st\u00e1le maj\u00ed IP adresy 192.168.1.1 a 192.168.1.2. Ale kdy\u017e se pokus\u00edme z po\u010d\u00edta\u010de PC0 pingnout po\u010d\u00edta\u010d PC1, nic se n\u00e1m nepoda\u0159\u00ed, proto\u017ee nyn\u00ed tyto po\u010d\u00edta\u010de pat\u0159\u00ed do r\u016fzn\u00fdch s\u00edt\u00ed: prvn\u00ed do VLAN10, druh\u00fd do nativn\u00ed VLAN1. <\/p>\n

Vr\u00e1t\u00edme se k rozhran\u00ed p\u0159ep\u00edna\u010de a nastav\u00edme druh\u00fd port. K tomu zad\u00e1m p\u0159\u00edkaz int f0\/2 a zopakuji pro s\u00ed\u0165 VLAN 20 ty sam\u00e9 kroky, kter\u00e9 jsem u\u010dinil p\u0159i nastavov\u00e1n\u00ed p\u0159edchoz\u00ed virtu\u00e1ln\u00ed s\u00edt\u011b.
\nVid\u00edme, \u017ee nyn\u00ed doln\u00ed port p\u0159ep\u00edna\u010de, ke kter\u00e9mu je p\u0159ipojen druh\u00fd po\u010d\u00edta\u010d, tak\u00e9 zm\u011bnil svou barvu z zelen\u00e9 na oran\u017eovou \u2013 bude trvat n\u011bkolik sekund, ne\u017e se zm\u011bny v nastaven\u00ed projev\u00ed a op\u011bt se stane zelen\u00fdm. Pokud znovu spust\u00edme pingov\u00e1n\u00ed druh\u00e9ho po\u010d\u00edta\u010de, nic se n\u00e1m nepoda\u0159\u00ed, proto\u017ee po\u010d\u00edta\u010de st\u00e1le pat\u0159\u00ed do r\u016fzn\u00fdch s\u00edt\u00ed, pouze PC1 nyn\u00ed pat\u0159\u00ed nikoli do VLAN1, ale do VLAN20.
\nT\u00edmto jste rozd\u011blili jeden fyzick\u00fd p\u0159ep\u00edna\u010d na dva r\u016fzn\u00e9 logick\u00e9 p\u0159ep\u00edna\u010de. Vid\u00edte, \u017ee nyn\u00ed barva portu zm\u011bnila z oran\u017eov\u00e9 na zelenou, port funguje, ale st\u00e1le se nepinge, proto\u017ee pat\u0159\u00ed do jin\u00e9 s\u00edt\u011b. <\/p>\n

U\u010din\u00edme zm\u011bny v na\u0161em sch\u00e9matu \u2013 odpoj\u00edme po\u010d\u00edta\u010d PC1 od prvn\u00edho p\u0159ep\u00edna\u010de a p\u0159ipoj\u00edme ho k druh\u00e9mu p\u0159ep\u00edna\u010di, a p\u0159ep\u00edna\u010de propoj\u00edme kabelem.<\/p>\n

\"Tr\u00e9nink
\n
\nAby ustanowi\u0107 mi\u0119dzy nimi po\u0142\u0105czenie, wejd\u0119 w ustawienia drugiego prze\u0142\u0105cznika i stworz\u0119 VLAN10, nadaj\u0105c jej nazw\u0119 'Zarz\u0105dzanie', czyli sie\u0107 zarz\u0105dzania. Nast\u0119pnie w\u0142\u0105cz\u0119 tryb Access i wska\u017c\u0119, \u017ce ten tryb jest przeznaczony dla sieci VLAN10. Teraz kolor port\u00f3w, przez kt\u00f3re po\u0142\u0105czone s\u0105 prze\u0142\u0105czniki, zmieni\u0142 si\u0119 z pomara\u0144czowego na zielony, poniewa\u017c oba s\u0105 skonfigurowane na VLAN10. Teraz musimy stworzy\u0107 trunk mi\u0119dzy obiema prze\u0142\u0105cznikami. Oba te porty to Fa0\/2, dlatego nale\u017cy utworzy\u0107 trunk dla portu Fa0\/2 pierwszego prze\u0142\u0105cznika, u\u017cywaj\u0105c polecenia 'switchport mode trunk'. To samo nale\u017cy wykona\u0107 dla drugiego prze\u0142\u0105cznika, po czym mi\u0119dzy tymi dwoma portami powstanie trunk.<\/p>\n

Teraz, je\u015bli zechc\u0119 pingowa\u0107 z pierwszego komputera komputer PC1, wszystko zadzia\u0142a, poniewa\u017c po\u0142\u0105czenie mi\u0119dzy PC0 a prze\u0142\u0105cznikiem #0 to sie\u0107 VLAN10, pomi\u0119dzy prze\u0142\u0105cznikiem #1 a PC1 te\u017c jest VLAN10, a oba prze\u0142\u0105czniki s\u0105 po\u0142\u0105czone trunkiem. <\/p>\n

Tak wi\u0119c, je\u015bli urz\u0105dzenia znajduj\u0105 si\u0119 w r\u00f3\u017cnych sieciach VLAN, nie s\u0105 ze sob\u0105 po\u0142\u0105czone, natomiast je\u015bli s\u0105 w tej samej sieci, mo\u017cliwa jest swobodna wymiana ruchu mi\u0119dzy nimi. Spr\u00f3bujmy doda\u0107 do ka\u017cdego prze\u0142\u0105cznika jeszcze jedno urz\u0105dzenie. <\/p>\n

\"Tr\u00e9nink
\n
\nW ustawieniach sieci dodanego komputera PC2 ustawi\u0119 adres IP 192.168.2.1, a w ustawieniach PC3 \u2013 adres 192.168.2.2. Przy tym porty, do kt\u00f3rych pod\u0142\u0105czone s\u0105 te dwa PC, otrzymaj\u0105 oznaczenie Fa0\/3. W ustawieniach prze\u0142\u0105cznika #0 ustawimy tryb Access i wska\u017cemy, \u017ce dany port jest przeznaczony dla VLAN20, to samo zrobimy dla prze\u0142\u0105cznika #1.<\/p>\n

Je\u015bli u\u017cyj\u0119 polecenia 'switchport access vlan 20', a sie\u0107 VLAN20 jeszcze nie zosta\u0142a utworzona, system wy\u015bwietli b\u0142\u0105d typu 'Access VLAN does not exist', poniewa\u017c prze\u0142\u0105czniki s\u0105 skonfigurowane tylko do pracy z VLAN10.<\/p>\n

Stw\u00f3rzmy VLAN20. U\u017cyj\u0119 polecenia 'show vlan', aby zobaczy\u0107 baz\u0119 danych wirtualnych sieci. <\/p>\n

\"Tr\u00e9nink
\n
\nWidzicie, \u017ce domy\u015bln\u0105 sieci\u0105 jest VLAN1, do kt\u00f3rej pod\u0142\u0105czone s\u0105 porty od Fa0\/4 do Fa0\/24 oraz Gig0\/1, Gig0\/2. Wirtualna sie\u0107 pod numerem 10 o nazwie Zarz\u0105dzanie jest pod\u0142\u0105czona do portu Fa0\/1, a sie\u0107 VLAN pod numerem 20 o domy\u015blnej nazwie VLAN0020 jest pod\u0142\u0105czona do portu Fa0\/3. <\/p>\n

V podstat\u011b nen\u00ed d\u016fle\u017eit\u00e9, jak se s\u00ed\u0165 jmenuje, hlavn\u011b aby se neopakovala pro r\u016fzn\u00e9 s\u00edt\u011b. Pokud chci zm\u011bnit jm\u00e9no s\u00edt\u011b, kter\u00e9 syst\u00e9m automaticky p\u0159i\u0159azuje, pou\u017e\u00edv\u00e1m p\u0159\u00edkaz vlan 20 a name Employees. Mohu toto jm\u00e9no zm\u011bnit na jin\u00e9, nap\u0159\u00edklad na IPphones, a pokud pingneme IP adresu 192.168.2.2, uvid\u00edme, \u017ee jm\u00e9no VLAN skute\u010dn\u011b nem\u00e1 \u017e\u00e1dn\u00fd v\u00fdznam.
\nPosledn\u00ed v\u011bc, kterou chci zm\u00ednit, je p\u0159i\u0159azen\u00ed Management IP, o kter\u00e9m jsme hovo\u0159ili na posledn\u00ed lekci. K tomu pou\u017e\u00edv\u00e1me p\u0159\u00edkaz int vlan1 a zad\u00e1me IP adresu 10.1.1.1 a masku pods\u00edt\u011b 255.255.255.0, pot\u00e9 p\u0159id\u00e1me p\u0159\u00edkaz no shutdown. P\u0159i\u0159adili jsme Management IP ne pro cel\u00fd switch, ale pouze pro porty VLAN1, tedy jsme p\u0159i\u0159adili IP adresu, ze kter\u00e9 se spravuje s\u00ed\u0165 VLAN1. Pokud chceme spravovat VLAN2, mus\u00edme vytvo\u0159it odpov\u00eddaj\u00edc\u00ed rozhran\u00ed pro VLAN2. V na\u0161em p\u0159\u00edpad\u011b m\u00e1me modr\u00e9 porty VLAN10 a oran\u017eov\u00e9 porty VLAN20, kter\u00fdm odpov\u00eddaj\u00ed adresy 192.168.1.0 a 192.168.2.0.
\nVLAN10 mus\u00ed m\u00edt adresy, kter\u00e9 jsou v tomto rozsahu, aby se k n\u00ed mohly p\u0159ipojit odpov\u00eddaj\u00edc\u00ed za\u0159\u00edzen\u00ed. Podobn\u00e9 nastaven\u00ed mus\u00ed b\u00fdt provedeno i pro VLAN20. <\/p>\n

V tomto okn\u011b p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku switche jsou zobrazeny nastaven\u00ed rozhran\u00ed pro VLAN1, tedy native VLAN. <\/p>\n

\"Tr\u00e9nink
\n
\nPro nastaven\u00ed Management IP pro VLAN10 mus\u00edme vytvo\u0159it rozhran\u00ed int vlan 10 a pot\u00e9 p\u0159idat IP adresu 192.168.1.10 a masku pods\u00edt\u011b 255.255.255.0. <\/p>\n

Pro nastaven\u00ed VLAN20, mus\u00edme vytvo\u0159it rozhran\u00ed int vlan 20 a pot\u00e9 p\u0159idat IP adresu 192.168.2.10 a masku pods\u00edt\u011b 255.255.255.0. <\/p>\n

\"Tr\u00e9nink
\n
\nPro\u010d je to pot\u0159eba? Pokud po\u010d\u00edta\u010d PC0 a horn\u00ed lev\u00fd port switche #0 pat\u0159\u00ed do s\u00edt\u011b 192.168.1.0, PC2 pat\u0159\u00ed do s\u00edt\u011b 192.168.2.0 a je p\u0159ipojen k portu native VLAN1, kter\u00fd pat\u0159\u00ed do s\u00edt\u011b 10.1.1.1, pak PC0 nem\u016f\u017ee nav\u00e1zat spojen\u00ed s t\u00edmto switchem p\u0159es protokol SSH, proto\u017ee pat\u0159\u00ed do r\u016fzn\u00fdch s\u00edt\u00ed. Proto, aby PC0 mohl komunikovat se switchem p\u0159es protokol SSH nebo Telnet, mus\u00edme mu poskytnout p\u0159\u00edstup Access. To je d\u016fvod, pro\u010d pot\u0159ebujeme spr\u00e1vu s\u00edt\u011b. <\/p>\n

Mus\u00edme m\u00edt mo\u017enost propojit PC0 pomoc\u00ed SSH nebo Telnet s IP adresou rozhran\u00ed VLAN20 a prov\u00e9st jak\u00e9koliv pot\u0159ebn\u00e9 zm\u011bny p\u0159es SSH. T\u00edmto zp\u016fsobem je Management IP nezbytn\u00e9 pr\u00e1v\u011b pro nastaven\u00ed VLAN, proto\u017ee ka\u017ed\u00e1 virtu\u00e1ln\u00ed s\u00ed\u0165 mus\u00ed m\u00edt svou vlastn\u00ed spr\u00e1vu p\u0159\u00edstupu. <\/p>\n

V dne\u0161n\u00edm videu jsme probrali mnoho ot\u00e1zek: z\u00e1kladn\u00ed nastaven\u00ed switche, vytv\u00e1\u0159en\u00ed VLAN s\u00edt\u00ed, p\u0159i\u0159azen\u00ed VLAN port\u016f, p\u0159i\u0159azen\u00ed Management IP pro VLAN s\u00edt\u011b a nastaven\u00ed trunk\u016f. Nezlobte se, pokud jste n\u011bco nepochopili, je to p\u0159irozen\u00e9, proto\u017ee VLAN je velmi slo\u017eit\u00e9 a rozs\u00e1hl\u00e9 t\u00e9ma, ke kter\u00e9mu se vr\u00e1t\u00edme v p\u0159\u00ed\u0161t\u00edch lekc\u00edch. Garantuj\u00ed v\u00e1m, \u017ee s moj\u00ed pomoc\u00ed se stanete \"mistry\" VLAN, ale smyslem t\u00e9to lekce bylo objasnit v\u00e1m 3 ot\u00e1zky: co jsou VLAN s\u00edt\u011b, pro\u010d je pot\u0159ebujeme a jak je nastavit. <\/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":"

\u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043c\u044b \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u043e\u0441\u043d\u043e\u0432\u0430\u043c VLAN, \u044f \u0431\u044b \u043f\u043e\u043f\u0440\u043e\u0441\u0438\u043b \u0432\u0441\u0435\u0445 \u0432\u0430\u0441 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u044d\u0442\u043e \u0432\u0438\u0434\u0435\u043e \u043d\u0430 \u043f\u0430\u0443\u0437\u0443, \u043d\u0430\u0436\u0430\u0442\u044c \u043d\u0430 \u0438\u043a\u043e\u043d\u043a\u0443 \u0432 \u043d\u0438\u0436\u043d\u0435\u043c \u043b\u0435\u0432\u043e\u043c \u0443\u0433\u043b\u0443, \u0433\u0434\u0435 \u043d\u0430\u043f\u0438\u0441\u0430\u043d\u043e Networking consultant, \u0437\u0430\u0439\u0442\u0438 \u043d\u0430 \u043d\u0430\u0448\u0443 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0443 Facebook \u0438 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u0442\u0430\u043c \u043b\u0430\u0439\u043a. \u0417\u0430\u0442\u0435\u043c \u0432\u0435\u0440\u043d\u0438\u0442\u0435\u0441\u044c \u043a \u0432\u0438\u0434\u0435\u043e \u0438 \u043d\u0430\u0436\u043c\u0438\u0442\u0435 \u043d\u0430 \u0438\u043a\u043e\u043d\u043a\u0443 King \u0432 \u043f\u0440\u0430\u0432\u043e\u043c \u043d\u0438\u0436\u043d\u0435\u043c \u0443\u0433\u043b\u0443, \u0447\u0442\u043e\u0431\u044b \u043f\u043e\u0434\u043f\u0438\u0441\u0430\u0442\u044c\u0441\u044f \u043d\u0430 \u043d\u0430\u0448 \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0439 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-35830","post","type-post","status-publish","format-standard","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\u0160kolen\u00ed Cisco 200-125 CCNA v3.0. Den 11. Z\u00e1klady VLAN | ProHoster","description":"Ne\u017e se pust\u00edme do z\u00e1klad\u016f VLAN, r\u00e1d bych v\u00e1s po\u017e\u00e1dal, abyste toto video pozastavili, klikli na ikonu v lev\u00e9m doln\u00edm rohu, kde je naps\u00e1no Networking consultant, nav\u0161t\u00edvili na\u0161i Facebook str\u00e1nku a dali tam like.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-11-osnovy-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 11. \u041e\u0441\u043d\u043e\u0432\u044b VLAN | ProHoster","og:description":"\u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043c\u044b \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u043e\u0441\u043d\u043e\u0432\u0430\u043c VLAN, \u044f \u0431\u044b \u043f\u043e\u043f\u0440\u043e\u0441\u0438\u043b \u0432\u0441\u0435\u0445 \u0432\u0430\u0441 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u044d\u0442\u043e \u0432\u0438\u0434\u0435\u043e \u043d\u0430 \u043f\u0430\u0443\u0437\u0443, \u043d\u0430\u0436\u0430\u0442\u044c \u043d\u0430 \u0438\u043a\u043e\u043d\u043a\u0443 \u0432 \u043d\u0438\u0436\u043d\u0435\u043c \u043b\u0435\u0432\u043e\u043c \u0443\u0433\u043b\u0443, \u0433\u0434\u0435 \u043d\u0430\u043f\u0438\u0441\u0430\u043d\u043e Networking consultant, \u0437\u0430\u0439\u0442\u0438 \u043d\u0430 \u043d\u0430\u0448\u0443 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0443 Facebook \u0438 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u0442\u0430\u043c.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-11-osnovy-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:06:40+00:00","article:modified_time":"2019-10-31T19:06:40+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35830","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 00:57:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:55:26","updated":"2026-01-22 00: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\/35830","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=35830"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/35830\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=35830"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=35830"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=35830"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}