OmniVista Terra 10.6.1 Documentation

OmniVista Terra Maintenance Release Notes 10.6.1 (MR1) (November 2026)

These release notes apply to OmniVista Terra (OVTX) 10.6.1 MR1 build (10.6.1.013.11).

New in This Release

The following sections provide an overview of the features and enhancements introduced with this maintenance release.

Release Packages/Hypervisors

Core Release

10.6.1.013.11_OVTX_Build.7z 

Network Release

10.6.1.013.11_core_OVTX_Build.7z 

VMware ESXi OVA file

10.6.1.013.11.ova

Microsoft Hyper-V .tar file

10.6.1.013.11.tar.gz      

Proxmox .run file

10.6.1.013.11.run

Features Available Only for Demonstration

The OmniVista Terra 10.6.1 MR1 features described in this section are available for demonstration purposes only. These features are not available for general or early release. Please contact your local Alcatel‑Lucent Enterprise sales representative to arrange a demo.

OmniVista Terra AIVA (AI Assistant)

AIVA is an AI-powered network management assistant. Ask questions in plain language and receive instant, formatted answers about your network—including infrastructure summaries, health reports, configuration guidance, and active alerts. AIVA reduces the time you spend navigating between screens by bringing key network insights into a single conversational interface.

  • OmniVista Terra access to AIVA - The AI Assistant does not run inside the OmniVista Terra cluster; instead, the assistant runs on an AIVA server operated by Alcatel-Lucent Enterprise (ALE) on the Internet.

    • Two connections link the customer site to the assistant, both opened from the customer site:

      • Users talk to AIVA when they chat from their browsers.

      • OmniVista Terra opens a secure tunnel to the AIVA server, which reads the OmniVista Terra data it needs to respond

    • No inbound connections on the customer network are required.

  • Beta release for selected customers - AIVA on OmniVista Terra is delivered as a beta with the 10.6.1 maintenance release for selected customers only. General availability is planned with OmniVista Terra 10.6.2.

  • Activation per installation - ALE allows each OmniVista Terra installation individually, identified by its OmniVista Terra ID shown in the OmniVista Admin Center. The customer gives this ID to their ALE contact; an installation that is not allowed receives a refusal message from AIVA.

  • Credits - Each allowed installation receives 10,000 AIVA credits when it is activated. ALE can add credits upon request.

  • Version - An OmniVista Terra build of the 10.6.1 Maintenance Release that includes AIVA, delivered by the official build.

    • The AIVA server is updated by ALE, separate from OmniVista Terra. As a result, the AIVA version may differ from the OmniVista Terra version.

    • The customer does not need to install anything on the AIVA side: upgrading OmniVista Terra updates only the OmniVista Terra AIVA connector.

  • Network Requirements

From

To

Port

Purpose

Users’ browsers

aiva.ovcirrus.com

TCP 443 (HTTPS)

Chat with AIVA

The OmniVista Terra, through its AIVA connector

tunnel-0.aiva.ovcirrus.com and
tunnel-1.aiva.ovcirrus.com

TCP 443 (TLS, mutual authentication)

Secure tunnel through which AIVA reads the OmniVista Terra

    • The three names must resolve in the DNS used by the OmniVista Terra and by the users’ workstations.

    • Both tunnel names are needed: the OmniVista Terra keeps a tunnel to each, for continuity when one AIVA server instance restarts.

    • No inbound port, no VPN and no fixed IP address are required on the customer side.

  • TLS inspection and proxies

    • The tunnel uses mutual TLS. A firewall or proxy that intercepts and decrypts TLS breaks it: AIVA then stays unavailable on that OV Terra, while the rest of OmniVista works normally. Exclude tunnel-0.aiva.ovcirrus.com and tunnel-1.aiva.ovcirrus.com from TLS inspection.

    • The browser traffic to aiva.ovcirrus.com is ordinary HTTPS and can go through the corporate proxy like any other website.

    • An OV Terra that goes out through an HTTP proxy is supported: set the proxy in the network proxy settings of the OV Terra. The AIVA connector uses it automatically and restarts when it changes. The proxy must let the connector open a tunnel, through HTTP CONNECT, to both tunnel names on port 443, without TLS inspection.

  • Troubleshooting

    • Turning AIVA off

      • ALE side: ALE can withdraw an installation from the list of allowed installations. AIVA then refuses that installation, and its credit account is kept.

      • Customer side, in this release: stopping the AIVA connector of the OmniVista Terra closes the tunnel. ALE support gives the exact command. This setting is undone by the next installation or upgrade of the OmniVista Terra; a durable switch is planned for 10.6.2.

    • Quick checks when AIVA does not answer:

What the user sees

Likely cause

What to check

AIVA unavailable on one OmniVista Terra, the rest of OmniVista works

The tunnel cannot open

Outbound TCP 443 to both tunnel names, directly or through the proxy of the OV Terra; TLS inspection on these names; DNS

AIVA answers with a refusal message

Installation not allowed

Ask the ALE contact to add the OmniVista Terra ID

AIVA does not load in the browser

The browser cannot reach aiva.ovcirrus.com

Outbound HTTPS from the workstation, corporate proxy rules

  • Scheduled Reports - AIVA can produce a report on demand, from a question in the chat, and on a schedule. Schedules are managed in the AIVA panel, where the generated reports are also listed. Generate network summary reports to show network status and provide insights for fast root-cause analysis.

    • Creating a schedule - A schedule can be created in two ways: by asking AIVA in plain language in the chat, or from the New schedule form of the Reports and Scheduler tab.
      The form carries:

      • the report type, Network Summary Report or Custom Report;

      • for a custom report, a description of the subject the report must cover;

      • the report language, which is the language the report itself is written in, independently of the language of the OmniVista interface;

      • the recurrence: every day, Monday to Friday, selected days of the week, or selected dates of the month;

      • the time and the time zone.

A summary line under the form states the resulting recurrence and time zone before the schedule is created. For a monthly schedule set on a date that some months do not have, those months are skipped. A schedule set on day 31 produces no report in a month of 30 days.

    • OmniVista application used to schedule a report - A scheduled report runs when nobody is signed in, so it needs credentials of its own. OmniVista creates them automatically.

      • The first time a schedule is created, an OmniVista application named AIVA Artifact Scheduler Report is created automatically for the account, with the description “Created automatically by AIVA to run scheduled reports. Deleting it stops your scheduled reports.”

        • Nothing has to be created or configured by hand. The application appears in the organization’s applications on its own.

        • This application belongs to AIVA. It should not be renamed, reused for anything else, or deleted.

        • Deleting this application stops the scheduled reports. Existing schedules remain listed but their runs fail, and the failure is shown in the Reports and Scheduler tab. Reports produced before the application was deleted are retained.

    • Reading the results - The Reports and Scheduler tab lists each report with its type, title, timestamp, status, and whether it came from a schedule or from a question in the chat.

      • Opening an entry displays the stored report; it can be exported to PDF.

      • A failed run is listed with its error message.

      • Reports produced on demand also stay in the conversation that produced them, and can be reopened from there later.

  • Configuration Agent - AIVA can apply network configuration from a request written or spoken in plain language. Administrators can now talk to the AI Virtual Assistant for day-to-day operational needs and insights.

    • How a configuration request is handled

        1. The user describes what they want in plain language, for example “create an SSID called Guest-WiFi on the Paris site”.

        2. AIVA identifies the matching configuration action and reads what that action requires.

        3. AIVA asks only for the mandatory values that have no default and cannot be deduced safely. This is the behaviour of the OmniVista interface itself: when a form is filled in, only the mandatory fields are asked for and the rest takes the standard default values. AIVA applies the same defaults.

        4. AIVA stops and displays an approval card listing the action, the object, the organization and every parameter retained, including the values it filled in itself, which are marked as defaults.

        5. The user approves, edits the parameters, or cancels. Nothing is applied before approval.

Consider the following when using the Configuration Agent:

        • The stop before execution is enforced by the product, not by the assistant’s judgement. There is no path by which a configuration is applied without the approval card.

        • AIVA acts only on the organization of the current conversation. Naming another organization in the request does not make it act there.

        • When several configurations depend on each other, AIVA proposes them one after the other, each with its own approval card, offering to create the missing one or to use an existing one.

    • What AIVA can configure - The areas below are covered. Within an area, not every attribute of every object is necessarily available: AIVA states what it cannot set rather than inventing a value.

      • Network and LAN - VLANs and their assignment to switch ports, Layer 2 profiles and Spanning Tree settings, Layer 3 IP interfaces, L3 VPN and VRF, SPB services, ARP configuration groups, LAN provisioning templates and provisioning configurations, value mappings, LAN global configuration, configuration backups and restore, switch management user templates.

      • Wireless - SSIDs and SSID schedules, AP groups and the devices they contain, RF profiles, captive portal templates, guest access and BYOD strategies, registration profiles, WIPS and mesh settings.

      • Access control and identity (UPAM) - Access policies, access records, employee, guest, company property and IMSI/IMEI accounts, guest operators, LDAP and Active Directory role mappings, external RADIUS, LDAP and Active Directory servers, UPAM certificates and certificate authorities, NAS clients, AAA server profiles, access authentication profiles, access role profiles and access classifications.

      • Policies - Unified policies and policy lists, location policies, period policies, redirect allowed profiles, MAC groups, IP groups, service groups and service ports.

      • Devices and inventory - Devices, device labels, remote access points, device placement in a site, building, floor and AP group, device diagnostics, firmware upgrade schedules.

      • Sites and topology - Organizations, creation and update, sites, buildings, floors, walls and zones.

      • Monitoring and reporting - Event configurations, webhooks and notifications, alerts and alert templates, reports, site thresholds, client blocklist, IoT categories and certificates, IoT dashboards, application visibility signature profiles, custom anomalies.

      • Connectivity - Tunnel profiles, data and management VPN settings, syslog over TLS, edge instances.

      • Users - User invitations at organization level.

    • What AIVA does not configure - The actions below are deliberately outside what AIVA can reach. The refusal is enforced by the product. Configure the following actions through the OmniVista Terra interface.

      • Subscriptions and billing - Requesting, upgrading, approving, rejecting or renewing a subscription, importing license entitlements, changing license consumption.

      • Licenses - Binding, unbinding, swapping or reassigning licenses, importing licenses, deleting expired licenses, automatic license assignment.

      • Deleting an organization - Deleting and moving an organization to a managed service provider. Creating and updating an organization are available.

      • Managed service provider administration - Everything acting above the organization level.

      • Identity and access management - Removing a user’s role, accepting or cancelling an invitation, forcing sessions to log out, changing the password policy or two-factor settings.

      • Sign-in and account flows - Sign-up, password reset, account lock and unlock, second factor, email validation, token refresh.

      • SSO and the authentication servers used to sign in to OmniVista - These are different from the RADIUS, LDAP and Active Directory servers used by UPAM for network authentication, which AIVA can configure.

      • Direct access to database collections.

      • Global purge and personal data operations.

      • Agent packages and fleet rollout.

      • AIVA’s own conversation data.

      • Platform-wide settings.

      • Switch bootloader upgrades.

      • Running a CLI script on a device, and opening an SSH session to a device.

      • Exporting certificates and credentials.

    • What is not in this release - AIVA applies one configuration at a time, with its immediate dependencies resolved and proposed in turn. It does not take a complete use case and build the whole chain from a single request: asking for a guest wireless network does not produce the captive portal template, the guest access strategy, the access policy and the SSID in one go. Each is proposed and approved in turn.

      • Orchestrating a complete use case from one request is planned for a later release.

  • Voice Agent - Administrators can now talk to the AI Virtual Assistant for day-to-day operational needs and insights. The following AI Assistant voice settings are configured on the AIVA Settings screen (Organization > Settings > AIVA):

    • Voice interaction mode: how the assistant listens during a voice session - Three modes:

      • Push to talk (the user holds the microphone button to speak).

      • Hands free, interruption allowed (the assistant listens continuously and the user can interrupt an answer).

      • Hands free, no interruption (the assistant listens continuously and finishes its answer before listening again).

    • Output voice - The voice used for spoken answers.

    • Assistant tone - The conversation style of the assistant.

    • Speech speed - The speed of the spoken answers.

  • OmniVista Network Advisor (OVNA) - AIVA using OVNA to show the remediation and anomalies detected in the network.

Installing OmniVista Terra

A fresh installation of the OmniVista Terra 10.6.1 MR1 follows the same procedure as a fresh installation of the 10.6.1 GA release. Refer to the Deployment Prerequisites online help for information about performing a fresh installation of OmniVista Terra.

Upgrading from 10.6.1 GA to 10.6.1 MR1

The Upgrade to a New Release online help describes the process for upgrading an existing OmniVista Terra GA installation. Refer to this procedure to upgrade from OmniVista Terra 10.6.1 GA to OmniVista Terra 10.6.1 MR1.

OmniVista Terra will be unavailable for approximately 15 to 20 minutes during the upgrade process.

Post-Upgrade Acceptance Checks

The Network Release installation should complete successfully with no failed tasks. After the Core Release and Network Release installations are complete, perform the following validation checks in the OmniVista Terra Admin Center.

Platform Status

Validation Item

Expected Result

OVTX version

10.6.1 MR1 is displayed

Installation tasks

No task is running or failed

Infrastructure Health

On the Monitoring page, verify that:

  • Nodes are healthy.

  • Pods are healthy.

  • Services are healthy.

Known Issues/Workarounds

Upgrade Process Takes Too Much Time
Summary: The upgrade from OmniVista Terra 10.6.1 GA to OmniVista Terra 10.6.1 MR1 may take too much time (more than an hour). This is a known issue based on some temporary failure that is specific to this upgrade process; production or OmniVista are not impacted.
Workaround: At step "[ovtx : Restart Kafka brokers one by one (OnDelete strategy)]" manually restart kafka pods from the Dashboard page in Web Admin. First recreate kafka-0, then kafka-1 and finally kafka-2.

Delay During Core Package Upgrade (OVNG-28220)
Summary: There is a 5 to 10 minute delay during a core package upgrade where you cannot access the OmniVista Admin Center and are redirected to the Account Registration screen.
Workaround: There is no workaround at this time.

Device State Changed to “OFF” When Node is Removed (OVNG-28156)
Summary: If a node is removed from the cluster, some pods may appear unhealthy (Terminating or Restarting) in the Admin Center UI. If devices and OmniVista are functioning normally, please ignore the unhealthy status of those pods.
Workaround: We are reviewing the deletion workflow to improve the experience.

Grafana Logs Visualizer May Load Slowly After Login (OVNG-26056)
Summary: The Grafana Logs Visualizer, accessed from the Web Admin Center, may take longer to load after login. This occurs because OmniVista Terra platform components consume more cluster resources in this release, leaving fewer resources available for Grafana.
Workaround: A lightweight monitoring solution is under evaluation to improve the user experience in a future release.

Access Point Is Stuck In “Connected to OV” State (OVNG-25565)
Summary: When “From LLDP” is enabled, the AP sends the switch location in the registration flow. However, the switch location value may contain invalid or special characters, so the AP remains in the “Connected to OV” state.
Workaround: When configuring the switch location information for LLDP/LLDP-MED on OmniSwitch devices, use standard alphanumeric (printable) characters only. Avoid using non-printable, control, or otherwise unsupported characters in the switch location configuration. Please remove any non-standard or invalid characters.

RAP Device Does Not Get New Management VPN Settings After Reset (OVNG-26129)
Summary: When a change is made to the Management VPN, a Remote Access Point (RAP) managed by OV Terra does not get the updated settings after the RAP device is reset. The RAP device keeps the OV Terra certificate and can NOT call OV Cirrus to get new Management VPN Settings.
Workaround: There are two possible workarounds for this issue based on whether the network configuration is working:

  1. The current network configuration is still working
    When you switch to the new Management VPN settings, the existing on-site network configuration remains functional. The old and new Management VPN settings can operate in parallel.

    In this case, RAP devices can still connect to the OVTx Activation Server and send requests. You can work around the issue by assigning the troubleshooting command resetDeviceToFactoryDefault to the RAP devices.

    1. Navigate to Diagnostics > Device Support > Custom Commands.

    2. Click on Assign Command, select the RAP device from the Devices list (Step 1), then click Next.

    3. Select resetDeviceToFactoryDefault from the command list (Step 2) and click Next.

    4. Set the Command Args “clearCertificateAndPrivateKey” value to Yes (Step 3) and click Next.

    5. Review the Assign Command Info and click Assign Command.

  2. The current network configuration is not working
    If the old Management VPN settings, including the mapping to the OVTx Activation Server, are no longer working and the user needs to switch to the new Management VPN settings, RAP devices cannot send the Call Home request to the OVTx Activation Server to retrieve the troubleshooting commands.

    In this case, you need to apply the workaround by running the following command:

    rm -rf /tmp/cloudurl /var/cluster_config/acv_client.conf /.ocloud/dhcp_ocloud_info /etc/config/ngcloudurl /tmp/dhcp_ocloud_info && echo 'Activation_Server_URL:activation.dev.myovcloud.com' > /tmp/dhcp_ocloud_info && cd /.ocloud && rm -f callhome_hash.json certificateFile.cert csr.csr privateKey.key publicKey.key && callhome.sh
    

Limited User Role Configured in an External DB is Not Supported (OVNG-24984)
Summary: If you configure limits for a user role in an External RADIUS server, the limited role mapping is not supported in the OmniVista UI. Users mapped to the limited role defined in the External RADIUS server cannot log into OmniVista.
Workaround: There is no workaround at this time.

Rainbow Bubbles Imported Into Advisor Edge Do Not Receive Anomalies (OVNG-28237)
Summary: When you import Rainbow Bubbles using the Advisor Edge application (Configure > Advisor Edge > Rainbow Bubbles), the imported bubbles do not receive any Anomaly notifications.
Workaround: There is no workaround at this time.

Operational Dashboard May Take A While to Load (OVNG-23020)
Summary: In a small OmniVista Terra installation, OmniVista may need approximately five minutes to initialize all the Microservice databases to load the dashboard.
Workaround: Please wait for five minutes after create/activate the subscription before accessing the organization.

Mesh Topology and Topology Do Not Show Links for AP Bridge Connections (OVNG-22977)
Summary: When you configure an AP as an AP Bridge (either Root or non-Root role), the links for AP Bridge connections are not displayed in the Mesh Topology or Topology applications.
Workaround: There is no workaround at this time.

Cannot Save Customized Captive Portal Template with Video Content (OVNG-20902)
Summary: When using the Firefox browser, Captive Portal template customization with a new video layout is not saved.
Workaround: Use the Chrome browser instead of Firefox.

Backup of switches running AOS 8.10R4 or later partially completes when you include security files (OVNG-22975)
Summary: Security files have root-level permissions. Due to enhanced security introduced in AOS 8.10R4 and later, OmniVista can no longer back up these files.
Workaround: Exclude security files from the backup.

Some Services Are Pending When Adding a New Node With the Same IP Address (OVNG-23226)
Summary: Some services show as pending in the Web Admin Center Dashboard when adding a new node with the same IP address as a previously removed node in a 3-node cluster.
Workaround: There is no known workaround at this time.

When Applying Two Policies With the Same Condition Group Simultaneously, the Latest Data on the AP Is Not Updated (OVNG-19125)
Summary: OmniVista Cirrus pushes the correct data to the AP when two Unified Policies with the same Condition Group are applied simultaneously. However, the latest policy data is not updated on the AP.
Workaround: Restore policy data synchronization to ensure APs will successfully receive and apply the most current policy configurations. This requires completing the following steps to re-establish policy associations:

  1. Navigate to Policy Management
    Access the Unified Policies screen (Configure > Auth & Automation > Access Profiles > Policy).
    Locate the two affected policies that share the same Condition Group.

  2. Unlink policies from the AP group
    Access the assignment settings for each affected policy.
    Remove the AP group association from both policies.
    Confirm the AP group is no longer listed under either policy's applied groups.

  3. Re-apply policies sequentially
    Return to the first policy's assignment page.
    Re-add the AP group to this policy's applied groups.
    Wait for the assignment to complete and propagate.
    Repeat the process for the second policy.

  4. Validation through Unified Policies Screen
    Verify both policies now show the AP group in their applied assignments.
    Confirm the shared condition group is properly configured in both policies.
    Monitor AP status to ensure the latest policy data has been synchronized.

Issued Fixed

PRs Fixed in 10.6.1 MR1

  • OVNG-27881: mqtt-source-ovng-wlan-ap-incoming-messages silently drops ~422k AP messages (non-UTF-8 switch_location from LLDP) - no task failure, no alert, no DLQ

  • OVNG-28219: ovng-edge-service killed by "fatal error: concurrent map writes" — unsynchronised writers map in kafka.Producer.getOrCreateWriter

  • OVNG-29434: [OVTx][Installation] Default Time Zone “Asia/Saigon” rejected: “This value is not allowed”

  • OVNG-27925: ovng-wlan-analytics logs at DEBUG despite LOG_LEVEL=INFO — 168 GB of logs in 4 days, OpenSearch disk at 92%

  • OVNG-27999: License Provider change OAuth to OAuth 2

  • OVNG-28189: Monitoring pages return 500 (42P01) for ~25 s after org creation — OVNG-22976 fix is OVTx/Dashboard-scoped and does not cover SwitchAnalytics/WlanAnalytics

  • OVNG-28172: An organization with no subscription is unreachable for everyone: the activation-request modal is no longer opened by any screen, so a self-signup org without MSP is permanently locked out (even for a super admin)

  • OVNG-28225: L3VPN poll incorrectly due to L3VPN poll before Service

  • OVNG-28270: [SPB] Manual Access Port should allow to select in List Port when configuration SAP

  • OVNG-27807: [Edge advisor]for no co-termination edge license is not getting consumed after instance is assigned

  • OVNG-27434: [OVTx][Recovery]Add Backup Deletion Support to Prevent Disk Space Exhaustion

  • OVNG-28176: Some switches do NOT display a list of ports

  • OVNG-28370: [UPAM] All SMS sent by UPAM fail with NoSuchMethodError - samp-service image ships httpclient 4.5.2 while message-center needs 4.5.10 (twilio 8.24.0)

  • OVNG-28399: discovery-manager-entries/warning takes 0.12 s per Discovery Manager entry (PBKDF2 decrypt per row), called 2x on org entry + on every progress-popup poll

  • OVNG-28286: Flyway V1.000.0.26 reports success but converts only 4 of 13 columns: responder.responder_id stays varchar, /networkevents/responder returns 500 permanently

  • OVNG-29080: [10.6.1 MR] Update OV Cirrus supported equipment List

  • OVNG-28088: Debug raise log left active in the analytics provisioning trigger floods the PostgreSQL server log on every cluster and every org schema (up to 74 GB/day on sqa-sca, ~70% of prod-eu log bytes)

  • OVNG-27927: Quick UI improvements

  • OVNG-28041: mongo-source connectors: heartbeat records discarded by the dropNullRecords SMT, so the change stream resume token is never refreshed -> silent data loss (errors.tolerance=all) or permanent task failure (errors.tolerance=none)

Customer PRs Fixed

  • CRNOV-8659 Unable to disable AIVA after OVNA configuration

  • CRNOV-8549 SMS sent by UPAM fail with NoSuchMethodError

  • CRNOV-8556 OVTX Installation failure with DNS Server configuration