{"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\/sq\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","title":{"rendered":"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" 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\/\">Pjesa e par\u00eb. Hyrja<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441026\/\">Pjesa e dyt\u00eb. Konfigurimi i rregullave Firewall dhe NAT<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441882\/\">Pjesa e tret\u00eb. Konfigurimi i DHCP<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/444644\/\">Pjesa e kat\u00ebrt. Konfigurimi i Routingut<\/a><\/noindex><\/p>\n<p>Her\u00ebn e kaluar fol\u00ebm p\u00ebr mund\u00ebsit\u00eb e NSX Edge n\u00eb lidhje me routingun statik dhe dinamik, dhe sot do t\u00eb shqyrtojm\u00eb balancuesin.<br \/>\nPara se t\u00eb fillojm\u00eb konfigurimin, do t\u00eb doja t\u00eb p\u00ebrmendja shkurtimisht llojet kryesore t\u00eb balancimit. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Teoria<\/h3>\n<p>\nT\u00eb gjitha zgjidhjet e sotme p\u00ebr balancimin e ngarkes\u00ebs zakonisht ndahen n\u00eb dy kategori: balancimi n\u00eb nivelin e kat\u00ebrt (transport) dhe balancimi n\u00eb nivelin e shtat\u00eb (aplikativ) t\u00eb modelit <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>. Modeli OSI nuk \u00ebsht\u00eb pik\u00eb reference e shkelqyer kur flasim p\u00ebr metodat e balancimit. P\u00ebr shembull, n\u00ebse nj\u00eb balancues L4 gjithashtu mb\u00ebshtet terminimin TLS, a b\u00ebhet ai me k\u00ebt\u00eb rast nj\u00eb balancues L7? Por kjo \u00ebsht\u00eb situata.<\/p>\n<ul>\n<li><b>Balancuesi L4 <\/b>zakonisht p\u00ebrb\u00ebn nj\u00eb proxy n\u00eb mes t\u00eb klientit dhe nj\u00eb grupi t\u00eb disponuesh\u00ebm backend, i cili terminon lidhjet TCP (do t\u00eb thot\u00eb, p\u00ebrgjigjet vet\u00eb ndaj SYN), zgjedh backend dhe inicon nj\u00eb seanc\u00eb t\u00eb re TCP n\u00eb drejtim t\u00eb tij, duke d\u00ebrguar vet\u00eb SYN. Ky tip \u00ebsht\u00eb nj\u00eb nga bazik\u00ebt, jan\u00eb t\u00eb mundshme dhe variante t\u00eb tjera.<\/li>\n<li><b>Balancuesi L7<\/b> distribuon trafikun tek backendet e disponueshme m\u00eb \"sofistikuar\" se \u00e7far\u00eb b\u00ebn balancuesi L4. Ai mund t\u00eb marr\u00eb vendime mbi zgjedhjen e backendit n\u00eb baz\u00eb, p\u00ebr shembull, t\u00eb p\u00ebrmbajtjes s\u00eb mesazhit HTTP (URL, cookie etj.).<\/li>\n<\/ul>\n<p>\nPavar\u00ebsisht nga tipi, balancuesi mund t\u00eb mb\u00ebshtes\u00eb funksione t\u00eb tjera si:<\/p>\n<ul>\n<li> Zbulimi i sh\u00ebrbimeve \u2013 procesi i identifikimit t\u00eb grupit t\u00eb backendave t\u00eb disponuesh\u00ebm (Static, DNS, Consul, Etcd etj.).<\/li>\n<li>Kontrolli i disponueshm\u00ebris\u00eb s\u00eb backendave t\u00eb zbuluar (ping aktiv t\u00eb backendit me k\u00ebrkes\u00eb HTTP, zbulimi pasiv i problemeve n\u00eb lidhjet TCP, prania n\u00eb p\u00ebrgjigje t\u00eb disa kodeve HTTP 503 nj\u00ebpasnj\u00ebsh\u00ebm etj.).<\/li>\n<li>Vet\u00eb balancimi (round robin, zgjedhje rast\u00ebsore, hash i IP burimit, URI).<\/li>\n<li>Terminimi TLS dhe verifikimi i certifikatat.<\/li>\n<li>Opsionet e lidhura me sigurin\u00eb (autentikimi, parandalimi i sulmeve DoS, kufizimi i shpejt\u00ebsis\u00eb) dhe shum\u00eb t\u00eb tjera.<\/li>\n<\/ul>\n<p>\nNSX Edge ofron mb\u00ebshtetje p\u00ebr dy moda t\u00eb vendosjes s\u00eb balancuesit:<\/p>\n<p><b>Rejimi proxy, ose one-arm<\/b>. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, NSX Edge, kur d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb te nj\u00eb nga backend-et, p\u00ebrdor adres\u00ebn e tij IP si adres\u00ebn burimore. K\u00ebshtu, balancuesi kryen nj\u00ebkoh\u00ebsisht funksionet Source dhe Destination NAT. Backend-i e sheh t\u00eb gjith\u00eb trafikun si t\u00eb d\u00ebrguar nga balancuesi dhe i p\u00ebrgjigjet drejtp\u00ebrs\u00ebdrejti atij. N\u00eb nj\u00eb skem\u00eb t\u00eb till\u00eb, balancuesi duhet t\u00eb jet\u00eb n\u00eb t\u00eb nj\u00ebjtin segment rrjeti me serverat e brendsh\u00ebm.<\/p>\n<p>Ja si ndodh:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0P\u00ebrdoruesi d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb p\u00ebr adres\u00ebn VIP (adres\u00ebn e balancuesit), e cila \u00ebsht\u00eb e konfiguruar n\u00eb Edge.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge zgjedh nj\u00eb nga backend-et dhe kryen destination NAT, duke z\u00ebvend\u00ebsuar adres\u00ebn VIP me adres\u00ebn e backend-it t\u00eb zgjedhur.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge kryen source NAT, duke z\u00ebvend\u00ebsuar adres\u00ebn e p\u00ebrdoruesit q\u00eb d\u00ebrgoi k\u00ebrkes\u00ebn me adres\u00ebn e tij.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Paketa d\u00ebrgohet te backend-i i zgjedhur.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Backend-i p\u00ebrgjigjet jo drejtp\u00ebrs\u00ebdrejti p\u00ebrdoruesit, por Edge-it, pasi adresa fillestare e p\u00ebrdoruesit u ndryshua n\u00eb adres\u00ebn e balancuesit.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge kalon p\u00ebrgjigjen e serverit te p\u00ebrdoruesi.<br \/>\nSkema m\u00eb posht\u00eb.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/a6073ec63f7aca05d61c5a40de2ba6be.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Re\u017eimi transparent ose inline.<\/b> N\u00eb k\u00ebt\u00eb skenar, balancuesi ka nd\u00ebrfaqe n\u00eb rrjetin e brendsh\u00ebm dhe t\u00eb jasht\u00ebm. N\u00eb k\u00ebt\u00eb rast, nuk ka qasje t\u00eb drejtp\u00ebrdrejt\u00eb n\u00eb rrjetin e brendsh\u00ebm nga jasht\u00eb. Balancuesi i ngarkes\u00ebs vepron si nj\u00eb gateway NAT p\u00ebr makinat virtuale n\u00eb rrjetin e brendsh\u00ebm.<\/p>\n<p>Mekanizmi \u00ebsht\u00eb si vijon:<br \/>\n1. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0P\u00ebrdoruesi d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb p\u00ebr adres\u00ebn VIP (adres\u00ebn e balancuesit), e cila \u00ebsht\u00eb e konfiguruar n\u00eb Edge.<br \/>\n2. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge zgjedh nj\u00eb nga backend-et dhe kryen destination NAT, duke z\u00ebvend\u00ebsuar adres\u00ebn VIP me adres\u00ebn e backend-it t\u00eb zgjedhur.<br \/>\n3. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Paketa d\u00ebrgohet te backend-i i zgjedhur.<br \/>\n4. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Backend-i merr k\u00ebrkes\u00ebn me adres\u00ebn fillestare t\u00eb p\u00ebrdoruesit (source NAT nuk \u00ebsht\u00eb kryer) dhe i p\u00ebrgjigjet asaj drejtp\u00ebrs\u00ebdrejti.<br \/>\n5. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Trafiku p\u00ebrs\u00ebri merret nga balancuesi i ngarkes\u00ebs, pasi n\u00eb skem\u00ebn inline ai zakonisht vepron si gateway i parazgjedhur p\u00ebr ferm\u00ebn e server\u00ebve.<br \/>\n6. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Edge kryen source NAT p\u00ebr t\u00eb d\u00ebrguar trafikun te p\u00ebrdoruesi, duke p\u00ebrdorur VIP-in e tij si adres\u00eb IP burimore.<br \/>\nSkema m\u00eb posht\u00eb.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/9ad9adcac02d40db1603aee84387264a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Praktika<\/h3>\n<p>\nN\u00eb skenarin tim t\u00eb testimit, jan\u00eb konfiguruar 3 server\u00eb me Apache, i cili \u00ebsht\u00eb konfiguruar p\u00ebr t\u00eb punuar p\u00ebrmes HTTPS. Edge do t\u00eb kryej\u00eb balancimin e k\u00ebrkesave HTTPS sipas metod\u00ebs round robin, duke proxy-uar \u00e7do k\u00ebrkes\u00eb t\u00eb re n\u00eb nj\u00eb server t\u00eb ri.<br \/>\nLe t\u00eb fillojm\u00eb.<\/p>\n<p><b>Krijojm\u00eb nj\u00eb certifikat\u00eb SSL, e cila do t\u00eb p\u00ebrdoret nga NSX Edge<\/b><br \/>\nMund t\u00eb importoni nj\u00eb certifikat\u00eb valide CA ose t\u00eb p\u00ebrdorni nj\u00eb t\u00eb vet\u00ebshkruar. N\u00eb k\u00ebt\u00eb test, un\u00eb do t\u00eb p\u00ebrdor nj\u00eb t\u00eb vet\u00ebshkruar.<\/p>\n<ol>\n<li>N\u00eb nd\u00ebrfaqen e vCloud Director kalojm\u00eb n\u00eb konfigurimet e sh\u00ebrbimeve Edge.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/df9be9f6d5b92af1cbe19f40459c8d9f.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Kalojm\u00eb n\u00eb sked\u00ebn Certifikatat. Nga lista e veprimeve zgjedhim shtimin e nj\u00eb CSR t\u00eb ri.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/72185bf69cb0c4d8dc0cbadc8fe4f376.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Plotni fushat e nevojshme dhe klikoni mbi Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/196394d4633d76dfde6d89b8f7049e19.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Zgjidhni CSR-n\u00eb e sapor krijuar dhe zgjidhni opsionin self-sign CSR.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/262e7a1ede8bda39a9ee098f360a38e3.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Zgjidhni periudh\u00ebn e vlefshm\u00ebris\u00eb t\u00eb certifikat\u00ebs dhe klikoni mbi Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/6c880218fd7874652e6540a0bde18310.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Certifikata e vet\u00eb-n\u00ebnshkruar u shfaq n\u00eb list\u00ebn e atyre q\u00eb jan\u00eb n\u00eb dispozicion.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/f065f461da8f96ca31c96d3c801350ec.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Konfigurojm\u00eb Profilin e Aplikacionit<\/b><br \/>\nProfilat e aplikacion\u00ebve ofrojn\u00eb kontroll m\u00eb t\u00eb plot\u00eb mbi trafikun n\u00eb rrjet dhe e b\u00ebjn\u00eb menaxhimin e tij t\u00eb thjesht\u00eb dhe efektiv. Me ndihm\u00ebn e tyre, mund t\u00eb p\u00ebrcaktojm\u00eb sjelljen p\u00ebr lloje t\u00eb ve\u00e7anta t\u00eb trafik. <\/p>\n<ol>\n<li>Kalo n\u00eb sked\u00ebn Load Balancer dhe aktivizo balancuesin. Opsioni Acceleration enabled k\u00ebtu lejon balancuesin t\u00eb p\u00ebrdor\u00eb balancimin m\u00eb t\u00eb shpejt\u00eb L4 n\u00eb vend t\u00eb L7.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/1ee064e2fe234fb1d96ec327f3f92f05.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Kalo n\u00eb sked\u00ebn Application profile p\u00ebr t\u00eb vendosur profilin e aplikacionit. Klikoni +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/5686a86bdff4d973f33f1a9d362ad273.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vendosni emrin e profilit dhe zgjidhni llojin e trafik q\u00eb do t\u00eb aplikohet p\u00ebr profilin. Do t\u00eb shpjegoj disa parametra.<br \/>\n<b>Persistenc\u00eb<\/b> \u2013 ruan dhe ndjek t\u00eb dh\u00ebnat e sesionit, p\u00ebr shembull: cili server i ve\u00e7ant\u00eb nga grupi sh\u00ebrben k\u00ebrkes\u00ebn e p\u00ebrdoruesit. Kjo garanton q\u00eb k\u00ebrkesat e p\u00ebrdoruesit d\u00ebrgohen n\u00eb t\u00eb nj\u00ebjtin an\u00ebtar t\u00eb grupit gjat\u00eb gjith\u00eb jet\u00ebs s\u00eb sesionit ose sesioneve t\u00eb ardhshme.<br \/>\n<b>Aktivizo SSL passthrough<\/b> \u2013 duke zgjedhur k\u00ebt\u00eb opsion, NSX Edge ndalon terminimin e SSL. N\u00eb vend t\u00eb k\u00ebsaj, terminimi ndodh direkt n\u00eb serverat p\u00ebr t\u00eb cil\u00ebt kryhet balancimi.<br \/>\n<b>Shto header-in X-Forwarded-For HTTP<\/b> \u2013 lejon p\u00ebrcaktimin e IP-n\u00eb origjinale t\u00eb klientit, q\u00eb lidhet me serverin e uebit n\u00ebp\u00ebrmjet balancuesit.<br \/>\n<b>Aktivizo SSL n\u00eb an\u00ebn e grupit<\/b> \u2013 lejon ta p\u00ebrshkruash se grupi i zgjedhur p\u00ebrb\u00ebhet nga servera HTTPS.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/81fa688f063f5cf1719461884bbb8dc2.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Pasi do t\u00eb balancoj trafik HTTPS, duhet t\u00eb aktivizoj SSL-n\u00eb n\u00eb an\u00ebn e grupit dhe t\u00eb zgjidh nj\u00eb certifikat\u00eb t\u00eb krijuar m\u00eb par\u00eb n\u00eb sked\u00ebn Virtual Server Certificates \u2014&gt; Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/d2585bcc33e57adc561bc5d956057479.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>E nj\u00ebjta gj\u00eb p\u00ebr Pool Certificates \u2014&gt; Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/b565acf03e4eba313b4624a912310663.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Krijo nj\u00eb grup serverash, trafik p\u00ebr t\u00eb cil\u00ebt do t\u00eb balancohet<\/b><\/p>\n<ol>\n<li>Kalo n\u00eb sked\u00ebn Pools. Klikoni +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/e3fd9f747f3cbc43f3d348c05ece07fd.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Vendosni emrin e grupit, zgjidhni algoritmin (do t\u00eb p\u00ebrdor round robin) dhe llojin e monitorimit p\u00ebr kontrollin e sh\u00ebndetit t\u00eb backendit. Opsioni Transparent tregon n\u00ebse IP-t\u00eb origjinale t\u00eb klient\u00ebve jan\u00eb t\u00eb dukshme p\u00ebr serverat e brendsh\u00ebm.\n<ul>\n<li>N\u00ebse opsioni \u00ebsht\u00eb i \u00e7aktivizuar, trafiku p\u00ebr serverat e brendsh\u00ebm shkon me IP-n\u00eb origjinale t\u00eb balancuesit.\n<\/li>\n<li> N\u00ebse opsioni \u00ebsht\u00eb aktivizuar, serverat e brendsh\u00ebm shohin IP-n\u00eb origjinale t\u00eb klient\u00ebve. N\u00eb nj\u00eb konfigurim t\u00eb till\u00eb, NSX Edge duhet t\u00eb veproj\u00eb si gateway-i i parazgjedhur p\u00ebr t\u00eb siguruar q\u00eb paketat e kthimit kalojn\u00eb n\u00ebp\u00ebr NSX Edge.<\/li>\n<\/ul>\n<p>NSX mb\u00ebshtet algoritmet e m\u00ebposhtme t\u00eb balancimit:<\/p>\n<ul>\n<li><b>IP_HASH<\/b> \u2013 zgjedhja e serverit n\u00eb baz\u00eb t\u00eb rezultateve t\u00eb funksionit hash p\u00ebr IP-n\u00eb source dhe destination t\u00eb \u00e7do pakete.<\/li>\n<li> <b>LEASTCONN <\/b>\u2013 balancimi i lidhjeve t\u00eb ardhshme, n\u00eb var\u00ebsi t\u00eb numrit t\u00eb lidhjeve q\u00eb tashm\u00eb ekzistojn\u00eb n\u00eb serverin p\u00ebrkat\u00ebs. Lidhjet e reja do t\u00eb d\u00ebrgohen n\u00eb serverin me numrin m\u00eb t\u00eb vog\u00ebl t\u00eb lidhjeve.<\/li>\n<li> <b>ROUND_ROBIN <\/b>\u2013 lidhjet e reja d\u00ebrgohen n\u00eb \u00e7do server n\u00eb m\u00ebnyr\u00eb t\u00eb rregullt, n\u00eb p\u00ebrputhje me pesh\u00ebn q\u00eb i \u00ebsht\u00eb caktuar.<\/li>\n<li><b>URI<\/b> \u2013 pjesa e majt\u00eb e URI (deri te pika e pyetjeve) hash-it dhe ndahet n\u00eb pesh\u00ebn totale t\u00eb server\u00ebve n\u00eb grup. Rezultati tregon se cili server merr k\u00ebrkes\u00ebn, duke garantuar q\u00eb k\u00ebrkesa gjithmon\u00eb d\u00ebrgohet n\u00eb t\u00eb nj\u00ebjtin server, p\u00ebr sa koh\u00eb q\u00eb t\u00eb gjith\u00eb server\u00ebt mbeten t\u00eb aksesuesh\u00ebm.<\/li>\n<li><b>HTTPHEADER <\/b>\u2013 balancimi n\u00eb baz\u00eb t\u00eb nj\u00eb header-i t\u00eb caktuar HTTP, i cili mund t\u00eb vihet si parametrik. N\u00ebse header-i mungon ose nuk ka ndonj\u00eb vler\u00eb, aplikohet algoritmi ROUND_ROBIN.<\/li>\n<li><b>URL <\/b>\u2013 n\u00eb \u00e7do k\u00ebrkes\u00eb HTTP GET, b\u00ebhet nj\u00eb k\u00ebrkim mbi parametrin e URL-s\u00eb, t\u00eb caktuar si argument. N\u00ebse pas parametrin ka nj\u00eb barazim dhe vler\u00eb, at\u00ebher\u00eb vlera hash-it dhe ndahet n\u00eb pesh\u00ebn totale t\u00eb server\u00ebve t\u00eb aktivizuar. Rezultati tregon se cili server merr k\u00ebrkes\u00ebn. Ky proces p\u00ebrdoret p\u00ebr t\u00eb ndjekur identifikuesit e p\u00ebrdoruesve n\u00eb k\u00ebrkesa dhe p\u00ebr t\u00eb siguruar q\u00eb id e nj\u00ebsoj p\u00ebrdoruesi gjithmon\u00eb d\u00ebrgohet n\u00eb t\u00eb nj\u00ebjtin server, p\u00ebr sa koh\u00eb q\u00eb t\u00eb gjith\u00eb server\u00ebt mbeten t\u00eb aksesuesh\u00ebm.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/ab98325a49a63d1d005839a47af39544.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>N\u00eb pjes\u00ebn Members kliko + p\u00ebr t\u00eb shtuar server\u00eb n\u00eb grup.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/f67e7567c48a6403bb5dcd165d150052.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nK\u00ebtu duhet t\u00eb tregoni:<\/p>\n<ul>\n<li>emrin e serverit;<\/li>\n<li>IP-adres\u00ebn e serverit;<\/li>\n<li>portin, n\u00eb t\u00eb cilin serveri do t\u00eb marr\u00eb trafik;<\/li>\n<li>portin p\u00ebr kontrollin sh\u00ebndet\u00ebsor (Monitor healthcheck); <\/li>\n<li>pesh\u00ebn (Weight) \u2013 me k\u00ebt\u00eb parameter mund t\u00eb rregulloni sasin\u00eb proporcionale t\u00eb trafikut t\u00eb marr\u00eb p\u00ebr \u00e7do an\u00ebtar t\u00eb grupit;<\/li>\n<li>Max Connections \u2013 numri maksimal i lidhjeve n\u00eb server;<\/li>\n<li>Min Connections \u2013 numri minimal i lidhjeve q\u00eb duhet t\u00eb p\u00ebrpunoj\u00eb serveri, para se trafiku t\u00eb redirektohet te an\u00ebtari tjet\u00ebr i grupit.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/4bfd6de65e50cb417845d358b11b91b5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nK\u00ebshtu duket grupi p\u00ebrfundimtar i tre server\u00ebve.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/42ebe47da99599628d9e6e75289a9f25.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Shtojm\u00eb Virtual Server<\/b><\/p>\n<ol>\n<li>Kalo n\u00eb kartel\u00ebn Virtual Servers. Kliko +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/4d95be098f50055d81f538ebe565cfbb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Aktivizoni serverin virtual me Enable Virtual Server.<br \/>\nI p\u00ebrcaktojm\u00eb emrin, zgjedhim Application Profile, Pool t\u00eb krijuar m\u00eb par\u00eb dhe \u00e7ojm\u00eb IP-n\u00eb e adres\u00ebs ku Serveri Virtual do t\u00eb pranoj\u00eb k\u00ebrkesat nga jasht\u00eb. T\u00eb cilat jan\u00eb protokolli HTTPS dhe porta 443.<br \/>\nParametrat opsional\u00eb k\u00ebtu:<br \/>\n<b>Limiti i lidhjes <\/b>\u2013 numri maksimal i lidhjeve t\u00eb p\u00ebrkohshme q\u00eb mund t\u00eb p\u00ebrpunoj\u00eb serveri virtual;<br \/>\n<b>Limiti i ritmit t\u00eb lidhjes (CPS)<\/b> \u2013 numri maksimal i k\u00ebrkesave t\u00eb reja q\u00eb i pranohen n\u00eb sekond\u00eb.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/fae8dff378af917a96b9a7d887bb2bd8.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>Me k\u00ebt\u00eb, konfigurimi i balancuesit p\u00ebrfundon, mund t\u00eb kontrollojm\u00eb funksionalitetin e tij. Serverat kan\u00eb nj\u00eb konfigurim t\u00eb thjesht\u00eb, e cila lejon t\u00eb kuptojm\u00eb se cili server nga pool-i ka procesuar k\u00ebrkes\u00ebn. Gjat\u00eb konfigurimit, ne zgjodh\u00ebm algoritmin e balancimit Round Robin, dhe parametri Weight p\u00ebr \u00e7do server \u00ebsht\u00eb nj\u00eb, k\u00ebshtu q\u00eb \u00e7do k\u00ebrkes\u00eb e ardhshme do t\u00eb p\u00ebrpunoj\u00eb serverin pasues nga pool-i.<br \/>\nShkruajm\u00eb n\u00eb shfletues adres\u00ebn e jashtme t\u00eb balancuesit dhe shohim:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/e10d1c9eb14b42f4f6fc03a0d6f03013.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPasi t\u00eb p\u00ebrdit\u00ebsohet faqja, k\u00ebrkesa do t\u00eb p\u00ebrpunoj\u00eb serverin pasues:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/09a67549ca2f05f835a2d4645779bfa1.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDhe nj\u00eb her\u00eb tjet\u00ebr \u2013 p\u00ebr t\u00eb kontrolluar dhe serverin e tret\u00eb nga pool-i:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/e0452323822ff0a3e02ff5bcee53bcdc.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nGjat\u00eb kontrollit, mund t\u00eb shohim se certifikata, e cila na d\u00ebrgon Edge, \u00ebsht\u00eb ajo e cila u gjenerua n\u00eb fillim. <\/p>\n<p>Kontrollimi i statusit t\u00eb balancuesit nga konsola e Gateway-it Edge. P\u00ebr k\u00ebt\u00eb, shkruani <b>show service loadbalancer pool<\/b>. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/10a7421dc6278ba2c721187bfeb076a9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Konfigurojm\u00eb Monitorin e Sh\u00ebrbimeve p\u00ebr t\u00eb kontrolluar gjendjen e server\u00ebve n\u00eb pool <\/b><br \/>\nMe ndihm\u00ebn e Monitorit t\u00eb Sh\u00ebrbimeve, ne mund t\u00eb mbik\u00ebqyrim gjendjen e server\u00ebve n\u00eb pool-in e bllokuar. N\u00ebse p\u00ebrgjigjja n\u00eb k\u00ebrkes\u00eb nuk p\u00ebrputhet me at\u00eb t\u00eb pritur, serveri mund t\u00eb p\u00ebrjashtohet nga pool-i, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb mos pranoj\u00eb k\u00ebrkesa t\u00eb reja.<br \/>\nN\u00eb parazgjedhje jan\u00eb konfiguruar tre metoda kontrolli:<\/p>\n<ul>\n<li> TCP-monitor,<\/li>\n<li> HTTP-monitor,<\/li>\n<li> HTTPS-monitor.<\/li>\n<\/ul>\n<p>\nKrijojm\u00eb nj\u00eb t\u00eb re. <\/p>\n<ol>\n<li>Kalojm\u00eb n\u00eb tab-in e Monitorimit t\u00eb Sh\u00ebrbimeve, shtypim +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/ceac4fac8197b395d7531391534ad4ff.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Zgjedhim:\n<ul>\n<li>emrin p\u00ebr metod\u00ebn e re;<\/li>\n<li>intervalin me t\u00eb cilin do t\u00eb d\u00ebrgohen k\u00ebrkesat, <\/li>\n<li>koh\u00ebn e pritjes p\u00ebr p\u00ebrgjigjen, <\/li>\n<li>tipin e monitorimit \u2013 k\u00ebrkes\u00eb HTTPS duke p\u00ebrdorur metod\u00ebn GET, kodin e pritur t\u00eb statusit \u2013 200(OK) dhe URL-n\u00eb e k\u00ebrkes\u00ebs.<\/li>\n<\/ul>\n<\/li>\n<li>Me k\u00ebt\u00eb, konfigurimi i Monitorit t\u00eb Sh\u00ebrbimeve t\u00eb ri p\u00ebrfundon, tani mund ta p\u00ebrdorim at\u00eb gjat\u00eb krijimit t\u00eb pool-it. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/9db2263d6e5c90e1a5aba6cee865fd50.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Konfigurojm\u00eb Rregullat e Aplikacioneve<\/b><\/p>\n<p>Rregullat e Aplikacioneve \u2013 nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb manipuluar trafikun, e bazuar n\u00eb disa triggerr. Me k\u00ebt\u00eb mjet mund t\u00eb krijojm\u00eb rregulla t\u00eb avancuara p\u00ebr balancimin e ngarkesave, konfigurimi i t\u00eb cilave mund t\u00eb jet\u00eb i pamundur p\u00ebrmes profileve t\u00eb Aplikacioneve ose sh\u00ebrbimeve t\u00eb tjera t\u00eb disponueshme n\u00eb Gateway-in Edge.<\/p>\n<ol>\n<li>P\u00ebr t\u00eb krijuar nj\u00eb rregull, kalojm\u00eb n\u00eb sked\u00ebn Rregullat e Aplikacionit t\u00eb balancuesit.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/b370858e444c144c95fe0d89d3ea42da.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Zgjidhni emrin, skriptin q\u00eb do t\u00eb p\u00ebrdor\u00eb rregulli, dhe kliko n\u00eb Ruaj.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/e0af1a95fb5b5bba46a52e582eba62bb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Pasi t\u00eb krijohet rregulli, na nevojitet t\u00eb redaktojm\u00eb Serverin Virtual t\u00eb konfiguruesh\u00ebm.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/c4617150f17e8e16cde94a9c3fb8e713.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>N\u00eb sked\u00ebn Avancuar, shtojm\u00eb rregullin q\u00eb krijuam.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX p\u00ebr t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs\" src=\"\/wp-content\/uploads\/2019\/04\/23f4ed5bb90bf178fec825e552fba8a6.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>N\u00eb shembullin e m\u00ebsip\u00ebrm, aktivizuam mb\u00ebshtetje p\u00ebr tlsv1.<\/p>\n<p>Disa shembuj t\u00eb tjer\u00eb:<\/p>\n<p>Rredirectimi i trafikut n\u00eb nj\u00eb grup tjet\u00ebr.<br \/>\nMe k\u00ebt\u00eb skript mund t\u00eb drejtojm\u00eb trafikun n\u00eb nj\u00eb grup tjet\u00ebr balancimi n\u00ebse grupi kryesor nuk funksionon. P\u00ebr t\u00eb vepruar rregulli, balancuesi duhet t\u00eb ket\u00eb disa grupe t\u00eb konfiguruara dhe t\u00eb gjitha an\u00ebtar\u00ebt e grupit kryesor duhet t\u00eb jen\u00eb n\u00eb gjendje down. Duhet t\u00eb specifikohet emri i grupit, jo ID-ja e tij.<\/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>Rredirectimi i trafikut n\u00eb nj\u00eb burim t\u00eb jasht\u00ebm.<br \/>\nK\u00ebtu ne drejtojm\u00eb trafikun n\u00eb nj\u00eb uebfaqe t\u00eb jashtme, n\u00ebse t\u00eb gjith\u00eb pjes\u00ebmarr\u00ebsit e grupit kryesor jan\u00eb n\u00eb gjendje 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>Edhe m\u00eb shum\u00eb shembuj <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\">k\u00ebtu<\/a><\/noindex>.<\/p>\n<p>K\u00ebtu p\u00ebr balancuesin kam p\u00ebrfunduar. N\u00ebse keni pyetje, pyetni, jam gati t\u00eb p\u00ebrgjigjem.<br \/>\n<br \/>Burimi: <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 - 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\/sq\/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\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\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\/sq\/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 p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa 5. Konfigurimi i balancuesit t\u00eb ngarkes\u00ebs | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/31817","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=31817"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/31817\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/23693"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=31817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=31817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=31817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}