3.3 Load Balancer
Transcript of 3.3 Load Balancer
© NTT Communications Corporation ALL Rights Reserved.
1
3.3 Load Balancer v 1.0.4
Disclaimer: The English version of the service description is translated by machine
translation. If there is any discrepancy, the Japanese version takes prevalence.
© NTT Communications Corporation ALL Rights Reserved.
2
Table of Contents
Table of Contents ........................................................................................................................................................................... 2
1 Summary ................................................................................................................................................................................ 3
2 delivery function .................................................................................................................................................................. 4
2.1 delivery function ...................................................................................................................................................... 4
2.2 Configuration ............................................................................................................................................................ 5
2.3 Configuration Details ............................................................................................................................................... 5
2.4 About Applications ................................................................................................................................................... 6
2.4.1 Document ............................................................................................................................................... 6
2.4.2 parameter sheet .................................................................................................................................... 6
3 Fee ............................................................................................................................................................................................ 8
4 Standard Due Date .............................................................................................................................................................. 9
5 Related Menus .................................................................................................................................................................... 10
6 Constraints ........................................................................................................................................................................... 11
7 maintenance operation .................................................................................................................................................... 13
8 Service Level........................................................................................................................................................................ 14
© NTT Communications Corporation ALL Rights Reserved.
3
1 Summary
The Load Balancer menu provides the ability to load balance communications to the servers in the Service.
The Load Balancer feature is provided on a virtual appliance on a redundant host cluster. The virtual appliance
has two redundant configurations. No single configuration is provided.
© NTT Communications Corporation ALL Rights Reserved.
4
2 delivery function
2.1 delivery function
Menu ID Menu Name Description
N-IC-NW-
LB -1 T Load Balancer Setup
• Load Balancer default menu.
• Load Balancer is provided in a virtual appliance on a redundant
host cluster.
• Load Balancer is provided in a redundant configuration with two
virtual appliances.
• Load Balancers can be located in the DMZ Zone within the
customer tenant as well as in the Internal Zone.
• Set the Load Balancer based on the parameter sheet provided by
the customer. Set the following items in our company.
1. Setting Up a Redundant Configuration
2. network interfaces, configuring VLANs
3. Configuring Syslog Parameters (If log forwarding is
required to the customer's Syslog server)
4. Creating a server load balance rule
5. Configuring Server Health Checks
• For Replicated menus, set the DR settings.
N-IC-NW-
LBM -200
LO
Managed Load
Balancer 200 Mbps -
Local Only
• Load Balancer operation menu for Basic μVM.
• Load Balancer is provided in a redundant configuration with two
virtual appliances.
• The maximum throughput is 200 Mbps.
• We will change the Load Balancer setting according to your
application.
• Monitor the Load Balancer.
N-IC-NW-
LBM -200
RE
Managed Load
Balancer 200 Mbp-
Replicated
• Load Balancer operation menu for Core μVM.
• Similar to Core μVM, this Load Balancer can be switched to the DR
site when the customer's system is switched to the DR site.
• Load Balancer is provided in a redundant configuration with two
virtual appliances.
• The maximum throughput is 200 Mbps.
• We will change the Load Balancer setting according to your
application.
• Monitor the Load Balancer.
© NTT Communications Corporation ALL Rights Reserved.
5
N-IC-NW-
LBM -1000
LO
Managed Load
Balancer 1 Gbps Local
Only
• Load Balancer operation menu for Basic μVM.
• Load Balancer is provided in a redundant configuration with two
virtual appliances.
• The maximum throughput is 1 Gbps.
• We will change the Load Balancer setting according to your
application.
• Monitor the Load Balancer.
N-IC-NW-
LBM -1000
RE
Managed Load
Balancer 1 Gbps
Replicated
• Load Balancer operation menu for Core μVM.
• Similar to Core μVM, this Load Balancer can be switched to the DR
site when the customer's system is switched to the DR site.
• Load Balancer is provided in a redundant configuration with two
virtual appliances.
• The maximum throughput is 1 Gbps.
• We will change the Load Balancer setting according to your
application.
• Monitor the Load Balancer.
2.2 Configuration
Load Balancers are located in the DMZ Zone and the Internal Zone.
Note that you cannot span two zones. If you want to balance each of the two zones, place a Load Balancer in
each zone.
The Load Balancer is placed in a one-arm configuration on the same segment as the server being balanced.
The Load Balancer translates the source address of the balanced communication to its own IP address.
2.3 Configuration Details
The following settings are made based on your application.
Summary Details
Managing Load Balancing
Policies
Create, modify, and delete real IP addresses and VIPs for the web server.
Configures the load-balancing method.
Configure persistence.
© NTT Communications Corporation ALL Rights Reserved.
6
Health Check
Management
Create, modify, and delete health checks to detect service responsiveness for servers
configured with load balancing policies.
Managing Network
Interfaces
Changes the configuration of network interface parameters (IP address, default
gateway).
Managing Log Settings Configure the Customer Syslog server to output server health check logs.
2.4 About Applications
2.4.1 Document
Document Description
order sheet Load Balancer Setup and Managed Load Balancer.
parameter
sheet
You will be asked to provide a Load Balancer at the time of initial setup and whenever you
request a configuration change during the usage period.
After changing the settings, our company will present a parameter sheet that reflects the
settings.
2.4.2 parameter sheet
The following parameters can be specified in the parameter sheet:.
Item Parameter Remarks
load balancing
policy
Virtual IP Address Virtual IP Address Required
real IP address Specify the IP address of the server to be balanced.
protocol Specify TCP/UDP and port
load balancing technique Choose from round robin/least connection/source IP
address HASH
© NTT Communications Corporation ALL Rights Reserved.
7
persistence
Choose from cookie insert/source IP address
For insert, the cookie name is ecl4erp
Health Check
Method
Choose normal or HTTP GET
⚫ normal - TCP port life-and-death monitoring via
TCP for TCP - ICMP life-and-death monitoring for
server nodes for UDP
⚫ HTTP GET For the HTTP protocol, you can select
HTTP GET for life-and-death monitoring Response
code is only 200
Spacing Default is 5 seconds Available from 1 to 3600 seconds
timeout Default is 2 seconds Available from 1 to 3600 seconds
Number of
attempts Default is 2. You can specify 1 ~ 127.
Network
Interfaces
IP Address/Netmask IP address/netmask required
Two share one IP address
Log Settings Syslog Server IP Address
Specify if you want to forward logs to the customer's
Syslog server.
Specifies the IP address of the Syslog server
© NTT Communications Corporation ALL Rights Reserved.
8
3 Fee
Menu ID Menu Name initial cost monthly cost
N-IC-NW-LB -1
T Load Balancer Setup
Per set of virtual load
balancers -
N-IC-NW-LBM -
200 LO
Managed Load Balancer 200
Mbps - Local Only
- Fixed monthly charge per set of
virtual load balancers *
N-IC-NW-LBM -
200 RE
Managed Load Balancer 200
Mbp-Replicated
N-IC-NW-LBM -
1000 LO
Managed Load Balancer 1 Gbps
- Local Only
N-IC-NW-LBM -
1000 RE
Managed Load Balancer 1 Gbps
- Replicated
*Tier 1 storage used separately by the Load Balancer is subject to billing. Please refer to the following restrictions
for details.
© NTT Communications Corporation ALL Rights Reserved.
9
4 Standard Due Date
Menu ID Menu Name delivery date
N-IC-NW-
LB -1 T
Load Balancer
Setup
It depends on the working volume. Standard volume (About 5 virtual IP
addresses), 10 business days after application is received (After confirming
on our company that there are no defects in the application contents).
Orders will be accepted until 14 o'clock on each business day, after which
they will be treated as received on the following business day. The day of
acceptance is counted as 0 day.
The DR setting of the Replicated menu is performed in this menu if the DR
Setup menu of Core μVM to be balanced is open. If DRSetup is not open, it
will be executed when you apply for the DR Setup menu.
N-IC-NW-
LBM -200
LO
Managed Load
Balancer 200 Mbps
- Local Only
The due date of a setup change order depends on the work volume.
Standard volume (About 5 virtual IP addresses), 5 business days after
application acceptance (After confirming on our company that there are no
defects in the application contents).
Orders will be accepted until 14 o'clock on each business day, after which
they will be treated as received on the following business day. The day of
acceptance is counted as 0 day.
N-IC-NW-
LBM -200
RE
Managed Load
Balancer 200 Mbp-
Replicated
N-IC-NW-
LBM -1000
LO
Managed Load
Balancer 1 Gbps -
Local Only
N-IC-NW-
LBM -1000
RE
Managed Load
Balancer 1 Gbps -
Replicated
© NTT Communications Corporation ALL Rights Reserved.
10
5 Related Menus
Menu ID Menu Name Related Service Category
N-IC-NW-LB -1 T Load Balancer Setup
• Network
• IaaS Compute μVM
• IaaS Storage
• DR Setup
N-IC-NW-LBM -200 LO Managed Load Balancer 200 Mbps - Local Only
N-IC-NW-LBM -200 RE Managed Load Balancer 200 Mbp-Replicated
N-IC-NW-LBM -1000 LO Managed Load Balancer 1 Gbps - Local Only
N-IC-NW-LBM -1000 RE Managed Load Balancer 1 Gbps - Replicated
© NTT Communications Corporation ALL Rights Reserved.
11
6 Constraints
• Load Balancer is provided in a redundant configuration of two virtual appliances. There is no single
configuration available.
• It is possible to change the usage menu after the start of usage, but you need to change it by our
company. Changes to the usage menu will cause downtime within hours.
• Menu changes may be made once a month or twice a year. If this limit is exceeded, a separate fee will be
charged.
• Load Balancer's Preempt feature is disabled.
• Load Balancers are located in the DMZ Zone and the Internal Zone.
• The Load Balancer can only distribute the load to servers in the zone in which it is deployed.
• Load Balancer cannot span two zones. If you want to balance each of the two zones, place a Load
Balancer in each zone.
• It does not provide WAF functionality.
• It does not provide DoS protection.
• It does not provide SSL termination.
• Customers cannot log in to the Load Balancer.
• Load Balancer virtual disks, as well as vswp, are created in Tier 1 Block Storage and are billed separately
as IaaS storage. The storage type and amount used are as follows.
Menu ID Menu Name Zone to
place Storage Used Amount used
N-IC-NW-LBM
-200 LO
Managed Load Balancer 200
Mbps - Local Only
DMZ DMZ - Tier 1 Block
Storage-Local Only
Virtual Disk:
20 GB
vswp — 8 GB
IZ ENT-Tier 1 Block Storage-
Local Only
N-IC-NW-LBM
-200 RE
Managed Load Balancer 200
Mbp-Replicated
DMZ DMZ - Tier 1 Block
Storage-Replicated 1
IZ ENT-Tier 1 Block Storage-
Replicated 1
N-IC-NW-LBM
-1000 LO
Managed Load Balancer 1
Gbps - Local Only DMZ
DMZ - Tier 1 Block
Storage-Local Only
Virtual Disk:
20 GB
© NTT Communications Corporation ALL Rights Reserved.
12
IZ ENT-Tier 1 Block Storage-
Local Only
vswp: 16 GB
N-IC-NW-LBM
-1000 RE
Managed Load Balancer 1
Gbps - Replicated
DMZ DMZ - Tier 1 Block
Storage-Replicated 1
IZ ENT-Tier 1 Block Storage-
Replicated 1
• The maximum throughput listed in each menu is not guaranteed.
• The source IP address of traffic destined for the server through the load balancer is translated to the IP
address of the network interface of the load balancer.
• The Load Balancer "X-Forwarded-For" feature is enabled. The source IP address of the client is embedded
in the "X-Forwarded-For" HTTP header field.
• You cannot specify a global IP address for all IP addresses configured in the Load Balancer.
• The Load Balancer can have a maximum of 15 virtual IP addresses and a maximum of 50 real IP
addresses.
• You cannot configure a load balancer with a static route.
• The default gateway for the Load Balancer is the Gateway device for the segment to which the Load
Balancer is connected.
• Load Balancer has only one network interface. Cannot be added.
• Load Balancer logs are not saved in this menu. It will not be disclosed or provided to customers. If
desired, log to the customer syslog server. Syslog may be lost due to various factors.
• The output log does not include the traffic log.
• The server health check result of the load balancer is not notified. If monitoring of health check results is
required, the customer must provide a Syslog server and specify the Syslog server to which the health
check log should be output in the parameter sheet. The customer then implements log monitoring of the
Syslog server.
• Replicated Load Balancer has a virtual machine group of 1 for DR. See "Part 11 Disaster Recovery" for
more information about virtual machine groups.
• You cannot specify a date and time for a Load Balancer configuration change.
• Load Balancer settings can be changed only once a month.
• If the upper limit of the number of virtual IP addresses and the number of setting changes is exceeded, a
separate fee will be charged.
© NTT Communications Corporation ALL Rights Reserved.
13
7 maintenance operation
• Load Balancer is monitored based on our company monitoring rules. Monitoring is 24 hours a day, 365
days a year.
• Ping the Admin context of the Load Balancer for life-and-death monitoring.
• If a failure affecting the customer service is detected due to both system failures, the customer will be
notified.
• If our company determines that a software update is required to provide this menu, it may perform Load
Balancer maintenance tasks. Service interruption may occur during maintenance work.
© NTT Communications Corporation ALL Rights Reserved.
14
8 Service Level
It is regarded as an error when both systems fail. Availability is 99.95%.
This menu does not cover SLAs.