OmniVista Cirrus Production Notes (10.2)
This release of OmniVista Cirrus 10.2 is a free trial version of the full OmniVista Cirrus Solution that will be offered in a subsequent release. This limited, trial 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.2 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).
These Production Notes detail features and functions, network/device configuration prerequisites, supported devices, and known issues/workarounds in OmniVista Cirrus 10.2. 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
This section provides an overview of the new features and functions introduced with this release.
Full Management of Stellar Access Points
Previously, OmniVista Cirrus supported the monitoring and reporting of advanced analytics for Stellar Access Points. This approach required an instance of OmniVista 2500 NMS or OmniVista Cirrus 4 to discover, register and manage the Access Point. In this release, the option to discover, register, and manage Stellar Access Points directly from OmniVista Cirrus 10.2 is now supported. There is no requirement for an OmniVista Legacy instance; the Access Points are fully managed through OmniVista 10.2.
When declaring Stellar Access Points in OmniVista 10.2, both options are supported:
Full Management Mode - The device is directly configured and managed through OmniVista Cirrus 10.2. After a device is added in this mode, OmniVista Cirrus the device is then validated by the OmniVista Cirrus. Once the device is validated and connected to your network, it is available for full management.
Analytics Only Mode - The device is directly managed and configured through an OmniVista 2500 NMS or OmniVista Cirrus 4 instance, but OmniVista Cirrus 10.2 will only gather and monitor analytic data sent from the device. The validation process for the device is completed through OmniVista 2500 NMS or OmniVista Cirrus 4, and the device is only declared in OmniVista Cirrus 10.2 for monitoring purposes.
Use the following links to familiarize yourself with OmniVista Cirrus 10.2 features and functionality:
Getting Started – What you need to know to get up and running.
Configuring Organizations for Network Management - How to create and manage Organizations, including creating/modifying sites, adding devices, and adding users.
Configure and Manage Device Inventory - Add, edit, or remove Access Point devices from the device inventory. The Device Inventory is also where devices obtain their provisioning configuration when they are added to the inventory.
Configure WLAN Network Management- Configure wireless networks, policies to prevent attacks on Stellar AP Series Wireless Devices, and Radio Frequency (RF) profiles for devices. It is also used to configure External Engines and UPAM server certificates.
Configure Network Access Control - Configure security functions (authentication, classification) to provide network access controls that are applied to devices attempting to access the network.
Monitoring Network Device Activity – Monitor, evaluate, and troubleshoot network components and device activity.
Automation with REST APIs – Develop applications to integrate with OmniVista Cirrus 10.2.
Few Steps to do before you experience this new version
Step#1: Please clear your browser cache to prevent outdated files from showing up and causing issues.
On Google Chrome, the steps are:
Launch chrome://settings
Click on “Privacy and Security” => “Clear Browsing Data”.
In the “Basic” tab, choose Time Range as “All Time”, and select only the “Cached images and files” option.
Click the “Clear Data” button.
On Mozilla Firefox, the steps are:
Launch the “Options” menu,
Click on “Privacy and Security” and in it find the “Cookies and Site Data” section.
Click on the “Clear Data” button and in the dialog box that opens, remember to choose only the “Cached Web Content” option
Click “Clear” in the dialog box.
Step#2: When you login and visit your Organization, you will be shown a dialog to set your “Country/Region” and “Timezone”. Please provide this information accurately depending on where your Stellar Access Points are located.
Network and Device Prerequisites
To ensure the necessary communication between Access Point devices and OmniVista Cirrus 10.2, verify/configure the following prerequisites on your local network:
Network Perquisites - Network deployment, bandwidth, proxy, firewall, and NTP server requirements.
Device Perquisites - Supported Access Point software and models.
OmniVista Legacy for Analytics Only Mode - Configure an OmniVista 2500 NMS or OmniVista Cirrus 4 to support communication between Analytics Only Access Point devices and OmniVista Cirrus 10.2.
Supported Devices
This release of OmniVista Cirrus 10.2 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 link based on your region: EU: https://eu.manage.ovcirrus.com/apidoc/apidoc.html
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.
Certificates
PKSC8 private key is not supported for LDAP cert and AP Web Cert (OVNG-7726)
Summary: PKSC8 private key will NOT be supported in OmniVista Cirrus 10.2
Workaround: Use RSA private key for AP Web certificate and Local LDAP certificate.
NaaS Device Licenses
Collect Support Info Feature Does Not Work on NaaS APs that have an expired Management License (OVNG-6271)
Summary: If the NaaS management license expires for an AP in NaaS mode, the Collect Support Info operation will fail.
Workaround: Make sure the NaaS Management License is active when the AP is functioning in the NaaS mode.
Other
AP does not Send “portal.report” Event when Wrong Username/Password Entered (OVNG-2811)
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.
Issues Fixed
Issues Fixed Since Release 10.1
The “Current clients table" and "Client session history" Missing Information (OVNG-3377)
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.