close
keyboard_arrow_left
Table of Contents
- Introduction
- Cover Page
- play_arrow Junos OS Release Notes for ACX Series
- play_arrow Junos OS Release Notes for cPCE
- play_arrow Junos OS Release Notes for cRPD
- play_arrow Junos OS Release Notes for cSRX
- play_arrow Junos OS Release Notes for JRR Series
- play_arrow Junos OS Release Notes for MX Series
- play_arrow What's New
- Hardware
- Authentication and Access Control
- Chassis
- Class of Service
- Dynamic Host Configuration Protocol
- EVPN
- Forwarding Options
- High Availability
- Interfaces
- Juniper Extension Toolkit (JET)
- Junos OS API and Scripting
- Junos Telemetry Interface
- MPLS
- Network Management and Monitoring
- Precision Time Protocol (PTP)
- Public Key Infrastructure (PKI)
- Routing Policy and Firewall Filters
- Routing Protocols
- Securing GTP and SCTP Traffic
- Serviceability
- Services Applications
- Source Packet Routing in Networking (SPRING) or Segment Routing
- Software Installation and Upgrade
- Subscriber Management and Services
- Additional Features
- What's Changed
- Known Limitations
- Open Issues
- Resolved Issues
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for NFX Series
- play_arrow Junos OS Release Notes for QFX Series
-
- play_arrow What's New
- Hardware
- Application Identification (AppID)
- Chassis
- Flow-Based and Packet-Based Processing
- High Availability
- Interfaces
- Juniper Advanced Threat Prevention Cloud (ATP Cloud)
- Juniper Extension Toolkit (JET)
- J-Web
- Network Management and Monitoring
- Public Key Infrastructure (PKI)
- Serviceability
- Software Installation and Upgrade
- VPNs
- Additional Features
- What's Changed
- Known Limitations
- Open Issues
- Resolved Issues
- Migration, Upgrade, and Downgrade Instructions
- Documentation Updates
- play_arrow Junos OS Release Notes for vSRX
- Licensing
- Finding More Information
- Requesting Technical Support
- Revision History
list Table of Contents
Junos Telemetry Interface
date_range
15-Aug-24
- OpenConfig MAC address and MAC address and IP path sensor support (ACX710, ACX5448, ACX5448-M, ACX5448-D, EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-48MP, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-24T, EX4100-F-12P, EX4100-F-48T, EX4100-F-12T, EX4300-MP, EX4300VC, EX4400-24MP, EX4400-24P, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, EX4650-48Y-VC, MX150, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX, QFX10002-60C, QFX5100VC, QFX5110, QFX5110-VC, QFX5110-VCF, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, QFX5120-48YM, QFX5200, QFX5210, QFX5500, QFX10002, QFX10008, and QFX10016)—Junos OS Release 24.2R1 supports the streaming of telemetry MAC address and MAC address and IP path data from the forwarding database to a collector using the OpenConfig resource path /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).
- Hardware resource threshold monitoring for capacity
planning (EX4100-48MP, EX4400-24MP, EX4650, QFX5120-32C, QFX5120-48T, QFX5120-48Y, and
QFX5120-48YM0)—Junos OS Release 24.2R1 supports hardware resource threshold
monitoring. Using this feature, you can monitor hardware resource utilization. Advance
knowledge about resource utilization nearing or crossing a maximum capacity provides time
for you to act and prevent network disruption and traffic loss.
Use the
system packet-forwarding-options hw-resource-monitor resource-listconfiguration statement at the[edit]hierarchy level to create a list of hardware resources that you want to monitor. Once configured, periodic resource monitoring ocurs at the polling interval you set.View the monitored data using operational mode commands or use Junos Telemetry interface (JTI) to send data from your device to a collector using the resource path /junos/system/linecard/npu/memory/.
[See Configure Hardware Threshold Monitoring for Capacity Planning. For sensors, see Junos YANG Data Model Explorer.]
- Chassis and event telemetry sensor support (EX4100-24MP,
EX4100-24P, EX4100-48MP, EX4100-48P, EX4100-24T, EX4100-48T, EX4100-F-24P, EX4100-F-48P,
EX4100-F-12P, EX4100-F-12T, EX4100-F-24T, EX4100-F-48T, EX4400-24MP, EX4400-24P,
EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, and EX4400-48T)—Junos OS
Release 24.2R1 supports the Routing Engine chassis-related sensors under the resource path
/components/component/ and the events data sensors under the native
resource path /junos/events/event/. You can stream data from a device
to a collector using native (UDP) sensors, Juniper proprietary Remote Procedure Call (gRPC)
service, or gRPC Network Management Interface (gNMI).
[For sensors, see Junos YANG Data Model Explorer.]
- Native support for interfaces and chassis sensors (EX9204, EX9208, and EX9214)—Junos OS Release 24.2R1 supports native streaming of operational state statistics and counters for chassis and interfaces using new Junos-specific sensor paths. To stream data, use the sensors /state/chassis/ and /state/interfaces/.
