- High Availability: General Architecture
- High Availability: Cluster Deployment with DRBD
- Axigen with Linux-HA and DRBD – Solution Deployment
- Axigen with Linux-HA and DRBD – Example Configuration
- Axigen with Linux-HA and DRBD – DRBD
- Axigen with Linux-HA and DRBD – Axigen
- Axigen with Linux-HA and DRBD – Heartbeat
Axigen must be installed on both nodes, just the package, without being started or configured.
After the package installation process finishes successfully, the
axigenfilters init scripts must be disabled to start at system boot in all runlevels:
This step must be performed on both nodes.
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:
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:
This step and the following steps for configuring Axigen 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:
By default, all enabled Axigen services will listen to the local loopback interface, 127.0.0.1. 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, on the first node:
Start the Axigen service with the following command:
Then, enable the WebAdmin listener on the cluster service floating IP address, using the CLI service:
Point your browser at the failover domain corresponding floating IP address or its corresponding DNS name, for example
http://10.9.9.90:9000, and try to login using the admin username and the password you have set earlier.
If the login has been successful, you can login and set the listeners for the Axigen services you want to use, including but not limited to: SMTP, IMAP, POP3, WebMail. Please use the floating cluster IP address for these services listener addresses, like for the WebAdmin service you have set above, for example
You can safely stop the Axigen service and its related resources and continue with the cluster setup:
On the secondary node, the
drbd daemon must also be stopped: