Brekeke Failover Configuration on Public Network

1. Brekeke Product Name and version:

Brekeke PBX, Version 2.4.3.9 , Multi-Tenant
ID: 4600000154, Users: 100, Concurrent: 100 , Multiline , ARS Type B/C , PAL , Virtual Number

2. Java version:

N/A

3. OS type and the version:

Windows 2008 R2 Standard

4. UA (phone), gateway or other hardware/software involved:

N/A

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :

Pattern 9

6. Your problem:

Thank you for your support in advance.

We are attempting to configure two servers for Brekeke SIP/PBX failover. We have read the wiki post thoroughly and have been working with a Brekeke distributor and have been unable to come to an accurate configuration.

Each server has two NICs (Network Interface Cards):

NIC1 is directly connected to a public network. This is the network used by clients to attached their UA devices and for SIP trunk carries to terminate/originate calls from.

NIC2 is an interconnection directly between servers used for the Brekeke failover heartbeat/mirror connection.

In particular:

Server 1 Configuration->

NIC1 IP: x.x.x.2
NIC1 Subnet: 255.255.255.192
NIC1 Gateway: x.x.x.1

x.x.x represents a public network address space given to us by our ISP.

NIC2 IP: 192.168.200.10
NIC2 Subnet: 255.255.255.0

Server 2 Configuration->

NIC1 IP: Disabled

x.x.x represents a public network address space given to us by our ISP.

NIC2 IP: 192.168.200.20
NIC2 Subnet: 255.255.255.0

Note that UA devices are terminated to x.x.x.2 and this is the IP address that is moved from Server1 to Server2 in case of a fail over situation.


My questions are:

1) Is this configuration correct/accurate/ideal?

2) Can I change the configuration as described below so that Server2 is accessible via the public network at all times:

Server 1 Configuration->

NIC1 IP: x.x.x.3
NIC1 Additional IP: x.x.x.2
NIC1 Subnet: 255.255.255.192
NIC1 Gateway: x.x.x.1

x.x.x represents a public network address space given to us by our ISP.

NIC2 IP: 192.168.200.10
NIC2 Subnet: 255.255.255.0

Server 2 Configuration->

NIC1 IP: x.x.x.4
NIC1 Subnet: 255.255.255.192
NIC1 Gateway: x.x.x.1

x.x.x represents a public network address space given to us by our ISP.

NIC2 IP: 192.168.200.20
NIC2 Subnet: 255.255.255.0

Note that UA devices are terminated to x.x.x.2 and this is the IP address that is moved from Server1 to Server2 in case of a fail over situation.

This is the configuration that makes most sense to me so that both servers are always accessible via the public address space and the x.x.x.2 public IP address is what moves from server to server during a failover situation.

You feedback, support and expertise is much appreciated in this matter.

Thank you in advance.

-Will

Server 2 Configuration->

NIC1 IP: Disabled

x.x.x represents a public network address space given to us by our ISP.

NIC2 IP: 192.168.200.20
NIC2 Subnet: 255.255.255.0

server 2 NIC1 can be set with some local ip first which is in different segment from NIC2.

if set NIC1 with another global ip x.x.x.4 at the beginning, there will be two global ip after failover. ip x.x.x.2 maynot be used. Since the SIP Server is running on Java, it can not choose an interface IP address for sending packets.

both servers are always accessible via the public address space

server 2 can be accessed through the router global ip which is connected to server 2 local ip 192.168.200.20

hope wrote:

Server 2 Configuration->

NIC1 IP: Disabled

x.x.x represents a public network address space given to us by our ISP.

NIC2 IP: 192.168.200.20
NIC2 Subnet: 255.255.255.0

server 2 NIC1 can be set with some local ip first which is in different segment from NIC2.

if set NIC1 with another global ip x.x.x.4 at the beginning, there will be two global ip after failover. ip x.x.x.2 maynot be used. Since the SIP Server is running on Java, it can not choose an interface IP address for sending packets.

both servers are always accessible via the public address space

server 2 can be accessed through the router global ip which is connected to server 2 local ip 192.168.200.20

UPDATE:

I was able to get the following configuration to work:

Server 1 Configuration->

NIC1 IP: x.x.x.3 (THIS IS ALSO THE GLOBAL IP)
NIC1 Subnet: 255.255.255.192
NIC1 Gateway: x.x.x.1

x.x.x represents a public network address space given to us by our ISP.

NIC2 IP: 192.168.200.10
NIC2 Subnet: 255.255.255.0

Server 2 Configuration->

NIC1 IP: x.x.x.4 (UPON FAILOVER, THIS WILL CHANGE TO x.x.x.3)
NIC1 Subnet: 255.255.255.192
NIC1 Gateway: x.x.x.1

x.x.x represents a public network address space given to us by our ISP.

NIC2 IP: 192.168.200.20
NIC2 Subnet: 255.255.255.0

Hi William,

Your new configuration seem no problem.

>> NIC1 IP: x.x.x.4 (UPON FAILOVER, THIS WILL CHANGE TO x.x.x.3)

How did you make the above?
Is it "Add IP Address" and "Delete IP Address"?


If you have any question regarding Failover, I recommend that you contact Brekeke's support team.

On the Secondary Server:

Heartbeat 1
Heartbeat Monitoring　Method: Network
IP Address: 192.168.200.10
Timeout: 3000
Interval: 500
Retry: 2
Edit
Action 1 Type: Re-initialize as primary
Remote URL:
Edit Delete
Action 2 Type: Delete IP Address (Linux/Win)
Interface Name: Eth0
IP Address: x.x.x.4
Subnet mask: 255.255.255.192
Remote URL:
Edit Delete
Action 3 Type: Add IP Address (Linux/Win)
Interface Name: Eth0
IP Address: x.x.x.3
Subnet mask: 255.255.255.192
Remote URL:
Edit Delete
Action 4 Type: Send Email
To: to@email.com
From: from@email.com
Subject: Failover Email Notification
Body: This is a Failover Email Notification
SMTP Server: smtp.server.com
POP3 Server:
User:
Password: ****
SMTP authentication: false
Encrypted Connection (SSL): false
Edit Delete