{"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. Laadimisseadmise seadistamine","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise 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. Firewali 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. Mar\u0161rutimise seadistamine<\/a><\/noindex><\/p>\n<p>Eelmises osas r\u00e4\u00e4kisime NSX Edge'i v\u00f5imetest staatilise ja d\u00fcnaamilise mar\u0161rutimise kontekstis ning t\u00e4na uurime koormuse tasakaalustajat.<br \/>\nEnne seadistamise alustamist tahaksin l\u00fchidalt meenutada peamisi koormuse tasakaalustamise t\u00fc\u00fcpe. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Teooria<\/h3>\n<p>\nPraegused koormuse tasakaalustamise lahendused jagunevad tavaliselt kaheks kategooriaks: koormuse tasakaalustamine neljandal (transport) ja seitsmendal (rakendus) tasemel mudelis. <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 juhtpunkt tasakaalustamismeetodite kirjeldamiseks. N\u00e4iteks, kui L4 koormuse tasakaalustaja toetab ka TLS-i l\u00f5petamist, kas siis muutub see L7 tasakaalustajaks? Aga mis on, see on.<\/p>\n<ul>\n<li><b>L4 koormuse tasakaalustaja <\/b>on k\u00f5ige sagedamini vaheline proxy, mis asub kliendi ja kavaliteetide tagumise kogumi vahel ning l\u00f5petab TCP-\u00fchendused (st vastab SYN-ile), valib tagumise serveri ja algatab temaga uue TCP-seansi, saates iseseisvalt SYN-i. See t\u00fc\u00fcp on \u00fcks alusteist, kuid v\u00f5imalused pole piiratud.<\/li>\n<li><b>L7 koormuse tasakaalustaja<\/b> jagab liiklust kavaliteetide vahel \u201epeenemalt\u201c kui L4 koormuse tasakaalustaja. See v\u00f5ib tagumise serveri valimise otsuse langetada nt HTTP s\u00f5numi sisu (URL, k\u00fcpsised jne) p\u00f5hjal.<\/li>\n<\/ul>\n<p>\n\u00dcksk\u00f5ik millise t\u00fc\u00fcbi puhul v\u00f5ib koormuse tasakaalustaja toetada j\u00e4rgmisi funktsioone:<\/p>\n<ul>\n<li> Teenuste avastamine \u2013 protsess, millega m\u00e4\u00e4ratakse kindlaks kavaliteetide kogum (Static, DNS, Consul, Etcd jms).<\/li>\n<li>Leitud tagumise serveri t\u00f6\u00f6kindluse kontrollimine (aktiivne \u201epingimine\u201c HTTP-p\u00e4ringu kaudu, passiivne probleemide avastamine TCP-\u00fchendustes, j\u00e4rjestikuste 503 HTTP-koodide olemasolu vastustes jne).<\/li>\n<li>Ise koormuse tasakaalustamine (round robin, juhuslik valik, allika IP-hash, URI).<\/li>\n<li>TLS-i l\u00f5petamine ja sertifikaatide kontrollimine.<\/li>\n<li>Turvafunktsioonidega seotud v\u00f5imalused (autentimine, DoS-r\u00fcnnakute v\u00e4ltimine, kiiruspiirangud) ja palju muud.<\/li>\n<\/ul>\n<p>\nNSX Edge pakub koormuse tasakaalustaja kahe juurutamismoodi tuge:<\/p>\n<p><b>Proxy-re\u017eiim ehk one-arm<\/b>. Sellise re\u017eiimi puhul kasutab NSX Edge taotluse saatmisel \u00fche b\u00e4ndi IP-aadressi allika aadressina. Nii t\u00e4idab koormuse tasakaalustaja samaaegselt nii Allika kui Kahtluse NAT funktsioone. B\u00e4nd n\u00e4eb kogu liiklust kui saadetud koormuse tasakaalustajast ja vastab sellele otse. Sellisel skeemil peab koormuse tasakaalustaja olema samas v\u00f5rgusegmentis sisemiste serveritega.<\/p>\n<p>Nii see t\u00f6\u00f6tab:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Kasutaja esitab taotluse VIP-aadressile (koormuse tasakaalustaja aadress), mis on seadistatud Edge'ile.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge valib \u00fche b\u00e4ndidest ja teostab sihtkoha NAT, asendades VIP-aadressi valitud b\u00e4ndi aadressiga.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge teostab allika NAT, asendades taotluse saatnud kasutaja aadressi oma isiklikuga.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Pakett saadetakse valitud b\u00e4ndile.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0B\u00e4nd vastab mitte otse kasutajale, vaid Edge'ile, sest kasutaja algne aadress muudeti koormuse 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. Laadimisseadmise 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 liidesed sise- ja v\u00e4listesse v\u00f5rkudesse. Sisev\u00f5rgule ei ole otsest juurdep\u00e4\u00e4su v\u00e4lisest. Sisseehitatud koormuse tasakaalustaja toimib NAT gateway'na virtuaalmasinate jaoks sisev\u00f5rgus.<\/p>\n<p>Mehhanism on j\u00e4rgmine:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Kasutaja esitab taotluse VIP-aadressile (koormuse tasakaalustaja aadress), mis on seadistatud Edge'ile.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge valib \u00fche b\u00e4ndidest ja teostab sihtkoha NAT, asendades VIP-aadressi valitud b\u00e4ndi aadressiga.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Pakett saadetakse valitud b\u00e4ndile.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0B\u00e4nd saab taotluse originaali aadressiga (allika NAT'i ei teostatud) ja vastab sellele otse.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Liiklus v\u00f5etakse uuesti vastu koormuse tasakaalustaja poolt, kuna inline skeemis toimib see tavaliselt vaikimisi v\u00e4ravana serverite farmi jaoks.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge teostab allika NAT'i, et saata liiklus kasutajale, kasutades oma VIP-d allika IP-aadressina.<br \/>\nAllolev skeem.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise 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 testkeskkonnas on seadistatud 3 serverit Apache'iga, mis on seadistatud HTTPS-i t\u00f6\u00f6tamiseks. Edge teostab HTTPS-i taotluste tasakaalustamist round robin meetodiga, edastades iga uue taotluse uuele serverile.<br \/>\nHakkame pihta.<\/p>\n<p><b>K\u00fcpsetame SSL-sertifikaadi, mida NSX Edge kasutab<\/b><br \/>\nSaate importida kehtiva CA-sertifikaadi v\u00f5i kasutada isekirjutatud. Selles testis kasutan iseallkirjastatud sertifikaati.<\/p>\n<ol>\n<li>vCloud Director'i liidese kaudu liikuda Edge'i teenuste seadete juurde.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/df9be9f6d5b92af1cbe19f40459c8d9f.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Liigume Sertifikaadid vahelehele. Toimingute nimekirjast valige uue CSR-i lisamine.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/72185bf69cb0c4d8dc0cbadc8fe4f376.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>T\u00e4ida vajalikud v\u00e4ljad ja vajuta Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/196394d4633d76dfde6d89b8f7049e19.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vali just loodud CSR ja vali valik self-sign CSR.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/262e7a1ede8bda39a9ee098f360a38e3.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vali sertifikaadi kehtivusaeg ja vajuta Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/6c880218fd7874652e6540a0bde18310.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Isesigneeritud sertifikaat on ilmunud saadavalolevate hulka.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/f065f461da8f96ca31c96d3c801350ec.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Seadista Rakenduse Profiil.<\/b><br \/>\nRakenduse profiilid annavad suurema kontrolli v\u00f5rgu liikluse \u00fcle ja muudavad selle haldamise lihtsaks ja t\u00f5husaks. Nende abil on v\u00f5imalik m\u00e4\u00e4rata k\u00e4itumine konkreetse liikluse t\u00fc\u00fcbi jaoks. <\/p>\n<ol>\n<li>Minna Load Balancer vahelehele ja aktiveerida tasakaalustaja. Valik Acceleration enabled v\u00f5imaldab tasakaalustajal kasutada kiiremat L4 tasakaalustust L7 asemel.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/1ee064e2fe234fb1d96ec327f3f92f05.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Mine Rakenduse profiili vahelehele, et m\u00e4\u00e4rata rakenduse profiil. Vajuta +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/5686a86bdff4d973f33f1a9d362ad273.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>M\u00e4\u00e4rake profiili nimi ja valige liikluse t\u00fc\u00fcp, millele profiil rakendub. Selgitan m\u00f5ningaid parameetreid.<br \/>\n<b>Persistence<\/b> \u2013 salvestab ja j\u00e4lgib kasutusseansi andmeid, n\u00e4iteks: milline konkreetne server basseinist teenindab kasutaja p\u00e4ringut. See tagab, et kasutaja p\u00e4ringud suunatakse kogu seansi v\u00f5i j\u00e4rgnevate seansside v\u00e4ltel samasse basseiniliikmesse.<br \/>\n<b>Enable SSL passthrough<\/b> \u2013 kui see valik on valitud, NSX Edge l\u00f5petab SSL-i. Selle asemel toimub l\u00f5petamine otse serverites, millele tasakaalustamine toimub.<br \/>\n<b>Insert X-Forwarded-For HTTP header<\/b> \u2013 v\u00f5imaldab m\u00e4\u00e4rata kliendi algse IP-aadressi, kes \u00fchendub veebiserveriga tasakaalustaja kaudu.<br \/>\n<b>Enable Pool Side SSL<\/b> \u2013 v\u00f5imaldab m\u00e4rkida, et valitud bassein koosneb HTTPS-serveritest.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/81fa688f063f5cf1719461884bbb8dc2.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Kuna ma tasakaalustan HTTPS-liiklust, pean lubama Pool Side SSL-i ja valima varem genereeritud sertifikaadi Virtual Server Certificates vahelehelt \u2192 Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/d2585bcc33e57adc561bc5d956057479.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Sarnaselt Pool Certificates \u2192 Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/b565acf03e4eba313b4624a912310663.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Loome serverite basseini, mille juurde liiklus tasakaalustatakse Pools.<\/b><\/p>\n<ol>\n<li>Mine Pools vahelehele. Vajuta +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/e3fd9f747f3cbc43f3d348c05ece07fd.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>M\u00e4\u00e4rake basseini nimi, valige algoritm (kasutan round robin) ja tervisekontrolli t\u00fc\u00fcbi jaoks. Valik Transparent n\u00e4itab, kas kliendi algsed IP-d on sise-serverite jaoks n\u00e4htavad.\n<ul>\n<li>Kui valik on v\u00e4lja l\u00fclitatud, tuleb sise-serveritele liiklus tasakaalustaja algse IP-ga.\n<\/li>\n<li> Kui valik on sisse l\u00fclitatud, n\u00e4evad sise-serverid klientide algset IP-aadressi. Sellises konfiguratsioonis peab NSX Edge olema vaikimisi l\u00fchi\u00fchendus, et tagada, et tagastatud paketid l\u00e4hevad l\u00e4bi NSX Edge.<\/li>\n<\/ul>\n<p>NSX toetab j\u00e4rgmisi koormuse tasakaalustamise algoritme:<\/p>\n<ul>\n<li><b>IP_HASH<\/b> \u2013 serveri valik p\u00f5hineb hash-funktsiooni tulemustel, mis arvutatakse iga paketi source ja destination IP jaoks.<\/li>\n<li> <b>LEASTCONN <\/b>\u2013 sissetulevate \u00fchenduste tasakaalustamine, s\u00f5ltuvalt juba olemasolevate \u00fchenduste arvust konkreetses serveris. Uued \u00fchendused suunatakse serverisse, kus on k\u00f5ige v\u00e4hem \u00fchendusi.<\/li>\n<li> <b>ROUND_ROBIN <\/b>\u2013 uued \u00fchendused saadetakse iga serveri juurde j\u00e4rjestikku vastavalt m\u00e4\u00e4ratud kaalule.<\/li>\n<li><b>URI<\/b> \u2013 URI vasak pool (kuni k\u00fcsim\u00e4rkide) hashitakse ja jagatakse serverite kogukaalu j\u00e4rgi. Tulemuseks on see, milline server saab p\u00e4ringu, tagades, et p\u00e4ring saadetakse alati samasse serverisse, kuni k\u00f5ik serverid j\u00e4\u00e4vad k\u00e4ttesaadavaks.<\/li>\n<li><b>HTTPHEADER <\/b>\u2013 tasakaalustamine p\u00f5hineb kindlal HTTP p\u00e4isel, mida saab m\u00e4\u00e4rata parameetrina. Kui p\u00e4is puudub v\u00f5i ei oma mingit v\u00e4\u00e4rtust, rakendatakse algoritmi ROUND_ROBIN.<\/li>\n<li><b>URL <\/b>\u2013 igas HTTP GET p\u00e4ringus otsitakse URL-i parameetrit, mis on m\u00e4\u00e4ratud argumendiks. Kui parameetri j\u00e4rel on v\u00f5rdsuse m\u00e4rk ja v\u00e4\u00e4rtus, siis v\u00e4\u00e4rtus hashitakse ja jagatakse k\u00e4imasolevate serverite kogukaalu j\u00e4rgi. Tulemuseks on see, milline server saab p\u00e4ringu. Selle protsessi eesm\u00e4rk on j\u00e4lgida kasutaja id-d p\u00e4ringutes ja tagada, et sama kasutaja id saadetakse alati samasse serverisse, kuni k\u00f5ik serverid j\u00e4\u00e4vad k\u00e4ttesaadavaks.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/ab98325a49a63d1d005839a47af39544.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Members plokis vajuta +, et lisada serverid gruppi.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/f67e7567c48a6403bb5dcd165d150052.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSiia tuleb m\u00e4rkida:<\/p>\n<ul>\n<li>serveri nimi;<\/li>\n<li>serveri IP-aadress;<\/li>\n<li>port, millele server saab liiklust;<\/li>\n<li>port tervise kontrollimiseks (Monitor healthcheck); <\/li>\n<li>kaal (Weight) \u2013 selle parameetriga saab reguleerida koormuse jaotust konkreetse grupi liikme vahel;<\/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 grupi liikmed.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/4bfd6de65e50cb417845d358b11b91b5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNii n\u00e4eb v\u00e4lja l\u00f5plik grupp kolmest serverist.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise 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. Vaja on vajutada +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/4d95be098f50055d81f538ebe565cfbb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Aktiveerime virtuaalse serveri nuppu Enable Virtual Server.<br \/>\nAnname sellele nime, valime varasemalt loodud rakenduse profiili, bassein ja m\u00e4\u00e4rame IP-aadressi, kuhu Virtuaalne Server v\u00e4ljastpoolt p\u00e4ringud vastu v\u00f5tab. M\u00e4\u00e4ra protokoll HTTPS ja port 443.<br \/>\nValikulised parameetrid siin:<br \/>\n<b>\u00dchenduse limiit <\/b>\u2013 maksimaalne samal ajal avatud \u00fchenduste arv, mida virtuaalne server saab t\u00f6\u00f6delda;<br \/>\n<b>\u00dchenduse m\u00e4\u00e4ramise limiit (CPS)<\/b> \u2013 maksimaalne uute sissetulevate p\u00e4ringute arv sekundis.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/fae8dff378af917a96b9a7d887bb2bd8.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>Sellega on koormustasakaalu konfiguratsioon l\u00f5petatud, n\u00fc\u00fcd saab selle t\u00f6\u00f6kindlust kontrollida. Serveritel on k\u00f5ige lihtsam konfiguratsioon, mis v\u00f5imaldab m\u00f5ista, milline server basseinist p\u00e4ringu t\u00f6\u00f6tleb. Seadistamise ajal valisime koormuse jaotusmeetodiks Round Robin ning iga serveri kaal on \u00fcks, seega t\u00f6\u00f6deldakse iga j\u00e4rgmine p\u00e4ring j\u00e4rgmise serveri poolt basseinist.<br \/>\nSisestame brauserisse koormustasakaalu v\u00e4lise aadressi ja n\u00e4eme:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/e10d1c9eb14b42f4f6fc03a0d6f03013.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP\u00e4rast lehe v\u00e4rskendamist t\u00f6\u00f6deldakse p\u00e4ring j\u00e4rgmisel serveril:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise 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 basseinist:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise 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 me alguses genereerisime. <\/p>\n<p>Kontrollime koormustasakaalu staatust Edge gateway konsoolist. Selle jaoks sisestage <b>show service loadbalancer pool<\/b>. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/10a7421dc6278ba2c721187bfeb076a9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Seadistame teenuse seire koondamiseks serverite olekute kontrollimiseks basseinist <\/b><br \/>\nTeenuse seire abil saame j\u00e4lgida serverite olekuid tagapool seotud basseinides. Kui p\u00e4ringu vastus ei vasta oodatavale, saab serveri basseinist v\u00e4lja j\u00e4tta, et see ei saaks uusi p\u00e4ringuid.<br \/>\nVaikes\u00e4tetena 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 uue. <\/p>\n<ol>\n<li>Liigume teenuse seiramise vahekaardile, vajutame +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise 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, mille jooksul p\u00e4ringud saadetakse, <\/li>\n<li>vastuse ootamise aja limit, <\/li>\n<li>seire 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 teenuse seire seadistus l\u00f5petatud, n\u00fc\u00fcd saame seda basseinide loomisel kasutada. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/9db2263d6e5c90e1a5aba6cee865fd50.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Seadistame rakenduse reegleid<\/b><\/p>\n<p>Rakenduse reeglid \u2013 liikluse manipuleerimise viis, mis p\u00f5hineb teatud k\u00e4ivitajatel. Selle t\u00f6\u00f6riista abil saame luua laiendatud koormuse jaotusreegleid, mille seadistamine v\u00f5ib olla v\u00f5imatu l\u00e4bi rakenduse profiilide v\u00f5i teiste teenuste, mis on saadaval Edge Gateway's.<\/p>\n<ol>\n<li>L\u00e4bi rakenduse reeglite vahekaardi loome reegli tasakaalustaja jaoks.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/b370858e444c144c95fe0d89d3ea42da.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Valime nime, skripti, mis kasutab reeglit, ja vajutame Hoia.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/e0af1a95fb5b5bba46a52e582eba62bb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>P\u00e4rast reegli loomist tuleb meil redigeerida juba seatud Virtuaalserverit.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/c4617150f17e8e16cde94a9c3fb8e713.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vahekaardil T\u00e4iendavad lisame meie loodud reegli.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX k\u00f5ige v\u00e4iksematele. Osa 5. Laadimisseadmise seadistamine\" src=\"\/wp-content\/uploads\/2019\/04\/23f4ed5bb90bf178fec825e552fba8a6.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>Eeltoodud n\u00e4ites aktiveerisime tlsv1 toe.<\/p>\n<p>Veel m\u00f5ned n\u00e4ited:<\/p>\n<p>Liiklus suunamine teise gruppi.<br \/>\nSelle skripti abil saame suunata liikluse teise tasakaalustamisr\u00fchma, kui p\u00f5higrupp ei t\u00f6\u00f6ta. Reegli toimimiseks peab tasakaalustaja olema konfigureerinud mitu gruppi ja k\u00f5ik p\u00f5higruppi kuuluvad liikmed peavad olema seisundis down. Tuleb m\u00e4rkida r\u00fchma nimi, mitte selle 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>Liiklus suunamine v\u00e4lishankijale.<br \/>\nSiin suuname liikluse v\u00e4lishaavale veebisaidile, kui k\u00f5ik p\u00f5higruppi kuuluvad liikmed on seisundis down.<\/p>\n<p><code>acl pool_down nbsrv(NIME_TIIGI) eq 0<br \/>\nsuuna asukoht http:\/\/www.example.com, kui 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\">siit<\/a><\/noindex>.<\/p>\n<p>Sellel meie tasakaalustaja teema l\u00f5petan. Kui on k\u00fcsimusi, k\u00fcsige, olen valmis vastama.<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 5.0.1.1 - 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\/et\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\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: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. Tasakaalustaja seadistamine | ProHoster","description":"","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: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","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"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}]}}