Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'}
JIRAIDAUTHTP-577
REV5UserResourceIdentifier{userKey=8a00a0c866dc3dee0166ea60b86f0014, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c8664c0be0016687d83fdb0025, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c8601a1bc701602339d1190006, userName='null'}

Table of Contents

Panel
borderColormaroon

 

Table of Contents
maxLevel3
indent5

...

This section contains specific upgrade notes for customers planning to upgrade to

Spacevars
0product
 16.1.0. For details on supported releases and upgrades, see Upgrade EdgeView.


Info

For an EdgeMarc

Spacevars
0product3
 Swap (eSWAP) use case,
Spacevars
0product
can be configured to automatically import legacy EdgeMarc
Spacevars
0product3
 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
Spacevars
0product
14 with an
Spacevars
0product
16, refer to Synchronize EdgeView 14 with EdgeView 16.

...


Issue IDCase No.SevProblem DescriptionResolution
1SCC-8133201005-3391312

The

EM

Spacevars
0product3
 container was not recovering from a container based interruption.

This has been fixed.
2SCC-8111

200929-338234, 201016-341086, 201130-347809

2The Edgeview GUI seemed

The 

Spacevars
0product
GUI seems slow (when changing between devices in the 'Device List' page) as a result of the

EM

Spacevars
0product3
 container being unhealthy.

This has been fixed.
3SCC-8082-3Navigation Bar to only show what is VisibleThe options in the top navigation bar are visible according to the user's provisioned roles.
4SCC-7593200519-3173603High Availability clusters that were running inside of environments that prohibit direct root ssh access during cluster formation were unable to successfully form.Alternative mechanisms were implemented to allow cluster formation and operations to occur on different ports without direct root ssh access between the cluster members.
5SCC-8220

201026-342386, 201016-341086, 201130-347809

3Cassandra container was not healthy Software improvements made to Cassandra configuration to address this. 

...


Issue IDCase No.SevProblem DescriptionResolution
1SCC-8272-

Elastic indexing of cassandra SIP calls causes performance issue.

Indexing each from/To DID SIP calls takes up lots of CPU time giving a slow performance. 

For this release, the indexing is disabled. Other options are being explored to index the DIDs to achieve search by DIDs functionality without degrading the performance.

1SCC-8465-
MOS and other call aggregation code is creating a huge load on the system.TBD

Known Issues - All Other Severities


Issue IDCase No.SevProblem DescriptionResolution
1SCC-6842201207-3488093

Add an

EdgeMarc to Edgeview

Spacevars
0product3
 to
Spacevars
0product
 (primary VM) after

EV

Spacevars
0product
 HA deployment:

  1. Login to
EdgeView
  1. Spacevars
    0product
    .
  2. Select an
EdgeMarc
  1. Spacevars
    0product3
         from the Device > List page.
  2. Go to the Analysis page.
  3. 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

Spacevars
0product
, even though the Action log reported "Completed successfully".

To be Resolved post Release 16.1.0

2SCC-8028-3

Inbound/Outbound call:

  1. Log in
EdgeView
  1. to 
    Spacevars
    0product
         and navigate to the node.
  2. In
EdgeMarc
  1. Spacevars
    0product3
    ,     check Recent call logs under the System Analysis page - OUT MOS under Analysis page - Displays N/A.
TBD
3EM-25755201201-3479783

VOS version 15.6.0 is the minimum VOS for this NEW 2900PoE when

EdgeView 15

Spacevars
0product
 15.x or 16.x is being deployed.

in VOS 15.6.0 and earlier for the new 2900PoE, the /var/ewn_model parameter is not present, which is required by

EdgeView to

Spacevars
0product
 to display the correct model in the

EdgeView UI

Spacevars
0product
 UI.

2900PoE RevB with VOS 15.6.0 or lower the

EdgeMarc displays incorrectly in EdgeView.

Spacevars
0product3
 displays incorrectly in
Spacevars
0product
.

Spacevars
0product3
 2900PoE

EdgeMarc 2900PoE

RevB must have a minimum VOS of 15.6.0 for

EdgeView 16

Spacevars
0product
 16.0.4 or greater. The label located on the bottom of the system is 125-2900EPoE-01-B for identification purposes.

4SCC-8328

201124-347101


3

eSWAP process ends with “unsuccessful” error message w/ EV 16.0.2.


Validate status of

Edgemarc and

Spacevars
0product3
 and ignore error message if the actual eSWAP was completed successfully.

65-

201207-348811

-

Request for Feature: Unable to remove the corrupted (e.g. incompatible FW release)

Edgemarc and

Spacevars
0product3
 and start over w/

EV 16

Spacevars
0product
 16.0.2 &

EM VOS

Spacevars
0product3
 VOS 15.5.1.

Investigation started.
76SCC-8438TBD201223-Excluded Devices failure reason is not fully readable.   The reason for the failure is cut in half from EV16.0.4.Open3513363

Spacevars
0product
 16

8-TBD-EdgeView 16

.0.4 has stopped to display

of

an IP address of

EM2900PoE for an unknown reason.  This issue is reproduced on EM2900e.		Open

any 

Spacevars
0product3
 model for an unknown reason.

Upgrade 

Spacevars
0product3
to 15.6.0 or later firmware. Older firmware like 15.5.1 does not send the NAT’ed IP to
Spacevars
0product
 and only the public address.  If an
Spacevars
0product3
 has been running 15.6.0 firmware, managed by
Spacevars
0product
 and downgraded to 15.5.1,
Spacevars
0product
 will continue to show that NAT’ed IP.

79SCC-8009-4

Unable to open SWe Lite and other 

Spacevars
0product3
 devices immediately after registering to 
Spacevars
0product
.

Wait 10 - 15 minutes and the system will open.
8SCC-8436201222-3513302

Password requirement for 

Spacevars
0product3
router is different when configured in EV16 vs directly on 
Spacevars
0product3
.

This is as designed. The 

Spacevars
0product
System is a central management piece and always enforces the latest security requirements as intended to manage the latest VOS on all 
Spacevars
0product3
routers.


New Features in This Release

...

Spacevars
0product
 uses unique certificates to manage mutual authentication between EdgeMarcs
Spacevars
0product3
s and
Spacevars
0product
. 

SCC-8016 The Enhanced Collection card displays Rolled up Status from Devices within the Collection Hierarchy

...

Three critical items namely; Total calls, Peak calls and Average MOS are run on a daily basis from 

Spacevars
0product
reports. It has the ability to run the report as well. The user needs to download the report and the downloaded report is in JSON format. Reports which are dependent on aggregation scripts such as Average MOS, Total Calls and Peak Calls report, only works for the call data generated on EdgeView 16on 
Spacevars
0product
16.1.0  and not for the old call data.

...

Under the Rules List and Schedule Jobs List pages, a view-only user can only see the User List or the 'Yes/No' option below Status. Also. a view-only user can navigate to Auto-Provision Devices page by selecting the Status option under the Provisioning tab.

SCC-

...

8257 
Spacevars
0product
allows multiple replacements on the same legacy device

Spacevars
0product
 allows EdgeView allows replacing the same legacy device multiple times to facilitate lab testing before rolling into production. 

...