OmniVista Cirrus Production Notes 2.0
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: Internet Explorer 11+ (on Windows client PCs), 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
- Network and Device Prerequisites
- Supported Devices
- Issues Fixed
- Additional Documentation
An overview of new features and functions is provided below.
OmniVista Cirrus now supports the following devices:
- Stellar APs
- OAW-AP1201H - Features three (3) RJ45 downlink Ethernet ports. This enables wireline clients to access the network via APs (for IP Phones, Printers, TVs in hotels/hospitals). The ports can be monitored and enabled/disabled in the OmniVista Cirrus Inventory application (Network - Inventory - Managed Inventory - Ports); and can be configured using the Unified Access application.
- Support for 4,000 APs - OmniVista now supports up to 4,000 APs.
- AOS Devices
- Mobile Device Support
- UPAM Captive Portal Login is now supported on tablets and phones.
OmniVista Cirrus now supports the following OS Software Versions:
- AOS 6.7.2.R04 - OS6350 and OS6450 Devices
- AOS 8.5R2 - OS6465, OS6560, OS6860/OS6860E/OS6865, and OS6900 Devices
- AWOS 184.108.40.2066 - Stellar APs
UI Enhancements Across Applications
- The UI has been optimized to display more information:
- Columns and text resized
- Full-screen view option available for all screens.
- Left-Hand Side Menus automatically close after a page is initially displayed to provide display more information on the screen. You can click on the arrows (>>) or hover the mouse over the area to temporarily display the menu, or lock the menu in place by clicking on the Pin Sidebar icon at the top of the menu.
- The navigation icon color scheme has been changed to a gray background for easier viewing.
- An "Application Results" button has been added to the top of the screen. Click on the button to display a list of user actions taken in the application. The information will persist until the user logs off. At this time, this feature is only supported in the Device Catalog application. The button is located to the left of the Support Center link at the top of the screen.
The following new applications have been added to OmniVista Cirrus.
- Audit - OmniVista Cirrus now includes the Audit Application (Administrator - Audit). The Audit application is used to monitor client and server activity, such as the date and time when a user logged into OmniVista, when an item was added to the discovery database, when a configuration file was saved, or when a particular application was launched. The information is contained in log files, which are organized by type (e.g., Network, Configuration) on the Audit Home Page. You can also collect log information from a network device that you can send to Alcatel-Lucent Enterprise (ALE) Technical Support to troubleshoot problems.
- Configuration Manager - The Configuration Manager application (previously known as Resource Manager) is used to backup/restore configuration files, view the contents of a backup file, compare configuration files, and view a summary of backup/restore operations. You can also set the backup retention policy and the amount of space that must be available on the CMM before an upgrade is allowed. Image Upgrade Functions (which were previously part of the Resource Manager application) are now performed on the Device Catalog page.
- Report - OmniVista Cirrus now includes the Report Application (Configuration - Report). The Report Application enables you to create and schedule reports in certain OmniVista Cirrus applications. These reports are generated and stored as PDF documents. So in addition to viewing information in real-time, you can generate PDFs of the screens.
- AP Registration
- Access Points
- Reset APs - A new "Reset APs" button has been added. When you reset an AP, the AP will reset to the factory default configuration and reboot. When an AP is rebooted as part of a reset, the latest configuration available on OmniVista is downloaded to the AP. If the AP is unable to connect to OmniVista, the AP will come up with the factory default configuration.
- Edit AP IP Address - You can edit the IP address of an AP by selecting the AP and clicking on the Edit icon. Click on "Edit Mode" to edit the IP address. You can also set the AP to default DHCP Mode.
- Web UI Device Management Tool - A Web UI Device Management Tool is now available to view configuration information and perform limited management on individual Stellar APs. To access the Web UI Device Management Tool, select an AP in the Access Points List and click on the AP Web option in the "Action" drop-down. Access Points Screen.
- Access Heat Maps for Individual APs - You can view a Heat map for a Stellar AP by selecting an AP in the Access Points List and clicking on the Heat Map option in the "Action" drop-down.
- View Port Information - You can view port information on 1201H APs by selecting an AP(s) and selecting "Port Management" from the "Action" drop-down. The Ports page in the Inventory application will open with port information displayed for the selected APs.
- Bridge Tab - A new Bridge Tab has been added to the Access Points Table to display information on APs working in wireless Bridge Mode.
- AP Group
- Enable SNMP - This option allows third-party SNMP-based platforms to monitor APs in a group using SNMP. OmniVista Cirrus does not use SNMP to manage Stellar APs. With defined SNMP MIBs, an Administrator can monitor APs, configured services, and wireless clients and their traffic utilization.
- External Captive Portal Configuration - The External Captive Portal Config File Screen has been added to create a custom External Captive Portal Configuration File. The file is used to establish a secure connection between OmniVista and an external captive portal server for authentication of Stellar APs.
- Captive Portal
- Redirect to FDQN - Captive Portal can be configured to redirect to an FDQN as well as an IP address.
- Captive Portal Certificates - You can create Captive Portal Certificates to implement the HTTPs login when UPAM is used as a Captive Portal Server.
- Device Catalog Updates
- Automatic Call Home Feature - There is a new Automatic Call Home Feature for the following devices: LAN Devices running AOS 6.7.2.R04 (and later) or AOS 8.5R2 (and later), and APs running AWOS 220.127.116.116. These devices contact the OmniVista Cirrus Server at regular intervals. If configured for automatic software updates, the device will download and install the latest software. Note that you should not reboot a device while it is upgrading. You can determine if a device is upgrading by checking the "Device Status" column; or check for the next schedule call home time in the "Approximate Time of Next Call Home" column.
- Image Upgrade - The image upgrade functions are now performed on the Device Catalog page. You can select a device(s) and click on the "Set Software Version" button at the top of the Device Catalog to upgrade image files.
- Streamlined Device Deletion - Device deletion from the Device Catalog has been streamlined. A device can be deleted directly from the Device Catalog in a single step.
- Color Coded Device Status - Information in the Device Status column is color coded to more easily view the status (e.g., Green, Yellow, Red).
- Color Code Current Software Version - Information in the Current Software Version column is also color coded to more easily view the status of the current device software. (e.g., Black = Up to Date, Yellow = Below the Latest Version, Red = Version Should Be Updated). In addition, you can hover over an entry for more information.
- Configuration Change Notification Button - There is an "Unsaved Working Directory" Notification button at the top of the screen. If any managed devices have unsaved changes in the Working Directory, a number will appear on the button (Bell icon). Click on the button to display a list of devices in this state. You then have the option of saving the changes in those devices. This Notification button is also displayed on the Managed Devices Screen and in the Topology application.
- Serial Number Links - Serial Numbers are displayed as links. When you click on a device's serial number, the Topology application will open and the device will be highlighted in a map.
- Updated Column Heading - The "Set to Software Version" column has been renamed to "Desired Software Version".
- Automatically Apply Licenses - A new option in the License Wizard enables you to automatically apply a license to a device when a device is added to the Device Catalog. The option is also presented when a user upgrades from a Freemium account to a Trial or Paid account. Also, two new buttons have been added to the License Home Page:
- Activate Add Ons - If you purchase additional licenses or license extensions through your Business Partner, the "Activate Ad-On" button at the top of the screen will be activated. Click on the button to activate the licenses. If you do not click on the button, the new licenses/extensions will automatically be activated when older licenses expire.
- Extension Details - If you purchase a license extension, the "Detail of Extension" button will be activated. Click on the button to see when the extension will be applied.
- Subscription Number and Activation Code - When you upgrade to a Paid account, you now enter your Subscription Number and Activation Code, which you receive from your Business Partner, in the applicable fields.
- Unified Access
- Map Access Role Profile to Untagged Traffic - For AOS Devices, a VLAN must exist on a switch to configure VLAN Mapping. However, for APs, you can now map an Access Role Profile to untagged traffic.
- "Walled Garden" Feature - Fields on the Access Role Profile configuration screen have been updated to support the “Walled Garden” feature for Stellar APs. This feature allows users to authenticate through social media login, and also enables you to configure “whitelist” domains to direct users to certain website without authentication. Also, you can now configure Client Session logging as part of an Access Role Profile.
- Client Session Logging - You can enable and configure logging for wireless client sessions as part of an Access Role Profile.
- Client Isolation - Client isolation is a security feature to lock down your Wi-Fi clients to only access the Internet. It is configured on the WLAN Service Screen.
- Smart Sticky Avoidance - This feature is used to assist with client Wi-Fi roaming (e.g., 802.11k/802.11v protocol, Client Data Rate Controls, Minimum MGMT Rate Controls). It is configured on the WLAN Service Screen.
- New Client Monitoring Screens - New client monitoring screens have been added (WLAN - Client):
- Client Summary Screen - Provides a graphical view of the number of clients and client throughput on the network. You can view the information by AP/AP Group and WLAN; and can view information over different time periods (24 Hours, Last 7 Days, 30 Days, 90 Days).
- Client Session Screens - Provide information about wireless and wired clients associated with APs.
- LBS Widget - Provides a link to the OmniAccess® Stellar Location Based Services (LBS) Cloud Manager application.
- Top N Devices by Traps - Displays a summary of traps by device and severity level. You can display the top 5, 10, 15, or 20 devices, and view traps by severity level.
DHCP Server 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 18.104.22.1686 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=22.214.171.124", "URL=http://server.name").
- 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.
- Option 138 - Remove any existing configuration (required for all ALE Devices).
For basic onboarding of devices and connection to the OmniVista Cirrus Server, a minimum of 10 kbps end-to-end network throughput is recommended between the customer premise and the OmniVista Cirrus hosting infrastructure.
To enable statistics data transfer, status queries, configuration commands, and other requests/responses between devices and OmniVista Cirrus, a minimum of 512 kbps end-to-end network throughput is recommended between the customer premise and the OmniVista Cirrus hosting infrastructure.
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=126.96.36.199”. The port is specified as a number (8080).
The following ports must be configured to allow outbound traffic from your local network if you are not using a Proxy to connect to the Internet, or if your DNS or NTP Servers are outside of your network:
- 443 - If you are not using a Proxy to connect to the Internet. Either your firewall must allow outbound access to this port; or if you have one, you may access the port via your local proxy.
- 80 - If you are not using a Proxy to connect to the Internet. Either your firewall must allow outbound access to this port; or if you have one, you may access the port via your local proxy.
- 123 - If you are using an NTP Server that is outside of your network. If External, 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 - If you are using a DNS Server that is outside of your network. If External, 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).
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.
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 2.0.
For onboarding (call home and connection to the OmniVista Cirrus Server), devices must be running the following minimum software versions:
- AOS 188.8.131.52.R03
- AOS 184.108.40.206.R03
- AWOS 220.127.116.11.
Devices must be running the software versions specified below to support all of the management features available in OmniVista Cirrus 2.0.
- Essential Switch (E) - OS6350/OS6450 - (6.7.2.R03 - Build 112 or higher, 6.7.2.R04), OS6465 (8.5R2), OS6560 (8.4.1.R03, 8.5R2)
- Core Switch (C) - OS6900 (8.4.1.R03, 8.5R2)
- Advanced Switch (A) - OS6860/OS6860E/OS6865 (8.4.1.R03, 8.5R2)
- Stellar AP (SA) - OAW-AP1101, OAW-1201H, OAW-AP1221, OAW-AP1222, OAW-AP1231, OAW-AP1232, OAW-AP1251 (AWOS 18.104.22.1686)
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.
A full list of ALE supported devices/AOS releases can be found here.
AP Image Upgrade From 3.0.2 to 3.0.4 Requires 2 Reboots (OVC-2957)
Summary: When an AP is upgraded from 3.0.2 to 3.0.4 from Device Catalog, it is upgraded in two steps. The AP is first upgraded to 22.214.171.12480 (which includes a reboot) and then upgraded to 3.0.4 (which requires a second reboot). Likewise, when an AP is upgraded from 3.0.3 to 3.0.4, it is upgraded in two steps. The AP is first upgraded to 126.96.36.1995 (which includes a reboot) and then upgraded to 3.0.4 (which requires a second reboot). However, this two-step upgrade process is transparent to the user.
Workaround: NA - 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
Device Status Color Does Not Change When a Trap is Sent From an AP (OVC-3220)
Summary: If a trap is sent from an AP, a Trap Notification Status circle appears in the upper-right corner of the Device Status circle, but the Device Status circle may not change to orange (indicating that traps have been received from the device).
Workaround: If a Trap Notification Status circle appears, this indicates that traps have been received on the device. The Device Status circle issue will be fixed in the next release.
Error When Applying Access Role Profile with Policy List to 6x Device (OVC-459)
Summary: A Failure error may occur when applying an Access Role Profile with a Policy List containing a large number of policies to 6x Devices. This may be due to network latency.
Workaround: Reduce the number of Policies in the Policy List and retry (e.g., reduce the number of policies in the list from 10 to 5).
BYOD Access Strategy "Go to initial URL" Option Does Not Work on AOS 6x and AOS 8x Switches (OVC-421)
Summary: The "Go to Initial URL" option for successful login does not work on AOS 6x and AOS 8x Switches. It does work on APs.
Workaround: There is no workaround at this time.
External LDAP Server Requires Direct Connection (OVCLOUD-2832)
Summary: If you are using an external LDAP Server, you must have a direct connection to the server using a public IP address.
Workaround: NA - Informational.
Cannot Remove a BYOD/Guest Online Device From Device List on AOS 8x Switches (OVC-419)
Summary: User is unable to remove a device from the BYOD/Guest Online Device List using the "Kick Off" button.
Workaround: There is no workaround at this time.
Cannot Apply Policy List from RADIUS Attribute "Alcatel-Policy-List" in UPAM on AOS 6.x Switches (OVC-463)
Summary: If RADIUS returns attributes Alcatel-Policy-List: list1 and Filter-Id: arp_byod, wired clients connected to AOS 6.x Switches (6.7.2.R04 and lower) only receive the Access Role Profile (attribute Filter-Id: arp_byod) and not the get Policy list (attribte Alcatel-Policy-List: list1).
Workaround: Do not configure Alcatel-Policy-List attribute in RADIUS. If RADIUS returns only the attribute Filter-Id: arp_byod, the CLI shows the "Policy List Name" correctly (to be the policy list associated with the Access Role Profile). This problem will be fixed in the AOS 6.7.2.R05 switch release.
Captive Portal Page Is Not Kept After Upgrading From 1.0.2 (OVC-2467)
Summary: After upgrade from 1.0.2 to 2.0.0, the data for Captive Portal Page is not kept. After upgrading, only the description and the page name are retained, other customizations are reset to default.
Workaround: The Portal Page design has been updated for OV 2.0. You must re-configure the Captive Portal Page in OV 2.0 based on the new design.
Cannot Find Audit Logs in OmniVista Cirrus (OVC-456)
Summary: Access to Audit Logs is not available in the OmniVista Cirrus UI.
Workaround: Contact Customer Support to review Audit Logs.
Minimum OS Versions Required for Full OmniVista Cirrus Functionality (OVC-3468)
Summary: Existing devices may need to be upgraded for full OmniVista Cirrus functionality. The information in the Current Software Version column in the Device Catalog is color-coded to indicate the state of the current software version running on the device (e.g., Black - SW is up to date, Amber - SW is below the latest version, Red - SW is old and is not recommended by ALE). If a device is running software that is not recommended by ALE (RED) it must be upgraded. The following software versions must be upgraded. To upgrade a device(s), select the device(s) in the Device Catalog, click on the Set Software Version button, then then select the software version specified below.
- AOS 188.8.131.52.R03 (GA) - Upgrade to the latest 6.7.2.R04 version.
- AWOS 3.0.2.x - Upgrade to the latest 3.0.4 version.
- AWOS 3.0.3.x - Upgrade to the latest 3.0.4 version.
OS6560 Device Loses VPN Connectivity and Remains in a DOWN State (OVC-3530)
Summary: There are two scenarios for this PR. The first scenario is when an OS6560 remains in the "VPN Connectivity In Progress" status in the Device Catalog after the device has been up and running for several days. This occurs when the Temp File system becomes full. The second scenario occurs when an OS6560 is rebooted with the Cloud Agent "Enabled" in the running configuration. When this happens, the ipcmmd process crashes and restarts with a PMD and the device loses Layer 3 functionality, resulting in cloud connection failure. The Device Catalog Status will show the device as "Down".
Workaround: For the first scenario (stuck in "VPN Connectivity In Progress" status), reboot the device. For the second scenario (loss of Layer 3 functionality), remove the Default Route and reconfigure it. This problem will be fixed in AOS Build 8.5R3.
Guidance for Users with ALE Business Store Based OmniVista Cirrus Subscriptions That Are Pending Activation (OVC-3776)
Summary: Previous releases of OmniVista Cirrus used Subscription Number and End Customer ID to identify a subscription. Release 2.0.0 of OmniVista Cirrus uses "Subscription Number" and "Activation Code" to identify a subscription.
Workaround: If a customer purchased an OmniVista Cirrus Subscription before the release of 2.0 and has not yet activated the subscription, they will still be able to activate it using the "Subscription Number" and "End Customer ID" they received when they purchased the subscription. When upgrading to a Paid account, enter your "Subscription ID" in the "Subscription Number" field, and "End Customer ID" in the "Activation Code" field. Both the Subscription Number and End Customer ID are contained in the Confirmation email sent from ALE to the Business Partner when the subscription was ordered.
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.
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)
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)
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, Trial, and Paid Accounts is available here.