Actions95
- Access Point Actions
- Client Actions
- Events Actions
- Gateway Actions
- Label Actions
- Mobility Controller Actions
- Network Actions
- Site Actions
- Swarm Actions
- Switch Actions
- List Switches
- Get VLAN Info of the Switch
- Get VLAN Info for CX Switch
- Get VLAN Info of the Switch Stack
- Get VLAN Info of the CX Switch Stack
- Get Switch Port PoE Info
- Get Switch Port PoE Info for CX Switch
- Get Switch PoE Info
- Get Switch PoE Info for CX Switch
- Get Switch VSX Info for CX Switch
- Get LLDP Device Neighbor Info for CX Switch
- Get LLDP Device Neighbor Info for CX Switch Stack
- Switch Bandwidth Usage
- Top N Switches
- Switch Details
- Delete Switch
- Switch Ports Details
- Get Ports Details for CX Switch
- Switch Chassis Details
- Switch Ports Bandwidth Usage
- Ports Bandwidth Usage for CX Switch
- Switch Ports Errors
- CX Switch Ports Errors
- Switch Stack Port Details
- CX Switch Stack Port Details
- List Switch Stacks
- Switch Stack Details
- Delete Switch Stack
- VPN Actions
Access Point → Get Client Match Steer History
AI-generatedOverview
This node interacts with the Aruba Central API to retrieve the client steering history for a specific Access Point (AP). It is useful for network administrators who want to monitor and analyze client steering events on their APs, particularly for troubleshooting or performance optimization. For example, an admin can specify the AP's serial number and a time range to get detailed steering history data.
Use Case Examples
- Retrieve client steering history for an AP with serial number '12345' from a specific start timestamp to an end timestamp to analyze client behavior and network performance.
- Monitor client steering events on an AP to troubleshoot connectivity issues or optimize network load balancing.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the Aruba Central API to use, such as monitoring, configuration, or firmware. For this operation, the domain is 'monitoring'. |
| Serial | The serial number of the Access Point to get client steering history for. This is required and specific to the AP being queried. Note that this API is undocumented and may not be available on all clusters or APs. |
| From Timestamp | The start time for the steering history query, specified as an epoch timestamp. |
| To Timestamp | The end time for the steering history query, specified as an epoch timestamp. |
Output
JSON
clientSteerHistory- Array of client steering history records retrieved from the Aruba Central API for the specified AP and time range.
Dependencies
- Aruba Central API with OAuth2 authentication
Troubleshooting
- If the node returns an error indicating the API is unavailable, verify that the AP serial number is correct and that the API is supported on the cluster or AP, as this is an undocumented API and may not be available everywhere.
- Ensure that the OAuth2 credentials for Aruba Central API are correctly configured and have the necessary permissions to access monitoring data.
- If timestamps are not provided or are invalid, the API may return incomplete or no data. Verify that 'From Timestamp' and 'To Timestamp' are valid epoch timestamps.
Links
- Aruba Central API Documentation - Official documentation for Aruba Central APIs, useful for understanding available endpoints and parameters.