Aruba Central PowerPack Release Notes, version 102

Version 102 of the Aruba Central PowerPack introduces enhancements to API monitoring and data collection.

  • 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 102.

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

A fresh installation of version 102 is highly recommended for this PowerPack as opposed to upgrading from the version 100. However, for those wishing to upgrade regardless, a list of steps can be found below, and in the manual, that explains how to ensure accurate data collection after the 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.

If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.

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.

To ensure accurate data collection after upgrading the PowerPack from version 100 , perform the additional steps:

  1. Go to the Credential Management page (System > Manage > Credentials). Identify your current credential and click on the credential’s name to edit.

    Add the following HTTP headers:
    login_url=oauth2/authorize/central/api/login
    auth_url=oauth2/authorize/central/api
    token_url=oauth2/token
    grant_type=authorization_code
    rest_api=aruba

    Update the first HTTP header with:
    %oauth2=Authorization:Bearer

  2. Add SSLCERT Curl Option and set the value as False.

  3. Change the Setting Client Secret Key from Embed Value [%3] to Embedded Password [%P].

  4. Set a page size between 1 and 1000 for the Embed Value [%3] field and click Save.

  5. Go to the Device Manager page (Devices > Device Manager). Identify the Aruba Central virtual root device and click the Device Properties icon.

  6. In the Collections tab, select the Actions menu and click the Add Dynamic Application button.

  7. Select the "REST: Performance Metrics Monitor (Aruba Central)" Dynamic Application with the current credential and click Save. To avoid seeing data collected on the old "REST: Performance Metrics Monitor" Dynamic Application report, disable the Dynamic Application's collection entirely. This allows only the new REST Dynamic Application to collect data.
    To disable the collection for the old Dynamic Application:

    1. Check the "REST: Performance Metrics Monitor" Dynamic Application and select Disable All Collection Objects from the Action menu.

    2. Click the Go button. You can also choose Stop Collecting and Remove Data to cease the collection of historical data.

Confirm there are no spaces in the following header name: Content-Type:application/json

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

Features

This release includes the following features:

  • Dynamic Applications to discover and monitor Aruba Central component devices:
    • Aruba Central AP Configuration
    • Aruba Central AP Container Discovery
    • Aruba Central AP Discovery
    • Aruba Central AP Performance
    • Aruba Central Component Counts
    • Aruba Central Notifications
    • Aruba Central SD-WAN Gateway Configuration
    • Aruba Central SD-WAN Gateway Container Discovery
    • Aruba Central SD-WAN Gateway Discovery
    • Aruba Central SD-WAN Gateway Performance
    • Aruba Central Switch Configuration
    • Aruba Central Switch Container Discovery
    • Aruba Central Switch Discovery
    • Aruba Central Switch Performance
    • REST: Performance Metrics Monitor (Aruba Central)
  • 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:
    • Aruba: Central Controller
    • Aruba: AP Container
    • Aruba: AP
    • Aruba: Gateway Container
    • Aruba: Gateway
    • Aruba: Switch Container
    • Aruba: Switch

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in version 102 of the "Aruba Central" PowerPack:

  • Due to the deprecation of the Mobility Controllers API v1, the collection objects for the following Dynamic Applications now use the Gateways API v1:
  • Aruba: Central SD-WAN Gateway Performance
  • Aruba: Central SD-WAN Gateway Discovery
  • Aruba: Central SD-WAN Gateway Configuration
  • Aruba: Central Component Counts
  • Due to the deprecation of the Aruba Central API v1, the collection objects for the following dynamic applications now use the Aruba Central API v2:
  • Aruba: Central AP Performance
  • Aruba: Central AP Discovery
  • Aruba: Central AP Configuration
  • Aruba: Central Component Counts
  • Updated the silo_apps content library to share the in-memory cache between Dynamic Applications as long as they are running in the same process

  • Corrected content issues and other inconsistencies, including incorrect copyright dates and data units.

Several collection objects were removed from the PowerPack in version 101. These collection objects no longer function in version 102, as their underlying collection code has been removed. Therefore, if you are upgrading to version 102 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 102 of the Aruba Central PowerPack:

 

  • Due to the removal of the "REST: Performance Metrics Monitor" Dynamic Application, the following widgets for the "Aruba: Central Controller" SL1 Dashboard contained on Aruba: SL1 Dashboards v102 PowerPack will not display data:
  • Requests (avg)
  • Latency-Maximum, Minimum, Average (avg)
  • SLL and Connection Errors (avg)
  • Timeout (avg)

Additionally, the following widgets on the "Aruba: CentralController" 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

You must use the metrics of the "REST: Performance Metrics Monitor (Aruba Central)" Dynamic Application instead.

  • Data for the "Total Requests Sent From EM7 to Aruba Central" and "Error Response Count (Errors Received back from Aruba Central)" widgets is missing from the Aruba: Central Controller device dashboard.
  • 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.
  • The "REST: Performance Metrics Monitor (Aruba Central)" Dynamic Application values are not consistent with the Performance Report data when a user hovers their selection tool over the desired data point. The data point's value is different than the HTML Report's data.
  • An exception will be logged when the Embed Value [%3] field, in the credential, is left empty or contains a non-numeric value.
  • Time gaps may be present in the Performance Dynamic Applications after upgrading the PowerPack. If so, increase the Timeout seconds from 2 to 4 (or 5); but no more than that.