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 → Get Paths
AI-generatedOverview
This node interacts with the NetBox API to retrieve path information related to a specific Rear Port resource within the DCIM domain. It is useful for network administrators or engineers who need to trace or analyze the connectivity paths of rear ports in their infrastructure. For example, it can be used to get detailed path data for troubleshooting or documentation purposes.
Use Case Examples
- Retrieve the connectivity paths of a rear port by specifying its ID in the DCIM domain to understand how devices are interconnected.
- Use the node to fetch path details for a rear port to assist in network audits or infrastructure mapping.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the NetBox API to interact with, here it is set to 'dcim' for data center infrastructure management. |
| ID | The unique identifier of the Rear Port resource for which the paths are to be retrieved. |
Output
JSON
json- The JSON response from the NetBox API containing the paths information related to the specified Rear Port.
Dependencies
- NetBox API with appropriate credentials
Troubleshooting
- Common issues include invalid or missing Rear Port ID, resulting in API errors or empty responses.
- API authentication failures due to incorrect or missing credentials.
- Network connectivity issues preventing access to the NetBox API endpoint.