Creating and managing Network Load Balancer
  • PDF

Creating and managing Network Load Balancer

  • PDF

Available in VPC

Network Load Balancer is a Load Balancer specialized in large-volume TCP layer load balancing. It logs the client IP as is and provides 2 load balancing algorithms (round robin, hash).

Create Network Load Balancer

The following describes how to create a Network Load Balancer.

  1. Please connect to the NAVER Cloud Platform console.
  2. Click Services > Networking > Load Balancer menus, in that order.
  3. Click the Load Balancer menu.
  4. Click the [Create load balancer] > [Create Network Load Balancer] buttons, in that order.
    loadbalancer-network-vpc_button_ko
  5. When the load balancer creation page appears, proceed with the following steps in order.

1. Create load balancer

Enter the Network Load Balancer information to create, and then click the [Next] button.

loadbalancer-network-vpc_create_ko

  • Network: Select the network type for the Load Balancer.

    • Private IP: It uses a private IP within a VPC to handle load balancing of an internal server, and can't be accessed from outside the VPC.
    • Public IP: It is set to a public IP to be called from outside the VPC or from the internet to handle load balancing. It can be used by connecting to the customer's domain or CDN service using a random domain provided with the public IP.
  • Load balancing performance: Select the size of the Load Balancer, depending on the load balancing performance.

    • You can select among Small/Medium/Large, depending on the load balancing performance.
    • Each size can handle at least 100,000, 200,000, or 400,000 loads, respectively, based on connections per minute (CPS).
    • For private network Load Balancer, only Small is provided.
  • Target VPC: Select the VPC where the Load Balancer will be created.

  • Select subnet: Select the zone and subnet where the Load Balancer will be created.

    Caution
    • Once the Load Balancer creation is completed, the selected zone and subnet can't be changed.
    • Create and select a dedicated subnet. If the Load Balancer is located in the same subnet with the server, then no load balancing is handled to the server.
    • In the Target VPC, only subnets included in the selected VPC can be selected.
    • For the Singapore region, subnets can be selected, depending on the selected network type.
      • If Private IP is selected, then only subnets created as private Load Balancer subnets can be selected.
      • If Public IP is selected, then only subnets created as public Load Balancer subnets can be selected.
      • For more details about creating subnets, refer to Create subnet.
    • It isn't necessary to create subnet for each Load Balancer, but a subnet of a C-class scale (255.255.255.0) is recommended.
  • If the Network is selected as public IP in the Singapore region, then a fixed public IP can be specified.

    • Public IP: Select the same zone as the subnet, and then select an IP not in use among the requested IPs in the Public IP menu to assign it to the Load Balancer. If there is no IP requested, then Request for public IP can be selected to make a new request.
    • The same public IP can't be selected in different zones.
    Caution

    Once a public IP is set, it becomes fixed and can be used semi-permanently, but can't be changed.

2. Create load balancer (Set listener)

loadbalancer-network-vpc_listener_ko

  1. Select a protocol where the Load Balancer's default listener will be operated.
    • For the Korea region, only TCP protocol can be selected.
    • For the Singapore region, either TCP or UDP protocol can be selected.
  2. Select a port where the Load Balancer's default listener will be bound.
  3. Click the [Add] button.
    • The listener is added.
    • Repeat Steps 1 to 3 to add multiple listeners.
    • For the Singapore region, only one listener can be added when creating a Load Balancer. If it is required to add a listener, then create a Load Balancer and add a listener by referring to Add listener.
    • Click the [Delete] button to delete the added listeners.
  4. Click the [Next] button.

3. Select target group

Select the target group to perform load balancing, and then click the [Next] button.

  • To do this, the target group need to be created in advance. If there aren't any previously created target groups, then click the [Create target group] button to create a target group. (Refer to Create target group)
  • Among target groups created, only target groups that can be connected are displayed.
    • Network Load Balancer has different selectable target groups, depending on the listener's protocol type.
      • For the Korea region, only TCP is supported as a listener protocol type. Only target groups created with TCP protocol can be selected.
      • For the Singapore region, TCP and UDP are supported as listener's protocol types. Only target groups created with the same protocol as the listener's protocol type can be selected.
Caution
  • Network Load Balancer is operated by direct server return (DSR) to balance loads with a higher performance.
    However, if a private IP Network Load Balancer is used, then communication might be restricted in the following situations.
    • A server that belongs to the target group requests to the Network Load Balancer
    • A client attempts a request to the same port in the server where the private IP Network Load Balancer and target group belong
  • The Load Balancer subnet range must be included as an access source and allowed port in the bound server's ACG and NACL.
Note
  • Network Load Balancer balances loads according to 5-tuple hash algorithm as follows. As a result, if a new request comes into Load Balancer, then it can be delivered to other servers as the source port is changed.
    • Source IP
    • Source Port
    • Destination IP
    • Destination Port
    • Protocol

4. View settings information

Check Load Balancer settings information, and then click the [Create load balancer] button.

Manage Network Load Balancer

Network Load Balancer created can change Load Balancer and listener settings, and check the monitoring information as a graph.

Note
  • The server applied to the Load Balancer can be changed in the Target Group menu. For more details, refer to Set target.
  • Network Load Balancer can't change a subnet. If it is required to change the subnet, then create a Load Balancer again.

Set Network Load Balancer

The following describes how to check the Load Balancer settings information and change the settings.

  1. From the NAVER Cloud Platform console, click the Services > Networking > Load Balancer menus, in that order.

  2. Click the Load Balancer menu.

  3. Check the settings information or select the Load Balancer to change, and then click the [Change load balancer settings] button.

    • The load balancer settings change pop-up window appears, and the Load Balancer's settings information can be checked.
  4. Apply the changes, and then click the [OK] button.

    loadbalancer-network-vpc_edit_ko

    • Load balancing performance can be changed.
      • You can select among Small/Medium/Large, depending on the load balancing performance.
      • Each size can handle at least 100,000, 200,000, or 400,000 loads, respectively, based on connections per minute (CPS).

Set listener

In the listener settings change page, registered listeners can be checked, listeners can be added/changed/deleted, and rules can be viewed and changed.

Note

Network load balancer can't add or delete a rule.

The following describes how to move listener to the settings change page.

  1. From the NAVER Cloud Platform console, click the Services > Networking > Load Balancer menus, in that order.
  2. Click the Load Balancer menu.
  3. Select the Load Balancer to change the listener settings, and then click the [Change listener settings] button.
    • After moving to the listener settings change page, the listener set when creating a Load Balancer is viewed as a default.

Add listener

The following describes how to add a listener.

  1. Click the [Add listener] button in the listener settings change page.
  2. Select a protocol of the listener to add.
    • For the Korea region, only TCP protocol can be selected.
    • For the Singapore region, either TCP or UDP protocol can be selected.
  3. Enter the port number for listener to be bound to.
  4. Select the target group where the listener's traffic will be sent.
  5. Click the [OK] button.

Change listener

The following describes how to change a listener.

  1. Click the [Change listener] button in the listener settings change page.
  2. Refer to Add listener to apply changes.
  3. Click the [OK] button.

Delete listener

Note
  • At least 1 listener must remain. So if one listener is added, then the listener can't be deleted. Perform Add listener to delete the one remaining listener.
  • The listener can be deleted if Load Balancer's status is Running.

The following describes how to delete a listener.

  1. Select the listener to delete in the listener settings change page.
  2. Click the [Delete listener] button.
  3. Check the details in the listener deletion pop-up window, and then click the [Delete] button.
    • The selected listener is deleted.

Viewing rule

Registered rules can be viewed in the rule view/change page.

Rules have the following characteristics.

  • Each rule is comprised of an action (No condition is specified for Network Load Balancer)
  • A default rule can't be deleted
  • Each rule is applied according to the priority, and traffic not applied is operated by default rule

The following describes how to view registered rules.

  1. Select the listener to view rules in the listener settings change page.
  2. Click the [View/Change rule] button.
    • Go to the rule view/change page.

Changing rule

The following describes how to change rules.

  1. Select the listener to change a rule, and then click the [View/Change rule] button in the listener settings change page.
  2. Select the rule to change, and then click the [Change rule] button in the rule view/change page.
  3. Apply the changes.
    • Change the target group in the Action, and then click the [Add] button.
      • Weights can't be changed.
    • Click the [X] button to delete the added target group.
  4. Click the [OK] button.

Network Load Balancer monitoring

The collected information about concurrent connection, connection per second, traffic-in, available host count, and unavailable host count can be checked as a graph, respectively, depending on the selected period.

Note

The collection cycle varies, depending on the selected period. Monitoring information collected by handling load balancing can be set up and checked from at least one minute to the recent one year.

The following describes how to check the Network Load Balancer's monitoring information.

  1. From the NAVER Cloud Platform console, click the Services > Networking > Load Balancer menus, in that order.
  2. Click the Load Balancer menu.
  3. Select the Load Balancer to monitor, and then click the [Monitoring] button.
    • The load balancer basic monitoring pop-up window appears, and the monitoring information can be checked as a graph.
    • Select the period to check the monitoring information collected for the selected period.
    • Click the [Refresh] button to refresh the graph viewed.
    • Click i_loadbalancer_enlargement to check the zoomed-in graph. Click the [X] button to download the collected monitoring information as an Excel file.

Delete Network Load Balancer

Caution

Deleting the Load Balancer also deletes rules set in a route table. If the route table rule is used in other services, then deleting the Load Balancer may cause the features to not work properly.

The following describes how to delete a Network Load Balancer.

  1. From the NAVER Cloud Platform console, click the Services > Networking > Load Balancer menus, in that order.
  2. Click the Load Balancer menu.
  3. Select the Load Balancer to delete, and then click the [Delete load balancer] button.
  4. Check the details in the load balancer deletion pop-up window, and then click the [Delete] button.
    • The selected Load Balancer is deleted.
Note

For the Singapore region, if the public IP Load Balancer is deleted, the public IP in use can be terminated together. Unterminated IP can be reassigned to a different server or public IP Load Balancer.


Was this article helpful?