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

Dne\u0161n\u00ed lekci v\u011bnujeme nastaven\u00ed VLAN, tedy se pokus\u00edme prov\u00e9st v\u0161echno, o \u010dem jsme hovo\u0159ili v p\u0159edchoz\u00edch lekc\u00edch. Nyn\u00ed se zam\u011b\u0159\u00edme na 3 ot\u00e1zky: vytvo\u0159en\u00ed VLAN, p\u0159id\u011blen\u00ed port\u016f VLAN a prohl\u00ed\u017een\u00ed datab\u00e1ze VLAN.<\/p>\n

Otev\u0159eme okno programu Cisco Packet Tracer s logickou topologi\u00ed na\u0161\u00ed s\u00edt\u011b, kterou jsem nakreslil. <\/p>\n

\"Tr\u00e9nink
\n
\nK prvn\u00edmu switche SW0 jsou p\u0159ipojena 2 po\u010d\u00edta\u010de PC0 a PC1, kter\u00e9 jsou spojeny do s\u00edt\u011b VLAN10 s rozsahy IP adres 192.168.10.0\/24. Odpov\u00eddaj\u00edc\u00ed IP adresy t\u011bchto po\u010d\u00edta\u010d\u016f budou 192.168.10.1 a 192.168.10.2. Obvykle lid\u00e9 identifikuj\u00ed \u010d\u00edslo VLAN podle t\u0159et\u00edho oktetu IP adresy, v na\u0161em p\u0159\u00edpad\u011b je to 10, nicm\u00e9n\u011b to nen\u00ed povinn\u00e9 ozna\u010den\u00ed s\u00edt\u00ed, m\u016f\u017eete p\u0159id\u011blit jak\u00fdkoli identifik\u00e1tor VLAN, av\u0161ak tento po\u0159\u00e1dek je p\u0159ijat v velk\u00fdch spole\u010dnostech, proto\u017ee usnad\u0148uje nastaven\u00ed s\u00edt\u011b. <\/p>\n

D\u00e1le je um\u00edst\u011bn switch SW1, kter\u00fd je p\u0159ipojen k s\u00edti VLAN20 s IP adresou 192.168.20.0\/24 a s dv\u011bma notebooky Laptop1 a Laptop2.<\/a><\/noindex><\/p>\n

VLAN10 se nach\u00e1z\u00ed v 1. pat\u0159e kancel\u00e1\u0159e spole\u010dnosti a p\u0159edstavuje s\u00ed\u0165 veden\u00ed odd\u011blen\u00ed prodeje. K tomuto switchi SW0 je p\u0159ipojen notebook Laptop0 market\u00e9ra, kter\u00fd pat\u0159\u00ed do VLAN20. Tato s\u00ed\u0165 se roz\u0161i\u0159uje do 2. patra, kde se nach\u00e1zej\u00ed dal\u0161\u00ed zam\u011bstnanci, a je spojena s odd\u011blen\u00edm prodeje, kter\u00e9 m\u016f\u017ee b\u00fdt um\u00edst\u011bno v jin\u00e9 budov\u011b nebo ve 3. pat\u0159e t\u00e9\u017ee kancel\u00e1\u0159e. Zde jsou je\u0161t\u011b 3 po\u010d\u00edta\u010de \u2013 PC2,3 a 4, kter\u00e9 jsou sou\u010d\u00e1st\u00ed s\u00edt\u011b VLAN10.<\/p>\n

S\u00ed\u0165 VLAN10, stejn\u011b jako VLAN20, by m\u011bla zaji\u0161\u0165ovat nep\u0159eru\u0161enou komunikaci v\u0161ech zam\u011bstnanc\u016f, a\u0165 u\u017e se nach\u00e1zej\u00ed na r\u016fzn\u00fdch podla\u017e\u00edch nebo v r\u016fzn\u00fdch budov\u00e1ch. Takovou koncepci s\u00edt\u011b dnes probereme. <\/p>\n

Poj\u010fme se pustit do jej\u00edho nastaven\u00ed a za\u010dneme po\u010d\u00edta\u010dem PC0. Kliknut\u00edm na ikonu vstoup\u00edme do nastaven\u00ed s\u00edt\u011b po\u010d\u00edta\u010de a zad\u00e1me IP adresu 192.168.10.1 a masku pods\u00edt\u011b 255.255.255.0. Nezad\u00e1v\u00e1m adresu v\u00fdchoz\u00ed br\u00e1ny, proto\u017ee ta je pot\u0159ebn\u00e1 pro p\u0159\u00edstup z jedn\u00e9 lok\u00e1ln\u00ed s\u00edt\u011b do druh\u00e9, a v na\u0161em p\u0159\u00edpad\u011b se nebudeme zab\u00fdvat nastaven\u00edm 3. \u00farovn\u011b OSI, zaj\u00edm\u00e1 n\u00e1s pouze \u00farove\u0148 2, a nebudeme zkoumat sm\u011brov\u00e1n\u00ed provozu do jin\u00e9 s\u00edt\u011b. <\/p>\n

\"Tr\u00e9nink
\n
\nChyst\u00e1me se nastavit intranet a pouze ty hosty, kter\u00e9 do n\u011bj pat\u0159\u00ed. Pot\u00e9 p\u0159ejdeme k po\u010d\u00edta\u010di PC2 a ud\u011bl\u00e1me to sam\u00e9, co pro prvn\u00ed PC. Nyn\u00ed zkontrolujeme, zda mohu pingnout PC1 z po\u010d\u00edta\u010de PC0. Jak vid\u00edte, ping prob\u00edh\u00e1 a po\u010d\u00edta\u010d s IP adresou 192.168.10.2 bez probl\u00e9m\u016f vrac\u00ed pakety. T\u00edmto jsme \u00fasp\u011b\u0161n\u011b nav\u00e1zali spojen\u00ed mezi PC0 a PC1 p\u0159es switch. <\/p>\n

Abychom pochopili, pro\u010d se n\u00e1m to poda\u0159ilo, pod\u00edv\u00e1me se do nastaven\u00ed switche a prozkoum\u00e1me tabulku VLAN.<\/p>\n

\"Tr\u00e9nink
\n
\nTechnicky m\u00e1 tento switch 5 VLAN: VLAN1 jako v\u00fdchoz\u00ed a tak\u00e9 1002, 1003, 1004 a 1005. Pokud se pod\u00edv\u00e1me na posledn\u00ed 4 s\u00edt\u011b, m\u016f\u017eeme vid\u011bt, \u017ee nejsou podporov\u00e1ny a jsou ozna\u010deny jako unsupported. To jsou virtu\u00e1ln\u00ed s\u00edt\u011b star\u00e9 technologie \u2013 fddi, fddinet, trnet. V sou\u010dasnosti se nepou\u017e\u00edvaj\u00ed, ale podle technick\u00fdch po\u017eadavk\u016f jsou st\u00e1le zahrnuty do nov\u00fdch za\u0159\u00edzen\u00ed. T\u00edm p\u00e1dem m\u00e1 n\u00e1\u0161 switch v\u00fdchoz\u00ed pouze jednu virtu\u00e1ln\u00ed s\u00ed\u0165 \u2013 VLAN1, tak\u017ee v\u0161echny porty jak\u00e9hokoli Cisco switche \u201ez krabice\u201c jsou nastaveny na tuto s\u00ed\u0165. To zahrnuje 24 port\u016f Fast Ethernet a 2 porty Gigabit Ethernet. To zna\u010dn\u011b usnad\u0148uje kompatibilitu nov\u00fdch switch\u016f, proto\u017ee v\u0161echny jsou ve v\u00fdchoz\u00edm nastaven\u00ed sou\u010d\u00e1st\u00ed jedn\u00e9 a t\u00e9 sam\u00e9 VLAN1.<\/p>\n

Mus\u00edme p\u0159eprogramovat porty, kter\u00e9 jsou ve v\u00fdchoz\u00edm nastaven\u00ed nastaveny na pr\u00e1ci s VLAN1, aby pracovaly s VLAN10. Packet Tracer ukazuje, \u017ee v na\u0161em p\u0159\u00edpad\u011b se jedn\u00e1 o porty Fa0 a Fa0\/2. <\/p>\n

\"Tr\u00e9nink
\n
\nVr\u00e1t\u00edme se k switche SW0 a nastav\u00edme tyto dva porty. K tomu pou\u017eiji p\u0159\u00edkaz configure terminal, abych se dostal do re\u017eimu glob\u00e1ln\u00ed konfigurace, a zad\u00e1m p\u0159\u00edkaz pro nastaven\u00ed tohoto rozhran\u00ed \u2013 int fastEthernet 0\/1. Mus\u00edm nastavit pracovn\u00ed re\u017eim tohoto portu na access, proto\u017ee je to access port, a pou\u017eiji p\u0159\u00edkaz switchport mode access. <\/p>\n

\"Tr\u00e9nink
\n
\nTento port je nakonfigurov\u00e1n jako statick\u00fd access port, ale pokud k n\u011bmu p\u0159ipoj\u00edm jin\u00fd switch, d\u00edky pou\u017eit\u00ed protokolu DTP se p\u0159epne do dynamick\u00e9ho trunk re\u017eimu. Tento port pat\u0159\u00ed ve v\u00fdchoz\u00edm nastaven\u00ed do VLAN1, proto mus\u00edm pou\u017e\u00edt p\u0159\u00edkaz switchport access vlan 10. Syst\u00e9m v tu chv\u00edli zobraz\u00ed zpr\u00e1vu, \u017ee VLAN10 neexistuje a mus\u00ed b\u00fdt vytvo\u0159ena. Pokud si vzpomenete, v datab\u00e1zi VLAN m\u00e1me pouze jednu s\u00ed\u0165 \u2013 VLAN1, a \u017e\u00e1dnou s\u00ed\u0165 VLAN10 tam nen\u00ed. Ale po\u017e\u00e1dali jsme switch, aby umo\u017enil p\u0159\u00edstup k VLAN10, proto jsme obdr\u017eeli chybovou zpr\u00e1vu.<\/p>\n

Proto je nutn\u00e9 vytvo\u0159it VLAN10 a p\u0159i\u0159adit k n\u00ed tento access port. Po t\u00e9to operaci, pokud se pod\u00edv\u00e1me do datab\u00e1ze VLAN, uvid\u00edme pr\u00e1v\u011b vytvo\u0159enou VLAN0010, kter\u00e1 je aktivn\u00ed a jej\u00ed sou\u010d\u00e1st\u00ed je port Fa0\/1. <\/p>\n

\"Tr\u00e9nink
\n
\nDo po\u010d\u00edta\u010de jsme neprov\u00e1d\u011bli \u017e\u00e1dn\u00e9 zm\u011bny, pouze jsme nakonfigurovali port switche, ke kter\u00e9mu je p\u0159ipojen. Te\u010f se pokus\u00edme prov\u00e9st ping IP adresy 192.168.10.2, co\u017e se n\u00e1m poda\u0159ilo p\u0159ed n\u011bkolika minutami. Neusp\u011bli jsme, proto\u017ee port, ke kter\u00e9mu je p\u0159ipojen PC0, nyn\u00ed pat\u0159\u00ed do s\u00edt\u011b VLAN10, zat\u00edmco port spojen\u00fd s po\u010d\u00edta\u010dem PC1 st\u00e1le pat\u0159\u00ed do VLAN1, a mezi t\u011bmito dv\u011bma s\u00edt\u011bmi neexistuje \u017e\u00e1dn\u00e9 spojen\u00ed. Abychom vytvo\u0159ili spojen\u00ed mezi t\u011bmito po\u010d\u00edta\u010di, je nutn\u00e9 oba porty nastavit na pr\u00e1ci s VLAN10. Znovu vstupu do re\u017eimu glob\u00e1ln\u00ed konfigurace a provedu podobn\u00e9 kroky pro switchport f0\/2.<\/p>\n

\"Tr\u00e9nink
\n
\nPod\u00edvejme se je\u0161t\u011b jednou na tabulku VLAN. Nyn\u00ed vid\u00edme, \u017ee s\u00ed\u0165 VLAN10 je nastavena na portech Fa0\/1 a Fa0\/2. Jak vid\u00edme, nyn\u00ed ping prob\u00edh\u00e1 \u00fasp\u011b\u0161n\u011b, proto\u017ee oba porty switche SW0, ke kter\u00fdm jsou za\u0159\u00edzen\u00ed p\u0159ipojena, pat\u0159\u00ed do stejn\u00e9 s\u00edt\u011b. Zkusme zm\u011bnit n\u00e1zev s\u00edt\u011b, abychom vyj\u00e1d\u0159ili jej\u00ed \u00fa\u010del. Pokud chceme prov\u00e9st n\u011bjak\u00e9 zm\u011bny v VLAN, mus\u00edme vstoupit do konfigurace t\u00e9to s\u00edt\u011b. <\/p>\n

K tomu zad\u00e1v\u00e1m p\u0159\u00edkaz vlan 10, a vid\u00edte, \u017ee se v\u00fdzva p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku zm\u011bnila ze Switch (config) # na Switch (config-vlan) #. Pokud zad\u00e1m otazn\u00edk, syst\u00e9m n\u00e1m uk\u00e1\u017ee pouze 3 mo\u017en\u00e9 p\u0159\u00edkazy: exit, name a no. Mohu p\u0159i\u0159adit n\u00e1zev s\u00edt\u011b pomoc\u00ed p\u0159\u00edkazu name, vr\u00e1tit p\u0159\u00edkazy do v\u00fdchoz\u00edho stavu zad\u00e1n\u00edm no nebo ulo\u017eit proveden\u00e9 zm\u011bny pomoc\u00ed p\u0159\u00edkazu exit. Proto zad\u00e1v\u00e1m p\u0159\u00edkazy name SALES a exit.<\/p>\n

\"Tr\u00e9nink
\n
\nPokud se pod\u00edv\u00e1te do datab\u00e1ze VLAN, m\u016f\u017eete si ov\u011b\u0159it, \u017ee na\u0161e \u00fakoly byly spln\u011bny a b\u00fdval\u00e1 VLAN10 nyn\u00ed nese n\u00e1zev SALES \u2013 odd\u011blen\u00ed prodeje. P\u0159ipojili jsme tedy 2 po\u010d\u00edta\u010de na\u0161\u00ed kancel\u00e1\u0159e k vytvo\u0159en\u00e9 s\u00edti odd\u011blen\u00ed prodeje. Nyn\u00ed je t\u0159eba vytvo\u0159it s\u00ed\u0165 pro odd\u011blen\u00ed marketingu. Abychom p\u0159ipojili notebook Laptop0 k t\u00e9to s\u00edti, je nutn\u00e9 vstoupit do jeho s\u00ed\u0165ov\u00fdch nastaven\u00ed a zadat IP adresu 192.168.20.1 a masku pods\u00edt\u011b 255.255.255.0, v\u00fdchoz\u00ed br\u00e1nu nepot\u0159ebujeme. Pot\u00e9 se vr\u00e1t\u00edme k nastaven\u00ed switche, zad\u00e1me p\u0159\u00edkaz int fa0\/3 a vlo\u017e\u00edme p\u0159\u00edkaz switchport mode access. Dal\u0161\u00edm p\u0159\u00edkazem bude switchport access vlan 20. <\/p>\n

Znovu dost\u00e1v\u00e1me zpr\u00e1vu, \u017ee takov\u00e1 VLAN neexistuje a \u017ee ji je t\u0159eba vytvo\u0159it. M\u016f\u017eeme j\u00edt jinou cestou \u2013 opust\u00edm nastaven\u00ed portu switche (config-if), p\u0159ejdu do konfigurace switche (config) a zad\u00e1m p\u0159\u00edkaz vlan 20, \u010d\u00edm\u017e vytvo\u0159\u00edm s\u00ed\u0165 VLAN20. To znamen\u00e1, \u017ee nejprve mohu vytvo\u0159it s\u00ed\u0165 VLAN20, p\u0159i\u0159adit j\u00ed n\u00e1zev MARKETING, ulo\u017eit zm\u011bny p\u0159\u00edkazem exit a pot\u00e9 nastavovat port pro tuto s\u00ed\u0165. <\/p>\n

Pokud zad\u00e1te p\u0159\u00edkaz sh vlan do datab\u00e1ze VLAN, m\u016f\u017eete vid\u011bt s\u00ed\u0165 MARKETING, kterou jsme vytvo\u0159ili, a odpov\u00eddaj\u00edc\u00ed port Fa0\/3. Nebudu schopen pingu po\u010d\u00edta\u010de z tohoto notebooku ze dvou d\u016fvod\u016f: m\u00e1me r\u016fzn\u00e9 VLAN a na\u0161e za\u0159\u00edzen\u00ed pat\u0159\u00ed do r\u016fzn\u00fdch pods\u00edt\u00ed. Proto\u017ee pat\u0159\u00ed do r\u016fzn\u00fdch VLAN, switch bude odm\u00edtat paket notebooku sm\u011b\u0159uj\u00edc\u00ed do jin\u00e9 s\u00edt\u011b, proto\u017ee nem\u00e1 port pat\u0159\u00edc\u00ed VLAN20. <\/p>\n

Jak jsem ji\u017e zm\u00ednil, spole\u010dnost se roz\u0161i\u0159uje, mal\u00fd kancel\u00e1\u0159 na prvn\u00edm pat\u0159e nesta\u010d\u00ed, a proto um\u00edst\u00ed odd\u011blen\u00ed marketingu ve druh\u00e9m pat\u0159e budovy, nainstaluje tam po\u010d\u00edta\u010de pro 2 zam\u011bstnance a chce zajistit spojen\u00ed s odd\u011blen\u00edm marketingu v prvn\u00edm pat\u0159e. K tomu je nejprve pot\u0159eba vytvo\u0159it trunk mezi dv\u011bma switche \u2013 portem Fa0\/4 prvn\u00edho switche a portem Fa0\/1 druh\u00e9ho switche. Proto vstupuji do nastaven\u00ed SW0 a zad\u00e1v\u00e1m p\u0159\u00edkazy int f0\/4 a switchport mode trunk. <\/p>\n

Existuje p\u0159\u00edkaz pro enkapsulaci switchport trunk enc, av\u0161ak v nov\u00fdch switchech se nepou\u017e\u00edv\u00e1, proto\u017ee ve v\u00fdchoz\u00edm nastaven\u00ed vyu\u017e\u00edvaj\u00ed technologii enkapsulace podle protokolu 802.1q. Star\u0161\u00ed modely switch\u016f Cisco pou\u017e\u00edvaly propriet\u00e1rn\u00ed protokol ISL, kter\u00fd se ji\u017e nepou\u017e\u00edv\u00e1, proto\u017ee nyn\u00ed v\u0161echny switche rozum\u00ed protokolu .1Q. Tak\u017ee u\u017e nen\u00ed pot\u0159eba pou\u017e\u00edvat p\u0159\u00edkaz switchport trunk enc.<\/p>\n

Pokud nyn\u00ed vstoup\u00edte do datab\u00e1ze VLAN, uvid\u00edte, \u017ee port Fa0\/4 z n\u00ed zmizel. D\u016fvodem je, \u017ee v t\u00e9to tabulce jsou uvedeny pouze access porty, kter\u00e9 se vztahuj\u00ed k konkr\u00e9tn\u00ed VLAN. Chcete-li vid\u011bt trunk porty switche, je t\u0159eba pou\u017e\u00edt p\u0159\u00edkaz sh int trunk. <\/p>\n

\"Tr\u00e9nink
\n
\nV okn\u011b p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku vid\u00edme, \u017ee port Fa0\/4 je zapnut\u00fd, prov\u00e1d\u00ed enkapsulaci podle protokolu 802.1q a pat\u0159\u00ed k native VLAN 1. Jak v\u00edme, pokud tento trunk port p\u0159ij\u00edm\u00e1 neozna\u010den\u00fd provoz, automaticky ho sm\u011bruje do s\u00edt\u011b native VLAN 1. V n\u00e1sleduj\u00edc\u00ed lekci se budeme zab\u00fdvat nastaven\u00edm native VLAN, zat\u00edm si pouze zapamatujte, jak vypadaj\u00ed nastaven\u00ed trunku pro toto za\u0159\u00edzen\u00ed.<\/p>\n

Nyn\u00ed p\u0159ech\u00e1z\u00edm k druh\u00e9mu switchi SW1, vstupuji do re\u017eimu nastaven\u00ed int f0\/1 a opakuji sekvenci nastaven\u00ed portu obdobn\u011b jako v p\u0159edchoz\u00edm p\u0159\u00edpad\u011b. Dva porty Fa0\/2 a Fa0\/3, ke kter\u00fdm jsou p\u0159ipojeny notebooky zam\u011bstnanc\u016f marketingov\u00e9ho odd\u011blen\u00ed, je t\u0159eba nastavit na re\u017eim access a p\u0159i\u0159adit k s\u00edti VLAN20. <\/p>\n

V p\u0159edchoz\u00edm p\u0159\u00edpad\u011b jsme jednotliv\u011b nastavovali ka\u017ed\u00fd port switche, a nyn\u00ed chci uk\u00e1zat, jak tento proces zrychlit pou\u017eit\u00edm \u0161ablony p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku. M\u016f\u017eete zadat p\u0159\u00edkaz pro nastaven\u00ed rozsahu rozhran\u00ed int range f0\/2-3, \u010d\u00edm\u017e se p\u0159\u00edkazov\u00fd \u0159\u00e1dek zm\u011bn\u00ed na Switch (config-if-range)#, a budete moci zav\u00e9st stejn\u00fd parametr nebo pou\u017e\u00edt stejn\u00fd p\u0159\u00edkaz pro uveden\u00fd rozsah port\u016f, nap\u0159\u00edklad sou\u010dasn\u011b pro 20 port\u016f. <\/p>\n

V p\u0159edchoz\u00edm p\u0159\u00edkladu jsme n\u011bkolikr\u00e1t pou\u017eili stejn\u00e9 p\u0159\u00edkazy switchport mode access a switchport access vlan 10 pro n\u011bkolik port\u016f switche. Tyto p\u0159\u00edkazy lze zadat jednou, pokud pou\u017eijete rozsah port\u016f. Nyn\u00ed zad\u00e1m p\u0159\u00edkazy switchport mode access a switchport access vlan 20 pro vybran\u00fd rozsah port\u016f. <\/p>\n

\"Tr\u00e9nink
\n
\nProto\u017ee s\u00ed\u0165 VLAN20 dosud neexistuje, syst\u00e9m ji automaticky vytvo\u0159\u00ed. Zad\u00e1v\u00e1m exit pro ulo\u017een\u00ed proveden\u00fdch zm\u011bn a \u017e\u00e1d\u00e1m o zobrazen\u00ed tabulky VLAN. Jak vid\u00edte, nyn\u00ed jsou porty Fa0\/2 a Fa0\/3 sou\u010d\u00e1st\u00ed pr\u00e1v\u011b vytvo\u0159en\u00e9 VLAN20. <\/p>\n

Nyn\u00ed nastav\u00edm IP adresy notebook\u016f ve druh\u00e9m pat\u0159e na\u0161\u00ed kancel\u00e1\u0159e: Laptop1 dostane adresu 192.168.20.2 a masku pods\u00edt\u011b 255.255.255.0, zat\u00edmco Laptop2 dostane IP adresu 192.168.20.3. Ov\u011b\u0159\u00edme funk\u010dnost s\u00edt\u011b pingnut\u00edm prvn\u00edho notebooku z druh\u00e9ho. Jak vid\u00edte, ping je \u00fasp\u011b\u0161n\u00fd, proto\u017ee ob\u011b za\u0159\u00edzen\u00ed jsou sou\u010d\u00e1st\u00ed jedn\u00e9 VLAN a jsou p\u0159ipojena ke stejn\u00e9mu switche. <\/p>\n

\"Tr\u00e9nink
\n
\nNotebooky marketingov\u00e9ho odd\u011blen\u00ed na prvn\u00edm a druh\u00e9m pat\u0159e jsou ale p\u0159ipojeny k r\u016fzn\u00fdm switchem, i kdy\u017e jsou ve stejn\u00e9 VLAN. Ov\u011b\u0159\u00edme, jak je zaji\u0161t\u011bna komunikace mezi nimi, proto pingnu z Laptop2 notebook ve prvn\u00edm pat\u0159e, kter\u00fd m\u00e1 IP adresu 192.168.20.1. Jak vid\u00edte, v\u0161e funguje bez probl\u00e9m\u016f, i kdy\u017e jsou notebooky p\u0159ipojeny k r\u016fzn\u00fdm switchem. Komunikace je zaji\u0161t\u011bna d\u00edky tomu, \u017ee oba switche jsou propojeny trunkem. <\/p>\n

Mohu nav\u00e1zat spojen\u00ed mezi Laptop2 a po\u010d\u00edta\u010dem PC0? Ne, nemohu, proto\u017ee pat\u0159\u00ed do r\u016fzn\u00fdch VLAN. Nyn\u00ed provedeme nastaven\u00ed s\u00edt\u011b pro po\u010d\u00edta\u010de PC2,3,4, k \u010demu\u017e nejprve vytvo\u0159\u00edme trunk mezi druh\u00fdm switchem Fa0\/4 a t\u0159et\u00edm switchem Fa0\/1. <\/p>\n

Vstupuji do nastaven\u00ed SW1 a zad\u00e1v\u00e1m p\u0159\u00edkaz config t, pot\u00e9 vyb\u00edr\u00e1m int f0\/4, n\u00e1sledn\u011b zad\u00e1v\u00e1m p\u0159\u00edkazy switchport mode trunk a exit. Stejn\u00fdm zp\u016fsobem nastav\u00edm t\u0159et\u00ed switch SW2. Vytvo\u0159ili jsme trunk a vid\u00edte, \u017ee pot\u00e9, co se nastaven\u00ed aktivovala, se barva port\u016f zm\u011bnila z oran\u017eov\u00e9 na zelenou. Nyn\u00ed je t\u0159eba nastavit porty Fa0\/2,0\/3,0\/4, k nim\u017e jsou p\u0159ipojeny po\u010d\u00edta\u010de prodeje, pat\u0159\u00edc\u00ed do s\u00edt\u011b VLAN10. Pro tento \u00fa\u010del vstupuji do nastaven\u00ed switche SW2, vyb\u00edr\u00e1m rozsah port\u016f f0\/2-4 a aplikuji na n\u011b p\u0159\u00edkazy switchport mode access a switchport access vlan 10. Proto\u017ee na t\u011bchto portech s\u00ed\u0165 VLAN10 neexistuje, je automaticky vytvo\u0159ena syst\u00e9mem. Pokud se pod\u00edv\u00e1te do datab\u00e1ze VLAN tohoto switche, uvid\u00edte, \u017ee nyn\u00ed porty Fa0\/2,0\/3,0\/4 pat\u0159\u00ed do s\u00edt\u011b VLAN10. <\/p>\n

Pot\u00e9 je nutn\u00e9 nastavit s\u00ed\u0165 pro ka\u017ed\u00fd z t\u011bchto 3 po\u010d\u00edta\u010d\u016f, zad\u00e1n\u00edm IP adres a masek pods\u00edt\u011b. PC2 z\u00edsk\u00e1v\u00e1 adresu 192.168.10.3, PC3 \u2013 adresu 192.168.10.4, a PC4 \u2013 IP adresu 192.168.10.5. <\/p>\n

\"Tr\u00e9nink
\n
\nAbychom zjistili, zda na\u0161e s\u00ed\u0165 funguje, pingneme po\u010d\u00edta\u010d PC0 v prvn\u00edm pat\u0159e z po\u010d\u00edta\u010de PC4, kter\u00fd se nach\u00e1z\u00ed ve 3. pat\u0159e nebo v jin\u00e9m budov\u011b. Pinging skon\u010dil ne\u00fasp\u011bchem, tak se pokusme zjistit, pro\u010d se n\u00e1m to nepoda\u0159ilo.<\/p>\n

Kdy\u017e jsme se pokusili pingovat Laptop0 z notebooku Laptop2, v\u0161e fungovalo skv\u011ble, i kdy\u017e byly notebooky p\u0159ipojeny k r\u016fzn\u00fdm switchem. Pro\u010d tedy nyn\u00ed, kdy\u017e jsou na\u0161e po\u010d\u00edta\u010de v prodeji tak\u00e9 p\u0159esn\u011b p\u0159ipojeny k r\u016fzn\u00fdm switchem spojen\u00fdm trunkem, ping neproch\u00e1z\u00ed? Abychom se dostali k p\u0159\u00ed\u010din\u011b probl\u00e9mu, mus\u00edme si vzpomenout, jak switch funguje. <\/p>\n

Kdy\u017e pos\u00edl\u00e1me paket z po\u010d\u00edta\u010de PC4 na switch SW2, vid\u00ed, \u017ee paket p\u0159ich\u00e1z\u00ed na port Fa0\/4. Switch kontroluje svou datab\u00e1zi a zjist\u00ed, \u017ee port Fa0\/4 n\u00e1le\u017e\u00ed do s\u00edt\u011b VLAN10. Pot\u00e9 switch ozna\u010duje r\u00e1mec \u010d\u00edslem s\u00edt\u011b, tedy p\u0159ipojuje k datov\u00e9mu paketu hlavi\u010dku VLAN10 a odes\u00edl\u00e1 ho trunkem druh\u00e9mu switchi SW1. Tento switch \u201e\u010dte\u201c hlavi\u010dku a vid\u00ed, \u017ee paket je ur\u010den pro s\u00ed\u0165 VLAN10, nahl\u00e9dne do sv\u00e9 datab\u00e1ze VLAN a zjist\u00ed, \u017ee \u017e\u00e1dn\u00e1 VLAN10 tam nen\u00ed, a pak paket odm\u00edtne. Takto mohou za\u0159\u00edzen\u00ed PC2, 3 a 4 bez probl\u00e9m\u016f komunikovat mezi sebou, ale pokus o nav\u00e1z\u00e1n\u00ed spojen\u00ed s po\u010d\u00edta\u010di PC0 a PC1 kon\u010d\u00ed ne\u00fasp\u011bchem, proto\u017ee switch SW1 nic nev\u00ed o s\u00edti VLAN10. <\/p>\n

Tento probl\u00e9m m\u016f\u017eeme snadno vy\u0159e\u0161it t\u00edm, \u017ee se dostaneme do nastaven\u00ed SW1, vytvo\u0159\u00edme s\u00ed\u0165 VLAN10 pomoc\u00ed p\u0159\u00edkazu vlan 10 a zad\u00e1me jej\u00ed n\u00e1zev MARKETING. Zkus\u00edme pingov\u00e1n\u00ed znovu \u2013 vid\u00edte, \u017ee prvn\u00ed t\u0159i pakety jsou odm\u00edtnuty, zat\u00edmco \u010dtvrt\u00fd proch\u00e1z\u00ed \u00fasp\u011b\u0161n\u011b. To je zp\u016fsobeno t\u00edm, \u017ee switch nejprve kontroloval IP adresy a ur\u010doval MAC adresu, co\u017e zabralo ur\u010ditou dobu, a proto byly prvn\u00ed t\u0159i pakety odhozeny kv\u016fli timeoutu. Nyn\u00ed je spojen\u00ed nav\u00e1z\u00e1no, proto\u017ee switch doplnil svou tabulku MAC adres a sm\u011bruje pakety p\u0159\u00edmo na po\u017eadovanou adresu.
\nV\u0161echno, co jsem ud\u011blal pro vy\u0159e\u0161en\u00ed probl\u00e9mu, bylo, \u017ee jsem \u0161el do nastaven\u00ed meziswitchu a vytvo\u0159il tam s\u00ed\u0165 VLAN10. Tak\u017ee, i kdy\u017e s\u00ed\u0165 nen\u00ed p\u0159\u00edmo spojena se switchem, m\u011bl by st\u00e1le v\u011bd\u011bt o v\u0161ech s\u00edt\u00edch, kter\u00e9 se \u00fa\u010dastn\u00ed s\u00ed\u0165ov\u00fdch spojen\u00ed. Pokud by v\u0161ak ve va\u0161\u00ed s\u00edti byla stovka switch\u016f, fyzicky byste se nemohli dostat do nastaven\u00ed ka\u017ed\u00e9ho z nich a ru\u010dn\u011b nakonfigurovat identifik\u00e1tory VLAN. Proto pou\u017e\u00edv\u00e1me protokol VTP, jeho\u017e konfiguraci si prozkoum\u00e1me v n\u00e1sleduj\u00edc\u00edm video\u0161kolen\u00ed. <\/p>\n

Dnes jsme probrali v\u0161e, co jsme pl\u00e1novali: jak vytv\u00e1\u0159et VLANy, jak p\u0159i\u0159azovat porty VLAN a jak prohl\u00ed\u017eet datab\u00e1zi VLAN. Pro vytvo\u0159en\u00ed s\u00edt\u00ed vstupujeme do glob\u00e1ln\u00ed konfigura\u010dn\u00edho re\u017eimu switche a pou\u017e\u00edv\u00e1me p\u0159\u00edkaz vlan , tak\u00e9 m\u016f\u017eeme p\u0159i\u0159adit n\u00e1zev vytvo\u0159en\u00e9 s\u00edt\u011b pomoc\u00ed p\u0159\u00edkazu name . <\/p>\n

\"Tr\u00e9nink
\n
\nM\u016f\u017eeme tak\u00e9 vytvo\u0159it VLAN jin\u00fdm zp\u016fsobem, vstupem do re\u017eimu rozhran\u00ed a pou\u017eit\u00edm p\u0159\u00edkazu switchport access vlan . V p\u0159\u00edpad\u011b, \u017ee neexistuje s\u00ed\u0165 s takov\u00fdm \u010d\u00edslem, bude automaticky vytvo\u0159ena syst\u00e9mem. Nezapome\u0148te pou\u017e\u00edt p\u0159\u00edkaz exit po proveden\u00ed zm\u011bn v po\u010d\u00e1te\u010dn\u00edch nastaven\u00edch, jinak se neulo\u017e\u00ed do datab\u00e1ze VLAN. Pot\u00e9 m\u016f\u017eete p\u0159i\u0159adit porty k konkr\u00e9tn\u00edm vl\u00e1k\u016fm VLAN pomoc\u00ed p\u0159\u00edslu\u0161n\u00fdch p\u0159\u00edkaz\u016f.<\/p>\n

\"Tr\u00e9nink
\n
\nP\u0159\u00edkaz switchport mode access p\u0159ev\u00e1d\u00ed rozhran\u00ed do statick\u00e9ho re\u017eimu access-port, po \u010dem\u017e je \u010d\u00edslo odpov\u00eddaj\u00edc\u00ed VLAN p\u0159i\u0159azeno portu pomoc\u00ed p\u0159\u00edkazu switchport access vlan . K zobrazen\u00ed datab\u00e1ze VLAN se pou\u017e\u00edv\u00e1 p\u0159\u00edkaz show vlan, kter\u00fd by m\u011bl b\u00fdt zad\u00e1n v u\u017eivatelsk\u00e9m re\u017eimu EXEC. Pro zobrazen\u00ed seznamu trunk port\u016f je pot\u0159eba pou\u017e\u00edt p\u0159\u00edkaz show int trunk. <\/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\u0448\u043d\u0438\u0439 \u0443\u0440\u043e\u043a \u043c\u044b \u043f\u043e\u0441\u0432\u044f\u0442\u0438\u043c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430\u043c VLAN, \u0442\u043e \u0435\u0441\u0442\u044c \u043f\u043e\u043f\u0440\u043e\u0431\u0443\u0435\u043c \u043f\u0440\u043e\u0434\u0435\u043b\u0430\u0442\u044c \u0432\u0441\u0451 \u0442\u043e, \u043e \u0447\u0435\u043c \u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438 \u043d\u0430 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0445 \u0443\u0440\u043e\u043a\u0430\u0445. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c 3 \u0432\u043e\u043f\u0440\u043e\u0441\u0430: \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u0435 VLAN, \u043f\u0440\u0438\u0441\u0432\u0430\u0438\u0432\u0430\u043d\u0438\u0435 \u043f\u043e\u0440\u0442\u043e\u0432 VLAN \u0438 \u043f\u0440\u043e\u0441\u043c\u043e\u0442\u0440 \u0431\u0430\u0437\u044b \u0434\u0430\u043d\u043d\u044b\u0445 VLAN. \u041e\u0442\u043a\u0440\u043e\u0435\u043c \u043e\u043a\u043d\u043e \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u044b Cisco Packer tracer \u0441 \u043d\u0430\u0440\u0438\u0441\u043e\u0432\u0430\u043d\u043d\u043e\u0439 \u043c\u043d\u043e\u044e \u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0442\u043e\u043f\u043e\u043b\u043e\u0433\u0438\u0435\u0439 \u043d\u0430\u0448\u0435\u0439 \u0441\u0435\u0442\u0438. \u041a \u043f\u0435\u0440\u0432\u043e\u043c\u0443 \u0441\u0432\u0438\u0442\u0447\u0443 SW0 \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0435\u043d\u044b 2 \u043a\u043e\u043c\u043f\u044c\u044e\u0442\u0435\u0440\u0430 PC0 \u0438 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27773,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37049","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 13. Nastaven\u00ed VLAN | ProHoster","description":"Dne\u0161n\u00ed lekci v\u011bnujeme nastaven\u00ed VLAN, tedy si zkus\u00edme proj\u00edt v\u0161echno, o \u010dem jsme hovo\u0159ili v p\u0159edchoz\u00edch lekc\u00edch.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-13-nastrojka-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 13. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 VLAN | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0438\u0439 \u0443\u0440\u043e\u043a \u043c\u044b \u043f\u043e\u0441\u0432\u044f\u0442\u0438\u043c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430\u043c VLAN, \u0442\u043e \u0435\u0441\u0442\u044c \u043f\u043e\u043f\u0440\u043e\u0431\u0443\u0435\u043c \u043f\u0440\u043e\u0434\u0435\u043b\u0430\u0442\u044c \u0432\u0441\u0451 \u0442\u043e, \u043e \u0447\u0435\u043c \u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438 \u043d\u0430 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0445 \u0443\u0440\u043e\u043a\u0430\u0445.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-13-nastrojka-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:29+00:00","article:modified_time":"2019-10-31T19:15:29+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37049","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:51:33","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:34:24","updated":"2026-01-22 05:51:33","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\/37049","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=37049"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37049\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/27773"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=37049"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=37049"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=37049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}