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 OpenConfig MAC address and MAC address and IP path sensor (ACX7024, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 24.2R1 supports streaming telemetry data for MAC addresses and MAC addresses and IP paths from the forwarding database to a collector using the resource path (sensor) /network-instances/network-instance/fdb/. This feature is based on data models openconfig-network-instance.yang (version 1.2.0) and openconfig-network-instance-l2.yang (version 1.2.0).

    [See Junos YANG Data Model Explorer.]

  • Alarms resource path enhanced with hardware component names (PTX10001-36MR, PTX10003, PTX10004, and PTX10008)—Junos OS Evolved Release 24.2R1 enhances the /system/alarms/alarm/state/ resource path to include hardware component names found in the OpenConfig data model platform.yang. For example, component names in the following format are also displayed at the same level in the alarms resource path for greater accuracy:
    • /components/component[name= ‘CHASSIS0:FPC0:PIC1:PORT2’]/port
    • /components/component[name= ‘CHASSIS0:RE0’]/controller-card
    • /components/component[name= ‘CHASSIS0:RE0:FPC1’]/linecard
    • /system/alarms/alarm/state/resource CHASSIS0:RE0:FPC1

    [See Junos YANG Data Model Explorer.]

  • Platform telemetry sensor support (PTX10004 and PTX10008)—Junos OS Evolved Release 24.2R1 supports streaming, ON_CHANGE, INITIAL_SYNC, and TARGET_DEFINED subscription modes as well as zero-suppression. Sensors are supported for all PEMs and fans.

    These sensors are supported:

    • /components/component/properties/property
    • /components/component/state/temperature
    • /components/component/state
    • /components/component/fan/state
    • /components/component/power-supply/state

    [See Understanding OpenConfig and gRPC on Junos Telemetry Interface. For sensors, see Junos YANG Data Model Explorer.]

  • OpenConfig configuration and sensor support for AFI-SAFI policies (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 24.2R1 supports export and import policies for address family indicator (AFI) and subsequent address family identifier (SAFI). OpenConfig support is for IPv4 and IPv6 unicast address families. Junos CLI-configured policies have priority over those configured with OpenConfig. For example, if different policies are configured for the same neighbor, one through an OpenConfig configuration and the other through a Junos CLI configuration, the latter policy takes effect.

    We support these OpenConfig configurations:

    • /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi<IPV4/V6_UNICAST>/apply-policy/config/import-policy

    • /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi<IPV4/V6_UNICAST>/apply-policy/config/export-policy

    We support these state sensors:

    • /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi<IPV4/V6_UNICAST>/apply-policy/state/import-policy

    • /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi<IPV4/V6_UNICAST>/apply-policy/state/export-policy

    [For configurations, see Mapping OpenConfig BGP Commands to Junos Configuration. For sensors, see Junos YANG Data Model Explorer.]

  • Support for native physical interface state sensors in the genstate YANG data models (PTX10003)—Junos OS Evolved Release 24.2R1 supports subscribable YANG data models for operational state on Junos devices. The genstate YANG models expose a subset of show command data through the gNMI subscribe RPC. A gNMI telemetry collector can subscribe to the resource paths defined in the published models to query for specific state data. This feature provides genstate YANG data model support for native physical interface state sensors.

    [See Junos Genstate YANG Data Models and gNMI Genstate Subscription.]

  • Support for native LLDP, DCBX, MVRP, and MAC rewrite sensors in genstate YANG data models (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 24.2R1 supports subscribable YANG data models for operational state on Junos devices. The genstate YANG models expose a subset of show command data through the gNMI subscribe RPC. A gNMI telemetry collector can subscribe to the resource paths defined in the published models to query for specific state data. This feature provides genstate YANG data model support for Link Layer Discovery Protocol (LLDP), Data Center Bridging Capability Exchange (DCBX), Multiple VLAN Registration Protocol (MVRP), and Layer 2 protocol tunneling (L2PT) MAC rewrite.

    [See Junos Genstate YANG Data Models and gNMI Genstate Subscription.]

  • Support for streaming Packet Forwarding Engine statistics at the NPU-level (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 24.2R1 supports streaming Packet Forwarding Engine statistics per network processing unit (NPU) and per Flexible PIC Concentrator (FPC). Before this release, ASIC statistics were collected for all NPUs and reported as a single counter for each FPC. This feature provides refined output for ASIC counters. To stream statistics, include the FPC and NPU name in the sensor path; for example: /components/component[name='FPC0:NPU0']/properties/property[name='hwds-normal']/. The following leaves are supported:

    • hwds-normal

    • hwds-data-error

    • hwds-tcp-error

    • hwds-illegal-nh

    • hwds-invalid-iif

    • hwds-fabric

    [See Junos YANG Data Model Explorer.]
  • Configure an IP source address and routing instance for legacy gRPC dial-out connections (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 24.2R1 supports configuring a source IP address and routing instance for remote procedure call (gRPC) service dial-out connections. In earlier releases that support legacy gRPC dial-out, the outgoing interface IP address is used as the source address without an option to configure a source IP address. This feature supports FLEX Deployments, providing the ability to send dial-out from the router's specified IP address or interface address (such as a loopback0 address).

    Use the routing-instance statement at the [edit services analytics export-profile profile-name] hierarchy level and the local-address ipv4 or ipv6 address statement at the [edit services analytics export-profile profile-name] hierarchy level.

    [See Using gRPC Dial-Out for Secure Telemetry Collection, routing-instance, and local-address.]