{"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\/hr\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","title":{"rendered":"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" 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\/\">Prvi dio. Uvod<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441026\/\">Drugi dio. Postavka pravila vatrozida i NAT-a<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441882\/\">Tre\u0107i dio. Postavka DHCP-a<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/444644\/\">\u010cetvrti deo. Konfiguracija usmeravanja<\/a><\/noindex><\/p>\n<p>Zadnji put smo govorili o mogu\u0107nostima NSX Edge u kontekstu stati\u010dke i dinami\u010dke rutiranja, a danas \u0107emo se baviti balancerom.<br \/>\nPrije nego \u0161to zapo\u010dnemo s konfiguracijom, \u017eelio bih se ukratko podsjetiti na osnovne vrste balansiranja. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Teorija<\/h3>\n<p>\nSva dana\u0161nja rje\u0161enja za uravnote\u017eenje optere\u0107enja obi\u010dno se dijele u dvije kategorije: uravnote\u017eenje na \u010detvrtom (transportnom) i sedmom (aplikacijskom) sloju modela <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 model nije najbolja referentna to\u010dka prilikom opisivanja metoda balansiranja. Na primjer, ako L4 balancer podr\u017eava TLS terminaciju, postaje li on tada L7 balancer? No, to je tako.<\/p>\n<ul>\n<li><b>L4 balancer <\/b>naj\u010de\u0161\u0107e predstavlja srednji proxy koji se nalazi izme\u0111u klijenta i skupa dostupnih backendova, koji terminira TCP veze (odnosno sam odgovara na SYN), bira backend i inicira novu TCP sesiju prema njemu, \u0161alju\u0107i SYN samostalno. Ova vrsta je jedna od osnovnih, mogu\u0107e su i druge varijante.<\/li>\n<li><b>L7 balancer<\/b> distribuira promet me\u0111u dostupnim backendovima na \u201eslo\u017eeniji\u201c na\u010din nego \u0161to to \u010dini L4 balancer. Mo\u017ee donositi odluke o odabiru backend-a na temelju, na primjer, sadr\u017eaja HTTP poruke (URL adresa, kola\u010di\u0107i itd.).<\/li>\n<\/ul>\n<p>\nNeovisno o vrsti, balancer mo\u017ee podr\u017eavati sljede\u0107e funkcije:<\/p>\n<ul>\n<li> Otkrivanje servisa \u2013 proces utvr\u0111ivanja skupa dostupnih backendova (Static, DNS, Consul, Etcd itd.).<\/li>\n<li>Provjera funkcionalnosti otkrivenih backendova (aktivno \u201epinganje\u201c backend-a putem HTTP zahtjeva, pasivno otkrivanje problema u TCP vezama, prisutnost vi\u0161e uzastopnih 503 HTTP koda u odgovorima itd.).<\/li>\n<li>Samo balansiranje (round robin, nasumi\u010dni odabir, hash izvorne IP adrese, URI).<\/li>\n<li>Terminacija TLS-a i verifikacija certifikata.<\/li>\n<li>Opcije vezane uz sigurnost (autentifikacija, prevencija DoS napada, ograni\u010denje brzine) i jo\u0161 mnogo toga.<\/li>\n<\/ul>\n<p>\nNSX Edge nudi podr\u0161ku za dva moda implementacije balancer-a:<\/p>\n<p><b>Proxy na\u010din, ili one-arm<\/b>. U ovom re\u017eimu, NSX Edge koristi svoju IP adresu kao adresu izvora kada \u0161alje zahtjev jednom od backendova. Tako balancer istovremeno obavlja funkcije Source i Destination NAT. Backend vidi sav promet kao da je poslan s balancera i izravno mu odgovara. U toj shemi, balancer mora biti u istom mre\u017enom segmentu s internim serverima.<\/p>\n<p>Evo kako to funkcionira:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Korisnik \u0161alje zahtjev na VIP adresu (adresu balancera) koja je konfigurirana na Edge.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge bira jedan od backendova i izvr\u0161ava destination NAT, zamjenjuju\u0107i VIP adresu adresom odabranog backend.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge izvr\u0161ava source NAT, zamjenjuju\u0107i adresu korisnika koji je poslao zahtjev svojom vlastitom.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Paketa se \u0161alje odabranom backendu.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Backend ne odgovara izravno korisniku, ve\u0107 Edge-u, budu\u0107i da je izvorna adresa korisnika promijenjena na adresu balancera.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge proslje\u0111uje odgovor servera korisniku.<br \/>\nShema ispod.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/a6073ec63f7aca05d61c5a40de2ba6be.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Transparentan ili inline re\u017eim.<\/b> U ovom scenariju, balancer ima su\u010delja u unutarnjoj i vanjskoj mre\u017ei. Pristup unutarnjoj mre\u017ei nije izravan iz vanjske. Ugra\u0111eni balansirnik optere\u0107enja djeluje kao NAT gateway za virtualne ma\u0161ine u unutra\u0161njoj mre\u017ei.<\/p>\n<p>Mehanizam je sljede\u0107i:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Korisnik \u0161alje zahtjev na VIP adresu (adresu balancera) koja je konfigurirana na Edge.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge bira jedan od backendova i izvr\u0161ava destination NAT, zamjenjuju\u0107i VIP adresu adresom odabranog backend.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Paketa se \u0161alje odabranom backendu.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Backend primi zahtjev s izvornoj adresom korisnika (source NAT nije izvr\u0161en) i odgovara mu izravno.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Promet ponovo prihva\u0107a balancer optere\u0107enja, budu\u0107i da u inline shemi obi\u010dno djeluje kao zadani gateway za farmu servera.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge izvr\u0161ava source NAT za slanje prometa korisniku, koriste\u0107i svoj VIP kao source IP adresu.<br \/>\nShema ispod.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/9ad9adcac02d40db1603aee84387264a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Praksa<\/h3>\n<p>\nNa mom testnom okviru konfigurirana su 3 servera s Apache-om, koji je pode\u0161en za rad putem HTTPS-a. Edge \u0107e vr\u0161iti balansiranje HTTPS zahtjeva metodom round robin, proksiraju\u0107i svaki novi zahtjev na novi server.<br \/>\nKrenimo.<\/p>\n<p><b>Generiramo SSL certifikat koji \u0107e koristiti NSX Edge.<\/b><br \/>\nMo\u017eete uvesti valjani CA certifikat ili koristiti samopotpisani. U ovom testu koristit \u0107u samopotpisani.<\/p>\n<ol>\n<li>U su\u010delju vCloud Director odlazimo na postavke usluga Edge.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/df9be9f6d5b92af1cbe19f40459c8d9f.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Odlazimo na karticu Certifikati. Iz padaju\u0107eg izbornika odabiremo dodavanje novog CSR-a.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/72185bf69cb0c4d8dc0cbadc8fe4f376.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Ispunjavamo potrebna polja i kliknemo na Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/196394d4633d76dfde6d89b8f7049e19.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Odabiremo upravo kreirani CSR i biramo opciju self-sign CSR.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/262e7a1ede8bda39a9ee098f360a38e3.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Odabiremo trajanje valjanosti certifikata i kliknemo na Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/6c880218fd7874652e6540a0bde18310.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Samo potpisani certifikat pojavljuje se na popisu dostupnih.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/f065f461da8f96ca31c96d3c801350ec.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Konfiguriramo Application Profile.<\/b><br \/>\nApplication profili pru\u017eaju potpuniju kontrolu nad mre\u017enim prometom i olak\u0161avaju upravljanje istim. Pomo\u0107u njih mo\u017eemo odrediti pona\u0161anje za odre\u0111ene tipove prometa. <\/p>\n<ol>\n<li>Idemo na karticu Load Balancer i uklju\u010dujemo ravnote\u017eu optere\u0107enja. Opcija Acceleration enabled ovdje omogu\u0107uje ravnote\u017ei optere\u0107enja da koristi br\u017eu L4 ravnote\u017eu umjesto L7.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/1ee064e2fe234fb1d96ec327f3f92f05.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Idemo na karticu Application profile kako bismo postavili profil aplikacije. Kliknite +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/5686a86bdff4d973f33f1a9d362ad273.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Postavljamo naziv profila i biramo tip prometa kojem \u0107e se profil primijeniti. Objasnit \u0107u neke parametre.<br \/>\n<b>Persistence<\/b> \u2013 \u010duva i prati podatke sesije, na primjer: koji to\u010dno poslu\u017eitelj iz grupe obra\u0111uje korisni\u010dki zahtjev. Ovo jam\u010di da se korisni\u010dki zahtjevi \u0161alju istoj \u010dlanici grupe tijekom trajanja sesije ili sljede\u0107ih sesija.<br \/>\n<b>Enable SSL passthrough<\/b> \u2013 odabirom ove opcije NSX Edge prestaje terminirati SSL. Umjesto toga, terminacija se doga\u0111a izravno na poslu\u017eiteljima za koje se obavlja ravnote\u017ea.<br \/>\n<b>Insert X-Forwarded-For HTTP header<\/b> \u2013 omogu\u0107uje identifikaciju izvorne IP adrese klijenta koji se povezuje s web poslu\u017eiteljem putem ravnote\u017ee optere\u0107enja.<br \/>\n<b>Enable Pool Side SSL<\/b> \u2013 ozna\u010dava da odabrana grupa sastoji se od HTTPS poslu\u017eitelja.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/81fa688f063f5cf1719461884bbb8dc2.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Budu\u0107i da \u0107u ravnote\u017eiti HTTPS promet, potrebno je uklju\u010diti Pool Side SSL i odabrati prethodno generirani certifikat na kartici Virtual Server Certificates \u2014&gt; Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/d2585bcc33e57adc561bc5d956057479.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Sli\u010dno za Pool Certificates \u2014&gt; Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/b565acf03e4eba313b4624a912310663.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Stvaramo grupu poslu\u017eitelja \u010diji \u0107e promet biti ravnote\u017een Pools.<\/b><\/p>\n<ol>\n<li>Idemo na karticu Pools. Kliknemo +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/e3fd9f747f3cbc43f3d348c05ece07fd.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Postavljamo naziv grupe, biramo algoritam (ja \u0107u koristiti round robin) i tip pra\u0107enja za health check pozadine. Opcija Transparent ozna\u010dava da li izvorni IP klijenata vidi interni poslu\u017eitelj.\n<ul>\n<li>Ako je opcija isklju\u010dena, promet za interne poslu\u017eitelje dolazi s IP adrese ravnote\u017ee.\n<\/li>\n<li> Ako je opcija uklju\u010dena, interni poslu\u017eitelji vide izvorni IP klijenata. U takvoj konfiguraciji NSX Edge mora biti zadani pristupnik kako bi se osiguralo da se vra\u0107eni paketi \u0161alju kroz NSX Edge.<\/li>\n<\/ul>\n<p>NSX podr\u017eava sljede\u0107e algoritme balansiranja:<\/p>\n<ul>\n<li><b>IP_HASH<\/b> \u2013 odabir poslu\u017eitelja na temelju rezultata funkcije raspr\u0161enja za source i destination IP svakog paketa.<\/li>\n<li> <b>LEASTCONN <\/b>\u2013 balansiranje ulaznih veza, ovisno o broju ve\u0107 postoje\u0107ih na odre\u0111enom poslu\u017eitelju. Nove veze \u0107e se usmjeriti na poslu\u017eitelj s najmanje veza.<\/li>\n<li> <b>ROUND_ROBIN <\/b>\u2013 nove veze se \u0161alju na svaki poslu\u017eitelj redoslijedom, prema unaprijed odre\u0111enoj te\u017eini.<\/li>\n<li><b>URI<\/b> \u2013 lijeva strana URI (prije upitnika) se hashira i dijeli na ukupnu te\u017einu poslu\u017eitelja u bazenu. Rezultat ukazuje koji poslu\u017eitelj prima zahtjev, osiguravaju\u0107i da se zahtjev uvijek \u0161alje na isti poslu\u017eitelj, sve dok svi poslu\u017eitelji ostaju dostupni.<\/li>\n<li><b>HTTPHEADER <\/b>\u2013 balansiranje na temelju odre\u0111enog HTTP zaglavlja koje se mo\u017ee odrediti kao parametar. Ako zaglavlje nedostaje ili nema nikakvu vrijednost, primjenjuje se algoritam ROUND_ROBIN.<\/li>\n<li><b>URL <\/b>\u2013 u svakom HTTP GET zahtjevu pretra\u017euje se po parametru URL, navedenom kao argument. Ako iza parametra slijedi znak jednakosti i vrijednost, onda se vrijednost hashira i dijeli na ukupnu te\u017einu aktivnih poslu\u017eitelja. Rezultat ukazuje koji poslu\u017eitelj prima zahtjev. Ovaj proces se koristi za pra\u0107enje identifikatora korisnika u zahtjevima i osiguranje da se isti user id uvijek \u0161alje na isti poslu\u017eitelj, sve dok svi poslu\u017eitelji ostaju dostupni.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/ab98325a49a63d1d005839a47af39544.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>U bloku Members kliknemo + za dodavanje poslu\u017eitelja u bazen.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/f67e7567c48a6403bb5dcd165d150052.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nOvdje treba navesti:<\/p>\n<ul>\n<li>ime poslu\u017eitelja;<\/li>\n<li>IP adresa poslu\u017eitelja;<\/li>\n<li>port na koji \u0107e poslu\u017eitelj primati promet;<\/li>\n<li>port za health check (Monitor healthcheck); <\/li>\n<li>te\u017eina (Weight) \u2013 pomo\u0107u ovog parametra mo\u017ee se regulirati proporcionalna koli\u010dina prometa za odre\u0111enog \u010dlana bazena;<\/li>\n<li>Max Connections \u2013 maksimalan broj veza na poslu\u017eitelj;<\/li>\n<li>Min Connections \u2013 minimalan broj veza koje poslu\u017eitelj mora obraditi prije nego \u0161to se promet prebaci na sljede\u0107eg \u010dlana bazena.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/4bfd6de65e50cb417845d358b11b91b5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nOvako izgleda kona\u010dni bazen od tri poslu\u017eitelja.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/42ebe47da99599628d9e6e75289a9f25.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Dodajemo Virtual Server<\/b><\/p>\n<ol>\n<li>Prelazimo na karticu Virtual Servers. Kliknemo +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/4d95be098f50055d81f538ebe565cfbb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Aktiviramo virtualni poslu\u017eitelj pomo\u0107u Enable Virtual Server.<br \/>\nPostavljamo mu ime, biramo prethodno stvoreni Application Profile, Pool i odre\u0111ujemo IP adresu na koju \u0107e Virtual Server primati zahtjeve izvana. Odre\u0111ujemo protokol HTTPS i port 443.<br \/>\nOpcionalni parametri ovdje:<br \/>\n<b>Ograni\u010denje veze <\/b>\u2013 maksimalni broj istovremenih veza koje virtualni server mo\u017ee obraditi;<br \/>\n<b>Ograni\u010denje brzine veze (CPS)<\/b> \u2013 maksimalni broj novih ulaznih zahtjeva u sekundi.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/fae8dff378af917a96b9a7d887bb2bd8.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>Na ovoj konfiguraciji balansera je gotovo, mo\u017eemo provjeriti njegovu funkcionalnost. Serveri imaju jednostavnu konfiguraciju koja omogu\u0107ava razumijevanje kojim je to\u010dno serverom iz poola obra\u0111en zahtjev. Tijekom konfiguracije odabrali smo algoritam uravnote\u017eenja Round Robin, a parametar Weight za svaki server iznosi jedan, tako da \u0107e svaki sljede\u0107i zahtjev biti obra\u0111en sljede\u0107im serverom iz poola.<br \/>\nUpisujemo vanjsku adresu balansira\u010da u pregledniku i vidimo:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/e10d1c9eb14b42f4f6fc03a0d6f03013.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNakon ponovnog u\u010ditavanja stranice, zahtjev \u0107e biti obra\u0111en sljede\u0107im serverom:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/09a67549ca2f05f835a2d4645779bfa1.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nJo\u0161 jednom \u2013 da provjerimo i tre\u0107i server iz poola:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/e0452323822ff0a3e02ff5bcee53bcdc.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTijekom provjere mo\u017eemo vidjeti da je certifikat koji nam \u0161alje Edge onaj koji smo generirali na samom po\u010detku. <\/p>\n<p>Provjera statusa balansira\u010da iz konzole Edge gateway. Za to unesite <b>show service loadbalancer pool<\/b>. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/10a7421dc6278ba2c721187bfeb076a9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Konfiguriramo Service Monitor za provjeru stanja servera u poolu <\/b><br \/>\nPomo\u0107u Service Monitora mo\u017eemo pratiti stanje servera u backend poolu. Ako odgovor na zahtjev ne odgovara o\u010dekivanju, server se mo\u017ee izbaciti iz poola kako ne bi primao nove zahtjeve.<br \/>\nPo defaultu su konfigurirane tri metode provjere:<\/p>\n<ul>\n<li> TCP-monitor,<\/li>\n<li> HTTP-monitor,<\/li>\n<li> HTTPS-monitor.<\/li>\n<\/ul>\n<p>\nNapravimo novi. <\/p>\n<ol>\n<li>Prelazimo na karticu Service Monitoring, kliknemo +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/ceac4fac8197b395d7531391534ad4ff.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Biramo:\n<ul>\n<li>ime za novu metodu;<\/li>\n<li>interval s kojim \u0107e se slati zahtjevi, <\/li>\n<li>timeout za \u010dekanje odgovora, <\/li>\n<li>tip monitoringa \u2013 HTTPS zahtjev koriste\u0107i metodu GET, o\u010dekivani statusni kod \u2013 200(OK) i URL zahtjeva.<\/li>\n<\/ul>\n<\/li>\n<li>S ovim je konfiguracija novog Service Monitora zavr\u0161ena, sada ga mo\u017eemo koristiti prilikom stvaranja poola. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/9db2263d6e5c90e1a5aba6cee865fd50.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Konfiguriramo Application Rules<\/b><\/p>\n<p>Application Rules \u2013 na\u010din manipulacije prometom temeljen na odre\u0111enim okida\u010dima. Pomo\u0107u ovog alata mo\u017eemo stvoriti napredna pravila uravnote\u017eenja optere\u0107enja, \u010dija konfiguracija mo\u017eda ne\u0107e biti mogu\u0107a putem Application profiles ili drugih usluga dostupnih na Edge Gateway.<\/p>\n<ol>\n<li>Da bismo stvorili pravilo, idemo na karticu Application Rules balansatora.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/b370858e444c144c95fe0d89d3ea42da.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Odabiremo ime, skript koji \u0107e koristiti pravilo i pritisnemo Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/e0af1a95fb5b5bba46a52e582eba62bb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Nakon \u0161to je pravilo stvoreno, trebamo urediti ve\u0107 postavljeni Virtual Server.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/c4617150f17e8e16cde94a9c3fb8e713.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Na kartici Advanced dodajemo pravilo koje smo stvorili.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX za male. Dio 5. Postavljanje ravnote\u017ee optere\u0107enja\" src=\"\/wp-content\/uploads\/2019\/04\/23f4ed5bb90bf178fec825e552fba8a6.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>U gornjem primjeru omogu\u0107ili smo podr\u0161ku za tlsv1.<\/p>\n<p>Jo\u0161 nekoliko primjera:<\/p>\n<p>Preusmjeravanje prometa u drugi bazen.<br \/>\nPomo\u0107u ovog skripta mo\u017eemo preusmjeriti promet u drugi bazen ravnote\u017ee, ako glavni bazen ne radi. Da bi pravilo radilo, na balansatoru mora biti konfigurirano vi\u0161e bazena, a svi \u010dlanovi glavnog bazena trebaju biti u stanju down. Treba navesti ime bazena, a ne njegov 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>Preusmjeravanje prometa na vanjski resurs.<br \/>\nOvdje preusmjeravamo promet na vanjsku web stranicu, ako su svi sudionici glavnog bazena u stanju down.<\/p>\n<p><code>acl pool_down nbsrv(NAME_OF_POOL) eq 0<br \/>\npreusmjeri lokaciju http:\/\/www.example.com ako je pool_down<\/code><\/p>\n<p>Jo\u0161 vi\u0161e primjera <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\">ovdje<\/a><\/noindex>.<\/p>\n<p>To je sve o balansatoru. Ako imate pitanja, slobodno pitajte, spreman sam odgovoriti.<br \/>\n<br \/>Izvor: <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.4 - 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\/hr\/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.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"hr_HR\" \/>\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\/hr\/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 za najmla\u0111e. Dio 5. Postavke balansatora optere\u0107enja | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","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\/hr\/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\/hr\/wp-json\/wp\/v2\/posts\/31817","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=31817"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/31817\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media\/23693"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=31817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=31817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=31817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}