This release of OmniVista Cirrus 10.1 is a free “teaser” version of the full OmniVista Cirrus Solution that will be offered in a subsequent release. This limited, “teaser” version of OmniVista Cirrus extends for 6 months and can be used to monitor up to 20 wireless devices (additional time and number of devices can be requested).

OmniVista Cirrus 10.1 can be accessed from anywhere, using any approved browser and device (e.g., workstation, tablet). Access to OmniVista Cirrus 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).

The following URL is used to access OmniVista Cirrus 10.1:
https://manage.ovcirrus.com

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

Features and Functions

Use the following links to familiarize yourself with OmniVista Cirrus 10.1 features and functionality:

Network and Device Prerequisites

An instance of OmniVista 2500 NMS 4.6R1 or OmniVista Cirrus 4.6.1 is required to initially discover and register Stellar Access Points. The Access Points are then configured to send event reports to OmniVista Cirrus 10.1, where the event data is gathered and analyzed.

To ensure communication between OmniVista Cirrus 10.1 and either OmniVista 2500 NMS 4.6R1 or OmniVista Cirrus 4.6.1, follow the steps and guidelines in the Getting Started section.

Supported Devices

This initial release of OmniVista Cirrus 10.1 supports monitoring and reporting of advanced analytics for Stellar Access Points, except for the following models:

  • OAW-AP1101

  • OAW-AP1201L

  • OAW-AP1201H

  • OAW-AP 1201HL

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 links based on your region:

For more information, see Automation with APIs.

Known Issues/Workarounds

Advanced Analytics

A Reconnected User is not Included in the "Devices per user" Statistics (OVNG-3285)
Summary: When a client connects for the first time to a Guest/BYOD portal SSID, their devices are included in “Devices per User”. However, if the client disconnects and then reconnects to the same Guest/BYOD portal SSID, their devices are no longer included in “Devices per User” on the “Client Behavior Analytics Dashboard”.
Workaround: No workaround at this time.

The “Current clients table" and "Client session history" Missing Information (OVNG-3377)
Summary: When a client connects to an AP, sometimes the AP is not sending some of the client attributes (such as Device Type, Device OS, Device Name, Client IPv6 Address). Hence, no values are shown for these attributes in some entries of the Client Session History and Current Clients tables.
Workaround: No workaround at this time.

Other

AP does not Send “portal.report” Event when Wrong Username/Password Entered (OVNG-2082)
Summary: When a user logs in to UPAM Captive Portal with an incorrect username/password, the login will fail but the failure is not immediately indicated on the QoE Analytics UI. Only after 15 minutes will QoE report the failure and the failure is reported as a “Timeout”. Two consequences of this are: Users won’t find out about the failures to login to UPAM Captive Portal until after 15 minutes, and the user will not be able to differentiate between a true “Timeout” with UPAM Captive Portal versus wrong credentials entered at UPAM Captive Portal login.
Workaround: No workaround at this time.

Additional Documentation

Online help is available in OmniVista Cirrus and can be accessed 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 Documentation home page.