Actions9
Overview
This node enables interaction with Juniper network devices using the NETCONF protocol over SSH. It supports a variety of operations to retrieve and manipulate device configuration and status information, including querying protocol statuses such as BGP, OSPF, MPLS, ARP, LACP, LDP, and others.
A common use case is network automation where administrators want to programmatically fetch detailed protocol or interface status from Juniper devices or apply configuration changes like setting or removing interface rate limits. For example, you can use this node to get a summary of BGP neighbors, check uncommitted configuration changes, or retrieve detailed MPLS LSP information.
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 830). |
| Protocol | The network protocol to query status for. Options: ARP, BGP, L2Circuit, LACP, LDP, MPLS, OSPF, OSPF3, Route. |
| ARP Query Type | Type of ARP query (only "Table Information" supported). |
| Logical System | Logical system name on the device; empty means default system. |
| Routing Engine | Routing engine selection (e.g., master, backup, re0, re1, both, local, other, default). |
| Hostname | Hostname filter for ARP queries; empty means all hosts. |
| Interface Name | Interface name filter; empty means all interfaces. Supports wildcards in some protocols. |
| VPN Routing Table | VPN routing table name for ARP queries. |
| No Resolve | Boolean flag whether to avoid symbolic address resolution in ARP queries. |
| Show Expiration Time | Boolean flag to show seconds remaining before expiration in ARP entries. |
| Show Reference Count | Boolean flag to show next hop reference count in ARP entries. |
| Show State | Boolean flag to show next hop current state in ARP entries. |
| LACP Query Type | Type of LACP query: Interface Information, Interface Statistics, Timeout Information. |
| Extensive | Boolean flag to show detailed LACP information. |
| MPLS Query Type | Type of MPLS query: Admin Group Information, Interface Information, LSP Information, Path Information, Static LSP Information. |
| Verbosity Level | Detail level for MPLS and other protocols: Brief, Detail, Extensive, Summary, etc. |
| LSP Type | Filter for MPLS LSP type: All Types, Egress, Ingress, Transit. |
| LSP Level | Detail level for MPLS LSP display: Brief, Descriptions, Detail, Extensive, Terse. |
| LSP Name | MPLS LSP name filter; empty means all LSPs. |
| Path Name | MPLS path name filter; empty means all paths. |
| Route Query Type | Type of route query: Forwarding Table Information, Instance Information, Route Information, Route Resolution Information, Route Summary Information. |
| RIB Sharding | RIB shard name for route summary queries. |
| Table Name | Route table name (e.g., inet.0, inet6.0); empty means all tables. |
| Destination | Destination prefix filter (e.g., 192.168.1.0/24); empty means all routes. |
| Protocol Filter | Protocol filter for routes: All Protocols, BGP, Direct, Local, OSPF, Static. |
| Address Family | Address family filter for forwarding table: All Families, Bridge, EVPN, IPv4, IPv6, ISO, MPLS, VPLS. |
| Detail Level | Display detail level for routes and forwarding tables: Brief, Detail, Extensive. |
| Instance Name | Routing instance name filter; empty means all instances. |
| OSPF3 Query Type | OSPFv3 query types: Database Information, Interface Information, Neighbor Information, Overview, Route Information, Statistics. |
| Realm | OSPFv3 realm selection: All Realms, IPv4 Multicast, IPv4 Unicast, IPv6 Multicast. |
| Area ID | OSPF/OSPF3 area ID filter (e.g., 0.0.0.0 or 1); empty means all areas. |
| Neighbor | Neighbor IP address or ID filter; empty means all neighbors. |
| LSA Type | Link-state advertisement type filter for OSPF/OSPF3 database queries. |
| LSA ID | LSA ID filter; empty or "all" means all LSAs. |
| BGP Query Type | BGP query types: Group Information, Group Output Queue, Monitoring Protocol Statistics, Neighbor Information, Outbound Route Filtering, Output Queue Information, Route Information, Route Target Filtering, Summary Information, Traffic Statistics. |
| BGP Logical System | Logical system name for BGP queries; empty means default. |
| BGP RIB Sharding | RIB shard name for BGP queries. |
| BGP Instance | BGP instance name prefix filter; empty means all instances. |
| Exact Instance | Exact BGP instance name filter. |
| BGP Verbosity Level | Detail level for BGP group, route target filtering, traffic statistics, outbound route filtering: Summary, Brief, Detail. |
| Group Name | BGP group name filter; empty means all groups. |
| Neighbor Address | BGP neighbor IP address filter; empty means all neighbors. |
| Auto-Discovered Peers | Boolean flag to show only auto-discovered BGP peers. |
| Station Name | Monitoring protocol station name for BGP monitoring queries. |
| Route Table | Route table name for BGP route queries (default inet.0). |
| Route Prefix | Route prefix filter for BGP route queries; empty means all routes. |
| LDP Query Type | LDP query types: Database Information, Database Label Requests, FEC Filters, Interface Information, Interface Statistics, Neighbor Information, OAM Information, Overview, P2MP FEC Information, P2MP Path Information, P2MP Tunnel Information, Path Information, RIB Groups, Route Information, Session Information, Statistics, Traffic Statistics. |
| LDP Logical System | Logical system name for LDP queries; empty means default. |
| LDP Instance | LDP routing instance name. |
| LDP Verbosity Level | Detail level for LDP queries: Brief, Detail, Extensive, Summary. |
| LDP Interface Name | Interface name filter for LDP queries. |
| Neighbor IP | Neighbor IP address filter for LDP queries. |
| Neighbor Type | Neighbor type filter for LDP queries: All Types, Auto Discovery, Auto Targeted, Link Protection, Session Protection. |
| Destination IP | Destination IP address filter for LDP session, route, path queries. |
| Session Type | Session type filter for LDP session queries. |
| LDP Route Type | Shadow route type for LDP route queries: FEC and Route, FEC Only, Route Only. |
| LDP Family | Address family for LDP route queries: All Families, IPv4, IPv6. |
| Session IP | Session destination IP address for LDP database and label requests queries. |
| FEC Type | FEC type for LDP database, label requests, traffic statistics queries: All Types, IPv4, IPv6, L2Circuit, P2MP. |
| FEC | Forwarding equivalence class (IP address and prefix length) for LDP fec-filters and OAM queries. |
| Interface Type | Interface type for LDP interface statistics queries (e.g., P2MP). |
| L2Circuit Query Type | L2Circuit query types: Connection Information, PW Auto-Sensing Information. |
| L2Circuit Logical System | Logical system name for L2Circuit queries; empty means default. |
| Neighbor IP | Neighbor IP address filter for L2Circuit queries (default "all"). |
| Interface Name | Interface name filter for L2Circuit connections query (default "all"). |
| Connection State | Connection state filter for L2Circuit connections query: Down, Up, Up-Down (all). |
| Detail Level | Detail level for L2Circuit connections query: Brief, Extensive, History, Instance History, Status, Summary. |
| VC ID | Virtual Circuit ID for L2Circuit PW Auto-Sensing query (default "all"). |
| Include Raw XML | Boolean flag to include raw XML response in output for debugging purposes. |
Output
The node outputs JSON data parsed from the XML response returned by the Juniper device's NETCONF RPC calls. The structure of the JSON depends on the operation and protocol queried but generally reflects the hierarchical data model of the device's configuration or operational state.
If the "Include Raw XML" option is enabled, the raw XML response string is also included in the output under the rawXml field for debugging.
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 custom NETCONF client implementation to establish SSH connections and send RPC commands.
- The user must provide valid host, port, and authentication credentials.
- The node expects the Juniper device to support the relevant NETCONF RPCs for the selected operations and protocols.
Troubleshooting
- Missing Credentials: If credentials are not provided or invalid, the node will throw an error indicating missing credentials.
- Unsupported Operation or Protocol: Selecting an unsupported operation or protocol value results in an error specifying the unsupported type.
- Connection Issues: Network connectivity problems, incorrect host/port, or SSH authentication failures will cause connection errors.
- Invalid Parameters: Some parameters have constraints (e.g., subtree filter paths must start with "configuration"). Violations will cause errors.
- Timeouts: The node has a configurable timeout for NETCONF operations; if exceeded, it may throw a timeout error.
- XML Parsing Errors: Malformed responses or unexpected XML structures might cause parsing errors.
- To resolve issues, verify credentials, network access, parameter correctness, and enable raw XML output for debugging.