Telium Support Group

You should place the new file in your /usr/local/haast folder, and remove the old file called haast.license or rename is to haast.lisence.old

Upon next HAAst service restart the new license file will be used. The new license allows you to install new upgrades to HAAst, and benefit from new features as they are released. The new license file will also reflect the updated expiry date for your maintenance agreement (in terms of support and upgrades).

In case you have multiple HAAst license files (following one or more maintenance agreement renewals) then this is how HAAst picks which license file to use: When HAAst starts it will first look for a file called haast.license and use that as the license. If that file does not exist then HAAst will look for a file called haast.XXXXX.license where XXXXX is your license number. If there are multiple files that match this format then HAAst will choose the one with the highest license number (most recent). If you have multiple HAAst license files and you want HAAst to use a particular one then you can create a symlink from haast.license to the file you wish.

I think you are mixing up some network terms/concepts, but I’ll offer a solution to your problem and some networking concepts along the way.

First, the reason we recommend placing the gateway on the management subnet is that when a node promotes/demotes the route to the other peer must not change. If the route does change then the PeerLink will drop and both of your nodes may attempt to promote.

You can safely place the gateway on the VoIP subnet if:

• the addresses of your management NICs of your two nodes are on the same subnet since they will never make use of the gateway; or
• you create a permanent route which tells each node how to find the other across the management network.

So long as you setup your nodes such that management traffic will always go in/out the management NIC then you can configure your gateway/default route however you like.

HAAst performs all NIC control using the Linux system API; it does not use network configuration scripts (such as ifcfg-ethX, ifup, ifdown, etc). These scripts you are referring to are Linux distribution specific, and are ignored by HAAst. All configuration of a shared VoIP NIC is accomplished in the [voipnic] stanza of the haast.conf file.

In order to perform other actions on the PBX at the time of promotion/demotion (i.e. becoming the active or becoming the standby node), you need to use the HAAst event handler system. For example, if you wanted to change the default route of the PBX when it is promoted, you could create a file called /usr/local/haast/events/asterisk.start.pre which contains:


#!/bin/bash
# Delete old default route
ip route del default via 172.31.254.1 2>&1
# Add new default route
ip route add default via 172.31.253.1 2>&1


And if you wanted to switch the default route back when the PBX is demoted, you could create a file called /usr/local/haast/events/asterisk.stop.post which reverses these statements. You can place any code you like in the event handler, but it should complete quickly (ideally < 5 seconds), so if you need to start long-running executables from the event handler be sure to fork them in the event handler code. For example, if you wanted to deleted all temporary files (which can run for several minutes) when the node becomes standby, your event handler file would contain (notice the ampersand which forks the command):

#!/bin/bash
rm -rf /tmp &


If you want to open/close ports in a firewall, control virtual machine functions, etc. then the event handler system is the right way to accomplish this. Just be sure to fork each command, or fork a single bash script which serializes those commands if any of these commands can run for an extended period of time.

Please note that event handlers are only available in the Commercial Unlimited edition of HAAst. See the EDITIONS tab of the HAAst web page to see what functionality is available in each HAAst edition.

The “FEATURES” page for HAAst on the Telium website is far from complete. I would compare our “FEATURES” page to the window sticker of a new car at a dealership. It shows the highlights of a car but is not an exhaustive list of all features.

The root cause of your problem is a regression (bug) in your Linux distro. There have been similar Linux regressions noted by Digium in the past (eg: https://issues.asterisk.org/jira/browse/ASTERISK-15603)

The solution is to use the HAAst event handler to create the missing directory for Asterisk, before Asterisk even starts.

Create the file /usr/local/haast/events/asterisk.start.pre with the following contents:


#!/bin/bash
If [ ! -d /var/run/asterisk ] ; then
mkdir /var/run/asterisk
chown asterisk:asterisk /var/run/asterisk
fi

and set the permissions on /usr/local/haast/events/asterisk.start.pre to 550:


chmod 550 /usr/local/haast/events/asterisk.start.pre

Note: The event handler system (including use of the asterisk.start.pre file) is restricted to the Commercial Unlimited edition of HAAst only.

Based on the Asterisk full message log received, it appears that your Asterisk process was hung for almost 30 seconds. As proof, you have a number of plug-ins/dialplan add-ons that trigger log messages at least once per second. Notice that at 2:38am all messages stopped for almost 30 seconds? Something was blocking IO/CPU to the Asterisk process.

Five seconds after the Asterisk process hung HAAst deemed the peer to be non-responsive and initiated a failover. (This is correct behavior on the part of HAAst – something was going wrong on your PBX).

You need to trace down the root cause of Asterisk hanging for almost 30 seconds. Look for badly written backup scripts, IO or CPU intensive jobs scheduled for this time, etc. Do a grep search through all of your system logs around that time for clues as to what else was happening on your system.

(Hint: Looking at your Asterisk log file you appear to have added a new plug-in in the last 2 days)

I think you are missing some basics concepts of networking. Your description above shows two NIC’s on the same subnet. That will confuse Linux as it is not sure which NIC to use for incoming/outgoing traffic.

Carefully review section 2.4 of the HAAst installation guide before going any further. If you are new to networking/multihoming/routing then you will find all HA product difficult to install or get working properly.

If this is for a commercial environment I would recommend you engage Telium professional services to perform the installation for you (or at least the network/VoIP NIC portion). If you wish, our engineers can also walk you through the key concepts of networking and multihoming, to help you understand what they configured and why.