{"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\/et\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","title":{"rendered":"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" 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\/\">Esimene osa. Sissejuhatus<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441026\/\">Teine osa. Firewalli ja NAT-i reeglite seadistamine<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441882\/\">Kolmas osa. DHCP seadistamine<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/444644\/\">Neljas osa. Suunamise seadistamine<\/a><\/noindex><\/p>\n<p>Eelmisel korral r\u00e4\u00e4kisime NSX Edge'i v\u00f5imalustest staatilise ja d\u00fcnaamilise marsruutimise osas, t\u00e4na aga uurime koormuse tasakaalustajat.<br \/>\nEnne seadistamise alustamist sooviksin l\u00fchidalt meenutada peamisi tasakaalustamise t\u00fc\u00fcpe. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Teooria<\/h3>\n<p>\nK\u00f5ik t\u00e4nap\u00e4eva koormuse tasakaalustamise lahendused jagunevad enamasti kaheks kategooriaks: tasakaalustamine neljandas (transport) ja seitsmendas (rakenduse) tasemes. <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>. OSI mudel ei ole parim viidatud punkt tasakaalustamismeetodite kirjeldamiseks. N\u00e4iteks, kui L4 tasakaalustaja toetab ka TLS-i l\u00f5petamist, kas ta muutub sel juhul L7 tasakaalustajaks? Aga mis seal siis ikka.<\/p>\n<ul>\n<li><b>L4 tasakaalustaja <\/b>tavaliselt esindab vahekohtuniku s\u00fcsteemi, mis asub kliendi ja saadaolevate tagapoolsete vahel, l\u00f5petades TCP-\u00fchendused (st vastates iseseisvalt SYN-le), valib tagapoolse ja algatab tema suunas uue TCP-seansi, saates iseseisvalt SYN. See t\u00fc\u00fcp on \u00fcks p\u00f5hilisi, olemas on ka teisi variante.<\/li>\n<li><b>L7 tasakaalustaja<\/b> suunab liiklust saadaval olevate tagaplaanide vahel \u201ekeerukamalt\u201d kui L4- tasandi koormuse jaotur. See suudab tagaplaani valikute tegemisel arvestada n\u00e4iteks HTTP-s\u00f5numi sisu (URL, k\u00fcpsis jne).<\/li>\n<\/ul>\n<p>\nOlenemata t\u00fc\u00fcbist, koormuse jaotur v\u00f5ib toetada j\u00e4rgmisi funktsioone:<\/p>\n<ul>\n<li> Teenuste avastamine \u2013 protsess saadaval olevate tagaplaanide (Static, DNS, Consul, Etcd jne) m\u00e4\u00e4ramiseks.<\/li>\n<li>Avastatud tagaplaanide t\u00f6\u00f6kontroll (aktiivne \u201eping\u201d HTTP-p\u00e4ringu abil, probleemide passiivne avastamine TCP-\u00fchendustes, mitu j\u00e4rjestikust 503 HTTP-koodi vastustes jne).<\/li>\n<li>Koormuse jaotamine (ringikujuline, juhuslik valik, allika IP-hashing, URI).<\/li>\n<li>TLS-i l\u00f5petamine ja sertifikaatide valideerimine.<\/li>\n<li>Turvalisuse tagamisega seotud valikud (autentimine, DoS-r\u00fcnnakute ennetamine, kiiruspiirang) ja palju muud.<\/li>\n<\/ul>\n<p>\nNSX Edge pakub toetust kaheks koormuse jaoturi juurutamise re\u017eiimiks:<\/p>\n<p><b>Proxire\u017eiim, ehk one-arm<\/b>. Selles re\u017eiimis kasutab NSX Edge p\u00e4ringu saatmisel \u00fchele tagasuunamisdestinaatorist IP-aadressi allika aadressina. Seega t\u00e4idab tasakaalustaja samaaegselt nii Source kui ka Destination NAT funktsioone. Tagasuunamisdestinaator n\u00e4eb kogu liiklust kui tasakaalustajalt saadetud ja vastab sellele otse. Sellises skeemis peab tasakaalustaja olema samas v\u00f5rgu segmendis sisemiste serveritega.<\/p>\n<p>Nii see toimub:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Kasutaja saadab p\u00e4ringu VIP-aadressile (tasakaalustaja aadress), mis on konfigureeritud Edge'il.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge valib \u00fche tagasuunamisdestinaatoritest ja teostab sihtkoha NAT, asendades VIP-aadressi valitud tagasuunamisdestinaatori aadressiga.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge teostab allika NAT, asendades p\u00e4ringu saatva kasutaja aadressi oma enda aadressiga.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Pakett saadetakse valitud tagasuunamisdestinaatorile.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Tagasuunamisdestinaator ei vasta otse kasutajale, vaid Edge'ile, kuna algne kasutaja aadress oli muudetud tasakaalustaja aadressiks.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge edastab serveri vastuse kasutajale.<br \/>\nAllolev skeem.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/a6073ec63f7aca05d61c5a40de2ba6be.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>L\u00e4bipaistev v\u00f5i inline re\u017eiim.<\/b> Selles stsenaariumis on koormuse tasakaalustajal liideseid nii sise- kui ka v\u00e4lisv\u00f5rgus. V\u00e4lisest v\u00f5rgust ei ole sisev\u00f5rku otsesele ligip\u00e4\u00e4sule.<\/p>\n<p>Mehanism on j\u00e4rgmine:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Kasutaja saadab p\u00e4ringu VIP-aadressile (tasakaalustaja aadress), mis on konfigureeritud Edge'il.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge valib \u00fche tagasuunamisdestinaatoritest ja teostab sihtkoha NAT, asendades VIP-aadressi valitud tagasuunamisdestinaatori aadressiga.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Paket saadetakse valitud taustteenusele.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Taustteenus saab p\u00e4ringu kasutaja algse aadressiga (source NAT ei ole teostatud) ja vastab sellele otse.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Liiklus v\u00f5etakse taas vastu koormuse tasakaalustaja poolt, kuna inline skeemis toimib see tavaliselt serverifarmi vaikev\u00e4ravana.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge teostab source NAT, et saata liiklust kasutajale, kasutades oma VIP-d source IP-aadressina.<br \/>\nAllolev skeem.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/9ad9adcac02d40db1603aee84387264a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Praktika<\/h3>\n<p>\nMinu testimise keskuses on seadistatud 3 serverit, mille Apache on konfigureeritud t\u00f6\u00f6tama HTTPS-iga. Edge teostab HTTPS-p\u00e4ringute koormuse tasakaalustamist round robin meetodiga, edastades iga uue p\u00e4ringu uuele serverile.<br \/>\nAlustame.<\/p>\n<p><b>Genereerime SSL-sertifikaadi, mida kasutab NSX Edge.<\/b><br \/>\nSaate importida kehtiva CA-sertifikaadi v\u00f5i kasutada iseenese allkirjastatud sertifikaati. Selles testis kasutan iseenese allkirjastatud sertifikaati.<\/p>\n<ol>\n<li>vCloud Director'i liideses liigume Edge teenuste seadete juurde.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/df9be9f6d5b92af1cbe19f40459c8d9f.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Liigume sertifikaatide vahekaardile. Tegevuste loendist valime uue CSR lisamise.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/72185bf69cb0c4d8dc0cbadc8fe4f376.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>T\u00e4idame vajalikud v\u00e4ljad ja vajutame Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/196394d4633d76dfde6d89b8f7049e19.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Valime just loodud CSR-i ja valime valiku self-sign CSR.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/262e7a1ede8bda39a9ee098f360a38e3.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Valime sertifikaadi kehtivusaja ja vajutame Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/6c880218fd7874652e6540a0bde18310.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Enesepoolt allkirjastatud sertifikaat ilmus saadavalolevate hulka.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/f065f461da8f96ca31c96d3c801350ec.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Seame Application Profile'i.<\/b><br \/>\nRakendusprofiilid annavad t\u00e4ieliku kontrolli v\u00f5rgu liikluse \u00fcle ning muudavad selle haldamise lihtsaks ja t\u00f5husaks. Nende abil saab m\u00e4\u00e4rata k\u00e4itumise konkreetsetele liiklust\u00fc\u00fcpidele. <\/p>\n<ol>\n<li>Liigume Load Balancer'i vahekaardile ja aktiveerime tasakaalustamise. Valik Acceleration enabled aitab tasakaalustajal kasutada kiiremaks L4 tasakaalustamist L7 asemel.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/1ee064e2fe234fb1d96ec327f3f92f05.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Liigume rakendusprofiili vahekaardile, et m\u00e4\u00e4rata rakendusprofiil. Vajutage +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/5686a86bdff4d973f33f1a9d362ad273.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>M\u00e4\u00e4rame profiili nime ja valime liikluse t\u00fc\u00fcbi, millele profiil kehtib. Selgitan m\u00f5ningaid parameetreid.<br \/>\n<b>Persistence<\/b> \u2013 salvestab ja j\u00e4lgib sessiooni andmeid, n\u00e4iteks: milline konkreetne server teenindab kasutaja p\u00e4ringut. See tagab, et kasutaja p\u00e4ringud suunatakse kogu sessiooni v\u00f5i j\u00e4rgmiste sessioonide v\u00e4ltel sama grupi liikme juurde.<br \/>\n<b>Luba SSL'i edasiviimine<\/b> \u2013 kui see valik on valitud, NSX Edge enam SSL'i ei termineeri. Selle asemel toimub termineerimine otse serverites, millele toimub koormuse jaotamine.<br \/>\n<b>Sisesta X-Forwarded-For HTTP p\u00e4is<\/b> \u2013 v\u00f5imaldab m\u00e4\u00e4rata kliendi algse IP-aadressi, kes \u00fchendub veebiserveriga koormuse jaotaja kaudu.<br \/>\n<b>Luba r\u00fchma poolne SSL<\/b> \u2013 v\u00f5imaldab m\u00e4\u00e4rata, et valitud r\u00fchm koosneb HTTPS-serveritest.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/81fa688f063f5cf1719461884bbb8dc2.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Kuna ma balanseerin HTTPS-liiklust, tuleb lubada r\u00fchma poolne SSL ja valida eelnevalt genereeritud sertifikaat vahekaardilt Virtuaalserveri Sertifikaadid \u2014&gt; Teenuse Sertifikaat.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/d2585bcc33e57adc561bc5d956057479.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Sama kehtib ka r\u00fchma Sertifikaatide \u2014&gt; Teenuse Sertifikaadi kohta.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/b565acf03e4eba313b4624a912310663.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Loome serverite r\u00fchma, millele liiklus jaotatakse<\/b><\/p>\n<ol>\n<li>Liigume vahekaardile R\u00fchmad. Kl\u00f5psame +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/e3fd9f747f3cbc43f3d348c05ece07fd.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>M\u00e4\u00e4rame partii nime, valime algoritmi (kasutan ringjuhitust) ja j\u00e4lgimise t\u00fc\u00fcbi b\u00e4nneri tervisekontrolli jaoks. Valik Transparent n\u00e4itab, kas algsed kliendi allika IP-d on n\u00e4htavad sisemistele serveritele.\n<ul>\n<li>Kui valik on keelatud, siis sisemistele serveritele edastatav liiklus tuleb tasakaalustajast allika IP-ga.\n<\/li>\n<li> Kui valik on lubatud, n\u00e4evad sisemised serverid klientide allika IP-d. Sellise konfiguratsiooni puhul peab NSX Edge olema vaikimisi v\u00e4rav, et tagada tagasisaadetavate pakettide l\u00e4bimine NSX Edge'ist.<\/li>\n<\/ul>\n<p>NSX toetab j\u00e4rgmisi tasakaalustamisalgorithme:<\/p>\n<ul>\n<li><b>IP_HASH<\/b> \u2013 serveri valik p\u00f5hineb hash-funktsiooni tulemuste alusel iga paketi allika ja siht-IP jaoks.<\/li>\n<li> <b>LEASTCONN <\/b>\u2013 sisenemisseoste tasakaalustamine s\u00f5ltub juba olemasolevate seoste arvust konkreetses serveris. Uued seosed suunatakse serverisse, kus on k\u00f5ige v\u00e4hem seoseid.<\/li>\n<li> <b>ROUND_ROBIN <\/b>\u2013 uued seosed saadetakse vaheldumisi igasse serverisse vastavalt m\u00e4\u00e4ratud kaalule.<\/li>\n<li><b>URI<\/b> \u2013 URI vasak osa (kuni k\u00fcsim\u00e4rgini) on h\u00e4\u00e4lestatud ja jagatud serverite kogukaaluga. Tulemuseks on see, milline server saab p\u00e4ringu, tagades, et p\u00e4ring suunatakse alati \u00fchte ja samasse serverisse, kuni k\u00f5ik serverid on endiselt k\u00e4ttesaadavad.<\/li>\n<li><b>HTTPHEADER <\/b>\u2013 tasakaalustamine p\u00f5hineb kindlal HTTP-pealkirjal, mida saab m\u00e4\u00e4rata parameetrina. Kui pealkiri puudub v\u00f5i ei oma mingit v\u00e4\u00e4rtust, rakendatakse ROUND_ROBIN algoritmi.<\/li>\n<li><b>URL <\/b>\u2013 igas HTTP GET p\u00e4ringus otsib URL-i parameetrit, mis on m\u00e4\u00e4ratud argumendina. Kui parameetrile j\u00e4rgneb v\u00f5rdusm\u00e4rk ja v\u00e4\u00e4rtus, siis v\u00e4\u00e4rtus h\u00e4\u00e4lestatakse ja jagatakse k\u00e4ivitatud serverite kogukaaluga. Tulemuseks on see, milline server saab p\u00e4ringu. Seda protsessi kasutatakse kasutaja ID-de j\u00e4lgimiseks p\u00e4ringutes ja tagamiseks, et sama kasutaja ID saadetakse alati \u00fchte ja samasse serverisse, kuni k\u00f5ik serverid on endiselt k\u00e4ttesaadavad.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/ab98325a49a63d1d005839a47af39544.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Liikmete blokis vajutage +, et lisada serverid puuli.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/f67e7567c48a6403bb5dcd165d150052.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n1. Elasticsearch serveri aadress (seatakse installimise ajal).<\/p>\n<ul>\n<li>serveri nimi;<\/li>\n<li>serveri IP-aadress;<\/li>\n<li>port, kuhu server saab liiklust;<\/li>\n<li>health check'i port (Monitor healthcheck); <\/li>\n<li>kaal (Weight) \u2013 selle parameetri abil saab reguleerida konkreetse basseini liikme jaoks saadud liikluse proportsionaalset hulka;<\/li>\n<li>Max Connections \u2013 maksimaalne \u00fchenduste arv serverisse;<\/li>\n<li>Min Connections \u2013 minimaalne \u00fchenduste arv, mida server peab t\u00f6\u00f6tlema, enne kui liiklus suunatakse j\u00e4rgmisele basseini liikmele.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/4bfd6de65e50cb417845d358b11b91b5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNii n\u00e4eb v\u00e4lja l\u00f5ppbassein kolmest serverist.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/42ebe47da99599628d9e6e75289a9f25.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Lisame Virtuaalse Serveri<\/b><\/p>\n<ol>\n<li>Liigume Virtuaalsete Serverite vahekaardile. Vajutame +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/4d95be098f50055d81f538ebe565cfbb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Aktiveerime virtuaalse serveri, kasutades Enable Virtual Server.<br \/>\nM\u00e4\u00e4rame nime, valime varem loodud Rakenduse Profiili, Basseini ja n\u00e4itame IP-aadressi, kuhu Virtuaalne Server v\u00e4ljastpoolt p\u00e4ringuid vastu v\u00f5tab. Valime protokolliks HTTPS ja pordiks 443.<br \/>\nSiin on valikulised parameetrid:<br \/>\n<b>Connection Limit <\/b>\u2013 maksimaalne arv samaaegseid \u00fchendusi, mida virtuaalne server suudab t\u00f6\u00f6delda;<br \/>\n<b>Connection Rate Limit (CPS)<\/b> \u2013 maksimaalne arv uusi sissetulevaid p\u00e4ringuid sekundis.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/fae8dff378af917a96b9a7d887bb2bd8.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>Selle konfiguratsiooni koormuse jaotaja l\u00f5petamine on n\u00fc\u00fcdseks tehtud ja saab kontrollida selle t\u00f6\u00f6d. Serveritel on lihtne konfiguratsioon, mis v\u00f5imaldab m\u00f5ista, milline server grupist on p\u00e4ringut t\u00f6\u00f6tlenud. Seadistuse k\u00e4igus valisime Round Robin tasakaalustamismeetodi ja iga serveri kaal on \u00fcks, seega t\u00f6\u00f6deldakse iga j\u00e4rgmine p\u00e4ring j\u00e4rgmise serveri poolt grupist.<br \/>\nSisestame brauserisse koormuse jaotaja v\u00e4lise aadressi ja n\u00e4eme:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/e10d1c9eb14b42f4f6fc03a0d6f03013.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP\u00e4rast lehe uuendamist t\u00f6\u00f6deldakse p\u00e4ring j\u00e4rgmise serveri poolt:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/09a67549ca2f05f835a2d4645779bfa1.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nJa veel kord \u2013 et kontrollida ka kolmandat serverit grupist:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/e0452323822ff0a3e02ff5bcee53bcdc.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKontrollimisel on n\u00e4ha, et sertifikaat, mille Edge meile saadab, on just see, mille genereerisime alguses. <\/p>\n<p>Kontrollige koormuse jaotaja staatust Edge gateway konsoolist. Selleks sisestage <b>show service loadbalancer pool<\/b>. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/10a7421dc6278ba2c721187bfeb076a9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Seadistame teenuse monitori serverite seisundi kontrollimiseks grupis <\/b><br \/>\nTeenuse monitori abil saame j\u00e4lgida serverite seisundit tagapool grupis. Kui p\u00e4ringu vastus ei vasta ootusele, saab serveri grupist eemaldada, et see ei saaks uusi p\u00e4ringuid.<br \/>\nVaikimisi on seadistatud kolm kontrollimise meetodit:<\/p>\n<ul>\n<li> TCP-monitor,<\/li>\n<li> HTTP-monitor,<\/li>\n<li> HTTPS-monitor.<\/li>\n<\/ul>\n<p>\nLoome uus. <\/p>\n<ol>\n<li>Liigume jaotisse Service Monitoring, kl\u00f5psame +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/ceac4fac8197b395d7531391534ad4ff.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Valime:\n<ul>\n<li>uue meetodi nime;<\/li>\n<li>intervall, millega p\u00e4ringud saadetakse, <\/li>\n<li>ootamise aja piirang, <\/li>\n<li>monitooringu t\u00fc\u00fcp \u2013 HTTPS p\u00e4ring, kasutades meetodit GET, oodatav staatuse kood \u2013 200 (OK) ja p\u00e4ringu URL.<\/li>\n<\/ul>\n<\/li>\n<li>Sellega on uue Service Monitori seadistamine l\u00f5petatud, n\u00fc\u00fcd saame seda kasutada puu loomisel. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/9db2263d6e5c90e1a5aba6cee865fd50.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Seame Application Rules<\/b><\/p>\n<p>Application Rules \u2013 liikluse k\u00e4sitlemise meetod, mis p\u00f5hineb teatud vallandajatel. Selle t\u00f6\u00f6riistaga saame luua t\u00e4iustatud koormuse tasakaalustamise reegleid, mille seadistamine v\u00f5ib olla v\u00f5imatu l\u00e4bi Application profiles v\u00f5i teiste teenuste, mis on saadaval Edge Gatewayl.<\/p>\n<ol>\n<li>Reegli loomiseks liigume koormuse tasakaalustaja jaotisse Application Rules.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/b370858e444c144c95fe0d89d3ea42da.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Valime nime, skripti, mis reeglit kasutab, ja kl\u00f5psame Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/e0af1a95fb5b5bba46a52e582eba62bb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>P\u00e4rast reegli loomist peame redigeerima juba seadistatud Virtual Serverit.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/c4617150f17e8e16cde94a9c3fb8e713.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Jaotises Advanced lisame meie loodud reegli.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalustaja seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/23f4ed5bb90bf178fec825e552fba8a6.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>\u00dclaltoodud n\u00e4ites aktiveerisime tlsv1 toe.<\/p>\n<p>Veel m\u00f5ned n\u00e4ited:<\/p>\n<p>Liikluse suunamine teise puusse.<br \/>\nSelle skripti abil saame suunata liiklust teise tasakaalustusgruppi, kui p\u00f5higrupp ei toimi. Et reegel rakenduks, peab tasakaalustajal olema konfigureeritud mitu gruppi ja k\u00f5ik p\u00f5higrupi liikmed peavad olema seisundis 'down'. Tuleb n\u00e4idata just grupi nime, mitte selle ID-d.<\/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>Liikluse \u00fcmber suunamine v\u00e4listesse allikatesse.<br \/>\nSiin suuname liikluse v\u00e4lish veebisaidile, kui k\u00f5ik p\u00f5higrupi osalised on seisundis '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>Veel rohkem n\u00e4iteid <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\">siin<\/a><\/noindex>.<\/p>\n<p>Sellega on tasakaalustaja teemad kaetud. Kui on k\u00fcsimusi, k\u00fcsige, vastan meeleldi.<br \/>\n<br \/>Allikas: <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 4.9.10 - aioseo.com -->\n\t<meta name=\"description\" content=\"\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\" \/>\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\/et\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\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:description\" content=\"\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\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/et\/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 k\u00f5ige v\u00e4iksematele. Osa 5. Koormuse tasakaalu seadistamine | ProHoster","description":"Esimene osa. Sissejuhatus Teine osa. Firewalli ja NAT-i reeglite seadistamine Kolmas osa. DHCP seadistamine Neljas osa. Suunamise seadistamine Eelmisel korral r\u00e4\u00e4kisime NSX Edge v\u00f5imalustest staatilise ja d\u00fcnaamilise suunamise osas ning t\u00e4na k\u00e4sitleme tasakaalustajat. Enne seadistamise alustamist tahaksin v\u00e4ga l\u00fchidalt meenutada p\u00f5hivorme tasakaalustamisest. Teooria","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","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:description":"\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","og:url":"https:\/\/prohoster.info\/et\/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"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/31817","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=31817"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/31817\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/23693"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=31817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=31817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=31817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}