Introduction

This section describes how to monitor Aruba Central in SL1 using the "Aruba Central" PowerPack.

What is Aruba Central?

Aruba Central is a cloud-based platform that provides management tools and built-in analytics for Aruba Instant Access Points (IAPs), switches, and gateways. In each Aruba network, one IAP acts as a virtual controller, which is a single configuration and management point for the network.

What Does the Aruba Central PowerPack Monitor?

To monitor Aruba Central using SL1, you must install the "Aruba Central" PowerPack. This PowerPack enables you to discover, model, and collect data about Aruba Central virtual controllers and their components.

The "Aruba Central" PowerPack includes:

• Dynamic Applications to discover and monitor Aruba Central virtual controllers and their component devices

• Device Classes for each of the Aruba Central components that the "Aruba Central" PowerPack can monitor
• Event Policies that are triggered when Aruba Central component devices meet certain status criteria
• Two samples of SOAP/XML Credential that you can use to create your own Aruba Central Credential
• A Device Template that aligns Dynamic Applications to the Aruba Central virtual controller and enables you to discover component devices for that virtual controller
• Device Dashboards that display information about Aruba Central component devices

Installing the Aruba Central PowerPack

Before completing the steps in this section, you must import and install the latest version of the "Aruba Central" PowerPack.

By default, installing a new version of a PowerPack overwrites all content from a previous version of 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 new PowerPacks from overwriting local changes for some commonly customized fields. For more information, see the section on Global Settings.

Ensure that you are running version 12.1.2 or later of SL1 before installing this PowerPack. For details on upgrading SL1, see the relevant SL1 Platform Release Notes.

To download and install the 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 button and choose Import PowerPack. The Import PowerPack dialog box 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 PowerPacks page.

If you exit the PowerPack Installer modal without installing the imported PowerPack, the imported PowerPack will not appear in the PowerPacks page. However, the imported PowerPack will appear in the Imported PowerPacks modal. This page appears when you click the Actions menu and select Install PowerPack.

If you are currently using a version prior to 103 of this PowerPack, a direct upgrade to version 200.2 is not supported and a fresh install and re-discovery of devices may be required with version 200.2. 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. Follow those procedures to ensure accurate data collection post upgrade. After upgrading to version 200, you can upgrade to version 200.2

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

The steps below are only needed if you aren't currently running version 200 or newer.

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.

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.

To ensure accurate data collection after upgrading PowerPack from any of the previous versions, perform the additional steps to authenticate using Oauth Grant Mechanism:

1. Go to the Credential Management page (System > Manage > Credentials). Identify your current credential and click on the credential’s name to edit.
2. In the Embed Password [%P] field, type your Aruba Central client secret key.
3. In the Embed Value [%1] field, type "AuthOauth2".
4. In the Embed Value [%2] field, type your Aruba Central customer ID.
5. In the Embed Value [%3] field, type your Aruba Central client ID.
6. In the Embed Value [%4] field, set a page size between 1 and 1000.
7. Remove all HTTP Headers.
8. Remove any CURL Option and set the SSLVERIFYPEER Curl Option to 0 as the value and click Save.

To authenticate using the Offline Token Mechanism:

1. Go to theCredential Management page (System > Manage > Credentials). Identify your current credential and click on the credential’s name to edit.
2. In the Embed Password [%P] field, type your Aruba Central client secret key.
3. In the Embed Value [%1] field, type "OfflineToken".
4. In the Embed Value [%2] field, type the refresh token.
5. In the Embed Value [%3] field, type your Aruba Central client ID.
6. In the Embed Value [%4] field, set a page size between 1 and 1000.
7. Remove all HTTP Headers.
8. Remove any CURL Option and set the SSLVERIFYPEER Curl Option to 0 as the value and click Save.