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 Health Monitoring telemetry data for standby nodes and FPCs (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, PTX10016, PTX12008, QFX5130-32CD, QFX5130E-32CD, QFX5130-48C, QFX5130-48CM, QFX5220, QFX5230-64CD, QFX5240-64OD, QFX5240-64QD, QFX5700, and QFX5700E)—We've expanded telemetry data to support Health Monitoring telemetry beyond the primary node to include standby nodes and Flexible PIC Concentrators (FPCs). You can stream statistics that include load average, process parameters, and component CPU utilization using either Juniper's proprietary remote procedure call (gRPC) or gRPC Network Management Interface (gNMI) transport from the device to the collector.

    [For sensors, see Junos YANG Data Model Explorer.]

  • Real-time hardware resource monitoring (QFX5130, QFX5130-48C, QFX5130-48CM, QFX5130E-32CD, QFX5220-32CD, QFX5220-128C, QFX5230-64CD, QFX5240-64OD, QFX5240-64QD, and QFX5700)—You can monitor hardware resource utilization statistics in real time for efficient capacity planning. The Junos telemetry interface (JTI) streams NPU resource utilization statistics through gRPC and the gNMI transport from a device to an external collector.

    [See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface), sensor (Junos Telemetry Interface), and Junos YANG Data Model Explorer.]

  • Telemetry and SNMP support for network counters and buffer usage (QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—This feature introduces telemetry streaming and SNMP support for explicit congestion notification (ECN), priority-based flow control (PFC) counters, and ingress buffer usage. Monitor the MAC Priority Flow Control Statistics, ECN Marked Packets, and Ingress Resource Errors counters using fields in the /state/interfaces/interface/counters/ sensor. Track the Egress Priority Group Peak Buffer Occupancy statistics with the /junos/system/linecard/qmon-sw/ sensor. The feature introduces SNMP support for these statistics using the respective fields.

    • In the /state/interfaces/interface/counters/ sensor:

      • MAC Priority Flow Control Statistics:

        • /state/interfaces/interface[name=' ']/counters/pfc[priority=' ']/priority

        • /state/interfaces/interface[name=' ']/counters/pfc[priority=' ']/in-pkts

        • /state/interfaces/interface[name=' ']/counters/pfc[priority=' ']/out-pkts

      • ECN Marked Packets:

        • /state/interfaces/interface[name=' ']/counters/errors/out-ecn-ce-marked-pkts

      • Ingress Resource Errors:

        • /state/interfaces/interface[name=' ']/counters/errors/in-resource-drops

    • In the /junos/system/linecard/qmon-sw/ sensor:

      • Egress Priority Group Peak Buffer Occupancy:

        • /cos/interfaces/interface[name=' ']/priority-groups/priority-group[pg=' ']/peakBufferOccupancy

    SNMP support is introduced with the following fields:

    • MAC Priority Flow Control Statistics:

      • JnxCosPfcPriorityTable (jnxCosPfcPriorityRequestsTx & JnxCosPfcPriorityRequestsRx)

    • ECN Marked Packets:

      • IfJnxTable (ifJnxOutEcnMarkedPackets)

    • Ingress Resource Errors:

      • IfJnxTable (ifJnxInQDrops)

    [See Junos YANG Data Model Explorer and Understanding Junos YANG Modules.]

  • Configuring IP source address for legacy gRPC dial-out connections (QFX5230-64CD, QFX5240-64OD, QFX5240-64QD)—Set a source IP address and routing instance for legacy gRPC service dial-out connections. Previously, the outgoing interface IP address was used as a source address without an option to configure a source IP address. This feature supports FLEX deployments, enabling dial-out from a specified IP address or interface (such as a loopback0 address). Use the routing-instance and local-address statements at the [edit services analytics export-profile profile-name] hierarchy level.

    [See local-address (Junos Telemetry Interface), export-profile (Junos Telemetry Interface), routing-instance (Junos Telemetry Interface), and Using gRPC Dial-Out for Secure Telemetry Collection]

  • IPv4 and IPv6 traffic statistics telemetry (QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—This feature supports streaming of IPv4 and IPv6 transit statistics using the native resource paths /state/interfaces/interface[name=' ']/counters/ipv4/ and /state/interfaces/interface[name=' ']/counters/ipv6/. The exported fields include in-pkts, in-bytes, out-pkts, and out-bytes. To enable transit statistics for the physical port, configure route accounting by including the route-accounting statement at the [edit forwarding-options family family-name] hierarchy level.

    [See Junos YANG Data Model Explorer and route-accounting.]

  • OpenConfig compatibility for Junos OS Evolved telemetry sensors (QFX5130-32CD, QFX5130E-32CD, QFX5130-48C, QFX5130-48CM, QFX5220, QFX5230-64CD, QFX5240-64OD, QFX5240-64QD, QFX5700, and QFX5700E)—We've introduced Junos telemetry interface (JTI) sensor support for renaming existing noncompatible interface sensor leaves to OpenConfig-compatible sensor leaves. We've removed a few nonstandard leaves for OpenConfig compatibility. Current sensors support target-defined streaming, but new sensors do not support ON-CHANGE.

    [For a complete list of all other sensors available in the above sensor path, see Junos YANG Data Model Explorer.]

  • Telemetry streaming support (QFX Series)—Junos OS Evolved supports telemetry on QFX Series switches using the following sensors:

    [See Junos YANG Data Model Explorer.]