Release Notes for Aternity on-premise 11.0.x

Version 11 of Aternity on-premise offers significant steps forward in functionality and features.

Deploy Aternity on-premise 11

You can deploy a clean setup of Aternity on-premise 11.0.x (learn more).

For the new features in Aternity on-premise 11.0.x release, learn here.

Aternity 11.0.x resolves several known issues related to dashboards and setup.

Aternity 11.0.1 successfully passed an extensive security check (also known as pen test).

Known Issues

Description In Version

In the Agent Administration screen, the version column sorting does not work as expected and does not display the versions in the numeric order.

11.0.1

If password of the Aternity Messaging Broker Docker Component (Kafka) includes special characters, the Aternity Management Server cannot connect to it.

11.0.1

On the Docker Components server, the executed command aternity-docker-admin fails to restart the SDA Server (Service Desk Alerts).

To resolve, use sudo ./aternity-docker-admin stop <component name> and sudo ./aternity-docker-admin start <component name> commands instead. Learn more.

11.0.1

When reconfiguring Aternity Docker Components Server, an error message Cannot connect to Cassandra might show.

To resolve, ignore it and continue. This does not have any impact on installation.

11.0.1

Log files of some Aternity components might show times of a different time zone than Management Server (Time zones of the Management Server and other Aternity components may differ.)

11.0.1

While reconfiguring Aternity Docker Components Server, setting password for Aternity Raw Data Docker Component (Cassandra) may fail due to a short timeout.

This does not have any impact on the installation process.

11.0.1

Changing Messaging Broker password causes Vertica Writer to lose connection to the Messaging Broker.

To resolve, restart both servers.

11.0.1

If in on-premise 9, users saved the Troubleshoot Device dashboard (although it should not have been saved), after upgrade to v11 it is still displayed in the main menu; although, you cannot open it, and the Enterprise Summary dashboard (default) loads instead.

11.0.1

Aternity update fails to run if the AternityPlatform service is up and running.

To resolve, stop the AternityPlatform service.

11.0.1

After a fresh installation, if no Agents have been connected within 4 hours, Vertica Scheduler may enter the Failing state. As soon as Agents are connected and data starts flowing to Vertica Database Server, the issue gets resolved.

11.0.1

In rare situations, after you update Aternity, the dashboards you saved in a previous version with Service Pack(s) attribute might appear empty. It might happen because this attribute name has been changed to OS Version(s).

To resolve, open a dashboard, adjust timeframe and make sure to select OS Version instead of Service Pack(s) in Breakdowns and Filters. Save if necessary.

11.0

In some cases, after you update Aternity, the homepage returns to its default, Enterprise Summary.

To resolve, define your homepage again.

11.0

LDAP users cannot access Aternity REST API.

11.0

Docker Components setup deploys Raw Data Component and Messaging Broker with hard coded network port values, rather than allowing users to set them.

11.0

In the Troubleshoot Activity and Analyze Business Activities dashboards, Aternity calculates Incoming Traffic and Outgoing Traffic using an Average, instead of a Sum, and therefore, the calculation is wrong.

11.0

The Aternity Docker Components Server stores truststore and keystore passwords in clear text in the container definitions for those containers that can be configured with ssl.

11.0, 11.0.1

Aternity Product Tours display the wrong product version.

To fix this, go to Aternity > Settings > Advanced Settings > account > walkMeSnippet and update the following: test-cloud to test-onprem.
Update the script to play the correct tours

11.0

No data displayed in the Analyze Installed Software (Advanced) dashboard.

11.0, 11.0.1

REST API, Data Source for Portal, and SDA components may fail to connect to Vertica DB if Vertica user’s password contains certain special characters. To resolve, download the patch from the v11.0.1 release page at the Riverbed Support site and replace the file utils/properties.py. Run the setup or reconfigure the server.

11.0.1

Resolved Issues

Description Issue ID Salesforce ID Resolved in Version

DNS is displayed as an attribute on the Device Details dashboard, although it is deprecated.

DE20545

1148175

11.0.1

LDAP users cannot access Aternity REST API.

DE20549

NA

11.0.1

It is impossible to configure SAML if the Aternity console URL structure does not comply with the SAML policy.

DE20725

1162071

11.0.1

Vertica Installation script fails on error No Vertica license is installed due to some issues with licensing file copy/paste permissions.

DE20733

1131563

11.0.1

In rare cases, database performance issues might occur in Oracle because Aternity_nam_statistics_job gathers stats on daily partitions not once a day, but every 20 minutes, which overloads the system.

DE20953

1159987

11.0.1

LDAP single account users with System Administrator privileges cannot perform administrative tasks on local users.

DE20114

1132170

11.0

Wrong group assignments for "Browser Extension/Add-On Version" cause errors in the Agent log.

DE20249

1146035

11.0

Changing the color of columns in the Advanced dashboards causes data to disappear from the screen.

DE16119

844873

11.0

If the Troubleshoot Device Health dashboard was customized using multiple Category values and saved, then when opening the dashboard (it loads using the URL), it loads empty.

DE17598

874682

11.0

In the Validate Application Change dashboard, the Browser and Browser Versions breakdowns show the application name instead of the browser name.

DE17987

901111

11.0

Cannot export WPM monitor via the Monitors Tree, where the name of an activity contains an asterisk (*).

DE18348

912018

11.0

In the Analyze Process Resources dashboard, Virtual Memory (Average) and Physical Memory (Average) measurements have a negative value.

DE19038

1087244

11.0

For some Agents, the Agent version is incorrect in the Analyze Device Inventory dashboard.

Although the Agent version in the Device Details dashboard is correct.

DE19208

1085083

11.0

The Commonalities Analysis dashboard returns the data source connection error when filtering the Total Activities column by At Least 1.

DE18992

1081091

11.0

An Email template for automatic alerts regarding incidents is incorrect.

DE19098

1078793 / 1082306

11.0

A memory leak in the Management Server causes a restart.

DE19027

1082306

11.0

Although the User Experience dashboard displays the Crash (After Hang) event, it does not show in the tooltip of the UXI column in the Analyze Applications dashboard. In the tooltip, the calculation for Crashes per Hour of Use includes the Crash (After Hang) event, but the calculation for Crashes + Browser Crashes does not include this event.

DE19295

1093748

11.0

The User Experience screen returns Data Source Error.

DE19309

1092937

11.0

When creating reports, the PDF report generated by Tableau shows the content of a wrong dashboard.

DE18668

1063310

11.0

(For IE only): In the Device Details dashboard with newly installed apps, when changing the time zone for Yours (GMT+3), the server returns an error 5038 because the time zone is not recognized.

DE19514

1109921

11.0

The Latency column in the User Experience dashboard is missing even for the devices that have this data.

DE19450

1106089

11.0

Inconsistency between data in SteelCentralâ„¢ Portal and Aternity console.

DE19589

1106950

11.0

Compatibility

Aternity on-premise 11 requires that devices ONLY run Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0.

Aternity on-premise 11 is compatible with Aternity Mobile packages 10.0.x and 11.0.x

Aternity on-premise 11 requires that Mac devices will only run Agent for Mac 3.1