{"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\/ro\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","title":{"rendered":"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" 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\/\">Partea \u00eent\u00e2i. Introducere<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441026\/\">Partea a doua. Configurarea regulilor Firewall \u0219i NAT<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441882\/\">Partea a treia. Configurarea DHCP<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/444644\/\">Partea a patra. Configurarea rut\u0103rii<\/a><\/noindex><\/p>\n<p>Data trecut\u0103 am discutat despre capabilit\u0103\u021bile NSX Edge \u00een contextul rut\u0103rii statice \u0219i dinamice, iar ast\u0103zi ne vom axa pe echilibrator.<br \/>\n\u00cenainte de a \u00eencepe configurarea, a\u0219 dori s\u0103 fac un scurt rezumat al principalelor tipuri de echilibrare. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Teorie<\/h3>\n<p>\nToate solu\u021biile de echilibrare a \u00eenc\u0103rc\u0103rii de ast\u0103zi se \u00eempart, de obicei, \u00een dou\u0103 categorii: echilibrarea la nivelul patru (transport) \u0219i la nivelul \u0219apte (aplica\u021bie) al modelului <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>. Modelul OSI nu este cea mai bun\u0103 referin\u021b\u0103 atunci c\u00e2nd descriem metodele de echilibrare. De exemplu, dac\u0103 un echilibrator L4 suport\u0103 \u0219i terminarea TLS, devine el astfel un echilibrator L7? Dar a\u0219a stau lucrurile.<\/p>\n<ul>\n<li><b>Echilibrator L4 <\/b>de obicei reprezint\u0103 un proxy care st\u0103 \u00eentre client \u0219i un set de backend-uri disponibile, termin\u00e2nd conexiunile TCP (adic\u0103 r\u0103spunz\u00e2nd singur la SYN), aleg\u00e2nd un backend \u0219i ini\u021biind o nou\u0103 sesiune TCP c\u0103tre acesta, trimi\u021b\u00e2nd singur SYN. Acest tip este unul de baz\u0103, pot exista \u0219i alte varia\u021bii.<\/li>\n<li><b>Echilibrator L7<\/b> distribuie traficul c\u0103tre backend-urile disponibile \u201emai sofisticat\u201d dec\u00e2t o face echilibratorul L4. Acesta poate lua decizii de selec\u021bie a backend-ului pe baza, de exemplu, con\u021binutului mesajului HTTP (URL, cookie etc.).<\/li>\n<\/ul>\n<p>\nIndiferent de tip, echilibratorul poate sus\u021bine urm\u0103toarele func\u021bii:<\/p>\n<ul>\n<li> Descoperirea serviciilor \u2013 procesul de determinare a setului de backend-uri disponibile (Static, DNS, Consul, Etcd etc.).<\/li>\n<li>Verificarea func\u021bion\u0103rii backend-urilor descoperite (ping activ al backend-ului printr-o cerere HTTP, descoperire pasiv\u0103 a problemelor \u00een conexiunile TCP, apari\u021bia consecutiv\u0103 a mai multor coduri HTTP 503 \u00een r\u0103spunsurile primite etc.).<\/li>\n<li>Efectuarea echilibr\u0103rii (round robin, selec\u021bie aleatoare, hash IP surs\u0103, URI).<\/li>\n<li>Terminarea TLS \u0219i validarea certificatelor.<\/li>\n<li>Op\u021biuni legate de asigurarea securit\u0103\u021bii (autentificare, prevenirea atacurilor DoS, limitarea ratelor) \u0219i multe altele.<\/li>\n<\/ul>\n<p>\nNSX Edge ofer\u0103 suport pentru dou\u0103 moduri de desf\u0103\u0219urare a echilibratorului:<\/p>\n<p><b>Modul proxy, sau one-arm<\/b>. \u00cen acest mod, NSX Edge folose\u0219te adresa sa IP ca adres\u0103 surs\u0103 atunci c\u00e2nd trimite solicit\u0103ri c\u0103tre unul dintre backend-uri. Astfel, echilibratorul de sarcin\u0103 \u00eendepline\u0219te simultan func\u021biile de NAT surs\u0103 \u0219i destina\u021bie. Backend-ul vede tot traficul ca fiind trimis de la echilibrator \u0219i \u00eei r\u0103spunde direct. \u00cen aceast\u0103 schem\u0103, echilibratorul trebuie s\u0103 fie \u00een acela\u0219i segment de re\u021bea cu serverele interne.<\/p>\n<p>Iat\u0103 cum se \u00eent\u00e2mpl\u0103:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Utilizatorul trimite o solicitare c\u0103tre adresa VIP (adresa echilibratorului), care este configurat\u0103 pe Edge.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge alege unul dintre backend-uri \u0219i efectueaz\u0103 NAT de destina\u021bie, \u00eenlocuind adresa VIP cu adresa backend-ului ales.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge efectueaz\u0103 NAT surs\u0103, \u00eenlocuind adresa utilizatorului care a trimis solicitarea cu propria sa adres\u0103.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Pachetul este trimis c\u0103tre backend-ul ales.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Backend-ul r\u0103spunde nu direct utilizatorului, ci lui Edge, deoarece adresa ini\u021bial\u0103 a utilizatorului a fost schimbat\u0103 cu adresa echilibratorului.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge transmite r\u0103spunsul serverului utilizatorului.<br \/>\nSchema de mai jos.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/a6073ec63f7aca05d61c5a40de2ba6be.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Modul transparent sau inline.<\/b> \u00cen acest scenariu, echilibratorul are interfe\u021be \u00een re\u021beaua intern\u0103 \u0219i \u00een cea extern\u0103. Totu\u0219i, nu exist\u0103 acces direct la re\u021beaua intern\u0103 din exterior. Echilibratorul de \u00eenc\u0103rcare integrat ac\u021bioneaz\u0103 ca un gateway NAT pentru ma\u0219inile virtuale din re\u021beaua intern\u0103.<\/p>\n<p>Mecanismul este urm\u0103torul:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Utilizatorul trimite o solicitare c\u0103tre adresa VIP (adresa echilibratorului), care este configurat\u0103 pe Edge.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge alege unul dintre backend-uri \u0219i efectueaz\u0103 NAT de destina\u021bie, \u00eenlocuind adresa VIP cu adresa backend-ului ales.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Pachetul este trimis c\u0103tre backend-ul ales.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Backend-ul prime\u0219te solicitarea cu adresa ini\u021bial\u0103 a utilizatorului (NAT surs\u0103 nu a fost efectuat) \u0219i \u00eei r\u0103spunde direct.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Traficul este din nou preluat de echilibratorul de sarcin\u0103, deoarece \u00een schema inline de obicei ac\u021bioneaz\u0103 ca gateway implicit pentru ferma de servere.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge efectueaz\u0103 NAT surs\u0103 pentru a trimite trafic utilizatorului, folosind VIP-ul s\u0103u ca adres\u0103 IP surs\u0103.<br \/>\nSchema de mai jos.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/9ad9adcac02d40db1603aee84387264a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Practic\u0103<\/h3>\n<p>\n\u00cen laboratorul meu de testare am configurat 3 servere cu Apache, care este configurat s\u0103 func\u021bioneze pe HTTPS. Edge va realiza echilibrarea solicit\u0103rilor HTTPS folosind metoda round robin, proxiind fiecare nou\u0103 solicitare c\u0103tre un nou server.<br \/>\nS\u0103 \u00eencepem.<\/p>\n<p><b>Gener\u0103m un certificat SSL, care va fi utilizat de NSX Edge.<\/b><br \/>\nPute\u021bi importa un certificat CA valid sau utiliza unul auto-semnat. \u00cen acest test, voi folosi un certificat auto-semnat.<\/p>\n<ol>\n<li>\u00cen interfa\u021ba vCloud Director, acces\u0103m set\u0103rile serviciilor Edge.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/df9be9f6d5b92af1cbe19f40459c8d9f.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Acces\u0103m tab-ul Certificate. Din lista de ac\u021biuni, alegem ad\u0103ugarea unui nou CSR.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/72185bf69cb0c4d8dc0cbadc8fe4f376.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Complet\u0103m c\u00e2mpurile necesare \u0219i ap\u0103s\u0103m Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/196394d4633d76dfde6d89b8f7049e19.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Select\u0103m CSR-ul nou creat \u0219i alegem op\u021biunea self-sign CSR.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/262e7a1ede8bda39a9ee098f360a38e3.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Alegem perioada de valabilitate a certificatului \u0219i ap\u0103s\u0103m Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/6c880218fd7874652e6540a0bde18310.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Certificatul auto-semnat a ap\u0103rut \u00een lista disponibil\u0103.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/f065f461da8f96ca31c96d3c801350ec.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Configur\u0103m Application Profile.<\/b><br \/>\nProfilele de aplica\u021bie ofer\u0103 un control mai mare asupra traficului de re\u021bea \u0219i fac gestionarea acestuia simpl\u0103 \u0219i eficient\u0103. Cu ajutorul lor, se poate defini comportamentul pentru anumite tipuri de trafic. <\/p>\n<ol>\n<li>Trecem la tab-ul Load Balancer \u0219i activ\u0103m balansorul. Op\u021biunea Acceleration enabled permite balansorului s\u0103 utilizeze un echilibru L4 mai rapid \u00een loc de L7.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/1ee064e2fe234fb1d96ec327f3f92f05.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Trecem la tab-ul Application profile pentru a defini profilul aplica\u021biei. Ap\u0103sa\u021bi +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/5686a86bdff4d973f33f1a9d362ad273.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Definim numele profilului \u0219i alegem tipul de trafic pentru care profilul va fi aplicat. Voi explica c\u00e2teva dintre parametri.<br \/>\n<b>Persistence<\/b> \u2013 p\u0103streaz\u0103 \u0219i urm\u0103re\u0219te datele sesiunii, de exemplu: care server specific din pool deserve\u0219te cererea utilizatorului. Aceasta garanteaz\u0103 c\u0103 cererile utilizatorului sunt direc\u021bionate c\u0103tre acela\u0219i membru din pool pe parcursul \u00eentregii sesiuni sau \u00een sesiuni ulterioare.<br \/>\n<b>Enable SSL passthrough<\/b> \u2013 aleg\u00e2nd aceast\u0103 op\u021biune, NSX Edge \u00eenceteaz\u0103 s\u0103 termine SSL. \u00cen schimb, terminarea are loc direct pe serverele pentru care se face echilibrarea.<br \/>\n<b>Insert X-Forwarded-For HTTP header<\/b> \u2013 permite identificarea adresei IP originale a clientului care se conecteaz\u0103 la serverul web prin intermediul balansorului.<br \/>\n<b>Enable Pool Side SSL<\/b> \u2013 permite specificarea faptului c\u0103 pool-ul selectat const\u0103 din servere HTTPS.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/81fa688f063f5cf1719461884bbb8dc2.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Deoarece voi echilibra traficul HTTPS, trebuie s\u0103 activez Pool Side SSL \u0219i s\u0103 aleg certificatul generat anterior \u00een tab-ul Virtual Server Certificates \u2014&gt; Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/d2585bcc33e57adc561bc5d956057479.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Similar pentru Pool Certificates \u2014&gt; Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/b565acf03e4eba313b4624a912310663.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Cre\u0103m un pool de servere, traficul c\u0103tre care va fi echilibrat Pools.<\/b><\/p>\n<ol>\n<li>Trecem la tab-ul Pools. Ap\u0103s\u0103m +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/e3fd9f747f3cbc43f3d348c05ece07fd.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Definim numele pool-ului, alegem algoritmul (voi folosi round robin) \u0219i tipul de monitorizare pentru health check-ul backend-ului. Op\u021biunea Transparent indic\u0103 dac\u0103 adresele IP originale ale clien\u021bilor sunt vizibile pentru serverele interne.\n<ul>\n<li>Dac\u0103 op\u021biunea este dezactivat\u0103, traficul pentru serverele interne vine cu adresa IP a balansorului.\n<\/li>\n<li> Dac\u0103 op\u021biunea este activat\u0103, serverele interne v\u0103d adresa IP a clien\u021bilor. \u00centr-o astfel de configura\u021bie, NSX Edge trebuie s\u0103 ac\u021bioneze ca gateway implicit pentru a garanta c\u0103 pachetele returnate trec prin NSX Edge.<\/li>\n<\/ul>\n<p>NSX suport\u0103 urm\u0103toarele algoritmi de echilibrare:<\/p>\n<ul>\n<li><b>IP_HASH<\/b> \u2013 alegerea serverului pe baza rezultatelor func\u021biei de hash pentru adresele IP surs\u0103 \u0219i destina\u021bie ale fiec\u0103rui pachet.<\/li>\n<li> <b>LEASTCONN <\/b>\u2013 echilibrarea conexiunilor de intrare, \u00een func\u021bie de num\u0103rul deja existent pe un server specific. Noi conexiuni vor fi direc\u021bionate c\u0103tre serverul cu cele mai pu\u021bine conexiuni.<\/li>\n<li> <b>ROUND_ROBIN <\/b>\u2013 noile conexiuni sunt trimise pe r\u00e2nd c\u0103tre fiecare server, conform greut\u0103\u021bii atribuite acestuia.<\/li>\n<li><b>URI<\/b> \u2013 partea st\u00e2ng\u0103 a URI (p\u00e2n\u0103 la semnul \u00eentreb\u0103rii) este hash-uit\u0103 \u0219i \u00eemp\u0103r\u021bit\u0103 la greutatea total\u0103 a serverelor din pool. Rezultatul indic\u0103 ce server prime\u0219te cererea, garant\u00e2nd c\u0103 cererea este \u00eentotdeauna direc\u021bionat\u0103 c\u0103tre acela\u0219i server, at\u00e2ta timp c\u00e2t toate serverele r\u0103m\u00e2n disponibile.<\/li>\n<li><b>HTTPHEADER <\/b>\u2013 echilibrarea pe baza unui anumit header HTTP, care poate fi specificat ca parametru. Dac\u0103 headerul lipse\u0219te sau nu are o valoare, se aplic\u0103 algoritmul ROUND_ROBIN.<\/li>\n<li><b>URL <\/b>\u2013 \u00een fiecare cerere HTTP GET se caut\u0103 parametrul URL specificat ca argument. Dac\u0103 parametrul este urmat de semnul egal \u0219i o valoare, atunci valoarea este hash-uit\u0103 \u0219i \u00eemp\u0103r\u021bit\u0103 la greutatea total\u0103 a serverelor active. Rezultatul indic\u0103 ce server prime\u0219te cererea. Acest proces este utilizat pentru a urm\u0103ri identificatorii utilizatorilor \u00een cereri \u0219i pentru a asigura c\u0103 acela\u0219i user id este \u00eentotdeauna trimis c\u0103tre acela\u0219i server, at\u00e2ta timp c\u00e2t toate serverele r\u0103m\u00e2n disponibile.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/ab98325a49a63d1d005839a47af39544.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>\u00cen blocul Members ap\u0103s\u0103m + pentru a ad\u0103uga servere \u00een pool.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/f67e7567c48a6403bb5dcd165d150052.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAici trebuie specificat:<\/p>\n<ul>\n<li>numele serverului;<\/li>\n<li>adresa IP a serverului;<\/li>\n<li>portul pe care serverul va primi trafic;<\/li>\n<li>portul pentru health check (Monitor healthcheck); <\/li>\n<li>greutatea (Weight) \u2013 cu ajutorul acestui parametru se poate regla cantitatea propor\u021bional\u0103 de trafic primit pentru un anumit membru al pool-ului;<\/li>\n<li>Max Connections \u2013 num\u0103rul maxim de conexiuni c\u0103tre server;<\/li>\n<li>Min Connections \u2013 num\u0103rul minim de conexiuni pe care serverul trebuie s\u0103 le proceseze \u00eenainte de a redirec\u021biona traficul c\u0103tre urm\u0103torul membru al pool-ului.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/4bfd6de65e50cb417845d358b11b91b5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nIat\u0103 cum arat\u0103 pool-ul final din trei servere.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/42ebe47da99599628d9e6e75289a9f25.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Ad\u0103ug\u0103m Server Virtual<\/b><\/p>\n<ol>\n<li>Trebuie s\u0103 trecem la tab-ul Servere Virtuale. Ap\u0103s\u0103m +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/4d95be098f50055d81f538ebe565cfbb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Activ\u0103m serverul virtual prin Enable Virtual Server.<br \/>\n\u00cei d\u0103m un nume, alegem Application Profile, Pool create anterior \u0219i specific\u0103m adresa IP la care Serverul Virtual va accepta cereri din exterior. Specific\u0103m protocolul HTTPS \u0219i portul 443.<br \/>\nParametrii op\u021bionali aici:<br \/>\n<b>Limit\u0103 de Conexiuni <\/b>\u2013 num\u0103rul maxim de conexiuni simultane pe care le poate gestiona serverul virtual;<br \/>\n<b>Limit\u0103 de Rat\u0103 a Conexiunilor (CPS)<\/b> \u2013 num\u0103rul maxim de cereri noi de intrare pe secund\u0103.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/fae8dff378af917a96b9a7d887bb2bd8.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>Configurarea echilibra\u0219ului de sarcin\u0103 este acum finalizat\u0103, iar func\u021bionalitatea acestuia poate fi verificat\u0103. Serverele au o configura\u021bie simpl\u0103 care permite \u00een\u021belegerea care server din pool a gestionat cererea. \u00cen timpul configur\u0103rii, am ales algoritmul de echilibrare Round Robin, iar parametrul Weight pentru fiecare server este egal cu unu, astfel \u00eenc\u00e2t fiecare cerere ulterioar\u0103 va fi gestionat\u0103 de urm\u0103torul server din pool.<br \/>\nIntroducem \u00een browser adresa extern\u0103 a echilibra\u0219ului de sarcin\u0103 \u0219i vedem:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/e10d1c9eb14b42f4f6fc03a0d6f03013.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDup\u0103 actualizarea paginii, cererea va fi gestionat\u0103 de urm\u0103torul server:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/09a67549ca2f05f835a2d4645779bfa1.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n\u0218i \u00eenc\u0103 o dat\u0103 \u2013 pentru a verifica \u0219i al treilea server din pool:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/e0452323822ff0a3e02ff5bcee53bcdc.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nLa verificare, putem vedea c\u0103 certificatul pe care ni-l trimite Edge este acela\u0219i pe care l-am generat la \u00eenceput. <\/p>\n<p>Verificarea st\u0103rii echilibra\u0219ului de sarcin\u0103 din consola Edge gateway. Pentru aceasta, introduce\u021bi <b>show service loadbalancer pool<\/b>. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/10a7421dc6278ba2c721187bfeb076a9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Configur\u0103m Service Monitor pentru a verifica starea serverelor din pool <\/b><br \/>\nCu ajutorul Service Monitor putem urm\u0103ri starea serverelor din pool-ul backend. Dac\u0103 r\u0103spunsul la cerere nu corespunde a\u0219tept\u0103rilor, serverul poate fi exclus din pool, astfel \u00eenc\u00e2t s\u0103 nu primeasc\u0103 cereri noi.<br \/>\nImplicit, sunt configurate trei metode de verificare:<\/p>\n<ul>\n<li> TCP-monitor,<\/li>\n<li> HTTP-monitor,<\/li>\n<li> HTTPS-monitor.<\/li>\n<\/ul>\n<p>\nVom crea unul nou. <\/p>\n<ol>\n<li>Trecem la tab-ul Service Monitoring, ap\u0103s\u0103m +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/ceac4fac8197b395d7531391534ad4ff.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Alegerile sunt:\n<ul>\n<li>numele pentru noua metod\u0103;<\/li>\n<li>intervalul la care vor fi trimise cererile, <\/li>\n<li>timpul de a\u0219teptare pentru r\u0103spuns, <\/li>\n<li>tipul de monitorizare \u2013 cerere HTTPS folosind metoda GET, codul de stare a\u0219teptat \u2013 200(OK) \u0219i URL-ul cererii.<\/li>\n<\/ul>\n<\/li>\n<li>Aceasta este configura\u021bia noului Service Monitor, acum o putem folosi la crearea pool-ului. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/9db2263d6e5c90e1a5aba6cee865fd50.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Configur\u0103m Reguli pentru Aplica\u021bii<\/b><\/p>\n<p>Regulile pentru Aplica\u021bii \u2013 un mod de manipulare a traficului bazat pe anumite declan\u0219atoare. Cu ajutorul acestui instrument, putem crea reguli avansate de echilibrare a sarcinii, configura\u021bia c\u0103rora poate fi imposibil\u0103 prin intermediul Application profiles sau folosind alte servicii disponibile pe Edge Gateway.<\/p>\n<ol>\n<li>Pentru a crea o regul\u0103, mergem la fila Application Rules a echilibratorului.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/b370858e444c144c95fe0d89d3ea42da.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Alegem un nume, scriptul care va folosi regula \u0219i d\u0103m click pe Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/e0af1a95fb5b5bba46a52e582eba62bb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Dup\u0103 ce regula este creat\u0103, trebuie s\u0103 edit\u0103m Serverul Virtual deja configurat.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/c4617150f17e8e16cde94a9c3fb8e713.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>\u00cen fila Advanced ad\u0103ug\u0103m regula pe care am creat-o.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX pentru \u00eencep\u0103tori. Partea 5. Configurarea echilibratorului de \u00eenc\u0103rcare\" src=\"\/wp-content\/uploads\/2019\/04\/23f4ed5bb90bf178fec825e552fba8a6.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>\u00cen exemplul de mai sus, am activat suportul pentru tlsv1.<\/p>\n<p>\u00cenc\u0103 c\u00e2teva exemple:<\/p>\n<p>Redirectarea traficului c\u0103tre un alt pool.<br \/>\nCu acest script putem redirec\u021biona traficul c\u0103tre un alt pool de echilibrare, dac\u0103 pool-ul principal nu func\u021bioneaz\u0103. Pentru ca regula s\u0103 func\u021bioneze, trebuie s\u0103 existe configurate mai multe pool-uri pe echilibrator, iar to\u021bi membrii pool-ului principal trebuie s\u0103 fie \u00een stare down. Trebuie specificat numele pool-ului, nu ID-ul acestuia.<\/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>Redirectarea traficului c\u0103tre o resurs\u0103 extern\u0103.<br \/>\nAici redirec\u021bion\u0103m traficul c\u0103tre un site web extern, dac\u0103 to\u021bi participan\u021bii pool-ului principal sunt \u00een stare 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>\u00cenc\u0103 \u0219i mai multe exemple <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\">aici<\/a><\/noindex>.<\/p>\n<p>Asta a fost tot despre echilibrator. Dac\u0103 mai ave\u021bi \u00eentreb\u0103ri, \u00eentreba\u021bi, sunt preg\u0103tit s\u0103 r\u0103spund.<br \/>\n<br \/>Sursa: <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.2.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\/ro\/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.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\/ro\/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 pentru cei mai mici. Partea 5. Configurarea echilibratorului de Sarcini | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/31817","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=31817"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/31817\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/23693"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=31817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=31817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=31817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}