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
Rear Port → Delete
AI-generatedOverview
This node interacts with the NetBox API to delete a specific Rear Port resource within the DCIM domain. It is useful for automating the removal of rear port records in network infrastructure management workflows, such as cleaning up unused or obsolete hardware connections in NetBox.
Use Case Examples
- Deleting a rear port by specifying its ID to maintain accurate and up-to-date network device documentation.
- Automating the cleanup of rear port entries during device decommissioning processes.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the NetBox API to target, here it is set to 'dcim' for data center infrastructure management. |
| ID | The unique identifier of the Rear Port record to delete. |
Output
JSON
json- The JSON response from the NetBox API after attempting to delete the Rear Port resource, typically indicating success or failure.
Dependencies
- Requires an API key credential for authenticating with the NetBox API.
Troubleshooting
- Common issues include providing an invalid or non-existent Rear Port ID, which will result in an error from the NetBox API indicating the resource was not found.
- Authentication failures due to incorrect or missing API credentials will prevent the node from successfully deleting the resource.
- Network connectivity issues to the NetBox server can cause timeouts or connection errors.
Links
- NetBox API Documentation for Rear Ports - Official documentation for the Rear Ports resource in the NetBox API, useful for understanding the API endpoints and expected parameters.