Overview

These release notes are for Nectar Foundation APM. For more information, contact Nectar Support (support@nectarcorp.com).

Foundation APM

• It is not possible to use the Remote Software Upgrade on a Linux platform to upgrade from a version prior to r8.6.
  NOTE: Runtime version will be enforced before RIG Client JAR files are downloaded.

• The beta version of the RIG Client (release 2024.1) requires OpenWebStart v1.8.0 or above, and OpenJDK JRE 17.

• Before upgrading to r2024.1, your existing installation must be at r5.6.2.x or later, licensed, and started successfully. If you attempt to upgrade directly to r2024.1, then the installer will display the following message: Selected installation’s main version is earlier than r5.6.2 required for upgrade.

• For the server to start successfully, the port number specified for the serverport property of the server. properties file must not be in use. If the port is already in use, change the port number to an unused port number to correct the issue. The default port number is 80.

Technical Notes

NOTE

Apache Log4j Critical Vulnerabilities (CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, CVE-2021-44832). Foundation APM uses Log4J versions 2.17.1 and 2.12.4 for all components in r2021.3 or higher that contain fixes for all known security vulnerabilities.

JREs used by existing RIGs will be updated as part of the upgrade process. If modifications have been made to the java.security config file, those changes will need to be manually transferred to the updated JRE. TLSv1 and TLSv1.1 are disabled by default by the JRE configuration. To learn how to enable this, go to the Nectar Foundation APM Installation Guide, or to review the instructions go to: https://www.java.com/en/configure_crypto.html.

Upgrade Requirements

WARNING

Before upgrading any RIG running r2023.4 or r2023.4.01, execute the following commands below. This can be done via a RIG Client (RIG > Admin > Command Line Terminal) or a Command Line (cmd.exe) running on the host system that is started with “Run as Administrator”.

• cd <righomedir>

• Server.exe update <rigsvcname> --StopTimeout 90

Once the commands are executed, restart the RIG service, either from the RIG Client (RIG > Admin > Restart) or from the host system's Services window. After the RIG service restart is completed, you can then upgrade the RIG to r2024.1 using the installer.

The actions above are not required when upgrading a RIG running r2023.3 or earlier. Upgrading RIGs running r2023.3 or earlier to r2024.1 can be done using the installer.

• If you upgraded your RIG up to r2023.4 or above from r2023.3 or below, be aware you cannot downgrade back to your previous version using an installer.

• The database migrations started with r2021.1 and it will make it difficult to downgrade to Foundation APM r8.7.1 and below.
  We strongly advise customers to back up the RIG database before upgrading to r2024.1 and later.

Cisco UCM VKM

• When upgrading RIGs from a release prior to release 8.0 that are monitoring Cisco UCM systems, additional time will be required based on the number of historical call detail records (CDRs) to perform database migration following restart.

• If the Cisco UCM VKM module is enabled on a system when upgrading to r2024.1 from a pre-7.x release, the Installer will detect it and display a warning message, informing the user to offboard any existing Cisco UCM systems before proceeding with the upgrade. For more information on offboarding, see Cisco UCM VKM Configuration Guide.

• Once the Cisco UCM system(s) has been offboarded, the user can re-run the upgrade process and select the Module Override to complete the upgrade.

Cisco Meeting Server VKM

For licensing, a status is received for each type of license (no-license, activated, or expired). If a no-license case, a WARNING event is generated. However, if the customer does not want to see these no-license events, they can disable the associated poller(s).

Cisco Expressway VKM

When onboarding Cisco Expressway VKM, use the same username and password across all cluster peers.

Microsoft Skype for Business VKM

Customers who upgrade to r2024.1 have the option to continue using the Legacy SfB module. However, to access the new SfB features available since release 8.0, you must:

1. Offboard the Legacy SfB system.

2. Enable and onboard the new SfB VKM and system.

Avaya Call Management System (CMS) VKM

As of r8.1, Nectar no longer supports Avaya CMS r16 (and earlier). CMS r16 uses the 256-bit Diffie-Helman encryption algorithm, which is considered a security risk and has been deprecated. It is no longer supported in current SSH-2 implementations.

If you accept this CMS security vulnerability, you can maintain CMS r16 monitoring with Nectar using a Nectar version prior to v8.1.

Avaya System Manager VKM

If you onboard Avaya System Manager with invalid credentials, you must delete the incorrect entry and re-onboard the System Manager. For more information, see Avaya System Manager r7.1 and above.

IP Office VKM (r10.1 and above)

Nectar leverages Avaya’s Service Monitoring Web Services API to monitor IP Office r10.1 and above. If you are currently monitoring an IPO r10.1 or above with Nectar r7.3 and prior, you can migrate to Nectar’s new API support by following these steps:

• Disable and remove the existing monitoring.

• Delete any IP Office traps in the Receiver module.

• Disable the previous module and enable the new module using RIG > Module Configuration.

• Restart the RIG.

For more information, see Avaya IP Office r10.1 and above Deployment Guide.

Properties File

After upgrading to r2024.1, if you have or plan to manipulate a properties file that uses a file path or directory, then you must verify that you are using the proper backslash (\) or forward slash (/):

Windows: 

• Use double backslash (\\), for example, <drive>:\\<folder>\\<folder|file> or

• Use single forward slash (/), for example, <drive>:/<folder>/<folder|file>

Linux/iOS:

• Use single forward slash (/), for example, /<folder>/<folder|file>

General Data Protection Regulation (GDPR)

You must upgrade to ‘Version 7.2 or later’ (CIP, EIP, RIG, Perspective Agent/Controller as well as the Nectar Foundation Client) to enable the new General Data Protection Regulation (GDPR) audit logging. Logging is enabled by default but can be customized to suit your specific auditing needs. The Apps\<partner name>\etc\log4j2.xml file is used to enable that customization after the upgrade to ‘Version 7.2 or later’.

The upgrade to ‘Version 7.2 or later’ will back up your existing log4j2.xml file before installing the new version of that file.

If you have previously customized the log4j2.xml file, you will have to manually migrate those changes to the new log4j2.xml file. Your previous version can be accessed by navigating to Apps\<partner name>\rollback\etc\log4j2.xml AFTER you have upgraded.

New Features, Improvements, and Bug Fixes

New Features

• N/A

Improvements

• CMP-10910: Implemented generation of events for Avaya Aura CM processor interchange.

• CMP-10951: Modified AES collections to detect empty list response and handle it correctly in Avaya Aura CM module.

• CMP-10964: Poller threshold description length limit has been increased to 255 characters. User entered poller threshold descriptions will be truncated at that length.

• CMP-10997: Updated 64-bit Windows Java runtime included in the installer to OpenJDK 17.0.10.

Bug Fixes

• CMP-10808: Improved Dependency Tree creation and modification in Avaya Aura CM module.

• CMP-10873: Fixed Dependency Tree creation for Trunk Groups with long names in Avaya Aura CM module.

• CMP-10953: CIDR notation for Gateway Timer Task should work correctly for “31/32” prefix notations.

• CMP-10960: Improved Trunk Member Status collection and Trunk Group Usage timer task to reduce amount of data requested in Avaya Aura CM module.

• CMP-10969: Replaced calendar widgets to make them JRE 17 compatible.

• CMP-10970: Fixed Dashboard Maps configuration page to make it JRE 17 compatible.

• CMP-10972: Removing poll function will delete historical data using poller compression mechanism.

• CMP-10973: Fixed the issue with saving edited Event Delay entries when multiple entries were configured for the specific Event Id.

• CMP-11002: Enabled manual onboarding of Cisco Room OS devices connected to Microsoft Teams in Cisco Video module.

Known Issues

• N/A

Documentation

• N/A