{"id":31817,"date":"2019-10-31T21:43:19","date_gmt":"2019-10-31T18:43:19","guid":{"rendered":"https:\/\/prohoster.info\/blog\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki\/"},"modified":"2019-10-31T21:43:19","modified_gmt":"2019-10-31T18:43:19","slug":"vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","title":{"rendered":"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/d71067a47ba1093d9783832e76e8eafb.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/432980\/\">Prv\u00e1 \u010das\u0165. \u00davod<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441026\/\">Druh\u00e1 \u010das\u0165. Nastavenie pravidiel Firewall a NAT<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441882\/\">\u010cas\u0165 tretia. Nastavenie DHCP<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/444644\/\">\u0160tvrt\u00e1 \u010das\u0165. Nastavenie routingu<\/a><\/noindex><\/p>\n<p>Minul\u00fd t\u00fd\u017ede\u0148 sme hovorili o mo\u017enostiach NSX Edge z poh\u013eadu statick\u00e9ho a dynamick\u00e9ho routingu, a dnes sa budeme zaobera\u0165 vyva\u017eova\u010dom z\u00e1\u0165a\u017ee.<br \/>\nPredt\u00fdm, ako za\u010dneme s nastaven\u00edm, chcel by som ve\u013emi stru\u010dne pripomen\u00fa\u0165 hlavn\u00e9 typy vyva\u017eovania. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Te\u00f3ria<\/h3>\n<p>\nV\u0161etky dne\u0161n\u00e9 rie\u0161enia vyva\u017eovania z\u00e1\u0165a\u017ee sa zvy\u010dajne delia do dvoch kateg\u00f3ri\u00ed: vyva\u017eovanie na \u0161tvrtom (transportnom) a siedmom (aplikovanom) stupni modelu <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%A1%D0%B5%D1%82%D0%B5%D0%B2%D0%B0%D1%8F_%D0%BC%D0%BE%D0%B4%D0%B5%D0%BB%D1%8C_OSI\">OSI<\/a><\/noindex>. Model OSI nie je najlep\u0161ou referen\u010dnou bodkou pri popisovan\u00ed met\u00f3d vyva\u017eovania. Napr\u00edklad, ak L4 vyva\u017eova\u010d podporuje aj termin\u00e1ciu TLS, st\u00e1va sa v tom pr\u00edpade L7 vyva\u017eova\u010dom? Ale \u010do je, to je.<\/p>\n<ul>\n<li><b>Vyva\u017eova\u010d L4 <\/b>sa zvy\u010dajne nach\u00e1dza medzi klientom a s\u00faborom dostupn\u00fdch backendov ako prostredn\u00fd proxy, ktor\u00fd terminuj\u00facu TCP pripojenia (to znamen\u00e1, \u017ee odpoved\u00e1 na SYN), vyber\u00e1 backend a iniciuje vo\u010di nemu nov\u00e9 TCP rel\u00e1ciu, pri\u010dom posiela SYN. Tento typ je jedn\u00fdm z z\u00e1kladn\u00fdch, existuj\u00fa aj in\u00e9 varianty.<\/li>\n<li><b>Vyva\u017eova\u010d L7<\/b> rozdelen\u00ed prev\u00e1dzku medzi dostupn\u00fdmi backendmi 'sofistikovanej\u0161ie', ako to rob\u00ed L4 vyva\u017eova\u010d. M\u00f4\u017ee sa rozhodova\u0165 o v\u00fdbere backendu na z\u00e1klade, napr\u00edklad, obsahu spr\u00e1vy HTTP (URL adresa, cookie at\u010f.).<\/li>\n<\/ul>\n<p>\nNez\u00e1visle od typu m\u00f4\u017ee vyva\u017eova\u010d podporova\u0165 nasleduj\u00face funkcie:<\/p>\n<ul>\n<li> Objavovanie slu\u017eieb - proces ur\u010dovania sady dostupn\u00fdch backendov (Static, DNS, Consul, Etcd at\u010f.).<\/li>\n<li>Kontrola funk\u010dnosti objaven\u00fdch backendov (akt\u00edvny 'ping' backendu pomocou HTTP po\u017eiadavky, pas\u00edvne zis\u0165ovanie probl\u00e9mov v TCP pripojeniach, pr\u00edtomnos\u0165 viacer\u00fdch po sebe id\u00facich 503 HTTP-k\u00f3dov v odpovediach at\u010f.).<\/li>\n<li>Samotn\u00e9 vyva\u017eovanie (round robin, n\u00e1hodn\u00fd v\u00fdber, hash IP adresy, URI).<\/li>\n<li>Termin\u00e1cia TLS a overovanie certifik\u00e1tov.<\/li>\n<li>Mo\u017enosti s\u00favisiace s bezpe\u010dnostn\u00fdmi opatreniami (autentifik\u00e1cia, prevencia DoS \u00fatokov, obmedzenie r\u00fdchlosti) a mnoho \u010fal\u0161ieho.<\/li>\n<\/ul>\n<p>\nNSX Edge pon\u00faka podporu dvoch re\u017eimov nasadenia vyva\u017eova\u010da:<\/p>\n<p><b>Re\u017eim proxy, alebo one-arm<\/b>V tomto re\u017eime NSX Edge pri zasielan\u00ed po\u017eiadavky na jeden z backendov pou\u017e\u00edva svoju IP adresu ako adresu zdroja. Takto vyva\u017eova\u010d s\u00fa\u010dasne vykon\u00e1va funkcie Source a Destination NAT. Backend vid\u00ed cel\u00fd prenos ako zaslan\u00fd z vyva\u017eova\u010da a odpoved\u00e1 mu priamo. V takej sch\u00e9me mus\u00ed by\u0165 vyva\u017eova\u010d v rovnakom sie\u0165ovom segmente s vn\u00fatorn\u00fdmi servermi.<\/p>\n<p>Takto to prebieha:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Pou\u017e\u00edvate\u013e zasiela po\u017eiadavku na VIP adresu (adresu vyva\u017eova\u010da), ktor\u00e1 je nakonfigurovan\u00e1 na Edge.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge si vyber\u00e1 jeden z backendov a vykon\u00e1va destination NAT, pri\u010dom nahr\u00e1dza VIP adresu adresou vybran\u00e9ho backendu.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge vykon\u00e1va source NAT, pri\u010dom nahr\u00e1dza adresu zasielaj\u00faceho pou\u017e\u00edvate\u013ea svojou vlastnou.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Pakety s\u00fa zasielan\u00e9 k vybran\u00e9mu backendu.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Backend neodpoved\u00e1 priamo pou\u017e\u00edvate\u013eovi, ale Edge, preto\u017ee p\u00f4vodn\u00e1 adresa pou\u017e\u00edvate\u013ea bola zmenen\u00e1 na adresu vyva\u017eova\u010da.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge pren\u00e1\u0161a odpove\u010f servera pou\u017e\u00edvate\u013eovi.<br \/>\nSch\u00e9ma ni\u017e\u0161ie.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/a6073ec63f7aca05d61c5a40de2ba6be.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Prieh\u013eadn\u00fd, alebo inline, re\u017eim.<\/b> V tomto scen\u00e1ri m\u00e1 vyva\u017eova\u010d rozhrania vo vn\u00fatorn\u00fdch a vonkaj\u0161\u00edch sie\u0165ach. Vn\u00fatorn\u00e1 sie\u0165 nie je priamo pr\u00edstupn\u00e1 z vonkaj\u0161ej strany. Vstavan\u00fd vyva\u017eova\u010d z\u00e1\u0165a\u017ee funguje ako NAT br\u00e1na pre virtu\u00e1lne stroje vo vn\u00fatorn\u00fdch sie\u0165ach.<\/p>\n<p>Mechanizmus je nasleduj\u00faci:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Pou\u017e\u00edvate\u013e zasiela po\u017eiadavku na VIP adresu (adresu vyva\u017eova\u010da), ktor\u00e1 je nakonfigurovan\u00e1 na Edge.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge si vyber\u00e1 jeden z backendov a vykon\u00e1va destination NAT, pri\u010dom nahr\u00e1dza VIP adresu adresou vybran\u00e9ho backendu.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Pakety s\u00fa zasielan\u00e9 k vybran\u00e9mu backendu.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Backend prij\u00edma po\u017eiadavku s p\u00f4vodnou adresou pou\u017e\u00edvate\u013ea (source NAT nebol vykonan\u00fd) a odpoved\u00e1 mu priamo.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Prenos je op\u00e4\u0165 prij\u00edman\u00fd vyva\u017eova\u010dom z\u00e1\u0165a\u017ee, preto\u017ee v inline sch\u00e9me zvy\u010dajne vystupuje ako predvolen\u00e1 br\u00e1na pre farmu serverov.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge vykon\u00e1va source NAT na zaslanie prenosu pou\u017e\u00edvate\u013eovi, pri\u010dom pou\u017e\u00edva svoju VIP ako source IP adresu.<br \/>\nSch\u00e9ma ni\u017e\u0161ie.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/9ad9adcac02d40db1603aee84387264a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Praktika<\/h3>\n<p>\nNa mojej testovacej platforme s\u00fa nakonfigurovan\u00e9 3 servery s Apache, ktor\u00e9 s\u00fa nastaven\u00e9 na pr\u00e1cu cez HTTPS. Edge bude vykon\u00e1va\u0165 vyva\u017eovanie HTTPS po\u017eiadaviek met\u00f3dou round robin, pri\u010dom ka\u017ed\u00fd nov\u00fd po\u017eiadavok bude proxyovan\u00fd na nov\u00fd server.<br \/>\nPo\u010fme na to.<\/p>\n<p><b>Generujeme SSL certifik\u00e1t, ktor\u00fd bude pou\u017e\u00edva\u0165 NSX Edge.<\/b><br \/>\nM\u00f4\u017eete importova\u0165 platn\u00fd CA certifik\u00e1t alebo pou\u017ei\u0165 samopodp\u00edsan\u00fd. V tomto teste pou\u017eijem samopodp\u00edsan\u00fd.<\/p>\n<ol>\n<li>V rozhran\u00ed vCloud Director prejdeme do nastaven\u00ed slu\u017eieb Edge.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/df9be9f6d5b92af1cbe19f40459c8d9f.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Prejdeme na kartu Certifik\u00e1ty. Z ponuky akci\u00ed vyberieme pridanie nov\u00e9ho CSR.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/72185bf69cb0c4d8dc0cbadc8fe4f376.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vypl\u0148te potrebn\u00e9 polia a kliknite na Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/196394d4633d76dfde6d89b8f7049e19.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vyberte pr\u00e1ve vytvoren\u00fd CSR a zvo\u013ete mo\u017enos\u0165 self-sign CSR.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/262e7a1ede8bda39a9ee098f360a38e3.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vyberte dobu platnosti certifik\u00e1tu a kliknite na Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/6c880218fd7874652e6540a0bde18310.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Samosignovan\u00fd certifik\u00e1t sa objavil v zozname dostupn\u00fdch certifik\u00e1tov.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/f065f461da8f96ca31c96d3c801350ec.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Nastavujeme Application Profile.<\/b><br \/>\nApplication profily poskytuj\u00fa \u00fapln\u00fa kontrolu nad sie\u0165ov\u00fdm prenosom a zjednodu\u0161uj\u00fa oraz efekt\u00edvne spravovanie. Pomocou nich m\u00f4\u017eete definova\u0165 spr\u00e1vanie pre konkr\u00e9tne typy prenosu. <\/p>\n<ol>\n<li>Prejdite na kartu Load Balancer a aktivujte vyva\u017eova\u010d. Mo\u017enos\u0165 Acceleration enabled umo\u017e\u0148uje vyva\u017eova\u010du pou\u017e\u00edva\u0165 r\u00fdchlej\u0161ie L4 vyva\u017eovanie namiesto L7.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/1ee064e2fe234fb1d96ec327f3f92f05.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Prejdite na kartu Application profile, aby ste nastavili profil aplik\u00e1cie. Kliknite na +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/5686a86bdff4d973f33f1a9d362ad273.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Zadajte n\u00e1zov profilu a vyberte typ prenosu, pre ktor\u00fd bude profil pou\u017eit\u00fd. Vysvetl\u00edm niektor\u00e9 parametre.<br \/>\n<b>Persistence<\/b> \u2013 uchov\u00e1va a sleduje \u00fadaje rel\u00e1cie, napr\u00edklad: ktor\u00fd konkr\u00e9tny server z poolu obsluhuje po\u017eiadavku pou\u017e\u00edvate\u013ea. To zabezpe\u010duje, \u017ee po\u017eiadavky pou\u017e\u00edvate\u013ea s\u00fa smerovan\u00e9 k jedn\u00e9mu a tomu ist\u00e9mu \u010dlenovi poolu po\u010das celej doby rel\u00e1cie alebo nasleduj\u00facich rel\u00e1ci\u00ed.<br \/>\n<b>Enable SSL passthrough<\/b> \u2013 pri zvolen\u00ed tejto mo\u017enosti NSX Edge prest\u00e1va terminova\u0165 SSL. Namiesto toho sa termin\u00e1cia uskuto\u010d\u0148uje priamo na serveroch, pre ktor\u00e9 sa vykon\u00e1va vyva\u017eovanie.<br \/>\n<b>Insert X-Forwarded-For HTTP header<\/b> \u2013 umo\u017e\u0148uje ur\u010di\u0165 p\u00f4vodn\u00fa IP adresu klienta, ktor\u00fd sa prip\u00e1ja k webov\u00e9mu serveru cez vyva\u017eova\u010d.<br \/>\n<b>Enable Pool Side SSL<\/b> \u2013 umo\u017e\u0148uje ozna\u010di\u0165, \u017ee vybran\u00fd pool pozost\u00e1va z HTTPS serverov.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/81fa688f063f5cf1719461884bbb8dc2.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Ke\u010f\u017ee budem vyva\u017eova\u0165 HTTPS prenos, je potrebn\u00e9 aktivova\u0165 Pool Side SSL a vybra\u0165 predt\u00fdm vygenerovan\u00fd certifik\u00e1t na karte Virtual Server Certificates \u2014&gt; Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/d2585bcc33e57adc561bc5d956057479.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Podobne pre Pool Certificates \u2014&gt; Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/b565acf03e4eba313b4624a912310663.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Vytv\u00e1rame pool serverov, ktor\u00e9ho prenos bude vyva\u017eovan\u00fd.<\/b><\/p>\n<ol>\n<li>Prejdite na kartu Pools. Kliknite na +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/e3fd9f747f3cbc43f3d348c05ece07fd.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Zadajte n\u00e1zov poolu, vyberte algoritmus (budem pou\u017e\u00edva\u0165 round robin) a typ monitorovania pre health check backendu. Mo\u017enos\u0165 Transparent ur\u010duje, \u010di s\u00fa p\u00f4vodn\u00e9 source IP klientov vidite\u013en\u00e9 pre intern\u00e9 servery.\n<ul>\n<li>Ak je mo\u017enos\u0165 vypnut\u00e1, prenos pre intern\u00e9 servery ide s source IP vyva\u017eova\u010da.\n<\/li>\n<li> Ak je mo\u017enos\u0165 zapnut\u00e1, intern\u00e9 servery vidia source IP klientov. V takej konfigur\u00e1cii mus\u00ed NSX Edge fungova\u0165 ako predvolen\u00e1 br\u00e1na, aby zabezpe\u010dilo, \u017ee vracaj\u00face pakety prech\u00e1dzaj\u00fa cez NSX Edge.<\/li>\n<\/ul>\n<p>NSX podporuje nasleduj\u00face algoritmy vyva\u017eovania:<\/p>\n<ul>\n<li><b>IP_HASH<\/b> \u2013 v\u00fdber servera na z\u00e1klade v\u00fdsledkov hash funkcie pre zdrojov\u00fa a cie\u013eov\u00fa IP adresu ka\u017ed\u00e9ho paketu.<\/li>\n<li> <b>LEASTCONN <\/b>\u2013 vyva\u017eovanie prich\u00e1dzaj\u00facich spojen\u00ed pod\u013ea po\u010dtu u\u017e existuj\u00facich na konkr\u00e9tnom serveri. Nov\u00e9 spojenia bud\u00fa smerovan\u00e9 na server s najmen\u0161\u00edm po\u010dtom spojen\u00ed.<\/li>\n<li> <b>ROUND_ROBIN <\/b>\u2013 nov\u00e9 spojenia sa odosielaj\u00fa na ka\u017ed\u00fd server po poriadku, v s\u00falade s predp\u00edsanou hmotnos\u0165ou.<\/li>\n<li><b>URI<\/b> \u2013 \u013eav\u00e1 \u010das\u0165 URI (pred ot\u00e1znikom) sa hash-uje a del\u00ed na celkov\u00fa hmotnos\u0165 serverov v poole. V\u00fdsledok ur\u010duje, ktor\u00fd server dost\u00e1va po\u017eiadavku, pri\u010dom zaru\u010duje, \u017ee po\u017eiadavka sa v\u017edy smeruje na ten ist\u00fd server, pokia\u013e v\u0161etky servery zost\u00e1vaj\u00fa dostupn\u00e9.<\/li>\n<li><b>HTTPHEADER <\/b>\u2013 vyva\u017eovanie na z\u00e1klade ur\u010dit\u00e9ho HTTP hlavi\u010dky, ktor\u00fa je mo\u017en\u00e9 uvies\u0165 ako parameter. Ak hlavi\u010dka ch\u00fdba alebo nem\u00e1 hodnotu, aplikuje sa algoritmus ROUND_ROBIN.<\/li>\n<li><b>URL <\/b>\u2013 v ka\u017edej HTTP GET po\u017eiadavke sa h\u013ead\u00e1 pod\u013ea parametra URL, uv\u00e1dzan\u00e9ho ako argument. Ak za parametrom nasleduje znak rovnosti a hodnota, t\u00e1to hodnota sa hash-uje a del\u00ed na celkov\u00fa hmotnos\u0165 be\u017eiacich serverov. V\u00fdsledok ur\u010duje, ktor\u00fd server dost\u00e1va po\u017eiadavku. Tento proces sa pou\u017e\u00edva na sledovanie identifik\u00e1torov pou\u017e\u00edvate\u013eov v po\u017eiadavk\u00e1ch a zabezpe\u010duje, aby rovnak\u00fd user id v\u017edy putoval na ten ist\u00fd server, pokia\u013e v\u0161etky servery zost\u00e1vaj\u00fa dostupn\u00e9.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/ab98325a49a63d1d005839a47af39544.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>V bloku Members klikneme na +, aby sme pridali servery do poolu.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/f67e7567c48a6403bb5dcd165d150052.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTu je potrebn\u00e9 uvies\u0165:<\/p>\n<ul>\n<li>n\u00e1zov servera;<\/li>\n<li>IP adresa servera;<\/li>\n<li>port, na ktor\u00fd server bude prij\u00edma\u0165 trafic;<\/li>\n<li>port pre health check (Monitor healthcheck); <\/li>\n<li>hmotnos\u0165 (Weight) \u2013 pomocou tohto parametra m\u00f4\u017eeme regulova\u0165 proporcion\u00e1lne mno\u017estvo prij\u00edman\u00e9ho trafficu pre konkr\u00e9tneho \u010dlena poolu;<\/li>\n<li>Max Connections \u2013 maxim\u00e1lny po\u010det spojen\u00ed k serveru;<\/li>\n<li>Min Connections \u2013 minim\u00e1lny po\u010det spojen\u00ed, ktor\u00fd mus\u00ed server spracova\u0165, sk\u00f4r ako sa traffic presmeruje na nasleduj\u00faceho \u010dlena poolu.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/4bfd6de65e50cb417845d358b11b91b5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTakto vyzer\u00e1 kone\u010dn\u00fd pool z troch serverov.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/42ebe47da99599628d9e6e75289a9f25.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Prid\u00e1vame virtu\u00e1lny server<\/b><\/p>\n<ol>\n<li>Prejdeme na kartu Virtu\u00e1lne servery. Klikneme na +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/4d95be098f50055d81f538ebe565cfbb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Aktivujeme virtu\u00e1lny server pomocou Enable Virtual Server.<br \/>\nZad\u00e1me mu meno, vyberieme predt\u00fdm vytvoren\u00e9 aplik\u00e1cie profily, pool a uvedieme IP adresu, na ktor\u00fa bude virtu\u00e1lny server prij\u00edma\u0165 po\u017eiadavky zvonka. Uvedieme protokol HTTPS a port 443.<br \/>\nVolite\u013en\u00e9 parametre tu s\u00fa:<br \/>\n<b>Limit pripojen\u00ed <\/b>\u2013 maxim\u00e1lny po\u010det s\u00fa\u010dasn\u00fdch pripojen\u00ed, ktor\u00e9 m\u00f4\u017ee spracova\u0165 virtu\u00e1lny server;<br \/>\n<b>Limit r\u00fdchlosti pripojen\u00ed (CPS)<\/b> \u2013 maxim\u00e1lny po\u010det nov\u00fdch prich\u00e1dzaj\u00facich po\u017eiadaviek za sekundu.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/fae8dff378af917a96b9a7d887bb2bd8.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>T\u00fdmto sa konfigur\u00e1cia vyva\u017eova\u010da dokon\u010dila, m\u00f4\u017eeme skontrolova\u0165 jeho funk\u010dnos\u0165. Servery maj\u00fa najjednoduch\u0161iu konfigur\u00e1ciu, ktor\u00e1 umo\u017e\u0148uje pochopi\u0165, ktor\u00fdm konkr\u00e9tnym serverom z poolu bola po\u017eiadavka spracovan\u00e1. Po\u010das nastavenia sme vybrali algoritmus vyva\u017eovania Round Robin a parameter Weight pre ka\u017ed\u00fd server je rovn\u00fd jednej, tak\u017ee ka\u017ed\u00e1 \u010fal\u0161ia po\u017eiadavka bude spracovan\u00e1 nasleduj\u00facim serverom z poolu.<br \/>\nZad\u00e1me do prehliada\u010da extern\u00fa adresu vyva\u017eova\u010da a vid\u00edme:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/e10d1c9eb14b42f4f6fc03a0d6f03013.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPo obnoven\u00ed str\u00e1nky bude po\u017eiadavka spracovan\u00e1 nasleduj\u00facim serverom:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/09a67549ca2f05f835a2d4645779bfa1.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA e\u0161te raz \u2013 aby sme skontrolovali aj tret\u00ed server z poolu:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/e0452323822ff0a3e02ff5bcee53bcdc.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPri kontrole m\u00f4\u017eeme vidie\u0165, \u017ee certifik\u00e1t, ktor\u00fd n\u00e1m posiela Edge, je ten ist\u00fd, ktor\u00fd sme generovali na za\u010diatku. <\/p>\n<p>Kontrola stavu vyva\u017eova\u010da z konzoly Edge gateway. Na to zadajte <b>show service loadbalancer pool<\/b>. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/10a7421dc6278ba2c721187bfeb076a9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Nastavujeme servisn\u00fd monitor na kontrolu stavu serverov v poole <\/b><br \/>\nS pomocou servisn\u00e9ho monitora m\u00f4\u017eeme sledova\u0165 stav serverov v backend poole. Ak odpove\u010f na po\u017eiadavku nezodpoved\u00e1 o\u010dak\u00e1vanej, server m\u00f4\u017eeme vy\u0148a\u0165 z poolu, aby nedost\u00e1val \u017eiadne nov\u00e9 po\u017eiadavky.<br \/>\nPredvolene s\u00fa nakonfigurovan\u00e9 tri met\u00f3dy kontroly:<\/p>\n<ul>\n<li> TCP-monitor,<\/li>\n<li> HTTP-monitor,<\/li>\n<li> HTTPS-monitor.<\/li>\n<\/ul>\n<p>\nVytvor\u00edme nov\u00fd. <\/p>\n<ol>\n<li>Prejdeme na kartu Service Monitoring, klikneme na +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/ceac4fac8197b395d7531391534ad4ff.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vyberieme:\n<ul>\n<li>meno pre nov\u00fa met\u00f3du;<\/li>\n<li>interval, s ktor\u00fdm bud\u00fa odosielan\u00e9 po\u017eiadavky, <\/li>\n<li>timeout na \u010dakanie na odpove\u010f, <\/li>\n<li>typ monitorovania \u2013 HTTPS request s pou\u017eit\u00edm met\u00f3dy GET, o\u010dak\u00e1van\u00fd status code \u2013 200(OK) a URL po\u017eiadavky.<\/li>\n<\/ul>\n<\/li>\n<li>T\u00fdmto sa nastavenie nov\u00e9ho servisn\u00e9ho monitora skon\u010dilo, teraz ho m\u00f4\u017eeme pou\u017ei\u0165 pri vytv\u00e1ran\u00ed poolu. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/9db2263d6e5c90e1a5aba6cee865fd50.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Nastavujeme aplika\u010dn\u00e9 pravidl\u00e1<\/b><\/p>\n<p>Aplika\u010dn\u00e9 pravidl\u00e1 \u2013 sp\u00f4sob manipul\u00e1cie s prenosom, zalo\u017een\u00fd na ur\u010dit\u00fdch sp\u00fa\u0161\u0165a\u010doch. Pomocou tohto n\u00e1stroja m\u00f4\u017eeme vytv\u00e1ra\u0165 roz\u0161\u00edren\u00e9 pravidl\u00e1 na vyva\u017eovanie z\u00e1\u0165a\u017ee, ktor\u00fdch nastavenie m\u00f4\u017ee by\u0165 nemo\u017en\u00e9 prostredn\u00edctvom aplika\u010dn\u00fdch profilov alebo in\u00fdch slu\u017eieb dostupn\u00fdch na Edge Gateway.<\/p>\n<ol>\n<li>Prejdite na kartu Application Rules vyrovn\u00e1va\u010da za za\u0165a\u017eenie na vytvorenie pravidla.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/b370858e444c144c95fe0d89d3ea42da.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vyberte n\u00e1zov, skript, ktor\u00fd bude pravidlo pou\u017e\u00edva\u0165, a kliknite na Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/e0af1a95fb5b5bba46a52e582eba62bb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Po vytvoren\u00ed pravidla je potrebn\u00e9 upravi\u0165 u\u017e nastaven\u00fd Virtual Server.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/c4617150f17e8e16cde94a9c3fb8e713.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Na karte Advanced prid\u00e1me vytvoren\u00e9 pravidlo.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da z\u00e1\u0165a\u017ee\" src=\"\/wp-content\/uploads\/2019\/04\/23f4ed5bb90bf178fec825e552fba8a6.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>V uvedenom pr\u00edklade sme zapli podporu tlsv1.<\/p>\n<p>E\u0161te p\u00e1r pr\u00edkladov:<\/p>\n<p>Presmerovanie prev\u00e1dzky do in\u00e9ho poolu.<br \/>\nS t\u00fdmto skriptom m\u00f4\u017eeme presmerova\u0165 prev\u00e1dzku do in\u00e9ho vyrovn\u00e1vacieho poolu, ak hlavn\u00fd pool nefunguje. Aby pravidlo fungovalo, na vyrovn\u00e1va\u010di za\u0165a\u017eenia musia by\u0165 nakonfigurovan\u00e9 viacer\u00e9 pooly a v\u0161etky \u010dleny hlavn\u00e9ho poolu musia by\u0165 v stave down. Je potrebn\u00e9 uvies\u0165 presne n\u00e1zov poolu, nie jeho ID.<\/p>\n<p><code>acl pool_down nbsrv(PRIMARY_POOL_NAME) eq 0<br \/>\nuse_backend SECONDARY_POOL_NAME if PRIMARY_POOL_NAME<br \/>\n<\/code><\/p>\n<p>Presmerovanie prev\u00e1dzky na extern\u00fd zdroj.<br \/>\nTu presmerov\u00e1vame prev\u00e1dzku na extern\u00fa webov\u00fa str\u00e1nku, ak s\u00fa v\u0161etci \u00fa\u010dastn\u00edci hlavn\u00e9ho poolu v stave down.<\/p>\n<p><code>acl pool_down nbsrv(NAME_OF_POOL) eq 0<br \/>\nredirect location http:\/\/www.example.com if pool_down<\/code><\/p>\n<p>E\u0161te viac pr\u00edkladov <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.vmware.com\/en\/VMware-NSX-Data-Center-for-vSphere\/6.3\/com.vmware.nsx.admin.doc\/GUID-A5779D43-AC0F-4407-AF4A-0C1622394452.html\">tu<\/a><\/noindex>.<\/p>\n<p>T\u00fdmto oh\u013eadom m\u00e1m k vyrovn\u00e1va\u010du v\u0161etko. Ak m\u00e1te nejak\u00e9 ot\u00e1zky, sp\u00fdtajte sa, som pripraven\u00fd odpoveda\u0165.<br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/448540\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0427\u0430\u0441\u0442\u044c \u043f\u0435\u0440\u0432\u0430\u044f. \u0412\u0432\u043e\u0434\u043d\u0430\u044f \u0427\u0430\u0441\u0442\u044c \u0432\u0442\u043e\u0440\u0430\u044f. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u043f\u0440\u0430\u0432\u0438\u043b Firewall \u0438 NAT \u0427\u0430\u0441\u0442\u044c \u0442\u0440\u0435\u0442\u044c\u044f. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 DHCP \u0427\u0430\u0441\u0442\u044c \u0447\u0435\u0442\u0432\u0435\u0440\u0442\u0430\u044f. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0439 \u0440\u0430\u0437 \u043c\u044b \u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438 \u043e \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044f\u0445 NSX Edge \u0432 \u0440\u0430\u0437\u0440\u0435\u0437\u0435 \u0441\u0442\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0438 \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438, \u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u0431\u0443\u0434\u0435\u043c \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\u0441\u044f \u0441 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u043e\u043c. \u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u0442\u044c \u043a \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0435, \u044f \u0445\u043e\u0442\u0435\u043b \u0431\u044b \u0441\u043e\u0432\u0441\u0435\u043c \u043a\u0440\u0430\u0442\u043a\u043e \u043d\u0430\u043f\u043e\u043c\u043d\u0438\u0442\u044c \u043e\u0431 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u0445 \u0432\u0438\u0434\u0430\u0445 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0438. \u0422\u0435\u043e\u0440\u0438\u044f [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23693,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31817","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.3 - aioseo.com -->\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\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\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\udd47VMware NSX \u0434\u043b\u044f \u0441\u0430\u043c\u044b\u0445 \u043c\u0430\u043b\u0435\u043d\u044c\u043a\u0438\u0445. \u0427\u0430\u0441\u0442\u044c 5. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki\" \/>\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:43:19+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:43:19+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\udd47VMware NSX pre najmen\u0161\u00edch. \u010cas\u0165 5. Nastavenie vyrovn\u00e1va\u010da za\u0165a\u017eenia | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","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\udd47VMware NSX \u0434\u043b\u044f \u0441\u0430\u043c\u044b\u0445 \u043c\u0430\u043b\u0435\u043d\u044c\u043a\u0438\u0445. \u0427\u0430\u0441\u0442\u044c 5. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 | ProHoster","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","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:43:19+00:00","article:modified_time":"2019-10-31T18:43:19+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31817","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 07:58:25","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:10:46","updated":"2026-01-21 07:58:25","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\/31817","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=31817"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/31817\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/23693"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=31817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=31817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=31817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}