Table of Contents

 

About EdgeView 16.1.1 Release Notes

This document describes new features, the latest hardware and software requirements, known limitations and other pertinent release information for the latest release of EdgeView 16.1.1.

Related Documentation

The EdgeView 16.1.1 documentation is located at the following Ribbon Wiki space: EdgeView Documentation Home

Release Notes Use and Distribution

Ribbon product release notes are protected under the copyright laws of the United States of America. This work contains proprietary information of Ribbon Communications, 6500 Chase Oaks Blvd, Suite 100, Plano, TX 75023 U.S.A. Use, disclosure, or reproduction in any form is strictly prohibited without prior authorization from Ribbon Communications.

Problems or Questions

For problems or questions, contact the Ribbon Support through telephone or fax:

  • Ribbon Support Portal: https://ribboncommunications.com/services/ribbon-support-portal
  • Voice: +1-833-RIBBON1 (1-833-742-2661)
  • Japan Support Assistance Center: +81-3-6414-8550  (Japanese Language Support)
  • Former Edgewater Networks Technical Assistance Center: +1-408-351-7200,#2 or +1-408-351-7255 (Americas), +44-203-769-0576 (EMEA)


About EdgeView Service Control Center

EdgeView Service Control Center offers a multi-tenant approach for remote configuration and central management of Ribbon Communications Intelligent Edges. The Service Control Center also offers auto-provisioning of VoIP phones without the overhead of running a complex software on separate hardware.

Using the EdgeView software, enterprises and service providers can monitor and troubleshoot VoIP performance statistics from a central location, thus enhancing the support services provided to their customers. As a virtualized micro-services based appliance, EdgeView offers excellent scale, high performance, agility, and cost-effectiveness providing a solid secure foundation for those enterprises and managed service providers considering hosted or managed, premise cloud or hybrid UCaaS offerings.

EdgeView manages networks of all sizes. EdgeView can be deployed as a standalone system or in a high-availability virtualized micro-service configuration for carrier-grade environments.

Supported Platforms

EdgeView version 16.1.1 supports the following platforms:

  • 302/304
  • 2900
  • 4550v2
  • 4806v2
  • 4808v2
  • 6000
  • 7304

Refer to EdgeView and EdgeMarc Interoperability Matrix for a detailed EdgeView interoperability matrix.

Required Software Versions

The following software versions are required for this release and are available for download from the Customer Portal:

ProductDateSoftware/Update Package
EV 16.1.1 Software

 

Filename: cluster-install-ev.sh Filesize26408 
Filename: install-ev.sh Filesize: 26714
Filename: ev-fullpkg.tar.xz  Filesize: 3492719423 

How to Verify Currently Installed Software/Firmware Versions

Use the EdgeView SCC WebUI to verify the currently installed software version.

  1. Open the WebUI and click the Admin tab.
  2. On the Admin page, you can see the current software version under Software Version.

Upgrade Notes

This section contains specific upgrade notes for customers planning to upgrade to EdgeView 16.1.1. For details on supported releases and upgrades, see Upgrade EdgeView.


For an EdgeMarc Swap (eSWAP) use case, EdgeView can be configured to automatically import legacy EdgeMarc devices and collections from 14.x.x to 16.x.x. Once configured, any future 14.x.x modifications are automatically reflected on 16.x.x. To synchronize an EdgeView 14 with an EdgeView 16, refer to Synchronize EdgeView 14 with EdgeView 16.

Resolved Issues - Severity 1


Issue IDCase No.SevProblem DescriptionResolution
1SCC-8396201210-3496581

ESWAP does not transfer the SIP settings from EdgeMarc 4550 to EdgeMarc 2990. 

The EdgeMarc GUI SIP settings page on the newer EdgeMarc device (2900) reflects the values from the older EdgeMarc router configuration.

Resolved Issues - All Other Severities


Issue IDCase No.SevProblem DescriptionResolution
1SCC-8430201221-3511793

The EdgeView GUI for Release Candidate (RC) does not show the updated build. 

Note: GA software is not affected.

'Docker image' output lists build reference (git hash) in the TAG.  

16.0.4RC1 images match the git hash - eccb88b.
16.0.4RC2 images match the git hash - 6506a8f.

2SCC-8437201223-3513324

The '/' in the Call ID gets treated as a path navigation to a non-existent page. The SIP call ID sometimes shows the error '404 - Not Found', when users try to view the call ladder and SIP call record. There is also no option to go back to the previous page.

Resolution: Call ID parameter has been updated from a path parameter to a query parameter. With the fix, If a call ID includes a "/" as part of the call ID, the call details are properly displayed in the page. 

3SCC-8328201124-3471013

After performing Replace Device action, the action log on the EdgeView falsely displays ESWAP failure when the configuration was successfully transferred. 

Change the DHCP parameter configuration setting to static.

Remove the variable PPPoE_PING=off from the configuration file. 

4SCC-8483-3Prepared statements discarded in the last minute because cache limit reached" are observed in the Cassandra log file:

This is due to the prepared statements not formed properly. In CDR report generation query statements are formed by concatenating parameters instead of using placeholders and binding them. This has been fixed.
5SCC-8465-3

MOS aggregation service causes a huge load on the EdgeView SCC.

Do not start a new process for each collection.
6SCC-8480-3The internal grid listener service leaks memory by not deleting listeners from its map. The map size continues to grow over time.Fixed memory leaks in internal grid listener service.
7SCC-8435201209-3494153

Unable to replace the same pair of legacy and replacement devices on which a successful ESWAP was performed earlier. 

Perform cfg_restore in device and remove the device from the EdgeView 16 GUI. 

8SCC-8220201026-3423863

EdgeView 16.1.0 GUI does not update MOS scores due to an unhealthy Cassandra container. 

Remove the purging and compaction services permanently from Cassandra. 
9SCC-8489/SCC-8465210120-3549053

Aggregation processes cause performance issue and cassandra container becomes unhealthy, unable to response to request to retrieve Average MOS score. Fixed aggregation processes not to spawn multiple processes to aggregate collection data.

N/A


Known Issues - All Severities


Issue IDCase No.SevProblem DescriptionWorkaround
1SCC-8235201106-3442473

All policy-triggered upgrades onEdgeMarc fails for VOS 16.0.x versions.

Log in as ztpuser, set firmware ignore for the policy and save the changes. 
2SCC-8434201222-3512893After performing ESWAP and unplugging the legacy device, the device status stays 'online' for 20 minutes after disconnecting.

 N/A

3SCC-8433201222-3513213

The EdgeView Collection System Report functionality does not initiate a download for 15 to 20 minutes after selection.

N/A

4SCC-8436201222-3513302

The password requirements for EdgeMarc router is different when configured directly than that of configuring through EdgeView GUI. 

The EdgeView System is a central management piece and always enforces the latest security requirements as intended to manage the latest VOS on all EdgeMarc routers.

5SCC-8488210120-3549173

In certain configurations, the EdgeView cannot connect to the EdgeMarc GUI. 

N/A
6SCC-8237201105-3442403

The ev_scc and ev_nginx_ssl containers are experiencing poor connectivity causing the EdgeView GUI to disconnect. 

N/A
7SCC-8519-3

ESWAP does not support a device with WLR configuration. WAN Link switching can happen during ESWAP, and EdgeView 16 will not be able to pull the configuration from EdgeView 14, when this occurs during ESWAP process.

N/A
8SCC-8438201223-3513363

EdgeView does not display the IP address of EdgeMarc 2900PoE after an upgrade or downgrade. 

Upgrade the EdgeMarc version to 15.6.0 or later. 

9SCC-8526-2Docker restarts Cassandra as it does not respond to the Docker Health Check.N/A
10SCC-6842201207-3488093

Add an EdgeMarc to Edgeview (primary VM) after EV HA deployment:

  1. Login to EdgeView.
  2. Select an EdgeMarc from the Device > List page.
  3. Go to the Analysis page.
  4. Click on the TAKE SNAPSHOT button.

Once the action is completed, and you try to download the logs by clicking on the download icon, the following is observed:
the "Snapshot doesn't exist" message is displayed in the EdgeView, even though the Action log reported "Completed successfully".

To be resolved in 16.2 GA.


New Features in This Release

SCC-8458 Registration Info Panel on the Evadmin Configuration Page 

The Registration Info panel on the evadmin configuration page allows the user to see the current registration key. Users can also validate or re-register EdgeView as required.   

SCC-8393 Ribbon Cloud Migration

Existing Jenkins infrastructure moved to centralized Jenkins and Artifactory resources.