Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Enhanced memory monitoring with configurable thresholds and improved alarm validation (EX2300-C, EX3400, EX4100-24P, EX4100-24T, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-48MP, EX4650, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, SRX2300, SRX4200, SRX4300, SRX4600, SRX4700, and SRX5800)—You can monitor system free pages and memory swap usage more efficiently to prevent issues related to memory shortages. The enhanced validation process reduces false alarm triggers. Additionally, you can set user-configurable thresholds for monitoring the virtual memory size (VSZ) of processes, with events categorized based on severity.

    Use the set system monitor memory process (minor/major/critical)-event threshold <process-name> memory-limit <threshold> command to configure these thresholds. Alarms are integrated with eventd and alarmd infrastructure and can be viewed using the show system alarms command. To view jsysmond events, use the show system monitor memory events all command.

    [See https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/command/show-system-monitor-memory-events.html.]

  • Enhanced telemetry with multiple gRPC servers and multiport gRPC services (EX2300, EX2300-C, EX2300-MP, EX2300-VC, EX3400, EX3400-VC, EX4000-8P, EX4000-12P, EX4000-12T, EX4000-12MP, EX4000-24MP, EX4000-48MP, EX4000-24P, EX4000-24T, EX4000-48P, EX4000-48T, EX4100-24MP, EX4100-24P, EX4100-24T, EX4100-48MP, EX4100-48P, EX4100-48T, EX4100-F-12P, EX4100-F-12T, EX4100-F-24P, EX4100-F-24T, EX4100-F-48P, EX4100-F-48T, EX4100-H-12MP, EX4100-H-12MP-DC, EX4100-H-24F, EX4100-H-24F-DC, EX4100-H-24MP, EX4100-H-24MP-DC, EX4300-MP, EX4300VC, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48MXP, EX4400-48P, EX4400-48T, EX4400-48XP, EX4600-VC, EX4650, EX4650-48Y-VC, EX9204, EX9208, EX9214, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10004, MX10008, cSRX, SRX300, SRX320, SRX340, SRX345, SRX380, SRX1500, SRX1600, SRX2300, SRX4100, SRX4200, SRX4300, SRX4600, SRX4700, SRX5400, SRX5600, SRX5800, and vSRX 3.0)—You can configure multiple gRPC servers with distinct services, listening addresses, and ports using the Junos Telemetry Interface. This feature enhances control over service management and telemetry data collection. You can also configure TLS certificates for secure communications. Use CLI commands to set listening addresses and ports and secure communications through TLS certificates. For example, you can configure a server to listen on a specific port and serve only designated gRPC services, enhancing flexibility and security in your telemetry setup.

  • Telemetry sensor support for IFL and IFL set statistics from CUPS and user plane (MX204, MX240, MX304, MX480, MX960, MX10003, MX10004, and MX10008)—You can monitor and export queue statistics and dynamic interface information for logical interfaces (IFLs) and logical interface sets (IFLsets) from the CUPS and user plane using telemetry sensor subscriptions. This feature enables you to collect and analyze queue statistics for IFLs and IFLsets efficiently. By leveraging the same sensor path tree and data model as integrated broadband network gateway (BNG), you can seamlessly extract these statistics and send them to an external collector. This functionality enhances your ability to monitor and manage network performance effectively by providing detailed ON_CHANGE telemetry data. For sensor paths, see Junos YANG Data Model Explorer.

  • Telemetry support for native SRv6 data model in SRv6 manager (MX10004 and MX10008)—You can enhance network telemetry by using the native Segment Routing for IPv6 (SRv6) data model for SRv6 base, facilitating detailed monitoring and management. The SRv6 manager in the routing protocol process (rpd) streams various XPaths from this model, providing comprehensive data about locators, node capabilities, and local SIDs. With this feature, you can efficiently monitor SRv6 performance metrics and improve network management and troubleshooting. Additionally, the show srv6 local-sidsCLI operational command has been introduced to display a consolidated list of local segment identifiers (SIDs) allocated by various protocols and applications from the SRv6 manager.

    For a complete list of sensors, see Junos YANG Data Model Explorer.]

    .

  • OpenConfig telemetry sensors for DHCP relay statistics (MX204, MX304, MX150, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, and MX2020)—You can monitor DHCP relay performance on your network by using OpenConfig telemetry sensors. For both DHCPv4 and DHCPv6, you can use only per-interface statistics sensors that stream data about total-dropped packets, invalid opcodes, and DHCP message types.This implementation supports comprehensive monitoring for Business Edge and Broadband Edge use cases, enabling you to track and aggregate critical DHCP relay statistics, ensuring efficient network management and troubleshooting.

    [See Junos YANG Data Model Explorer.]

  • Per-segment-list telemetry support for colored and uncolored SR-TE tunnels (MX10003, MX10004, MX10008, MX10016, and MX2008)—You can configure per-segment-list sensors in segment routing–traffic engineering (SR-TE) tunnels to generate sensor IDs and collect traffic statistics from both ingress and transit points.The feature generates unique sensor IDs for each segment-list and provides the option to disable specific sensors.Additionally,updated SR-TE displays and route installations reflect per-path sensor information, ensuring comprehensive visibility and management of network telemetry.

    [See https://www.juniper.net/documentation/us/en/software/junos/interfaces-telemetry/topics/concept/srv6_traffic_sensor_telemetry.html.]

  • Leaf-level resource configuration support for data export in telemetry(MX301, MX304, MX480, MX960, MX10004, and MX10008)—You can configure leaf-level resource paths for telemetry data export on network devices, reducing computational overhead and bandwidth usage. This feature supports selective querying of specific data elements,such as interface operational status or packet counters. The feature removes the need of exporting data for all instances of a resource. By focusing on relevant leaf devices, you obtain precise information efficiently, enhancing performance of telemetry collectors. Use the following XPath-based resource filters to further refine data queries for sensors using advanced forwarding technologies to stream Packet Forwarding Engine performance data:

    • Precise leaf such as /interfaces/interface[name='et-1/0/35']/state/counters/in-pkts

    • Container within the path such as /interfaces/interface[name='et-1/0/35']/state/counters/

    • List within the path /interfaces/interface/

    • Exported leafs for IFD/IFL/Queues

    Note that leaf-level support is applicable to both the RPC developed by Google (gRPC) and gRPC Network Management Interface (gNMI) transport modes. Leaf level subscription is not supported for leaf devices where configuration and exported paths are different.

  • XPath-based resource filtering support for Packet Forwarding Engine sensors on AFT platforms (MX301, MX304, MX480, MX960, MX10004, and MX10008)— You can use XPath-based resource filtering to selectively export telemetry data from specific instances of network device components, reducing bandwidth usage and processing time. This feature supports precise paths, full wildcards, partial wildcards, and multilevel key options. For example, you can filter data using paths like '/interfaces/interface[name=xe-0/0/0]' or wildcards such as '/interfaces/interface[name=*]'. This functionality is particularly beneficial on fully loaded devices with numerous interfaces, enabling you to target the data of interest efficiently. Note that XPath based resource filtering is applicable to both the RPC developed by Google (gRPC) and gRPC Network Management Interface (gNMI) transport modes but not to the UDP transport mode.

    [See Junos YANG Data Model Explorer.]

  • SRv6 telemetry support (MX10004 and MX10008)— You can manage complex networks by using Segment Routing for IPv6 (SRv6) telemetry, which provides essential tools and insights for high performance, security, and operational efficiency. This feature supports traffic sensor data streaming for IS-IS SRv6 segment identifiers (SIDs) or routes and SRv6 Traffic Engineering policies through a native YANG data model.By using these telemetry capabilities, you can monitor traffic statistics and enhance the management of SRv6 TE tunnels, ensuring robust network performance and reliability. Only the DEFAULT instance is supported for thistelemetry enhancement. For more information, see SRv6 and SRv6-TE Traffic Sensor Telemetry.