Ozeki NG SMS Gateway logo OZEKI NG SMS Gateway
"The World's most reliable SMS gateway software!"

OZEKI NG SMS Gateway - Product Guide

Failover clustering<br />(Windows Server 2003) Contents | SearchSNMP

Home > Product Manual > User Guide > Administrator's guide > Failover clustering
(Windows Server 2012 R2)


Contact Us!
If you wish to get further information, do not hesitate to contact us!

E-mail: info@ozekisms.com

If you have a technical question, please submit a support request on-line.

Building an Ozeki NG SMS Gateway cluster on Windows Server 2012 R2

Building an Ozeki NG SMS Gateway cluster on Windows Server 2012 R2

This guide gives information about how to build an Ozeki NG SMS Gateway cluster on Windows Server 2012 R2. In this text a failover cluster is discussed which can be used to prepare for hardware failures. If you setup a failover cluster your system will provide better uptimes and better tolerance against hardware related errors.

Before we begin the configuration of Ozeki NG cluster using Microsoft Windows Server 2012 R2, I will show you our own Ozeki Cluster software product which allows you to setup a cluster configuration easier than using Microsoft's solution.

how a cluster works

Ozeki Cluster is responsible for protecting your service against hardware failure and reach higher availability of your Ozeki NG SMS Gateway software. Ozeki Cluster automatically moves any service to another computer in case of a hardware failure. You can download it from the following website: ozeki.hu/index.php?owpn=1086

In the following part of this guide you will show how to configure your Windows Server 2012 R2.

The failover clustering will be working in the following way:

  • The Ozeki NG SMS Gateway service will be running on one PC at the same time.
  • The shared storage can be seen by only one computer at the same time (where the service is running).
  • If the service will fail due to any reason, it will be restarted immediately on the same PC. If the service will be restarted as many times as it was provided, in the specified period (for example 5 times in 15 minutes), it will be restarted on the other PC after the next failure.
  • If the computer will shutdown or there is a network failure, the service will be restarted on the other PC.

In order to setup failover clustering, you need the followings:

  • Three Windows Server 2012 R2 operating systems on three computers.
  • On one computer, an iSCSI virtual disk will be created.
  • The two other computers will be connected to the virtual disk using iSCSI Initiator and the two Ozeki NG SMS Gateway will be installed on the virtual disk.
  • Connect the two PCs to the same domain (without installing active directory). After you have connected the PCs to the domain, you need to login to your Windows operating systems using a domain user who is the member of the Domain Admins group. If you do not want to use a domain admin user, follow the instructions on the next page: https://technet.microsoft.com/en-us/library/cc731002(v=ws.10).aspx.

In the next part of the guide you can get information about the followings:

I. Creating an iSCSI Virtual Disk on a remote Windows Server 2012 R2

First, create a new folder where the virtual disk will be stored.

creating a new folder for a virtual disk
Figure 1 - Creation of a new folder

Under Server Manager, select File and Storage Services.

selecting file and stroage service for the cluster
Figure 2 - Selecting file and storage services

On the next page select iSCSI, and start the iSCSI Virtual Disk Wizard to create a new virtual disk that will be used by the two nodes. The two Ozeki NG SMS Gateway software products will be installed on this virtual disk.

the iscsi virtual disk
Figure 3 - Creating an iSCSI virtual disk

In the next window, select the "Type a custom path", and provide the previously created folder.

setting the path for the new virtual disk
Figure 4 - Providing the path of the virtual disk

Then provide a name for the Virtual Disk.

setting the name of the disk
Figure 5 - Specifying a name for the disk

The next step is to determine the size of the virtual disk. Type a value (for the size) that you would like to use, and select Fixed size radio button.

setting the size of the disk
Figure 6 - Specifying the disk size

Now you should specify a target name for the two nodes.

specifying a target name for the two nodes
Figure 7 - Specifying a target name

Now you need to specify the IP addresses of your two nodes to access the virtual disk.

specifying the server which has access for the virtual disk
Figure 8 - Specifying the servers which can access the virtual disks

Select the last radio button and an IP address type. Then provide the ip address of your Node 1. After that perform this action again to give access to Node 2 as well.

providing the two ip addresses where the two ozeki ng sms gateway will be installed
Figure 9 - Providing the two IP addresses where the two Ozeki NG SMS Gateway will be installed

If you have added the two nodes, click on Next button.

the list of ip addresses that you have added
Figure 10 - Verifying the list of IP addresses you have added

If you would like to setup authentication, you can choose from chap or pap on the next page. If you do not want to set it up, just leave it blank, and click on next button. At the end of the process, click on Create button.

the confirmation of the selected options
Figure 11 - Confirmation of the selected options

Then wait for the end of the process while Windows is creating and clearing the virtual disk.

waiting for the end of the clearing
Figure 12 - Waiting for the end of the process

II. Performing basic settings on the two nodes

Now, login to your two computers that will be the members of the cluster. In this guide I am using two freshly installed Windows Server 2012 R2 without any modifications, features or roles.

In this step you need to perform the following:

  • Provide a static IPv4 address to your network interfaces
  • Give a unique name for the PCs (e.g. ng1 and ng2)

add unique names and a static ip address
Figure 13 - Providing unique names and a static IP addresses

III. Connecting the two nodes to the same domain

Now you need to connect the two computers to the same domain.

First click on WORKGROUP button on both PCs in the Server Manager \ Local Server menu.

click on workgroup menu
Figure 14 - Clicking on Workgroup

Then click on the Change button to change the membership of the operating systems. Select Member of Domain and provide the domain name to where you would like to connect the two computers.

changing the membership to domain
Figure 15 - Changing the membership to domain

After that provide the name and the password of the Administrator on the domain and restart the two computers.

entering the name and password with permission to join the domain
Figure 16 - Entering the name and password with permission to join the domain

Then login to the two PCs with the admin user of the domain where you have connected the two PCs.

log in with the name of the two pcs
Figure 17 - Logging in with the name to the two PCs

IV. Connecting the two nodes to the virtual disk using iSCSI Initiator

Now you need to connect the two nodes to the virtual disk that has been created earlier. You need to perform the following steps in both computers.

Click on Tools button, and select iSCSI Initiator from the list.

selecting the iscsi initiator
Figure 18 - Selecting iSCSI Initiator

If the service is not running, click on Yes button.

click on the yes button on the pop-up window
Figure 19 - Clicking on Yes button

In the target textbox provide the IP address of the iSCSI virtual disk, and click on QuickConnect.

quick connect to the virtual disk
Figure 20 - Quick connection to the virtual disk

On the next window, you can see that the two computers connected to the virtual disk on the target server successfully.

the login is successfull
Figure 21 - Login succeeded

Under the Volumes and Devices tab click on Auto-configure.

volume and devices tab
Figure 22 - Selecting Volumes and Devices tab

As I said, the previous 5 steps have to be performed on the other PC, as well. The following steps have to be performed only on one PC.

Under the Server Manager \ File and Storage Services, click on Disks and bring the virtual disk online.

bringing the disks online
Figure 23 - Bringing online

Then click on "To create a volume, start the new Volume wizard".

start the new volume wizard
Figure 24 - Starting the volume wizard

After that click on the OK button.

clicking ok button
Figure 25 - Clicking on OK

The next step is to specify the size of the volume.

specifying the size of the new volume
Figure 26 - Specifying the size

Now you need to specify the letter for the volume.

specifying the letter for the new drive
Figure 27 - Specifying a drive letter

The next step is to select NTFS type of the partition and provide a label.

selecting ntfs as a file system and select volume label
Figure 28 - Selecting NTFS and a volume label

Finally, click on Create button and then you can see that the volume has been created.

list of volumes
Figure 29 - Verifying the new volume

Take the disk offline, to be able to configure it on the other PC.

take the disk offline
Figure 30 - Take the disk offline

On the other PC take it online.

bring the disk online in the second pc

changing the drive letter
Figure 32 - Changing the drive letter to "q"

Finally take offline again, and return to the first Node.

V. Installing Ozeki NG SMS Gateway on the nodes

If the disk is active on the Node 1 (do not forget to take it offline on Node 2!) install the Ozeki NG SMS Gateway to Node 1 first, then on Node 2 (to install it on Node 2, first take it offline on Node 1, and take it online on Node 2).

During the installation process, you need to change the installation path to Q drive.

installation of the ozeki ng sms gateway on your q drive
Figure 33 - Installation of Ozeki NG SMS Gateway on "q"

Now Stop the Ozeki NG service on Node 1.

stopping the service on the first node
Figure 34 - Stop the service on Node 1

Then take the Disk offline again on Node 1.

make the disk on the first node offline
Figure 35 - Taking the disk offline on Node 1

And take it Online on Node 2.

bring the second node online
Figure 36 - Bringing it online on Node 2

Then install the Ozeki NG SMS Gateway on Node 2 to the same directory on drive Q.

install ozeki ng sms gateway to q on the second node
Figure 37 - Installation of Ozeki NG SMS Gateway to "q" on Node 2

VI. Adding Failover Clustering role to the nodes

The next step is to add the Failover Clustering role to your two Windows Server 2012 R2 operating systems.

Click on Manage and Add Roles and Features.

add roles and features
Figure 38 - Selecting Add Roles and Features

Under the Features list, select Failover clustering (on both Nodes) and click on Next button and then on Install button.

enable failover clustering
Figure 39 - Enabling the checkbox of Failover Clustering

VII. Validating and creating a new failover cluster

After you have installed the Ozeki NG SMS Gateway software product on both Nodes and added failover clustering role to your servers please open Failover Cluster Manager from the Tools menu.

Open it on that PC, where the shared disk is online at that moment.

selecting failover cluster manager from the tools menu
Figure 40 - Selecting Failover Cluster Manager from Tools menu

Click on Create button to create a new cluster.

creating a new cluster
Figure 41 - Creating a new cluster

The next step is to specify the servers where you would like to use this cluster.

adding an ip address to the nodes
Figure 42 - Providing the IP addresses of the nodes

On the next page, the wizard can ask you to run the validation wizard. Click on Next button, and select Run all tests option. Let it finish the validation test.

validate a configuration wizard
Figure 43 - Validation test

If the test has completed successfully (it means there is no error), click on Finish button to create your cluster.

the validation report
Figure 44 - Validation report

Provide a name and an IP address to the cluster.

specifying the clusters name and ip address
Figure 45 - Specifying a cluster name and IP address

At the end of the installation, click on Finish button.

the cluster report
Figure 46 - Cluster report

VIII. Adding Ozeki NG SMS Gateway to the cluster

After you have successfully created the cluster, you need to add Ozeki NG SMS Gateway and the shared storage as resources to the cluster.

Right click on the name of the cluster, and click on Configure Role.

adding a new role to the cluster
Figure 47 - Adding new role to the cluster

On the role list, select Generic Service and click on Next button.

slecting the new generic service
Figure 48 - Selecting Generic service

From the list of services, select Ozeki NG SMS Gateway.

ozeki ng services list
Figure 49 - Selecting Ozeki NG service from the list

Then provide a name and IP address where users can access this role.

specifying a name and ip addres to this role
Figure 50 - Specifying a name and IP addres to this role

Then follow the steps, and always click on Next button without any modification.

Now select Configure cluster quorum settings.

configuring a cluster quorum
Figure 51 - Configur cluster quorum

Select the Select quorum wittness.

select the quorum wittness
Figure 52 - Select the quorum wittness

Then select Configure a file share wittness.

selecting the file share wittness
Figure 53 - Selecting the file share wittness

And finally provide a file share path to this cluster and follow the steps (just click on Next buttons).

adding a file path to the cluster quorom wizard
Figure 54 - Providing file share path

Then right click on the name of the role, and select Add storage button.

adding a storage to the role
Figure 55 - Adding storage to the role

From the list, select the Q volume.

selecting the q volume
Figure 56 - Selecting q volume

Then right click on the name of the Ozeki NG SMS Gateway service and click on Properties (here you can specify how many times the service can be restarted in the specified period).

select role properties
Figure 57 - Selecting role properties

Under dependencies add a new dependency. This means that the service will be started when the shared disk will be online on the PC.

depedencies sub menu
Figure 58 - Dependencies

Under Policies tab, you can configure the maximum restart number in a specified period. In the Period for restarts and Maximum restarts in the specified period textboxes you need the specify the period in which the provided restart number will be allowed. In this example 10 restarts will be allowed in 15 minutes. After the next failure, the service will be restarted on the other node of the cluster.

policies sub menu
Figure 59 - Policies

Now click with the right button on the name of the Role, and select Properties menu.

properties of the role
Figure 60 - Selecting Properties of the Role

On the next window, under the General tab, select both nodes, and move to the top of the list the preferred node.

selecting preferred owners
Figure 61 - Selecting preferred owners

Under the Failover tab, configure the maximum failures in the specified period to 1 and the period (hours) to 0. This is not the same configuration that we have configured earlier.

the failover tab
Figure 62 - Failover tab

IX. Testing the cluster

Now we have finished the configuration of the failover clustering. You can test the functionality in the following ways:

  • If you shutdown the computer where Ozeki NG SMS Gateway is running, the other computer will take over the control over the service and the shared storage.
  • Manually you can simulate failure by right clicking on the name of the service, select More actions and Simulate failures buttons.

simulating the failure
Figure 63 - Simulating failure

If you have any other question, please send us an e-mail at info@ozekisms.com.

Dig deeper!
People who read this also read...

More information

Next page: SNMP
Copyright © 2000- - Ozeki Ltd | info@ozeki.hu
Home > Product Manual > User Guide > Administrator's guide > Failover clustering
(Windows Server 2012 R2)
Legal | Privacy | Terms of use | 2885 | | Login