Network Management and Monitoring
-
Clear LLDP neighbors from an interface with the gRPC Network Operations Interface (gNOI)
Layer2
service (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 24.2R1, you can execute supportedLayer2
service remote procedure calls (RPCs) to perform the equivalent of theclear lldp neighbors interface interface-name
command.[See gNOI Layer 2 Service.]
-
Support for the
genstate
YANG data models (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 24.2R1, we publish subscribable YANG data models for operational state on Junos devices. Thegenstate
YANG models expose a subset ofshow
command data through the gRPC Network Management Interface (gNMI)subscribe
RPC. A gNMI telemetry collector can subscribe to the resource paths defined in the published models to query for specific state data.[See Junos Genstate YANG Data Models and gNMI Genstate Subscription.]
-
Support for NETCONF Call Home (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 24.2R1, Junos devices support the NETCONF Call Home feature for establishing a NETCONF session over SSH. NETCONF Call Home enables the Junos device to initiate a secure connection to a NETCONF client. You can use NETCONF Call Home when the NETCONF client cannot initiate a connection with the server. This situation can occur when a firewall or another security tool restricts management access to the server or implements Network Address Translation (NAT). NETCONF Call Home can also streamline the initial deployment of network devices by enabling a device to register with a management system when it is first powered on.
[See NETCONF Call Home.]