Aruba Central icon

Aruba Central

Interact with the Aruba Central API

Actions95

Mobility Controller → Get Mobility_controllers

AI-generated

Overview

This node interacts with the Aruba Central API to retrieve information about Mobility Controllers within the specified domain, particularly under the 'monitoring' domain. It allows users to fetch details such as status, MAC address, model, firmware version, labels, AP count, and usage of Mobility Controllers. This is useful for network administrators who want to monitor and manage their network devices efficiently.

Use Case Examples

  1. A network admin wants to get a list of all Mobility Controllers currently active in the network to check their status and firmware versions.
  2. Fetching Mobility Controller details filtered by model or MAC address to troubleshoot specific devices.
  3. Retrieving a limited number of Mobility Controllers with sorting options to display in a dashboard.

Properties

Name Meaning
Domain Specifies the domain of the Aruba Central API to interact with, defaulting to 'monitoring' for Mobility Controllers.
Return All Determines whether to return all Mobility Controller results or limit the number of results returned.
Limit Maximum number of Mobility Controller results to return when 'Return All' is false.
Additional Fields Optional filters and parameters to refine the Mobility Controller query, such as status, MAC address, model, fields to return, whether to calculate total controllers, and sorting options.

Output

JSON

  • status - Status of the Mobility Controller
  • ip_address - IP address of the Mobility Controller
  • model - Model of the Mobility Controller
  • firmware_version - Firmware version running on the Mobility Controller
  • labels - Labels assigned to the Mobility Controller
  • ap_count - Number of access points managed by the Mobility Controller
  • usage - Usage statistics of the Mobility Controller

Dependencies

  • Aruba Central API with OAuth2 authentication

Troubleshooting

  • Ensure the OAuth2 API credentials are correctly configured and have the necessary permissions to access the Mobility Controller data.
  • If the node returns an error related to limits, check the 'Return All' and 'Limit' settings to ensure they are set appropriately.
  • Filtering parameters in 'Additional Fields' must be valid and correctly formatted; invalid filters may cause the API to reject the request.

Discussion