Release Notes

Learn about new features and enhancements, fixed issues, and known issues in Oracle Communications Unified Assurance.

6.1.0.0.0 - April 10, 2025

Release 6.1.0.0.0 includes new features, enhancements, bug fixes, and documentation updates.

New Features in 6.1.0.0.0

This section describes the new features for release 6.1.0.0.0.

Migration to OpenSearch and Observability Analytics

This release replaces Elasticsearch with OpenSearch as the Historical database for analytics, including Event Analytics (now called Observability Analytics), Flow Analytics, and Log Analytics. OpenSearch is an open source program with industry-wide active support and updates. It provides advanced machine learning capabilities for anomaly detection and supports flexible use and licensing models, including clustering.

Other related components that have been replaced include:

• OpenSearch Dashboards replace Kibana dashboards. The functionality is similar, but with a slightly different appearance. Dashboards have been migrated automatically.

• Fluentbit and Fluentd replace Filebeat for log collection and ingestion. A Fluentbit instance running on each server collects logs, and Fluentd inserts the logs into the Historical database, supporting clustering, redundancy, and failover. You can view and search logs from Unified Assurance components in OpenSearch Dashboards.

• Event Analytics is now called Observability Analytics. This change is reflected in the documentation and licensing, while navigation menus in the UI remain the same.

New installations of version 6.1.0.0.0 automatically include OpenSearch and all required supporting framework. You use AnalyticsWizard to set up your OpenSearch cluster, and the cluster can consist of multiple nodes.

Because licensing for Elasticsearch will no longer be available, all customers must move to version 6.1 and migrate to OpenSearch before March 31, 2026. On this date, Elasticsearch license keys will expire. Elasticsearch will stop accepting new data, and you will lose access to existing unmigrated data.

If you are using an earlier version of Unified Assurance, including versions 4, 5, and 6.0.X, you must upgrade or update to 6.1 on Linux 8. This may involve several phases, including an operating system upgrade. See Supported Migration Paths in Unified Assurance Migration Guide and About Upgrading Unified Assurance in Unified Assurance Installation Guide for full details.

After updating to version 6.1.0.0.0, you migrate to OpenSearch as follows:

• Most data and components are migrated automatically when you update to 6.1.0.0.0, including saved objects, dashboards, standard anomaly detectors, index patterns, and more.

• You use the new MigrateHistoricalData application to migrate your Event and Flow Analytics indexes.

• You manually migrate some custom artifacts, including Snapshot Management policies for automated backups.

See About Migration in Unified Assurance Migration Guide for information about migration.

Note the following:

• Unified Assurance uses JSON Web Signatures to authenticate with OpenSearch. The keys and certificates for the assure1 user, as well as OpenSearch internal users and roles that correspond to the Unified Assurance Analytics Viewer, Operator, and Admin permissions, are created automatically.

• The MySQL Replication Data Importer service replicates data from the Event database to the OpenSearch Historical database. This now also includes event journals.

• Event journals now include JournalActor and JournalAction fields to specify the actor and action that added the journal. When creating event tools, you must also specify JournalActor and JournalAction (though you can set them to null values if you are not enabling journaling for the tool).

• OpenSearch is supported in FIPS-enabled Oracle Linux 8 systems

Migration from Redis to Coherence

This release replaces Redis with Oracle Coherence as the in-memory data cache for microservices. You do not need to perform any migration tasks other than undeploying the Redis microservice and deploying the new Coherence microservices.

Coherence provides thread-safe, distributed caching that supports scalability, high availability, database sharding, SSL security, and parallel query processing. Coherence runs as a cluster, automatically managed by Coherence Operator.

For more information about the Coherence microservices in Unified Assurance, see the following topics in Unified Assurance Implementation Guide:

• Coherence describes how to deploy the microservice and access the CLI.

• Coherence Operator describes how to deploy the operator.

• Device Cache Warmup describes the microservice for loading devices into Coherence.

• Lookup and Cache Lookup Properties describe how to use lookups in FCOM overrides to access Coherence cache entries.

For more information about Coherence, see the following resources:

• In Oracle Fusion Middleware Developing Applications with Oracle Coherence:

  • Introduction to Coherence

  • Using Coherence Query Language

• On GitHub:

  • Coherence Operator

Universal Topology Enhancements

This release includes the following enhancements and fixes to Universal Topology:

• You can now define custom functions that apply when you interact with edges and vertices in Universal Topology graphs. These functions can override the default functions.

  The custom functions can occur before the interaction takes place (for example, to block functions, such as preventing a node from being dragged) or after the interaction takes place (for example, to perform a custom function after clicking on a node). You implement the custom functions as UI overrides to the GraphsPanelViewController file. See Overriding a User Interface and Overriding Universal Topology Graphs in Unified Assurance Developer's Guide for information.

• When creating topology tools:

  • You can specify whether the tool applies to all nodes and edges, all nodes, all edges, a specific node type, or a specific edge type.

    To support this, the REST API endpoint for creating tools now includes the following additional optional properties in the request body:

    • ContextElement

    • ContextEdgeType

    • ContextVertexType

    See Tools in Unified Assurance User's Guide for information about creating custom Universal Topology tools and see the Create a Topology Tool endpoint in REST API for Unified Assurance Core for information about using the new fields.

  • You can specify a function name in the Path field and set the Path Type field to Function. This lets the tool apply a function implemented as an override to GraphsPanelViewController.

    See Overriding Universal Topology Graphs in Unified Assurance Developer's Guide for information about implementing functions to use with topology tools as overrides.

• When navigating a topology graph with a geographic layout, you can hold the Shift key while clicking and dragging the mouse to select an area to zoom in on.

• Universal Topology now uses Ogma version 5.2.0. Because of the Ogma version upgrade, Oracle recommends testing any Universal Topology overrides you have implemented before moving your Unified Assurance 6.1 environment to production.

• When editing a vertex, you can no longer change the Vertex Type. When editing an edge, you can no longer change the start and end vertex.

• When creating a vertex, if you add a custom property called Name, when you click Submit, the value for that property replaces any value you entered in the Name field under Vertex Information. Previously this resulted in an error.

• The Geo Map and Tile Server fields have been moved from the View section to the Layout section, under Advanced Configuration. They only appear when you select Geographic Map from the Type menu.

Vision Enhancements

This release introduces the following enhancements for Vision:

• Vision now includes zone information for devices:

  • On the Entities page, you can view and edit an entity's zone on the View tab, and you can specify zones when adding entities on the Add tab. See Entities in Oracle Communications Unified Assurance User's Guide for more information.

  • On the Vision map, on the General tab for markers, zone information is included. See Interacting with Events on the Map in Oracle Communications Unified Assurance User's Guide for more information.

  • Entity names throughout the Vision UI now include zone information. Entity names by themselves are no longer required to be unique; the combination of Entity name and zone information is unique.

• The Vision API supports zone information, but zone ID is not a required in post requests.

• A new Vision REST API guide is available in the documentation library on Oracle Help Center and in the documentation available within the product. This guide fully describes the endpoints and request schemas and provides an example use case for managing Vision links. It replaces the previous Vision API information page.

  See REST API for Unified Assurance Vision.

Externally Requested Enhancements in 6.1.0.0.0

This release includes the externally requested enhancements described in the following table.

Fixed Issues in 6.1.0.0.0

This table describes the externally reported bugs fixed in release 6.1.0.0.0

Internal Fixes and Enhancements in 6.1.0.0.0

Release 6.1.0.0.0 includes the following additional internally-reported bug fixes and enhancements:

AAA:

• Previously, it was possible to delete or rename the default API user. This is no longer possible.

• Previously, usernames were not case sensitive. This has been fixed.

• While viewing your user profile, clicking the help button now displays the User Profile documentation.

• The DefaultTimeZone global property was not applying to the default Operators user or user group. This issue has been fixed.

• The PageSize user or user group preference was not being applied. This issue has been fixed. Event lists use the EventListPageSize preference and all others use the PageSize preference.

• In the Users UI, when adding users, incorrect or inconsistent default fields were displaying. This issue has been fixed.

• When the main navigation menu was collapsed, you were unable to navigate to your user profile by clicking on the circle icon around your abbreviated username. This issue has been fixed.

• The Depot FQDN global property has been removed. It was no longer being used.

Broker:

• Previously, when scheduling jobs, you could enter 0 in the Every time fields (for example, Every 0 Minute(s)). This was invalid and crashed the browser. This issue has been fixed. You can no longer enter 0, it automatically changes to 1.

• When you select a server in the Servers UI, read-only fields (Name, Platform, and BootTime) are no longer rendered as though they are editable.

Dashboards:

• Previously, you could not edit locked dashboards, including the default dashboards. Now, you can edit them, but you cannot delete them.

• For Dynamic Inputs panels, in the API menu, the Device(combo) option has been deprecated. Now, use the Device(devicecombo) option instead. This option returns serialized device names (the device name and zone ID) instead of just device IDs.

• The help button on various dashboard panels was not working. This issue has been fixed. Relevant documentation is now displayed.

Devices:

• Date related fields in the Devices UI now also let you select a time.

• Unnecessary white space has been removed from the popups that appear when hovering over icons in the Devices UI.

• The UI for manually discovering a device now contains a Cancel button that you can click to go back to the device list without running discovery.

• When you delete a device configuration collection, any files created for it by the Config Gatherer job are also deleted.

• Attempting to delete a device group was not working. This issue has been fixed.

• Attempting to use the Remote button to start an SSH connection to a device did not work if the Guacamole service was not running, but the error message was not clear. This issue has been fixed.

Diagrams:

• The Diagrams UI now uses correct colors for the dark theme.

• Background images in diagrams were not scaling correctly. This issue has been fixed.

Events:

• Previously, when configuring event displays, the values you entered for column width were not validated. You could enter invalid values, like text strings, which resulted in columns being hidden from the event list. This issue has been fixed.

• The date picker in the event list now uses correct colors for the dark theme.

• Previously, when filtering the event list by columns, if you selected a different event filter or event filter type from the Filter Type and Filter menus, the column filtering remained, further filtering the event list. This issue has been fixed. Now the column filtering clears when you change filters or filter types.

• Previously, if you used an API request to create an event tool, the tool was always added with journals enabled, even if you set the JournalStatus property to 0 and JournalStatusName to Disabled. This issue has been fixed.

• Previously, if you added a custom event field with the DATETIME type and selected Default to NULL or set a blank default value, the ApplyEventSchema application failed to add the fields. This issue has been fixed.

• Previously, if a large number of results were returned in the event list, the counter that displays the number of results was cut off, and you could not see the total number of results. Now the counter expands appropriately to fit even large numbers of results.

Graph:

• In Adhoc Graph dashboards, pagination was not working consistently with the Start Vertex menu. This issue has been fixed.

Metrics:

• When filtering metrics in the Metrics UI or on dashboards, the Not Regular Expression option was not working as expected. This issue has been fixed.

• Metric charts were rendering incorrect time ranges when no data existed in the specified time range. This issue has been fixed.

Microservices:

• When deploying a microservice by using the UI, the Changes tab previously showed the changed version on the left, with new values highlighted in red, and the original version on the right with original values highlighted in green. This was contrary to conventional diffs, and has been fixed. Now the original version is on the left, with original values highlighted in red, and the changed version is on the right, with new values highlighted in green.

Reports:

• In the report Profiles UI, the Profile column is now less wide, and the appearance of the Notification column when the filter bar is displayed is consistent.

• When creating report profiles, there are now default values set for the PDF Orientation and Page Size fields, and the default value for the Archive Days to Retain option is changed from Never to Forever for improved clarity.

• Previously, you were able to submit a job for a report without setting the schedule fields. This issue has been fixed.

Rules:

• Deprecated Metric Generic SNMP Poller rules files that were no longer used in version 6 have been removed.

• The Default Commit Message text that was provided when committing a rules file no longer appears. Now, you can either enter a message or leave the field blank. This is consistent with commit dialogs used in other areas, such as for diagrams.

• When running a diff in the Rules UI, the Reverse from/to button was too small, resulting in truncated label text. The From Revision and To Revision paths were also not being updated when you clicked the button. These issues have been fixed.

• After deleting a rules file or folder, the entire tree was collapsing. This issue is fixed, and your current level of expansion is preserved.

• Previously, you were unable to create a rules file with no content. When you tried to commit, you were prompted to discard your changes. This issue has been fixed.

• Previously, when you uploaded a new rules file, you had to manually enter the name in the FileName field. Now this field is now automatically populated based on the file you select. You can still edit it to change the name if needed.

SLM services:

• When configuring SLM services and adding service metrics, the options in the Metric Instance menu were not changing when you changed the device. This issue has been fixed.

• If you deleted a service availability metric from an SLM service, the metric was deleted successfully, but an error was displayed. This issue has been fixed.

• Previously, metric charts for SLM services were showing thresholds configured for device metrics rather than the SLM-specific metrics. This issue has been fixed.

REST API updates:

• REST API requests to get a specific global property was not working. This issue has been fixed.

• REST API requests to get tools by ID was adding a separator in the response. This issue has been fixed.

• Responses to REST API requests to create event filter groups did not include the filter group ID. This issue has been fixed.

General updates:

• Previously, you could create objects that used integers for names, which created confusion with numeric IDs. Now, the UI and API contain validations to ensure that object names are not integers only or integers prefixed with the + or - symbols only. All object names must contain letters or other characters. For example, 1234, +1234, and -1234 are not valid, but US1234, US+1234 and US_1234 are. REST API for Unified Assurance Core now mentions this in the relevant name properties.

• Previously, web server responses included the PHP version in the header. This issue has been fixed. The PHP version no longer appears.

• Previously, the link type for the Knowledgebase wiki was External. This opened it in a new page, without the Unified Assurance menu, rather than embedding it within the Unified Assurance UI. This has been changed. Now the link type is Embedded by default. You can see or change this by selecting the Configuration menu, then Links, and then Links and clicking the Unified Assurance Knowledgebase link.

• Popup messages (also known as toast messages) displayed at the top center of the UI are now properly centered, long text strings wrap appropriately, and appropriate colors are used (green for success, orange for warning, blue for information)

• The Reset button in various UIs was not reverting changes as expected. This issue has been fixed.

• You were previously unable to update the values of names and links for bookmarks consistently. This issue has been fixed.

• A typo in the End User License Agreement that appears before updating has been fixed.

• If you deleted a database query, then added a new one, the query from the previous query was populated in the new one. This issue has been fixed.

• When filtering various tables by dates, clearing the date from the filter was not working until you pressed Enter. This issue has been fixed.

• Localization was not applied to some navigation menu items. This issue has been fixed.

• When adding files, you could submit the file without specifying a value for the Type field, causing the UI to crash. This issue has been fixed. The Type field is required and you cannot click Submit without setting it.

• All forms now have a minimum width. Previously, you were able to resize some to be too small to use.

Documentation Updates in 6.1.0.0.0

The documentation has been updated for the new features, enhancements, and issues described above. In addition, the following externally-reported documentation issues have been fixed in this release:

Additionally, the documentation for Performance Common Object Model (PCOM) curation has been updated with detailed information about the PCOM schema and definitions, an example file, and enhanced guidance on the PCOM curation process. See Performance for complete information.

Known Issues in 6.1.0.0.0

Due to the potentially high number of log entries and internal OpenSearch PPL query limit settings, the graphs and visualizations in the Logs UI for the default PPL query may not behave as expected. When viewing logs:

• Use the default PPL query in the Logs UI to see a live stream of the logs.

• Use OpenSearch Dashboards Query Language (DQL) queries in the OpenSearch Dashboards Discover application to search the complete logs and show meaningful graphs. See Searching the Logs with the Discover Application in Unified Assurance Concepts for more information.

6.0.5.0.0 - September 30, 2024

Release 6.0.5.0.0 includes new features and enhancements, bug fixes, and known issues.

New Features and Enhancements in 6.0.5.0.0

This section describes the new features and enhancements for release 6.0.5.0.0.

Publishing Events in TMF688 and TMF642 Format for Inventory Systems

This release includes a new microservice that converts standard Unified Assurance events into a format compliant with the TM Forum (TMF) 688 Event Management API specification, with embedded schemas for alarm events and performance threshold events from the TMF 642 Alarm Management API specification. The microservice publishes the converted events to an Apache Pulsar topic for consumption downstream. You can deploy the Kafka Bridge microservice (previously called Kafka Adapter) to consume the events and publish them to your external Kafka server, where external inventory applications, such as Oracle Communications Unified Inventory Management, can read the events from the Kafka topic and act on them accordingly.

See Understanding the Event Pipeline in Unified Assurance Concepts for information about how the new microservice fits into the overall flow, and Kafka Bridge and TMF688 Event Processor in Unified Assurance Implementation Guide for information about the microservices.

Vision Enhancements

This release introduces the following enhancements for Vision:

• UI enhancements:

  • You can select multiple markers on the Vision map by drawing a rectangular or freeform boundary or holding CTRL and clicking. You can add custom tools and custom context menus to use when selecting multiple markers. See Interacting with Events on the Map in Unified Assurance User's Guide for more information.

  • You can add pLink markers to custom layers. See Custom in Unified Assurance User's Guide for more information.

  • When adding a file or raw JSON to a custom layer, the data is checked to confirm that IDs are unique and that required fields exist. See Custom in Unified Assurance User's Guide for more information.

  • You can use the severity filter bar to filter custom markers as well as event markers. See Filtering Events by Severity in Unified Assurance User's Guide for more information.

  • You can add custom metadata to markers and search the map using the metadata. See Searching the Map Unified Assurance User's Guide for more information.

• New restrictions:

  • Previously, roles with the Operator for the Vision package had read, write, and execute access for Vision components. Now the Operator permission for the Vision package grants read access only.

  • Previously, you could specify multiple sources for Vision data. Now, assure1 is the only supported source. The documentation about configuring sources has also been removed.

  • Previously, Vision enriched events in Unified Assurance with power data along with coordinates and weather. Now, Vision does not consume utility feeds like power outages or show them on the map.

• API enhancements:

  • You can access documentation for the Vision REST API and download the OpenAPI JSON definition.

  • The vision API now uses SSL certificates for authentication and authorization instead of a gatekeeper service.

  See REST API for Unified Assurance Vision.

• Installation enhancement: Previously, when running SetupWizard to install Unified Assurance, Vision roles were not included when you chose to install all roles, and you had to install Vision roles separately. This has been fixed.

Microservices Enhancements

This release includes the following new microservices to integrate with external systems:

• ActiveMQ Bridge: Provides bidirectional communication between ActiveMQ and Unified Assurance Pulsar topics.

• ServiceNow Adapter: Retrieves events from the Unified Assurance Event database, publishes them to ServiceNow for ticket creation, and keeps both systems updated with ServiceNow work log and Unified Assurance event journal entries.

• Webhook Collector: Collects messages from a custom webhook endpoint and publishes them to a Unified Assurance Pulsar topic. By default, this is the topic for the Event Sink microservice.

The following microservices have been enhanced:

• CORBA Collector:

  • Can now communicate with SSL-enabled Element Management Systems.

  • Now consumes events with some common vendor-identified fixes to the TMF814 specification in the CosNotification.idl and FlowDomain.idl structures. See CORBA Event Details for information.

• Cisco Meraki Poller: Now supports database failover in addition to microservice redundancy.

• Discovery Service: When making PATCH API requests at the /inventory endpoint, you can now optionally remove any interfaces from a device that are not specified in the request payload. See REST API for Unified Assurance Microservices for details.

• Event Canal:

  • The Event Canal microservice uses the MySQL binary logs to stream events to the Unified Assurance Event database. You can now choose where the microservice should start streaming events when its pod restarts. See About Event Canal and the MySQL binlog for information.

  • The microservice exposes a new Prometheus metric to track the number of binlog events received.

• Event Sink:

  • You can now enable this microservice to group database records into batches and insert the batches into the Event database. Batching events enhances performance by reducing the backlog of events, better handling event bursts, and mitigating high latency between the external devices where events are collected and the database.

  • You can now enable autoscaling for this microservice.

  • When this microservice deduplicates an event, it now also updates the ExpireTime field, preventing problems when clearing incoming event transitions.

• FCOM Processor: Exposes new Prometheus metrics for discarded events, errors during overrides, and number of events from different sources.

• Kafka Bridge (previously called Kafka Adapter):

  • You can now use OAuth or basic authentication when communicating with Kafka servers, and you can communicate with external SSL-enabled Kafka servers.

  • You can now enable autoscaling for this microservice when using a Unified Assurance Pulsar topic as the input.

  • You can now enable redundancy for this microservice when using a Kafka topic as the input.

  • Can participate in the TMF Flow of the Event microservice pipeline. See Publishing Events in TMF688 and TMF642 Format for Inventory Systems.

• Ping Poller: The command to disable autoscaling and the configuration parameter for setting the percentage of discovery workers have been made consistent with those used in other microservices, such as SNMP Poller.

• Syslog Collector:

  • Exposes new Prometheus metrics for UDP and UDP6 queue lengths.

• Trap Collector:

  • Now collects SNMP v2 and v3 informs. This requires you to create SNMP access profiles.

  • Exposes new Prometheus metrics for UDP and UDP6 queue lengths, number of traps per second, and number of discarded traps.

General microservice enhancements:

• Microservice loggers now use the appid field instead of pid to contain the pod name.

• When you deploy a microservice, the following settings are validated:

  • global.imageRegistry is set

  • The Pulsar microservice is being deployed to the a1-messaging namespace.

  • Keda or Prometheus-related microservices are being deployed to the a1-monitoring namespace.

  • The Redis microservice is being deployed to the a1-cache namespace.

• All microservices now use the same log level by default (INFO). You can change this by specifying the configData.LOG_LEVEL parameter when deploying a microservice.

• The batch size for Pulsar payloads has been increased to 50MB.

SELinux Support

Unified Assurance version 6.0.5.0.0 is supported on environments with SELinux set to enforcing.

See the following topics in Unified Assurance Installation Guide:

• See Linux Prerequisites for information about preparing to install Unified Assurance on an SELinux-enabled system.

• See Updating Unified Assurance for information about how to update from an earlier version of Unified Assurance, with SELinux disabled, to version 6.0.5.0.0 with SELinux enabled and enforcing.

New Device Support

This release introduces support for new devices, fault MIBs, and performance metrics, including performance metrics for Ixia devices. See Unified Assurance Device Support Overview.

Enhancements

This release includes the externally requested enhancements described in the following table.

Documentation Updates

This release includes documentation to describe all of the new features and enhancements, documentation bug fixes, and the following additional major documentation updates:

• New card layout landing page: The Oracle Help Center landing page for Unified Assurance now features a new task-based card layout to help you find information more easily. The old book list layout is also still available by selecting Books from the panel at the left of the landing page.

• Enhanced microservice documentation:

  • In Unified Assurance Concepts, microservice information is organized in one place, and new topics describe microservice pipelines and give end-to-end details about the Event Pipeline.

    See Understanding Microservice Pipelines and Understanding the Event Pipeline.

  • Unified Assurance Implementation Guide contains a new topic that describes microservice management tasks at a high level. The topic for setting up microservice clusters has been moved to the microservices section for easier reference. The documentation for each microservice has been updated with the latest configurations and functionality, and edited for style and clarity.

    See Managing Microservices and Microservice Cluster Setup.

  • The JSON reference schemas that define the output for the TMF688 Event Processor microservice are included. See Reference Schemas.

• Installation documentation:

  • Topics have been reorganized to make finding them easier, and edited for style and clarity.

  • The procedure for upgrading Unified Assurance from Linux 7 to a new Linux 8 system has been extensively updated to support upgrades with minimal downtime. See Upgrading Unified Assurance to a New Linux System.

  • Linux prerequisites have been updated with requirements for SELinux, additional required ports to open, and additional firewalld configuration. See Linux Prerequisites.

• SDK documentation:

  • Unified Assurance Developer's Guide now includes information about building custom UIs, creating UI overrides, and building custom packages. See Core Interface SDK Overview.

• Documentation about user and group ownership and viewer access has been added in Unified Assurance Security Guide. See Configuring Ownership and View Access.

• Core REST API documentation:

  • All POST requests now list the minimum required parameters.

  • Examples of query parameters have been added to some metrics-related GET requests to make it easier to successfully filter data.

  See REST API for Unified Assurance Core.

Fixed Issues in 6.0.5.0.0

This table describes the externally reported bugs fixed in release 6.0.5.

Release 6.0.5 includes the following additional internally-reported bug fixes and enhancements:

• FCOM:

  • The standard ExpireTime for fault resolution events in FCOM foundation rules has been updated to 3600.

  • In a redundant cluster, when the Graph database was restarted (as in a failover situation), some FCOM overrides were timing out when trying to connect to the database. This resulted in events that should have been filtered by the override instead getting through. This issue has been fixed. The FCOM Processor now retries the database connection instead of timing out.

  • The MIB2FCOM and FCOM2Rules applications are now processing varbinds for MacAddress and DateAndTime correctly.

  • The math processor now supports the modulo operator (%).

  • Previously, if you used multiple referenced variables with the same key-value pair in syslog overrides, the event text was not properly populated. This issue has been fixed.

  • FCOM2Rules now includes conversion types to convert OCTET STRINGS into various formats. See Preprocessors for the Fault component of the COM SDK in Unified Assurance Developer's Guide.

  • In v2 overrides, you can now use eq or ne operators in addition to == and !=. These are standard Perl operators, and were previously supported in v1 overrides.

  • For the FCOM Processor microservice, the processing_time_per_event and total_events_processed Prometheus metrics were not being updated. This has been fixed.

• SLM Services:

  • In dashboards for SLM services:

    • Service Compliance panels used vertex ID for the title. This was not helpful. The title now contains the service name instead.

    • When you refreshed Services panels, the color icons were not updating. This issue has been fixed.

    • When you changed the time range in one panel, other panels were not updated to reflect the new time range. This issue has been fixed.

  • In the Service Management configuration interface, dragging and dropping services was not working. This issue has been fixed.

  • The Event SLM Engine service was not processing events for SLM services with realtime thresholds. This issue has been fixed.

• Installation:

  • When installing Unified Assurance on Linux 8, the SetupWizard log included warnings about deprecated Perl features for the CreateSSLCertificate application. This issue has been fixed.

  • Previously, when running SetupWizard to install Unified Assurance on a redundant server, if the redundant server did not have the same roles as its primary partner, the installation would fail very late in the process. Now SetupWizard checks that the roles are the same, and fails much earlier if they are not.

• Microservices:

  • Metrics in redundant systems: After running Redundancy Wizard, metrics were not being populated unless the telegraf-kafka microservice was restarted using the command line (the Telegraf microservice was not responsive in the UI). This issue has been fixed.

  • Supervised Event Correlator: When multiple severities were listed as possible symptoms in a supervised correlation, the Supervised Event Correlator microservice was only using the first severity value for symptom processing, preventing events from being correlated properly. This issue has been fixed.

  • SNMP Poller:

    • This microservice was experiencing performance issues, including inaccurate application of autoscaling limits and worker percentages, incorrect log messages, and overlapping poll cycles. These issues have been fixed.

    • This microservice now gets profiles from profiles in zone 0 as well as the active zone.

    • You can now configure the period of time to wait for a GRPC connection by setting the GPRC_CONN_DOWN_DEADLINE parameter when deploying the microservice. The default is five seconds.

  • Command line:

    • Previously, running clusterctl with the --debug flag was not showing debug logs for Rancher Kubernetes Engine (RKE), only info logs. This has been fixed.

    • Environment variables for the Kubernetes repository cache and configuration have been added to the assure1_bashrc script that sets the variables. This allows users other than the root user to run kubectl commands and their aliased a1k counterparts (after running assure1_bashrc).

  • The Help links for some microservice Helm charts and workloads were not working. This issue has been fixed.

• UI:

  • For configuration interfaces with tree grids (lists of groups or menus), the Add button was automatically enabled before you selected an element from the list, and you were able to delete or clone the root-level element. This issue has been fixed.

  • Devices:

    • The way device zones are shown has changed. Generally, zone ID is used instead of zone name. When device names are displayed with zones, a serialized device name that combines device name and zone ID (for example, device_name;z1) is used, rather than device name and zone name.

    • When devices in different groups had similar names, selecting their group was not opening the correct page. This issue has been fixed.

    • In dashboards with metric panels, when devices in different zones had the same name, incorrect metric types were appearing. This issue has been fixed.

    • When selecting devices for actions while creating diagram widgets, if multiple devices in different zones had the same name, you could not distinguish between them. This has been fixed. Now each device's zone name also appears in the list of devices.

    • In multiserver environments with multiple database shards, device metrics and topology were not updating correctly for all shards. This issue has been fixed.

  • Custom event fields: The interface for adding custom event fields had a variety of validation issues allowing you to set invalid default values and invalid combinations of size and precision for different field types. These issues have been fixed.

  • JSON in Rules: Previously, the Rules configuration UI required any JSON entered in rules to be valid. Uploading, creating, or editing a file with incorrectly-formatted JSON in the UI failed. Now, it is possible to upload, create, or edit JSON files with incorrect formatting. It is your responsibility to provide valid JSON. You can use the Check syntax button in the Rule editor to check the syntax, but incorrect formatting will not prevent you from clicking Submit. See Rules in Unified Assurance User's Guide for information about the Rules configuration interface.

  • SNMP access profiles: The way version numbers are represented when configuring SNMP access profiles has been made consistent. Previously, version three appeared as just 3. Now it appears as v3.

  • Group and user ownership, user settings:

    • If a user selected a UI elements where User Owner or Group Owner were set to a specific group or user, and that user was in the viewers group but was not the owner or in the owner group, that user's group was showing in the Group Owner field. This has been fixed. Now HIDDEN is shown in this situation.

    • Setting Group Owner for event filters was preventing the filters from appearing in the Event Filter Group UI. This issue has been fixed.

    • When configuring users, you were previously able to add their primary group to their subgroups list as well. This issue has been fixed. Now, trying to add the primary group as a subgroup returns a validation error.

  • When configuring package depots (from the Configuration menu, select Broker Control, then Package Depots), it was possible to use invalid values in the Locations field. As a result, when attempting to update a server, the list of depots failed to load. This issue has been fixed.

• When using the command line, you can now press Tab to autocomplete commands with the Unified Assurance aliases defined in the assure1_bashrc script. These include the aliases starting with a1 for:

  • Databases, such as a1db, a1mysql, a1influx, and a1neo4j.
  • Microservices, such as a1helm, a1k, a1docker, a1kube, and a1cluster.
  • a1perl and a1svn.

  Review the contents of assure1_bashrc for a full list.

• Network Interface Poller was not using custom maximum values when checking whether to use spike prevention. This issue has been fixed.

• You can now prevent the Topology Gather Network Inventory job from pruning data based on TimeStampModified. When configuring the job, add the new DisablePruning configuration option and set it to Enabled.

Known Issues in 6.0.5.0.0

Due to an issue in Rancher Kubernetes Engine (RKE), the clusterctl update command is disabled. This command is commonly used to change a cluster from using a single master to use multiple masters. There is no workaround.

6.0.4.0.2 - February 29, 2024

Release 6.0.4.0.2 includes new features and enhancements, bug fixes, and known issues.

New Features and Enhancements in 6.0.4.0.2

This section describes the new features for release 6.0.4.0.2.

Support for Oracle Linux 8

This release is supported on Oracle Linux 8 as well as Oracle Linux 7. Upgrading installations can choose between Linux 7 and 8, and all new installations must use Linux 8.

For details, see the following topics in Unified Assurance Installation Guide:

• Linux prerequisites in Linux Prerequisites.

• Upgrade information in Upgrading Unified Assurance on Linux 7 to Linux 8.

• Update information in Updating Unified Assurance.

For general information about Oracle Linux 8, see the Oracle Linux 8 documentation.

FIPS Compliance

When you install Unified Assurance release 6.0.4.0.2 on Oracle Linux 8, you can enable Linux to be compliant with the Federal Information Processing Standards (FIPS) Publication 140-2. FIPS 140-2 is a U.S. government computer security standard used to validate cryptographic modules that include both software and hardware components.

Installing Unified Assurance on Linux 8 in FIPS mode ensures that the application only uses FIPS-certified modules. This allows the individual components of Unified Assurance 6.0.4 to be compliant with FIPS 140-2, including all databases, layers, and integrated third-party applications.

Some of the benefits of being compliant with FIPS 140-2 are:

• Ensures a high degree of system security.

• Demonstrates that the product has passed rigorous testing with an accredited laboratory.

• Ensures that the product can store sensitive information safely. Customer data will not be compromised in the event of a breach.

For more information about how FIPS is supported in Unified Assurance, see FIPS Compliance in Unified Assurance in Unified Assurance Security Guide.

For more information about how FIPS is supported by Oracle Linux 8, including how to configure a system in FIPS mode, see FIPS 140-2 Compliance in Oracle Linux 8 in Oracle Linux 8 Enhancing System Security.

CORBA Collector

This release introduces the Common Object Request Broker Architecture (CORBA) collector microservice to collect events from external Element Management Systems (EMS) and Network Management Systems (NMS). The CORBA collector lets you collect Multi-Technology Network Management (MTNM) CORBA events and normalize them for handling within Unified Assurance using standard event analysis features such as event enrichment, correlation, and filtering.

For details about the CORBA collector, see CORBA Collector in Unified Assurance Implementation Guide.

Java SDK

This release introduces a software development kit (SDK) based on Java 17 to help you build Java-based microservices for Unified Assurance. The Java SDK includes:

• A Java microservice template with a number of built-in capabilities including logging, configuration, and connectivity

• A sample microservice that you can reference when building your microservice following standard Unified Assurance design patterns.

For details about the Java SDK, see Java Microservice SDK in Unified Assurance Developers Guide.

Root Cause Analysis Availability Engine

This release introduces a Root Cause Analysis Availability Engine microservice to automatically correlate device outage events with their root cause. When a device goes down, the microservice looks at the network topology for the device to identify where the outage originated, and enriches the event with information about the root cause and other downstream symptoms. You view the information in the Unified Assurance Event user interface, and you can use it to identify the right place to resolve outages.

For details about root cause analysis, see Understanding Root Cause Analysis in Unified Assurance Concepts.

Device Discovery and Polling Microservices and REST API

This release introduces a new device discovery flow and polling microservices for monitoring device status. You can now discover devices and add them to the Device database by consuming incoming REST API POST requests. The Discovery Service microservice processes the requests, sets up the appropriate device zones, groups, and pollers, and sends the device information to the new DOM processor to be added to the databases. The SNMP, Ping, and VMware Poller microservices monitor the discovered devices at configured intervals and send availability status messages to Pulsar topics for other microservices to consume.

For details about the new flow, see Understanding the Discovery Pipeline in Unified Assurance Concepts.

For details about the new REST API, see REST API for Oracle Communications Unified Assurance Microservices.

Juniper Mist Integration

This release includes integration with Juniper MIST through microservices that connect to the MIST REST API. The Mist Poller microservice polls topology data to be included in the Graph database and the Mist Event Collector microservice polls alarms and events. To support discovery and monitoring, this microservice integrates with other microservices, including discovery, root cause analysis, topology, and the FCOM Processor.

For details about the new microservice, see Mist Poller and Mist Event Collector in Unified Assurance Implementation Guide.

New Device Support

This release introduces support for new devices, fault MIBs, and performance metrics. See Unified Assurance Device Support Overview.

REST API Documentation

This release includes complete documentation for the core Unified Assurance REST APIs. You can use the REST APIs to configure and manage objects in the Unified Assurance database and user interfaces. The features described in the REST API documentation were previously supported, but not fully documented.

See REST API for Unified Assurance Core.

Enhancements

This release includes the externally requested enhancements described in the following table.

This release includes the following other enhancements:

• Monolith aliasing used in various Unified Assurance libraries has been removed. This eliminates erroneous alias warnings when running applications.

• Documentation has been added for the following panels, described in Unified Assurance User's Guide:

  • Panel - SLM Tree

  • Panel - Diagram

  • Panel - Dynamic Inputs

• When using the Graph Edges configuration interface, you must apply filters to the list of vertices before seeing results.
  To apply filters, scroll to the far right of the table and click the filter icon. Enter filter values under any of the columns, and click the Apply Filters button to apply them and display data. Oracle recommends filtering at least by start vertex.

• You can now apply filters in the vertices, edges, and metrics UIs by pressing enter on your keyboard. Previously you had to click a button.

• You can use custom background images on Topology Graph dashboards. See Background Image Settings under "Universal Topology User Guide" in Unified Assurance Implementation Guide for more information.

• When you add or edit a topology graph panel on a dashboard, you can choose from some default values for the advanced layout settings for some sample use cases. See Layout Settings under "Universal Topology User Guide" in Unified Assurance Implementation Guide for more information.

• When viewing a topology graph, you can apply filters to limit the number of items that are displayed. See Topology Graph under "Universal Topology User Guide" in Unified Assurance Implementation Guide for more information.

• You can now add users to more than one user group. This gives you greater flexibility in managing user access. For example, you can create different user groups with different roles and permissions for different domains, then add users to the groups for all the domains that they manage. For more information about users, roles, groups, and permissions, see Authentication Options and Adding User Accounts in Unified Assurance Security Guide.

• You can now use a user interface to add custom fields to the Events table in the MySQL database. Previously this was managed in the command line, which is no longer supported. For details about the new user interface, see Adding Custom Fields to the Event Database in Unified Assurance Implementation Guide.

• A new compatibility matrix has been added to the Unified Assurance documentation. This document outlines software and versions that are compatible with Unified Assurance. See Unified Assurance Compatibility Matrix.

Fixed Issues in 6.0.4.0.2

This table describes the externally reported bugs fixed in release 6.0.4.0.2.

The following additional internally-reported bugs are fixed in release 6.0.4.0.2:

• Several Vision UIs with custom configurations were returning 404 API responses. These have been fixed.

• The Supervised Event Correlator microservice was concatenating the strings for SQL queries. SQL statements with bound arguments were added to fix this.

• A missing agent node was erroneously removed from the Trap Collector microservice. This has been restored.

• Diagram widgets with Link Type set to manual (external) were not working properly. This issue has been fixed.

• In the Installed Microservices Configuration UI, microservices with long service names were not wrapping properly and clicking on them changed the page layout. This issue has been fixed.

• EngineID was coming up as an empty field for SNMP v3 traps in the Trap Collector microservice, preventing proper profiles lookup. This issue has been fixed.

• Dashboards that load devices with the readForSelect API were not displaying properly. This issue has been fixed.

• Secondary microservices were trying to process data even while the primary microservice was healthy due to an incorrectly called defer function. This issue has been fixed and the function is being called in the right place.

• Tree combo pickers in application configuration UIs were not working as expected; some were displaying pagination controls and not loading data. This issue has been fixed.

• Dashboard panels were not showing what zone a device was from. This issue has been fixed and there is now a Device Zone Name column.

• In the Devices UI, opening and then closing the topology view for any device was resulting in console errors. This issue has been fixed.

• In the Service Management UI, attempting to edit SLM services that did not have compliance properties or realtime properties resulted in an error. This issue has been fixed.

• Upgrading a cluster from Unified Assurance 6.0.2 to 6.0.3 was failing due to an error with clusterctl. This issue has been fixed.

• Swagger dependencies in Vision have been updated for Spring Boot 3.

• The Event Mechanizations UI was truncating the mechanization code it displayed when END IF statements were included. This issue has been fixed.

• Attempting to delete a layer in Vision was not working. This issue has been fixed.

• Manually reloading a dashboard was causing an error and changing the URL into a value that got longer with each reload attempt. This issue has been fixed.

Known Issues in 6.0.4.0.2

This section describes the known issues and workarounds for release 6.0.4.0.2.

Trap and Syslog Messages Not Forwarding to Collectors

If you are using Kubernetes version 1.19.16 and trap or syslog messages are already being sent to the server before setting up the Trap Collector or Syslog Collector microservices, new messages may not be sent to the collectors after the microservices are set up. This is especially relevant if you are using a trap forwarder.

The microservice setup adds new connection rules to forward packets to trap and syslog collectors, but if entries already exist, the new rules will be ignored.

To resolve this issue, delete the existing connection tracking entries after setting up each microservice as described in "Syslog Collector" and "Trap Collector" in Unified Assurance Implementation Guide.

To delete the connection tracking entries:

1. In a multiserver deployment, from the command line, access the node where you installed the collector.

If you did not specify a node when installing the collector, or you do not know which node it was installed on, get a list of pods and their details, including nodes, by running the following command:

a1k get pods -o wide

1. Run one of the following commands, depending on the collector:
   • For the Trap Collector microservice:

     conntrack -D -p 162
     

   • For the Syslog Collector microservice:

     conntrack -D -p 514
     

This issue is not present in later versions of Kubernetes, including those distributed with the latest release of Unified Assurance. To avoid this issue, you can upgrade to the latest version of Kubernetes on your existing cluster. See Making Customizations to an Existing Cluster in Unified Assurance Implementation Guide.

Deprecated Features in 6.0.4.0.2

Unified Assurance no longer supports the RADIUS user authentication type.

If you are upgrading or updating to version 6.0.4.0.2, any existing user accounts using the RADIUS authentication type are switched to the internal authentication type. Before these accounts can be used again, you must either set passwords for them or change them to a different authentication type.

See "Authentication Options and Adding User Accounts" in Unified Assurance Security Guide for information about authentication types and configuring user passwords.

See "Authentication Types" and "Users" in Unified Assurance User's Guide for information about the related configuration interfaces.

6.0.3.0.0 - September 5, 2023

Release 6.0.3.0.0 includes new features and enhancements, bug fixes, and known issues.

New Features and Enhancements in 6.0.3.0.0

New features and enhancements in release 6.0.3.0.0:

• [OCUA-1177] - Non-local kibana traffic should go through /go/k
• [OCUA-2405] - Dashboard "Network Traffic" panel should show the Threshold Alerts column
• [OCUA-2797] - [34779877] Document how to implement custom logos in the splash screen, login screen, and navigation
• [OCUA-3118] - ifAlias should be visible in the "Interfaces" tab of the "Network Details" panel in the Device Overview dashboard
• [OCUA-3119] - Index the ifAlias, ifName and IfDescr columns in the Graph database schema
• [OCUA-3384] - Add new User and User Group preference to control adding an event Journal entry for any edit done in the event list
• [OCUA-3532] - Add update functionality to graph-sink for vertices and tuples
• [OCUA-3644] - Ciena MCP REST/Kafkacomet API Integration
• [OCUA-3965] - Add teles certified fault Foundations support
• [OCUA-4095] - Document how to change the background color on alternate rows in tables
• [OCUA-4259] - Create Pulsar "availability" namespace where required
• [OCUA-4290] - Add delta certified fault Foundations support
• [OCUA-4291] - Add ascend certified fault Foundations support
• [OCUA-10034] - Add timetra certified fault Foundations support
• [OCUA-10211] - Add xylan certified fault Foundations support
• [OCUA-10236] - Add digital-link certified fault Foundations support
• [OCUA-10240] - Add sun certified fault Foundations support
• [OCUA-10241] - Add usr certified fault Foundations support
• [OCUA-10246] - Add cabletron certified fault Foundations support
• [OCUA-10260] - Add fore certified fault Foundations support
• [OCUA-10267] - Add Universal Topology User Guide documentation
• [OCUA-10269] - Add a3com certified fault Foundations support
• [OCUA-10271] - Add nai certified fault Foundations support
• [OCUA-10275] - Add ibm certified fault Foundations support
• [OCUA-10276] - Add rapidCity certified fault Foundations support
• [OCUA-10278] - Add hh3c certified fault Foundations support
• [OCUA-10287] - Telegraf should have a way to persist custom configurations
• [OCUA-10314] - Add blade certified fault Foundations support
• [OCUA-10329] - Add codex certified fault Foundations support
• [OCUA-10330] - Add synoptics certified fault Foundations support
• [OCUA-10331] - Add netgear certified fault Foundations support
• [OCUA-10387] - Add alcatel certified fault Foundations support
• [OCUA-10448] - Update Graph Sink microservice to support edgeMeta type inserts from dom-processor
• [OCUA-10592] - Add additional dataConnectionLtd certified fault Foundations support
• [OCUA-10601] - Improve graph sink microservice performance
• [OCUA-10604] - [34873909] - Create binaries for Unified Assurance to Vision integration
• [OCUA-10810] - Add dataConnectionTraps certified fault Foundations support
• [OCUA-10967] - Dashboard "All Metrics Overview" panel should have an option to exclude Disabled devices when different Device Sources are selected
• [OCUA-11004] - Optimize the CorrelateProblemResolutions mechanization to improve processing speed
• [OCUA-11014] - Add configuration option to append snmpTrapAddress to varbind and fix Trap Forwarder microservice bugs
• [OCUA-11027] - Add node name to the "agents" object field within Trap Collector microservice and Syslog Collector microservice to indicate which server received the message
• [OCUA-11043] - Added Device Zone ID to readMetricStatus calls for diagram metric widgets
• [OCUA-11054] - Log4j plugin needs to be removed from Kafka
• [OCUA-11055] - Update Apache httpd to v2.4.56
• [OCUA-11095] - Remove prometheus configurability from microservices
• [OCUA-11102] - Replace neo4j-go-driver-v5 deprecated functions with new versions
• [OCUA-11126] - Improve InfluxDB performance
• [OCUA-11127] - Metric Standard Thresholding Engine should be more robust when influx queries time out
• [OCUA-11153] - Add frequentis certified fault Foundations support
• [OCUA-11189] - [35126998] - Add omnitron certified fault Foundations support
• [OCUA-11190] - [35127010] - Update cisco certified fault Foundations support for MPLS-LDP-MIB
• [OCUA-11192] - [35129806] - Add ceragon certified fault Foundations support
• [OCUA-11193] - [35129820] - Add zte certified fault Foundations support
• [OCUA-11194] - [35129837] - Add versa certified fault Foundations support
• [OCUA-11196] - [35129918] - Add ruggedcom certified fault Foundations support
• [OCUA-11197] - [35129948] - Add additional symmetricom certified fault Foundations support
• [OCUA-11198] - [35130372] - Add cyberArkMIB certified fault Foundations support
• [OCUA-11199] - [35130608] - Add net certified fault Foundations support
• [OCUA-11200] - [35130617] - Add pulsesecure-gateway certified fault Foundations support
• [OCUA-11202] - Change clusterctl to use mutating admission webhooks
• [OCUA-11205] - [35130894] - Add Microchip Enterprise timing certified fault Foundations support
• [OCUA-11213] - Add telindus 1424 & 1645 routers certified fault Foundations support
• [OCUA-11221] - Default font size should be smaller for vertex labels and can be configured, and the number of characters shown in a label can be configured in Topology Graph dashboard panels
• [OCUA-11222] - Vertex labels should by default have a lighter background color, and background color can be configured in Topology Graph dashboard panels
• [OCUA-11223] - Change validation limit of "Node Distance" and "Level Distance" to 1000 in Topology Graph dashboard panels when using the Hierarchy layout
• [OCUA-11224] - Change validation limit of "Charge" and "Edge Strength" to 100 in Topology Graph dashboard panels when using the Force layout
• [OCUA-11225] - Remove the Sequential layout option in Topology Graph dashboard panels
• [OCUA-11233] - Filebeat should have a way to persist custom configurations
• [OCUA-11234] - Kafka and Telegraf-Kafka should have a way to persist custom configurations
• [OCUA-11237] - [35149840] - Update RabbitMQ to v3.11.10 and Erlang to v25.2
• [OCUA-11253] - [35151042] - Add machine learning policies to Flow Analytics
• [OCUA-11297] - [35176669] - Dashboard "Device Info" panel should support exporting the data
• [OCUA-11306] - [35185352] - Flow Collector microservice should support generically named environment variables
• [OCUA-11307] - [35186310] - Add "Threads" as a configuration option to the Event Run Mechanizations job to support mechanizations being run sequentially
• [OCUA-11337] - Add a visual indicator to the "Devices" navigation to indicate a device in a device group is in a maintenance window or is disabled
• [OCUA-11362] - Update PHP to 8.1.17
• [OCUA-11363] - Update HTTP::Daemon Perl module to 6.16
• [OCUA-11364] - Update Kafka to 3.4.0
• [OCUA-11365] - Update jQuery-UI to 1.13.2
• [OCUA-11366] - Update ejs to 3.1.9
• [OCUA-11446] - Add dhyan certified fault Foundations support
• [OCUA-11447] - Add additional hitachi certified fault Foundations support
• [OCUA-11448] - Update compaq certified fault Foundations support
• [OCUA-11473] - [35260833] - Add a button to the dashboard "Device Info" panel to open the entry in the device catalog "Devices" UI, add a button to the device catalog "Devices" UI to open the "Device Overview" dashboard for that device
• [OCUA-11474] - [35260853] - Graph "Vertices" UI requires a filter to show data to limit impact on the database
• [OCUA-11486] - Update Net::HTTP Perl module to 6.22
• [OCUA-11527] - [35303406] - Neo4j connections should failover and failback properly
• [OCUA-11528] - [35303439] - Event Aggregators and the Metric Standard Thresholding Engine should log going into and leaving Store & Forward mode using the WARN logging level
• [OCUA-11530] - [35303583] - Add new TrapReplay application to extract historical traps for replay testing
• [OCUA-11537] - [35309747] - Update Perl Module::Runtime to version compatible with Moose::Util
• [OCUA-11538] - [35312801] - Add a visual indicator to the "Devices" navigation to indicate a device is in a maintenance window or is disabled
• [OCUA-11544] - Add Perl module Config::Tiny version 2.29
• [OCUA-11549] - Add microwave-radio-2 certified fault Foundations support
• [OCUA-11550] - Add additional extreme certified fault Foundations support
• [OCUA-11554] - Update the Java Apache Pulsar client library used in Vision applications
• [OCUA-11555] - Update Java PostgreSQL library to 42.6.0
• [OCUA-11558] - [35341797] - Kibana should have a way to persist custom configurations
• [OCUA-11561] - [35342707] - Add Affirmed certified fault Foundations support
• [OCUA-11584] - Update MediaWiki to v1.39.3
• [OCUA-11595] - Add huawei certified fault Foundations support
• [OCUA-11600] - Add sni certified fault Foundations support for X733GROUP-MIB and TNMS-MIB
• [OCUA-11633] - Update SpringBoot to 3.1.0
• [OCUA-11636] - Update guacamole client and server to 1.5.2
• [OCUA-11637] - RabbitMQ should use high security cyphers
• [OCUA-11642] - Update RabbitMQ to 3.11.11
• [OCUA-11662] - [35429960] - Add tandem certified fault Foundations support
• [OCUA-11663] - [35429984] - Add nortele certified fault Foundations support
• [OCUA-11664] - [35430021] - Add scopusRoot certified fault Foundations support
• [OCUA-11666] - [35430245] - Add threepar certified fault Foundations support
• [OCUA-11667] - [35430461] - Add radisys certified fault Foundations support
• [OCUA-11668] - [35430489] - Add Tandberg Television certified fault Foundations support
• [OCUA-11669] - [35430503] - Add pti certified fault Foundations support
• [OCUA-11685] - [35434956] - Add additional dell certified fault Foundations support
• [OCUA-11697] - Update rke to 1.4.5 and Kubernetes to 1.25.9
• [OCUA-11713] - Update Java to 11.0.20
• [OCUA-11722] - [35479235] - Add audioCodes certified fault Foundations support
• [OCUA-11736] - [35494583] - Add ees certified fault Foundations support
• [OCUA-11737] - [35494665] - Add tlabPENRoot certified fault Foundations support
• [OCUA-11738] - [35494715] - Add jma certified fault Foundations support
• [OCUA-11739] - [35494789] - Add radioBridgeRoot certified fault Foundations support
• [OCUA-11749] - Implement SQL database failover in microservices
• [OCUA-11750] - Implement Neo4j database failover in microservices
• [OCUA-11773] - ElasticSearch Database should run using the integrated vendor java
• [OCUA-11809] - Add _source indexed field to graph schema for all vertices and edges
• [OCUA-11829] - Update MySQL to 8.0.33
• [OCUA-11865] - Update Go Microservices dependencies to match BA's for 6.0.3.0.0
• [OCUA-11868] - Update docker to 20.10.24
• [OCUA-11870] - [35620333] - Add frontier certified fault Foundations support
• [OCUA-11871] - [35620393] - Add ericsson certified fault Foundations support
• [OCUA-11872] - [35620412] - Add CastleRock certified fault Foundations support
• [OCUA-11874] - [35620454] - Add dmc certified fault Foundations support
• [OCUA-11875] - [35620584] - Update eltek certified fault Foundations support
• [OCUA-11876] - [35620598] - Add ascotInternational certified fault Foundations support
• [OCUA-11877] - [35620627] - Add raritan certified fault Foundations support
• [OCUA-11878] - [35620654] - Add additional hp certified fault Foundations support
• [OCUA-11879] - [35620667] - Add lenovo certified fault Foundations support
• [OCUA-11880] - [35620675] - Add additional ibm certified fault Foundations support
• [OCUA-11881] - [35620692] - Add picaPrivateMib certified fault Foundations support
• [OCUA-11882] - [35620699] - Add rfCode certified fault Foundations support
• [OCUA-11883] - [35620785] - Add additional vmware certified fault Foundations support
• [OCUA-11884] - [35620892] - Add harmonic certified fault Foundations support
• [OCUA-11885] - [35620906] - Add additional sonus certified fault Foundations support
• [OCUA-11886] - [35620917] - Add cumulusMIB certified fault Foundations support
• [OCUA-11913] - [35620351] - Add bcsi certified fault Foundations support
• [OCUA-11957] - Update Pulsar to 2.11.2 and Helm Charts to 3.0.0
• [OCUA-11975] - Update submariner to 0.14.6
• [OCUA-11983] - [35706821] - Device SNMP Discovery should discover SNMPv3 Engine ID during discovery, and the Event Trap Aggregator and Trap Collector microservice should then check the Engine ID

Fixed Issues in 6.0.3.0.0

Bugs fixed in release 6.0.3.0.0:

• [OCUA-1269] - Diagrams UI should show the correct values for the "Timestamp Modified" and "Last Revision" columns
• [OCUA-1271] - Diagrams UI should show the correct value for the "Diagram Type" column
• [OCUA-2141] - [35111890] - Event Mechanizations edits should be propagated to other Event Shards
• [OCUA-2467] - Foundations rule file changes should be updated in the default branch
• [OCUA-2836] - Grafana should have a way to persist custom configurations
• [OCUA-2885] - Users editing an event within an event list should change the Action field to "edit"
• [OCUA-2923] - Unified Assurance Package Manager binary should log when it is done working
• [OCUA-2972] - Update the "How To Override Default Vendor Configurations" documentation
• [OCUA-3283] - All logging in libraries should properly reference from where they were called
• [OCUA-3408] - Fix Graph.pm logging to be consistent with the rest of the application
• [OCUA-3521] - Event Syslog Aggregator should correctly log the raw syslog message when running in DEBUG
• [OCUA-3661] - Optimize the CorrelateProblemResolutions mechanization to handle a possible race condition on flapping events
• [OCUA-3920] - graph-sink does not properly escape key values
• [OCUA-3949] - SLM service using a pre-defined threshold should still work properly in the SLM Gauge dashboard panel
• [OCUA-4060] - Loading a Dashboard on the main map in Vision should work properly
• [OCUA-10284] - Metric Poller Discovery should be optimised for MySQL
• [OCUA-10441] - [35230002] - Change default settings used for the Vision ingress controller to support uploading 15 megabyte images for use in Vision
• [OCUA-10468] - Topology context menu should maintain proper orientation and visibility when the graph is rotated
• [OCUA-10622] - Using a Device filter type in an Event List should better distinguish devices with the same name but are in different device zones
• [OCUA-10635] - [34902025] - Improve Metric Post-Collection Calculation Engine (PCCE) processing speed
• [OCUA-10639] - Neo4j queries should be parsed through the runCypher function
• [OCUA-10690] - [34944714] - Vision validations for Entities should properly handle IPv6 addresses that might be used to match to a Device
• [OCUA-10736] - Microservices that failed to deploy should be removable via the Microservices UI without returning a database error
• [OCUA-10746] - Vision validations for Entities should properly handle the different data that might be used to match to a Device
• [OCUA-10789] - Dashboard "Adhoc Graph" panels should work properly when the stack option is set to "All"
• [OCUA-10958] - Default diagram Tools should have up-to-date paths
• [OCUA-10993] - Topology Graph dashboard panels should show nested edges properly
• [OCUA-11010] - Metric Standard Thresholding Engine error messages should contain more useful information
• [OCUA-11013] - Clicking on a Device Group should always open the "Device Group Overview" dashboard in the Devices navigation
• [OCUA-11039] - Dashboard columns should be properly aligned on the right side
• [OCUA-11041] - "Data State" column in the Metrics UI should work for metrics with a Display Instance configured
• [OCUA-11045] - Event list tool "View Topology" should work properly with PHP8
• [OCUA-11066] - Metric "Adhoc Graph" dashboard panel should work when the toolbar is hidden
• [OCUA-11091] - Dashboard "All Metrics Overview" panel should work properly when sorting a large table by different values
• [OCUA-11121] - [35121524] - User accounts created using a non-internal authentication type should not check the validation on the password fields
• [OCUA-11122] - [35299780] - Preferences should load their data properly on the "Users" UI
• [OCUA-11133] - Improve metrics API execution speed
• [OCUA-11169] - Topology Graph tools should only replace tokens instead of the entire value
• [OCUA-11191] - Metric Poller Discovery should ignore virtual devices
• [OCUA-11201] - [35130631] - Event Trap Aggregator should not crash when returning from Store & Forward
• [OCUA-11214] - Elastic UIs should only show Unified Assurance navigation
• [OCUA-11217] - Add a direct link to Flow Analytics UIs in the Analytics navigational menu
• [OCUA-11218] - Time pickers in the Elastic UIs should more closely resemble the rest of the time pickers in the UI
• [OCUA-11219] - Changing "All Metric Overview" dashboard panel form selections should not interfere with each other
• [OCUA-11236] - SLM Metric definitions should work properly on display with predefined thresholds
• [OCUA-11238] - [35150376] - UI should support showing Grafana dashboard without the Unified Assurance navigation bar on the left
• [OCUA-11239] - [35529342] - Fix various issues found in configuration UIs when using different filters
• [OCUA-11240] - [35150400] - Password change screen should indicate whether it worked or not, and should redirect the user when they do it
• [OCUA-11242] - Navigating to the event analytics Management using the navigation should open the correct page and not automatically redirect to the Kibana home page
• [OCUA-11243] - [35150618] - Flow analytic Dashboards should use a consistent naming schema
• [OCUA-11247] - [35150745] - TL1 "Elements" UI should work when sorting and filtering by different columns in the grid
• [OCUA-11248] - Dashboard "Network Details" panels should correctly display interfaces on devices with 1000 entries or more
• [OCUA-11255] - After using the search in the "Devices" navigation page, collapsing and re-expanding a Device Group should still show the correct information
• [OCUA-11266] - SLM Metric configuration form should include Device Zone in the Device combo box
• [OCUA-11267] - "Device" picker combo boxes for diagram metric widgets should include the Device Zone
• [OCUA-11274] - Metric Generic SNMP Poller should update SNMP profiles during configuration CheckTime cycles
• [OCUA-11276] - Grid in the Metrics UI should include a Device Zone column to help differentiate devices with same name in different zones
• [OCUA-11281] - Event Aggregators and the Metric Standard Thresholding Engine should log the correct message-type being processed when going into Store & Forward mode
• [OCUA-11285] - Dashboard "All Metrics Overview" panels should show data properly
• [OCUA-11296] - [35176398] - Topology Graph dashboard panel in the Network Details dashboard should load data if a device has Neighbors
• [OCUA-11299] - [35176761] - Using the Topology Dashboard link from Vision should properly open the Network Details dashboard
• [OCUA-11304] - CLUSTER_NAME tag in InfluxDB for microservice metrics should be interpolated correctly during ingestion
• [OCUA-11309] - [35186656] - Operator user should have access to the Kibana UIs to view the event historical data using the Event List tools
• [OCUA-11310] - [35186670] - PHP should not FATAL when connecting to Graph Database
• [OCUA-11312] - "Upload" button should only be enabled when a valid folder or file is selected in the Rules UI, then disabled after different user actions
• [OCUA-11324] - Device catalog "Devices" UI validation error messages should show field names
• [OCUA-11325] - When multiple diagram widgets are selected, clicking on the diagram background should unselect all widgets
• [OCUA-11341] - Diagrams UI should handle multiple widgets being selected properly, and using the Quick Clone function with multiple widgets selected should keep the layer sequence in the view
• [OCUA-11358] - "Device Overview" dashboard should still work properly with different user interactions
• [OCUA-11374] - Expanding a vertex in a Topology Graph dashboard panel should still show the relevant badges
• [OCUA-11384] - Zoom slider should work more smoothly in Topology Graph dashboard panels
• [OCUA-11423] - Event list "Device Info" tool should work without an error in the browser console
• [OCUA-11427] - [35240445] - Migrate Event Root Cause Analysis (RCA) rules to use Neo4j connections by default
• [OCUA-11432] - [35244059] - Metric Standard Thresholding Engine should only send violations for enabled Metrics, and ignore disabled Metrics
• [OCUA-11433] - [35244089] - MetricBatchWriter should log the full body of an error
• [OCUA-11434] - [35244825] - Links to the "Device Overview" dashboard from the Devices navigation should include Device Zone information to ensure uniqueness
• [OCUA-11435] - [35244888] - Graph-based UIs should be able to handle very large numbers properly
• [OCUA-11438] - [35245679] - Add a visual indicator to the "Devices" navigation to indicate a device is in a maintenance window
• [OCUA-11441] - Fix issues affecting Vision configuration UIs not being visible and the event Severity bar missing when using Safari
• [OCUA-11469] - [35260720] - Metric Post-Collection Calculation Engine (PCCE) should properly set the availability state on a calculated metric
• [OCUA-11472] - [35260815] - InsertDBDataWorker should properly handle data values with spaces
• [OCUA-11487] - [35269434] - Devices that have a Custom Name should not have the name be stripped when searching in the Devices navigation
• [OCUA-11496] - [35278102] - Users should be able to set their DefaultTimeZone
• [OCUA-11498] - FindVertexID library function should handle duplicate Vertex names
• [OCUA-11503] - Fix the unicode so Topology Graph dashboard panels show a Firewall and Appliance properly
• [OCUA-11517] - [35298685] - Event Trap Aggregator should set the correct millisecond values for times
• [OCUA-11529] - [35303569] - Metric Missing Data Threshold Engine should properly quote sanitizing metric instances
• [OCUA-11531] - [35303594] - Add new Assure1::Log library function "IsLevel" that checks the application logging level and then only calls the log "Message" library function when appropriate to reduce logging impact, also add example to Event Trap Aggregator
• [OCUA-11532] - [35303607] - Add BulkInsert, BulkTime and Limit application configuration options to the Event Trap Aggregator to improve database insertion efficiency
• [OCUA-11539] - [35370088] - Event lists using Shard 0 should sort the data properly based on the Sorting Order set in the display that is used
• [OCUA-11543] - [35319110] - User should be able to have a DefaultLink
• [OCUA-11548] - [35329247] - Metrics UI should show a valid result count
• [OCUA-11551] - [35453538] - SAML should work properly when an environment has a Web FQDN alias
• [OCUA-11557] - [35341355] - Perl library function FindDeviceID() should be case-insensitive for DNS name
• [OCUA-11559] - graph-sink automatic edge direction support
• [OCUA-11560] - [35342703] - Improve handling of custom ports for LDAP authentication type
• [OCUA-11590] - Update Kubernetes to resolve ImagePullBackOff error
• [OCUA-11609] - Kafka Adapter microservice should properly parse JSON arrays
• [OCUA-11616] - [35392533] - Event Custom Action Policy Engine (CAPE) should run properly as a clustered service
• [OCUA-11617] - [35392618] - CreateVertexTree() library function should properly handle a numeric value being set for a vertex Property configured as a string-type
• [OCUA-11618] - [35392748] - Modifying a Backup service/job should leave the Primary service/job properly selected every time
• [OCUA-11621] - Replace spring-security-oauth2 in Vision
• [OCUA-11622] - Upgrading from v5.5.12 or later to v6 should complete without errors
• [OCUA-11627] - [35402297] - Core microservices should create or update fields starting with @
• [OCUA-11639] - Fix the validations for the SAML authentication type
• [OCUA-11641] - [35410094] - TL1 Gateway should use memory correctly and should not consistently increase memory usage over time
• [OCUA-11665] - [35430049] - Vendor RabbitMQ updates should remove files that are no longer used
• [OCUA-11683] - [35434193] - Kibana export and save menu should be visible in all available kibana-based views
• [OCUA-11716] - Pass DeviceZoneID properly to the PerformanceData API
• [OCUA-11723] - [35479262] - FindThresholdID library function should use the passed in Metric Field value properly
• [OCUA-11724] - [35479656] - Event Trap Aggregator should log originating IP Address or Node for "Invalid version" logs
• [OCUA-11725] - [35479671] - Event Trap Aggregator should log originating IP Address or Node for traps with an incorrect security level
• [OCUA-11727] - [35483282] - "Logs" navigational view should still show the Unified Assurance Navigation bar
• [OCUA-11728] - [35484017] - Update ConfigCheck in the Metric Standard Thresholding Engine to prevent segfaults and other issues
• [OCUA-11744] - [35495358] - Bundle the Metrics UI readStates call into the general read to reduce unnecessary calls for data
• [OCUA-11755] - [35503856] - Value used in SAML AuthnRequest NameIDPolicy should match the NameID Format provided in the Authentication Types UI
• [OCUA-11756] - Adding a Diagram panel to a dashboard should work without logging a javascript error in the console
• [OCUA-11768] - Filter unneeded and disable unnecessary Prometheus' kubernetes/cluster/self-health metrics, and increase the interval between metric collection periods
• [OCUA-11821] - Update microservice cluster certificates to remove keyUsage
• [OCUA-11873] - [35620420] - Device SNMP Discovery should recover gracefully when encountering a deadlock
• [OCUA-11887] - [35620923] - Influx should change integer values to floating point values for data storage
• [OCUA-11888] - [35620938] - Poller applications should FATAL if threads are terminated abnormally
• [OCUA-11889] - [35620994] - Context clicking should work properly on Edges in Topology Graph dashboard panels
• [OCUA-11890] - [35621023] - Change the defaults used in the Reports UI to have a Render Timeout value of 15 seconds
• [OCUA-11891] - [35621098] - Metric Standard Thresholding Engine should handle an Influx database query failure
• [OCUA-11914] - [35620951] - Event list panels should show all matching Events when using different device-based filters
• [OCUA-11915] - [35621001] - Tools using the Remote functionality should open the external site properly, Remote tools should work when opening in a New or the Same Tab

Known Issues in 6.0.3.0.0

Known issues in release 6.0.3.0.0:

• Changes to the Influx library functions to insert integer values as floats may impact metric collection for measurements that are currently stored as integers only. In certain circumstances where a measurement is currently inserted as an integer, the float values will not be written to the database until the Group Shard Duration for the retention period roles over to the next shard. If you suspect you may be impacted by this, the impact can be limited if the update is applied shortly before the Group Shard Duration for the retention policy is due to roll over.
• Administrators will need to synchronize the jobs for Flow Analytics after this update is installed. This is done on the Machine Learning UI.

Analytics -> Events -> Machine Learning

6.0.2.0.0 - March 9, 2023

Release 6.0.2.0.0 includes new features and enhancements and bug fixes.

New Features and Enhancements in 6.0.2.0.0

This release introduces Unified Assurance Flow Analytics. Unified Assurance Flow Analytics is a complete solution to collect, analyze, and provide real-time visibility into whom and what are consuming network bandwidth.

See Understanding Flow Analytics in Unified Assurance Concepts.

New features and enhancements in this release:

• [OCUA-1486] - [34605994] - Upgrade Elasticsearch Database, Kibana and MySQL Replication Data Importer to 7.17.8
• [OCUA-3779] - Collection microservices should scale out and scale back based on workload
• [OCUA-3826] - Add functionality to support Microservice Cross-Datacenter Redundancy
• [OCUA-3966] - Add papouchProjekt certified fault Foundations support
• [OCUA-4049] - Allow custom ports for LDAPS authentication type
• [OCUA-4055] - Add Trap Forwarder microservice
• [OCUA-4114] - Allow configurable client ServerID in Event Canal microservice
• [OCUA-4277] - Add netScaler certified fault Foundations support
• [OCUA-4278] - Add emerson certified fault Foundations support
• [OCUA-10208] - Add rad certified fault Foundations support
• [OCUA-10232] - Add juniperUni certified fault Foundations support
• [OCUA-10250] - Add symmetricom certified fault Foundations support
• [OCUA-10251] - Add sigma certified fault Foundations support
• [OCUA-10326] - Add optical-metro certified fault Foundations support
• [OCUA-10327] - Add citrix certified fault Foundations support
• [OCUA-10328] - Add symbol certified fault Foundations support
• [OCUA-10388] - Add crossbeamSystems certified fault Foundations support
• [OCUA-10525] - Add stratacom certified fault Foundations support
• [OCUA-10545] - [34843536] - Add UIs for microservices that are "Installed", a list of available "Helmcharts" which can then be deployed, and different "Workloads" states
• [OCUA-10546] - Update APIs to support PHP 8
• [OCUA-10547] - [34844709] - Assure1::SLM subroutines should specify a VertexType value to improve efficiency in CreateVertexTree calls
• [OCUA-10564] - Update the Unified Assurance navigation in Kibana
• [OCUA-10571] - [34857596] - Update Neo4j to 4.4.15
• [OCUA-10573] - [34857673] - Re-implement "Log Checker" functionality
• [OCUA-10579] - [34857773] - Update mavenir certified fault Foundations support
• [OCUA-10589] - Unified Assurance should use high security TLS ciphers
• [OCUA-10591] - Update Device Interface Types to align with IANAifType-MIB
• [OCUA-10595] - Update MySQL EE to 8.0.31
• [OCUA-10596] - Update Java SE to 11.0.18
• [OCUA-10641] - Microservices "Installed" UI should have additional breakdown groups by namespace
• [OCUA-10651] - Update Helm to 3.10.3
• [OCUA-10680] - Update NodeJS to 16.19.0
• [OCUA-10686] - Update Pulsar 3rd party library to address security issues
• [OCUA-10692] - Update CPAN to 2.29 and Perl DBI to 1.643
• [OCUA-10699] - [34955411] - Add endace fault Foundations support
• [OCUA-10729] - Update Perl modules
• [OCUA-10739] - Update Golang modules
• [OCUA-10799] - Update NodeJS and JavaScript dependencies in Vision
• [OCUA-10812] - Update JWT library in Graph Sink microservice
• [OCUA-10813] - Update Kafka to 3.3.1
• [OCUA-10956] - Update Unison to 2.53.0
• [OCUA-10962] - Add PDUv1 conversion support in Trap Collector microservice
• [OCUA-10995] - Update Influx binary to prevent segfaults
• [OCUA-11009] - Metric Standard Thresholding Engine should fully process threshold violations when in a clustered failover type, and only read from the messaging bus for other threshold violation messages
• [OCUA-11019] - Update golang to 1.19.5
• [OCUA-11094] - Update 4th party Java libraries in Vision Gatekeeper

Fixed Issues in 6.0.2.0.0

Bug fixes in this release:

• [OCUA-1875] - Event list tools and in-line event editing should work on events in different shards
• [OCUA-2266] - Update Zone Validation in Cluster Control to allow the same zone in multiple clusters
• [OCUA-2517] - Diagrams with "Autofit" enabled should properly scale vertically
• [OCUA-2672] - Large diagrams should be displayed properly with "Auto Fit" enabled
• [OCUA-2763] - Kibana UI should load in Safari browser
• [OCUA-3537] - Using the topology "Device Overview" and "Network Details" tools should result in a properly displaying dashboard
• [OCUA-3963] - Event list "View SLM" tool should work properly
• [OCUA-4213] - [34863878] - Implement customization of event, performance, and availability state visibility for vertices in Topology Graph dashboard panels
• [OCUA-4284] - Null character should be handled the same way by all Unified Assurance applications
• [OCUA-4286] - Topology Gather Network Inventory should only try to create a neighbor if IPAddress is available
• [OCUA-4287] - Metric Standard Thresholding Engine should handle influx query failures and should still properly clear violations
• [OCUA-10255] - [34614891] - Tools using the Remote functionality should open the external site properly, Remote tools should work when opening in a New or the Same Tab
• [OCUA-10343] - [34529681] - Unified Assurance should use high security TLS ciphers
• [OCUA-10399] - Interfaces should be tucked away into the correct device in Topology Graph panels
• [OCUA-10475] - Rebuild Apache Guacamole to remove security vulnerabilities
• [OCUA-10476] - [34787540] - Update embedded Tomcat server in Apache Guacamole
• [OCUA-10535] - Changing the zoom level using the mouse scroll wheel should be more consistent on Topology Graphs using the Geographical Map layout
• [OCUA-10536] - Topology Graph vertex state calls should consistently be started correctly
• [OCUA-10537] - Remote connections to devices should work properly with Apache Guacamole
• [OCUA-10538] - Post to PollingAssignments API should work properly, and the Devices picker in the Polling Assignments UI should reset to Available when the page is submitted
• [OCUA-10574] - [34857696] - Metric Standard Thresholding Engine should handle instances where there are no configured thresholds to check
• [OCUA-10590] - Changing the time range in the "All Metrics" pop up from a topology graph should work properly
• [OCUA-10599] - [34871460] - Events navigation "readStates" calls and events API reads should load data when an event filter is set to use a different shard
• [OCUA-10602] - [34873005] - Telegraf should properly handle updates and recover gracefully
• [OCUA-10603] - [34873017] - MergeView plugin should be included in codemirror
• [OCUA-10609] - [34878185] - Analytics Wizard should properly access the API
• [OCUA-10623] - Topology Graph dashboard panels using the Geographical Map layout should show vertices properly on the map in full screen mode
• [OCUA-10634] - [34902006] - Elastic and Kibana should only update if the ElasticSearch database is writable
• [OCUA-10636] - [34902029] - Improve Dashboard configuration UI user experience
• [OCUA-10652] - [34918546] - Topology graphs should allow custom vertex icons and edge properties
• [OCUA-10655] - Rules UI should be able to handle JSON formatting in files
• [OCUA-10685] - Calling the API from Perl API library should work
• [OCUA-10695] - Topology graphs using the "Geographic" view should show the tool menu when context-clicking on a vertex
• [OCUA-10698] - Update "All Metrics Overview" and "Network Traffic" views to handle PHP8 empty data access violations when no data is present
• [OCUA-10707] - [34961026] - Event, diagram and topology Tools should work without requiring placeholders
• [OCUA-10709] - Event Lists with Shard 0 should properly sort aggregated data from each shard
• [OCUA-10710] - [34961925] - Graph API should still return success even if no path is found with the provided inputs
• [OCUA-10738] - Microservices UI Readme section should show correct data
• [OCUA-10741] - [34975119] - SNMPv3 support for trap-collector microservice
• [OCUA-10761] - Event list "Traceroute Device" tool should handle when the endpoint is down
• [OCUA-10797] - [34986200] - Layout options on Graph Dashboard panel should function properly
• [OCUA-10808] - [34993033] - Full screen view of the Graph Dashboard should work correctly
• [OCUA-10959] - Upgrades from v5 to v6 should handle redundant servers, non-default installation directories and Metric or Graph only servers
• [OCUA-10978] - Dashboards should support multiple metric "Graph" panels in a single dashboard properly
• [OCUA-10984] - Dashboard layout should be preserved when adding panels from the cog configuration menu
• [OCUA-10997] - Network Details dashboard panel should display IPv4 and IPv6 addresses
• [OCUA-10998] - [35023194] - Improve backend database query execution in dashboard Topology Graph panels
• [OCUA-11000] - [35027527] - Kafka should create a local copy of telegraf-kafka.conf on install
• [OCUA-11057] - [35063784] - Improve backend database query execution in SLM UI's
• [OCUA-11058] - [35063980] - All Metrics Overview panel should show metrics with DisplayInstances
• [OCUA-11063] - Edge API validation should accept EdgeTypeID as a string
• [OCUA-11089] - Default Kibana dashboards should be created
• [OCUA-11114] - clusterctl "create" should store Cluster Name in the RKE config file

6.0.1.0.0 - December 6, 2022

Release 6.0.1.0.0 includes new features and enhancements and bug fixes.

New Features and Enhancements in 6.0.1.0.0

New features and enhancements in this release:

• [OCUA-1851] - Add custom icon library used in Universal Topology
• [OCUA-1885] - Update prerequisites documentation adding NTP as a requirement on all servers
• [OCUA-2043] - Add geographical map layout in Universal Topology
• [OCUA-2514] - Add VMWare vCenter microservice
• [OCUA-3124] - Create additional grafana dashboards for vendor services
• [OCUA-3204] - Add Cisco Meraki microservice
• [OCUA-3235] - Event Generic Agent should be able to query data from ElasticSearch
• [OCUA-3581] - Add rules for FCOM Processor microservice to handle Syslog Collector microservice events
• [OCUA-3582] - Add Syslog Collector microservice
• [OCUA-3607] - Optimize Dashboards loading and simplify event handlings
• [OCUA-3654] - Add Redis microservice, add Device and Topology warmup microservices to add data to Redis
• [OCUA-3657] - Allow customizable source server hostname, port, and schema within Event Canal microservice
• [OCUA-3681] - Add override support for FCOM Processor microservice
• [OCUA-3718] - Add Netapps microservice
• [OCUA-3736] - Add apc certified fault Foundations support
• [OCUA-3744] - Add avaya certified fault Foundations support
• [OCUA-3747] - Add netapp certified fault Foundations support
• [OCUA-3832] - Add panduit certified fault Foundations support
• [OCUA-3896] - Add microsoft certified fault Foundations support
• [OCUA-3897] - Add fireeye certified fault Foundations support
• [OCUA-3902] - Add scc certified fault Foundations support
• [OCUA-3929] - Pulsar Tester microservice port should be configurable
• [OCUA-3930] - Add vertical certified fault Foundations support
• [OCUA-3931] - Add avocent certified fault Foundations support
• [OCUA-3932] - Add grandjunction certified fault Foundations support
• [OCUA-3933] - Add nortel certified fault Foundations support
• [OCUA-3937] - Add mcafee certified fault Foundations support
• [OCUA-3940] - Add mrv certified fault Foundations support
• [OCUA-3941] - Add netIQEnterprise certified fault Foundations support
• [OCUA-3996] - Move ejnmobileipABmib fault Foundations support to a dedicated rules file, remove from ietf rules file
• [OCUA-4003] - Add adtran certified fault Foundations support
• [OCUA-4011] - Replace Universal Topology's display engine
• [OCUA-4019] - Add nokia certified fault Foundations support
• [OCUA-4021] - Add fortinet certified fault Foundations support
• [OCUA-4022] - Add mikrotik certified fault Foundations support
• [OCUA-4023] - Add onstream certified fault Foundations support
• [OCUA-4025] - Add acornTop certified fault Foundations support
• [OCUA-4026] - Add nec certified fault Foundations support
• [OCUA-4030] - Add ironPort certified fault Foundations support
• [OCUA-4031] - Add adcKentrox certified fault Foundations support
• [OCUA-4033] - Add emc certified fault Foundations support
• [OCUA-4038] - Add synchronous certified fault Foundations support
• [OCUA-4052] - Update Puppeteer to 14.4.1
• [OCUA-4058] - Vision should display additional entity information on devices
• [OCUA-4059] - Improve geo-cone visibility when clicking a site in a dashboard in Vision
• [OCUA-4099] - Add privileged port binding and node selection to Trap Collector microservice
• [OCUA-4117] - Add packeteer certified fault Foundations support
• [OCUA-4120] - Update Trap Collector microservice to use SendAsync
• [OCUA-4122] - Add kafka adapter microservice
• [OCUA-4125] - Degree sign in FCOM Summary fields should display properly in the UI if used in foundationrules
• [OCUA-4126] - Add cloudgenix certified fault Foundations support
• [OCUA-4131] - Add marconi certified fault Foundations support
• [OCUA-4186] - Kafka should log to the $A1BASEDIR/logs directory
• [OCUA-4189] - Update Go to 1.19.2
• [OCUA-4215] - Update PHP to 8.1
• [OCUA-4227] - Add clariion certified fault Foundations support
• [OCUA-4235] - Add xedia certified fault Foundations support
• [OCUA-4240] - Apache should use high security TLS ciphers
• [OCUA-4247] - Add tandberg certified fault Foundations support
• [OCUA-4248] - Add wipipe certified fault Foundations support
• [OCUA-4249] - Add ad certified fault Foundations support
• [OCUA-4250] - Add ods certified fault Foundations support
• [OCUA-4251] - Add olicom certified fault Foundations support
• [OCUA-4253] - Add vmware event collector microservice
• [OCUA-4255] - Update CodeMirror to 5.65.5
• [OCUA-4282] - Add apcon certified fault Foundations support
• [OCUA-4283] - Add redCreek certified fault Foundations support
• [OCUA-10024] - Update fault Foundations support for newer revision of CISCO-RTTMON-MIB
• [OCUA-10030] - Add f5 certified fault Foundations support
• [OCUA-10031] - Add opengear certified fault Foundations support
• [OCUA-10036] - Add sni TNS-MIB certified fault Foundations support
• [OCUA-10044] - Add viptela certified fault Foundations support
• [OCUA-10048] - Add panRoot (Palo Alto Networks) certified fault Foundations support
• [OCUA-10082] - Add checkpoint certified fault Foundations support
• [OCUA-10094] - Add gigamonSnmp certified fault Foundations support
• [OCUA-10100] - Add hpe certified fault Foundations support
• [OCUA-10108] - Add arista certified fault Foundations support
• [OCUA-10198] - Add hp certified fault Foundations support
• [OCUA-10202] - Add synernetics certified fault Foundations support
• [OCUA-10203] - Add hitachi certified fault Foundations support
• [OCUA-10209] - Add pdyn certified fault Foundations support
• [OCUA-10214] - Add alteon certified fault Foundations support
• [OCUA-10216] - Add a10 certified fault Foundations support
• [OCUA-10219] - Add aptis certified fault Foundations support
• [OCUA-10220] - Add extreme certified fault Foundations support
• [OCUA-10235] - Add meraki certified fault Foundations support
• [OCUA-10237] - Add shasta certified fault Foundations support
• [OCUA-10238] - Add dec certified fault Foundations support
• [OCUA-10242] - Add baytech certified fault Foundations support
• [OCUA-10243] - Add chipcom certified fault Foundations support
• [OCUA-10247] - Add riverstoneNetworks certified fault Foundations support
• [OCUA-10249] - Add colubris certified fault Foundations support
• [OCUA-10268] - Add nbase certified fault Foundations support
• [OCUA-10270] - Add empire certified fault Foundations support
• [OCUA-10272] - Add infoVista certified fault Foundations support
• [OCUA-10273] - Add concord certified fault Foundations support
• [OCUA-10274] - Add wellfleet certified fault Foundations support
• [OCUA-10277] - Add arrowPoint certified fault Foundations support
• [OCUA-10279] - Add exaltcommunications certified fault Foundations support
• [OCUA-10311] - Add blueCoat certified fault Foundations support
• [OCUA-10391] - Create upgrade path from Assure1 v5 to Unified Assurance v6
• [OCUA-10412] - Update 3rd party dependencies in Supervised Event Correlator microservice
• [OCUA-10417] - [34606430] - CreateSLM functions should specify VertexType and/or EdgeType when calling FindVertexProperty, FindVertexID, FindEdgeID, DeleteEdgeID and DeleteVertexID
• [OCUA-10418] - [34606304] - Metric library function "FindMetricID" should detect and update stored Maximums
• [OCUA-10422] - [34606331] - Add Relocate Metric Data Tool to help migrate Influx data between zones and shards
• [OCUA-10484] - [34606312] - Add calixNetworks certified fault Foundations support
• [OCUA-10498] - Update Kafka to 3.2.3
• [OCUA-10499] - [34606299] - Add multitel certified fault Foundations support

Fixed Issues in 6.0.1.0.0

Bugs fixed in this release:

• [OCUA-827] - Combo boxes should be more consistent throughout the application
• [OCUA-2596] - BrokerControl "ping" should work when directed to any Unified Assurance server that is part of the same installation
• [OCUA-3050] - Tools that open a pop-up window should have a usable scroll-bar when displayed
• [OCUA-3722] - Default service configuration for Event Pipe Aggregator should have the right path to LoadRules
• [OCUA-3823] - Topology graph tools should pass placeholders to the destination link properly
• [OCUA-3829] - Events listed in the "Symptom Events" tab should be expandable to see all of the fields
• [OCUA-4024] - Topology API call to get nodeDetails should use the same availability, event, and metric threshold calls as the "Devices" navigation
• [OCUA-4029] - "All Metrics Overview", "Device Group Availability", and "Top-N Metrics Table" dashboard panel configuration based on a Device Group should work properly
• [OCUA-4036] - Event Canal microservice should use pulsar's SendAsync()
• [OCUA-4088] - Dashboard panel export functionality should work for PDF and HTML formats
• [OCUA-4098] - Setting a metric chart to automatically refresh should work properly
• [OCUA-4127] - User group "Properties" calls to event filter groups "readForTree" should work properly
• [OCUA-4130] - Supervised event "Correlations" pop-up in the event list should only open if a user has the correct permissions
• [OCUA-4135] - In application threshold polling should properly support the "SendAllViolation" option
• [OCUA-4148] - Vision addErrorLog API call should work properly when called
• [OCUA-4151] - Fix issues preventing applications from being run via the UI
• [OCUA-4154] - Vision API documentation should be accessible via ingress proxy
• [OCUA-4155] - Mechanizations UI should work properly
• [OCUA-4160] - Vision API configCheck endpoint should work properly
• [OCUA-4181] - FCOM eval statements should be compatible with JavaScript and Perl
• [OCUA-4182] - Trap Collector microservice should properly format resolved DNS names and not add a trailing period
• [OCUA-4185] - Improve Syslog Collector microservice message processing
• [OCUA-4188] - Update prerequisites documentation changing the filename used for firewalld & include the default port for the Event WebHook Aggregator on collection servers
• [OCUA-4239] - Fix issues with links from Vision views to Unified Assurance UIs
• [OCUA-4285] - All Metrics Overview dashboard panel should use system memory more efficiently
• [OCUA-10025] - Add the SNMP-TLS-TM-MIB to the certified MIB repository
• [OCUA-10415] - [34676724] - TL1 "Gateways" and "Elements" UIs should properly return results when using to Neo4j
• [OCUA-10416] - [34606412] - Fix user authentication using LDAP to properly validate login credentials
• [OCUA-10419] - [34606388] - View changes to columns in the event list should be maintained when data is refreshed
• [OCUA-10420] - [34606287] - A slash in a group name should still then work properly when accessing items in a multi-tree UI
• [OCUA-10421] - [34606318] - Broker control "Jobs" and "Services" UIs should limit the "Primary Service/Job" combo box to the already existing entries on the primary server, add decouple functionality to support other primary/redundant configurations
• [OCUA-10480] - [34624187] - Cloning diagram Metric Widgets should be more efficient
• [OCUA-10481] - [34684023] - Improve the user experience on the "Dashboards" UI when trying to change the panel area
• [OCUA-10482] - [34783016] - Reports should support formats other than PDF
• [OCUA-10483] - [34606288] - Kibana Event Analytics Dashboard reports should generate properly
• [OCUA-10486] - [34606327] - Report Runner should work properly
• [OCUA-10487] - [34606343] - Metric Standard Threshold Engine should be aware of data modifications that have been applied to Influx
• [OCUA-10488] - [34606374] - Metric "Collections" UI should work when a large number of metrics are included in a policy
• [OCUA-10489] - [34606380] - Improve Metric "readStates" API functionality
• [OCUA-10490] - [34606419] - Adhoc Graph Dashboard should not error when filtering by "Edge" and "Property"
• [OCUA-10491] - [34606436] - Metric Poller Discovery should update thresholds more efficiently
• [OCUA-10500] - [34606395] - Add dependency for additional library needed to install MediaWiki in Unified Assurance on Centos 7.9

6.0.0.0.0 - August 1, 2022

Release 6.0.0.0.0 is the initial stable release of Unified Assurance v6. See "What is Unified Assurance" in Unified Assurance Concepts for details.