Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Configure an IP source address and routing instance for legacy gRPC dial-out connections (QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—Junos OS Evolved Release 23.4R2 supports configuring a source IP address and routing instance for legacy Remote Procedure Call (gRPC) service dial-out connections. In prior releases supporting 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.]

  • Telemetry for IPv4 and IPv6 traffic statistics (QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—Starting from Junos OS Evolved Release 23.4R2, you can stream IPv4 and IPv6 transit statistics using the native resource path /junos/system/linecard/interface/traffic or the OpenConfig resource path /interfaces/interface/. You can export the following fields are exported:

    • if_in_ipv4pkts

    • if_in_ipv4_1sec_pkts

    • if_in_ipv4_bytes

    • if_in_ipv4_1sec_octets

    • if_out_ipv4pkts

    • if_out_ipv4_1sec_pkts

    • if_out_ipv4_bytes

    • if_out_ipv4_1sec_octets

    • if_in_ipv6pkts

    • if_in_ipv6_1sec_pkts

    • if_in_ipv6_bytes

    • if_in_ipv6_1sec_octets

    • if_out_ipv6pkts

    • if_out_ipv6_1sec_pkts

    • if_out_ipv6_bytes

    • if_out_ipv6_1sec_octets

    To enable transit statistics for the physical port, you must configure route accounting. To enable IPv4 route accounting or IPv6 route accounting, include the route-accounting statement at the [edit forwarding-options family family-name] hierarchy level.

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

  • Telemetry for IPv4 and IPv6 traffic statistics (QFX5130-48C)—Starting from Junos OS Evolved Release 23.4R2, you can stream hardware Routing Engine-based sensors using Junos telemetry interface (JTI). Subscribe to the /components/ sensor to stream hardware operational states for the Routing Engines, power supply units (PSUs), control boards, FPCs, and PICs.

    [For sensors, see Junos YANG Data Model Explorer.

  • Telemetry support for CoS ingress packet drop accounting (QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—Junos OS Evolved Release 23.4R2 supports streaming counters for packets that are dropped due to ingress port congestion. Use the native sensor /junos/system/linecard/interface/traffic to stream counters for priority-based flow control (PFC), explicit congestion notification (ECN), and ingress drops. Use the native sensor /junos/system/linecard/qmon-sw/ to stream the priority group (PG) buffer utilization. You can stream counters for PFC, ECN, and ingress drops by means of OpenConfig using the sensor /interfaces/interface/.

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