Alcatel-Lucent OmniVista Cirrus

Network Management as a Service

OmniVista Cirrus Production Notes 4.5.2

OmniVista Cirrus Production Notes 4.5.2

OmniVista® Cirrus is a cloud-based Network Management System (NMS). This cloud-based approach eliminates the need for purchasing and maintaining a physical server and installing the NMS on premise, since everything resides in the cloud. Network Operators can access OmniVista Cirrus from anywhere, using any approved browser and device (e.g., workstation, tablet).

Access to OmniVista Cirrus is supported on the following browsers: Chrome 68+ (on Windows and Redhat/SuSE Linux client PCs), and Firefox 62+ (on Windows and Redhat/SuSE Linux client PCs).

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

New Features and Functions

An overview of new features and functions is provided below.


OmniVista Cirrus now supports the following devices:

  • AOS Devices
    • OS6860N - OS6860N-U28, OS6860N-P48Z, and OS6860N-P48M
    • OS6900 - OS6900T48 and OS6900X48


OmniVista Cirrus now supports the following OS Software Versions:

  • AWOS and higher
  • AOS 6.7.2.R08
  • AOS 8.7R1


New Applications

The following section details new applications introduced in this release.

  • Scheduled Upgrades
    • The new Scheduled Upgrades feature (Network - Inventory - Scheduled Upgrades) enables you to schedule automatic upgrades to specific network devices during specific time windows (e.g., non-business hours) to ensure minimal network disruption. Scheduled upgrades can also be configured on the Device Catalog Screen (Inventory - Device Catalog) by selecting a device(s) in the Device Catalog and clicking on the "Set Software Version" button to bring up the Schedule Software Upgrade Wizard. A device must be managed and the Running Configuration must be saved for an upgrade to occur.
  • It is recommended that you schedule upgrades on devices so that they do not adversely affect network performance. For example, stagger upgrades of different devices in different time windows during non-busy hours.

  • Responder mDNS
    • You can now configure mDNS using the Responder Model. Responder mDNS is configured on Responder Switches which communicate with Edge Switches/APs to which clients connect. In this mode, the Responder Device acts as a core switch. Server Rules are created on the Responder Device that contain Server Policies and Client Policies. The Service Rules define the criteria by which the Responder Device decides which services can be shared with which client requests.
  • The following devices can be configured as Responder Devices: OS6860, OS6865, OS6900, and higher. The following switches and APs can be configured as Edge Devices: OS6465, OS6560, OS6860, OS6865, and OS6900; and APs running and higher (except for OAW-AP1101).

    Note that OmniVista does not support importing existing mDNS configurations.

  • External Apps
    • The new External Apps feature in the (Security - External Apps) is used to create an API security key that is used by external devices/applications to access the OmniVista Server. For example, the Asset Tracking Engine will use this key to access OmniVista Cirrus.

Application Updates/Enhancements

The following section details updates and enhancements to existing OmniVista Cirrus applications.


  • New Stellar AP Uptime/Downtime Report
    • The new Analytics AP Uptime/Downtime Report displays detailed information about the Uptime/Downtime of APs, and the Uptime/Downtime of the link between APs and OmniVista.
  • Port Statistics Displayed in Kbps
    • Port Tx/Rx Kpbs options are now available when configuring Analytics Statistics Collection Profiles.

Application Visibility

  • Application Visibility Support on AP132x and AP136x
    • Application Visibility is now supported on Stellar AP132x and AP136x models (requires minimum Signature Kit version 3.6.11).

AP Registration

  • Out-of-the-Box Mesh Configuration
    • Out-of-the- box Mesh is a feature that helps you quickly set up a Mesh Network without configuring the out-of-box APs. The out-of-box APs will establish a Mesh network with hardcoded settings. You only need to specify the Mesh root, then other APs will establish a Mesh configuration automatically. Select an AP in the Access Points List and select Edit Mesh Configuration to enable Mesh and configure Mesh root. Note that to enable Out-of-box Mesh, the factory AP should be powered up by adapter or PoE injector without connecting to wired LAN.
  • Edit Bridge AP Name
    • You can now edit a Bridge AP Name. Go to the Bridge AP Tab, select an AP and select the Edit Basic Info edit option.
  • AP Uptime Displayed in Detailed View
    • AP Uptime is now displayed in the Detailed View of an AP. Select an AP to bring up the Detailed View. AP Uptime information is in the General section.
  • IoT/Location Server KonSP BLE Beacon Is Now Supported
    • The KonSP BLE Beacon format is now supported. This format must be used for location data when tags are not in motion.
  • APs Support Multiple VLANs for Local Breakout
    • APs can now support Local Breakout for multiple APs. Local Breakout is configured as part of a tunnel configuration in the Unified Profile application and the SSIDs application.

Authentication Servers

  • Increased Password Length for LDAP Servers
    • You can now create a password of up to 128 characters when configuring an LDAP Server (Security - Authentication Servers - LDAP Server).

CLI Scripting

  • Browser Tab Improvement When Connecting to a Device
    • When you connect to a device using the CLI Scripting Terminal application, the browser tab now displays the device IP address.
  • Improved Device Selection Process to Connect to a Switch
    • You can now enter search criteria (e.g., IP address, OS Version, Location) in the Device field to search for and select a device to connect to. The Switch Picker and Topology options are still available.


  • IPv6 Endpoint Support
    • IPv6 endpoints connected to AOS 8x switches are now reported in the IoT application.


  • Report Name and Widget Name Included in Report PDF
    • When you create a PDF of a Report, the Report Name and Widget Name are now included in the Report PDF.


  • External Apps Feature
    • The new External Apps feature (Security - External Apps) is used to create an API security key that is used by external devices/applications to access the OmniVista Server. For example, the Asset Tracking Engine will use this key to access OmniVista Cirrus.

SSID (and WLAN Expert)

  • New Roaming Option
    • FBD Update on Association - Enables/Disables FDB update on Association. If enabled, when a client roams to a new AP, the AP will send ARP packets to the uplink switch to notify the switch to change the downstream forwarding port for the wireless client's traffic.


  • New Highlight Filters
    • There is a new Filter Category - Device Properties, that can be used to highlight SPB Backbone Edge Bridge (BEB) devices and Backbone Core Bridge (BCB) devices in a map.

Users and User Groups

  • New Permissions for Netadmin User
    • The netadmin user now has read/write access to the License Screen and can also create/edit/delete AP Groups, Trust/Untrust APs, create/delete maps/sites, and modify the accessible maps of role.


  • Enable the Local UPAM Database for ASA
    • You can enable Switch User Authentication through the local Switch User Account Database in UPAM. By default, this option is disabled, and Switch User Accounts are authenticated through an external Authentication Server. To enable ASA using the local UPAM Database, go to the Switch User Account Screen (UPAM Authentication Switch User Account), select a username(s) and click on the “Enable ASA” button.
  • Automatically Generate Random Device Specific Passphrase
    • When you are creating/editing an entry in the Company Property List, click on the “Generate” button to automatically create a random Device Specific Passphrase.
  • Device Specific Passphrase Validity Period
    • You can now set the duration for a Device Specific Passphrase (e.g., Always, 6 Weeks, 3 Months). You can also set a specific date and time for the validity period to expire.
  • Additional Information on Company Property PSK Printout
    • The Device Name and PSK Passcode Validity Period are now displayed on the PSK Printout.
  • PSK Passphrase Can Be Viewed Company Property List
    • You can now view the Device Specific Passphrase for a device in the Company Property List. In the Detailed View for the device click on the “Show Password” icon next to the field to view the passphrase. It can also be viewed when creating/editing the passphrase.
  • Custom Attributes Displayed for Captive Portal Access Records
    • Custom Attributes created by a user are now displayed in the Detailed View of Captive Portal Access Records as well as in exported .csv files of Captive Portal Access Records if Login Strategy = “Terms and Conditions”.
  • Create Employee Account or Company Property Entry from Authentication Record
    • If a device fails authenticated through the Local Database, you can automatically create an Employee Account, or add the device to the Company Property List by selection it and clicking on the Generation button at the top of the Authentication Record Screen.

Unified Policy

  • Reflexive Policies for Stellar APs
    • You can now configure Reflexive Policies for Stellar APs in when configuring a Unified Policy. Note that if the Reflexive option is set to "No", the policy will be a stateless rule. In this case, the iptable rule is with "NOTRACK". If some traffic matches the NOTRACK rule, functions depending on conntrack will not work. For example, DPI depends on the first 15 packets of the same conntrack session, it might not work if the traffic matches a "NOTRACK" policy. 


  • Filter Clients by Physical Map and Logical Map
    • You can now filter the Wireless Client List, Wired Client List, Wireless Client Session, Wired Client Session, and Client Summary data by Physical or Logical Map.
  • Heat Map Improvement
    • You can now configure up to 150 floors in a Heat Map.
  • Export the Wireless Client List
    • You can now export the List of Clients on All APs List to a .csv file. You can include all clients. However, only the clients included in the current filter applied to the list, if applicable.
  • New RF Profile Settings
    • MU-MIMO - Enables/Disables Multi-User, Multiple-Input, Multiple-Output (MU-MIMO) feature. If enabled, the AP can communicate with multiple devices simultaneously. This decreases the time each device has to wait for a signal and speeds up the network.
    • High-Efficiency - Enables/Disables 802.11ax high efficiency wireless functionality. If Disabled, an HE mode capable AP will downgrade to VHT (Very High Throughput) mode.
    • Scanning Channel -Specify the channel(s) on which the wireless background scanning is executed (Working Channel/Working Channel and Non-Working Channel). For a highly-sensitive packet delay use case, it is recommended that you enable background scanning only for the Working Channel.

Remote Access Points

  • Hyper-V Deployment Support
    • Hyper-V is now supported for RAP VPN VA deployment.
  • Improved RAP Import Process
  • You can now include the VPN Server Settings name in the .csv file used to import RAPs into the Device Catalog of your Freemium OmniVista account.
  • Improved VPN Settings Export Process
  • You can now export VPN Settings for RAP as soon as the RAP is added to the Device Catalog. You do not have to wait until the AP reaches “Registered” status.
  • Remote APs Support for Multiple VLANs and Local Breakout
    • SSID Tagged VLAN - SSID Tagged VLANs are now supported. Note that on AP1201H downlink ports, only untagged traffic is supported for tunneling.
    • Local Breakout - Local Breakout is now supported. Local Breakout must be configured in the SSIDs application. The routes are applied to all SSIDs.

Network and Device Prerequisites

The following prerequisites must be verified/configured before using OmniVista Cirrus.

Customer Network Prerequisites

The following Network Deployment, Bandwidth, Proxy, Firewall, and NTP Server configurations must be verified/configured on your local network before using OmniVista Cirrus.

Network Deployment

The following sections detail DHCP Network and Static Network deployment prerequisites.

DHCP Deployment Requirements

Standard Requirements

  • IP Address - DHCP Server IP address.
  • Option 1 - Subnet Mask.
  • Option 2 - Gateway.
  • Option 6 - Domain Name Servers - Required for FQDN resolution of OmniVista Cirrus connection points.
  • Option 28 - Broadcast Address. This option is only recommended, not required.
  • Option 42 - NTP Server(s) - Required for Certificate validation (start date and duration), and all related encryption functions. This option is not required on devices running AOS 6.7.2 R04 / AOS 8.5R2 / AWOS or higher. It is however, recommended.

ALE Specific Requirements

  • Option 43
    • Sub-Option 1 - Vendor ID. Validate the DHCP response (must be set with the value alenterprise). This sub-option is only required if you specify any of the sub-options listed below, or any devices on your network are running AOS 6.7.2 R03.

The following Sub-Options are only required if you are using a Proxy to connect to the Internet.

    • Sub-Option 129 - Proxy URL. It can be either an IP address or a URL (e.g., "IP-address=", "URL=").
    • Sub-Option 130 - Proxy Port.
    • Sub-Option 131 - Proxy User Name. If the customer proxy access requires authentication, both 131 and 132 can be supplied via these sub-options.
    • Sub-Option 132 - Proxy Password.
    • Sub-Option 133 - Network ID.
  • Option 138 - Remove any existing configuration (required for all ALE Devices).

Static Deployment Requirements

The following switch configuration prerequisites must be met for a Static Network Deployment.

1. Execute the following CLI commands on each switch. The commands can be contained in a CLI Script and pushed to network switches. See the CLI Scripting online help for more information.

ip name-server <dns_ip>
ip domain-lookup
ntp server <ntp_ip>
ntp client enable

2. (If you are using a Proxy), modify the <running directory>/cloudagent.cfg file on each switch as follows:

  • Activation Server URL: Enter the Activation Server FQDN.
  • HTTP Proxy Server: Enter the Proxy IP address.
  • HTTP Proxy Port: Enter the Proxy IP port.
  • HTTP Proxy User Name: Enter the Proxy username.
  • HTTP Proxy Password: Enter the Proxy password.

3. Enable the Cloud Agent on each switch with the following CLI Command:

cloud-agent admin-state enable

Bandwidth Requirements

For basic onboarding of devices and connection to the OmniVista Cirrus Server, a minimum of 10 kbps end-to-end network throughput is required between the device and OmniVista Cirrus.

Advanced Management
To enable statistics data transfer, status queries, configuration commands, and other requests/responses between devices and OmniVista Cirrus, a minimum of 64 kbps end-to-end network throughput is required between the device and OmniVista Cirrus. APs must be running the latest AWOS software version.

Proxy Requirements

If a device is accessing the Internet via an HTTP/HTTPs proxy, the proxy server must be specified in DHCP Option 43, Sub-option 129 (Server) and Sub-Option 130 (Port). The server may be specified in 1 of 2 formats: 1) “URL=http://server.domain”, or 2) “IP-address=”. The port is specified as a number (8080).

Firewall Requirements

The following ports must be configured to allow outbound traffic from your local network:

  • 443 - If you are not using a Proxy to connect to the Internet, your firewall must allow outbound access to this port; if you are using a Proxy, you need to be able to access this port via your local proxy.
  • 80 - Relevant only if you are accessing UPAM Guest/BYOD Captive portal via insecure HTTP.  If you are not using a Proxy to connect to the Internet, your firewall must allow outbound access to this port; if you are using a proxy, you need to be able to access this port via your local proxy.
  • 123 - Relevant if you are using an NTP Server that is outside of your network. You must ensure that your firewall allows outbound access to port 123 udp. This access cannot be mediated by a proxy, it must be direct (NAT is allowed).
  • 53 - Relevant if you are using a DNS Server that is outside of your network. You must ensure that your firewall allows outbound access to both port 53 tcp and port 53 udp. This access cannot be mediated by a proxy, it must be direct (NAT is allowed).

NTP Server Requirements

An NTP Server(s) is required for Certificate validation (start date and duration), and all related encryption functions. Devices must have access to at least one NTP Server, whether local or external. Note that if a device's System Time is not correct, it may take several attempts to synchronize with the NTP Server before the device connects to the OmniVista Cirrus Server.

Device Prerequisites

The minimum device software versions for onboarding and management are detailed below. The minimum onboarding versions are required for the device to connect the to the OmniVista Cirrus Server. The specified management software versions are required to support all of the management features available in OmniVista Cirrus 4.5.2.


For onboarding (call home and connection to the OmniVista Cirrus Server), devices must be running the following minimum software versions:

  • AOS 6.7.2.R05
  • AOS 8.5R2
  • AWOS 3.0.5.xx.


Devices must be running the software versions specified below to support all of the management features available in OmniVista Cirrus 4.5.2.

  • Essential Switch (E) - OS6350/OS6450 - (6.7.2.R06), OS6465 (8.6R1), OS6560 (8.6R1)
  • Core Switch (C) - OS6900 (8.6R1)  
  • Advanced Switch (A) - OS6860/OS6860E/OS6865 (8.6R1), OS6860N (8.7R1)
  • Stellar AP (SA) - OAW-AP1101, OAW-1201, OAW-1201H, OAW-1201L (available in Brazil only), OAW-AP1221, OAW-AP1222, OAW-AP1231, OAW-AP1232, OAW-AP1251 (AWOS 3.0.7), OAW-AP1201BG, OAW-AP1321, OAW-AP1322, OAW-AP1361, OAW-AP1362 (AWOS 4.0.0)

A link to the latest software images is included in the Verification E-Mail you receive when you create your account. If necessary, click on the link and download the required AOS software. Release Notes, containing detailed upgrade instructions for each device type, are available on the ALE Business Portal.

Supported Devices

A full list of ALE supported devices/AOS releases can be found here.

REST API Management

You can use REST APIs for scripting or integration with any 3rd party systems in your management network. Available OmniVista REST APIs can be found here


Application Visibility

AV No Longer Supports OS6900 Switches (OVC-4434)
Summary: Application Visibility no longer supports OS6900 Switches. Any Application Visibility Policies or Policy Lists applied to these devices should be updated/deleted.
Workaround: NA - Informational.

Configuration Manager

Device Address Column Sorted Incorrectly in Device Backup/Restore Table (OVE-1861)
Summary: If you sort the Device Address Column in the Backup/Restore Table in ascending or descending order, the IP addresses are not sorted correctly. For example, a list of IP addresses will be incorrectly sorted as,,
Workaround: No workaround at this time.

Device Catalog

OV Managed Device Automatically Deleted and License Unassigned (OVC-4683)
Summary: A currently-managed device can be automatically deleted, its license unassigned, and the device moved to “Registered” if the IP address assignments of devices are changed.

For example, suppose there are two devices discovered and managed by OmniVista: Device1 with IP address "IP1", and Device2 with IP address "IP2". At some point, the IP Address assignment for these devices are changed as follows: Device1 IP address is changed from "IP1" to "IP2"; and Device2 IP address is changed from "IP2" to something else. This scenario could happen, for example, if the DHCP Server is restarted and does not attempt to give the same IP address as before to the DHCP clients.

If Device1 is then rediscovered (as part of periodic polling or by a manual user action), Device2 will be deleted from OmniVista when OmniVista discovers that Device1 now has the "IP2" IP address to avoid the situation where two devices have the same IP address in OmniVista.
Workaround: NA - Informational.

Upgrades Are Triggered Differently for 6x and 8x Switches (OVC-435)
Summary: The Activation Server checks the "current software version" from the switches to determine whether a switch should upgrade or not. Because of the different behaviors of 6x and 8x Switches, there may be some inconsistencies about when a switch will be triggered to upgrade.

  • AOS 8x switches send current software version of the current running directory.
  • AOS 6x switches send current software version of WORKING directory when in sync.

Example AOS 6x:
Assume switch comes up in the Certified Directory.
Assume /flash/working has the same image version as "desired software version" set in Device Catalog, whereas /flash/certified has a lower version. Since AOS 6x sends current software version of /flash/working, upgrade will NOT be triggered on the switch.

Example AOS 8x:
Assume switch comes up in the Certified Directory.
Assume /flash/cloud has the same image version as "desired software version" set in Device Catalog, whereas /flash/certified has a lower version. Since AOS 8x sends current software version of current running directory which is /flash/certified. there will be an upgrade. The switch will download the desired software version to /flash/cloud and reboots from /flash/cloud.

Workaround: NA - Informational.

Auto-Upgrade for Switches Running Lower Than AOS 6.7.2.R7 (OVC-8103)
Summary: Switches running an AOS version lower than 6.7.2.R7 will be automatically upgraded to AOS 6.7.2.R7 even if you select the "Do Not Upgrade" option when adding the device to the Device Catalog.
Workaround: N/A - Informational.


Upgrade Workflow Should Be Changed When Device Is Loaded From Certified Directory (OVC-435)
Summary: When an AOS 6.x Switch with "Set to Software Version" set to "Latest Version" contacts the OmniVista Server, the server checks the Working Directory to see if it is running the latest AOS software. If the Working Directory contains the latest software version, an upgrade will not be triggered, even if the Certified Directory is running on an older software version. To upgrade the Certified Directory to the latest software, reboot the switch from the Working Directory.
Workaround: NA - Informational.


APs Are Displayed as IOT Devices in IoT Inventory (OVE-5542)
Summary: Stellar APs connected to AOS switches are displayed as IOT endstation devices in IoT inventory List.
Workaround: To prevent an AP from being displayed in the Inventory List, you must disable IoT profiling on the switch port connected to the AP using the following CLI command: device-profile port slot/port admin-state disable.

IoT Inventory Does Not Work if sFlow is Enabled on Switch (OVE-5544)
Summary: Devices are not displayed in the Inventory List if sFlow is enabled on a switch.
The problem is fixed in AOS 8.6R2. Upgrade switch to AOS 8.6R2.

Device Start Time Is Incorrect in IoT Inventory List (OVE-5658)
Summary: If a device is moved to a different port on a switch, the Start Time displayed in the Inventory List will reflect the first time the device was connected to the switch.
Workaround: The problem is fixed in AOS 8.6R2. Upgrade switch to AOS 8.6R2.

IoT Inventory List Displays Active/Online Endpoints as Offline (OVC-6788)
Summary: The IoT Inventory List displays multiple Active/Online endpoints as offline for devices connected to switches running AOS 8.6R1.
Workaround: The problem is fixed in AOS 8.6R2. Upgrade switch to AOS 8.6R2.

IoT Client Continuously Re-Connects After Category Enforcement (OVE-7648)
Summary: If a client is authenticated over a RADIUS Server and classified into a UNP Profile, and then another UNP Profile is applied via IoT Category Enforcement (same or different profile), the client will continuously re-connect.
Workaround: No workaround at this time. The problem will be fixed AOS 8.7R1. Upgrade switch to AOS 8.7R1.


Cannot Onboard a Switch Running AOS 6.7.2.R05 (OVC-6879)
Summary: You cannot successfully onboard a 6.x switch in the Provisioning application that is running a AOS 6.7.2.R05.
Workaround: For 6.x Switches, Provisioning is only supported on AOS 6.7.2.R06 and higher. Upgrade the 6.x Switch to a supported build.


MTS-Managed Tenant Local Users Cannot Use "View SSIDs on an AP Group" Feature (OVC-6321)
Summary: When managed by MTS, local Tenant Users cannot use the "View SSIDs on an AP Group" button to quickly view SSIDs by AP Group.
Workaround: Users who want to view SSIDs associated with a specific AP Group need to go to each SSID and view its AP Group association. Click on the AP Group Assignment and Schedule button at the top of the SSIDs screen to bring up the “AP Group Assignment and Schedule” Screen. Select an SSID from the SSID Service Name drop-down. The AP Group(s) associated with the SSID are displayed.


HTTPs Traffic is Not redirected to Portal Page for an HSTS Website (OVC-1777)
Summary: The first time a user opens an HSTS website, they are redirected to the portal page, as expected. The second time a user opens an HSTS website, the redirection will not work. If the user clears browser cache and retries connecting to the HSTS website, it will work. The behavior depends on the browser used. Chrome is very strict, so the problem is always seen, Firefox is not as strict; the problem will still happen but not as frequently.
Workaround: There is no workaround at this time.

No IPv4 or IPv6 Value Displayed in UPAM Authentication Record (OVC-6061)
Summary: Client IP address is not displayed in UPAM Authentication Record.
Workaround: No workaround at this time.

Delay in UPAM Interactions After Subscriber Gets a Paid Account (OVC-6806)
Summary: After a subscriber gets a paid account, UPAM related interactions will not work until free radius server is restarted (at 00:00 AM the subsequent day).
Workaround: There will be a delay in realizing any expected changes in UPAM function when any of the following occurs:

  • Creation of a new tenant
  • Activation of a different RADIUS Server Certificate
  • Synchronization of RADIUS Attribute Dictionary at OmniVista with RADIUS Server
  • Edit of NAS Client details.

After any of the above actions, expected UPAM changes will take effect after the following midnight (00:01 a.m. PST), as these require a restart of the OmniVista internal RADIUS Server. The OmniVista internal RADIUS Server is restarted periodically at midnight PST. All tenants sharing the same OmniVista VM will experience a brief period of interruption of UPAM RADIUS functionality during this periodic restart.


Client Blacklisting Does Not Work on AP1320/AP1360 (OVE-9544)
Summary: The “Add to Blacklist” function from WLAN - Client List in OmniVista does not work with clients connected to Stellar OAW-AP1320/AP1360 APs. The client is moved to the Blacklist on the OmniVista GUI, but remains connected to the network on the AP1320/AP1360.
Workaround: No workaround at this time.


If You Remove a Master from a Virtual Chassis Slave Devices Lose Connectivity
Summary: If You Remove a Master from a Virtual Chassis (VC), Slave devices Lose Connectivity Due to stale certificates. Devices use a certificate to communicate with OmniVista Cirrus. This certificate is given to the devices by the OmniVista Cirrus on their first Activation attempt. In a VC, the Master chassis is issued a certificate for its Serial Number and this certificate is copied over to all the Slaves. If the owner of the certificate (Master) is removed permanently from the VC, the remaining chassis will form a VC and attempt activation using the certificate of the old Master, but will be unable to activate using this certificate. Customers should raise a ticket with ALE Customer Support to overcome this issue. After understanding the VC topology, ALE Customer Support might take a decision to remove the certificate from the VC and enable the remaining chassis in the VC to attempt Cloud Activation afresh.
Workaround: Raise a ticket with ALE Customer Support. After investigating the VC topology, ALE Customer Support may decide to remove the certificate from the VC and enable the remaining chassis in the VC to re-attempt activation.

Problem Connecting to Switch with OV Assistant When Multiple Bluetooth Dongles Present (OVC-7240)
Summary: The OmniVista Assistant uses the Bluetooth dongle MAC address to initiate a connection to a switch. If multiple Bluetooth dongles are active at the same time, OmniVista Assistant may initiate a connection to an unexpected dongle.
Workaround: Make sure there are no other active Bluetooth dongles in the area. And make sure the correct model and serial number appear under "Paired Devices" before initiating a connection to a switch.

Unable to find the RAP in the OV2500 (OVC-8302)
Summary: RAP was not displayed in OmniVista when the Dual Stack Lite technology was used for Internet access in RAP/VPN VA configuration.
Workaround: Dual stack configuration is not supported in Remote Access Point/VPN VA deployment.

Issues Fixed

Issues Fixed Since Release 4.5.1

  • ALE-BYOD Users and ALE-Corp Users Disassociated from SSIDs (OVE-6759)
  • Delete Map Cannot Complete in Topology (OVC-7412)

Issues Fixed Since Release 3.0

  • If Network ID Strict Mode Is Enabled Some Devices Will Be Unable to On-Board (OVC-4381)
  • Cannot Notify Policy List with Accept All | Deny All Policy on AOS 6x Devices (OVC-6133)
  • Unable to upload Captive Portal Certificate on UPAM (ALEISSUE-410)
  • Unable to change “Account Validity Period” While Creating Guest Access Code with Service Level (ALEISSUE-459)
  • APs were UP, however showed DOWN in OmniVista (ALEISSUE-383)

Issues Fixed Since Release 2.1.0

  • External LDAP Server Requires Direct Connection (OVCLOUD-2832)
  • BYOD Access Strategy "Go to initial URL" Option Does Not Work on AOS 6x Switches (OVC-421)
  • No CLI Command to Configure Network ID in Statically Configured Cloud Agents (OVC-4569)

Issues Fixed Since Release 2.0

  • Cannot Remove a BYOD/Guest Online Device From Device List on AOS 8x Switches (OVC-419)
  • Cannot Find Audit Logs in OmniVista Cirrus (OVC-456)
  • Error When Applying Access Role Profile with Policy List to 6x Device (OVC-459)
  • Cannot Apply Policy List from RADIUS Attribute "Alcatel-Policy-List" in UPAM on AOS 6.x Switches (OVC-463)
  • Captive Portal Page Is Not Kept After Upgrading From 1.0.2 (OVC-2467)
  • AP Image Upgrade From 3.0.2 to 3.0.4 Requires 2 Reboots (OVC-2957)
  • Device Status Color Does Not Change When a Trap is Sent From an AP (OVC-3220)
  • Minimum OS Versions Required for Full OmniVista Cirrus Functionality (OVC-3468)
  • OS6560 Device Loses VPN Connectivity and Remains in a DOWN State (OVC-3530)
  • Guidance for Users with ALE Business Store Based OmniVista Cirrus Subscriptions That Are Pending Activation (OVC-3776)
  • OS6560 Dumps ipcmmd pmds When Calling Home (OVC-3834)

Issues Fixed Since Release 1.0.2

  • Hide Top N clients and Top N App Charts (OVC-1565)
  • OS6560 Does Not Support Policy List on OS6560 Switch running AOS 8.4.1.R03 (OVCLOUD-1384)
  • Status of All AOS Devices Changed from “OV Managed” to “Pre-Provisioning" in Device Catalog (OVC-145)
  • Analytics Line Chart Does Not Display Date in X-Axis (OVC-461)

Issues Fixed Since Release 1.0.1

  • Device Added to Data Lake Is Not Added to Device Catalog Even Though "Call Home" Was Successful (OVC-146)
  • VC of 2 OS6900-X20 Disappeared from the List of Managed Devices (OVC-147)

Additional Documentation

Online help is available in OmniVista Cirrus and can be access by clicking on the Help Link (?) in the upper-right corner of any screen. You can also search through the online help on the OmniVista Cirrus Home Page. An overview of OV Cirrus as well as Getting Started Guides for Freemium and Paid Accounts is available here.