Entuity v23.0 Migration Guide

Introduction

Entuity multi-server environments

Compatibility matrix, system requirements and shipped software

Minimum server specifications

Third-party software versions

Allocating additional memory to Java processes

JRE upgrade overrides SSL/TLS certificates in the default keystore

Entuity web UI system requirements

Entuity migration path

Migrating to Entuity v23.0

Entuity v23.0 key changes

Configuration management and monitoring enhancements

Entuity Agent architecture

User defined data receivers

Note regarding BMC Event Integrations

Introduction:

Welcome to Entuity v23.0. This migration guide covers important changes that should be considered by users migrating from earlier versions of the Entuity software to Entuity v23.0.

For further help on starting up Entuity, please also see these other sections in our guide:

• Installation Guide
• Licensing
• Data Backup
• Starting Entuity
• Discovering my network
• Navigating and viewing my network

Entuity multi-server environments:

If you use multiple Entuity servers to manage your network, and you group these together using a consolidation server, you must upgrade all servers in the group to the same version of Entuity. The consolidation server within the environment should be upgraded first, then followed by upgrading the remote polling servers.

If you use multiple Entuity servers to manage your network, independently of each other, then you may continue to operate these servers using different versions of the software.

Compatibility matrix, system requirements and shipped software:

Entuity v23.0 is only certified for use with the 64-bit English edition variants of:

• Red Hat Enterprise Linux ES version 8
• Red Hat Enterprise Linux ES version 9
• Oracle Linux 8
• Oracle Linux 9
• Windows Server 2022
• Windows Server 2025

Minimum server specifications:

• Low: 400 devices and 25,000 ports
• Intermediate: 800 devices and 50,000 ports
• High: 1,000 devices and 70,000 ports

Third-party software versions:

For information regarding third-party software versions used in Entuity, please see this article.

Note, for information regarding third-party software vulnerabilities (published CVEs), please see this article.

Allocating Additional Memory to Java Processes:

As of Entuity v23.0, the ability to allocate additional memory to individual Java processes using the entuity.cfg file was added rather than overriding the start up commands through site-specific config files. Prior to upgrading, check the site-specific config file (startup_UNIX_site_specific.cfg or startup_WIN32_site_specific.cfg), and if the config file contains an override, the override must be commented out or removed. You must then move the override into the entuity.cfg file before the upgrade.

JRE upgrade overrides SSL/TLS certificates in the default keystore:

This section is only applicable if users have implemented the Entuity external authentication using secure LDAPs.

The default keystore file entuity_home\install\JRE\lib\security\cacerts is overwritten during the JRE upgrade, which means that security certificates imported into that keystore are now lost.

To preserve your certificate setup, you can export them before migrating to Entuity, and import them after completing the migration. It is important to export and then import all security certificates in a certificate chain.

To retain imported SSL/TLS certificates:

1. Before starting migration, export the security certificate chains using entuity_home\install\JRE\bin\keytool.
2. Enter the keystore password. The default keystore password is changeit, although it may have been amended by a system administrator.
3. After installing Entuity, re-import the security certificates. Entuity provides a tool for this purpose, certtool. It is located in entuity_home\bin\certtool.bat (on windows) and entuity_home/bin/certtool (on Linux). certtool works by storing keys in a secondary keystore which persists across JRE upgrades. In the future, running configure will merge keys in the secondary keystore with the default JRE keystore.
4. After you have imported all of the security certificates, you must ensure they are picked up by Apache Tomcat on the Entuity server. When Tomcat starts, it updates its security certificates. You do not need to stop Entuity, you only need to stop Tomcat (which will automatically restart). For example, from entuity_home\bin, enter: stop tomcat

Note: when configured for external authentication via LDAPs, Entuity enforces hostname verification between certificates and the LDAP server. If your LDAP TLS certificates are non-compliant with hostname verification, then the LDAPs integrations will stop working after installing Entuity.

Entuity recommends that users plan for new certificates before upgrading to Entuity v23.0. If you are unable to rebuild certificates, Entuity recommend that you contact Entuity Support for details of how to handle non-compliant certifications.

Entuity web UI system requirements:

The Entuity v23.0 web UI is certified for use with:

• Microsoft Edge v44 or later.
• Firefox 68 or later.
• Google Chrome 79 or later.

Users must enable their web browsers for both JavaScript (e.g. to enable the Entuity menu structures) and cookies (e.g. to maintain login status).

Entuity migration path:

The certified migration paths to Entuity are from the latest patch of Entuity v21.0 and Entuity v22.0. The current latest patch for these versions are as follows:

• Entuity v21.0 P11.
• Entuity v22.0 P08.
  • Migrating from a BMC Entuity Network Monitoring variant to v23.0 is only supported from Entuity v22.0 P08. If you are running an older BMC Entuity Network Monitoring variant, you must first migrate to v22.0 up to P08, and then migrate to v23.0

Click here for help on how to check the current version and patch level of an Entuity server.

Migrating to Entuity v23.0:

Migrating to and installing Entuity v23.0 is the same process whether migrating from Entuity v21.0 P11 or Entuity v22.0 P08. If you are upgrading from Entuity 21.0 on Windows Server 2019, you can upgrade the OS and then Entuity in the same migration.

1. Stop the Entuity server and take a backup.
   Note, If you are running your original install on Windows Server 2019, upgrade the server from 2019 to Windows Server 2022 or 2025.
2. Run install to install Entuity and install it on top of the existing install.
   Note, you must run install as administrator from the command prompt.
3. Run configure and update the license file to point at the new install.
4. Restart the Entuity server.
5. Deploy the updated Event Management System (EMS) event project, or apply the changes within it to your current project.

For every possible migration path to Entuity v23.0 from v21.0 or v22.0, please see this article.

Entuity v23.0 key changes:

Please find below the key changes in Entuity v23.0:

Configuration Management and Monitoring Enhancements

Entuity Agent Architecture

User Defined Data Receivers

Configuration management and monitoring enhancements

Configuration management and monitoring

Enhancements to configuration management and monitoring, including:

• Setting Task parameters in scheduled tasks.
• Improved firmware upload form to allow multiple files to be uploaded at once.
• Addition of Copy Policy Rules button for easier policy creation.
• Enhancements to compare functionality to allow exclusions of special characters.
• Other improvements.

Entuity Agent architecture

Entuity Agents

Addition of Entuity Agent Architecture enabling users to monitor server and storage devices through the agent, as well as locally monitoring Windows or Linux operating systems. Entuity Agents allow monitoring of devices throughout a segmented network with support for proxy use between the agent and Entuity server. Entuity Agents provide monitoring scalability by supporting up to 100 server/storage devices and Entuity servers supporting multiple agents. 

User defined data receivers

User Defined Data Receivers

Addition of functionality with the new User Defined Data Receivers, enabling you to add support for devices and software-defined platforms that use newer technologies, such as Streaming Telemetry. Supported streaming telemetry methods are through Cisco’s Model-Driven Telemetry (MDT), DMTF’s Redfish, and gNMI. You can define data receivers via the UI or Entuity's RESTful API functionality. 

Note regarding BMC Event Integrations

As of Entuity v23.0, the following BMC event integrations have been removed.

• BMC Atrium
• BMC Remedy
• BMC TrueSight Operations Management

Reinstatement of the BEM event integration is available for customers that previously had the integration following its removal in v23 GA. For additional details on how to reinstate the integration, please see the following article.