{"id":37888,"date":"2019-10-31T22:20:23","date_gmt":"2019-10-31T19:20:23","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-vlan\/"},"modified":"2019-10-31T22:20:23","modified_gmt":"2019-10-31T19:20:23","slug":"trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-vlan","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-vlan","title":{"rendered":"\u0160kolen\u00ed Cisco 200-125 CCNA v3.0. Den 34. Roz\u0161\u00ed\u0159en\u00e1 koncepce VLAN","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

V\u010dera jsme se zab\u00fdvali VLAN s\u00edt\u011bmi ve video lekc\u00edch Dne 11, 12 a 13, a dnes budeme pokra\u010dovat ve studiu podle t\u00e9matiky ICND2. P\u0159ed m\u011bs\u00edcem jsem nahr\u00e1l p\u0159edchoz\u00ed video, kter\u00e9 ukon\u010dilo p\u0159\u00edpravu na zkou\u0161ku ICND1, a od t\u00e9 doby jsem byl velmi zanepr\u00e1zdn\u011bn. Mysl\u00edm, \u017ee mnoz\u00ed z v\u00e1s \u00fasp\u011b\u0161n\u011b slo\u017eili tuto zkou\u0161ku, ti, kte\u0159\u00ed odlo\u017eili testov\u00e1n\u00ed, mohou po\u010dkat na dokon\u010den\u00ed druh\u00e9 \u010d\u00e1sti kurzu a pokusit se slo\u017eit komplexn\u00ed zkou\u0161ku CCNA 200-125.<\/p>\n

Dne\u0161n\u00edm video lekc\u00ed \u201eDen 34\u201c zahajujeme t\u00e9matiku kurzu ICND2. Mnoz\u00ed se m\u011b ptaj\u00ed, pro\u010d jsme nezahrnuli OSPF a EIGRP. Fakt je takov\u00fd, \u017ee tyto protokoly nejsou zahrnuty do t\u00e9matiky kurzu ICND1 a studuj\u00ed se p\u0159i p\u0159\u00edprav\u011b na slo\u017een\u00ed ICND2. Od dne\u0161n\u00edho dne za\u010dneme pokr\u00fdvat t\u00e9mata druh\u00e9 \u010d\u00e1sti kurzu a samoz\u0159ejm\u011b se pod\u00edv\u00e1me na OSPF a EIGRP. Ne\u017e za\u010dneme dne\u0161n\u00ed t\u00e9ma, cht\u011bl bych promluvit o strukturov\u00e1n\u00ed na\u0161ich video lekc\u00ed. P\u0159i p\u0159edn\u00e1\u0161en\u00ed t\u00e9matiky ICND1 jsem se nedr\u017eel stanoven\u00fdch \u0161ablon, ale jednodu\u0161e jsem logicky vysv\u011btloval materi\u00e1l, proto\u017ee jsem pova\u017eoval, \u017ee tento zp\u016fsob je pro pochopen\u00ed snaz\u0161\u00ed. Nyn\u00ed, p\u0159i studiu ICND2, budu na \u017e\u00e1dost poslucha\u010d\u016f prezentovat studijn\u00ed materi\u00e1l v souladu s u\u010debn\u00edm pl\u00e1nem a programem kurzu Cisco.<\/a><\/noindex><\/p>\n

Pokud nav\u0161t\u00edv\u00edte webovou str\u00e1nku spole\u010dnosti, uvid\u00edte tento pl\u00e1n a tak\u00e9 to, \u017ee cel\u00fd kurz je rozd\u011blen do p\u011bti hlavn\u00edch \u010d\u00e1st\u00ed: <\/p>\n

\u2014 Technologie p\u0159ep\u00edn\u00e1n\u00ed m\u00edstn\u00edch s\u00edt\u00ed (26 % studijn\u00edho materi\u00e1lu);
\n \u2014 Technologie sm\u011brov\u00e1n\u00ed (29 %);
\n \u2014 Technologie glob\u00e1ln\u00edch s\u00edt\u00ed (16 %);
\n \u2014 Slu\u017eby infrastruktury (14 %);
\n \u2014 \u00dadr\u017eba infrastruktury (15 %).<\/p>\n

Za\u010dnu prvn\u00ed \u010d\u00e1st\u00ed. Pokud kliknete na rozv\u00edjec\u00ed menu na prav\u00e9 stran\u011b, m\u016f\u017eete vid\u011bt podrobnosti o t\u00e9matu t\u00e9to sekce. Dne\u0161n\u00ed video lekce pokryje t\u00e9ma sekce 1.1: \u201eNastaven\u00ed, ov\u011b\u0159en\u00ed a odstra\u0148ov\u00e1n\u00ed probl\u00e9m\u016f s\u00edt\u00ed VLAN (b\u011b\u017en\u00fd \/ roz\u0161\u00ed\u0159en\u00fd rozsah), pokr\u00fdvaj\u00edc\u00ed v\u00edce switch\u016f\u201c a podsekce 1.1a \u201eP\u0159\u00edstupov\u00e9 porty (data a hlasov\u00e9 zpr\u00e1vy)\u201c a 1.1.b \u201eV\u00fdchoz\u00ed VLAN\u201c.<\/p>\n

D\u00e1le se budu sna\u017eit dr\u017eet stejn\u00fd princip struktury, tedy ka\u017ed\u00fd video lekce bude zam\u011b\u0159ena na jednu kapitolu s podkapitolami. Pokud bude materi\u00e1lu m\u00e1lo, spoj\u00edm t\u00e9mata n\u011bkolika kapitol do jedn\u00e9 lekce, nap\u0159\u00edklad 1.2 a 1.3. Pokud v\u0161ak bude materi\u00e1lu hodn\u011b, rozd\u011bl\u00edm ho do dvou vide\u00ed. V ka\u017ed\u00e9m p\u0159\u00edpad\u011b se budeme \u0159\u00eddit programem kurzu, a vy si snadno m\u016f\u017eete porovnat shodu va\u0161ich pozn\u00e1mek s aktu\u00e1ln\u00edm studijn\u00edm pl\u00e1nem Cisco. <\/p>\n

\"\u0160kolen\u00ed
\n
\nNa obrazovce vid\u00edte m\u016fj nov\u00fd pracovn\u00ed st\u016fl, to je Windows 10. Pokud chcete vylep\u0161it sv\u016fj pracovn\u00ed st\u016fl r\u016fzn\u00fdmi widgety, m\u016f\u017eete se pod\u00edvat na m\u00e9 video s n\u00e1zvem \u201ePimp Your Desktop\u201c, kde vysv\u011btluji, jak p\u0159izp\u016fsobit pracovn\u00ed st\u016fl po\u010d\u00edta\u010de podle sv\u00fdch pot\u0159eb. Takov\u00e1 videa zve\u0159ej\u0148uji na jin\u00e9m kan\u00e1lu, ExplainWorld, tak\u017ee m\u016f\u017eete vyu\u017e\u00edt odkaz v prav\u00e9m horn\u00edm rohu a sezn\u00e1mit se s obsahem.<\/p>\n

P\u0159ed za\u010d\u00e1tkem lekce v\u00e1s pros\u00edm, abyste nezapom\u00ednali sd\u00edlet m\u00e1 videa a d\u00e1vat 'like'. Chci tak\u00e9 p\u0159ipomenout na\u0161e kontakty na soci\u00e1ln\u00edch s\u00edt\u00edch a odkazy na m\u00e9 osobn\u00ed str\u00e1nky. M\u016f\u017eete mi napsat na e-mail, a jak jsem ji\u017e \u0159ekl, prioritu v obdr\u017een\u00ed m\u00e9 osobn\u00ed odpov\u011bdi budou m\u00edt lid\u00e9, kte\u0159\u00ed p\u0159isp\u011bli na na\u0161em webu. <\/p>\n

Pokud jste nep\u0159isp\u011bli, nic se ned\u011bje, m\u016f\u017eete zanech\u00e1vat sv\u00e9 koment\u00e1\u0159e pod video lekcemi na kan\u00e1lu YouTube a j\u00e1 na n\u011b budu odpov\u00eddat, jakmile to bude mo\u017en\u00e9. <\/p>\n

Tak\u017ee dnes, podle rozvrhu Cisco, probereme 3 ot\u00e1zky: porovn\u00e1me Default VLAN, tedy VLAN podle defaultu, s Native VLAN, nebo \u2018rodn\u00fdm\u2019 VLAN, zjist\u00edme, \u010d\u00edm se li\u0161\u00ed Normal VLAN (b\u011b\u017en\u00fd rozsah VLAN) od roz\u0161\u00ed\u0159en\u00e9ho rozsahu s\u00edt\u011b Extended VLAN a prozkoum\u00e1me rozd\u00edl mezi Data VLAN (VLAN dat) a Voice VLAN (hlasov\u00e1 VLAN). Jak jsem \u0159ekl, tuto ot\u00e1zku jsme ji\u017e probrali v p\u0159edchoz\u00edch epizod\u00e1ch, ale pom\u011brn\u011b povrchn\u011b, proto si ji dodnes mnoz\u00ed studenti slo\u017eit\u011b ur\u010duj\u00ed. Dnes to vysv\u011btl\u00edm tak, aby tomu v\u0161ichni rozum\u011bli. <\/p>\n

Pod\u00edvejme se, jak\u00fd je rozd\u00edl mezi Default VLAN a Native VLAN. Pokud vezmete zcela nov\u00fd Cisco switch s tov\u00e1rn\u00edmi nastaven\u00edmi, bude m\u00edt 5 VLAN \u2013 VLAN1, VLAN1002, VLAN1003, VLAN1004 a VLAN1005. <\/p>\n

\"\u0160kolen\u00ed
\n
\nVLAN1 je v\u00fdchoz\u00ed VLAN pro v\u0161echna za\u0159\u00edzen\u00ed Cisco a VLAN 1002\u20131005 jsou vyhrazeny pro Token Ring a FDDI. S\u00ed\u0165 VLAN1 nelze odstranit ani p\u0159ejmenovat, nen\u00ed mo\u017en\u00e9 k n\u00ed p\u0159id\u00e1vat rozhran\u00ed a v\u0161echny porty switche pat\u0159\u00ed k t\u00e9to s\u00edti, dokud nejsou nastaveny jinak. Ve v\u00fdchoz\u00edm nastaven\u00ed mohou v\u0161echny switche mezi sebou komunikovat, proto\u017ee jsou sou\u010d\u00e1st\u00ed VLAN1. To je to, co znamen\u00e1 \u201ev\u00fdchoz\u00ed VLAN\u201c nebo Default VLAN.<\/p>\n

Pokud se pod\u00edv\u00e1te do nastaven\u00ed switche SW1 a p\u0159i\u0159ad\u00edte dv\u011b rozhran\u00ed k s\u00edti VLAN20, stanou se sou\u010d\u00e1st\u00ed s\u00edt\u011b VLAN20. P\u0159ed t\u00edm, ne\u017e za\u010dnete dne\u0161n\u00ed lekci, d\u016frazn\u011b doporu\u010duji znovu si proj\u00edt v\u00fd\u0161e zm\u00edn\u011bn\u00e9 epizody 11, 12 a 13, proto\u017ee nebudu opakovat, co je VLAN a jak funguj\u00ed. <\/p>\n

\"\u0160kolen\u00ed
\n
\nJen p\u0159ipom\u00edn\u00e1m, \u017ee rozhran\u00ed nelze automaticky p\u0159i\u0159adit k s\u00edti VLAN20, dokud ji nevytvo\u0159\u00edte, tak\u017ee nejprve mus\u00edte p\u0159ej\u00edt do glob\u00e1ln\u00ed konfigura\u010dn\u00edho re\u017eimu switche a vytvo\u0159it VLAN20. M\u016f\u017eete se pod\u00edvat na konzoli nastaven\u00ed CLI a pochopit, co m\u00e1m na mysli. Jakmile p\u0159i\u0159ad\u00edte tyto 2 porty pro pr\u00e1ci s VLAN20, po\u010d\u00edta\u010de PC1 a PC2 si budou moci vz\u00e1jemn\u011b komunikovat, proto\u017ee oba budou pat\u0159it do jedn\u00e9 s\u00edt\u011b VLAN20. Ale po\u010d\u00edta\u010d PC3 st\u00e1le z\u016fstane sou\u010d\u00e1st\u00ed VLAN1 a proto nebude moct komunikovat s po\u010d\u00edta\u010di v s\u00edti VLAN20. <\/p>\n

M\u00e1me druh\u00fd switch SW2, z jeho\u017e jednoho rozhran\u00ed je p\u0159i\u0159azeno pro VLAN20, a k tomuto portu je p\u0159ipojen po\u010d\u00edta\u010d PC5. V t\u00e9to konfiguraci nem\u016f\u017ee PC5 komunikovat s PC4 a PC6, ale tyto dva po\u010d\u00edta\u010de si mohou navz\u00e1jem komunikovat, proto\u017ee pat\u0159\u00ed do stejn\u00e9 s\u00edt\u011b VLAN1. <\/p>\n

Oba switche jsou propojeny trunkem p\u0159es spr\u00e1vn\u011b nastaven\u00e9 porty. Nebudu se opakovat, jen \u0159eknu, \u017ee v\u0161echny porty switche jsou ve v\u00fdchoz\u00edm nastaven\u00ed nastaveny na trunkov\u00e1n\u00ed podle protokolu DTP. Pokud k n\u011bjak\u00e9mu portu p\u0159ipoj\u00edte po\u010d\u00edta\u010d, tento port bude pou\u017e\u00edvat p\u0159\u00edstupov\u00fd re\u017eim. Pokud chcete p\u0159ev\u00e9st do tohoto re\u017eimu port, k n\u011bmu\u017e je p\u0159ipojen PC3, mus\u00edte zadat p\u0159\u00edkaz switchport mode access. <\/p>\n

Tak\u017ee pokud spoj\u00edte dva switche navz\u00e1jem, vytvo\u0159\u00ed trunk. Dva horn\u00ed porty SW1 budou p\u0159en\u00e1\u0161et provoz pouze VLAN20, doln\u00ed port pouze provoz VLAN1, ale trunkov\u00e9 spojen\u00ed bude p\u0159en\u00e1\u0161et ve\u0161ker\u00fd provoz, kter\u00fd proch\u00e1z\u00ed switchem. Takto do SW2 p\u0159ijde provoz jak VLAN1, tak VLAN20. <\/p>\n

Jak v\u00edte, VLAN s\u00edt\u011b maj\u00ed m\u00edstn\u00ed v\u00fdznam. Proto SW2 v\u00ed, \u017ee provoz p\u0159ich\u00e1zej\u00edc\u00ed na portu VLAN1 od PC4 m\u016f\u017ee b\u00fdt posl\u00e1n pouze na PC6 p\u0159es port, kter\u00fd tak\u00e9 pat\u0159\u00ed VLAN1. Kdy\u017e v\u0161ak jeden switch pos\u00edl\u00e1 provoz jin\u00e9mu switchi p\u0159es trunk, mus\u00ed pou\u017e\u00edt mechanismus, kter\u00fd vysv\u011btl\u00ed druh\u00e9mu switchi, o jak\u00fd provoz se jedn\u00e1. K tomu se pou\u017e\u00edv\u00e1 s\u00ed\u0165 Native VLAN, kter\u00e1 je p\u0159ipojena k trunk portu a propou\u0161t\u00ed ozna\u010den\u00fd provoz. <\/p>\n

\"\u0160kolen\u00ed<\/p>\n

Jak jsem ji\u017e zm\u00ednil, switch m\u00e1 pouze jednu s\u00ed\u0165, kter\u00e1 se nem\u011bn\u00ed \u2013 je to v\u00fdchoz\u00ed s\u00ed\u0165 VLAN1. Ale v\u00fdchoz\u00ed Native VLAN je pr\u00e1v\u011b VLAN1. Co je Native VLAN? Je to s\u00ed\u0165, kter\u00e1 propou\u0161t\u00ed neozna\u010den\u00fd provoz VLAN1, ale jakmile na trunk-port p\u0159ijde provoz z jak\u00e9koli jin\u00e9 s\u00edt\u011b, v na\u0161em p\u0159\u00edpad\u011b VLAN20, mus\u00ed b\u00fdt ozna\u010den. Ka\u017ed\u00fd r\u00e1mec m\u00e1 adresu c\u00edlov\u00e9ho DA, adresu zdrojov\u00e9ho SA a VLAN tag, kter\u00fd obsahuje identifik\u00e1tor s\u00edt\u011b VLAN ID. V na\u0161em p\u0159\u00edpad\u011b tento identifik\u00e1tor ukazuje, \u017ee tento provoz n\u00e1le\u017e\u00ed VLAN20, a proto m\u016f\u017ee b\u00fdt posl\u00e1n pouze p\u0159es port VLAN20 a ur\u010den pro PC5. Lze \u0159\u00edci, \u017ee Native VLAN rozhoduje, zda m\u00e1 b\u00fdt provoz ozna\u010den nebo neozna\u010den. <\/p>\n

Pamatujte, \u017ee VLAN1 je v\u00fdchoz\u00ed s\u00edt\u00ed Native VLAN, proto\u017ee ve v\u00fdchoz\u00edm nastaven\u00ed v\u0161echny porty pou\u017e\u00edvaj\u00ed VLAN1 jako Native VLAN pro p\u0159enos neozna\u010den\u00e9ho provozu. Nicm\u00e9n\u011b s\u00edt\u00ed Default VLAN je pouze VLAN1, jedin\u00e1 s\u00ed\u0165, kterou nelze zm\u011bnit. Pokud switch obdr\u017e\u00ed neozna\u010den\u00e9 r\u00e1mce na trunkov\u00e9m portu, automaticky je za\u0159ad\u00ed do Native VLAN. <\/p>\n

Jednodu\u0161e \u0159e\u010deno, ve switch\u00edch Cisco m\u016f\u017ee b\u00fdt jako Native VLAN pou\u017eita jak\u00e1koli VLAN, nap\u0159\u00edklad VLAN20, ale jako Default VLAN m\u016f\u017ee b\u00fdt pou\u017eita pouze VLAN1. <\/p>\n

M\u016f\u017eeme se v\u0161ak setkat s probl\u00e9mem. Pokud zm\u011bn\u00edme Native VLAN na trunkov\u00e9m portu prvn\u00edho switchu na VLAN20, port si pomysl\u00ed: \u201eproto\u017ee to je Native VLAN, tak jej\u00ed provoz nemus\u00edm ozna\u010dovat\u201c a ode\u0161le neozna\u010den\u00fd provoz s\u00edt\u011b VLAN20 p\u0159es trunk k druh\u00e9mu switchi. Switch SW2, kdy\u017e tento provoz obdr\u017e\u00ed, \u0159ekne: \u201eskv\u011ble, tenhle provoz nem\u00e1 \u0161t\u00edtek. Podle m\u00fdch nastaven\u00ed, moje Native VLAN je VLAN1, co\u017e znamen\u00e1, \u017ee tento neozna\u010den\u00fd provoz mus\u00edm poslat p\u0159es s\u00ed\u0165 VLAN1\u201c. T\u00edmto zp\u016fsobem SW2 nasm\u011bruje p\u0159ijat\u00fd provoz pouze k PC4 a PC6, i kdy\u017e je ur\u010den pro PC5. To zp\u016fsob\u00ed velk\u00fd bezpe\u010dnostn\u00ed probl\u00e9m, proto\u017ee se sm\u00edch\u00e1 provoz VLAN. Proto je d\u016fle\u017eit\u00e9, aby byly na obou trunkov\u00fdch portech v\u017edy nastaveny stejn\u00e9 Native VLAN; tedy pokud je Native VLAN pro trunk port SW1 VLAN20, pak by m\u011bla b\u00fdt stejn\u00e1 VLAN20 nastavena jako Native VLAN na trunk portu SW2. <\/p>\n

Toto je rozd\u00edl mezi Native VLAN a Default VLAN, a je d\u016fle\u017eit\u00e9 si pamatovat, \u017ee v\u0161echny Native VLAN v trunku mus\u00ed b\u00fdt shodn\u00e9 (pozn\u00e1mka p\u0159ekladatele: proto je lep\u0161\u00ed pou\u017e\u00edvat pro Native VLAN s\u00ed\u0165 jinou ne\u017e VLAN1). <\/p>\n

Pod\u00edvejme se na to z pohledu switche. M\u016f\u017eete se p\u0159ihl\u00e1sit do switche a zadat p\u0159\u00edkaz show vlan brief, po kter\u00e9m uvid\u00edte, \u017ee v\u0161echny porty switche jsou p\u0159ipojeny k Default VLAN1.<\/p>\n

\"\u0160kolen\u00ed
\n
\nN\u00ed\u017ee je uvedeno dal\u0161\u00edch 4 VLAN s\u00edt\u00ed: 1002, 1003, 1004 a 1005. To jsou tak\u00e9 Default VLAN, co\u017e vid\u00edte z jejich ozna\u010den\u00ed. Jsou to s\u00ed\u0165ov\u00e9 standardy vyhrazen\u00e9 pro specifick\u00e9 s\u00edt\u011b \u2014 Token Ring a FDDI. Jak vid\u00edte, jsou v aktivn\u00edm stavu, ale nejsou podporov\u00e1ny, proto\u017ee k switchi nejsou p\u0159ipojeny s\u00edt\u011b uveden\u00fdch standard\u016f. <\/p>\n

Ozna\u010den\u00ed \u201edefault\u201c pro s\u00ed\u0165 VLAN 1 nem\u016f\u017ee b\u00fdt zm\u011bn\u011bno, proto\u017ee to je s\u00ed\u0165 s v\u00fdchoz\u00edm nastaven\u00edm. Proto\u017ee ve v\u00fdchoz\u00edm nastaven\u00ed pat\u0159\u00ed v\u0161echny porty switche do t\u00e9to s\u00edt\u011b, mohou si v\u0161echny switche vz\u00e1jemn\u011b komunikovat ve v\u00fdchoz\u00edm nastaven\u00ed, tedy bez nutnosti dodate\u010dn\u00e9ho nastaven\u00ed port\u016f. Pokud chcete p\u0159ipojit switch k jin\u00e9 s\u00edti, p\u0159ejdete do re\u017eimu glob\u00e1ln\u00edch nastaven\u00ed a vytvo\u0159\u00edte tuto s\u00ed\u0165, nap\u0159\u00edklad VLAN20. Po stisknut\u00ed \u201eEnter\u201c p\u0159ejdete k nastaven\u00edm vytvo\u0159en\u00e9 s\u00edt\u011b a m\u016f\u017eete ji pojmenovat, nap\u0159\u00edklad Management, a pot\u00e9 z nastaven\u00ed vystoupit.<\/p>\n

Pokud nyn\u00ed pou\u017eijete p\u0159\u00edkaz show vlan brief, uvid\u00edte, \u017ee m\u00e1me novou s\u00ed\u0165 VLAN20, kter\u00e1 nen\u00ed p\u0159i\u0159azena \u017e\u00e1dn\u00e9mu portu p\u0159ep\u00edna\u010de. Abychom p\u0159i\u0159adili tomuto s\u00edti konkr\u00e9tn\u00ed port, mus\u00edme vybrat rozhran\u00ed, nap\u0159\u00edklad int e0\/1, p\u0159ej\u00edt do nastaven\u00ed tohoto portu a zadat p\u0159\u00edkazy switchport mode access a switchport access vlan20. <\/p>\n

\"\u0160kolen\u00ed
\n
\nPokud po\u017e\u00e1d\u00e1me syst\u00e9m o zobrazen\u00ed stavu s\u00edt\u00ed VLAN, uvid\u00edme, \u017ee port Ethernet 0\/1 je nyn\u00ed ur\u010den pro s\u00ed\u0165 Management, co\u017e znamen\u00e1, \u017ee byl automaticky p\u0159esunut sem z oblasti port\u016f ur\u010den\u00fdch pro VLAN1.<\/p>\n

\"\u0160kolen\u00ed
\n
\nPamatujte si, \u017ee ka\u017ed\u00fd access-port m\u016f\u017ee m\u00edt pouze jednu Data VLAN, proto nem\u016f\u017ee sou\u010dasn\u011b obsluhovat dv\u011b s\u00edt\u011b VLAN. <\/p>\n

Pod\u00edv\u00e1me se nyn\u00ed na Native VLAN. Pou\u017e\u00edv\u00e1m p\u0159\u00edkaz show int trunk a vid\u00edm, \u017ee port Ethernet0\/0 je vyhrazen pro trunk. <\/p>\n

\"\u0160kolen\u00ed
\n
\nNemusel jsem to d\u011blat speci\u00e1ln\u011b, proto\u017ee protokol DTP automaticky p\u0159i\u0159adil toto rozhran\u00ed pro trunking. Port je v re\u017eimu desirable, enkapsulace typu n-isl, stav portu je trunking, s\u00ed\u0165 je Native VLAN1. <\/p>\n

N\u00ed\u017ee je uveden povolen\u00fd rozsah \u010d\u00edsel s\u00edt\u00ed VLAN pro trunking od 1 do 4094 a je uvedeno, \u017ee u n\u00e1s funguj\u00ed s\u00edt\u011b VLAN1 a VLAN20. Nyn\u00ed p\u0159ejdu do glob\u00e1ln\u00ed konfigura\u010dn\u00edho re\u017eimu a zad\u00e1m p\u0159\u00edkaz int e0\/0, d\u00edky kter\u00e9mu se dostanu do nastaven\u00ed tohoto rozhran\u00ed. Pokou\u0161\u00edm se ru\u010dn\u011b naprogramovat tento port pro pr\u00e1ci v re\u017eimu trunk pomoc\u00ed p\u0159\u00edkazu switchport mode trunk, ale syst\u00e9m p\u0159\u00edkaz nep\u0159ij\u00edm\u00e1 a odpov\u00edd\u00e1, \u017ee: \u201erozhran\u00ed s automatick\u00fdm re\u017eimem enkapsulace trunk nem\u016f\u017ee b\u00fdt p\u0159evedeno do re\u017eimu 'trunk'. <\/p>\n

Proto mus\u00edm nejprve nastavit typ enkapsulace trunku, k \u010demu\u017e pou\u017eiji p\u0159\u00edkaz switchport trunk encapsulation. Syst\u00e9m dal n\u00e1pov\u011bdu s mo\u017en\u00fdmi parametry tohoto p\u0159\u00edkazu:<\/p>\n

dot1q \u2014 b\u011bhem trunkingu port pou\u017e\u00edv\u00e1 enkapsulaci trunk standardu 802.1q;
\nisl \u2014 b\u011bhem trunkingu port pou\u017e\u00edv\u00e1 enkapsulaci trunk pouze propriet\u00e1rn\u00edho protokolu Cisco ISL;
\nnegotiate \u2013 za\u0159\u00edzen\u00ed prov\u00e1d\u00ed enkapsulaci trunku s jak\u00fdmkoli za\u0159\u00edzen\u00edm p\u0159ipojen\u00fdm k tomuto portu.<\/p>\n

\"\u0160kolen\u00ed
\n
\nNa ka\u017ed\u00e9m konci trunku by m\u011bl b\u00fdt vybr\u00e1n stejn\u00fd typ enkapsulace. Ve v\u00fdchoz\u00edm nastaven\u00ed switch \"z krabice\" podporuje pouze trunking typu dot1q, proto\u017ee tento standard podporuj\u00ed prakticky v\u0161echna s\u00ed\u0165ov\u00e1 za\u0159\u00edzen\u00ed. Naprogramuji na\u0161e rozhran\u00ed na enkapsulaci trunkingu podle tohoto standardu pomoc\u00ed p\u0159\u00edkazu switchport trunk encapsulation dot1q, po \u010dem\u017e pou\u017eiji d\u0159\u00edve odm\u00edtnut\u00fd p\u0159\u00edkaz switchport mode trunk. Nyn\u00ed je n\u00e1\u0161 port naprogramov\u00e1n na trunkov\u00fd re\u017eim. <\/p>\n

Pokud je trunk tvo\u0159en dv\u011bma switchemi Cisco, ve v\u00fdchoz\u00edm nastaven\u00ed se pou\u017eije propriet\u00e1rn\u00ed protokol ISL. Pokud v\u0161ak jeden switch podporuje dot1q a ISL, a druh\u00fd pouze dot1q, trunk se automaticky p\u0159evede do re\u017eimu enkapsulace dot1q. Kdy\u017e se znovu pod\u00edv\u00e1me na nastaven\u00ed trunkingu, uvid\u00edme, \u017ee se re\u017eim enkapsulace trunkingov\u00e9ho rozhran\u00ed Et0\/0 zm\u011bnil z n-isl na 802.1q.<\/p>\n

\"\u0160kolen\u00ed
\n
\nPokud zad\u00e1te p\u0159\u00edkaz show int e0\/0 switchport, uvid\u00edte v\u0161echny parametry stavu tohoto portu. <\/p>\n

\"\u0160kolen\u00ed
\n
\nVid\u00edte, \u017ee ve v\u00fdchoz\u00edm nastaven\u00ed je VLAN1 pro trunking \"nativn\u00ed s\u00edt\u00ed\" Native VLAN a p\u0159itom je mo\u017en\u00fd re\u017eim tagov\u00e1n\u00ed provozu Native VLAN. D\u00e1le pou\u017e\u00edv\u00e1m p\u0159\u00edkaz int e0\/0, vstupuji do nastaven\u00ed tohoto rozhran\u00ed a zad\u00e1v\u00e1m switchport trunk, po \u010dem\u017e syst\u00e9m poskytne n\u00e1pov\u011bdu mo\u017en\u00fdch parametr\u016f tohoto p\u0159\u00edkazu. <\/p>\n

\"\u0160kolen\u00ed
\n
\nAllowed znamen\u00e1, \u017ee pokud je port v re\u017eimu trunku, budou nastaveny povolen\u00e9 charakteristiky VLAN. Encapsulation aktivuje enkapsulaci trunkingu, pokud je port v re\u017eimu trunku. Pou\u017e\u00edv\u00e1m parametr native, kter\u00fd znamen\u00e1, \u017ee v re\u017eimu trunku budou pro port nastaveny native-charakteristiky, a zad\u00e1v\u00e1m p\u0159\u00edkaz switchport trunk native VLAN20. T\u00edmto zp\u016fsobem bude VLAN20 v re\u017eimu trunku Native VLAN pro tento port prvn\u00edho switche SW1.<\/p>\n

M\u00e1me dal\u0161\u00ed switch, SW2, jeho\u017e trunkov\u00fd port pou\u017e\u00edv\u00e1 jako Native VLAN VLAN1. Nyn\u00ed vid\u00edte, \u017ee protokol CDP vyd\u00e1v\u00e1 zpr\u00e1vu, \u017ee do\u0161lo k nesouladu Native VLAN na obou konc\u00edch trunku: trunkov\u00fd port prvn\u00edho switche Ethernet0\/0 pou\u017e\u00edv\u00e1 Native VLAN20, zat\u00edmco trunkov\u00fd port druh\u00e9ho \u2014 Native VLAN1. To ilustruje, v \u010dem spo\u010d\u00edv\u00e1 rozd\u00edl mezi Native VLAN a Default VLAN. <\/p>\n

Poj\u010fme se nyn\u00ed pod\u00edvat na b\u011b\u017en\u00fd a roz\u0161\u00ed\u0159en\u00fd rozsah s\u00edt\u00ed VLAN.<\/p>\n

\"\u0160kolen\u00ed
\n
\nDlouhou dobu Cisco podporovala pouze rozsah VLAN \u010d\u00edsel od 1 do 1005, p\u0159i\u010dem\u017e rozsah od 1002 do 1005 byl v\u00fdchoz\u00ed rezervov\u00e1n pro Token Ring a FDDI VLAN. Tyto s\u00edt\u011b byly naz\u00fdv\u00e1ny b\u011b\u017en\u00e9 VLAN. Pokud si pamatujete, VLAN ID p\u0159edstavuje \u0161t\u00edtek velikosti 12 bit\u016f, kter\u00fd umo\u017e\u0148uje nastavit \u010d\u00edslo a\u017e do 4096, nicm\u00e9n\u011b z d\u016fvodu kompatibility Cisco pou\u017e\u00edvala pouze \u010d\u00edsla do 1005. <\/p>\n

Roz\u0161\u00ed\u0159en\u00fd rozsah VLAN zahrnuje \u010d\u00edsla od 1006 do 4095. M\u016f\u017ee b\u00fdt pou\u017eit na star\u0161\u00edch za\u0159\u00edzen\u00edch pouze v p\u0159\u00edpad\u011b, \u017ee podporuj\u00ed VTP v3. Pokud pou\u017e\u00edv\u00e1te VTP v3 a roz\u0161\u00ed\u0159en\u00fd rozsah VLAN, mus\u00edte vypnout podporu VTP v1 a v2, proto\u017ee prvn\u00ed a druh\u00e1 verze nemohou fungovat s VLAN, pokud maj\u00ed \u010d\u00edslo vy\u0161\u0161\u00ed ne\u017e 1005. <\/p>\n

Pokud tedy pou\u017e\u00edv\u00e1te roz\u0161\u00ed\u0159enou VLAN pro star\u00e9 switche, mus\u00ed b\u00fdt VTP nastaveno na \"desable\" a mus\u00edte jej ru\u010dn\u011b nakonfigurovat pro VLAN, jinak nebude mo\u017en\u00e9 aktualizovat datab\u00e1zi VLAN. Pokud pl\u00e1nujete pou\u017e\u00edvat roz\u0161\u00ed\u0159enou VLAN s VTP, budete pot\u0159ebovat t\u0159et\u00ed verzi VTP.<\/p>\n

Pod\u00edvejme se na stav VTP pomoc\u00ed p\u0159\u00edkazu show vtp status. Vid\u00edte, \u017ee switch pracuje v re\u017eimu VTP v2, p\u0159i\u010dem\u017e je podporov\u00e1na verze 1 a 3. P\u0159i\u0159adil jsem mu dom\u00e9nov\u00e9 jm\u00e9no nwking.org.<\/p>\n

Zde je d\u016fle\u017eit\u00fd re\u017eim spr\u00e1vy VTP \u2013 server. Vid\u00edte, \u017ee maxim\u00e1ln\u00ed po\u010det podporovan\u00fdch VLAN s\u00edt\u00ed je 1005. Tak\u017ee je jasn\u00e9, \u017ee tento switch v\u00fdchoz\u00edm zp\u016fsobem podporuje pouze b\u011b\u017en\u00fd rozsah VLAN. <\/p>\n

\"\u0160kolen\u00ed
\n
\nTe\u010f nap\u00ed\u0161u p\u0159\u00edkaz show vlan brief a uvid\u00edte VLAN20 Management, kter\u00e1 je zde zm\u00edn\u011bna, proto\u017ee je sou\u010d\u00e1st\u00ed datab\u00e1ze VLAN.<\/p>\n

\"\u0160kolen\u00ed
\n
\nPokud nyn\u00ed po\u017e\u00e1d\u00e1m o zobrazen\u00ed aktu\u00e1ln\u00ed konfigurace za\u0159\u00edzen\u00ed p\u0159\u00edkazem show run, neuvid\u00edme \u017e\u00e1dn\u00e9 zm\u00ednky o VLAN, proto\u017ee se nach\u00e1zej\u00ed pouze v datab\u00e1zi VLAN.
\nDal\u0161\u00ed pou\u017eiji p\u0159\u00edkaz vtp mode k nastaven\u00ed re\u017eimu VTP. Switche star\u0161\u00edch model\u016f m\u011bly pro tento p\u0159\u00edkaz pouze t\u0159i parametry: client, kter\u00fd p\u0159evede switch do re\u017eimu klienta, server, kter\u00fd aktivuje re\u017eim serveru, a transparent, kter\u00fd p\u0159ev\u00e1d\u00ed switch do \"transparentn\u00edho\" re\u017eimu. Proto\u017ee na star\u00fdch switchech nebylo mo\u017en\u00e9 VTP \u00fapln\u011b vypnout, v tomto re\u017eimu switch, z\u016fst\u00e1vaj\u00edc\u00ed v dom\u00e9n\u011b VTP, jednodu\u0161e p\u0159estal p\u0159ij\u00edmat aktualizace datab\u00e1ze VLAN s\u00edt\u00ed, kter\u00e9 p\u0159ich\u00e1zely na jeho porty prost\u0159ednictv\u00edm protokolu VTP.<\/p>\n

Nov\u00e9 switche obsahuj\u00ed parametr off, kter\u00fd umo\u017e\u0148uje \u00fapln\u00e9 vypnut\u00ed re\u017eimu VTP. P\u0159eve\u010fme za\u0159\u00edzen\u00ed do transparentn\u00edho re\u017eimu pomoc\u00ed p\u0159\u00edkazu vtp mode transparent a znovu se pod\u00edvejme na aktu\u00e1ln\u00ed konfiguraci. Jak vid\u00edte, nyn\u00ed se do n\u00ed p\u0159idala polo\u017eka o VLAN20. T\u00edm p\u00e1dem, pokud p\u0159id\u00e1me n\u011bjakou VLAN s\u00ed\u0165, jej\u00ed\u017e \u010d\u00edslo se nach\u00e1z\u00ed v b\u011b\u017en\u00e9m rozsahu VLAN od 1 do 1005, a z\u00e1rove\u0148 bude VTP v re\u017eimu transparent nebo off, podle vnit\u0159n\u00edch politik VLAN bude tato s\u00ed\u0165 p\u0159id\u00e1na do aktu\u00e1ln\u00ed konfigurace a do datab\u00e1ze virtu\u00e1ln\u00edch lok\u00e1ln\u00edch s\u00edt\u00ed.<\/p>\n

Zkus\u00edme p\u0159idat VLAN 3000 a uvid\u00edte, \u017ee i v transparentn\u00edm re\u017eimu se objevila v aktu\u00e1ln\u00ed konfiguraci. Obvykle pokud chceme p\u0159idat s\u00ed\u0165 z roz\u0161\u00ed\u0159en\u00e9ho rozsahu VLAN, mus\u00edme pou\u017e\u00edt p\u0159\u00edkaz vtp version 3. Jak vid\u00edte, ob\u011b s\u00edt\u011b VLAN20 a VLAN3000 jsou zobrazeny v aktu\u00e1ln\u00ed konfiguraci.<\/p>\n

Pokud p\u0159ejdete z re\u017eimu transparentn\u00edho do re\u017eimu serveru pomoc\u00ed p\u0159\u00edkazu vtp mode server a pot\u00e9 se znovu pod\u00edv\u00e1te na aktu\u00e1ln\u00ed konfiguraci, uvid\u00edte, \u017ee z\u00e1znamy o VLAN \u00fapln\u011b zmizely. K tomu do\u0161lo, proto\u017ee ve\u0161ker\u00e9 informace o VLAN jsou uchov\u00e1v\u00e1ny pouze v datab\u00e1zi VLAN a je mo\u017en\u00e9 je zobrazit pouze v transparentn\u00edm re\u017eimu VTP. Jeliko\u017e jsem zapnul re\u017eim VTP v3, po pou\u017eit\u00ed p\u0159\u00edkazu show vtp status m\u016f\u017eete vid\u011bt, \u017ee maxim\u00e1ln\u00ed po\u010det podporovan\u00fdch VLAN se zv\u00fd\u0161il na 4096. <\/p>\n

Tak\u017ee datab\u00e1ze VTP v1 a VTP v2 podporuj\u00ed pouze b\u011b\u017en\u00e9 VLAN s \u010d\u00edsly od 1 do 1005, zat\u00edmco datab\u00e1ze VTP v3 zahrnuje z\u00e1znamy o roz\u0161\u00ed\u0159en\u00fdch VLAN s \u010d\u00edsly od 1 do 4096. Pokud pou\u017e\u00edv\u00e1te re\u017eim VTP transparent nebo VTP off, informace o VLAN budou p\u0159id\u00e1ny do aktu\u00e1ln\u00ed konfigurace. Pokud chcete pou\u017e\u00edvat roz\u0161\u00ed\u0159en\u00fd rozsah VLAN, za\u0159\u00edzen\u00ed mus\u00ed b\u00fdt v re\u017eimu VTP v3. To je rozd\u00edl mezi b\u011b\u017en\u00fdmi a roz\u0161\u00ed\u0159en\u00fdmi VLAN.<\/p>\n

A nyn\u00ed porovn\u00e1me VLAN pro data a VLAN pro hlasov\u00e9 p\u0159enosy. Pokud si pamatujete, \u0159ekl jsem, \u017ee ka\u017ed\u00fd port m\u016f\u017ee sou\u010dasn\u011b pat\u0159it pouze k jedn\u00e9 VLAN. <\/p>\n

\"\u0160kolen\u00ed
\n
\nV mnoha p\u0159\u00edpadech pot\u0159ebujeme nastavit port pro pr\u00e1ci s IP telefonem. Modern\u00ed IP telefony Cisco maj\u00ed zabudovan\u00fd switch, tak\u017ee m\u016f\u017eete telefon jednodu\u0161e p\u0159ipojit k z\u00e1suvce na st\u011bn\u011b a pomoc\u00ed patch cordu k vlastn\u00edmu po\u010d\u00edta\u010di. Probl\u00e9m spo\u010d\u00edval v tom, \u017ee z\u00e1suvka na st\u011bn\u011b, do kter\u00e9 se p\u0159ipojuje port telefonu, musela m\u00edt dv\u011b r\u016fzn\u00e9 VLAN. Jak jsme ji\u017e probrali v video lekc\u00edch 11 a 12, co je t\u0159eba ud\u011blat, aby se zabr\u00e1nilo smy\u010dk\u00e1m provozu, jak pou\u017e\u00edt koncept \u201enativn\u00ed\u201c VLAN, kter\u00e1 propou\u0161t\u00ed netegovan\u00fd provoz, ale to byly v\u0161echno pouze obchvatov\u00e9 metody. Definitivn\u00edm \u0159e\u0161en\u00edm probl\u00e9mu se stal koncept rozd\u011blen\u00ed VLAN na s\u00edt\u011b pro datov\u00fd provoz a s\u00edt\u011b pro hlasov\u00fd provoz. <\/p>\n

V tomto p\u0159\u00edpad\u011b slu\u010dujete v\u0161echny telefonn\u00ed linky do hlasov\u00e9 VLAN. Na obr\u00e1zku je zn\u00e1zorn\u011bno, \u017ee po\u010d\u00edta\u010de PC1 a PC2 mohou pat\u0159it do \u010derven\u00e9 s\u00edt\u011b VLAN20, po\u010d\u00edta\u010d PC3 do zelen\u00e9 s\u00edt\u011b VLAN30, ale v\u0161echny s nimi spojen\u00e9 IP telefony budou pat\u0159it do jedn\u00e9 a t\u00e9 sam\u00e9 \u017elut\u00e9 hlasov\u00e9 s\u00edt\u011b VLAN50. <\/p>\n

Fakticky ka\u017ed\u00fd port switche SW1 bude m\u00edt sou\u010dasn\u011b 2 s\u00edt\u011b VLAN \u2013 pro data a pro hlas. <\/p>\n

\"\u0160kolen\u00ed
\n
\nJak jsem ji\u017e \u0159ekl, access VLAN m\u00e1 v\u017edy jednu VLAN, nem\u016f\u017eete m\u00edt dv\u011b VLAN na jednom portu. Nem\u016f\u017eete sou\u010dasn\u011b pou\u017e\u00edt na jednom rozhran\u00ed p\u0159\u00edkazy switchport access vlan 10, switchport access vlan 20 a switchport access vlan 50. Ale m\u016f\u017eete pou\u017e\u00edt p\u0159\u00edkaz pro stejn\u00e9 rozhran\u00ed dv\u011b p\u0159\u00edkazy: p\u0159\u00edkaz switchport access vlan 10 a p\u0159\u00edkaz switchport voice vlan 50. Tak\u017ee, proto\u017ee IP telefon obsahuje uvnit\u0159 switch, m\u016f\u017ee enkapsulovat a odes\u00edlat hlasov\u00fd provoz VLAN50 a sou\u010dasn\u011b p\u0159ij\u00edmat a odes\u00edlat v re\u017eimu switchport access provoz datov\u00e9 s\u00edt\u011b VLAN20 switchem SW1. Pod\u00edvejme se, jak se tento re\u017eim nastavuje. <\/p>\n

Nejprve vytvo\u0159\u00edme s\u00ed\u0165 VLAN50 a pot\u00e9 p\u0159ejdeme k nastaven\u00ed rozhran\u00ed Ethernet 0\/1 a nastav\u00edme ho na re\u017eim switchport mode access. Pot\u00e9 postupn\u011b zad\u00e1m p\u0159\u00edkazy switchport access vlan 10 a switchport voice vlan 50.<\/p>\n

Zapomn\u011bl jsem nastavit stejn\u00fd re\u017eim VLAN pro trunk, proto p\u0159ejdu k nastaven\u00ed portu Ethernet 0\/0 a zad\u00e1m p\u0159\u00edkaz switchport trunk native vlan 1. Nyn\u00ed po\u017e\u00e1d\u00e1m o zobrazen\u00ed parametr\u016f VLAN a vid\u00edte, \u017ee nyn\u00ed m\u00e1me na portu Ethernet 0\/1 ob\u011b s\u00edt\u011b \u2013 VLAN 50 a VLAN20.<\/p>\n

\"\u0160kolen\u00ed
\n
\nPokud vid\u00edte, \u017ee na jednom portu jsou um\u00edst\u011bny dv\u011b VLAN, znamen\u00e1 to, \u017ee jedna z nich je hlasov\u00e1 s\u00ed\u0165 Voice VLAN. To nem\u016f\u017ee b\u00fdt trunk, proto\u017ee pokud se pod\u00edv\u00e1te na parametry trunku pomoc\u00ed p\u0159\u00edkazu show int trunk, zjist\u00edte, \u017ee trunkov\u00fd port obsahuje v\u0161echny VLAN s\u00edt\u011b v\u010detn\u011b v\u00fdchoz\u00ed s\u00edt\u011b VLAN1. <\/p>\n

\"\u0160kolen\u00ed
\n
\nLze \u0159\u00edci, \u017ee technicky, kdy\u017e vytv\u00e1\u0159\u00edte datovou s\u00ed\u0165 a hlasovou s\u00ed\u0165, ka\u017ed\u00fd z t\u011bchto port\u016f se chov\u00e1 jako polotrunk: pro jednu s\u00ed\u0165 funguje jako trunk, pro druhou jako access port. <\/p>\n

Pokud zad\u00e1te p\u0159\u00edkaz show int e0\/1 switchport, m\u016f\u017eete vid\u011bt, \u017ee n\u011bkter\u00e9 charakteristiky odpov\u00eddaj\u00ed dv\u011bma re\u017eim\u016fm provozu: m\u00e1me jak static access, tak encapsulation trunking. P\u0159itom re\u017eimu access mode odpov\u00edd\u00e1 datov\u00e1 s\u00ed\u0165 VLAN 20 Management a z\u00e1rove\u0148 je p\u0159\u00edtomna hlasov\u00e1 s\u00ed\u0165 VLAN 50. <\/p>\n

\"\u0160kolen\u00ed
\n
\nM\u016f\u017eete se pod\u00edvat na aktu\u00e1ln\u00ed konfiguraci, kter\u00e1 tak\u00e9 uk\u00e1\u017ee, \u017ee na tomto portu jsou p\u0159\u00edtomny s\u00edt\u011b access VLAN 20 a voice VLAN 50. <\/p>\n

\"\u0160kolen\u00ed
\n
\nTo je rozd\u00edl mezi s\u00edt\u011bmi Data VLAN a Voice VLAN. Douf\u00e1m, \u017ee jste pochopili v\u0161e, o \u010dem jsem hovo\u0159il, pokud ne \u2013 jednodu\u0161e se pod\u00edvejte na tento video \u0443\u0440\u043e\u043a znovu. <\/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":"

\u041c\u044b \u0443\u0436\u0435 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u043b\u0438 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u044b\u0435 \u0441\u0435\u0442\u0438 VLAN \u0432 \u0432\u0438\u0434\u0435\u043e\u0443\u0440\u043e\u043a\u0430\u0445 \u0414\u0435\u043d\u044c 11, 12 \u0438 13 \u0438 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0438\u043c \u0438\u0445 \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u0435 \u0432 \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0438\u0438 \u0441 \u0442\u0435\u043c\u0430\u0442\u0438\u043a\u043e\u0439 ICND2. \u042f \u0437\u0430\u043f\u0438\u0441\u0430\u043b \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0435 \u0432\u0438\u0434\u0435\u043e, \u043a\u043e\u0442\u043e\u0440\u043e\u0435 \u043e\u0437\u043d\u0430\u043c\u0435\u043d\u043e\u0432\u0430\u043b\u043e \u043e\u043a\u043e\u043d\u0447\u0430\u043d\u0438\u0435 \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u043a\u0438 \u043a \u0441\u0434\u0430\u0447\u0435 \u044d\u043a\u0437\u0430\u043c\u0435\u043d\u0430 ICND1, \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043c\u0435\u0441\u044f\u0446\u0435\u0432 \u043d\u0430\u0437\u0430\u0434 \u0438 \u0432\u0441\u0435 \u044d\u0442\u043e \u0432\u0440\u0435\u043c\u044f \u0434\u043e \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0433\u043e \u0434\u043d\u044f \u0431\u044b\u043b \u043e\u0447\u0435\u043d\u044c \u0437\u0430\u043d\u044f\u0442. \u0414\u0443\u043c\u0430\u044e, \u043c\u043d\u043e\u0433\u0438\u0435 \u0438\u0437 \u0432\u0430\u0441 \u0443\u0441\u043f\u0435\u0448\u043d\u043e \u0441\u0434\u0430\u043b\u0438 \u044d\u0442\u043e\u0442 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28433,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37888","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 34. Roz\u0161\u00ed\u0159en\u00e1 koncepce VLAN | ProHoster","description":"Ji\u017e jsme zkoumali m\u00edstn\u00ed VLAN s\u00edt\u011b ve video lekc\u00edch Den 11, 12 a 13 a dnes budeme pokra\u010dovat v jejich studiu v souladu s t\u00e9matem ICND2.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-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 34. \u0420\u0430\u0441\u0448\u0438\u0440\u0435\u043d\u043d\u0430\u044f \u043a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f VLAN | ProHoster","og:description":"\u041c\u044b \u0443\u0436\u0435 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u043b\u0438 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u044b\u0435 \u0441\u0435\u0442\u0438 VLAN \u0432 \u0432\u0438\u0434\u0435\u043e\u0443\u0440\u043e\u043a\u0430\u0445 \u0414\u0435\u043d\u044c 11, 12 \u0438 13 \u0438 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0438\u043c \u0438\u0445 \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u0435 \u0432 \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0438\u0438 \u0441 \u0442\u0435\u043c\u0430\u0442\u0438\u043a\u043e\u0439 ICND2.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-34-rasshirennaya-kontseptsiya-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:20:23+00:00","article:modified_time":"2019-10-31T19:20:23+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37888","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 19:38:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:19:21","updated":"2026-01-23 19:38: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\/37888","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=37888"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37888\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/28433"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=37888"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=37888"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=37888"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}