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 → Initiate Client Steer
AI-generatedOverview
This node interacts with the Aruba Central API to initiate client steering on an Access Point (AP). It is used to steer a client device from one AP to another, which can help optimize network performance and client distribution. Common scenarios include managing Wi-Fi client connections in enterprise networks to improve signal quality and load balancing.
Use Case Examples
- Steer a client device to a different AP to improve signal strength.
- Manage client connections dynamically in a large Wi-Fi deployment to balance network load.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the Aruba Central API to use, such as monitoring or configuration. |
| Serial | Serial Number of the AP to initiate client steering from. Note that this is an undocumented API and may not be available on all clusters or APs. |
| Client MAC | MAC address of the client device to steer. |
| Target AP | Serial number of the target AP to steer the client to. |
Output
JSON
success- Indicates whether the client steering operation was successful.message- Additional information or status message about the client steering operation.
Dependencies
- Requires Aruba Central API access with OAuth2 authentication.
Troubleshooting
- If the API is undocumented or unavailable on certain APs or clusters, the operation may fail or return errors.
- Ensure the serial numbers and client MAC address are correct and valid to avoid errors.
- Common error messages may include authentication failures, invalid parameters, or unsupported operations on the target AP.