NetBox icon

NetBox

Consume NetBox API

Actions243

Cable → Update

AI-generated

Overview

This node interacts with the NetBox API to update cable records within the DCIM domain. It allows users to modify various attributes of a cable, such as its terminations, type, status, label, color, length, tenant association, description, tags, and custom fields. This is useful in network management scenarios where cable details need to be kept current, for example, updating the physical type of a cable or changing its operational status after maintenance.

Use Case Examples

  1. Updating the physical type of a cable from CAT5e to CAT6 after replacement.
  2. Changing the status of a cable to 'decommissioning' when it is being retired.
  3. Adding or modifying the label and color of a cable for easier identification in documentation.

Properties

Name Meaning
Domain Specifies the domain of the NetBox API to use, here it is 'dcim' for data center infrastructure management.
Cable ID The unique identifier of the cable record to update.
Update Fields A collection of fields to update on the cable record, including terminations, type, status, label, color, length, tenant, description, tags, and custom fields.

Output

JSON

  • id - The unique identifier of the updated cable record.
  • type - The physical type of the cable after update.
  • status - The operational status of the cable after update.
  • label - The physical label of the cable after update.
  • color - The color of the cable after update.
  • length - The length of the cable after update.
  • length_unit - The unit of measurement for the cable length after update.
  • tenant - The tenant ID associated with the cable after update.
  • description - The description of the cable after update.
  • tags - Tags associated with the cable after update.
  • custom_fields - Custom fields data of the cable after update.

Dependencies

  • NetBox API with appropriate API key credentials

Troubleshooting

  • Ensure the Cable ID provided exists in the NetBox instance; otherwise, the update will fail with a not found error.
  • Validate JSON format for A Terminations and B Terminations fields to avoid parsing errors.
  • Check that the API credentials have sufficient permissions to update cable records.
  • If the node throws an error, enabling 'Continue on Fail' will allow the workflow to proceed and output the error message as JSON.

Links

Discussion