network Integration
aruba-wireless-controller (en)


ServicePilot network-aruba-wireless-controller


# Aruba Wireless Controller

Overview

This package monitors Aruba Wireless Controller using SNMP.

Description

This package automatically configures the ServicePilot Manager to collect statistics from the Aruba Wireless Controller in terms of CPU, Memory, Storages, interfaces, Licences and Access Points based on an SNMP collection.

Requirements

  • SNMP service must be configured and started on the targeted Aruba Wireless Controller (Security: read-only SNMP community and allowed host must be set).

  • Network Flows - It is is necessary to ensure network connectivity between ServicePilot and the monitored device. In case of a network infrastructure using a firewall, all the ports below must be opened:

    • UDP/161 (SNMP): Between ServicePilot Manager and Aruba Wireless Controller
    • ICMP/Echo Request (Ping): Between ServicePilot Manager and Aruba Wireless Controller
    • UDP/162 (SNMP Trap): (Optional) Between Aruba Wireless Controller and ServicePilot Agent
  • ServicePilot Requirements

    • ServicePilot Manager minimum version: 8.5

Installation

Before adding a resource to monitor, make certain that all pre-requisites are in place and if a ServicePilot Agent is required, that it is communicating correctly with the ServicePilot Manager. Resources can be added to ServicePilot configuration in a number of ways:

Add resource using Views Configuration web interface

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration. The Configuration > Views web page will open.
  3. Click on the view in which to place the new resource in the Views hierarchy on the left of the interface. The View editor section will show the existing view contents.
  4. From the Packages list on the right of the interface, click and drag the network-aruba-wireless-controller package into the View editor and let go.
  5. The Package properties dialog box will open to allow resource configuration.
  6. Click OK to close the Package properties dialog box. Note that the dialog box will not close if required parameters are not set.
  7. Click Save to apply the new resource to ServicePilot configuration.

Add resource by changing servicepilot.conf configuration file

Resources can be added to ServicePilot configuration by directly editing the servicepilot.conf or other included YAML configuration files. The ServicePilot web interface can be used to make these changes and apply them to the running configuration.

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration.
  3. Navigate to Configuration > Edit configuration.
  4. Expand the configuration to find the provisioning: and then packages: section of the view in which the new resource will be placed.
  5. Add the example package configuration line below.
  6. Click on the green - package: word to open then Package properties dialog box to allow resource configuration.
  7. Click OK to close the Package properties dialog box. Note that the dialog box will not close if required parameters are not set.
  8. Click Save to apply the new resource to ServicePilot configuration.

Example:

- package: "network-aruba-wireless-controller;;;;;;;;network-aruba-wireless-controller;;127.0.0.1;Y;Y;*vlan*;;;Y;Y;Y;Y;Y;Y;N;N;;"

Key field notes

In the Monitoring Policies tab, specify the policy or policies to apply to the package

  1. Basic Parameters tab:

    1. IP address: Specify the IP address of the Aruba Wireless Controller as resolvable by the machine on which ServicePilot Manager is running
  2. Interfaces tab:

    1. Auto-Discover Interfaces: tick to get details about interfaces.
    2. Use Interface filter instead of Addressing Information: tick to get statistics for a specified list on interfaces only. Set it off to get statistics for all available interfaces
    3. {Optional} Ignored Interfaces names separated with '|': Specify name(s) of interface(s) NOT to be monitored
    4. {Optional} Allowed Interfaces names separated with '|': Specify name(s) of interface(s) to be monitored
    5. {Optional} Custom interface speed separated with '|': Specify maximum speed of interface
  3. Monitoring Options tab:

    1. CPU Performance: tick to get CPU Utilization
    2. Memory Usage: tick to get memory Utilization
    3. Temperature: tick to get temperature statistics
    4. Fans: tick to get fan activity
    5. Power Supplies: tick to power supply activity
    6. Storage Usage: tick to get statistics for all Storage Units
    7. Licenses: tick to get statistics for all Licences
  4. Access Point Detail tab:

    1. Access Point Details: tick to enable Access Point detail collecction
    2. {Optional} Include IP Address,ESSID,Physical Layer Protocol filter separated with '|': If specified only include Access Point information for the described IP Addresses, ESSIDs and Physical Layer Protocol specified. Each element of the list is pipe (|) separated while each item consists of three items that are comma (,) separated.
    3. {Optional} Include BSSID filter separated with '|': If specified only include Access Point information for the selected BSSIDs. The list is pipe (|) separated.

Note: Each element of the ignored/allowed interface and Access Points lists is a regular expression as defined by Like Operator (Visual Basic)

Notes

MIBs Used:

  • ARUBA-MIB
  • WLSX Mibs
  • RFC1213-MIB2.mib
network aruba-wireless-controller 0

network aruba-wireless-controller 1

network aruba-wireless-controller 2