Operating System

The default operating system must be installed to ensure that all required packages are installed. The minimal operating system install does not contain all of the required packages, and therefore, cannot be used with LifeKeeper.

Kernel updates

In order to provide the highest level of availability for a LifeKeeper cluster, the kernel version used on a system is very important.  The table below lists each supported distribution and version with the kernel that has passed LifeKeeper certification testing.

Note: Beginning with SPS v8.1, when performing a kernel upgrade on Red Hat Enterprise Linux and supported Red Hat Enterprise Linux derivatives (CentOS and OEL), it is no longer a requirement that the setup script (./setup) from the installation image be rerun. Modules should be automatically available to the upgraded kernel without any intervention as long as the kernel was installed from a proper Red Hat package (rpm file).
However, for Red Hat Enterprise Linux 7.3 or later and its compatible distributions, it may be necessary to update the kernel module. If DataKeeper fails to start after upgrading the kernel, check to see if the nbd kernel module is loaded. If it is not loaded run the SPS for Linux setup script to install the appropriate kernel module. There are no SPS kernel module requirements for SUSE Linux Enterprise Server.


Distribution/Version
Supported Version Supported Kernels

Red Hat Enterprise Linux for AMD64/EM64T

(*6.0 is Not Recommended)

6.0*
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10

2.6.32-71.el6
2.6.32-131.17.1.el6
2.6.32-220.el6
2.6.32-279.el6
2.6.32-358.el6
2.6.32-431.el6
2.6.32-504.el6
2.6.32-573.el6
2.6.32-642.el6
2.6.32-696.el6
2.6.32-754.el6

Red Hat Enterprise Linux for AMD64/EM64T

(*DataKeeper asynchronous mirrors are not supported on some kernels on RHEL 7.4-7.6. Click here for full details.)

(Note: If you are using DataKeeper with RHEL 7.7 follow these steps when installing LifeKeeper)

(Some kernel versions do not support asynchronous mode. Please see Known Issues and Restrictions for details)

7
7.1
7.2
7.3
7.4*
7.5*
7.6*
7.7**

3.10.0-123.el7
3.10.0-229.el7
3.10.0-327.el7
3.10.0-514.el7
3.10.0-693.el7
3.10.0-862.el7
3.10.0-957.el7
3.10.0-1062.el7

SUSE Linux Enterprise Server 11 for x86_64

(The kernel should be updated to 3.0.42-0.7.3 for SP2.)

11
11 SP1
11 SP2*
11 SP3
11 SP4

2.6.27.19-5.1
2.6.32.12-0.7.1
3.0.42-0.7.3
3.0.76-0.11.1
3.0.101-63.1

SUSE Linux Enterprise Server 12 for x86_64

(The kernel should be updated to 4.4.82-6.9.1 for SP3.)

12 SP1
12 SP2
12 SP3*
12 SP4
* SLES12.0 is not supported.

3.12.49-11.1
4.4.21-69.1
4.4.82-6.9.1
4.12.14-94.41.1

Oracle Linux

6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
UEK R3
UEK R4

2.6.32-279.el6
2.6.32-358.el6
2.6.32-431.el6
2.6.32-504.el6
2.6.32-573.el6
2.6.32-642.el6
2.6.32-696.el6
2.6.32-754.el6
3.8.13-16.2.1.el6uek
4.1.12-37.3.1.el6uek

Oracle Linux

(*DataKeeper asynchronous mirrors are not supported on some kernels on OEL 7.4-7.6. Click here for full details.)

7
7.1
7.2
7.3
7.4*
7.5*
7.6*
UEK R3
UEK R4

3.10.0-123.el7
3.10.0-229.el7
3.10.0-327.el7
3.10.0-514.el7
3.10.0-693.el7
3.10.0-862.el7
3.10.0-957.el7
3.8.13-16.2.1.el7uek
4.1.12-37.3.1.el7uek

CentOS

(*6.0 – DataKeeper Configuration is Not Supported)

6.0*
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10

2.6.32-71.el6
2.6.32-131.el6
2.6.32-220.el6
2.6.32-279.2.1.el6
2.6.32-358.el6
2.6.32-431.el6
2.6.32-504.el6
2.6.32-573.el6
2.6.32-642.el6
2.6.32-696.el6
2.6.32-754.el6

CentOS

(*DataKeeper asynchronous mirrors are not supported on some kernels on CentOS 7.4-7.6. Click here for full details.)

7
7.1
7.2
7.3
7.4*
7.5*
7.6*

3.10.0-123.el7
3.10.0-229.el7
3.10.0-327.el7
3.10.0-514.el7
3.10.0-693.el7
3.10.0-862.el7
3.10.0-957.el7

 
Note:  This list of supported distributions and kernels is for LifeKeeper only. You should also determine and adhere to the supported distributions and kernels for your server and storage hardware as specified by the manufacturer.

Testing environment of channel bonding, network teaming

In LifeKeeper, we performed tests in the environment using the channel bonding or network teaming with the following settings:

  • Bonding policy in channel bonding

     + balance-rr

     + active-backup

  • Runner in network teaming

     + round-robin

     + active-backup

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment