Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • IPv6 transit statistics for logical interfaces (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.2R1 you can stream operational state statistics for IPv6 logical interfaces. Telemetry sensors include counters for octets and packets under the resource path /junos/system/linecard/interface/logical/family/ipv6/usage/.

    [See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

  • IS-IS configuration using OpenConfig (PTX10001-36MR, PTX10008, and PTX10016)—Junos OS Evolved Release 23.2R1 introduces support for new configuration paths based on the OpenConfig data model openconfig-isis.yang version 1.0.0.

    [See Mapping OpenConfig ISIS Commands to Junos Configuration.]

  • LDP traffic statistics sensor support (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.2R1, we support LDP traffic sensors to deliver statistics natively through UDP or through OpenConfig using Juniper proprietary Remote Procedure Call (gRPC) or gRPC Network Management Interface (gNMI).

    Use these paths for native delivery:

    • /junos/services/ldp/label-switched-path/transit/usage

    • /junos/services/ldp/label-switched-path/ingress/usage

    Use these paths for OpenConfig delivery:

    • /mpls/signaling-protocols/ldp/lsp-transit-policies/lsp-transit-policy/state/counters

    • /mpls/signaling-protocols/ldp/lsp-ingress-policies/lsp-ingress-policy/state/counters

    [See Junos YANG Data Model Explorer for OpenConfig and native sensors or sensor (Junos Telemetry Interface) for UDP. ]

  • On-box aggregation support (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.2R1, we support on-board aggregation of interface, CoS, MPLS, and aggregated Ethernet counters. Off-box aggregation has limited insight into systemic events, such as line- card resets or LAG membership changes. On-box aggregation aggregates the counters at the source and generates a telemetry stream of aggregated Packet Forwarding Engine statistics and telemetry data that reduces production errors at the collector.

    These sensors are supported with on-box aggregation:

    • /junos/system/linecard/interface/traffic/

    • /junos/system/linecard/interface/queue/

    • /junos/system/linecard/interface/logical/usage/

    • /junos/system/linecard/cos/interface/interface-set/output/queue/

    • /junos/services/label-switched-path/usage/

    • /qos/interfaces/interface/output/queues/queue/state/

    • /interfaces/interface/state/counters/

    • /interfaces/interface/subinterfaces/subinterface/state/counters/

    • /interfaces/interface/subinterfaces/subinterface/ipv4/state/counters/

    • /interfaces/interface/subinterfaces/subinterface/ipv6/state/counters/

    • /network-instances/network-instance/mpls/lsps/constrained-path/tunnels/tunnel/state/counters/

    • /junos/system/linecard/interface/queue/

    • /junos/system/linecard/qmon-sw/

    • /qos/interfaces/interface/output/queues/queue/state/

    • /qos/interfaces/interface/input/virtual-output-queues/voq-interface/queues/queue/state/

    [See Junos YANG Data Model Explorer for sensors. ]

  • OpenConfig interface configuration and operational state sensors support (PTX10008 and PTX10016)—Junos OS Evolved Release 23.2R1 introduces support for OpenConfig interface configuration. Support includes streaming of operational state data.

    [See Junos YANG Data Model Explorer for state sensors. ]

  • OpenConfig and telemetry firewall filter support (PTX10001-36MR, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.2R1, we support OpenConfig firewall configuration and telemetry streaming for forwarding policy to include dscp-set and apply-vrf-selection-policy.

    [See Junos YANG Data Model Explorer for state sensors and Mapping OpenConfig Firewall Filter Commands to Junos Configuration for configuration. ]

  • OpenConfig multicast data model support (ACX7024, ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5220, and QFX5700)—Junos OS Evolved Release 23.2R1 introduces support for OpenConfig multicast data models openconfig-pim.yang (version 0.4.2) and openconfig-igmp.yang (version 0.3.0). Support includes telemetry streaming of operational state data and configuration using OpenConfig.

    [See Junos YANG Data Model Explorer for state sensors and Mapping OpenConfig Multicast Commands to Junos Configuration for configuration. ]

  • OpenConfig QoS operational state sensors (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.2R1 introduces support for OpenConfig quality-of-service (QoS) forwarding classes, classifiers, and rewrites. Support includes streaming of operational state data.

    [See Junos YANG Data Model Explorer for state sensors.]

  • Packet Forwarding Engine pipeline sensor support (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.2R1 introduces support for PacketForwarding Engine sensors with additional resource utilization for components.

    [See Junos YANG Data Model Explorer for state sensors. ]

  • Subscribe RPC for configuration paths (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.2R1 you can subscribe to telemetry updates for configuration paths using the Subscribe RPC, which is defined by the gRPC Network Management Interface (gNMI) protocol. Support includes ONCE and STREAM modes. STREAM mode includes ON_CHANGE, TARGET_DEFINED, and SAMPLE support.

    [See Understanding OpenConfig and gRPC.]

  • Support for configuring the routing instance and source address for each gRPC tunnel session (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5220, and QFX5700)—Starting with Junos OS Evolved Release 23.2R1, you can configure the routing instance and source address for each gRPC tunnel session to dial out a connection to the tunnel server.

    To configure the routing instance, add the routing-instance routing-instance option and to configure the source address, add the source-address ip-address option in the grpc-tunnel configuration statement.

    If you do not choose to configure a routing instance, the gRPC tunnel uses the default routing instance. If you do not configure the source address, the kernel picks the source address that can reach the tunnel server.

    [See gRPC Tunnels Overview and grpc-tunnel].

  • Support for FEC monitoring sensors and counters (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.2R1, we support forward error correction (FEC) monitoring sensors and counters on Ethernet interfaces. You can stream Ethernet FEC mode, FEC codeword size, and the FEC codeword rate, as well as bit errors, FEC corrected words, and FEC uncorrected words counters.

    [See Junos YANG Data Model Explorer.]

  • System memory and mount points telemetry (PTX10016)—Junos OS Evolved Release 23.2R1 introduces support for operational state sensors based on the OpenConfig data model openconfig-system.yang version 0.10.0. Using Junos telemetry interface (JTI), you can stream statistics for system memory and mount points to monitor overall system health.

    [See Junos YANG Data Model Explorer.]

  • Telemetry streaming for BGP protocol based on OpenConfig data model (PTX10008 and PTX10016)—Starting in Junos OS Evolved Release 23.2R1, the data model for BGP is compliant with OpenConfig. The node type for /network-instances/network-instance/protocols/protocol/ is defined as a list that contains user-configurable keys for the protocol name and identifier.

    [See Junos YANG Data Model Explorer.]

  • Telemetry streaming for IS-IS protocol based on OpenConfig data model (PTX10008 and PTX10016)—Starting in Junos OS Evolved Release 23.2R1, the data model for IS-IS is compliant with OpenConfig. The node type for /network-instances/network-instance/protocols/protocol/ is defined as a list that contains user-configurable keys for the protocol name and identifier.

    [See Junos YANG Data Model Explorer.]

  • Telemetry streaming for static and local aggregate routes based on OpenConfig data model (PTX10016)—Starting in Junos OS Evolved Release 23.2R1, the data model for static and local aggregate routes is compliant with OpenConfig. The node type for /network-instances/network-instance/protocols/protocol/ is defined as a list that contains user-configurable keys for the protocol name and identifier.

    [See Junos YANG Data Model Explorer.]

  • Upgrade of OpenConfig BGP models (ACX7024, ACX7509, ACX7100-32C, ACX7100-48L, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.2R1 supports an upgrade for the following OpenConfig BGP models to version 9.1.0:

    • openconfig-bgp-global.yang

    • openconfig-bgp-neighbor.yang

    • openconfig-bgp-peer-group.yang

    The upgraded models introduce new leaves for operational state sensors and configuration.

    [See Junos YANG Data Model Explorer for state sensors and Mapping OpenConfig BGP Commands to Junos Configuration for configuration. ]

  • Upgrade of OpenConfig BGP RIB models (ACX7024, ACX7100-32C, ACX7100-48L, ACX7509, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.2R1 supports operational state sensors based on the latest OpenConfig BGP RIB data models:

    • openconfig-rib-bgp-attributes.yang (version 0.8.1)

    • openconfig-rib-bgp-ext.yang (version 0.6.0)

    • openconfig-rib-bgp-shared-attributes.yang (version 0.8.1)

    • openconfig-rib-bgp-table-attributes.yang (version 0.8.1)

    • openconfig-rib-bgp-tables.yang (version 0.8.1)

    • openconfig-rib-bgp-types.yang (version 0.5.0)

    • openconfig-rib-bgp.yang (version 0.8.1)

    Junos OS Evolved no longer supports the following model versions:

    • openconfig-rib-bgp-ext.yang (version 0.2.0)

    • openconfig-rib-bgp-types.yang (version 0.2.0)

    • openconfig-rib-bgp.yang (version 0.2.0)

    See Junos YANG Data Model Explorer.

  • Easy access to spring sensor-based traffic statistics (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.2R1, you can use the set protocols isis source-packet-routing sensor-based-stats subscribe interval <interval> configuration statement to subscribe to spring traffic sensors or sensor paths on the PTX Series devices. You can use the following show commands to view the telemetry sensor-based traffic updates:

    • show spring traffic-statistics
    • show spring traffic-statistics per-interface-per-member-link <ingress> <egress>
    • show spring traffic-statistics per-sid <ingress> <egress>

    [See sensor-based-stats].