Notification:  

Add   Edit   Delete   Sort   Print   Change Password   Settings   Permissions

Set up Heartbeat on Secondary Brekeke SIP Server

Example
PRIMARY_IP_ADDRESS: 192.168.200.10 /255.255.255.0 and 172.16.0.10 / 255.255.0.0
SECONDARY_IP_ADDRESS: 192.168.200.20 / 255.255.255.0
VIRTRUAL_IP_ADDRESS: primary IP, 172.16.0.10 / 255.255.0.0
Gateway: 172.16.0.1/255.255.0.0

Create Heartbeat on secondary server

At [SIP Server]>[Configuration]>[Heartbeat], create [New Heartbeat]
---------------------------------------------------
Monitoring methods: Network
IP Address: PRIMARY_IP_ADDRESS, e.g. 192.168.200.10
Timeout: 3000
Interval: 500
Retry: 2
---------------------------------------------------
Save the settings

Note: Set large number to [Timeout] and [Retry] fields when it takes time to get response from Primary server due to slow network, such as using VPN for network connection.

Add Actions

Please choose actions according to the OS where the secondary Brekeke SIP server is running.

On LINUX OS:

Action 1: Add Virtual IP to secondary server PC when failover happens
---------------------------------------------------
Type: Add IP Address (Linux)
Position: 1
Interface Name: the interface name, e.g. eth0
IP Address: VIRTRUAL_IP_ADDRESS,e.g. 172.16.0.10
Subnet mask: blank
Remote URL: leave it blank
---------------------------------------------------

Action 2: Set subnet mask for VIRTRUAL_IP_ADDRESS
---------------------------------------------------
Type: Execute Command
Position: 2
Command: /sbin/ifconfig eth0:0 netmask 255.255.0.0
Remote URL: leave it blank
---------------------------------------------------

Action 3: Assign default GW to VIRTURAL_IP_ADDRESS
---------------------------------------------------
Type: Execute Command
Position: 3
Command: route add default gw 172.16.0.1 eth0:0
Remote URL: leave it blank
---------------------------------------------------

Action 4: Change secondary mirroring role to primary when failover happens
------------------------------
Type: Re-intialize as primary
Position: 4
Remote URL: leave it blank
------------------------------

Action 5: Send notification email when failover happens
---------------------------------------------------
Type: Send Email
Position:  5
To: a real email address
From: a real email address
Subject: text
[Body]
SMTP Server: your mail server address
POP3 Server: your mail server address
User: your mail server logon information
Password: your mail server logon information
SMTP authentication: on
Encrypted Connection(SSL): off/on depend on your mail server type
---------------------------------------------------
Save the settings

On WINDOWS OS:

Action 1: Add Virtual IP to secondary server PC when failover happens
---------------------------------------------------
Type: Add IP Address (Win)
Position: 1
Interface Name: interface name found in network connect, e.g. Local Area Connection
IP Address: VIRTURAL_IP_ADDRESS, e.g. 172.16.0.10
Subnet mask: subnet mask of virtural IP, e.g. 255.255.0.0
Remote URL: leave it blank
---------------------------------------------------

Action 2: Assign default GW to VIRTURAL_IP_ADDRESS
---------------------------------------------------
Type: Execute Command
Position: 2
Command: route ADD 172.16.0.0 MASK 255.255.0.0 172.16.0.1
Remote URL: leave it blank
---------------------------------------------------

Action 3: Change secondary mirroring role to primary when failover happens
------------------------------
Type: Re-intialize as primary
Position: 3
Remote URL: leave it blank
------------------------------

Action 4: Send notification email when failover happens
---------------------------------------------------
Type: Send Email
Position: 4
To: a real email address
From: a real email address
Subject: text
[Body]
SMTP Server: your mail server address
POP3 Server: your mail server address
User: your mail server logon information
Password: your mail server logon information
SMTP authentication: on
Encrypted Connection(SSL): off/on depend on your mail server type
---------------------------------------------------
Save the settings

Start Heartbeat

At secondary server, click the [start] button at the [Configuration] > [Heartbeat] page.
If the [Auto Start] check box is checked, the heartbeat on secondary server will start automatically when Brekeke SIP Server restarts.

Note:
If primary Brekeke SIP Server PC is not running when heartbeat on secondary server starts, the heartbeat status on secondary server will show idle till primary server IP address is reachable.