Actions243
- Cable Actions
- Cable Termination Actions
- Connected Device Actions
- Console Port Actions
- Console Port Template Actions
- Console Server Port Actions
- Console Server Port Template Actions
- Device Actions
- Device Bay Actions
- Device Bay Template Actions
- Device Role Actions
- Device Type Actions
- Front Port Actions
- Front Port Template Actions
- Interface Actions
- Interface Template Actions
- Inventory Item Actions
- Inventory Item Role Actions
- Inventory Item Template Actions
- Location Actions
- MAC Address Actions
- Manufacturer Actions
- Module Actions
- Module Bay Actions
- Module Bay Template Actions
- Module Type Actions
- Module Type Profile Actions
- Platform Actions
- Power Feed Actions
- Power Outlet Actions
- Power Outlet Template Actions
- Power Panel Actions
- Power Port Actions
- Power Port Template Actions
- Rack Actions
- Rack Reservation Actions
- Rack Role Actions
- Rack Type Actions
- Rear Port Actions
- Rear Port Template Actions
- Region Actions
- Site Actions
- Site Group Actions
- Virtual Chassis Actions
- Virtual Device Context Actions
- Virtual Link Actions
Virtual Link → Update
AI-generatedOverview
This node updates a Virtual Link resource in the NetBox API within the DCIM domain. It is useful for network administrators or automation engineers who need to programmatically modify virtual link details such as interface IDs, status, tenant association, description, tags, and custom fields. For example, it can be used to update the status of a virtual link from 'planned' to 'active' or to assign a tenant ID to a virtual link.
Use Case Examples
- Updating the status and description of a virtual link identified by its ID.
- Assigning a tenant ID and adding tags to a virtual link.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the NetBox API to use, here it is 'dcim' for Data Center Infrastructure Management. |
| ID | The unique identifier of the virtual link to update. |
| Update Fields | A collection of fields to update on the virtual link, including Interface A ID, Interface B ID, Status, Tenant ID, Description, Tags, and Custom Fields in JSON format. |
Output
JSON
id- The unique identifier of the updated virtual link.interface_a- ID of the first interface in the updated virtual link.interface_b- ID of the second interface in the updated virtual link.status- The updated status of the virtual link.tenant- The tenant ID associated with the updated virtual link.description- The updated description of the virtual link.tags- Tags associated with the updated virtual link.custom_fields- Custom fields data of the updated virtual link.
Dependencies
- NetBox API with appropriate credentials for authentication
Troubleshooting
- Common issues include providing an invalid virtual link ID, which results in a 'not found' error from the API.
- Incorrectly formatted custom fields JSON can cause update failures.
- Lack of proper API credentials or permissions will result in authentication or authorization errors.
Links
- NetBox API Documentation for Virtual Links - Official documentation for managing virtual links via the NetBox API.