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
Client → Get Client Count
AI-generatedOverview
This node interacts with the Aruba Central API to retrieve the count of clients based on specified filters within the Monitoring domain. It is useful for network administrators who want to monitor client counts on their network devices, such as Access Points (APs) or switches, filtered by various parameters like device type, serial number, band, and radio number.
Use Case Examples
- A network admin wants to get the total number of clients connected to a specific AP identified by its serial number and band.
- Filtering client counts by device type (AP or Switch) to analyze network usage patterns.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the Aruba Central API to use, e.g., Monitoring, Configuration, Firmware, etc. |
| Additional Fields | Optional filters to refine the client count query, including cluster ID, stack ID, device type, serial number, band, and radio number. |
Output
JSON
count- The total number of clients matching the specified filters.
Dependencies
- Aruba Central API with OAuth2 authentication
Troubleshooting
- Ensure the OAuth2 credentials for Aruba Central API are correctly configured and valid.
- Verify that the domain is set to 'monitoring' when using the Get Client Count operation, as other domains may not support this operation.
- Check that filter values such as serial number, band, and device type are valid and correctly formatted.
- If the node throws an error, enabling 'continueOnFail' allows the workflow to proceed with error details in the output.