Actions9
Overview
This node enables interaction with Juniper network devices using the NETCONF protocol over SSH. It supports a variety of operations to retrieve configuration and status information, modify interface rate limits, and check for uncommitted changes on Juniper devices.
A common use case is automating network management tasks such as fetching firewall policers, interface details, routing protocol statuses, or applying/removing rate limits on interfaces. For example, a network engineer can use this node to programmatically retrieve all configured firewall policers from a Juniper device or to set bandwidth limits on specific interfaces without manual CLI access.
Properties
| Name | Meaning |
|---|---|
| Host | The hostname or IP address of the Juniper device to connect to. |
| Port | The port number for NETCONF over SSH connection (default is 830). |
| Include Raw XML | Whether to include the raw XML response in the output for debugging purposes. |
Note: The "Include Raw XML" property applies specifically when performing the "Get Firewall Policers" operation.
Output
The node outputs JSON data parsed from the XML response returned by the Juniper device. The structure depends on the operation performed but generally contains detailed configuration or status information corresponding to the requested data.
If the "Include Raw XML" option is enabled, the raw XML response from the device is also included in the output under the rawXml field for troubleshooting or inspection.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating to the Juniper device via NETCONF over SSH.
- The node uses a NETCONF client library internally to establish connections and send RPC requests.
- The user must provide valid credentials and ensure network connectivity to the Juniper device's NETCONF port.
Troubleshooting
- Missing Credentials Error: If the node throws an error about missing credentials, ensure that the required API authentication token or key is properly configured in n8n.
- Unsupported Operation or Protocol Errors: The node validates supported operations and protocols; providing unsupported values will cause errors. Verify that the selected operation and parameters are valid.
- Connection Timeout or Refused: Network issues or incorrect host/port settings may prevent connection. Confirm device accessibility and correct NETCONF port.
- XML Parsing Issues: If the device returns unexpected XML, enabling "Include Raw XML" helps diagnose response format problems.
- Commit Failures: When setting or removing interface rate limits with auto-commit enabled, commit operations might time out or fail. Adjust the commit timeout or verify device state.