Actions9
Overview
This node enables interaction with Juniper network devices using the NETCONF protocol over SSH. It supports various operations to retrieve device information, check configuration changes, manage firewall policers, and specifically for this context, remove interface rate limits on specified interfaces.
The "Remove Interface Rate Limit" operation allows users to delete configured rate limiting (policer) settings from a logical interface unit on a Juniper device. This is useful when you want to disable or clear traffic shaping or policing policies applied to an interface's input, output, or both directions.
Practical examples:
- Removing bandwidth restrictions on an interface after a policy change.
- Clearing all Layer 2 policers on a specific interface unit to reset traffic control.
- Automating network device cleanup tasks in workflows that manage Juniper configurations.
Properties
| Name | Meaning |
|---|---|
| Host | The hostname or IP address of the Juniper device to connect to. |
| Port | The NETCONF over SSH port number (default is 830). |
| Interface Name | The physical interface name on the device (e.g., ge-1/2/7) where the rate limit will be removed. |
| Unit Number | The logical unit number of the interface (e.g., 0). |
| Direction | The direction of the rate limit to remove. Options: Input Only, Output Only, Both Input and Output, All (removes entire Layer2-Policer). |
| Auto Commit | Whether to automatically commit the configuration changes after removal (true/false). |
| Commit Timeout (Ms) | Timeout in milliseconds for the commit operation if auto commit is enabled (default 120000 ms). |
Output
The node outputs JSON data representing the XML response parsed from the Juniper device after executing the NETCONF RPC command.
For the "Remove Interface Rate Limit" operation:
- The output JSON contains the result of the
<edit-config>RPC call that deletes the policer configuration. - If auto commit is enabled, it also includes the commit operation result nested inside a
<configuration-result>structure. - The output does not include binary data.
Example output JSON structure (simplified):
{
"data": {
"configuration-result": {
"edit-result": { /* result of edit-config RPC */ },
"commit-result": { /* result of commit RPC if autoCommit=true */ },
"commit-status": "not-committed" // if autoCommit=false
}
}
}
Dependencies
- Requires an API key credential for authenticating to the Juniper device via NETCONF over SSH.
- The node uses a bundled NETCONF client library to establish SSH connections and send RPC commands.
- No additional external services are required beyond access to the Juniper device.
- Ensure the Juniper device is reachable at the specified host and port, and that NETCONF over SSH is enabled.
Troubleshooting
- Connection errors: May occur if the host is unreachable, port is blocked, or credentials are incorrect. Verify network connectivity and authentication details.
- Unsupported operation error: If the operation parameter is set incorrectly or unsupported, the node throws an error. Confirm the operation is set to "Remove Interface Rate Limit".
- Timeouts: If the device takes too long to respond, increase the timeout settings in the credentials or node parameters.
- Commit failures: When auto commit is enabled, commit may fail due to configuration conflicts or syntax errors. Review device logs and ensure the configuration is valid before committing.
- Missing required parameters: The interface name and unit number must be provided; otherwise, the node will throw an error.