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 → Create
AI-generatedOverview
This node interacts with the NetBox API to create a Virtual Link resource within the DCIM domain. It is useful for network administrators and engineers who want to automate the creation of virtual links between interfaces in their network infrastructure. For example, it can be used to programmatically link two network interfaces by specifying their IDs and additional optional details such as status, tenant, description, tags, and custom fields.
Use Case Examples
- Creating a virtual link between two interfaces in a data center to represent a logical connection.
- Automating network documentation by adding virtual links with metadata like status and tenant information.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the NetBox API to use, here it is set to 'dcim' for data center infrastructure management. |
| Interface A ID | The ID of the first interface to be linked. |
| Interface B ID | The ID of the second interface to be linked. |
| Additional Fields | Optional additional fields to provide more details about the virtual link. |
Output
JSON
id- The unique identifier of the created virtual link.interface_a_id- The ID of the first interface in the created virtual link.interface_b_id- The ID of the second interface in the created virtual link.status- The status of the virtual link.tenant- The tenant associated with the virtual link.description- Description of the virtual link.tags- Tags associated with the virtual link.custom_fields- Custom fields metadata of the virtual link.
Dependencies
- NetBox API
- An API key credential for authentication
Troubleshooting
- Ensure the Interface A ID and Interface B ID are valid and exist in the NetBox instance.
- Verify that the API key credential is correctly configured and has permissions to create virtual links.
- Check that the domain is set to 'dcim' as the virtual link resource is under this domain.
- Common error messages may include authentication errors, invalid interface IDs, or missing required fields. Resolving these involves verifying credentials, input values, and required parameters.
Links
- NetBox API Documentation for Virtual Links - Official documentation for the Virtual Link resource in the NetBox API.