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 controller card power management using gNMI and gNOI (PTX10001-36MR, PTX10008, and PTX10016)—You can manage the power state of Routing Engines using the gRPC Network Management Interface (gNMI) and gRPC Network Operations Interface (gNOI) services. Use gNMI for configurations that persist across reboots, ensuring the controller card remains powered off. Use gNOI to temporarily power down a Routing Engine until the next reboot. This capability is particularly beneficial for troubleshooting and isolating faulty cards. To use the gNMI service, configure the path /components/component/controller-card/config/power-admin-state and set the value to "POWER_DISABLED" or "POWER_ENABLED" for the target Routing Engine. For the gNOI service, use the System service Reboot() RPC with the POWERDOWN or POWERUP option and specify the target Routing Engine.

    [See gNOI System Service and Sensor Power-State Management Support Using gNMI.]

    [See Junos YANG Data Model Explorer.]

  • Support for genstate YANG data models (PTX10003)—You can subscribe to genstate YANG data models to access a subset of show command data. This feature enables a gNMI telemetry collector to subscribe to resource paths in the models, enabling you to query specific state data. This feature supports the show snmp command. The supported root resource paths are genstate:genstate/snmp-statistics, genstate:genstate/rmon-alarm-information, genstate:genstate/rmon-event-information, and genstate:genstate/snmp-v3-information. With this feature you can now subscribe to more specific state data on the device.

    [See Junos YANG Data Model Explorer and https://www.juniper.net/documentation/us/en/software/junos/interfaces-telemetry/topics/concept/genstate-gnmi-overview-telemetry.html.]

  • Export timing data to collectors (ACX7100-32C, PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008, and PTX10016)—Junos telemetry interface (JTI) supports export of timing attributes for Precision Time Protocol (PTP) and Synchronous Ethernet to a collector. Export of data is through native models (export of PTP data is through the YANG data model). This feature supports both periodic streaming and on-change notifications. The feature introduces the following subscription paths:

    • For Precision Time Protocol : /state/protocols/ptp/instances/instance[instance-index]/

    • For Synchronous Ethernet: /state/protocols/synce/

    With this feature you can now view Precision Time Protocol and Synchronous Ethernet sensor information.

    For a complete list of sensor paths supported by the device, 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 firewall filter monitoring under OpenConfig network-instance AFTs (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—You can configure firewall filters under the OpenConfig network instance policy-forwarding (OC-NI-PF) hierarchy, enabling state sensors capture. You can use the OpenConfig network-instance AFTs feature to monitor policy forwarding entries, such as IP prefixes, DiffServ code point (DSCP), IP protocol, and packet counters.

    [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.]

  • Support for genstate YANG data models (PTX10003)—Use genstate YANG data models to access a subset of show command data. A gNMI telemetry collector can subscribe to resource paths in these models to query specific state data. The feature supports the show lacp command.

    [See Junos YANG Data Model Explorer,Understanding Junos YANG Modules and gNMI Genstate Subscription.]

  • 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.]

  • Per-segment list telemetry support for colored and uncolored SR-TE tunnels(ACX7100-32C, ACX7100-48L, ACX7332, ACX7024, ACX7024X, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—You can configure per-segment-list sensors for segment routing–traffic engineering (SR-TE) tunnels to generate sensor IDs and collect traffic statistics from both ingress and transit points.The feature generates unique sensor IDs for each segment-list and provides the option to disable specific sensors. Additionally, updated SR-TE displays and route installations reflect per-path sensor information, ensuring comprehensive visibility and management of network telemetry.