Version 103 of the Aruba Central PowerPack includes updates toDynamic Applications, scale optimization, and enhancements to Aruba Central API request rate limitation.
- 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 103.
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 103 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.
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:
- Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
- In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
- Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
- Click and navigate to the PowerPack file from step 1.
- Select the PowerPack file and click . The PowerPack Installer modal displays a list of the PowerPack contents.
- Click . 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 Applications 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
Enhancements and Issues Addressed
The following enhancements and addressed issues are included in version 103 of the "Aruba Central" PowerPack:
-
The "silo_aruba_central" content library was updated to optimize PowerPack performance at scale by reducing payload.
-
Support for the Aruba Central API 7 calls per second request rate limitation was added to the PowerPack.
-
The "Aruba Central Example" credential was updated based on Snippet Framework (silo-auth) requirements.
-
The "silo_low_code" content library was added to support Snippet Framework.
-
An issue was addressed in which discovery Dynamic Applications were failing due to rate limitations.
-
An issue was addressed in which the "Aruba: Central Switch Discovery" configuration report was not displaying the model of switch devices.
-
The following content libraries were removed:
- silo_core
- silo_core_rest
- silo_credentials
-
The following Dynamic Applications were disabled by default:
- Aruba: Central Component Counts
- Aruba: Central Notifications
- REST: Performance Metrics Monitor (Aruba Central)
-
The following Dynamic Applications were updated to use the "silo_low_code" content library:
- Aruba: Central Switch Configuration
- Aruba: Central Switch Container Discovery
- Aruba: Central Switch Discovery
- Aruba: Central Switch Performance
- 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 AP Configuration
- Aruba: Central AP Container Discovery
- Aruba: Central AP Discovery
- Aruba: Central AP Performance
Several collection objects were removed from the PowerPack in version 101. These collection objects no longer function in version 103, as their underlying collection code has been removed. Therefore, if you are upgrading to version 103 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
Known Issues
The following known issues affect version 103 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.
- 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.
- 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 103, 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 when the user credential has an incorrect username and password. This behavior will continue until the refresh token expires.