Deployment Checklist

Review the following information before you start the deployment and network configuration process.

To get started, download and use the applicable Implementation worksheet for your environment (MySQL or MSSQL) provided as an attachment at the end of this article.

Reference the following tables for additional settings.

Note: Fields marked with an asterisk * are mandatory.

Configuring the network

Field name

Value

Comments

*Hostname

Primary

Default value: ScaleArcha1, valid characters: a-z 0-9 _ - . 

  • Note: Make sure you specify a different hostname and IP address for each ScaleArc appliance if you are planning to configure HA. For HA the Secondary ScaleArc appliance must have the same configuration as the Primary ScaleArc, with the same timezone and user access credentials.
  • For MSSQL deployments, if you plan to integrate with Windows AD, make sure you observe the Naming conventions in Active Directory as recommended by Microsoft, particularly the maximum name length.

Secondary

*Interface

Primary

Default: eth0, in case of multiple network cards, you can select any one of them.

Secondary

*IP Address

Primary

Default value: 192.168.1.10, using this you can access ScaleArc UI. Also referred as the Management IP.

Secondary

*Subnet

Primary

 

Secondary

Gateway

   

Primary DNS

   

Secondary DNS

   

Time Zone

 

Default value: (GMT -12:00) Eniwetok, Kwajalein

 

Configuring ScaleArc user access credentials

By default, ScaleArc has a single user with admin privileges to make changes to the configuration. If you are a first-time user and are logging into ScaleArc, use the admin username and password to start the configuration. 

When you configure HA, the username and password(s) of the primary ScaleArc appliance get overwritten onto the secondary ScaleArc appliance.

Field name Value Comments
*Username   Default value: admin
*Admin password   Default value: admin@123

 

Configuring High Availability (HA) 

This step is required only when you want to configure HA between two ScaleArc appliances. DATE/TIME should be synced on both ScaleArc appliances before configuring HA. Similarly, HA VIP should be configured on the same network interface (for example, eth0 or eth1) on which individual Management IP is configured. 

Field name Value Comments
*Floating Virtual IP  

VIP will always point to Primary ScaleArc server once HA is configured. (Also referred to as HA Management IP)

HA keepalive interval (adjust for VM)    
HA deadtime (adjust for VM)    
HA warning interval (must be at least half of deadtime; adjust for VM)    
Rackspace HA   See How to configure High Availability (HA) on RackSpace in ScaleArc
AWS HA   See ScaleArc HA on AWS
Azure HA   See ScaleArc HA on MS Azure


Configuring extra network interface(s)

You can use any one or more network interfaces to configure a cluster. Eth0 is the most commonly used default interface and can also be used for configuring a cluster. If you are planning to use any network interface mentioned below, make sure you change the IP address and subnet for the same, based on your network topology.

If you want to configure bonding link aggregation, please contact ScaleArc support for further assistance with the configuration. 

Field name

Value

Comments

Eth1

IP

Default IP: 192.168.1.11, Subnet: 255.255.255.0

Subnet

Eth2

IP 

Default IP: 192.168.1.12, Subnet: 255.255.255.0 

Subnet

Eth3

IP

Default IP: 192.168.1.13, Subnet: 255.255.255.0 

Subnet

Eth4

IP

Default IP: 192.168.1.14, Subnet: 255.255.255.0

Subnet

Configuring the cluster

You need at least one IP address to create a cluster. The IP address can either be a physical IP address or a floating VIP. HA requires a floating IP. Inbound IP address & Port are used by the application to connect to the ScaleArc cluster, while Outbound IP address is used by the ScaleArc server to connect to the backend database server(s) in that cluster. Inbound & Outbound IP addresses can be on the same or different network interfaces. 

Field Value Comment

*Cluster Name

   

*Instance Name

 

Applicable only for MS SQL deployments.

Default: MSSQLSERVER.

*Inbound Network Interface  

Any network interface on which the physical IP address is configured. 

*Inbound IP Address  

The existing physical IP address or create a new floating VIP. 

*Inbound Subnet Address  

Required only when you want to create a new VIP for the cluster. 

*Cluster Port  

Default value: 3306 (MySQL)

OR

Default value: 1433 (MS SQL) 

*Outbound Network Interface  

Can be the same as or different from the Inbound NIC. 

*Outbound IP Address  

Can be the same as the Inbound IP address or any other existing VIP; alternatively you can create a new floating VIP. 

*Outbound Subnet Address  

Required only when you want to create new VIP for the cluster. 

Database user credentials

In order for ScaleArc to access the database server(s), you need to provide database user credentials and the necessary permissions for the cluster's outbound IP address and management IP address.

ScaleArc uses this information to monitor database server health and the slave replication lag time. See here for the minimum required ScaleArc cluster root user privileges.

Field Value Comment
User Name   Database server username.
Password   The password for the above user.

 

Database server(s)

Specify the database server details needed to define the clusters. 

Tip: Use the checklist below for each database server you add to the cluster.

Field Value Comment
 *DB Server IP   IP address of database server.  
 *Port  

Default value: 3306 (MySQL)

OR

Default value: 1433 (MS SQL)

 *Server Type   Read/Write (Principal) or Read Only (Slave)  
 Version   Database server version; for example, MS SQL Server 2008 R2, etc.

 

Some additional questions

The following questions allow to you correctly prepare for ScaleArc deployment:

Question Response

Are the application server(s) & database server(s) at the same location? This will help in determining possible latency. 

 

What is the platform and version for the application server(s), Linux / MS Windows / UNIX, etc.? 

 

What is the platform and version for the database server(s), Linux / MS Windows / UNIX, etc.? 

 

Are you using client-side connection pooling from the application? 

 

What type of replication have you configured for multiple servers, if any?

 

Are you using any memory data caching technology like memcache

 

What type of ScaleArc deployment platform, appliance / VM / Xen / Custom HW / etc. do you use?

 

Back to top

Attachments

Comments

0 comments

Please sign in to leave a comment.