{"id":37511,"date":"2019-10-31T22:18:02","date_gmt":"2019-10-31T19:18:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-marshrutizatsii\/"},"modified":"2019-10-31T22:18:02","modified_gmt":"2019-10-31T19:18:02","slug":"trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-marshrutizatsii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-marshrutizatsii","title":{"rendered":"Tr\u00e9nink Cisco 200-125 CCNA v3.0. Den 23. Pokro\u010dil\u00e9 technologie routingu","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dnes se podrobn\u011bji pod\u00edv\u00e1me na n\u011bkter\u00e9 aspekty sm\u011brov\u00e1n\u00ed. Ne\u017e za\u010dneme, chci odpov\u011bd\u011bt na ot\u00e1zku student\u016f ohledn\u011b m\u00fdch profil\u016f na soci\u00e1ln\u00edch s\u00edt\u00edch. Na lev\u00e9 stran\u011b jsem um\u00edstil odkazy na profily na\u0161\u00ed spole\u010dnosti a na prav\u00e9 stran\u011b \u2013 na m\u00e9 osobn\u00ed profily. R\u00e1d bych poznamenal, \u017ee nep\u0159id\u00e1v\u00e1m lidi do sv\u00fdch p\u0159\u00e1tel na Facebooku, pokud je osobn\u011b nezn\u00e1m, tak\u017ee mi pros\u00edm nepos\u00edlejte \u017e\u00e1dosti o p\u0159\u00e1telstv\u00ed. <\/p>\n

\"Tr\u00e9nink
\n
\nJednodu\u0161e se m\u016f\u017eete p\u0159ihl\u00e1sit k m\u00e9mu profilu na Facebooku a b\u00fdt v obraze o v\u0161ech ud\u00e1lostech. Odpov\u00edd\u00e1m na zpr\u00e1vy na sv\u00e9m profilu LinkedIn, tak\u017ee mi tam m\u016f\u017eete ps\u00e1t, a samoz\u0159ejm\u011b jsem velmi aktivn\u00ed na Twitteru. Pod t\u00edmto video tutori\u00e1lem jsou odkazy na v\u0161ech 6 soci\u00e1ln\u00edch s\u00edt\u00ed, tak\u017ee je m\u016f\u017eete vyu\u017e\u00edt. <\/a><\/noindex><\/p>\n

Jak u\u017e je obvykl\u00e9, dnes probereme t\u0159i t\u00e9mata. Prvn\u00ed se zab\u00fdv\u00e1 vysv\u011btlen\u00edm podstaty sm\u011brov\u00e1n\u00ed, kde v\u00e1m pov\u00edm o sm\u011brovac\u00edch tabulk\u00e1ch, statick\u00e9m sm\u011brov\u00e1n\u00ed a tak d\u00e1le. Pot\u00e9 se zam\u011b\u0159\u00edme na meziswitchov\u00e9 sm\u011brov\u00e1n\u00ed, tedy jak prob\u00edh\u00e1 sm\u011brov\u00e1n\u00ed mezi dv\u011bma switche. Na konci lekce se sezn\u00e1m\u00edme s konceptem sm\u011brov\u00e1n\u00ed Inter-VLAN, kdy jeden switch interaguje s n\u011bkolika VLAN a jak\u00fd zp\u016fsobem doch\u00e1z\u00ed k propojen\u00ed mezi t\u011bmito s\u00edt\u011bmi. Je to velmi zaj\u00edmav\u00e9 t\u00e9ma, a mo\u017en\u00e1 budete cht\u00edt si je n\u011bkolikr\u00e1t p\u0159ehr\u00e1t. Je tu je\u0161t\u011b jedno zaj\u00edmav\u00e9 t\u00e9ma, kter\u00e9 se naz\u00fdv\u00e1 Router-on-a-Stick. <\/p>\n

Tak\u017ee, co je to sm\u011brovac\u00ed tabulka? Je to tabulka, na jej\u00edm\u017e z\u00e1klad\u011b sm\u011brova\u010de rozhoduj\u00ed o sm\u011brov\u00e1n\u00ed. Vid\u00edte, jak vypad\u00e1 typick\u00e1 sm\u011brovac\u00ed tabulka sm\u011brova\u010d\u016f Cisco. Ka\u017ed\u00fd po\u010d\u00edta\u010d b\u011b\u017e\u00edc\u00ed na Windows m\u00e1 tak\u00e9 sm\u011brovac\u00ed tabulku, ale to je jin\u00e1 t\u00e9ma. <\/p>\n

P\u00edsmeno R na za\u010d\u00e1tku \u0159\u00e1dku znamen\u00e1, \u017ee cesta k s\u00edti 192.168.30.0\/24 je zaji\u0161t\u011bna protokolem RIP, C znamen\u00e1, \u017ee s\u00ed\u0165 je p\u0159\u00edmo p\u0159ipojena k rozhran\u00ed sm\u011brova\u010de, S ozna\u010duje statick\u00e9 sm\u011brov\u00e1n\u00ed a te\u010dka po tomto p\u00edsmenu ukazuje, \u017ee tato cesta je candidate default, nebo kandid\u00e1tem pro statick\u00e9 sm\u011brov\u00e1n\u00ed. Existuje n\u011bkolik typ\u016f statick\u00fdch tras, a dnes si je p\u0159edstav\u00edme. <\/p>\n

\"Tr\u00e9nink
\n
\nPod\u00edvejme se na prvn\u00ed s\u00ed\u0165 192.168.30.0\/24. V \u0159\u00e1dku vid\u00edte dv\u011b \u010d\u00edsla v hranat\u00fdch z\u00e1vork\u00e1ch odd\u011blen\u00e1 lom\u00edtkem, o kter\u00fdch jsme ji\u017e hovo\u0159ili. Prvn\u00ed \u010d\u00edslo 120 \u2013 to je administrativn\u00ed vzd\u00e1lenost, kter\u00e1 charakterizuje m\u00edru d\u016fv\u011bry k t\u00e9to trase. P\u0159edstavme si, \u017ee v tabulce existuje dal\u0161\u00ed trasa k t\u00e9to s\u00edti, ozna\u010den\u00e1 p\u00edsmenem C nebo S s ni\u017e\u0161\u00ed administrativn\u00ed vzd\u00e1lenost\u00ed, nap\u0159\u00edklad 1, jako pro statick\u00e9 sm\u011brov\u00e1n\u00ed. V t\u00e9to tabulce nenajdete dv\u011b stejn\u00e9 s\u00edt\u011b, pokud nepou\u017eijeme mechanismus, jako je vyva\u017eov\u00e1n\u00ed zat\u00ed\u017een\u00ed, ale p\u0159edpokl\u00e1dejme, \u017ee m\u00e1me 2 z\u00e1znamy pro jednu a tut\u00e9\u017e s\u00ed\u0165. Tak\u017ee, pokud uvid\u00edte men\u0161\u00ed \u010d\u00edslo, bude to znamenat, \u017ee tato trasa si zaslou\u017e\u00ed v\u011bt\u0161\u00ed d\u016fv\u011bru, a naopak, \u010d\u00edm v\u011bt\u0161\u00ed je hodnota administrativn\u00ed vzd\u00e1lenosti, t\u00edm men\u0161\u00ed d\u016fv\u011bru tato trasa zaslou\u017e\u00ed. D\u00e1le v \u0159\u00e1dku je uvedeno, p\u0159es jak\u00e9 rozhran\u00ed by m\u011bl b\u00fdt pos\u00edl\u00e1n provoz \u2013 v na\u0161em p\u0159\u00edpad\u011b je to port 192.168.20.1 FastEthernet0\/1. Tak z jak\u00fdch komponent\u016f se skl\u00e1d\u00e1 sm\u011brovac\u00ed tabulka. <\/p>\n

Nyn\u00ed si promluvme o tom, jak router p\u0159ij\u00edm\u00e1 rozhodnut\u00ed o sm\u011brov\u00e1n\u00ed. V\u00fd\u0161e jsem zm\u00ednil kandid\u00e1ta zdroje a nyn\u00ed \u0159eknu, co to znamen\u00e1. P\u0159edpokl\u00e1dejme, \u017ee na router doraz\u00ed provoz pro s\u00ed\u0165 30.1.1.1, z\u00e1znam o kter\u00e9 chyb\u00ed v sm\u011brovac\u00ed tabulce. V obvykl\u00e9m p\u0159\u00edpad\u011b router tento provoz jednodu\u0161e odm\u00edtne, ale pokud je v tabulce z\u00e1znam o kandid\u00e1tovi zdroje, znamen\u00e1 to, \u017ee v\u0161e, co router nezn\u00e1, bude sm\u011brov\u00e1no k candidate default. V tomto p\u0159\u00edpad\u011b z\u00e1znam nazna\u010duje, \u017ee provoz, kter\u00fd dorazil pro s\u00ed\u0165, kterou router nezn\u00e1, by m\u011bl b\u00fdt d\u00e1le sm\u011brov\u00e1n p\u0159es port 192.168.10.1. Takto provoz pro s\u00ed\u0165 30.1.1.1 projde trasou, kter\u00e1 je kandid\u00e1tem zdroje. <\/p>\n

Kdy\u017e router obdr\u017e\u00ed po\u017eadavek na nav\u00e1z\u00e1n\u00ed spojen\u00ed s n\u011bjakou IP adresou, nejprve se pod\u00edv\u00e1, zda se tato adresa nach\u00e1z\u00ed v n\u011bjak\u00e9 ur\u010dit\u00e9 trase. Pokud tedy obdr\u017e\u00ed provoz pro s\u00ed\u0165 30.1.1.1, nejprve zkontroluje, zda je jej\u00ed adresa obsa\u017eena ve konkr\u00e9tn\u00ed polo\u017ece v tabulce sm\u011brov\u00e1n\u00ed. Tak\u017ee pokud router obdr\u017e\u00ed provoz pro 192.168.30.1, po kontrole v\u0161ech polo\u017eek uvid\u00ed, \u017ee tato adresa je sou\u010d\u00e1st\u00ed rozsahu adres pro s\u00ed\u0165 192.168.30.0\/24, a pot\u00e9 po\u0161le provoz touto trasou. Pokud nenajde \u017e\u00e1dn\u00e9 konkr\u00e9tn\u00ed polo\u017eky pro s\u00ed\u0165 30.1.1.1, router po\u0161le ur\u010den\u00fd provoz podle defaultn\u00ed kandid\u00e1tn\u00ed trasy. Takto jsou p\u0159ij\u00edm\u00e1na rozhodnut\u00ed: nejprve se kontroluj\u00ed polo\u017eky konkr\u00e9tn\u00edch tras v tabulce a pot\u00e9 se pou\u017e\u00edv\u00e1 defaultn\u00ed kandid\u00e1tn\u00ed trasa.
\nNyn\u00ed se pod\u00edvejme na r\u016fzn\u00e9 typy statick\u00fdch tras. Prvn\u00edm typem je defaultn\u00ed trasa, nebo trasa podle um\u00edst\u011bn\u00ed. <\/p>\n

\"Tr\u00e9nink
\n
\nJak jsem ji\u017e zm\u00ednil, pokud router obdr\u017e\u00ed provoz, kter\u00fd je ur\u010den pro nezn\u00e1mou s\u00ed\u0165, po\u0161le jej po defaultn\u00ed trase. O tom, \u017ee je nastavena defaultn\u00ed trasa, informuje polo\u017eka Gateway of last resort is 192.168.10.1 to network 0.0.0.0, tedy \u201eBr\u00e1na posledn\u00edho uzn\u00e1n\u00ed pro s\u00ed\u0165 0.0.0.0 m\u00e1 IP adresu 192.168.10.1\u201c. Tato trasa je uvedena v posledn\u00edm \u0159\u00e1dku tabulky sm\u011brov\u00e1n\u00ed, ozna\u010den\u00e9m p\u00edsmenem S s te\u010dkou. <\/p>\n

Tento parametr lze nastavit z re\u017eimu glob\u00e1ln\u00ed konfigurace. Pro b\u011b\u017enou trasu podle protokolu RIP mus\u00edte zadat p\u0159\u00edkaz ip route, uv\u00e9st identifik\u00e1tor p\u0159\u00edslu\u0161n\u00e9 s\u00edt\u011b, v na\u0161em p\u0159\u00edpad\u011b 192.168.30.0, a masku pods\u00edt\u011b 255.255.255.0, a pot\u00e9 uv\u00e9st 192.168.20.1 jako dal\u0161\u00ed skok. Kdy\u017e v\u0161ak nastavujete defaultn\u00ed trasu, nemus\u00edte uv\u00e1d\u011bt identifik\u00e1tor s\u00edt\u011b a masku, sta\u010d\u00ed zadat ip route 0.0.0.0 0.0.0.0, tedy m\u00edsto adresy masky pods\u00edt\u011b znova zad\u00e1te \u010dty\u0159i nuly, a na konci \u0159\u00e1dku uvedete adresu 192.168.20.1, kter\u00e1 bude znamenat defaultn\u00ed trasu.
\nDal\u0161\u00edm typem statick\u00e9 trasy je s\u00ed\u0165ov\u00e1 trasa. Pro nastaven\u00ed s\u00ed\u0165ov\u00e9 trasy je nutn\u00e9 uv\u00e9st celou s\u00ed\u0165, tedy pou\u017e\u00edt p\u0159\u00edkaz ip route 192.168.30.0 255.255.255.0, kde 0 na konci masky pods\u00edt\u011b znamen\u00e1 cel\u00fd rozsah 256 adres pro s\u00ed\u0165 \/24, a uv\u00e9st IP adresu dal\u0161\u00edho skoku.<\/p>\n

Nyn\u00ed nakresl\u00edm \u0161ablonu, kter\u00e1 zn\u00e1zor\u0148uje p\u0159\u00edkaz pro nastaven\u00ed v\u00fdchoz\u00edho a s\u00ed\u0165ov\u00e9ho sm\u011brov\u00e1n\u00ed. Vypad\u00e1 n\u00e1sledovn\u011b:<\/p>\n

ip route prvn\u00ed \u010d\u00e1st adresy druh\u00e1 \u010d\u00e1st adresy . <\/p>\n

Pro v\u00fdchoz\u00ed sm\u011brov\u00e1n\u00ed budou prvn\u00ed a druh\u00e1 \u010d\u00e1st adresy slo\u017eeny z 0.0.0.0, zat\u00edmco pro s\u00ed\u0165ov\u00e9 sm\u011brov\u00e1n\u00ed prvn\u00ed \u010d\u00e1st p\u0159edstavuje identifik\u00e1tor s\u00edt\u011b a druh\u00e1 \u010d\u00e1st je maska pods\u00edt\u011b. D\u00e1le bude um\u00edst\u011bna IP adresa s\u00edt\u011b, do kter\u00e9 se router rozhodl prov\u00e9st dal\u0161\u00ed skok. <\/p>\n

\"Tr\u00e9nink
\n
\nPro nastaven\u00ed sm\u011bru hosta se pou\u017e\u00edv\u00e1 IP adresa konkr\u00e9tn\u00edho hosta. V \u0161ablon\u011b p\u0159\u00edkazu to bude prvn\u00ed \u010d\u00e1st adresy, v na\u0161em p\u0159\u00edpad\u011b 192.168.30.1, kter\u00e1 ukazuje na konkr\u00e9tn\u00ed za\u0159\u00edzen\u00ed. Druh\u00e1 \u010d\u00e1st p\u0159edstavuje masku pods\u00edt\u011b 255.255.255.255, kter\u00e1 rovn\u011b\u017e ukazuje na IP adresu konkr\u00e9tn\u00edho hosta, nikoli na celou s\u00ed\u0165 \/24. Pot\u00e9 je t\u0159eba uv\u00e9st IP adresu dal\u0161\u00edho skoku. Takto lze nastavit sm\u011br hosta. <\/p>\n

Shrnovac\u00ed sm\u011br \u2013 to je shrnovac\u00ed sm\u011br. Pamatujete si, \u017ee jsme ji\u017e diskutovali o ot\u00e1zce sumarizace sm\u011brov\u00e1n\u00ed, kdy\u017e m\u00e1me ur\u010dit\u00fd rozsah IP adres. Vezm\u011bme nap\u0159\u00edklad prvn\u00ed s\u00ed\u0165 192.168.30.0\/24 a p\u0159edstavme si, \u017ee m\u00e1me router R1, kter\u00fd je p\u0159ipojen k s\u00edti 192.168.30.0\/24 s \u010dty\u0159mi IP adresami: 192.168.30.4, 192.168.30.5, 192.168.30.6 a 192.168.30.7. Lom\u00edtko 24 znamen\u00e1, \u017ee v t\u00e9to s\u00edti je celkem 256 platn\u00fdch adres, av\u0161ak v tomto p\u0159\u00edpad\u011b m\u00e1me pouze 4 IP adresy. <\/p>\n

\"Tr\u00e9nink
\n
\nPokud ozn\u00e1m\u00edm, \u017ee ve\u0161ker\u00fd provoz pro s\u00ed\u0165 192.168.30.0\/24 mus\u00ed b\u00fdt sm\u011brov\u00e1n touto cestou, bylo by to nepravdiv\u00e9, proto\u017ee takov\u00e1 IP adresa jako 192.168.30.1 m\u016f\u017ee b\u00fdt nedostupn\u00e1 p\u0159es toto rozhran\u00ed. Proto v tomto p\u0159\u00edpad\u011b nem\u016f\u017eeme pou\u017e\u00edt jako prvn\u00ed \u010d\u00e1st adresy 192.168.30.0, ale mus\u00edme uv\u00e9st, kter\u00e9 konkr\u00e9tn\u00ed adresy budou dostupn\u00e9. V tomto p\u0159\u00edpad\u011b 4 konkr\u00e9tn\u00ed adresy budou dostupn\u00e9 p\u0159es prav\u00e9 rozhran\u00ed, zat\u00edmco ostatn\u00ed adresy s\u00edt\u011b \u2013 p\u0159es lev\u00e9 rozhran\u00ed routeru. To je d\u016fvod, pro\u010d mus\u00edme nastavit shrnovac\u00ed, nebo souhrnn\u00fd sm\u011br.<\/p>\n

Z princip\u016f sumarizace tras si pamatujeme, \u017ee v jedn\u00e9 pods\u00edti z\u016fst\u00e1vaj\u00ed prvn\u00ed t\u0159i oktety adresy nezm\u011bn\u011bny, a mus\u00edme vytvo\u0159it pods\u00ed\u0165, kter\u00e1 by spojila v\u0161echny 4 adresy. K tomu mus\u00edme uv\u00e9st v prvn\u00ed \u010d\u00e1sti adresy 192.168.30.4 a ve druh\u00e9 \u010d\u00e1sti pou\u017e\u00edt masku pods\u00edt\u011b 255.255.255.252, kde 252 znamen\u00e1, \u017ee v t\u00e9to pods\u00edti jsou obsa\u017eeny 4 IP adresy: .4, .5, .6 a .7.<\/p>\n

Pokud budete m\u00edt v tabulce sm\u011brov\u00e1n\u00ed dv\u011b polo\u017eky: trasu RIP pro s\u00ed\u0165 192.168.30.0\/24 a sumarizovanou trasu 192.168.30.4\/252, pak podle princip\u016f sm\u011brov\u00e1n\u00ed bude priorizovanou trasou pro konkr\u00e9tn\u00ed provoz pr\u00e1v\u011b Sumarizovan\u00e1 trasa. V\u0161e, co se nebude vztahovat k tomuto konkr\u00e9tn\u00edmu provozu, za\u010dne pou\u017e\u00edvat s\u00ed\u0165ovou trasu Network route. <\/p>\n

\"Tr\u00e9nink
\n
\nToto je to, co p\u0159edstavuje sumarizovan\u00e1 trasa \u2013 sumarizujete n\u011bkolik konkr\u00e9tn\u00edch IP adres a vytv\u00e1\u0159\u00edte pro n\u011b samostatnou trasu. <\/p>\n

Ve skupin\u011b statick\u00fdch tras existuje tak\u00e9 tzv. \"plovouc\u00ed trasa\" nebo Floating Route. Je to z\u00e1lo\u017en\u00ed trasa. Pou\u017e\u00edv\u00e1 se v p\u0159\u00edpad\u011b probl\u00e9m\u016f s fyzick\u00fdm spojen\u00edm podle statick\u00e9 trasy, kter\u00e1 m\u00e1 administrativn\u00ed vzd\u00e1lenost rovnou 1. V na\u0161em p\u0159\u00edkladu je to trasa p\u0159es IP adresu 192.168.10.1 v posledn\u00edm \u0159\u00e1dku tabulky sm\u011brov\u00e1n\u00ed, a pokud dojde k jej\u00edmu p\u0159eru\u0161en\u00ed na fyzick\u00e9 \u00farovni, pou\u017eije se z\u00e1lo\u017en\u00ed plovouc\u00ed trasa. <\/p>\n

Aby se aktivovala z\u00e1lo\u017en\u00ed trasa, na konci p\u0159\u00edkazu nam\u00edsto IP adresy n\u00e1sleduj\u00edc\u00edho skoku, kter\u00e1 m\u00e1 obvykle hodnotu 1, uvedete jinou hodnotu skok\u016f, nap\u0159\u00edklad 5. Plovouc\u00ed trasa nen\u00ed uvedena v tabulce sm\u011brov\u00e1n\u00ed, proto\u017ee se pou\u017e\u00edv\u00e1 pouze v p\u0159\u00edpad\u011b, kdy je statick\u00e1 trasa nedostupn\u00e1 kv\u016fli poru\u0161e. <\/p>\n

Pokud jste z toho, co jsem pr\u00e1v\u011b \u0159ekl, n\u011bco nepochopili, p\u0159ehrajte si toto video znovu. Pokud st\u00e1le budete m\u00edt ot\u00e1zky, m\u016f\u017eete mi poslat e-mail a j\u00e1 v\u00e1m v\u0161e vysv\u011btl\u00edm. <\/p>\n

A nyn\u00ed se poj\u010fme pod\u00edvat na sm\u011brov\u00e1n\u00ed Inter-Switch. Na sch\u00e9matu se vlevo nach\u00e1z\u00ed switch, kter\u00fd obsluhuje modrou s\u00ed\u0165 odd\u011blen\u00ed prodeje. Vpravo je jin\u00fd switch, kter\u00fd pracuje pouze se zelenou s\u00edt\u00ed odd\u011blen\u00ed marketingu. V tomto p\u0159\u00edpad\u011b se pou\u017e\u00edvaj\u00ed dva nez\u00e1visl\u00e9 switche, kter\u00e9 obsluhuj\u00ed r\u016fzn\u00e9 odd\u011blen\u00ed, proto\u017ee v t\u00e9to topologii nen\u00ed pou\u017eita spole\u010dn\u00e1 s\u00ed\u0165 VLAN. <\/p>\n

\"Tr\u00e9nink
\n
\nPokud pot\u0159ebujete nav\u00e1zat spojen\u00ed mezi t\u011bmito dv\u011bma switche, tedy mezi dv\u011bma r\u016fzn\u00fdmi s\u00edt\u011bmi 192.168.1.0\/24 a 192.168.2.0\/24, je nutn\u00e9 pou\u017e\u00edt router. Pak si tyto s\u00edt\u011b budou moci vym\u011b\u0148ovat pakety a p\u0159ipojit se k internetu prost\u0159ednictv\u00edm routeru R1. Kdybychom pou\u017eili VLAN1 jako v\u00fdchoz\u00ed pro oba switche a propojili je fyzick\u00fdmi kabely, mohly by si navz\u00e1jem komunikovat. Av\u0161ak vzhledem k odd\u011blen\u00ed s\u00edt\u00ed pat\u0159\u00edc\u00edch r\u016fzn\u00fdm vys\u00edlac\u00edm dom\u00e9n\u00e1m je pro jejich komunikaci nezbytn\u00fd router.<\/p>\n

P\u0159edpokl\u00e1dejme, \u017ee ka\u017ed\u00fd switch m\u00e1 16 port\u016f. V na\u0161em p\u0159\u00edpad\u011b nepou\u017e\u00edv\u00e1me 14 port\u016f, proto\u017ee v ka\u017ed\u00e9m odd\u011blen\u00ed jsou pouze 2 po\u010d\u00edta\u010de. Proto je v tomto p\u0159\u00edpad\u011b optim\u00e1ln\u00ed pou\u017e\u00edt VLAN, jak je zn\u00e1zorn\u011bno na n\u00e1sleduj\u00edc\u00edm sch\u00e9matu. <\/p>\n

\"Tr\u00e9nink
\n
\nV tomto p\u0159\u00edpad\u011b m\u00e1 modr\u00e1 s\u00ed\u0165 VLAN10 a zelen\u00e1 s\u00ed\u0165 VLAN20 vlastn\u00ed vys\u00edlac\u00ed dom\u00e9nu. S\u00ed\u0165 VLAN10 je spojena kabelem s jedn\u00edm portem routeru a s\u00ed\u0165 VLAN20 s jin\u00fdm portem, p\u0159i\u010dem\u017e oba kabely vych\u00e1zej\u00ed z r\u016fzn\u00fdch port\u016f switche. Zd\u00e1 se, \u017ee d\u00edky tomuto skv\u011bl\u00e9mu \u0159e\u0161en\u00ed jsme nav\u00e1zali spojen\u00ed mezi s\u00edt\u011bmi. Av\u0161ak vzhledem k tomu, \u017ee router m\u00e1 omezen\u00fd po\u010det port\u016f, velmi neefektivn\u011b vyu\u017e\u00edv\u00e1me mo\u017enosti tohoto za\u0159\u00edzen\u00ed, kdy\u017e je takto obsazujeme. <\/p>\n

Existuje efektivn\u011bj\u0161\u00ed \u0159e\u0161en\u00ed \u2013 \"router na ty\u010di\". P\u0159i tomto \u0159e\u0161en\u00ed spojujeme port switche trunkem s jedn\u00edm z port\u016f routeru. Ji\u017e jsme zm\u00ednili, \u017ee v\u00fdchoz\u00ed router nerozum\u00ed enkapsulaci podle standardu .1Q, tak\u017ee pro nav\u00e1z\u00e1n\u00ed spojen\u00ed s n\u00edm je nutn\u00e9 pou\u017e\u00edt trunk. P\u0159i tom doch\u00e1z\u00ed k n\u00e1sleduj\u00edc\u00edmu.<\/p>\n

Modr\u00e1 s\u00ed\u0165 VLAN10 pos\u00edl\u00e1 provoz p\u0159es switch k rozhran\u00ed F0\/0 routeru. Tento port je rozd\u011blen na subinterfacy, p\u0159i\u010dem\u017e ka\u017ed\u00fd z nich m\u00e1 jednu IP adresu nach\u00e1zej\u00edc\u00ed se bu\u010f v rozsahu adres s\u00edt\u011b 192.168.1.0\/24, nebo s\u00edt\u011b 192.168.2.0\/24. Zde vznik\u00e1 ur\u010dit\u00e1 nejistota \u2013 pro dv\u011b r\u016fzn\u00e9 s\u00edt\u011b pot\u0159ebujeme m\u00edt dv\u011b r\u016fzn\u00e9 IP adresy. Proto, i kdy\u017e trunk mezi switchem a routerem je vytvo\u0159en na jednom fyzick\u00e9m rozhran\u00ed, mus\u00edme vytvo\u0159it dva subinterfacy pro ka\u017edou VLAN. T\u00edmto zp\u016fsobem bude jeden subinterface obsluhovat s\u00ed\u0165 VLAN10 a druh\u00fd VLAN20. Pro prvn\u00ed subinterface mus\u00edme vybrat IP adresu z rozsahu adres 192.168.1.0\/24, a pro druh\u00fd z rozsahu 192.168.2.0\/24. Kdy\u017e VLAN10 po\u0161le paket, br\u00e1nou bude jedna IP adresa, a kdy\u017e paket po\u0161le VLAN20, jako br\u00e1na bude pou\u017eita druh\u00e1 IP adresa. Router \u201ena ty\u010dce\u201c p\u0159itom rozhodne o propou\u0161t\u011bn\u00ed provozu od ka\u017ed\u00e9ho ze dvou po\u010d\u00edta\u010d\u016f, kter\u00e9 pat\u0159\u00ed do r\u016fzn\u00fdch VLAN. Jednodu\u0161e \u0159e\u010deno, rozd\u011blujeme jedno fyzick\u00e9 rozhran\u00ed routeru na dva nebo v\u00edce logick\u00fdch rozhran\u00ed. <\/p>\n

\"Tr\u00e9nink
\n
\nPod\u00edvejme se, jak to vypad\u00e1 v programu Packet Tracer. <\/p>\n

\"Tr\u00e9nink
\n
\nTrochu jsem zjednodu\u0161il sch\u00e9ma, tak\u017ee m\u00e1me jeden po\u010d\u00edta\u010d PC0 s IP adresou 192.168.1.10 a druh\u00fd po\u010d\u00edta\u010d PC1 s adresou 192.168.2.10. P\u0159i nastavov\u00e1n\u00ed switche vyhrazuji jedno rozhran\u00ed pro VLAN10, druh\u00e9 pro VLAN20. Vstupuji do konzole CLI a zad\u00e1v\u00e1m p\u0159\u00edkaz show ip interface brief, abych se ujistil, \u017ee rozhran\u00ed FastEthernet0\/2 a 0\/3 jsou aktivn\u00ed. Pot\u00e9 si prohl\u00ed\u017e\u00edm datab\u00e1zi VLAN a vid\u00edm, \u017ee v sou\u010dasnosti v\u0161echna rozhran\u00ed switche jsou sou\u010d\u00e1st\u00ed v\u00fdchoz\u00ed VLAN. Pot\u00e9 postupn\u011b zad\u00e1v\u00e1m p\u0159\u00edkazy config t a int f0\/2, abych vyvolal port, ke kter\u00e9mu je p\u0159ipojena VLAN odd\u011blen\u00ed prodeje. <\/p>\n

Nyn\u00ed pou\u017eiji p\u0159\u00edkaz switchport mode access. Re\u017eim access je v\u00fdchoz\u00ed, tak\u017ee tento p\u0159\u00edkaz prost\u011b zad\u00e1m. Pot\u00e9 zad\u00e1m switchport access VLAN10 a syst\u00e9m odpov\u00ed, \u017ee proto\u017ee takov\u00e1 s\u00ed\u0165 neexistuje, automaticky vytvo\u0159\u00ed VLAN10. Pokud chcete vytvo\u0159it s\u00ed\u0165 VLAN ru\u010dn\u011b, nap\u0159\u00edklad VLAN20, mus\u00edte zadat p\u0159\u00edkaz vlan 20, \u010d\u00edm\u017e se p\u0159\u00edkazov\u00fd \u0159\u00e1dek p\u0159epne na nastaven\u00ed virtu\u00e1ln\u00ed s\u00edt\u011b a zm\u011bn\u00ed sv\u016fj z\u00e1hlav\u00ed z Switch(config) # na Switch(config-vlan) #. D\u00e1le mus\u00edte vytvo\u0159en\u00e9 s\u00edti p\u0159i\u0159adit n\u00e1zev MARKETING pomoc\u00ed p\u0159\u00edkazu name . Pot\u00e9 nastav\u00edme rozhran\u00ed f0\/3. Postupn\u011b zad\u00e1m p\u0159\u00edkazy switchport mode access a switchport access vlan 20, po \u010dem\u017e bude s\u00ed\u0165 p\u0159ipojena k tomuto portu. <\/p>\n

Tak\u017ee m\u016f\u017eete nakonfigurovat switch dv\u011bma zp\u016fsoby: prvn\u00ed \u2013 pomoc\u00ed p\u0159\u00edkazu switchport access vlan 10, po \u010dem\u017e se s\u00ed\u0165 automaticky vytvo\u0159\u00ed na tomto portu, druh\u00fd \u2013 kdy\u017e nejprve vytvo\u0159\u00edte s\u00ed\u0165 a pot\u00e9 ji p\u0159ipoj\u00edte k jednotliv\u00e9mu portu.
\nStejn\u00fdm zp\u016fsobem m\u016f\u017eete postupovat u VLAN10. Vr\u00e1t\u00edm se zp\u011bt a zopakuji proces ru\u010dn\u00edho nastaven\u00ed pro tuto s\u00ed\u0165: p\u0159ejdu do re\u017eimu glob\u00e1ln\u00ed konfigurace, zad\u00e1m p\u0159\u00edkaz vlan 10, pot\u00e9 j\u00ed p\u0159i\u0159ad\u00edm n\u00e1zev name SALES a tak d\u00e1le. Nyn\u00ed v\u00e1m uk\u00e1\u017eu, co se stane, pokud to neud\u011bl\u00e1te, tedy pokud nech\u00e1te syst\u00e9m automaticky vytvo\u0159it s\u00ed\u0165 VLAN. <\/p>\n

\"Tr\u00e9nink
\n
\nVid\u00edte, \u017ee m\u00e1me ob\u011b s\u00edt\u011b, ale druh\u00e1, kterou jsme vytvo\u0159ili ru\u010dn\u011b, m\u00e1 vlastn\u00ed n\u00e1zev MARKETING, zat\u00edmco prvn\u00ed s\u00ed\u0165 VLAN10 dostala v\u00fdchoz\u00ed n\u00e1zev VLAN0010. Mohu to opravit, pokud nyn\u00ed v re\u017eimu glob\u00e1ln\u00ed konfigurace zad\u00e1m p\u0159\u00edkaz name SALES. Nyn\u00ed vid\u00edte, \u017ee po tomto krok se prvn\u00ed s\u00ed\u0165 zm\u011bnila na SALES. <\/p>\n

Nyn\u00ed se vra\u0165me do Packet Tracer a zkontrolujme, zda se po\u010d\u00edta\u010d PC0 m\u016f\u017ee spojit s po\u010d\u00edta\u010dem PC1. Za t\u00edmto \u00fa\u010delem otev\u0159u termin\u00e1l p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku prvn\u00edho po\u010d\u00edta\u010de a po\u0161lu ping na adresu druh\u00e9ho po\u010d\u00edta\u010de. <\/p>\n

Vid\u00edme, \u017ee pingov\u00e1n\u00ed skon\u010dilo ne\u00fasp\u011b\u0161n\u011b. D\u016fvodem je, \u017ee PC0 odeslal ARP po\u017eadavek na adresu 192.168.2.10 p\u0159es br\u00e1nu 192.168.1.1. P\u0159i tom se po\u010d\u00edta\u010d vlastn\u011b ptal switche, kdo je tento 192.168.1.1. Nicm\u00e9n\u011b switch m\u00e1 pouze jedno rozhran\u00ed pro s\u00ed\u0165 VLAN10 a p\u0159ijat\u00fd po\u017eadavek nem\u016f\u017ee nikam odej\u00edt \u2013 p\u0159ijde na tento port a tam zahyne. Po\u010d\u00edta\u010d nedostane odpov\u011b\u010f, a proto je jako d\u016fvod ne\u00fasp\u011bchu pingu uv\u00e1d\u011bno vypr\u0161en\u00ed \u010dasov\u00e9ho limitu. Odpov\u011b\u010f nebyla p\u0159ijata, proto\u017ee v s\u00edti VLAN10 nen\u00ed \u017e\u00e1dn\u00e9 dal\u0161\u00ed za\u0159\u00edzen\u00ed krom\u011b PC0. Nav\u00edc, i kdy\u017e by oba po\u010d\u00edta\u010de byly sou\u010d\u00e1st\u00ed t\u00e9 sam\u00e9 s\u00edt\u011b, stejn\u011b by se nemohly spojit, proto\u017ee maj\u00ed r\u016fzn\u00e9 rozsahy IP adres. Abychom tuto sch\u00e9matu uvedli do chodu, je pot\u0159eba pou\u017e\u00edt router. <\/p>\n

Ne\u017e v\u0161ak uk\u00e1\u017eu, jak aktivovat router, ud\u011bl\u00e1m malou odbo\u010dku. P\u0159ipoj\u00edm port Fa0\/1 switche a port routeru Gig0\/0 jedn\u00edm kabelem, a pot\u00e9 p\u0159id\u00e1m dal\u0161\u00ed kabel, kter\u00fd bude p\u0159ipojen k portu Fa0\/4 switche a portu Gif0\/1 routeru. <\/p>\n

\"Tr\u00e9nink
\n
\nP\u0159ipoj\u00edm s\u00ed\u0165 VLAN10 k portu f0\/1 switche, k \u010demu\u017e zad\u00e1m p\u0159\u00edkazy int f0\/1 a switchport access vlan10, a s\u00ed\u0165 VLAN20 k portu f0\/4, pou\u017e\u00edvaj\u00edc\u00ed p\u0159\u00edkazy int f0\/4 a switchport access vlan 20. Pokud se nyn\u00ed pod\u00edv\u00e1me na datab\u00e1zi VLAN, vid\u00edme, \u017ee s\u00ed\u0165 SALES je p\u0159ipojena k rozhran\u00edm Fa0\/1, Fa0\/2, zat\u00edmco s\u00ed\u0165 MARKETING je p\u0159ipojena k port\u016fm Fa0\/3, Fa0\/4. <\/p>\n

Vra\u0165me se zp\u011bt k routeru a vstoup\u00edme do nastaven\u00ed rozhran\u00ed g0\/0, zad\u00e1me p\u0159\u00edkaz no shutdown a p\u0159i\u0159ad\u00edme mu IP adresu: ip add 192.168.1.1 255.255.255.0.<\/p>\n

Podobn\u011b nastav\u00edme rozhran\u00ed g0\/1, p\u0159i\u0159ad\u00edme mu adresu ip add 192.168.2.1 255.255.255.0. Pot\u00e9 po\u017e\u00e1d\u00e1me o zobrazen\u00ed tabulky sm\u011brov\u00e1n\u00ed, ve kter\u00e9 nyn\u00ed jsou z\u00e1znamy o s\u00edt\u00edch 1.0 a 2.0. <\/p>\n

\"Tr\u00e9nink
\n
\nPod\u00edvejme se, jestli tato sch\u00e9ma funguje. Po\u010dk\u00e1me, a\u017e oba porty switche a routeru budou zelen\u00e9, a zopakujeme pingov\u00e1n\u00ed IP adresy 192.168.2.10. Jak vid\u00edte, v\u0161echno funguje!<\/p>\n

\"Tr\u00e9nink
\n
\nPo\u010d\u00edta\u010d PC0 odes\u00edl\u00e1 po\u017eadavek pomoc\u00ed protokolu ARP switchi, switch jej adresuje routeru, a ten pos\u00edl\u00e1 zp\u011bt po\u010d\u00edta\u010di svou MAC adresu. Pot\u00e9 po\u010d\u00edta\u010d odes\u00edl\u00e1 pingov\u00fd paket stejnou cestou. Router v\u00ed, \u017ee s\u00ed\u0165 VLAN20 je p\u0159ipojena k jeho portu g0\/1, a proto jej pos\u00edl\u00e1 switchi, kter\u00fd paket p\u0159epos\u00edl\u00e1 p\u0159\u00edjemci \u2013 PC1. <\/p>\n

Tato sch\u00e9ma funguje, ale nen\u00ed efektivn\u00ed, proto\u017ee zab\u00edr\u00e1 2 rozhran\u00ed routeru, co\u017e znamen\u00e1, \u017ee nevyu\u017e\u00edv\u00e1me technick\u00e9 mo\u017enosti routeru efektivn\u011b. Proto uk\u00e1\u017eu, jak to stejn\u00e9 lze ud\u011blat pomoc\u00ed jednoho rozhran\u00ed. <\/p>\n

Odstran\u00edm sch\u00e9ma se dv\u011bma kabely a obnov\u00edm p\u0159edchoz\u00ed spojen\u00ed mezi switchem a routerem pomoc\u00ed jednoho kabelu. Rozhran\u00ed f0\/1 switche by se m\u011blo st\u00e1t trunk portem, tak\u017ee se vrac\u00edm do nastaven\u00ed switche a pro toto port pou\u017e\u00edv\u00e1m p\u0159\u00edkaz switchport mode trunk. Port f0\/4 ji\u017e nepou\u017e\u00edv\u00e1me. D\u00e1le pou\u017eijeme p\u0159\u00edkaz show int trunk, abychom zjistili, zda je port spr\u00e1vn\u011b nakonfigurov\u00e1n. <\/p>\n

\"Tr\u00e9nink
\n
\nVid\u00edme, \u017ee port Fa0\/1 pracuje v re\u017eimu trunk podle protokolu zapouzd\u0159en\u00ed 802.1q. Pod\u00edv\u00e1me se na tabulku VLAN \u2013 vid\u00edme, \u017ee rozhran\u00ed F0\/2 je obsazeno s\u00edt\u00ed prodeje VLAN10, a rozhran\u00ed f0\/3 je pod s\u00edt\u00ed marketingu VLAN20. <\/p>\n

\"Tr\u00e9nink
\n
\nP\u0159itom je switch p\u0159ipojen k portu g0\/0 routeru. V nastaven\u00ed routeru pou\u017e\u00edv\u00e1m p\u0159\u00edkazy int g0\/0 a no ip address, abych odstranil IP adresu tohoto rozhran\u00ed. Ale toto rozhran\u00ed st\u00e1le funguje, nen\u00ed v stavu shutdown. Pokud si vzpomenete, router mus\u00ed p\u0159ij\u00edmat provoz ze dvou s\u00edt\u00ed \u2013 1.0 a 2.0. Proto\u017ee je switch p\u0159ipojen k routeru trunkem, pro router bude p\u0159ich\u00e1zet provoz jak z prvn\u00ed, tak z druh\u00e9 s\u00edt\u011b. Jakou IP adresu by v\u0161ak m\u011blo m\u00edt rozhran\u00ed routeru v tomto p\u0159\u00edpad\u011b? <\/p>\n

G0\/0 p\u0159edstavuje fyzick\u00e9 rozhran\u00ed, kter\u00e9 ve v\u00fdchoz\u00edm nastaven\u00ed nem\u00e1 \u017e\u00e1dnou IP adresu. Proto pou\u017e\u00edv\u00e1me koncept logick\u00e9ho podrozhran\u00ed. Pokud zad\u00e1m p\u0159\u00edkaz int g0\/0, syst\u00e9m mi nab\u00eddne dv\u011b mo\u017en\u00e9 varianty p\u0159\u00edkazu: lom\u00edtko \/ nebo te\u010dku. Lom\u00edtko se pou\u017e\u00edv\u00e1 p\u0159i modul\u00e1rn\u00edm nastaven\u00ed rozhran\u00ed typu 0\/0\/0, zat\u00edmco te\u010dka se pou\u017e\u00edv\u00e1, pokud m\u00e1te podrozhran\u00ed.<\/p>\n

Pokud v \u0159\u00e1dku int g0\/0. ?, syst\u00e9m mi nab\u00eddne rozsah mo\u017en\u00fdch \u010d\u00edsel logick\u00e9ho podrozhran\u00ed GigabitEthernet, kter\u00e1 jsou uvedena za te\u010dkou: . Tento rozsah obsahuje v\u00edce ne\u017e 4 miliardy \u010d\u00edsel, co\u017e znamen\u00e1, \u017ee lze vytvo\u0159it takov\u00e9 mno\u017estv\u00ed logick\u00fdch podrozhran\u00ed. <\/p>\n

\"Tr\u00e9nink
\n
\nPo te\u010dce uvedu \u010d\u00edslo 10, kter\u00e9 bude p\u0159edstavovat VLAN10. Nyn\u00ed jsme p\u0159e\u0161li do nastaven\u00ed podrozhran\u00ed, co\u017e dokl\u00e1d\u00e1 zm\u011bna hlavi\u010dky \u0159\u00e1dku p\u0159\u00edkazov\u00e9ho rozhran\u00ed na Router (config-subif) #, v tomto p\u0159\u00edpad\u011b se to t\u00fdk\u00e1 podrozhran\u00ed g0\/0.10. Nyn\u00ed mus\u00edm p\u0159i\u0159adit IP adresu, k \u010demu\u017e pou\u017eiji p\u0159\u00edkaz ip add 192.168.1.1 255.255.255.0. P\u0159ed t\u00edm, ne\u017e nastav\u00edm tuto adresu, je t\u0159eba prov\u00e9st inkapsulaci, aby na\u0161e vytvo\u0159en\u00e9 podrozhran\u00ed v\u011bd\u011blo, jak\u00fd inkapsula\u010dn\u00ed protokol pou\u017e\u00edt \u2014 802.1q nebo ISL. V \u0159\u00e1dku p\u0159\u00edkaz\u016f zad\u00e1v\u00e1m slovo encapsulation a syst\u00e9m zobrazuje mo\u017en\u00e9 varianty parametr\u016f pro tento p\u0159\u00edkaz. <\/p>\n

\"Tr\u00e9nink
\n
\nPou\u017e\u00edv\u00e1m p\u0159\u00edkaz encapsulation dot1Q. Technicky nen\u00ed nutn\u00e9 tento p\u0159\u00edkaz zad\u00e1vat, ale zad\u00e1v\u00e1m ho, abych routeru uk\u00e1zal, jak\u00fd protokol m\u00e1 aplikovat pro pr\u00e1ci s VLAN, proto\u017ee v sou\u010dasnosti funguje jako switch, obsluhuj\u00edc\u00ed trunking VLAN. T\u00edmto p\u0159\u00edkazem ur\u010dujeme routeru, \u017ee ve\u0161ker\u00fd provoz mus\u00ed b\u00fdt inkapsulov\u00e1n v protokolu dot1Q. D\u00e1le v \u0159\u00e1dku p\u0159\u00edkaz\u016f mus\u00edm uv\u00e9st, \u017ee tato inkapsulace se t\u00fdk\u00e1 s\u00edt\u011b VLAN10. Syst\u00e9m n\u00e1m zobrazuje pou\u017e\u00edvanou IP adresu a rozhran\u00ed pro s\u00ed\u0165 VLAN10 za\u010d\u00edn\u00e1 fungovat. <\/p>\n

\"Tr\u00e9nink
\n
\nPodobn\u00fdm zp\u016fsobem konfiguruji rozhran\u00ed g0\/0.20. Vytv\u00e1\u0159\u00edm nov\u00e9 podrozhran\u00ed, nastav\u00edm inkapsula\u010dn\u00ed protokol a nastav\u00edm IP adresu p\u0159\u00edkazem ip add 192.168.2.1 255.255.255.0.<\/p>\n

\"Tr\u00e9nink
\n
\nP\u0159itom je nezbytn\u00e9 odstranit IP adresu fyzick\u00e9ho rozhran\u00ed, proto\u017ee te\u010f m\u00e1 fyzick\u00e9 rozhran\u00ed a logick\u00e9 podrozhran\u00ed stejnou adresu pro s\u00ed\u0165 VLAN20. K tomu postupn\u011b zad\u00e1v\u00e1m p\u0159\u00edkazy int g0\/1 a no ip address. Pot\u00e9 toto rozhran\u00ed deaktivuji, proto\u017ee ho u\u017e nepot\u0159ebujeme. <\/p>\n

\"Tr\u00e9nink
\n
\nNyn\u00ed se znovu vrac\u00edm k rozhran\u00ed g0\/0.20 a p\u0159i\u0159azuji mu IP adresu p\u0159\u00edkazem ip add 192.168.2.1 255.255.255.0. Te\u010f u\u017e to bude fungovat spr\u00e1vn\u011b. <\/p>\n

Nyn\u00ed pou\u017e\u00edv\u00e1m p\u0159\u00edkaz show ip route, abych se pod\u00edval na tabulku sm\u011brov\u00e1n\u00ed. <\/p>\n

\"Tr\u00e9nink
\n
\nVid\u00edme, \u017ee s\u00ed\u0165 192.168.1.0\/24 je p\u0159\u00edmo p\u0159ipojena k podinterfaci GigabitEthernet0\/0.10 a s\u00ed\u0165 192.168.2.0\/24 je p\u0159\u00edmo p\u0159ipojena k podinterfaci GigabitEthernet0\/0.20. Te\u010f se vr\u00e1t\u00edm do termin\u00e1lu p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku PC0 a provedu ping na PC1. P\u0159itom proud\u00ed data na port routeru, ten je p\u0159epos\u00edl\u00e1 na p\u0159\u00edslu\u0161nou podinterfaci a vrac\u00ed je p\u0159es switch po\u010d\u00edta\u010di PC1. Jak vid\u00edte, ping byl \u00fasp\u011b\u0161n\u00fd. Dva prvn\u00ed pakety byly zahozeny, proto\u017ee p\u0159ep\u00edn\u00e1n\u00ed mezi rozhran\u00edmi routeru trv\u00e1 n\u011bjakou dobu, nav\u00edc za\u0159\u00edzen\u00ed mus\u00ed zjistit MAC adresy, ale dva dal\u0161\u00ed pakety \u00fasp\u011b\u0161n\u011b dorazily k c\u00edli. Takto funguje koncept \u201erouteru na ty\u010di\u201c.<\/p>\n

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

Dell R730xd za polovinu ceny?<\/b> Jen u n\u00e1s 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB od 199 $<\/a><\/noindex> v Nizozemsku! Dell R420 \u2014 2x E5-2430 2.2GHz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 $!<\/b><\/b> \u010ct\u011bte o tom Jak postavit infrastrukturu podnikov\u00e9 t\u0159\u00eddy s pou\u017eit\u00edm server\u016f Dell R730xd E5-2650 v4 v hodnot\u011b 9000 eur za pakatel?<\/a><\/noindex>
\n
Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0431\u043e\u043b\u0435\u0435 \u043e\u0441\u043d\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0430\u0441\u043f\u0435\u043a\u0442\u044b \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438. \u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043d\u0430\u0447\u0430\u0442\u044c, \u044f \u0445\u043e\u0447\u0443 \u043e\u0442\u0432\u0435\u0442\u0438\u0442\u044c \u043d\u0430 \u0432\u043e\u043f\u0440\u043e\u0441 \u0441\u0442\u0443\u0434\u0435\u043d\u0442\u043e\u0432 \u043e \u043c\u043e\u0438\u0445 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0430\u0445 \u0432 \u0441\u043e\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0445 \u0441\u0435\u0442\u044f\u0445. \u0421\u043b\u0435\u0432\u0430 \u044f \u043f\u043e\u043c\u0435\u0441\u0442\u0438\u043b \u0441\u0441\u044b\u043b\u043a\u0438 \u043d\u0430 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0438 \u043d\u0430\u0448\u0435\u0439 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u0430 \u0441\u043f\u0440\u0430\u0432\u0430 \u2013 \u043d\u0430 \u043c\u043e\u0438 \u043f\u0435\u0440\u0441\u043e\u043d\u0430\u043b\u044c\u043d\u044b\u0435 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0438. \u0417\u0430\u043c\u0435\u0447\u0443, \u0447\u0442\u043e \u044f \u043d\u0435 \u0434\u043e\u0431\u0430\u0432\u043b\u044f\u044e \u0447\u0435\u043b\u043e\u0432\u0435\u043a\u0430 \u0432 \u0441\u0432\u043e\u0438 \u0434\u0440\u0443\u0437\u044c\u044f \u043d\u0430 Facebook, \u0435\u0441\u043b\u0438 \u043d\u0435 \u0437\u043d\u0430\u044e \u0435\u0433\u043e \u043b\u0438\u0447\u043d\u043e, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28149,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37511","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\udd47\u0160kolen\u00ed Cisco 200-125 CCNA v3.0. Den 23. Pokro\u010dil\u00e9 technologie routingu | ProHoster","description":"Dnes se pod\u00edv\u00e1me hloub\u011bji na n\u011bkter\u00e9 aspekty routingu. Ne\u017e za\u010dneme, chci odpov\u011bd\u011bt na dotaz student\u016f o m\u00fdch str\u00e1nk\u00e1ch na soci\u00e1ln\u00edch s\u00edt\u00edch.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-marshrutizatsii","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 23. \u041f\u0435\u0440\u0435\u0434\u043e\u0432\u044b\u0435 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0438 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0431\u043e\u043b\u0435\u0435 \u043e\u0441\u043d\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0430\u0441\u043f\u0435\u043a\u0442\u044b \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438. \u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043d\u0430\u0447\u0430\u0442\u044c, \u044f \u0445\u043e\u0447\u0443 \u043e\u0442\u0432\u0435\u0442\u0438\u0442\u044c \u043d\u0430 \u0432\u043e\u043f\u0440\u043e\u0441 \u0441\u0442\u0443\u0434\u0435\u043d\u0442\u043e\u0432 \u043e \u043c\u043e\u0438\u0445 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0430\u0445 \u0432 \u0441\u043e\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0445 \u0441\u0435\u0442\u044f\u0445.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-23-peredovye-tehnologii-marshrutizatsii","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:18:02+00:00","article:modified_time":"2019-10-31T19:18:02+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37511","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 18:09:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:25:27","updated":"2026-01-23 18:09:20","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\/37511","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=37511"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/37511\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/28149"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=37511"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=37511"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=37511"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}