Contents

1   About This Document

1.1   Purpose

The purpose of this document is to give a brief overview and introduction to the current version of the ESA, that is ESA 16 and its sub releases, as well as present the changes compared to ESA 4.

1.2   Target Group

This document is intended for all users of the ESA 16.

1.3   Prerequisites

-

2   Introduction

2.1   General

The main focus for the ESA 16 was to improve the cluster solution in large cluster setups, together with a simplified way of seamless expand and reduce the cluster size during runtime. Internal architecture was improved in order to provide a better user experience and a more stable cluster solution. The differences between ESA 4 and ESA 16 looking at fault and performance management features, no changes have been made. The ESA 16 can be seen as a new major release of the ESA, implying that major changes have been done.

The following areas of the agent are improved.

• Architecture

  The internal architecture of the ESA cluster solution is redesigned to secure better performance for large clusters. This also makes it possible to expand end reduce the cluster size during runtime without the need for restarting any nodes or manually update the already present nodes with the expanded one.

• Upgrade

  The ESA16 RPM is now upgradeable, which means that the ESA 16 RPM installations can be upgraded to a newer version of the ESA without uninstalling the present version.

• Java Runtime Environment

  ESA 16 requires the Oracle Java 8 or OpenJDK 8, or later versions.

• SNMPv3 in VIP configurations

  ESA 16 introduces the support for SNMPv3 in VIP configurations.

3   What's New

3.1   Introduction

All the features and functions from the ESA 4 are kept, but with improvements, enhancements and additional functionalities.

The following chapters presents all the news and changes in more detail.

3.2   Product Packaging

The following product packaging changes have been made in ESA 16 compared to ESA 4.

• ASM is no longer available

  The ASMs were previously optional components to the ESA. In ESA 16, ASM can no longer be ordered.

3.3   Backward Compatibility

• Configuration files

  This new ESA version has the same configuration files as the ESA 4, except one tag that is added to the mainCfg.xml and a completely new configuration file for the cluster configuration, named cluster.conf . Hence these two configuration files are NOT backward compatible.

• OSS SNMP support

  The SNMP interface is not changed, which means that ESA 16 is using the same SNMP format as ESA 4. An existing integration between an OSS and ESA 4 can be replaced with ESA 16 with no impact on the OSS.

  Please contact product support for the OSS of interest to get information of which releases of the OSSes that supports the ESA.

• 3GPP XML format

  The 3GPP XML format used for PM output files is not changed, which means that ESA 16 is using the same PM format as ESA 4. An existing integration between an OSS and ESA 4 can be replaced with ESA 16 with no impact on the OSS.

3.4   Functionality

The following functions and features are new or changed in ESA 16 compared to ESA 4.

• System Service Monitors

  The latest security patch for the module System Service Monitors (SSM) is provided within the release.

• APIs

  Small changes are made to the Fault Management API. The getMembers-method in the ICluster interface is NOT backwards compatible.

• Dynamic cluster

  With ESA 16 it is possible to expand and reduce the cluster size during runtime, without the need of manually updating any of the already present cluster members.

• SNMPv3 in VIP configurations

  ESA 16 now support to run SNMPv3 in VIP configurations.

• ESA16 RPM

  The ESA 16 RPM package is now upgradeable, meaning that an ESA RPM upgrade can be done from ESA 16 to a newer release without the need of first uninstalling the ESA RPM installation.

3.5   System Resources

The ESA is a small component and runs well on any modern hardware configuration.

3.6   Improvements

See overall introduction in Section 2.

3.7   Interfaces

-

3.8   Deployment

3.8.1   System Requirements

ESA 16 requires the Oracle Java 8 or OpenJDK 8, or later versions.

3.8.2   Software Packages

The installation packages have been renamed to:

• esa-<version>.rpm
• esa-<version>.sh
• esa-<version>.exe

3.8.3   Deployment Procedure

The deployment procedure has not been changed between ESA 4 and ESA 16.

For further information about the installation procedure, see Reference [1].

3.8.4   Platform Support

The following platform support is removed and thus not supported in the latest version of ESA:

• Red Hat Enterprise Linux 5

3.8.5   Upgrade

The following upgrade paths are supported:

• ESA 4 to ESA 16.

Two of the configuration files must be manually migrated from an older ESA 4 format to the ESA 16 format. The affected files are the cluster.conf and mainCfg.xml.

For further information about ESA upgrades, see Reference [2].

4   Known limitations

4.1   Support for IPv6

Using ESA together with IBM SSM in IPv6 only systems is not possible due to limitations within the SSM.

Please observe that the ESA fully supports IPv6, but the optional IBM SSM package has limitations requiring IPv4 configurations in its trap destination configuration.

4.2   Redhat 7.2

In order to run ESA 16 on Red Hat Enterprise Linux version 7.2, the following ERRATA needs to be installed: https://rhn.redhat.com/errata/RHBA-2016-0199.html.

Glossary

Glossary

ESA Glossary of Terms and Acronyms, 0033-CSH 109 532

Reference List

[1] ESA Installation Instruction, INSTALLATION INSTRUCTIONS, 1531-CSH 109 532
[2] ESA Upgrade Instruction, UPGRADE INSTRUCTIONS, 153 72-CSH 109 532