Aruba Central PowerPack Release Notes, version 200

Version 200 of the Aruba Central PowerPack adds proxy support to the PowerPack, updates the structure of the Dynamic Component Map tree, and updates the template included in this PowerPack to accommodate changes to the list of Dynamic Applications that align to the virtual root device.

• Minimum Required SL1 Version: 11.3.0

Before You Install or Upgrade

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

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

If you are currently using a version prior to 103 of this PowerPack, a direct upgrade to version 200 is not supported and a fresh install and re-discovery of devices may be required with version 200. Versions 103, 104, and 104.1 can be upgraded directly to version 200 if there is only one DCM tree discovered per Aruba Central account. If separate API keys are being used to discover sites individually as their own DCM tree, a fresh install and re-discovery is also required. 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.

After upgrading the PowerPack to version 200, follow the steps below:

1. Disable the listed Dynamic Applications.

   • Aruba: Central AP Container Discovery

   • Aruba: Central SD-WAN Gateway Container Discovery

   • Aruba: Central Switch Container Discovery

For instructions on disabling Dynamic Applications, see the section on "Performing Other Tasks in the Dynamic Application Manager Page " in the Dynamic Application Development manual.

2. Disable the listed container device components.

   • AP Container

   • SD-WAN Gateway Container

   • Switch Container

3. Apply the new Aruba template included in this version of the PowerPack to the root virtual device. This will cause devices to move from the container component devices to sites.

For instructions on applying a template, see the see the "Aligning the Device Template to Your Aruba Central Virtual Device" section in the Monitoring Aruba Central manual.

4. Once all components have been migrated to sites, remove the empty container device components listed in step 2.

5. Delete the disabled Dynamic Applications listed in step 1.

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 structure of the Dynamic Component Map tree created by this PowerPack. Previously, the component tree consisted of a virtual device with three device type-specific containers underneath (APs, SD-WAN Gateways, Switches). The new DCM tree groups devices by site instead of device type. Each site is modeled as a separate container, and all devices belonging to a site are discovered as its child components.

Devices that are not assigned to a site will not be discovered in SL1.

• Updated the template included in this PowerPack to accommodate changes to the list of Dynamic Applications that align to the virtual root device.
• Added proxy support to the PowerPack. For more information, see the section on "Configuring Aruba Central Credentials" in the Monitoring Aruba Central manual.

Known Issues

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

• The "Aruba: Central AP Discovery" Dynamic Application will be disabled after install of version 200 of this PowerPack regardless of the PowerPack Field Protection setting for this Dynamic Application.
• An additional "Aruba Central Example" and/or "Aruba Central SSO Example" credential may be created when upgrading to version 200 from a version prior to version 104.1.
• 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)" is 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.
• 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]).