1

NTT Communications

Cloudⁿ

Load Balancing Advanced

(VPC Type Open NW)

Operation Guidelines

Ver.1.0

Refrain from secondary distribution (distribution, reproduction,

provision, etc.) of the content described in this booklet.

2

Edition Edited on Revisions

Ver.1.0 2014/02/20 First version

3

1. Introduction Page 4 1) Service Overview

2) Preparations

3) Start LBA Services

3. Using LBA Services Page 8 1) Basic LBA Settings

2) Register a virtual server under LBA

3) Change Detailed Settings of LBA

4) Delete LBA

5) Register SSL Certificate

6) Manage LBA Copies

Table of Contents

2. Preparations for LBA Services Page 7 1) Start up LBA Console

4. Points to Remember Page 23 1) Points to Remember when Creating LBA

1-1) Service Overview

4

This guideline describes how to use Cloudn Load Balancing Advanced (LBA).

Cloudn Load Balancing Advanced (LBA) is a load balancing service that automatically

distributes the application traffic to several Cloudn Compute virtual servers. It is equivalent to

Elastic Load Balancing (ELB) for Amazon Web Services (AWS). By using Cloudn Load

Balancing Advanced, large-scale traffic that flows through the internet can be configured into a

scalable system that is not restricted to the performances of one virtual server.

The main functions are as follows:

■Distributing the application traffic A special virtual service called load balancer instance (LBI) is created in the specified zone

when a load balancer is made. The application traffic (HTTP and HTTPS) that reaches that

virtual service will be distributed to the Cloudn Compute virtual service that was registered

beforehand.

The number of LBI will automatically increase and decrease according to the number of

average and simultaneous connections.

The load balance method is Layer 4 (TCP/SSL) and Layer 7 (HTTP/ HTTPS).

LBI is the terminus for the HTTP/HTTPS sessions from the client.

Sessions can be maintained with the virtual server with Cookies.

SSL communications will be possible from the client to the load balancer by registering the

SSL certificate onto the load balancer.

■ Health Check The Cloudn Load Balancing Advanced service will carry out a health check to the load

balancing virtual server. It will be deleted from the load balancer in case the virtual server

does not react normally.

A health check will be carried out continuously on the deleted virtual server and it will be

added to the load balancer when it reacts normally again.

By default, the TCP protocol will carry out a health check for virtual server port 80.

When carrying out a health check with HTTP/HTTPS protocol, it will access the specific

URL path and will depend on whether it responds successfully (using port 200) as a HTTP

response.

Starting to use the LBA service

Please start the LBA service with a Cloudn portal by referring to “3-1 Start Service in the

Cloudn Portal Operation Guidelines”.

Service for Internet Access

Please have a service for internet access.

Eg. An always-on service such as OCN dial access service, OCN ADSL access service, and super OCN.

*You can use internet access services offered by other companies.

*Please confirm that the HTTPS port 443 is open when using an in-house proxy server.

5

Device for Internet Access

Please have a device ready such as personal computers and modems to access the

intranet and internet.

Please prepare the following to use Cloudn LBA.

1-2) Preparations

Start using LBA services.

1-3) Start LBA Services

6

The LBA service will start up.

Log into the Cloudⁿ portal and click “Sign Up Now” that is displayed by placing your

mouse on LBA on the VPC type OpenNW in the East Japan Region.

1

2

Click

2-1) Start Up LBA Console

7

The LBA console will start up from Cloudn portal.

1 Log into Cloudⁿ portal and click Console that is displayed by placing your mouse on

the LBA icon in the region of your use.

The LBA console will start up using a new window and the initial screen will display a

the List of Load Balancing Advanced (LBA).

2

Click

3-1) Basic LBA Settings

8

Click Create (Basic Config).

1

To create a new load balancer.

3-1) Basic LBA Settings

9

Enter the LBA name. When adding a listener, enter the listener settings (LBA protocol, LBA

port, Compute protocol, Compute port, SSL certificate) and click Add.

2

The SSL certificate must be registered prior to entering the SSL certificate. (Please

refer to page 22.)

The SSL certificate is a requirement when selecting HTTPS or SSL in the LBA

protocol. Either TCP or SSL can be selected for LBA protocol when selecting TCP for

Compute protocol.

The listener setting is included in the HTTP default. It will need to be deleted when it

is not required.

VPC must be created in the Compute (VPC type Open VW) console beforehand.

3-1) Basic LBA Settings

10

3 Confirm the listener settings and click OK.

3-1) Basic LBA Settings

11

Click OK to create a LBA.

4

The status will change from Creating to Running in a few minutes and the LBA

will be completed.

Using specific examples, the following describes how to register a virtual server created

separately on Compute (East Japan Region) with the load balancer created in 3-1).

3-2) Register a Virtual Server under LBA

12

Click Instances Link.

Click Modify (Detailed Config).

1

2

3-2) Register a Virtual Server under LBA

13

Click Register Instances with LBA by selecting the virtual server where the LBA will be

registered from Your Instances (Unregistered with LBA) in the lower part of the screen.

3

The Subnet Compute List that was set under Subnet Settings will be displayed.

3-2) Register a Virtual Server under LBA

14

After clicking OK, the virtual server is registered on LBA and the virtual service registered

on Instances Registered with LBA will be displayed.

4

Can check the conditions of the virtual server with the health check of the virtual

server. In Service stands for a healthy server and Out Of Service stands for an

unhealthy server.

The health check settings must be completed prior to carrying out a health check.

(Please refer to page 16.)

Will make detailed listener settings.

3-3) Change Detailed Settings of LBA

15

Carry out detailed LBA listener settings. Select Protocol and click Modify.

Click Listeners.

1

2

3-3) Change Detailed Settings of LBA

16

Select How to Maintain the Sessions. Enter Expiration Period for Enable Load

Balancer Generated Cookie Stickness. Enter Cookie Name for Enable Application

Generated Cookie Stickness. Confirm the settings and click OK.

3

The listener settings (LBA protocol, LBA port, Compute protocol, Compute port, and

SSL certificate) can be changed from the above screen.

3-3) Change Detailed Settings of LBA

17

Click OK to change the settings.

4

Will return to the above screen after changing the settings.

To set the health check.

3-3) Change Detailed Settings of LBA

18

5 Click Health Check.

3-3) Change Detailed Settings of LBA

19

From LBA set how to set health checks for Compute and click OK.

6

3-3) Change Detailed Settings of LBA

20

Click OK to change the settings.

7

The same screen will be displayed after the settings are changed.

Apply Subnet settings to LBA.

3-3) Change Detailed Settings of LBA

21

Click Subnet.

8

3-3) Change Detailed Settings of LBA

22

Select the Subnet that will be set and click OK.

9

The same screen will be displayed after the settings are changed.

Must create VPC in advance in the Compute (VPC type Open NW) console.

3-3) Change Detailed Settings of LBA

3-3) Change Detailed Settings of LBA

23

Click Sorry Page.

11

3-3) Change Detailed Settings of LBA

24

Enter Redirect URI to Redirect to the other Server. Enter Title and Body to Use Sorry

Page of LBA. Check the settings and click OK.

12

3-3) Change Detailed Settings of LBA

25

Click OK to change the settings.

13

The same screen will be displayed after the settings are changed.

To delete LBA.

3-4) Delete LBA

26

Select the LBA that will be deleted and click Delete.

1

2

Click OK to delete the LBA.

To register SSL certificate.

3-5) Register SSL Certificate

27

Click SSL Certificates Registration.

1

2

Enter Certificate Name, Private Key, Certificate, and Intermediate CA Certificate and

click Register.

To manage LBA copies.

3-6) Manage LBA Copies

28

Select the LBA and Click Replication Mgmt.

1

２

Specify the Number of Copies and click OK.

3-6) Manage LBA Copies

29

Confirm that Replication Set Number has changed from 0 to 1.

3

4-1) Points to Remember when Creating LBA

30

• To use an LBA, it is required to use Compute and an LBA. Start using Compute

form the Cloudn Portal.

• Please use Cloudn DNS to define the DNS alias.

• Please upload the SSL certificate documents in the X.509 PEM format.

An SSL certificate registered to a listener cannot be deleted.

When data is entered, pay attention not to enter a return code at the last.

• The session maintenance cannot be used when the LBA protocol under listener

is TCP or SSL.

• This service cannot register Compute that stores several NICs.

• Only one VPC can be specified. Several Subnets cannot be specified under the

same VPC.

• To change the VPC in the existing LBA, first delete the LBA and specify another

VPC to create a new LBA.