This document will guide you through the installation of the LifeKeeper Single Server Protection Software (SSP) and assumes the user has basic knowledge of the Linux operating system. Please refer to the LifeKeeper Single Server Protection Software for Linux product documentation for more information.
Pre-Installation Requirements
Before installing SSP for Linux, please check the following:
- SSP for Linux Release Notes -The Release Notes include supported platforms, operating systems, applications, and storage. They also include the latest features and Bug Fixes.
- TCP/IP Connection and Name Resolution – In order to use the GUI function, both cluster nodes need to be able to resolve the name. Use the DNS service or /etc/hosts for name resolution. Also, localhost needs to be resolved to 127.0.0.1.
- Firewall – The following ports are used:
- Communication Path (TCP): 7365/tcp
- Communication of a GUI Server: 81/tcp、82/tcp
- RMI Communication between the GUI Server and Client: all the ports after 1024/tcp
- More Firewall Information
- The port used for communication with the GUI server and a client needs to be open on the cluster node where SSP is installed and on all systems where the GUI client runs.
- For communication between the GUI server and a client, Java RMI (Remote Method Invocation) randomly uses ports 1024 and above. Please refer to the Technical Documentation for the setting details.
- Add the following to the port numbers you are using: WebGUI server process and policy setting with the lkpolicy command : 778(SSL) /tcp
- Check the SELinux Setting
- Enabled (enforcing or permissive mode)
- LifeKeeper installer will set mmap_low_allowed to “on”.
- Please make sure that the application(s) to be run on the cluster support the SELinux mode. While LifeKeeper has been tested with some ARKs in permissive and enforcing mode it is important for the system administrator to validate the SELinux mode supported by all applications in the cluster.
- SELinux enforcing mode has been tested on the following ARKs: IP Address / Filesystem.
- SELinux permissive mode has been tested on the following ARKs: SAP / SAP MaxDB /Oracle Database / IBM Db2 Database / NFS Server /Network Attached Storage / IP Address / FileSystem / IBM MQ.
- Disabled
- For more information refer to SELinux
- Enabled (enforcing or permissive mode)
- Check Known Issues – Please make sure that there are no known issues for your environment.
Installing SSP for Linux
Install the LifeKeeper Single Server Protection software on each server in the LifeKeeper Single Server Protection configuration.
Packages that LifeKeeper is dependent on are installed automatically because the LifeKeeper installation setup script uses package manager tools (yum or zypper) to ensure installation of all dependent packages.
The LifeKeeper Single Server Protection image file (SingleServerProtection_linux_version number.img (example: SingleServerProtection_linux_10-0-0)) provides a set of installation scripts designed to perform the user interactive system setup tasks that are necessary when installing SSP on your system (see Interactive Mode for more information). A non-user interactive install can be performed as well (see Non-interactive Mode for more information).
A licensing utilities package is also installed providing utilities for obtaining and displaying the Host ID or Entitlement ID of your server. Host IDs and/or Entitlement IDs are used to obtain valid licenses for running LKSSP.
Please refer to How to Use Setup Scripts for the installation activities.
For upgrading, please refer to Upgrading SSP.
Post your comment on this topic.