{"id":31067,"date":"2019-10-31T21:39:16","date_gmt":"2019-10-31T18:39:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie\/"},"modified":"2019-10-31T21:39:16","modified_gmt":"2019-10-31T18:39:16","slug":"kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie","title":{"rendered":"Ako ma\u0165 sie\u0165ov\u00fa infra\u0161trukt\u00faru pod kontrolou. Hlava druh\u00e1. \u00dadr\u017eba a dokument\u00e1cia","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i>Tento \u010dl\u00e1nok je druh\u00fd v cykle \u010dl\u00e1nkov \u201eAko si z\u00edska\u0165 kontrolu nad sie\u0165ovou infra\u0161trukt\u00farou\u201c. Obsah v\u0161etk\u00fdch \u010dl\u00e1nkov cyklu a odkazy n\u00e1jdete <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/447008\/\">tu<\/a><\/noindex><\/i>.<\/p>\n<p><img decoding=\"async\" alt=\"Ako ma\u0165 sie\u0165ov\u00fa infra\u0161trukt\u00faru pod kontrolou. Hlava druh\u00e1. \u00dadr\u017eba a dokument\u00e1cia\" src=\"\/wp-content\/uploads\/2019\/04\/7b8e020272ed52ef0a119714b0a5d58b.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNa\u0161im cie\u013eom v tomto kroku je usporiada\u0165 dokument\u00e1ciu a konfigur\u00e1ciu. <br \/>\nNa konci tohto procesu by ste mali ma\u0165 potrebn\u00fa dokument\u00e1ciu a sie\u0165 nakonfigurovan\u00fa pod\u013ea nej.<\/p>\n<p>Teraz nebudeme hovori\u0165 o audite zabezpe\u010denia \u2013 tomu sa bude venova\u0165 tretia \u010das\u0165. <\/p>\n<p>N\u00e1ro\u010dnos\u0165 \u00falohy stanoven\u00e9 v tejto f\u00e1ze sa samozrejme ve\u013emi l\u00ed\u0161i od firmy k firme.<\/p>\n<p>Ide\u00e1lna situ\u00e1cia je, ke\u010f<\/p>\n<ul>\n<li>va\u0161a sie\u0165 bola vytvoren\u00e1 pod\u013ea pl\u00e1nu a m\u00e1te \u00fapln\u00fd s\u00fabor dokument\u00e1cie<\/li>\n<li>vo va\u0161ej spolo\u010dnosti bol zaveden\u00fd <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/433614\/\">proces kontroly a riadenia zmien<\/a><\/noindex> pre sie\u0165<\/li>\n<li>pod\u013ea tohto procesu m\u00e1te k dispoz\u00edcii dokumenty (vr\u00e1tane v\u0161etk\u00fdch potrebn\u00fdch sch\u00e9m), ktor\u00e9 poskytuj\u00fa \u00fapln\u00e9 inform\u00e1cie o aktu\u00e1lnom stave vec\u00ed<\/li>\n<\/ul>\n<p>\nV takom pr\u00edpade je va\u0161a \u00faloha celkom jednoduch\u00e1. Mus\u00edte si pre\u0161tudova\u0165 dokumenty a skontrolova\u0165 v\u0161etky zmeny, ktor\u00e9 boli vykonan\u00e9. <\/p>\n<p>V najhor\u0161om pr\u00edpade budete ma\u0165<\/p>\n<ul>\n<li>sie\u0165 vytvoren\u00fa bez pl\u00e1nu, bez projektu, bez ods\u00fahlasenia, in\u017einiermi, ktor\u00ed nemaj\u00fa dostato\u010dn\u00fa kvalifik\u00e1ciu,<\/li>\n<li>s chaotick\u00fdmi, nedokumentovan\u00fdmi zmenami, s mno\u017estvom \u201eodpadu\u201c a suboptim\u00e1lnych rie\u0161en\u00ed<\/li>\n<\/ul>\n<p>\nJe jasn\u00e9, \u017ee va\u0161a situ\u00e1cia bude niekde medzi t\u00fdmito dvoma extr\u00e9mami, ale bohu\u017eia\u013e, na tejto \u0161k\u00e1le je s ve\u013ekou pravdepodobnos\u0165ou lep\u0161\u00ed koniec, ste bli\u017e\u0161ie k hor\u0161iemu.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>V takom pr\u00edpade budete musie\u0165 tie\u017e ovl\u00e1da\u0165 \u010d\u00edtanie medzi riadkami, preto\u017ee sa budete musie\u0165 nau\u010di\u0165 ch\u00e1pa\u0165, \u010do chceli urobi\u0165 \u201edizajn\u00e9ri\u201c, obnovi\u0165 ich logiku, dokon\u010di\u0165 to, \u010do zostalo nedokon\u010den\u00e9 a odstr\u00e1ni\u0165 \u201eodpad\u201c. <br \/>\nA samozrejme, budete musie\u0165 skorigova\u0165 ich chyby, zmeni\u0165 (v tejto f\u00e1ze \u010do najmenej) dizajn a upravi\u0165 alebo znovu vytvori\u0165 sch\u00e9my. <\/p>\n<p>Tento \u010dl\u00e1nok si rozhodne neuzurpuje \u00faplnos\u0165. Tu op\u00ed\u0161em len v\u0161eobecn\u00e9 princ\u00edpy a zameriam sa na niektor\u00e9 be\u017en\u00e9 probl\u00e9my, ktor\u00e9 je potrebn\u00e9 rie\u0161i\u0165.<\/p>\n<h2>S\u00fabor dokumentov<\/h2>\n<p><\/p>\n<blockquote><p>Za\u010dnime pr\u00edkladom.<\/p>\n<p>Ni\u017e\u0161ie s\u00fa uveden\u00e9 niektor\u00e9 dokumenty, ktor\u00e9 sa zvykn\u00fa vytv\u00e1ra\u0165 v spolo\u010dnosti Cisco Systems pri projektovan\u00ed.<\/p>\n<p><b>CR<\/b> \u2013 Po\u017eiadavky z\u00e1kazn\u00edka (technick\u00e1 \u0161pecifik\u00e1cia).<br \/>\nVytv\u00e1ra sa spolo\u010dne so z\u00e1kazn\u00edkom a ur\u010duje po\u017eiadavky na sie\u0165.<\/p>\n<p><b>HLD<\/b> \u2013 Vysok\u00e9 \u00farov\u0148ov\u00e9 n\u00e1vrhy, vysok\u00farov\u0148ov\u00fd dizajn zalo\u017een\u00fd na po\u017eiadavk\u00e1ch siete (CR). Dokument vysvet\u013euje a od\u00f4vod\u0148uje prijat\u00e9 architektonick\u00e9 rozhodnutia (topol\u00f3gia, protokoly, v\u00fdber vybavenia, ...). HLD neobsahuje podrobnosti dizajnu, napr\u00edklad o pou\u017eit\u00fdch rozhraniach a IP adres\u00e1ch. Takisto sa tu neprediskutov\u00e1va konkr\u00e9tna konfigur\u00e1cia vybavenia. Tento dokument je sk\u00f4r ur\u010den\u00fd na vysvetlenie k\u013e\u00fa\u010dov\u00fdch koncepci\u00ed dizajnu technick\u00e9mu mana\u017ementu z\u00e1kazn\u00edka.<\/p>\n<p><b>LLD<\/b> \u2013 Low Level Design, n\u00edzkolevelov\u00fd dizajn na z\u00e1klade vysokolevelov\u00e9ho (HLD). <br \/>\nMus\u00ed obsahova\u0165 v\u0161etky detaily potrebn\u00e9 na realiz\u00e1ciu projektu, ako napr\u00edklad inform\u00e1cie o tom, ako pripoji\u0165 a nastavi\u0165 zariadenia. Je to kompletn\u00fd sprievodca realiz\u00e1ciou dizajnu. Tento dokument by mal poskytn\u00fa\u0165 dostatok inform\u00e1ci\u00ed pre jeho realiz\u00e1ciu aj menej kvalifikovan\u00e9mu person\u00e1lu. <\/p>\n<p>Nie\u010do, ako napr\u00edklad IP adresy, \u010d\u00edsla AS, sch\u00e9ma fyzickej komunik\u00e1cie (cabling), m\u00f4\u017ee by\u0165 \"vy\u010dlenen\u00e9\" do samostatn\u00fdch dokumentov, ako s\u00fa <b>NIP<\/b> (Network Implementation Plan).<\/p>\n<p>Budovanie siete za\u010d\u00edna po vytvoren\u00ed t\u00fdchto dokumentov a prebieha v pr\u00edsnom s\u00falade s nimi a n\u00e1sledne je overovan\u00e9 z\u00e1kazn\u00edkom (testy) na s\u00falad s dizajnom.<\/p><\/blockquote>\n<p>\nSamozrejme, r\u00f4zni integr\u00e1tori, r\u00f4zni z\u00e1kazn\u00edci, v r\u00f4znych krajin\u00e1ch m\u00f4\u017eu ma\u0165 r\u00f4zne po\u017eiadavky na projektov\u00fa dokument\u00e1ciu. Ale chceli by sme sa vyhn\u00fa\u0165 formalit\u00e1m a zv\u00e1\u017ei\u0165 veci podstatn\u00e9. Tento krok nie je o projektovan\u00ed, ale o usporiadan\u00ed a potrebujeme dostato\u010dn\u00e9 mno\u017estvo dokumentov (sch\u00e9my, tabu\u013eky, popisy \u2026) na splnenie na\u0161ich \u00faloh. <\/p>\n<p>A pod\u013ea m\u00f4jho n\u00e1zoru existuje ak\u00fdsi absol\u00fatny minimum, bez ktor\u00e9ho nie je mo\u017en\u00e9 efekt\u00edvne kontrolova\u0165 sie\u0165.<\/p>\n<p>S\u00fa to nasleduj\u00face dokumenty:<\/p>\n<ul>\n<li>sch\u00e9ma (z\u00e1pisn\u00edk) fyzickej komunik\u00e1cie (cabling)<\/li>\n<li>sch\u00e9ma alebo sch\u00e9my siete s podstatn\u00fdmi L2\/L3 inform\u00e1ciami<\/li>\n<\/ul>\n<p><\/p>\n<h2>Sch\u00e9ma fyzick\u00e9ho prepojenia<\/h2>\n<p>\nV niektor\u00fdch mal\u00fdch spolo\u010dnostiach s\u00fa pr\u00e1ce spojen\u00e9 s in\u0161tal\u00e1ciou zariaden\u00ed a fyzickou komunik\u00e1ciou (cabling) v z\u00f3ne zodpovednosti sie\u0165ov\u00fdch in\u017einierov. <\/p>\n<p>V tomto pr\u00edpade je probl\u00e9m \u010diasto\u010dne rie\u0161en\u00fd nasleduj\u00facim pr\u00edstupom. <\/p>\n<ul>\n<li>pou\u017eite popis na rozhran\u00ed na opis toho, \u010do je k nemu pripojen\u00e9<\/li>\n<li>administrat\u00edvne vypnite (shutdown) v\u0161etky nepripojen\u00e9 porty sie\u0165ov\u00e9ho zariadenia<\/li>\n<\/ul>\n<p>\nTo je umo\u017en\u00ed r\u00fdchlo ur\u010di\u0165, \u010do je pripojen\u00e9 k tomuto portu, aj v pr\u00edpade, \u017ee nastane probl\u00e9m s linkou (ke\u010f na tomto rozhran\u00ed nefunguje cdp alebo lldp).<br \/>\nRovnako \u013eahko uvid\u00edte, ak\u00e9 porty m\u00e1te obsaden\u00e9 a ak\u00e9 s\u00fa vo\u013en\u00e9, \u010do je potrebn\u00e9 na pl\u00e1novanie pripojen\u00ed nov\u00e9ho sie\u0165ov\u00e9ho zariadenia, serverov alebo pracovn\u00fdch stan\u00edc. <\/p>\n<p>Je zrejm\u00e9, \u017ee ak strat\u00edte pr\u00edstup k vybaveniu, strat\u00edte aj pr\u00edstup k t\u00fdmto inform\u00e1ci\u00e1m. Okrem toho t\u00fdmto sp\u00f4sobom nebudete m\u00f4c\u0165 zdokumentova\u0165 tak\u00e9 d\u00f4le\u017eit\u00e9 inform\u00e1cie ako to, ak\u00e9 zariadenie to je, ak\u00fa m\u00e1 spotrebu, ko\u013eko portov m\u00e1, v akej stojke sa nach\u00e1dza, ak\u00e9 s\u00fa tam patch panely a kam (do akej stojky\/patch panelu) s\u00fa zapojen\u00e9. Preto je nasledovn\u00e9 dodato\u010dn\u00e9 dokumentovanie (nielen popisy na vybaven\u00ed) ve\u013emi u\u017eito\u010dn\u00e9.<\/p>\n<p>Ide\u00e1lnym rie\u0161en\u00edm je pou\u017e\u00edva\u0165 aplik\u00e1cie, ktor\u00e9 s\u00fa navrhnut\u00e9 na pr\u00e1cu s podobn\u00fdmi inform\u00e1ciami. No m\u00f4\u017eete sa obmedzi\u0165 aj na jednoduch\u00e9 tabu\u013eky (napr\u00edklad v Exceli) alebo zobrazi\u0165 inform\u00e1cie, ktor\u00e9 pova\u017eujete za potrebn\u00e9, v sch\u00e9mach L1\/L2.<\/p>\n<blockquote><p>D\u00f4le\u017eit\u00e9!<\/p>\n<p>Sie\u0165ov\u00fd in\u017einier m\u00f4\u017ee dobre pozna\u0165 nuansy a \u0161tandardy HKP, typy stojok, typy zdrojov nep\u0159eru\u0161ovan\u00e9ho nap\u00e1jania, \u010do je studen\u00fd a hor\u00faci koridor, vykon\u00e1va\u0165 spr\u00e1vne uzemnenie,\u2026 rovnako ako m\u00f4\u017ee taktie\u017e vedie\u0165 fyziku element\u00e1rnych \u010dast\u00edc alebo C++. Ale treba rozumie\u0165 tomu, \u017ee v\u0161etko toto nie je jeho oblas\u0165ou znalosti. <\/p>\n<p>Preto dobr\u00fdm zvykom je ma\u0165 oddelenia alebo vyhraden\u00fdch \u013eud\u00ed na rie\u0161enie \u00faloh s\u00favisiacich s in\u0161tal\u00e1ciou, pripojen\u00edm, podporou funk\u010dnosti vybavenia a fyzickou komut\u00e1ciou. Zvy\u010dajne pre d\u00e1tov\u00e9 centr\u00e1 to s\u00fa in\u017einieri d\u00e1tov\u00fdch centier, a pre kancel\u00e1riu \u2014 help-desk. <\/p>\n<p>Ak s\u00fa tak\u00e9to oddelenia v va\u0161ej spolo\u010dnosti zoh\u013eadnen\u00e9, ot\u00e1zky vedenia denn\u00edka fyzickej komut\u00e1cie nie s\u00fa va\u0161ou \u00falohou a m\u00f4\u017eete sa obmedzi\u0165 iba na popis na rozhran\u00ed a administrat\u00edvne vypnutie nepou\u017e\u00edvan\u00fdch portov.<\/p><\/blockquote>\n<h2>Sch\u00e9my siete<\/h2>\n<p>\nNeexistuje univerz\u00e1lny pr\u00edstup k kresleniu sch\u00e9m.<\/p>\n<p>Najd\u00f4le\u017eitej\u0161ie je, aby sch\u00e9my poskytovali pochopenie toho, ako bude pr\u00fadi\u0165 prev\u00e1dzka cez ak\u00e9 logick\u00e9 a fyzick\u00e9 prvky va\u0161ej siete.<\/p>\n<p>Pod fyzick\u00fdmi prvkami rozumieme<\/p>\n<ul>\n<li>akt\u00edvne vybavenie<\/li>\n<li>rozhrania\/porty akt\u00edvneho zariadenia<\/li>\n<\/ul>\n<p>\nPod logick\u00fdmi \u2014 <\/p>\n<ul>\n<li>logick\u00e9 zariadenia (N7K VDC, Palo Alto VSYS, \u2026)<\/li>\n<li>VRF <\/li>\n<li>vlan<\/li>\n<li>podrozhrania<\/li>\n<li>tunely<\/li>\n<li>z\u00f3ny<\/li>\n<li>\u2026<\/li>\n<\/ul>\n<p>\nTak, ak va\u0161a sie\u0165 nie je \u00faplne jednoduch\u00e1, bude pozost\u00e1va\u0165 z r\u00f4znych segmentov. <br \/>\nnapr\u00edklad<\/p>\n<ul>\n<li>d\u00e1tov\u00e9 centrum<\/li>\n<li>internet<\/li>\n<li>WAN<\/li>\n<li>dia\u013ekov\u00fd pr\u00edstup<\/li>\n<li>kancel\u00e1rska LAN<\/li>\n<li>DMZ<\/li>\n<li>\u2026<\/li>\n<\/ul>\n<p>\nBolo by rozumn\u00e9 ma\u0165 nieko\u013eko sch\u00e9m, ktor\u00e9 poskytn\u00fa ako v\u0161eobecn\u00fd preh\u013ead (ako prech\u00e1dza traffic medzi v\u0161etk\u00fdmi t\u00fdmito segmentmi), tak aj podrobn\u00e9 vysvetlenie ka\u017ed\u00e9ho jednotliv\u00e9ho segmentu.<\/p>\n<p>Ke\u010f\u017ee v modern\u00fdch sie\u0165ach m\u00f4\u017ee by\u0165 ve\u013ea logick\u00fdch \u00farovn\u00ed, dobr\u00fdm (ale nie povinn\u00fdm) pr\u00edstupom je vytv\u00e1ra\u0165 r\u00f4zne sch\u00e9my pre r\u00f4zne \u00farovne, napr\u00edklad v pr\u00edpade overlay pr\u00edstupu to m\u00f4\u017eu by\u0165 nasleduj\u00face sch\u00e9my:<\/p>\n<ul>\n<li>overlay<\/li>\n<li>L1\/L2 underlay<\/li>\n<li>L3 underlay<\/li>\n<\/ul>\n<p>\nSamozrejme, najd\u00f4le\u017eitej\u0161ou sch\u00e9mou, bez ktorej nie je mo\u017en\u00e9 pochopi\u0165 my\u0161lienku v\u00e1\u0161ho dizajnu, je sch\u00e9ma smerovania.<\/p>\n<h4>Sch\u00e9ma smerovania<\/h4>\n<p>\nNa tejto sch\u00e9me by malo by\u0165 uveden\u00e9<\/p>\n<ul>\n<li>ak\u00e9 smerovacie protokoly a kde sa pou\u017e\u00edvaj\u00fa<\/li>\n<li>z\u00e1kladn\u00e9 inform\u00e1cie o nastaveniach smerovacieho protokolu (area\/AS number\/router-id\/\u2026)<\/li>\n<li>na ak\u00fdch zariadeniach doch\u00e1dza k redistrib\u00facii<\/li>\n<li>kde prebieha filtrovanie a agreg\u00e1cia tr\u00e1s<\/li>\n<li>inform\u00e1cie o predvolenom smere <\/li>\n<\/ul>\n<p>\nTak, \u010dastokr\u00e1t je u\u017eito\u010dn\u00e1 aj L2 sch\u00e9ma (OSI).<\/p>\n<h4>L2 sch\u00e9ma (OSI)<\/h4>\n<p>\nNa tejto sch\u00e9me m\u00f4\u017eu by\u0165 uveden\u00e9 nasleduj\u00face inform\u00e1cie:<\/p>\n<ul>\n<li>ak\u00e9 VLAN<\/li>\n<li>ak\u00e9 porty s\u00fa trunk porty<\/li>\n<li>ak\u00e9 porty s\u00fa agregovan\u00e9 do ether-channel (port channel), virtu\u00e1lny port channel<\/li>\n<li>ak\u00e9 STP protokoly a na ak\u00fdch zariadeniach sa pou\u017e\u00edvaj\u00fa<\/li>\n<li>z\u00e1kladn\u00e9 nastavenia STP: root\/root backup, STP cost, priorita portu<\/li>\n<li>\u010fal\u0161ie nastavenia STP: BPDU guard\/filter, root guard ...<\/li>\n<\/ul>\n<p><\/p>\n<h2>Typick\u00e9 chyby pri navrhovan\u00ed<\/h2>\n<p><\/p>\n<blockquote><p>Pr\u00edklad zl\u00e9ho pr\u00edstupu k budovaniu siete.<\/p>\n<p>Po\u010fme si zobrazi\u0165 jednoduch\u00fd pr\u00edklad budovania jednoduchej kancel\u00e1rskej lok\u00e1lnej siete.<\/p>\n<p>Pri v\u00fdu\u010dbe telekomunik\u00e1ci\u00ed \u0161tudentom m\u00f4\u017eem poveda\u0165, \u017ee prakticky ka\u017ed\u00fd \u0161tudent v polovici druh\u00e9ho semestra m\u00e1 potrebn\u00e9 znalosti (v r\u00e1mci kurzu, ktor\u00fd som viedol) na to, aby nastavil jednoduch\u00fa kancel\u00e1rsku LAN.<\/p>\n<p>\u010co je tak\u00e9 n\u00e1ro\u010dn\u00e9 na prepojenie prep\u00edna\u010dov, nastaven\u00ed VLAN, SVI rozhran\u00ed (v pr\u00edpade L3 prep\u00edna\u010dov) a zadan\u00ed statick\u00e9ho smerovania?<\/p>\n<p>V\u0161etko bude fungova\u0165.<\/p>\n<p>Ale pri tom zost\u00e1vaj\u00fa bokom ot\u00e1zky t\u00fdkaj\u00face sa <\/p>\n<ul>\n<li>bezpe\u010dnosti<\/li>\n<li>z\u00e1lohovania<\/li>\n<li>\u0161k\u00e1lovate\u013enosti siete<\/li>\n<li>v\u00fdkonom<\/li>\n<li>priepustnosti<\/li>\n<li>spo\u013eahlivosti<\/li>\n<li>\u2026<\/li>\n<\/ul>\n<p>\nNiekedy po\u010dujem tvrdenie, \u017ee kancel\u00e1rska LAN je nie\u010do ve\u013emi jednoduch\u00e9, a to zvy\u010dajne od in\u017einierov (a mana\u017e\u00e9rov), ktor\u00ed sa zaoberaj\u00fa v\u0161etk\u00fdm mo\u017en\u00fdm, len nie sie\u0165ami, a hovoria to tak sebavedomo, \u017ee sa ne\u010dudujte, ak bude LAN vytvoren\u00e1 \u013eu\u010fmi s nedostato\u010dnou praxou a znalos\u0165ami a bude zahr\u0148ova\u0165 pribli\u017ene tie chyby, ktor\u00e9 op\u00ed\u0161em ni\u017e\u0161ie.<\/p><\/blockquote>\n<p><\/p>\n<h4>Charakteristick\u00e9 chyby n\u00e1vrhu na \u00farovni L1 (OSI)<\/h4>\n<p><\/p>\n<ul>\n<li>Ak ste zodpovedn\u00ed aj za \u0161trukt\u00farovan\u00fa kabel\u00e1\u017e, jedn\u00fdm z najnepr\u00edjemnej\u0161\u00edch dedi\u010dstiev, ktor\u00e9 v\u00e1m m\u00f4\u017ee osta\u0165, je nedbalo a neprakticky navrhnut\u00e9 zapojenie.<\/li>\n<\/ul>\n<p>\nTie\u017e by som ku typu L1 priradil chyby s\u00favisiace so zdrojmi pou\u017e\u00edvan\u00e9ho zariadenia, napr\u00edklad,<\/p>\n<ul>\n<li>nedostato\u010dn\u00e1 \u0161\u00edrka p\u00e1sma<\/li>\n<li>nedostato\u010dn\u00fd TCAM na zariaden\u00ed (alebo neefekt\u00edvne jeho vyu\u017eitie)<\/li>\n<li>nedostato\u010dn\u00fd v\u00fdkon (\u010dasto sa to t\u00fdka firewallov)<\/li>\n<\/ul>\n<p><\/p>\n<h4>Charakteristick\u00e9 chyby n\u00e1vrhu na \u00farovni L2 (OSI)<\/h4>\n<p>\n\u010casto, ke\u010f nie je dobr\u00e9 pochopenie, ako funguje STP a ak\u00e9 potenci\u00e1lne probl\u00e9my so sebou nesie, s\u00fa prep\u00edna\u010de pripojen\u00e9 chaoticky, s predvolen\u00e9 nastavenia bez dodato\u010dn\u00e9ho ladenia STP. <\/p>\n<p>V d\u00f4sledku toho \u010dasto m\u00e1me nasledovn\u00e9<\/p>\n<ul>\n<li>ve\u013ek\u00fd STP priemer siete, \u010do m\u00f4\u017ee vies\u0165 k broadcastov\u00fdm b\u00farkam <\/li>\n<li>STP root bude ur\u010den\u00fd n\u00e1hodne (na z\u00e1klade mac adresy) a cesta trafiku bude suboptim\u00e1lna<\/li>\n<li>porty pripojen\u00e9 k hostite\u013eom nebud\u00fa nastaven\u00e9 ako edge (portfast), \u010do povedie k prepo\u010dtu STP pri zapnut\u00ed\/vypnut\u00ed koncov\u00fdch zariaden\u00ed<\/li>\n<li>sie\u0165 nebude segmentovan\u00e1 na \u00farovni L1\/L2, \u010do sp\u00f4sob\u00ed, \u017ee probl\u00e9my s ktor\u00fdmko\u013evek prep\u00edna\u010dom (napr\u00edklad pre\u0165a\u017eenie nap\u00e1jan\u00edm) poved\u00fa k prepo\u010dtu STP topol\u00f3gie a zastaveniu trafiku vo v\u0161etk\u00fdch VLAN na v\u0161etk\u00fdch prep\u00edna\u010doch (vr\u00e1tane kritick\u00e9ho segmentu z h\u013eadiska kontinuity slu\u017eby)<\/li>\n<\/ul>\n<p><\/p>\n<h4>Pr\u00edklady ch\u00fdb v navrhovan\u00ed L3 (OSI)<\/h4>\n<p>\nNieko\u013eko charakteristick\u00fdch ch\u00fdb za\u010diato\u010dn\u00edkov v sieti:<\/p>\n<ul>\n<li>\u010dast\u00e9 pou\u017e\u00edvanie (alebo pou\u017e\u00edvanie iba) statick\u00e9ho routingu<\/li>\n<li>pou\u017e\u00edvanie neoptim\u00e1lnych protokolov routovania pre dan\u00fd dizajn<\/li>\n<li>neoptim\u00e1lna logick\u00e1 segment\u00e1cia siete<\/li>\n<li>neoptim\u00e1lne vyu\u017e\u00edvanie adresn\u00e9ho priestoru, \u010do zabra\u0148uje agreg\u00e1cii tr\u00e1s<\/li>\n<li>nedostatok z\u00e1lo\u017en\u00fdch tr\u00e1s<\/li>\n<li>nedostatok z\u00e1lohovania pre default gateway<\/li>\n<li>asymetrick\u00e9 smerovanie pri prestavbe tr\u00e1s (m\u00f4\u017ee by\u0165 kritick\u00e9 v pr\u00edpade NAT\/PAT, statefull firewallov)<\/li>\n<li>probl\u00e9my s MTU<\/li>\n<li>pri prestavbe tr\u00e1s prech\u00e1dza traffic cez in\u00e9 bezpe\u010dnostn\u00e9 z\u00f3ny alebo dokonca in\u00e9 firewally, \u010do vedie k tomu, \u017ee tento traffic je zamietnut\u00fd<\/li>\n<li>zl\u00e1 \u0161k\u00e1lovate\u013enos\u0165 topol\u00f3gie<\/li>\n<\/ul>\n<p><\/p>\n<h2>Krit\u00e9ri\u00e1 hodnotenia kvality dizajnu<\/h2>\n<p>\nKe\u010f hovor\u00edme o optimalite\/neoptimalite, mus\u00edme porozumie\u0165, pod\u013ea ak\u00fdch krit\u00e9ri\u00ed to m\u00f4\u017eeme hodnoti\u0165. Z m\u00f4jho poh\u013eadu s\u00fa najpodstatnej\u0161ie (ale nie v\u0161etky) krit\u00e9ri\u00e1 (a ich vysvetlenie vz\u0165ahuj\u00face sa na smerovacie protokoly):<\/p>\n<ul>\n<li>\u0161k\u00e1lovate\u013enos\u0165 (scalability)<br \/>\n Napr\u00edklad, ak ste sa rozhodli prida\u0165 \u010fal\u0161ie d\u00e1tov\u00e9 centrum. Ako \u013eahko to m\u00f4\u017eete urobi\u0165.<\/li>\n<li>pohodlie v spr\u00e1ve (managability)<br \/>\n Ako jednoducho a bezpe\u010dne sa vykon\u00e1vaj\u00fa opera\u010dn\u00e9 zmeny, napr\u00edklad oznamovanie novej siete alebo filtrovanie tr\u00e1s<\/li>\n<li>dostupnos\u0165 (availability)<br \/>\n Ak\u00fd percentu\u00e1lny podiel \u010dasu va\u0161a syst\u00e9m poskytuje po\u017eadovan\u00fa \u00farove\u0148 slu\u017eieb<\/li>\n<li>bezpe\u010dnos\u0165 (security)<br \/>\n Ako s\u00fa chr\u00e1nen\u00e9 pren\u00e1\u0161an\u00e9 d\u00e1ta<\/li>\n<li>cena<\/li>\n<\/ul>\n<p><\/p>\n<h2>Zmeny<\/h2>\n<p>\nHlavn\u00fd princ\u00edp v tejto f\u00e1ze m\u00f4\u017eeme vyjadri\u0165 vzorcom \u201eneubl\u00ed\u017e\u201c.<br \/>\nPreto, aj ke\u010f sa nemus\u00edte \u00faplne zhodova\u0165 s dizajnom a vybranou implement\u00e1ciou (konfigur\u00e1ciou), nie v\u017edy je rozumn\u00e9 robi\u0165 zmeny. Rozumn\u00fd pr\u00edstup je zoradi\u0165 v\u0161etky zjaven\u00e9 probl\u00e9my pod\u013ea dvoch parametrov: <\/p>\n<ul>\n<li>ako \u013eahko m\u00f4\u017ee by\u0165 tento probl\u00e9m opraven\u00fd<\/li>\n<li>ako ve\u013ek\u00e9 riziko nesie<\/li>\n<\/ul>\n<p>\nPredov\u0161etk\u00fdm je potrebn\u00e9 odstr\u00e1ni\u0165 to, \u010do v s\u00fa\u010dasnosti zni\u017euje \u00farove\u0148 poskytovan\u00fdch slu\u017eieb pod pr\u00edpustn\u00fa hranicu, napr\u00edklad probl\u00e9my ved\u00face k strate paketov. Potom odstr\u00e1\u0148te to, \u010do je najjednoduch\u0161ie a najbezpe\u010dnej\u0161ie opravi\u0165, v porad\u00ed zni\u017euj\u00facej sa z\u00e1va\u017enosti rizika (od probl\u00e9mov v dizajne alebo konfigur\u00e1cii, ktor\u00e9 nes\u00fa v\u00e4\u010d\u0161ie rizik\u00e1, k men\u0161\u00edm).<\/p>\n<p>Perfekcionizmus v tejto f\u00e1ze m\u00f4\u017ee by\u0165 \u0161kodliv\u00fd. Prive\u010fte dizajn do uspokojiv\u00e9ho stavu a synchronizujte konfigur\u00e1ciu siete v s\u00falade s n\u00edm.<br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/434750\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0442\u043e\u0440\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb. \u0421\u043e\u0434\u0435\u0440\u0436\u0430\u043d\u0438\u0435 \u0432\u0441\u0435\u0445 \u0441\u0442\u0430\u0442\u0435\u0439 \u0446\u0438\u043a\u043b\u0430 \u0438 \u0441\u0441\u044b\u043b\u043a\u0438 \u043c\u043e\u0436\u043d\u043e \u043d\u0430\u0439\u0442\u0438 \u0437\u0434\u0435\u0441\u044c. \u041d\u0430\u0448\u0430 \u0446\u0435\u043b\u044c \u043d\u0430 \u0434\u0430\u043d\u043d\u043e\u043c \u044d\u0442\u0430\u043f\u0435 \u2014 \u043d\u0430\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u043f\u043e\u0440\u044f\u0434\u043a\u0430 \u0432 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u0438 \u0438 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438. \u041d\u0430 \u0432\u044b\u0445\u043e\u0434\u0435 \u044d\u0442\u043e\u0433\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u0430 \u0443 \u0432\u0430\u0441 \u0434\u043e\u043b\u0436\u0435\u043d \u0431\u044b\u0442\u044c \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u044b\u0439 \u043a\u043e\u043c\u043f\u043b\u0435\u043a\u0442 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u043e\u0432 \u0438 \u0441\u0435\u0442\u044c, \u0441\u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u0430\u044f \u0432 \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0438\u0438 \u0441 \u043d\u0438\u043c\u0438. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23042,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31067","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0442\u043e\u0440\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c. \u0413\u043b\u0430\u0432\u0430 \u0432\u0442\u043e\u0440\u0430\u044f. \u0427\u0438\u0441\u0442\u043a\u0430 \u0438 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0442\u043e\u0440\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:39:16+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:39:16+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Ako z\u00edska\u0165 kontrolu nad sie\u0165ovou infra\u0161trukt\u00farou. Kapitola druh\u00e1. \u010cistenie a dokumentovanie | ProHoster","description":"Tento \u010dl\u00e1nok je druh\u00fd v cykle \u010dl\u00e1nkov \u201eAko z\u00edska\u0165 kontrolu nad sie\u0165ovou infra\u0161trukt\u00farou\u201c.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c. \u0413\u043b\u0430\u0432\u0430 \u0432\u0442\u043e\u0440\u0430\u044f. \u0427\u0438\u0441\u0442\u043a\u0430 \u0438 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 | ProHoster","og:description":"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0442\u043e\u0440\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie","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-31T18:39:16+00:00","article:modified_time":"2019-10-31T18:39:16+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31067","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-21 04:22:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:24:13","updated":"2026-01-21 04:22:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/31067","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=31067"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/31067\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/23042"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=31067"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=31067"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=31067"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}