Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Support for tail-drop sensor in OpenConfig model (QXF5220, QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—This feature supports the OpenConfig model openconfig-if-ethernet.yang (physical interface level) version 2.6.2 (no configuration). You can now monitor tail-drop metrics using the OpenConfig model, enhancing your network management capabilities.The sensor supports tracking tail-drop packets and bytes for both ingress and egress queues. This integration enables you to use standardized data modeling for better interoperability and streamlined network performance analysis.

    [See Junos YANG Data Model Explorer.]

  • Enhanced telemetry with multiple gRPC servers and multi-port gRPC services (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5130-48C, QFX5130-48CM, QFX5130E-32CD, QFX5220, QFX5230-64CD,QFX5700, and QFX5700E)—You can configure multiple RPC developed by Google (gRPC) servers with distinct services, listening addresses, and ports by using the Junos telemetry interface (JTI). This feature enhances control over service management and telemetry data collection. You can also configure TLS certificates for secure communications. For example, you can configure a server to listen on a specific port and serve only designated gRPC services, enhancing flexibility and security in your telemetry setup.

  • Support for tail-drop sensor in OpenConfig mode (QFX5220, QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—This feature supports OpenConfig model openconfig-if-ethernet.yang (physical interface level) version 2.6.2 (no configuration). You can now monitor tail-drop metrics using the OpenConfig model, enhancing your network management capabilities. The sensor supports tracking tail-drop packets and bytes for both ingress and egress queues. This integration allows you to utilize standardized data modeling for better interoperability and streamlined network performance analysis.

    [See Junos YANG Data Model Explorer.]

  • Native YANG state model and telemetry support for network stack protocol statistics (ACX Series, QFX Series, and PTX Series)—You can use a native YANG state model and telemetry to monitor network stack protocol statistics on EVO platforms. Telemetry provides real-time data streaming for protocols such as TTP, ICMP, MPLS, TCP, and more. These statistics, previously available through CLI commands, are now accessible through telemetry streaming, ensuring real-time updates. This feature provides a comprehensive and dynamic monitoring solution, configurable in either "on-change" or "periodic" mode, enhancing your network's observability and performance management.

    [See Junos YANG Data Model Explorer.]

  • Health monitoring sensors (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5130E-32CD, QFX5130-48C, QFX5130-48CM, QFX5220, QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)— Junos telemetry interface (JTI) provides native sensors to monitor device infrastructure health. Device streams health statistics that external collectors use to track performance.

    Use the resource path /state/system/infrastructure/junos-evolved/ to view the health statistics.

    These sensors stream details such as cluster data, distributor statistics, Distributed Data Store (DDS) client information, common resources, and indexes for Identity Management and Device Management .

    [See Junos YANG Data Model Explorer.]