Aruba AirWave

Application Version and Upgrade Details

Introduction

AirWave is an API tool that collects and analyzes vast amounts of data from multiple network components, including access points, controllers, switches, and authentication sources. AirWave can provide this valuable information to other wireless applications, relegating the need for these applications to develop direct interfaces with these components.

Examples of wireless applications that would require AMP’s correlated information are RF scanning IDS solutions, RF scanning analysis solutions, and wireless site planning tools. The API uses Extensible Markup Language(XML) over HTTPS using session- based authentication. All HTTP parameters and form fields must be URL encoded.

With visibility into everything that affects wireless and mobility service-level agreements (SLAs), AirWave lets you proactively plan for capacity, visualize client performance and troubleshoot application issues before you get a help desk ticket.

With AirWave, your entire distributed enterprise – from campuses to branch offices around town and around the world – are easily and efficiently managed from a single pane of glass, making it easy to keep your SLAs on track.

Prerequisites

• OpsRamp Classic Gateway 14.0.0 and above.
• OpsRamp NextGen Gateway 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.
• Provided IpAddress/hostname, Credentials should work for AirWave API Integrations REST API’s.

Hierarchy of AirWave API resources

• AirWave Management Platform (AMP)
       - AirWave Access Points
       - AirWave Air Monitors
       - AirWave Remote Access Points
       - AirWave Virtual Controllers
       - AirWave Physical Controllers

Default Monitoring Configurations

Aruba AirWave has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends performing the below activity before installing the application to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of AirWave Management Platform. You can find those Device Management Policies at Setup > Resources > Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: aruba-airwave AirWave Management Platform - 1 (i.e, appName = aruba-airwave, nativeType =AirWave Management Platform, version = 1)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of AirWave Management Platform. You can find those templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: aruba-airwave AirWave Management Platform Template - 1 (i.e, appName = aruba-airwave, nativeType = AirWave Management Platform, version = 1)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find those monitors at Setup > Monitoring > Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: AirWave Management Platform Monitor aruba-airwave AirWave Management Platform 1 (i.e, monitorKey = AirWave Management Platform Monitor, appName = aruba-airwave, nativeType = AirWave Management Platform, version= 1)

Configure and Install the Aruba AirWave Integration

1. From All Clients, select a client.
2. Go to Setup > Account.
3. Select the Integrations and Apps tab.
4. The Installed Integrations page, where all the installed applications are displayed.
   Note: If there are no installed applications, it will navigate to the ADD APP page.
5. Click + ADD on the Installed Integrations page. The Available Integrations and Apps page displays all the available applications along with the newly created application with the version.
   Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.

6. Click ADD in the Aruba AirWave application.
7. In the Configuration page, click + ADD. The Add Configuration page appears.
8. Enter the below mentioned BASIC INFORMATION:

Notes:

• By default the Is Secure checkbox is selected.
• AirWave Ip Address/Host Name and AirWave API Port should be accessible from Gateway.
• Select the following:
  • App Failure Notifications: if enabled,
    • an alert will be sent to the registered gateway resource.
    • an alert is raised for connectivity, authentication exception,
      • Discovery - alert will be on a gateway resource that is registered with the application.
      • Monitoring - alert will be on a particular Powerflex resource.

9. Select the below mentioned CUSTOM ATTRIBUTES:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

10. In the RESOURCE TYPE section, select:
    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.
11. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
12. Click ADD.

Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.
13. Click NEXT.
14. Below are the optional steps you can perform on the Installation page.

• Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

  Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

• Click +ADD to create a new collector by providing a name or use the pre-populated name.

15. Select an existing registered profile.

16. Click FINISH.

The integration is installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed integration.

• See Modify an Installed Integration or Application article.

  Note: Select the Aruba AirWave application.

View the Aruba AirWave Details

The discovered resource(s) are displayed in Infrastructure > Resources > Network Device, with Native Resource Type as AirWave Access Points. You can navigate to the Attributes tab to view the discovery details, and the Metrics tab to view the metric details for Aruba AirWave.

View resource metrics

• Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
• Alerts: Alerts are generated for metrics that are configured as defined for integration.

Resource Type Filter Keys

Aruba Airwave application Resources are filtered and discovered based on below keys:

Supported Metrics

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
• Using metrics for monitoring the resources and generating alerts when the threshold values are breached.
• Application cannot control monitoring pause/resume actions based on above alerts.
• This application only supports Classic Gateway and NextGen Gateway.
• Not supported with Cluster Gateway.
• No support of showing activity logs.
• The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.