Entuity v21.0 Migration Guide

Introduction

Entuity multi-server environments

Compatibility matrix, system requirements and shipped software

Entuity web UI system requirements

Entuity migration path

Entuity v21.0 key changes

Introduction:

Welcome to Entuity v21.0. This migration guide covers important changes that should be considered by users migrating from earlier versions of the Entuity software to Entuity v21.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.

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 v21.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 2019.
• Windows Server 2022.

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 vulnerabilties (published CVEs), please see this article.

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 intgrations will stop working after installing Entuity.

Entuity recommend that users plan for new certificates before upgrading to Entuity v21.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 v21.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 v19.0 and Entuity v20.0. The current latest patch for these versions are as follows:

• Entuity v19.0 P09.
• Entuity v20.0 P04.

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

Migrating to Entuity v21.0:

Migrating to and installing Entuity v21.0 is the same process whether migrating from Entuity v19.0 P09 or Entuity v20.0 P04. If you are upgrading from Entuity 19.0 on Windows Server 2016, you can upgrade the OS and then Entuity in the same migration.

1. Stop the Entuity server and take a backup.
2. (If you are running your original install on Windows Server 2016, upgrade the server from 2016 to Windows Server 2019 or 2022.)
3. 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.
4. Run configure and update the license file to point at the new install.
5. Restart the Entuity server.
6. Deploy the updated Event Management System (EMS) event project, or apply the changes within it to your current project.

For every possible migration paths to Entuity v21.0 from v19.0 or v20.0, please see this article.

Central license server changes introduced in Entuity v21.0:

Changes to the central license server in Entuity v21.0 introduce incompatibilities between v21.0 and earlier versions of Entuity. Please see the following instructions for upgrading central license servers (CLS) and client (remote) servers.

1. When upgrading multiple servers that use a CLS to Entuity v21.0, remote servers on v20.0/v19.0 must be deregistered from the CLS before the CLS is upgraded to v21.0.
2. After the CLS is upgraded to v21.0, the remote servers should then be upgraded within 5 days. During this 5-day period, the remote servers will continue to function normally.
3. As individual remote servers are upgraded to v21.0, they can be re-registered to the CLS.
   • Where it is not possible to update all remote servers within this period, Entuity recommends that an Entuity v21.0 license server is run in addition to the existing license server, and remote servers be migrated to the new license server as they are upgraded.

Note: a license client (an Entuity server that uses license credits from a central pool) must be a remote server of the central license server, but not all remote servers are necessarily license clients.

Please see this article for help and information on licensing in Entuity.

Entuity v21.0 key changes:

Please find below the key changes you will find in Entuity v21.0:

IP Address Management (IPAM)

Keyboard Navigation Accessibility Enhancement

Multi-Server Administration Enhancements

Multi-Server Topology Enhancements

VMWare Monitoring Enhancements

Note, due to changes to server access in Entuity v21.0, it is necessary that all user groups in multi-server configurations are granted access to the consolidation server, otherwise the users therein will lose visibility to data in the UI. Please see this article for help and information on this. Note that data on the consolidation server will therefore become available to those user groups.

IP Address Management (IPAM)

IP Address Management (IPAM)

Addition of functionality that enables users to plan, track and manage the IP address space used in their network in the context of IPv4/v6 networks and subnets.

Keyboard Navigation Accessibility Enhancement

Keyboard Navigation Accessibility

Introduction of WCAG guideline-compliant functionality enabling keyboard navigation of the Entuity UI without the need to use a mouse. A user can navigate through input fields, forms, tables, dashboards and context menus, as well as trigger buttons and selections.

Multi-Server Administration Enhancements

Enhancements to administration of multi-server installations for improved efficiency in maintaining identical server configurations across multiple remote servers:

• Addition of server configuration sets.
• UI overhaul of user account, user group and user external authentication management.
• Enhanced View Management.

Multi-Server Topology Enhancements

Multi-Server Topology

Addition of Topology Group functionality, enabling users to group Entuity servers such that they can share topology information and discover and monitor changes to links between devices managed on the different Entuity servers within the group, and removing the need to manually create links between devices across different servers. Users can create and manage topology groups that define sets of remote servers through the Topology Group Management page.

VMWare Monitoring Enhancements

Virtualization Summary dashboards

Addition of support for new VMware metrics and individual system Summary dashboards to monitor their data:

• Clusters
• Datastores
• Host Bus Adaptors (HBAs)