Aruba Central PowerPack Release Notes, version 104

Version 104 of the Aruba Central PowerPack includes updates to a number of Dynamic Applications.

• Minimum Required SL1 Version: 10.2.0

Before You Install or Upgrade

Ensure that you are running version 10.2.0 or later of SL1 before installing "Aruba Central" PowerPack version 104.

For details on upgrading SL1, see the relevant SL1 Platform Release Notes.

If you are currently using version 100 of the PowerPack, ScienceLogic strongly recommends completing a fresh installation of version 104 rather than upgrading. If you are currently using versions 101 and 102, then you can do a standard upgrade. The steps for both methods can be found below and in the Monitoring Aruba Central manual. Follow those procedures to ensure accurate data collection post-upgrade.

Installing or Upgrading the PowerPack

By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.

To install this PowerPack:

1. Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
2. In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
3. Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
4. Click Browse and navigate to the PowerPack file from step 1.
5. Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.
6. Click Install. The PowerPack is added to the PowerPack Manager page.

For instructions on using the PowerPack, see the Monitoring Aruba manual.

Features

This release includes the following features:

• Dynamic Application to discover and monitor Aruba Central component devices
• Device Classes for each of the Aruba Central components that the PowerPack can monitor
• Event Policies that are triggered when Aruba Central component devices meet certain status criteria
• A sample SOAP/XML Credential ("Aruba Central Example") that you can use to create your own Aruba Central Credential
• A Device Template ("Aruba Central Template") that aligns Dynamic Applications to the Aruba Central controller virtual device and enables you to discover component devices for that controller
• Device Dashboards that display information about Aruba Central component devices
• A sample SOAP/XML Credential (Aruba Central SSO Example) that can be used to create an Aruba Central SSO Credential.

Enhancements and Issues Addressed

The following enhancements and addressed issues are included this release of the "Aruba Central":

• Updated the "Aruba: Central Component Counts" Dynamic Application to collect and report a value of 0 for the collection object when discovery Dynamic Applications are disabled or unable to collect and store data in the cache.
• Added support for SSO (Single Sign-On) by using Aruba Central's Offline Token Authentication Mechanism.
• Included retries in the count of requests for the rate limit per second of the Aruba Central API.
• Added new Critical API events for HTTP, Connection and Authentication Errors (Aruba Central Connection Errors, Aruba Central HTTP Errors, and Aruba Central Authentication Errors).

• This PowerPack was refactored to use bulk API calls to collect all devices in one call and keep API calls under 1000 per day. Larger customers may have a higher limit of calls per day.

• Most Dynamic Applications were rewritten using the Snippet Framework, except the Dynamic Application "REST: Performance Metrics Monitor."

• Re-enabled the following Dynamic Applications:

  • Aruba: Central Notifications
  • Aruba: Central Components Counts

• Disabled the following Dynamic Applications by default:

  • Aruba Central APs Discovery
  • Aruba Central APs Configuration
  • Aruba Central APs Performance
  • REST: Performance Metrics Monitor (Aruba Central)

  The "REST: Performance Metrics Monitor" Dynamic Application should not be enabled because it has not been rewritten in the Snippet Framework format and will fail to collect if enabled.

  If you wish to collect data for APs, you will need to enable these Dynamic Applications. If the total number of devices in Aruba Central is higher than 8000, visit the SL1 Scale Settings section of the manual.

• Updated the following ScienceLogic libraries:

  • silo_apps
  • silo_aruba_central
  • silo_low_code
  • silo_low_code_steps_standard

Several collection objects were removed from the PowerPack in version 101. These collection objects no longer function in version 104, as their underlying collection code has been removed. Therefore, if you are upgrading to version 104 from version 100, you must either delete or modify the collection objects that were removed in version 101. If you delete them, you will lose any data they previously collected. Alternatively, you can modify them so they no longer have valid snippet arguments; doing so will retain the previously collected data. For more information, see the "Enhancements and Issue Addressed" in the Aruba Central version 101 release notes.

Known Issues

The following known issues affect version 104 of the Aruba Central PowerPack:

• The following widgets will not display data for the "Aruba: Central Controller," "Aruba: Wireless Access Points," "Aruba: Gateway Summary," "Aruba: Gateway," and "Aruba: Switches" SL1 dashboards because the Dynamic Applications "REST: Performance Metrics Monitor (Aruba Central)" and "Aruba: Central Component Counts" are disabled by default for this version:

• Requests (avg)
• Latency-Maximum, Minimum, Average (avg)
• SLL and Connection Errors (avg)
• Timeout (avg)
• Total Components
• AP Count
• Switch Count
• Gateway Count

Additionally, the following widgets on the "Aruba: Central Controller" Device Dashboard included in the PowerPack will not display data:

• Total Requests sent from EM7 to Aruba Central
• Error Response Count (Errors received back from Aruba Central)
• Total Access Points
• Total Switches
• Total Gateways

• A non-numeric value API-response, for the "Aruba: Central Switch Performance" collection objects, generates too many system log entries. An error message reads “Non-digits in oid with object id: <object_id>, did: <device_id> in dynamic app: <app_id> when updating performance value (val:-)”. However, this does not affect data collection.
• Vitals metrics are displaying unusual labels for CPU and Memory Utilization metrics in the "Aruba: Central SD-WAN Gateway Performance" and "Aruba: Central Switch Performance" Dynamic Applications.
• An exception will be logged when the Embed Value [%4] field, in the credential, is left empty, contains a non-numeric value, or contains a value less than or equal to 0. SIGTERMS could be present on system logs as well.
• The performance and configuration Dynamic Applications cannot run more frequently than their associated discovery Dynamic Applications.
• By default, configuration Dynamic Applications are set to display "Last Collected" data if a poll is missed. If you would like for the most recent value to display, set "--values" for the "Null Column Option" property.
• A known issue might cause Dynamic Application debug mode to fail in the SL1 user interface. To troubleshoot Dynamic Applications in version 104, ScienceLogic recommends using the command line debug mode on the Data Collector.
• The error messages for a device, during data collection, will not display on Device Logs, but device error messages will print on log files.
• A known issue causes Dynamic Applications to display information on reports even if the user credential has an incorrect username and password when a session was previously generated with valid credentials. This behavior will continue until the refresh token expires.
• The tokens generated from the API Gateway UI in Aruba Central during SSO authentication are available for 15 days, and if not refreshed within that period, it will be revoked and all collection will stop. To restart collection, you must generate a new refresh token in Aruba Central and include it in the SOAP/XML credential (EmbedValue[%2]).