Actions9
Overview
This node enables interaction with Juniper network devices using the NETCONF protocol over SSH. Specifically, the "Get Interface Operations" operation retrieves various detailed operational data about network interfaces on a Juniper device. It supports multiple types of interface-related queries such as summaries, controller info, filter info, MC-AE details, optics diagnostics, policer info, port profiles, queue info, and transport info.
Typical use cases include:
- Monitoring interface status and statistics for network management.
- Gathering detailed diagnostics for troubleshooting physical or logical interfaces.
- Retrieving configuration and operational state related to interface queues, policers, or transport layers.
- Automating network audits by extracting interface operational data programmatically.
For example, a network engineer could use this node to fetch an interface summary to check overall interface health or query MC-AE (Multi-Chassis Aggregation Ethernet) information to verify link aggregation status across chassis.
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 Operation Type | The type of interface operation data to retrieve. Options: Controller Information, Filter Information, Interfaces Summary, MC-AE Information, MC-AE Revertive, Optics Diagnostics, Policer Information, Port Profile, Queue Information, Transport Information. Default is Interfaces Summary. |
| Interface Name | The name of the interface (e.g., xe-0/0/0). Required for some operation types like controller, filter, mc-ae, optics-diagnostics, policer, port-profile, queue, transport. |
| MC-AE ID | Identifier for MC-AE (Multi-Chassis Aggregation Ethernet). Required for MC-AE and MC-AE Revertive operations. |
| Unit Number | Logical interface unit number (0-16385). Used in MC-AE operation type. |
| Extensive | Boolean flag indicating whether to show detailed MC-AE information. |
| Forwarding Class | Name of the forwarding class. Used in Queue Information operation type. |
| Traffic Direction | Traffic direction filter for queue info: Both Ingress and Egress, Egress only, or Ingress only. Default is both. |
| Include Raw XML | Whether to include the raw XML response from the device in the output (useful for debugging). |
Output
The node outputs JSON data representing the parsed XML response from the Juniper device corresponding to the requested interface operation. The structure varies depending on the selected interface operation type but generally includes detailed operational information about interfaces, such as status, statistics, configuration, diagnostics, and other relevant metrics.
If the "Include Raw XML" option is enabled, the raw NETCONF XML response is also included in the output under the rawXml field for debugging purposes.
No binary data output is produced by this node.
Example simplified output structure (JSON):
{
"data": {
"interface-summary-information": {
"physical-interface": [
{
"name": "xe-0/0/0",
"admin-status": "up",
"oper-status": "up",
"traffic-statistics": { ... }
},
...
]
}
},
"rawXml": "<rpc-reply>...</rpc-reply>" // optional, if enabled
}
Dependencies
- Requires a valid API key credential or authentication token for connecting to the Juniper device via NETCONF over SSH.
- The node uses an internal NETCONF client library to establish SSH connections and send RPC commands.
- The Juniper device must have NETCONF enabled and accessible on the specified host and port.
- No additional external services are required beyond the Juniper device itself.
Troubleshooting
Common Issues
- Connection failures: Ensure the host IP/hostname and port are correct, and that the Juniper device allows NETCONF connections from the n8n server.
- Authentication errors: Verify that the provided credentials (username, password, private key) are correct and have sufficient permissions.
- Unsupported interface operation type: Selecting an unsupported or misspelled interface operation type will cause an error.
- Missing required parameters: Some interface operation types require additional parameters like interface name or MC-AE ID; omitting these will cause errors.
- Timeouts: Large queries or slow network connections may cause timeouts; consider increasing the timeout setting if available.
Error Messages
"Unsupported interface operation type: <type>": The chosen interface operation type is not supported by the node. Check the spelling and available options."Missing credentials": Credentials for connecting to the Juniper device are not configured or invalid."Connection timed out": Unable to reach the Juniper device within the timeout period."RPC error": The Juniper device returned an error in response to the NETCONF RPC command. Review the raw XML output if enabled for details.
To resolve errors, verify all input parameters, credentials, and network connectivity. Enable raw XML output to inspect the exact device responses for debugging.