NetBox icon

NetBox

Consume NetBox API

Actions243

Console Server Port → List

AI-generated

Overview

This node interacts with the NetBox API to list console server ports within the DCIM domain. It is useful for retrieving detailed information about console server ports in a network infrastructure managed by NetBox, allowing users to filter and limit the results based on various criteria.

Use Case Examples

  1. A network administrator wants to retrieve all console server ports associated with a specific device or module.
  2. A user needs to search for console server ports by name or label to audit or manage network equipment connections.

Properties

Name Meaning
Domain Specifies the domain of the NetBox API to use, here it is set to 'dcim' for data center infrastructure management.
Return All Determines whether to return all results or limit the number of results returned.
Limit Maximum number of console server port results to return when 'Return All' is false.
Filters Collection of filters to narrow down the list of console server ports based on various attributes such as ID, device ID, module ID, name, label, type, speed, connection status, ordering, and creation or update timestamps.

Output

JSON

  • id - Unique identifier of the console server port.
  • device_id - Identifier of the device associated with the console server port.
  • module_id - Identifier of the module associated with the console server port.
  • name - Name of the console server port.
  • label - Label assigned to the console server port.
  • type - Type of the console server port (e.g., DE-9, DB-25, RJ-45, USB types).
  • speed - Baud rate speed of the console server port.
  • mark_connected - Boolean flag indicating if the port is marked as connected.
  • created - Timestamp when the console server port was created.
  • last_updated - Timestamp when the console server port was last updated.

Dependencies

  • NetBox API
  • API key credential for authentication

Troubleshooting

  • Common issues include authentication failures due to invalid or missing API credentials. Ensure the API key credential is correctly configured.
  • Incorrect filter values or unsupported filter fields may result in empty or error responses. Verify filter parameters against NetBox API documentation.
  • Network connectivity issues to the NetBox server can cause request failures. Check network access and server availability.
  • If the node throws errors, enabling 'Continue on Fail' allows the workflow to proceed and outputs the error message for debugging.

Links

Discussion