Axigen Cluster Deployment with DRBD

Highly Available Single-Tier Solution Architecture

Following steps must be performed on both nodes unless specified otherwise.

Package Installation

Axigen must be installed on both nodes, just the package, without being started or configured.

After the package installation process finishes successfully, the axigen and axigenfilters init scripts must be disabled to start at system boot and removed from all runlevels:

Init Script

First, you need to disable the regular axigen init script to accidentally start, by editing its corresponding configuration file /etc/sysconfig/axigen and literally setting:

A hard link must be created, which will point to the original package init script:

Do not attempt to set the cluster init scripts (like the axigen-ha defined above) to start at system boot.
They will be started, stopped and generally managed by the clustering management software.

Then, the corresponding configuration file must be created as /etc/sysconfig/axigen-ha, with the following configuration:

Storage Preparation

On both nodes, you have to create a common mount point directory for the Axigen DRBD resource. In our example setup we have used the /var/clusterfs/data directory for mounting the AxigenData DRBD resource. Create the mount points on both nodes using:

On the primary node, mount the DRBD resource, as follows:

Admin Password

This step must be performed only on the primary node.

To be able to login in the Axigen administrative interfaces, you need to set the password for the top level administrative user, called admin. The following command helps you with this step:

Log Separation

In order to avoid unnecessarily replication for Axigen logs we recommend changing the default log directory from ${AXIGEN_DATA_DIR}/log to a local partition, like /var/log/axigen.

On both nodes run the following commands:

On the primary node run the following command:

This action will decrease DRBD network communication and lower the IO operations on the DRBD devices.

In the same time this separation will avoid unfortunate situations when the DRBD device get full due to extensive Axigen logging at protocol level.

Service Start

The following steps must be performed only on the primary node.

By default, all enabled Axigen services will listen to the local loopback interface, In order to be able to use the WebAdmin interface via the cluster floating IP address, you must set it on the corresponding network interface:

You can see it set if it appears in the output of the following command:

The output should be similar with the following one:

Start the Axigen service with the following command:

WebAdmin Setup

This step must be performed only on the primary node.

Then, enable the WebAdmin listener on the cluster service floating IP address, using the CLI service:

Point your browser at the corresponding floating IP address or its corresponding DNS name, for example, and try to log in using the admin username and the password you have set earlier.

If the login has been successful, you can set the listeners for the Axigen services you want to use, including but not limited to: WebMail, IMAP, POP3, and SMTP. Please use the floating cluster IP address for these services listener address, like for the WebAdmin service you have set above, for example


At the end you can safely stop the Axigen service and the other resources running on primary node:

On the secondary node, the DRBD resource should be also closed and drbd daemon disabled to start at boot: