OmniVista Network Advisor Production Release Notes 2.0

The Release Notes detail Prerequisites, Upgrade Steps, New Features, and Known Issues/Workarounds for OmniVista Network Advisor. Please read the Release Notes in their entirety as they contain important operational information that may impact successful use of the application.

• Technical Support

• Related Documentation

• Prerequisites

• Upgrade Steps from OmniVista Network Advisor 1.x

• New Features (Release 2.0.X)

• Known Issues and Workarounds

• Fixed Issues

Technical Support

ALE technical support is committed to resolving our customer’s technical issues in a timely manner. Customers with inquiries should contact us at:

Related Documentation

• OmniVista Network Advisor Service Description:
  https://myportal.al-enterprise.com 

•   Rainbow documentation:
  https://www.openrainbow.com/app/en

• Microsoft Teams documentation:
  Appendix E - Microsoft Teams Bot Setup Guide

Prerequisites

The following prerequisites must be verified/configured before using OmniVista Network Advisor:

• System Requirements

• Devices Prerequisites

• Rainbow Prerequisites

• Microsoft Teams Prerequisites

• OmniVista Enterprise and Cirrus Prerequisites

System Requirements

The following are the suggested minimum requirements for installing and running the OmniVista Network Advisor application.

• Internet access is mandatory.

• Processor: Quad-core. The CPU must support Advanced Vector Extensions (AVX).

• RAM: 8 GB

• HDD: Up to 200 devices, 50 GB (To allow for storage of syslog messages)

  • For 1,000 devices, 120GB storage is recommended

  • For 2,000 devices, 210GB storage is recommended

• Linux OS: Ubuntu 22.04 Server Edition or Debian 11 or 12
  (OVNA is not compatible with Ubuntu 26)

  • For installation on RHEL, ensure that firewalld is turned off.

• The minimum requirements for OmniVista Network Advisor support on OmniVista are:

  • OmniVista Enterprise 4.8R2 and above

  • OmniVista Cirrus 4.8.2 and above

  • OmniVista Terra 10.6.1 and above

  • OmniVista Cirrus 10.6.1 and above

• When using Microsoft Teams, ensure that smba.trafficmanager is turned on.

• Ports:

  • TCP 80/443 (HTTP/S for WebUI),

  • UDP, TCP 10514 (Syslog),

  • TCP with secure Port TLS 6514 (Syslog over TLS)

  • TCP 22 (SSH/SFTP Application to devices or access to Application),

  • TCP 443 (Setup Installation and Cloud Services)

  • Port default of Microsoft Teams

• By default, Kubernetes uses the following IPv4 address ranges for its various components:

  • Pods: 10.42.0.0/16

  • Services: 10.43.0.0/16

  • CoreDNS: 10.43.0.10

Devices Prerequisites

Applies to ALE OmniSwitch LAN switches and OmniAccess Stellar WLAN APs.

The equipment must be running the following minimum software versions:

• OS6xxx and 9xxx models, AOS 8.7.R2 or higher.

• OS2xxx, AOS 5.2.R1 or higher.

• Stellar APs, AWOS 4.0.3 MR-3 or higher.

 Supported equipment listed below and available here.

Rainbow Prerequisites

OmniVista Network Advisor users must have an active Rainbow account. A dedicated service account is required for the setup of OmniVista Network Advisor. If you don’t yet have an account navigate to the below URL to sign up.
https://web.openrainbow.com

Microsoft Teams Prerequisites

• You should have a Microsoft company account (with administrator rights on a company.)

• Microsoft license for a product which comes with at least Microsoft Entra ID.

• A public URL with a defined port exposed on the Internet must be accessible to allow MS Teams to reach your Network Advisor application.

OmniVista Enterprise, Cirrus, and Terra Prerequisites

• OmniVista synchronization requires OmniVista Enterprise 4.8.R2 and above.

• OmniVista synchronization requires OmniVista Cirrus 4.8.2 and above.

• OmniVista synchronization requires OmniVista Terra 10.6.1 and above.

• OmniVista synchronization requires OmniVista Cirrus 10.6.1 and above.

NTP Server Requirements

Accurate system time is required for certificate validation (start date and validity period) and for all encryption-related functions. All devices must have access to at least one NTP server, either local or external. For virtual machines, the system clock is initially synchronized with the hypervisor clock by default. Therefore, it is critical to ensure that:

• The hypervisor itself is correctly synchronized with a reliable NTP source.

• The virtual machine is allowed to synchronize its time (via hypervisor tools and/or an NTP service inside the VM).

Upgrade Steps from OmniVista Network Advisor 1.X

• Download the latest package file from MyPortal and copy it to your linux host.

• Use the following command to upgrade OmniVista Network Advisor

-> sudo ale-ovna update

• The command will first check if a .deb has to be updated.

  • `if yes, the new .Deb is downloaded after which command will exit saying that a new .Deb has been installed and invite the user to relaunch "ale-ovna update" to update the software using the last ale-ovna.

  • if no , software update is performed normally.

For an installation example, see Appendix A—Step-by-Step Installation Example.

New Features (Release 2.0.X)

OVNA Interaction with OmniVista Advisor Edge Application

The OmniVista Advisor Edge application extends OmniVista Cirrus and OmniVista Terra functionality with advanced anomaly detection and alert routing capabilities. This feature allows Organization Administrators to declare Advisor Edge instances, associate Organization devices for monitoring, manage anomalies, and route alerts to Rainbow communication bubbles. Advisor Edge is available for users with an active OmniVista subscription or trial license on non-Lite plans.

• Using the OmniVista Advisor Edge management interface requires interaction with an OVNA installation. The following options are available to accommodate this requirement:

  • Standalone OVNA - During the standalone installation process you are asked if you want to use OmniVista Cirrus or Terra for management, select “Yes”. This allows you to declare the OVNA standalone installation as an Advisor Edge instance in the OmniVista organization. See the OmniVista Advisor Edge online help for more information.

  • OVNA Edge - An OmniVista Network Advisor appliance installed in Edge mode via the OmniVista Terra Admin Center. You can declare OVNA Edge as an Advisor Edge instance in the OmniVista organization. See the OmniVista Advisor Edge and Configuring OVNA Edge sections in the OmniVista Terra online help for more information.

    • Note that if you select this option, the following prerequisites apply:

      • OVNA Edge is supported only on 1 VM.

      • If OVNA Edge is installed on 1 VM, installing Network Services on that same VM is not supported.

New Commands

The following new commands now available with 1.x Mongo update from 6 to 8:

• Run a full installation health and connectivity check: sudo ale-ovna sanitycheck

• Collect diagnostic logs and system information into an archive: sudo ale-ovna collect

Known Issues and Workarounds

• Installing OVNA behind a proxy is a known issue in Edge mode with OmniVista Cirrus.

• Internet access is mandatory for the installation setup and for proper functioning.

• After any OmniSwitch reboot, if you haven't run write memory, run these two commands so OmniVista Network Advisor continues to monitor the device:

-> swlog output socket <IP address> <port>
-> appmgr restart ams cron-app

The above command is valid for OS6xxx and OS9xxx only.

• Network Loop anomaly is only supported on OmniSwitch models OS6860(E), OS6860N, OS6900.

• OS6860 and OS6860N Core dumps are generated until the ‘pmd’ directory is full. Fixed in AOS 8.9R01 GA.

·        AOS switches: When setting the TLS method in syslog, the correct outgoing interface is not correctly set with the command ip service source-ip <interface-2> all if <interface-1> is changed by <interface-2>. Fix is planned with 8.9R04 GA.

• Stellar APs running in Express mode support remote syslog server port 514 only.

• Incorrect NTP settings may prevent a device from being properly monitored by OmniVista Network Advisor.

• Some anomalies do not work if the switch is configured in aaa JITC or aaa enhanced mode.

• Activation of DEBUG log on the OmniSwitch can result in a high impact on OmniVista Network Advisor storage.

• Backup files must be deleted manually by OmniVista Network Advisor operator on the host instance.

Fixed Issues

Issues Fixed in Release 2.0.X

• [OVNG-27814] AP SSH authentication

• [OVNG-27655] Rainbow account login fails after proxy is configured on air-gapped OVTX

• [OVNG-27636] Frontend fix

• [OVNG-27509] Frontend fix

• [OVNG-27348] Frontend fix

• [OVNG-27186] Port flapping adaptive card

• [OVNG-27188] %S Cards handling

• [OVNG-27157] Pass password into su mode

• [OVNG-27104] IoT profiling anomaly spamming — suppress internal SSH remote exec failure

• [OVNG-26338] Preserve UUID from cloud for custom anomalies to ensure deduplication

• [OVNG-26117] Frontend fix

• [OVNG-24178] Standalone import — check DB result, preserve UUID, normalize booleans

• [OVNG-22926] Check for anomalies update

• [OVNA-1262] Watchdog rollback fix

• [OVNA-1252] Device SSH credentials resolution on refresh all command

• [OVNA-1248] Run na-ovng-notifier container as non-root user (UID 1000)

• [OVNA-1240] Update console log messages

• [OVNA-1201] Send notifications to Rainbow in case of update

• [CRONA-169] DDoS attack — debug activation not required

Security

• CVE fixes across all Docker base images (Node.js 24.7, nginx, Go, Alpine)

• [OVNG-26552] Trivy vulnerability analysis and remediation

New Features (Edge)

• [OVNG-27184] Advisor Edge — Edge Advisor convergence with OmniVista Cirrus

• [OVNG-27075/27082] Edge Advisor UI integration

• [OVNG-27062] Edge Advisor frontend support

• [OVNG-26457/26386/26463/26614] Edge Advisor licensing and device management

• [OVNG-25244] Download and export custom anomalies in Edge mode

• [OVNG-26027] Remove login column from devices association

Deprecated Anomalies / Anomalies Changes

The following table lists deprecated anomalies or changes by release.