OmniVista Terra Release Notes 10.6.1 (September 2026)

OmniVista Terra is an on-premise Network Management System that simplifies the monitoring and managing of Stellar Access Points and AOS Switches from an easy-to-read dashboard display. An on-premise version of OmniVista is particularly useful for customers with local installation requirements.

This release of OmniVista Terra is available as a free trial or paid version of the full OmniVista Terra Solution. The trial version extends for 90 days and can be used to monitor up to 20 Access Point and Switch devices combined (additional time and number of devices can be requested). You can then upgrade from the free trial version to a paid licensed version of OmniVista Terra.

You can access OmniVista Terra 10.6.1 (OVT 10.6.1) using any approved browser and device (e.g., workstation, tablet). Access to OmniVista Terra is supported on the following browsers: Chrome 79+ (on Windows and Redhat/SuSE Linux client PCs), and Firefox 62+ (on Windows and Redhat/SuSE Linux client PCs).

These Release Notes detail features and functions, network/device configuration prerequisites, supported devices, and known issues/workarounds in OmniVista Terra 10.6.1. Please read the Release Notes in their entirety as they contain important operational information that may impact successful use of the application.

• New in This Release

• Features and Functions

• Network and Device Prerequisites

• Installing OmniVista Terra

• Launching OmniVista Terra

• REST API Management

• Known Issues/Workarounds

• Issues Fixed

• Additional Documentation

• Technical Support

New in This Release

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

• New Devices Supported

• New Software Supported

• New Features and Functions

• Application Updates/Enhancements

• Early Availability Features

• Features Available Only for Demonstration

New Devices Supported

Stellar Access Points

The following Wi-Fi Gen 7 OmniAccess Stellar Access Points are now supported:

• OAW-AP1541

• OAW-AP1542

• OAW-AP1501S

AOS Switches

The following AOS switch models are now supported:

• OS6370

• Legacy AOS 6 models supported: OS6350, OS6450

See the Supported Devices section below for a list of all devices currently supported in OmniVista Terra 10.6.1.

New Software Supported

• AWOS 5.0.5 - OmniVista Terra 10.6.1 supports AWOS 5.0.5 on all supported Access Points.

• AOS 6.7.2.222.R08 - OmniVista Cirrus 10.6.1 supports AOS 6.7.2.222R08 on the OS6350 and OS6450 switch models.

• AOS 8.11.R01 - OmniVista Cirrus 10.6.1 supports AOS 8.11R1 on all supported AOS Switches, except for the OS6900-T20/T40/X20/X40/X72/Q32 models, which do not support AOS 8.10R1 or later versions.

New Features and Functions

This section details the following General Availability (GA) features introduced in this release. These features completed the full validation cycle and are officially supported in OmniVista Terra 10.6.1.

• OmniVista Advisor Edge

• Authenticated Switch Access Through UPAM

• Authentication Server for External Sources (OV Terra only)

• Certificate Local Authorization Rules

• CLI Scripting Tool

• Disaster Recovery

• Hypervisor Support - Proxmox

• Legacy OmniSwitch (AOS 6) Support With SNMP

• RAP Support for the Branch Office

• Scalability

• SPB for L3VPN and VLANs

• Third-party Device Support

• U-Boot Upgrade

OmniVista Advisor Edge

Advisor Edge extends 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 interface requires interaction with an OmniVista Network Advisor (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 standalone OVNA installation as an Advisor Edge instance in the OmniVista Advisor Edge application.

  • OVNA Edge - An OVNA installation that you can add in Edge mode to your OmniVista Terra appliance (see the OmniVista Terra Admin Center online help). You can declare the OVNA Edge installation as an Advisor Edge instance in the OmniVista Advisor Edge application, in the same way you would declare a standalone OVNA. 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.

Authenticated Switch Access Through UPAM

Authenticated Switch Access allows you to use the UPAM local database for switch authentication. This new feature provides the following functionality:

• Configuring a single database for both network/switch and client authentication to centralize account management, apply consistent privileges, and monitor successful and failed switch login attempts.

• Enable or Disable the UPAM local database for ASA and enable or disable an existing Switch User Account.

• After creating a switch user, create an AAA Server Profile for that user, set UPAM as the server for switch access, and assign the AAA Server Profile to network switches.

Authentication Server for External Sources

The Authentication Server lets you configure an external authentication source—LDAP, Active Directory, or RADIUS—for user login on OmniVista Terra. When enabled, all user logins for the Organization are authenticated against the configured external server instead of the local database. This provides centralized credential management for organizations that already maintain user directories. You must have the Organization Administrator role to configure the Authentication Server. This feature applies only to OmniVista Terra.

Certificate Local Authorization Rules

When an Access Policy uses Local Database as the authentication source and EAP-TLS as the sole authentication method, you can enable Local Authorization to control network access based on the attributes in the client certificate. Local Authorization evaluates administrator-defined rules against the connecting device's certificate and either assigns a specific Access Role Profile or denies access. You can configure access control policies by creating Authorization rules in OmniVista.

CLI Scripting Tool

The CLI Scripting Tool lets you create, manage, and run CLI scripts on network devices across the organization. You can execute scripts immediately or schedule them to run repeatedly. Results consolidate into searchable logs that you can export or email. Organization administrators use the CLI scripting tool to automate device configuration or data collection. This implementation of the CLI Scripting Tool provides the following functionality:

• CLI Scripts - Create and manage all configured CLI scripts in the organization using this tool.

• CLI Executions - Manage and view all executions in the organization.

• Execution Logs - View all execution log entries for all past runs in your organization.

• Execution Logs Settings - Set the general and email scheduler settings for CLI Automation.

Disaster Recovery

OmniVista Terra provides disaster recovery capabilities to protect your network configurations against cluster failures. For example:

• Adding a New VM to an Existing Cluster - You can add a new virtual machine to expand an existing OmniVista Terra cluster or replace a failed node. This operation is certified on:

  • VMware vSphere

  • Microsoft Hyper-V

  • Proxmox VE

When adding a new VM, the cluster automatically rebalances services and data across nodes while maintaining service continuity.

• VM Migration Between Physical Hosts - You can migrate an OmniVista Terra virtual machine from one physical server to another using your hypervisor's native migration capabilities:

  • VMware vMotion

  • Hyper-V Live Migration

  • Proxmox Migration

During migration, the cluster maintains data integrity and minimizes service interruption. After migration completes, services resume automatically without requiring manual database or Kafka recovery.

• Restore Backups - You can restore your system to a previous state using backups that capture organization data, device configurations, site settings, and operational state.

Hypervisor Support - Proxmox

In addition to VMWare and Hyper-V environments, OmniVista Terra compatibility is extended to the Proxmox hypervisor. You can now deploy OmniVista Terra as a Virtual Appliance on Proxmox.

Legacy OmniSwitch (AOS 6) Support With SNMP

OmniVista Terra now provides limited support of Legacy OmniSwitch (AOS 6) devices through the SNMP protocol using standard SNMP MIBs . You can add these devices to the Device Inventory by serial number, assign SNMP credentials through Management User Templates, and control how frequently OmniVista polls them for status updates.

This release of OmniVista Cirrus 10.6.1 supports the following features on switches running AOS 6.x:

RAP Support for the Branch Office

OmniVista Terra now supports Remote Access Points. You can configure an offsite, remote AP as a Remote Access Point (RAP) that can be managed through a local OmniVista Terra installation Management VPN Tunnel. OmniVista Cirrus is used to declare the APs that will be managed remotely and assign the remote APs to a Management VPN Tunnel.

When the AP(s) connect to the network, the OmniVista Cirrus Activation Server is automatically contacted, which downloads the necessary IP and VPN configurations so the AP can be added to your Device List and managed by OmniVista Terra.

Scalability

OmniVista Terra supports up to 8K (6400 AP + 1600 AOS) devices.

Shortest Path Bridging (SPB) for L3VPN and VLAN Support

SPB Services on AOS Switches now support L3VPN and VLAN configuration. This implementation of SPB provides the following functionality:

• VRF Configuration - You can create and manage VRF (Virtual Routing and Forwarding) instances and L3 VPN bindings on SPB-enabled switches. VRF instances segment networks by isolating routing tables, while L3 VPN bindings link VRFs to SPB services for inter-site Layer 3 connectivity. Both IPv4 and IPv6 gateway types are supported.

• L3VPN - The L3 VPN Configuration feature lets you create and manage L3 VPN bindings on SPB-capable switches. These bindings connect VRFs to SPB services for inter-site Layer 3 connectivity. Both IPv4 and IPv6 gateways are supported.

Third-Party Device Support

Third-Party device support allows you to onboard and monitor network devices from any vendor directly within Device Inventory using SNMP. Once added, third-party devices appear alongside native devices in the Device List, on the Topology map, and in Network Analytics—giving you a unified view of your entire network.

Note that Third-party device support does not include callhome-based registration, IP range discovery, software upgrades, initial provisioning templates, or device certification. The following basic functionality is supported:

U-Boot Upgrade

You can now update the U-Boot firmware on your AOS network switches directly from the OmniVista management interface. Use the U-Boot Upgrade screen to upload a U-Boot package, select target switches, and monitor file transfer, installation, and reboot—all in one workflow. This functionality is intended for network administrators managing AOS switch infrastructure to keep U-Boot firmware current across their deployment.

Application Updates/Enhancements

• Countries of Service for OmniVista Terra - You can now select the countries of Singapore and Vietnam to create a 6GHz band RF Profile.

• CoA/DM from External RADIUS Server - The CoA/DM from External RADIUS server feature enables UPAM to act as a proxy between an External RADIUS server and Network Access Servers (NAS) such as Steller Access Points (APs). When enabled, UPAM replaces the NAS-IP-Address attribute in RADIUS packets with a designated UPAM IP address, allowing the External RADIUS server to send Change of Authorization (CoA) and Disconnect Message (DM) requests back through UPAM. UPAM then forwards these requests to the correct NAS device. This functionality is supported only on Stellar APs.

• Event Responder Profile Forward Trap Action - This functionality extends the existing Event Responder capability (which already supports email notifications and auto-acknowledgement) by adding a third response action specifically for switch devices. The Forward Trap action automatically forwards SNMP traps from switch devices to an external monitoring system. When a trap matches a responder rule, the application resends it to a specified destination—an IPv4 address, IPv6 address, or fully qualified domain name (FQDN)—with a configurable port number.

• License Management - The following required licenses are now available for the related OmniVista features and are manageable from the License Management screen:

• • Edge Advisor Subscription and License Management - Controls how many network devices your organization can monitor with Advisor Edge instances. The system enforces device-level entitlement: you assign eligible devices to Advisor Edge instances, and each assigned device consumes one entitlement unit from your Organization's trial or paid capacity.

  • Legacy OmniSwitch (AOS 6x) - OmniVista supports dedicated paid license categories for managing Legacy OmniSwitch (AOS 6x) devices under a CAPEX subscription.

  • Third-Party Devices - OmniVista supports dedicated paid license categories for managing Third-Party devices under a CAPEX subscription.

• Provisioning Configuration - New attributes for provisioning APs:

  • Network Forwarding - You can now provision administrator controls for TCP Segmentation Offload (TSO) and Large Receive Offload (LRO) in the Provisioning Template. TSO and LRO are network forwarding parameters that control how Stellar APs handle TCP packet segmentation and reassembly at the hardware level.

Early Availability Features

The following Early Availability (EA) features are available in OmniVista Terra 10.6.1 and can be configured. However, they have not gone through the complete validation cycle and are therefore not officially supported.

• AP Neighbor Information - A new “State” column and filter added to the Neighbor APs List screen. You can filter the AP state by “Active”, “Static Active”, or “Inactive” (“Offline”, Wireless Aging”, “Static Offline”).

• Standard Power AP Support for 6GHz - Standard power AP models (AP1571, AP1572, AP1561, AP1542) running AWOS 5.0.5 support 6GHz operation.

• Celona Integration (Phase II) - The following functionality further enhances OmniVista Terra integration with the Celona Private Wireless solution:

  • OmniVista Terra implementation of SAML SSO (Single Sign-On) - Provides the required login to access the Celona Orchestrator.

    • If the same SSO user account is configured for both the Celona Orchestrator and OmniVista Terra, users will have seamless access to both systems via single sign-on.

    • Single Sign-On is integrated with Okta and Azure identity Providers to follow the SAML 2.0 protocol authentication.

    • The OmniVista Terra SSO access to Celona Orchestrator authenticates users and provides tokens/assertions (like SAML tokens) to the Celona Orchestrator.

  • Device Catalog View - OmniVista Terra fetches Celona access points on demand from the Celona Orchestrator and displays detailed inventory information in the OmniVista Device Catalog view.

  • Network Topology View - The network topology for Celona access points is shown in the OmniVista Terra topology view. Topology is derived from LLDP information provided by the configured switch.

  • Alerts (Rainbow notifications) - Alerts from the Celona Orchestrator are reported in OmniVista Terra on the Alerts page. If desired, alerts can also be pushed as Rainbow notification bubbles.

• Manual and API RADIUS-CoA in UPAM - The RADIUS Change of Authorization (CoA) updates a connected wireless client’s access policy without disconnecting the client.

  • A “Trigger CoA Client” action is now available to change the Access Role Profile, Policy List, or session timeout for a client in real time.

• Multi-lingual support - OmniVista supports six display languages across the entire platform interface: English, French, Japanese, Chinese, German, and Spanish. This allows you to work in your preferred language with localized labels, menus, dates, numbers, maps, email templates, and captive portal content.

• One Month Add-On Sku - Allows partners and organization administrators to purchase and apply license subscriptions with a one-month duration. This supports short-term co-termination extensions that align subscription end dates with monthly budgeting cycles. OmniVista Terra recognizes and processes 1-month license entries alongside existing yearly durations (1-year, 3-year, 5-year, and 10-year).

• Provisioning Configuration - New attributes for provisioning APs:

  • Client-Context - Information shared between Stellar APs when wireless stations (STAs) roam between access points. This data includes the client's hostname, operating system, device type, and authenticated user identity. Encrypting this exchange prevents client details from being transmitted in plaintext between APs.

    • Encryption - Controls whether client-context data exchanged between APs when roaming is encrypted.

    • Roaming Domain - Defines the roaming group for the AP. Clients can roam only between APs that share the same roaming domain, and only RF neighbors within the same domain are considered for roaming decisions. By default, the Roaming Domain is set to the Organization ID.

• SNMP Traps - Automatic Polling support for missed SNMP traps.

• The Wi-Fi Floorplan and Heatmap - Provides real-time visualization of wireless coverage and client density across your buildings and floors. It uses a modern propagation model that supports 2.4 GHz, 5 GHz, and 6 GHz bands, accounting for wall materials and antenna characteristics to deliver accurate coverage predictions. Network administrators responsible for wireless planning and monitoring can use this guide to set up floor plans, analyze coverage gaps, and track client distribution.

• Web Admin Center UI Evolution - The OVTX Web Admin Center provides system administrators with a centralized interface for configuring platform-wide settings, managing software updates, and troubleshooting remote deployments.

  • Proxy configuration

  • DNS settings

  • Custom domain

  • Certificate management

  • Release file handling

  • Remote support sessions.

System administrators and IT operators managing OmniVista Terra deployments use Admin Center functionality to configure network connectivity, security settings, and software updates.

Features Available Only for Demonstration

The 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.

• PBX Management - The PBX Device Management feature allows administrators to register, monitor, and manage PBX (OmniPCX Enterprise) devices within OmniVista Terra. You can create PBX devices individually or import them in bulk, track their connectivity status, configure OXE parameters, and manage authentication credentials. The following functionality enhances PBX Management integration with OmniVista Terra:

  • • PBX Device Management (Multiple OXE) - Allows you to configure and manage multiple OmniPCX Enterprise (OXE) systems from a single OmniVista Terra interface. This capability is designed for organizations operating more than one OXE system, enabling centralized management through Inventory.

    • Users and SIP Trunk Configuration - Allows you configure phone users, user profiles, programmable keys, hunting and pickup groups, and SIP trunks for a PBX (OmniPCX Enterprise) directly from OmniVista.

    • PBX Admin Logs - The Audit Logs screen records all administrative operations performed on PBX devices managed in OmniVista Terra Inventory. Every time a PBX device is added, updated, deleted, imported, or has its credentials or settings modified, a corresponding log entry is created automatically. This provides organization administrators and viewers with a complete activity history for compliance, troubleshooting, and operational review.

    • PBX Gateway Password Reset - Allows you to reset the gateway password of a PBX device (OXE) directly from the Device List. Resetting the gateway password re-establishes the connection between the PBX and the gateway service. This operation is required when the connectivity between the PBX and the gateway service is not working.

    • Expert Configuration - Provides direct access to advanced, low-level PBX configuration settings within OmniVista Terra, eliminating the need to open a separate PBX management tool.

Network and Device Prerequisites

To ensure the necessary communication between devices (Access Point/Switch) and OmniVista Terra 10.6.1, verify/configure the following prerequisites on your local network:

• Network Prerequisites - Network deployment, bandwidth, proxy, firewall, and NTP server requirements.

• Device Prerequisites - Supported Access Point software and models.

  • If your fully managed Access Points are running AWOS 4.0.8, it is recommended that you upgrade to AWOS 5.0.4 by setting the Desired Software Version first before accessing OmniVista Terra.

  • It is also recommended that you upgrade your OmniSwitch AOS release to 8.10R3 or higher.

• Onboarding Devices Workflow - The basic steps involved to onboard Switches and Access Points for management in OmniVista Terra.

Installing OmniVista Terra

OmniVista Terra is installed from a download file available on the Customer Support website. Refer to the OmniVista Terra Installation online help for information about how to install OmniVista Terra.

When the installation is complete, you will have an initial Network Administrator login and an Organization that was created based on the information you provided during the installation process. The login consists of the email address entered during the installation process and “changeme” as the default password.

OmniVista Terra Release to Release Upgrade

OmniVista Terra supports safe, repeatable upgrades from one software version to another. The upgrade process is designed to:

• Preserve your data, configuration, and settings across versions.

• Minimize service disruption during the upgrade.

• Provide clear visibility into upgrade progress and status.

• Support both single-node and multi-node deployments.

Upgrades are performed by uploading a release file and initiating the installation through the Admin Center web interface. The system handles the upgrade automatically, including infrastructure components, network services, and voice services as applicable.

Launching OmniVista Terra

To launch OmniVista Terra, enter myovterra.myovcloud.com in your browser to access the login screen. When you login to OmniVista Terra for the first time, use the email address for your account (specified during the installation process) and “changeme” as the default password. You are then required to change the password at that time.

Supported Devices

• Click here for a list of supported Stellar Access Points and AOS Switch models, which includes the supported software releases and the license information based on the licensing model (Flexible Pay or CAPEX).

• The following Access Point models are not supported:

  • OAW-AP1101

  • OAW-AP1201L

  • OAW-AP1201H

  • OAW-AP1201HL

  • OAW-AP1201BG

  • OAW-AP1261

REST API Management

You can use REST APIs for scripting or integration with any third-party systems in your management network. The complete API reference can be found at the following link based on your region:

• https://myovterra.myovcloud.com/apidoc/apidoc.html

For more information, see Automation with APIs.

Known Issues/Workarounds

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:

   Bash

   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.

Issues Fixed

PRs Fixed Since 10.5.2 MR1

• UPAM Not Available After Restarting the VM (OVNG-25288)

• Error Occurs When Accessing/Deleting an Organization (OVNG-22976)

• Node or Browser Times Not Synchronized (OVNG-21212)

• Cannot Edit an AP Web/External CP Certificate if Name Contains a Dot (OVNG-23397)

• BYOD Self-Service Login Page Account Password Rules and the Account Password Rules Are Inconsistent (OVNG-22726)

Customer PRs Fixed

• If Message-Authenticator verification fails, the authentication failure reason is displayed incorrectly as "Unprintable Password" instead of the actual cause.(CRNOV-7838 OVNG-23139)

• OVNG Display wrong client roaming history showing client connected to 2 different AP at the same time (CRNOV-7920 OVNG-24700)

• OVNG Web Page delay and latency issue ( CRNOV-8210 CRNOV-8135 CRNOV-8134 CRNOV-8118 CRNOV-7629 OVNG-21185)

• OVNG user should be able to fetch traps from a switch (CRNOV-8128 OVNG-21904)

• Employee Account / Guest Operator: show hidden password is wrong in the Edit page (CRNOV-8099 OVNG-23485)

• Unable to map the ports to the VLAN via OVC 10 (CRNOV-8277 OVNG-25640)

• Issue with SSO for login to OVNG via Entra ( CRNOV-8270 OVNG-26000)

• Improve error message for Access Policy limit (CRNOV-7951 OVNG-24595)

PRs Fixed Since Release 10.5.1

• Device Fails to Get Certificates (OVNG-21279)

• Some Reports Fail When Scheduled to Run at the Same Time (OVNG-21932)

Customer PRs Fixed

• Cannot import company property from CSV or XLSX. (CRNOV-7494 OVNG-21709)

• Unable to search the RF profile details. (CRNOV-7604 OVNG-21903)

• The username with "space" in captive portal guest account is not working if it is created using self-registration strategy. (ALEISSUE-2249)

• Unable to modify SSID parameters after update 10.5.1. (CRNOV-7632 OVNG-22034)

• Issue with License Release when deleting Floor/Building. (CRNOV-7635 OVNG-21962)

• Reset UPAM/Email templates after customization. (CRNOV-7600 OVNG-22821)

• OmniVista should allow user to delete Incremental/Value mapping template that was not used.   (CRNOV-7375 OVNG-22906)

• Notify When Access Role Profiles Are Removed from Switches. (CRNOV-7621 OVNG-21933)

• License utilization is showing incorrectly in OmniVista. (CRNOV-7500 OVNG-21556)

• Unable to SSH the switch from OmniVista with 3 letter usernames. (CRNOV-7495 OVNG-21774)

• There's a typo error in the External Captive Portal Template. (CRNOV-7852 OVNG-22951)

Additional Documentation

The user documentation is contained in the on-line help installed with this product. Click on the Help link (?) in the upper-right corner of a page to access the online help for the page. You can also access the user documentation directly at OmniVista Terra 10.6.1 Documentation.

Technical Support

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

Region Phone Number

North America 1-800-995-2696

Latin America 1-877-919-9526

Europe Union  +800 00200100 (Toll Free) or +1(650)385-2193

Asia Pacific     +65 6240 8484

Internet: Customers with Alcatel-Lucent service agreements may open cases 24 hours a day via Alcatel-Lucent’s support web page at: https://myportal.al-enterprise.com/.

Upon opening a case, customers will receive a case number and may review, update, or escalate support cases on-line. Please specify the severity level of the issue per the definitions below. For fastest resolution, please have telnet or dial-in access, hardware configuration—module type and revision by slot, software revision, and configuration file available for each switch.

Severity 1 - Production network is down resulting in critical impact on business—no workaround available.

Severity 2 - Segment or Ring is down or intermittent loss of connectivity across network.

Severity 3 - Network performance is slow or impaired—no loss of connectivity or data.

Severity 4 - Information or assistance on product feature, functionality, configuration, or installation.