Aruba Central icon

Aruba Central

Interact with the Aruba Central API

Actions95

Mobility Controller → Get Ports

AI-generated

Overview

This node interacts with the Aruba Central API to retrieve port information from a specified Mobility Controller device. It is useful for network administrators who need to monitor or manage the ports on their Aruba Mobility Controllers, such as checking port status, configurations, or troubleshooting connectivity issues.

Use Case Examples

  1. A network admin wants to get a list of all ports on a specific Mobility Controller to verify which ports are active.
  2. Retrieving port details to audit network device connections and ensure compliance with network policies.

Properties

Name Meaning
Domain Specifies the domain of the Aruba Central API to use, such as monitoring, configuration, or inventory. For this operation, the domain is typically 'monitoring'.
Return All Determines whether to return all port results or limit the number of results returned. Only applicable when domain is 'monitoring' and operation is 'getPorts'.
Limit Maximum number of port results to return when 'Return All' is false. Must be at least 1. Only shown when 'Return All' is false.
Serial The serial number of the Mobility Controller device to query for port information.

Output

JSON

  • portId - Unique identifier of the port.
  • portName - Name of the port.
  • status - Current status of the port (e.g., up, down).
  • speed - Speed of the port connection.
  • type - Type of the port (e.g., Ethernet, fiber).
  • macAddress - MAC address associated with the port.
  • description - Description or label of the port.

Dependencies

  • Aruba Central API with OAuth2 authentication

Troubleshooting

  • Ensure the serial number provided is correct and corresponds to an existing Mobility Controller device in Aruba Central.
  • Verify that the OAuth2 credentials for Aruba Central API are valid and have sufficient permissions to access monitoring data.
  • If the node returns an error about limits or pagination, check the 'Return All' and 'Limit' settings to ensure they are configured properly.
  • Network connectivity issues between n8n and Aruba Central API can cause failures; verify network access and API endpoint availability.

Links

Discussion