{"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\/en\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","title":{"rendered":"VMware NSX for the smallest. Part 5. Configuring the load balancer","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" 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\/\">Part One. Introduction<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441026\/\">Part Two. Configuring Firewall and NAT Rules<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/441882\/\">Part Three. DHCP Configuration<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/444644\/\">Part Four. Routing Configuration<\/a><\/noindex><\/p>\n<p>Last time we discussed the capabilities of NSX Edge concerning both static and dynamic routing, and today we will dive into load balancing.<br \/>\nBefore we begin with the configuration, I would like to briefly remind you of the main types of load balancing. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Theory<\/h3>\n<p>\nCurrent load balancing solutions are typically divided into two categories: Layer 4 (transport layer) and Layer 7 (application layer) load balancing. <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>The OSI model is not the best reference point when describing load balancing methods. For example, if an L4 load balancer also supports TLS termination, does it then become an L7 load balancer? That's one of the questions.<\/p>\n<ul>\n<li><b>L4 Load Balancer <\/b>is often a middle proxy positioned between the client and a set of available backends, which terminates TCP connections (i.e., responds to SYN), selects a backend, and initiates a new TCP session towards it, sending a SYN on its own. This type is one of the basics, though there are other variations.<\/li>\n<li><b>L7 Load Balancer<\/b> distributes traffic to available backends in a more sophisticated manner than an L4 load balancer. It can make backend selection decisions based on, for instance, the content of an HTTP message (URL, cookies, etc.).<\/li>\n<\/ul>\n<p>\nRegardless of the type, a load balancer can support the following features:<\/p>\n<ul>\n<li> Service discovery \u2014 the process of determining the available backend set (Static, DNS, Consul, Etcd, etc.).<\/li>\n<li>Health checks of discovered backends (active 'ping' of a backend using HTTP requests, passive detection of issues in TCP connections, the presence of several consecutive 503 HTTP codes in responses, etc.).<\/li>\n<li>The load balancing itself (round-robin, random selection, source IP hash, URI).<\/li>\n<li>TLS termination and certificate verification.<\/li>\n<li>Security-related options (authentication, DoS attack prevention, rate limiting) and much more.<\/li>\n<\/ul>\n<p>\nNSX Edge offers support for two deployment modes of the load balancer:<\/p>\n<p><b>Proxy mode, or one-arm<\/b>In this mode, NSX Edge uses its IP address as the source address when sending a request to one of the backends. Thus, the load balancer performs both Source and Destination NAT functions simultaneously. The backend sees all traffic as coming from the load balancer and responds directly to it. In this configuration, the load balancer must be on the same network segment as the internal servers.<\/p>\n<p>Here's how it works:<br \/>\n1. The user sends a request to the VIP address (the address of the load balancer) configured on Edge.<br \/>\n2. Edge selects one of the backends and performs destination NAT, replacing the VIP address with the address of the selected backend.<br \/>\n3. Edge performs source NAT, replacing the requester's address with its own.<br \/>\n4. The packet is sent to the selected backend.<br \/>\n5. The backend does not respond directly to the user, but to Edge, since the original user's address has been changed to that of the load balancer.<br \/>\n6. Edge forwards the server's response to the user.<br \/>\nSee the diagram below.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/a6073ec63f7aca05d61c5a40de2ba6be.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Transparent or inline mode.<\/b> In this scenario, the load balancer has interfaces in both the internal and external networks. There is no direct access to the internal network from the outside. The built-in load balancer acts as a NAT gateway for virtual machines within the internal network.<\/p>\n<p>The mechanism is as follows:<br \/>\n1. The user sends a request to the VIP address (the address of the load balancer) configured on Edge.<br \/>\n2. Edge selects one of the backends and performs destination NAT, replacing the VIP address with the address of the selected backend.<br \/>\n3. The packet is sent to the selected backend.<br \/>\n4. The backend receives the request with the original user's address (source NAT was not performed) and responds directly to it.<br \/>\n5. The traffic is again received by the load balancer since, in inline mode, it typically serves as the default gateway for the server farm.<br \/>\n6. Edge performs source NAT to send traffic to the user, using its VIP as the source IP address.<br \/>\nSee the diagram below.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/9ad9adcac02d40db1603aee84387264a.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Practice<\/h3>\n<p>\nOn my test setup, 3 Apache servers are configured to operate over HTTPS. Edge will balance HTTPS requests using a round-robin method, proxying each new request to a new server.<br \/>\nLet's get started.<\/p>\n<p><b>Generate an SSL certificate that will be used by NSX Edge.<\/b><br \/>\nYou can import a valid CA certificate or use a self-signed one. In this test, I will use a self-signed certificate.<\/p>\n<ol>\n<li>In the vCloud Director interface, go to the Edge service settings.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/df9be9f6d5b92af1cbe19f40459c8d9f.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Go to the Certificates tab. From the actions list, select to add a new CSR.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/72185bf69cb0c4d8dc0cbadc8fe4f376.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Fill in the necessary fields and click Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/196394d4633d76dfde6d89b8f7049e19.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Select the newly created CSR and choose the self-sign CSR option.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/262e7a1ede8bda39a9ee098f360a38e3.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Choose the validity period for the certificate and click Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/6c880218fd7874652e6540a0bde18310.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>The self-signed certificate has appeared in the list of available certificates.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/f065f461da8f96ca31c96d3c801350ec.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Configure the Application Profile.<\/b><br \/>\nApplication profiles provide more comprehensive control over network traffic, making management simple and effective. They allow you to define the behavior for specific types of traffic. <\/p>\n<ol>\n<li>Go to the Load Balancer tab and enable the balancer. The Acceleration enabled option here allows the balancer to use faster L4 balancing instead of L7.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/1ee064e2fe234fb1d96ec327f3f92f05.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Go to the Application profile tab to define the application profile. Click +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/5686a86bdff4d973f33f1a9d362ad273.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Set the profile name and select the type of traffic for which the profile will be applied. Let me explain some parameters.<br \/>\n<b>Persistence<\/b> \u2013 retains and tracks session data, for example: which specific server from the pool is handling the user request. This ensures that user requests are directed to the same pool member throughout the session or across subsequent sessions.<br \/>\n<b>Enable SSL passthrough<\/b> \u2013 selecting this option means that NSX Edge stops terminating SSL. Instead, termination happens directly on the servers being load balanced.<br \/>\n<b>Insert X-Forwarded-For HTTP header<\/b> \u2013 allows determination of the original client IP address connecting to the web server through the balancer.<br \/>\n<b>Enable Pool Side SSL<\/b> \u2013 indicates that the selected pool consists of HTTPS servers.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/81fa688f063f5cf1719461884bbb8dc2.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Since I will be balancing HTTPS traffic, I need to enable Pool Side SSL and select the previously generated certificate under the Virtual Server Certificates tab \u2192 Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/d2585bcc33e57adc561bc5d956057479.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Similarly for Pool Certificates \u2192 Service Certificate.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/b565acf03e4eba313b4624a912310663.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Create a pool of servers for which traffic will be balanced Pools<\/b><\/p>\n<ol>\n<li>Go to the Pools tab. Click +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/e3fd9f747f3cbc43f3d348c05ece07fd.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Set the pool name, choose the algorithm (I will use round robin) and the monitoring type for the backend health check. The Transparent option indicates whether the original source IP of clients is visible to internal servers.\n<ul>\n<li>If the option is disabled, traffic for internal servers comes with the source IP of the balancer.\n<\/li>\n<li> If the option is enabled, internal servers see the source IP of the clients. In such a configuration, NSX Edge must act as the default gateway to ensure that returned packets go through NSX Edge.<\/li>\n<\/ul>\n<p>NSX supports the following load balancing algorithms:<\/p>\n<ul>\n<li><b>IP_HASH<\/b> \u2013 server selection based on the results of a hash function for the source and destination IP of each packet.<\/li>\n<li> <b>LEASTCONN <\/b>\u2013 load balancing of incoming connections based on the number of connections already established on a specific server. New connections will be directed to the server with the least number of connections.<\/li>\n<li> <b>ROUND_ROBIN <\/b>\u2013 new connections are sent to each server in turn, according to its assigned weight.<\/li>\n<li><b>URI<\/b> \u2013 the left part of the URI (before the question mark) is hashed and divided by the total weight of the servers in the pool. The result indicates which server receives the request, ensuring that the request always goes to the same server as long as all servers remain available.<\/li>\n<li><b>HTTPHEADER <\/b>\u2013 load balancing based on a specific HTTP header that can be specified as a parameter. If the header is missing or has no value, the ROUND_ROBIN algorithm is applied.<\/li>\n<li><b>URL <\/b>\u2013 each HTTP GET request looks for the URL parameter specified as an argument. If the parameter is followed by an equal sign and a value, then the value is hashed and divided by the total weight of the running servers. The result indicates which server receives the request. This process is used to track user IDs in requests and ensure that the same user ID is always sent to the same server, as long as all servers remain available.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/ab98325a49a63d1d005839a47af39544.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>In the Members block, click + to add servers to the pool.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/f67e7567c48a6403bb5dcd165d150052.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n1. The address of the Elasticsearch server (set during installation).<\/p>\n<ul>\n<li>server name;<\/li>\n<li>server IP address;<\/li>\n<li>port to which the server will receive traffic;<\/li>\n<li>port for health check (Monitor healthcheck); <\/li>\n<li>weight (Weight) \u2013 this parameter allows you to regulate the proportional amount of traffic received by a specific member of the pool;<\/li>\n<li>Max Connections \u2013 the maximum number of connections to the server;<\/li>\n<li>Min Connections \u2013 the minimum number of connections that the server must handle before traffic is redirected to the next member of the pool.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/4bfd6de65e50cb417845d358b11b91b5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nThis is what the final pool of three servers looks like.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/42ebe47da99599628d9e6e75289a9f25.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Adding Virtual Server<\/b><\/p>\n<ol>\n<li>Go to the Virtual Servers tab. Click +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/4d95be098f50055d81f538ebe565cfbb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Activate the virtual server using Enable Virtual Server.<br \/>\nWe assign it a name, select the previously created Application Profile, Pool, and specify the IP address to which the Virtual Server will accept external requests. We specify the HTTPS protocol and port 443.<br \/>\nOptional parameters here:<br \/>\n<b>Connection Limit <\/b>\u2013 the maximum number of simultaneous connections that the virtual server can handle;<br \/>\n<b>Connection Rate Limit (CPS)<\/b> \u2013 the maximum number of new incoming requests per second.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/fae8dff378af917a96b9a7d887bb2bd8.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>At this point, the configuration of the load balancer is complete, and we can test its functionality. The servers have a simple configuration allowing us to understand which specific server from the pool processed the request. During setup, we selected the Round Robin load balancing algorithm, and the Weight parameter for each server is set to one, so each subsequent request will be handled by the next server in the pool.<br \/>\nWe enter the external address of the load balancer in the browser and see:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/e10d1c9eb14b42f4f6fc03a0d6f03013.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAfter refreshing the page, the request will be processed by the next server:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/09a67549ca2f05f835a2d4645779bfa1.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAnd again \u2013 to check the third server from the pool:<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/e0452323822ff0a3e02ff5bcee53bcdc.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nWhen checking, we can see that the certificate sent to us by Edge is the same one that we generated at the very beginning. <\/p>\n<p>Checking the status of the load balancer from the Edge gateway console. For this, enter <b>show service loadbalancer pool<\/b>. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/10a7421dc6278ba2c721187bfeb076a9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Setting up a Service Monitor to check the status of servers in the pool <\/b><br \/>\nUsing the Service Monitor, we can track the status of the servers in the backend pool. If the response to a request does not match the expected one, the server can be taken out of the pool so that it does not receive any new requests.<br \/>\nBy default, three checking methods are configured:<\/p>\n<ul>\n<li> TCP-monitor,<\/li>\n<li> HTTP-monitor,<\/li>\n<li> HTTPS-monitor.<\/li>\n<\/ul>\n<p>\nLet's create a new one. <\/p>\n<ol>\n<li>We go to the Service Monitoring tab and click +.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/ceac4fac8197b395d7531391534ad4ff.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>We select:\n<ul>\n<li>a name for the new method;<\/li>\n<li>the interval at which requests will be sent, <\/li>\n<li>the timeout waiting for a response, <\/li>\n<li>the monitoring type \u2013 HTTPS request using the GET method, the expected status code \u2013 200(OK) and the request URL.<\/li>\n<\/ul>\n<\/li>\n<li>The setup of the new Service Monitor is now complete, and we can use it when creating a pool. <br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/9db2263d6e5c90e1a5aba6cee865fd50.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p><b>Setting up Application Rules<\/b><\/p>\n<p>Application Rules \u2013 a way to manipulate traffic based on specific triggers. With this tool, we can create advanced load balancing rules, the configuration of which may not be possible through Application profiles or using other services available on the Edge Gateway.<\/p>\n<ol>\n<li>To create a rule, navigate to the Application Rules tab of the load balancer.<br \/>\n <img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/b370858e444c144c95fe0d89d3ea42da.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Select a name, the script that will use the rule, and click Keep.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/e0af1a95fb5b5bba46a52e582eba62bb.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Once the rule is created, we need to edit the already configured Virtual Server.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/c4617150f17e8e16cde94a9c3fb8e713.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>In the Advanced tab, add the rule we created.<br \/>\n<img decoding=\"async\" alt=\"VMware NSX for the smallest. Part 5. Configuring the load balancer\" src=\"\/wp-content\/uploads\/2019\/04\/23f4ed5bb90bf178fec825e552fba8a6.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ol>\n<p>In the example above, we enabled support for tlsv1.<\/p>\n<p>A couple more examples:<\/p>\n<p>Redirecting traffic to another pool.<br \/>\nWith this script, we can redirect traffic to another load balancing pool if the main pool is not functioning. For the rule to take effect, multiple pools should be configured on the load balancer, and all members of the main pool must be in a down state. You need to specify the name of the pool, not its 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>Redirecting traffic to an external resource.<br \/>\nHere we redirect traffic to an external website if all members of the main pool are in a down state.<\/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>Even more examples <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\">here<\/a><\/noindex>.<\/p>\n<p>That's all I have on the load balancer. If you have any questions, feel free to ask; I'm ready to help.<br \/>\n<br \/>Source: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/448540\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0427\u0430\u0441\u0442\u044c \u043f\u0435\u0440\u0432\u0430\u044f. \u0412\u0432\u043e\u0434\u043d\u0430\u044f \u0427\u0430\u0441\u0442\u044c \u0432\u0442\u043e\u0440\u0430\u044f. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u043f\u0440\u0430\u0432\u0438\u043b Firewall \u0438 NAT \u0427\u0430\u0441\u0442\u044c \u0442\u0440\u0435\u0442\u044c\u044f. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 DHCP \u0427\u0430\u0441\u0442\u044c \u0447\u0435\u0442\u0432\u0435\u0440\u0442\u0430\u044f. \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0439 \u0440\u0430\u0437 \u043c\u044b \u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438 \u043e \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044f\u0445 NSX Edge \u0432 \u0440\u0430\u0437\u0440\u0435\u0437\u0435 \u0441\u0442\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0438 \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438, \u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u0431\u0443\u0434\u0435\u043c \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\u0441\u044f \u0441 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u043e\u043c. \u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u0442\u044c \u043a \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0435, \u044f \u0445\u043e\u0442\u0435\u043b \u0431\u044b \u0441\u043e\u0432\u0441\u0435\u043c \u043a\u0440\u0430\u0442\u043a\u043e \u043d\u0430\u043f\u043e\u043c\u043d\u0438\u0442\u044c \u043e\u0431 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u0445 \u0432\u0438\u0434\u0430\u0445 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0438. \u0422\u0435\u043e\u0440\u0438\u044f [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23693,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31817","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - aioseo.com -->\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\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\/en\/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 for the smallest. Part 5. Configuring the load balancer | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/vmware-nsx-dlya-samyh-malenkih-chast-5-nastrojka-balansirovshhika-nagruzki","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","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\/en\/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\/en\/wp-json\/wp\/v2\/posts\/31817","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=31817"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/31817\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/23693"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=31817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=31817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=31817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}