ENA v17.0 Migration Guide

 

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

For further help on starting up ENA, please also see the other sections in our Getting Started guide:

• Installation Guide (including help with configuring ENA v17.0)
• Licensing
• Data Backup
• Starting Entuity
• Discovering my network
• Navigating and viewing my network

 

*Important*

A new image has been made available on the Entuity FTP server that contains both ENA v17.0 and patch P01. This fixes a critical issue that, in some cases, can result in database corruption (see Known Issues). Customers who have not yet installed ENA v17.0 are strongly advised to download and install this new image.

 

ENA 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 ENA.

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.

 

System requirements and shipped software:

ENA is only certified for use with the 64-bit English edition variants of:

• Red Hat Enterprise Linux ES version 6.
• Red Hat Enterprise Linux ES version 7.
• Oracle Linux 6.
• Oracle Linux 7.
• Windows Server 2012.
• Windows Server 2012 R2.
• Windows Server 2016.

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 ENA 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 ENA, 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 ENA, re-import the security certificates. ENA provides a new tool for this purpose, certtool. It is located in entuity_home\bin\certtool.bat (on windows) and entuity_home/bin/certtool (on Linux). An example would be   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 ENA, you only need to stop Tomcat (which will automatically restart). For example, from entuity_home\bin, enter: stop tomcat

 

ENA web UI system requirements:

The ENA web UI is certified for use with:

• Internet Explorer 11.0 or later.
• Microsoft Edge v42.17134.1.0 (with EdgeHTML v16)
• Firefox 60 or later
• Google Chrome 67 or later.

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

 

ENA migration path:

The certified migration paths to ENA are from the latest patch of Entuity 16.0 and Entuity 16.5. The current latest patches for these versions are as follows:

• Entuity 16.0 Patch 6
• Entuity 16.5 Patch 4 

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

Migrating to ENA:

Migrating to and installing ENA is the same process whether migrating from Entuity 16.0 Patch 6 or Entuity 16.5 Patch 4.

1. Stop the Entuity server and take a backup.
2. Run install to install ENA. Add the new license and then run configure.
3. After install completes, you are prompted to continue with the installation process.
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.

 

Configuration files:

When upgrading from Entuity 16.5 or earlier, please check whether the server's sw_site_specific.cfg file refers to any configuration files that were provided by Entuity. If so, please contact Entuity Support, who will ensure the compatibility of any such files and, if necessary, provide new files to be applied before upgrading to ENA.

 

ENA key changes:

Please find below the key changes you will find in ENA.

 

Dashboards

Views

Filtering Views

Drop Box

Preferences

Events and Incidents

InSight Center

MIB Browser

Help, support and training

Relation between services and Views

Ownership of and access to services

Supported SNMP versions

Selecting modules during the configuration process

Device support changes

Virtualization support

BMC TrueSight

Language support

Mobile UI

 

Dashboards:

Dashboards have been overhauled for ENA. They are now based upon a framework of dashlets, and are either static or dynamic depending on the context. Custom dashboards developed for Entuity 16.5 and earlier will not be migrated to or compatible with ENA.

The Status Summary, Service Summary, TopN Summary, and Path Summary dashboards from Entuity 16.5 and earlier have been replaced by new, context-sensitive View-level dashboards in ENA.

The Device Metrics dashboard from Entuity 16.5 and earlier has been removed. If desired, users can recreate this dashboard using the new dashboard framework.

 

Views:

In ENA, all of the Views that a user has access to will appear as Subviews beneath the My Network View.

As a result of this modification to the View hierarchy, any map layout associated with the My Network View in Entuity 16.5 or earlier will be lost. In ENA, the map for the My Network View will show its Subviews rather than just a flat selection of devices. No other Views will be affected.

From ENA v17.0 P08 upwards, any Views hidden in Entuity 16.5 will become visible upon upgrade to ENA v17.0.

 

Filtering Views:

In Entuity 16.5, there was a user preference to filter out Views so that they are not seen in the UI for that user. In ENA, users are no longer able to filter out Views. Any preferences that users have set in Entuity 16.5 and earlier will also be removed during the upgrade to ENA.

 

Drop Box:

Drop Box has been removed from ENA. Instead, users can:

• pick and add managed objects/attributes directly where they want to use/include them via an Explorer menu.
• drag and drop managed objects/attributes from one tab/window to another to drop objects/attributes directly into the target page.

 

Preferences:

Users can now set their homepage to any page within the ENA UI. Following upgrade, any homepage previously specified in Entuity 16.5 or earlier will automatically be reset to the new default homepage. The new default homepage is the Summary dashboard for the My Network View.

The Traffic Type option that was available in Entuity 16.5 and earlier has been removed. Instead, the new Charts dashlet covers all attributes and traffic types.

 

Events and Incidents:

In ENA, Events and Incidents have been moved from user preferences to the new Administration page.

The process for saving Event or Incident filters has changed in ENA.

 

InSight Center:

In ENA, the InSight Center has been removed from the menu bar. All perspectives and associated reports are still available via the Reports page.

 

MIB Browser:

In ENA, the MIB Browser has been moved from a device-level tab in Explorer, to a device-level context menu.

 

Help, support and training:

All help and support is now accessible online at https://entuity.com/help/home. All training is now accessible online at https://entuity.com/training.

  

Relation between services and Views:

In ENA, managed objects in a service are no longer automatically part of the View that the service is in. This means that if a user does not have access to all objects in a service, then they will not have access by virtue of having access to the View. Instead, the user will see the object(s) in the service and its status, but no further details.

 

Ownership of and access to services:

In Entuity 16.5 and earlier, a user could create a service and it would appear in their My Network because they were the owner, even if they did not have access to any other View containing the actual service. However, following upgrade to ENA, users will lose access to their services because access to services will now be based purely on View access.

In ENA, the ability to create/edit/delete services is based on a single permission called Service Administration.

Note, as of ENA release in June 2018, the permission in the View Administration section of Tool Permission is still called Create Service, and service edit ability is still based on ownership. This is a known issue that will be fixed shortly.

 

Supported SNMP versions

In Entuity 16.5 and earlier, users could use one of four SNMP versions:

• v1
• v1/2c
• v2c
• v3

If you are upgrading to ENA from Entuity 16.5 or earlier, all four versions of SNMP will continue to be available for devices already under management. However, when new devices are added to ENA, v1/2c will no longer be available. This means that, for new devices, users can use one of three SNMP versions:

• v1
• v2c
• v3

 

 

Selecting modules during the configuration process:

We have simplified the selection of modules during the configuration process for ENA. A number of modules are now enabled by default, and a further number are hidden from the process.

In ENA, the following modules are now enabled by default:

• Autonomous WAP
• Configuration Management
• Data Export
• High Availability
• IPv6 Module
• Load Balancer Support
• Routing Protocol Extension
• SurePath
• VPN Gateway
• Wireless Controller

Users have the option to enable the following modules during the configuration process:

• Cisco IP SLA
• Cisco Unified Communication Manager
• Integration for BMC Atrium CMDB
• Integration for BMC Remedy Action Request System
• QoS Module

The following modules are not enabled by default, and are hidden from the configuration process. If users want to enable these hidden modules, they will need to contact support:

• BladeCenter
• Cisco Additional Port Status Events
• Cisco SSL Service
• MPLS
• Netcontinuum Firewall
• Vipman trunk promote
• Wide Area Application Services Support

 

Device support changes:

In ENA, there are a number of device support changes:

Wireless

In ENA, there is added support for Wireless Access Points deployed in high availability (HA) that changes how events are raised:

• When an Entuity server has 2 wireless LAN controllers (WLCs) that manage the same access point (AP High Availability), ENA will set the "AP HA status" attribute to enabled and raise the following incidents and events based on the association statuses of the AP as reported by all of its WLCs:

• Incident:
  • AP Association With Controllers Degraded
• Opened by:
  • AP Association With Controllers Degraded
• Closed by:
  • AP Associated With Controller
  • AP Not Associated With Controller

• Incident:
  • AP Not Associated With Controller
• Opened by:
  • AP Not Associated With Controller
• Closed by:
  • AP Associated With Controller
  • AP Association With Controllers Degraded

APs not in a HA configuration will have "AP HA status" set to disabled, and the normal/old events and incidents will be used.

In ENA, all event details have been updated to show details of WLC association and AP connectivity from the Access Point Connectivity stream (where available).

This feature is only applicable when the WLCs are managed by the same Entuity server. There is no multi-server support.

Users must merge/deploy the "Upgrade: new version" EMS Project to ensure that incidents work correctly and that they will can get the new ACI incidents.

Firewall

In ENA, there is updated Firewall HA State support. ENA now automatically detects state changes and raises events when the firewall's HA state changes.

Incident Firewall High Avail User Set Oper State Non Compliant has been replaced with Firewall High Availability State Changed. This is now opened by the new event, Firewall High Availability State Changed.

The following events have been removed:

• Firewall High Avail User Set Oper State Non Compliant
• Firewall High Avail User Set Oper State Compliant

The User Set Oper State attribute has been replaced with HA State.

MIB support

In ENA, there is updated Entity MIB support. Entuity 16.5 and earlier enabled MIB support on a per device basis, but in ENA there is support for all devices. This change means ENA automatically discovers the following information from the Entuity MIB in cases where the manufacturers' MIBs do not provide sufficient data:

• device inventory data - model, version and serial number.
• modules - ENA ignores modules that have no value for both model number and serial number. This change may result in Module Disappeared and Module Discovered events when modules are discovered.
• sensors.
• fans.
• power supplies.

Port (interface) description

In ENA, there is improved vendor file support. Interface descriptions have been updated for devices that correctly specify ifAlias.

 

Virtualization support:

ENA improves on earlier versions of Entuity by adding support for Microsoft Azure, and additionally by monitoring the status, CPU, memory, storage and network I/O for each VM instance in your AWS, Azure and VMware clouds.

IMPORTANT: AWS and Azure charge for monitoring VM instances in their cloud. Therefore, using the virtualization support in ENA can incur additional charges to your monthly AWS or Azure bills.

In order for ENA to provide detailed monitoring of VM instances in either AWS or Azure, you will need to:

1. Enable the collection and storage of metrics for each VM instance that you wish to monitor.
   • for AWS, enable "Detailed monitoring" via the AWS Console.
   • for Azure, enable "Basic metrics" and/or "Basic Performance Counters" via the Azure Portal.
2. Instrument these VM instances, as necessary, to push the required metrics into AWS and Azure.
3. Take the AWS and/or Azure platform under ENA management.

Once the above steps have been completed, ENA will automatically start monitoring the chosen VM instances, and provide valuable insight into the status, performance, capacity and use of your cloud resources.

IMPORTANT: Customers should be aware that if they have already carried out the above steps 1 to 3 before migration to ENA then, following upgrade, ENA will automatically begin collecting metrics for the said VM instances. This will incur additional charges to your monthly AWS or Azure bills. All additional charges to the monthly AWS or Azure bills are the sole responsibility of the customer.

If you want to ensure these additional charges are not incurred, then before upgrade, either:

• disable collection and storage for your VM instances in AWS and Azure (see point 1). Note, Azure retains metric data for up to 10 days, soo you will need to do this 10 days before upgrade.

or

• remove the AWS and/or Azure platform ENA management.

 

BMC TrueSight:

In ENA, there will be no support for older versions of the Entuity component on the BMC TrueSight server. Therefore, upon upgrade to ENA, users will need to:

1. copy Entuity.zip from their Entuity installation (entuity_home/integ/TrueSight/Entuity.zip) to the TrueSight presentation server.
2. update the component on the TrueSight server using the command: tssh.bat componenttype update Entuity.zip.

 

Language support:

Language support has not been migrated to ENA. This will be added in a future patch.

 

Mobile UI:

For users who have used the mobile UI for Entuity 16.5 and earlier:

• when accessing the mobile UI through the browser on Android, users will need to clear their browser cache, or they will still be redirected to the old mobile page.
• if users formerly had it installed as a web app on iOS, they need to remove the app, clear the Safari cache and then use the browser to navigate to ENA.