Aruba Central icon

Aruba Central

Interact with the Aruba Central API

Actions95

Client → Get Client Mobility Trail

AI-generated

Overview

This node interacts with the Aruba Central API to retrieve the mobility trail of a wireless client based on its MAC address within the monitoring domain. It is useful for network administrators who want to track the movement and transitions of a client device across the network over a specified time period. For example, it can be used to analyze client connectivity patterns, troubleshoot roaming issues, or monitor client behavior in a wireless network environment.

Use Case Examples

  1. Retrieve the mobility trail of a specific client device by providing its MAC address to understand its movement across access points.
  2. Use pagination options to fetch mobility data in chunks for large datasets.
  3. Calculate total transitions of the client between access points over a given time range.

Properties

Name Meaning
Domain Specifies the domain of the Aruba Central API to use, such as monitoring, inventory, or configuration. For this operation, it defaults to 'monitoring'.
MAC Address The MAC address of the wireless client whose mobility trail is to be retrieved.
Additional Fields Optional parameters to customize the request, including whether to calculate total transitions, pagination offset and limit, and time range (from and to timestamps) for the mobility data.

Output

JSON

  • clientMobilityTrail - Array of mobility trail records for the specified client, detailing its movement across the network.

Dependencies

  • Aruba Central API with OAuth2 authentication

Troubleshooting

  • Ensure the MAC address is correctly formatted and valid; invalid MAC addresses may cause errors.
  • Verify that the OAuth2 credentials for Aruba Central API are correctly configured and have sufficient permissions.
  • Check the domain parameter is set to 'monitoring' for this operation; other domains may not support this operation.
  • If pagination parameters (offset, limit) are used, ensure they are within valid ranges to avoid empty or partial results.
  • Timestamp parameters should be valid epoch seconds; incorrect values may result in no data or errors.

Discussion