Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • New state data model for Juniper proprietary Remote Procedure (gRPC) service (PTX10001-36MR, PTX10003, PTX10008, PTX10016)—Junos OS Evolved Release 23.4R1 contains a restructured native state data model defining gRPC server instances. The new model includes common attributes and gRPC Network Management Interface (gNMI) service details.

    The sensor /state/system/services/http/servers/ and its leaves illustrate the new structure.

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

  • 400G ZR+ optic enhancement for signal power statistics (PTX10001-36MR)—Junos OS Evolved Release 23.4R1 supports enhanced signal power statistics for 400G ZR+ optics. Use the sensor /components/component/optical-channel/state/input-power/ to export signal power statistics from a Juniper device to an outside collector. This feature supports the OpenConfig data model openconfig-terminal-device.yang version (version 1.9.0).

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

  • Resource Public Key Infrastructure (RPKI) enhanced streaming telemetry support (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports enhanced statistics for RPKI databases and RPKI sessions and validation-related statistics per route, per RIB and per BGP peer basis. Using these statistics, you can perform operational debugging on your network and take appropriate mitigating actions.

    These existing Junos operational mode commands contain new statistics:

    • show route [extensive|detail] displays origin validation information for each route entry

    • show bgp neighbor validation statistics <peer> displays BGP peer-RIB validation statistics

    • show route validation-statistics displays local routing information base (RIB) specific validation statistics

    • show validation statistics displays new counters for the VRP table

    These telemetry sensors (with leaves) are supported:

    • /state/routing-instances/routing-instance/protocols/bgp/rib/afi-safis/afi-safi/[ipv4|ipv6]-unicast/loc-rib/routes/route/origin-validation-state

    • /state/routing-instances/routing-instance/protocols/bgp/rib/afi-safis/afi-safi/[ipv4|ipv6]-unicast/loc-rib/routes/route/origin-validation-invalid-reason

    • /state/routing-instances/routing-instance/protocols/bgp/groups/group/neighbors/neighbor/afi-safis/afi-safi[ipv4|ipv6]/validation-counters/

    • /state/routing-instances/routing-instance/protocols/bgp/groups/group/neighbors/neighbor/afi-safis/afi-safi[ipv4|ipv6]/validation-counters

    • /state/routing-instances/routing-instance/protocols/bgp/rib/afi-safis/afi-safi/[ipv4|ipv6]-unicast/loc-rib/validation-counters/

    • /state/routing-instances/routing-instance/routing-options/route-validation/rpki-rtr/groups/group/sessions/session/rpki-session-counters/

    • /state/routing-instances/routing-instance/routing-options/route-validation/route-validation-databases/route-validation-database/[ipv4|ipv6]/

    • /state/routing-instances/routing-instance/routing-options/route-validation/rpki-rtr/groups/group/sessions/session/

    [For sensors, see Junos YANG Data Model Explorer.] For operational mode commands, see show route, show bgp neighbor validation statistics, show route validation-statistics, and show validation statistics.

  • Multicast telemetry support with IGMP and PIM operational state sensors (ACX7024, ACX7100-32C, ACX7100-48L, ACX7509, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports IGMP and PIM sensors based on the OpenConfig data models openconfig-igmp.yang (version 0.3.0) and openconfig-pim.yang (version 0.4.2).

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

  • Telemetry streaming of operational state data for syslog messages (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports telemetry streaming of operational state data for syslog messages to an external gRPC Network Management Interface (gNMI) collector. Sensors are based on the native Junos data model under the /state/system/syslog/messages hierarchy. You can stream data using ON_CHANGE and TARGET_DEFINED modes.

    [See Junos YANG Data Model Explorer.]

  • SR-TE policy telemetry (ACX7348, PTX10003, PTX10004, PTX10008, and PTX10016)—In Junos OS Evolved Release 23.4R1, we introduce support for telemetry streaming of operational state data for the segment routing–traffic engineering (SR-TE) policy. State sensors are based on the OpenConfig data model openconfig-srte-policy.yang. You can subscribe to SR-TE sensors using the resource path /network-instances/network-instance/segment-routing/te-policies.

    [See Junos YANG Data Model Explorer.]

  • FIB sensor support (PTX10008)—Junos OS Evolved Release 23.4R1 supports the OpenConfig-Abstract Forwarding Table (oc-aft) model and the forwarding information base (FIB) to stream enhanced routing statistics. To deliver statistics to a collector, you add sensors to a subscription and also include the set routing-options forwarding-table oc-tlv-support statement at the [edit] hierarchy level to enable statistics collection. The Junos routing protocol process (rpd) sends the origin-protocol and origin-network-instance of a route, as well as the next hop using an opaque TLV to the collector. Include the following sensors in your subscription:

    • Next hops:

      • /network-instances/network-instance/afts/next-hops/next-hop/state/pop-top-label

      • /network-instances/network-instance/afts/next-hops/next-hop/state/vni-label

      • /network-instances/network-instance/afts/next-hops/next-hop/state/vni-label

      • /network-instances/network-instance/afts/next-hops/next-hop/ip-in-ip/state/dest-ip

    • State-synchronized:

      • /network-instances/network-instance/afts/state-synced/state/ipv4-unicast

      • /network-instances/network-instance/afts/state-synced/state/ipv6-unicast)

    • IPv4 and IPv6 unicast:

      • /network-instances/network-instance/afts/ipv4-unicast/ipv4-entry/state/origin-network-instance

      • /network-instances/network-instance/afts/ipv6-unicast/ipv6-entry/state/origin-network-instance)

    [For statement support, see forwarding-table. For state sensors, see Junos YANG Data Model Explorer.]

  • Hardware temperature alarm sensor support (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports the data model openconfig-platform.yang (version 0.12.2) to stream granular hardware alarm temperature statistics. At present, temperature states are streamed assuming that there is one temperature sensor representing the whole physical component. However, a component can report alarms not only for the primary temperature sensor but also for multiple temperature sensors. We have created additional temperature sensors to determine alarm origins.

    For example, if you subscribe to /components/component[name='CHASSIS0:FPC0:PEX_Temp_Sensor']/, the data exported to the collector could look like this:

    [For state sensors, see Junos YANG Data Model Explorer. For information about creating a subcription, see Configure a NETCONF Proxy Telemetry Sensor in Junos.]

  • IS-IS operational state sensors and configuration using OpenConfig (PTX10008 and PTX10016)—Junos OS Evolved Release 23.4R1 introduces enhancements to IS-IS telemetry support based on the OpenConfig data model openconfig-isis.yang (version 1.0.0). Support includes new operational state paths and configuration paths.

    [For OpenConfig configuration, see Mapping OpenConfig ISIS Commands to Junos Configuration. For state sensors, see Junos YANG Data Model Explorer.]

  • IS-IS OpenConfig and operational state sensor support (ACX7024, ACX7100-32C, ACX7100-48L, ACX7348, ACX7509, PTX10001-36MR, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports OpenConfig IS-IS configurations and sensors based on the OpenConfig data model openconfig-isis.yang (version 1.0.0). This feature closes some gaps in our OpenConfig configuration and sensor support in the IS-IS area.

    [For OpenConfig configuration, see Mapping OpenConfig ISIS Commands to Junos Configuration. For state sensors, see Junos YANG Data Model Explorer.]

  • MPLS OpenConfig and operational state sensor support (ACX7024, ACX7100-32C, ACX7100-48L, ACX7348, ACX7509, PTX10003, PTX10004, and PTX10008)—Junos OS Evolved Release 23.4R1 supports OpenConfig MPLS configurations and sensors based on the OpenConfig data models openconfig-mpls.yang (version 3.2.2), openconfig-mpls-types.yang (version 3.2.1), andopenconfig-mpls-te.yang (version 3.2.2). The following OpenConfig configurations and state sensors are supported.

    • Configurations:

      • MPLS global TTL propagation (/network-instances/network-instance/mpls/global/config/ttl-propagation)

      • MPLS LSP PRI/SEC path-metric-bound-constraint (/network-instances/network-instance/mpls/lsps/constrained-path/tunnels/tunnel/p2p-tunnel-attributes/p2p-primary-path/p2p-primary-path/path-metric-bound-constraints/path-metric-bound-constraint/config/)

    • Sensors:

      • MPLS global (/network-instances/network-instance/mpls/global/state/)

      • MPLS global interface attributes (/network-instances/network-instance/mpls/global/interface-attributes/)

      • MPLS LSP autobandwidth (/network-instances/network-instance/mpls/lsps/constrained-path/tunnels/tunnel/bandwidth/auto-bandwidth/state/)

      • MPLS LSP PRI/SEC path-metric-bound-constraint (/network-instances/network-instance/mpls/lsps/constrained-path/tunnels/tunnel/p2p-tunnel-attributes/p2p-primary-path/p2p-primary-path/path-metric-bound-constraints/path-metric-bound-constraint/state/)

      • MPLS traffic engineering global attributes SRLG (/network-instances/network-instance/mpls/te-global-attributes/srlgs/srlg/static-srlg-members/members-list/state/)

    [For OpenConfig configuration, see Mapping MPLS OpenConfig MPLS Commands to Junos Configuration. For state sensors, see Junos YANG Data Model Explorer.]

  • MPLS OpenConfig and operational state sensor support (ACX7024, ACX7100-32C, ACX7100-48L, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports OpenConfig MPLS configurations and sensors based on the OpenConfig data models openconfig-mpls-ldp.yang (version 3.2.0) and openconfig-mpls-rsvp.yang (version 4.0.0). This feature closes some gaps in our OpenConfig configuration and sensor support in the MPLS RSVP-TE and MPLS LDP areas.

    [For OpenConfig configuration, see Mapping MPLS OpenConfig MPLS Commands to Junos Configuration. For state sensors, see Junos YANG Data Model Explorer.]

  • OpenConfig support for local station MAC address (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports configuration and streaming of the local station MAC address using OpenConfig.

    [For state sensor, see Junos YANG Data Model Explorer. For OpenConfig configuration, see Mapping OpenConfig System Management Model Commands to Junos Configuration.]

  • Platform reboot and switchover sensor support (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports the data model openconfig-platform.yang (versions 0.15.0, 0.17.0, and 0.18.0) to stream state data and statistics related to component reboot and switchover activities.

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

  • QoS configuration and streaming with OpenConfig (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports additional leaves for the configuration and streaming of QoS statistics with OpenConfig for the following features:

    • MPLS classifiers

    • Classifier interface binding

    • Rewrite rules

    • Scheduler policies

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

    For OpenConfig configuration, see Mapping OpenConfig QoS Commands to Junos Configuration.]

  • Streaming telemetry for hardware components using OpenConfig (PTX10001-36MR, PTX10004, PTX10008 and PTX10016)—Junos OS Evolved Release 23.4R1 supports telemetry streaming for the following leaves based on the OpenConfig data model openconfig-platform.yang (version 0.19.0):

    • /components/component/fabric/state/power-admin-state

    • /components/component/controller-card/state/power-admin-state

    Support for the following leaves will be extended to all relevant hardware components:

    • /components/component/state/mfg-name

    • /components/component/state/type

    [See Junos YANG Data Model Explorer.]

  • Support for YANG data models in a single package and repository (PTX10008)—Starting in Junos OS Evolved Release 23.4R1, we provide all YANG data models for a given OS and release in a single download package and GitHub repository. The package and repository include the native configuration, state, and RPC data models and the OpenConfig and IETF data models that the OS supports. You can access the YANG data models from the Juniper/yang GitHub repository or the Juniper Networks download site.

    [See Understanding Junos YANG Modules and GitHub Resources.]

  • STP OpenConfig and operational state sensor support (ACX7024, ACX7100-32C, ACX7100-48L,ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports OpenConfig STP configurations and sensors based on the OpenConfig data model openconfig-spanning-tree (version 1.0, revision 0.3.1).

    [For OpenConfig configuration, see Mapping OpenConfig STP Commands to Junos Configuration. For state sensors, see Junos YANG Data Model Explorer.]

  • Telemetry streaming of operational state data for syslog messages (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016)—Junos OS Evolved Release 23.4R1 supports telemetry streaming of operational state data for syslog messages to an external gNMI collector. Sensors are based on the native Junos data model under the /state/system/syslog/messages/ hierarchy. You can stream data using ON_CHANGE and TARGET_DEFINED modes.

    [See Junos YANG Data Model Explorer.]

  • Upgrade of OpenConfig models for routing instances (ACX7100-32C, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.4R1 supports an upgrade for the following OpenConfig models:

    • openconfig-local-routing.yang to version 2.0.0.

    • openconfig-routing-policy.yang to version 3.3.0.

    The upgraded models introduce new leaves for operational state sensors and configuration in the following areas:

    • Inter-instance policies

    • Route limits

    • Router advertisement

    • Local aggregates

    • Static routes

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

    For OpenConfig configuration, see Mapping OpenConfig Network Instance Commands to Junos Configuration.]