Junos Telemetry Interface
-
Native sensor support for 802.1x telemetry (EX2300-VC, EX3400-VC, EX4100-MP, EX4100, EX4300-MP, EX4400-MP, and EX4400)—Starting in Junos OS Release 23.4R1, we support telemetry streaming of operational state data for the 802.1x protocol based on the native Junos data model junos-state-dot1x.yang.
-
802.1X configuration and operational state sensors using OpenConfig (ACX5448, ACX5448-M, ACX5448-D, ACX710, EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100-48MP, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-48T, EX4100-F-24T, EX4100-F-12P, EX4100-F-12T, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, EX4650-48Y-VC, MX204, MX240, MX304, MX480, MX960, MX10003,MX10004,MX10008, MX10016, MX2008, MX2010, MX2020, and QFX10002-60C)—Starting in Junos OS Release 23.4R1, we support configuration and telemetry streaming of operational state data based on the OpenConfig data model openconfig-if-8021x.yang.
[For state sensors, see Junos YANG Data Model Explorer. For OpenConfig configuration, see Mapping OpenConfig 802.1X Commands to Junos Configuration.]
-
Firewall filter OpenConfig configuration support (EX9204, EX9208, EX9214, MX204, MX240, MX480, MX960, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—Junos OS Release 23.4R1 supports OpenConfig firewall filter (also known as access control list) configurations based on the OpenConfig data models openconfig-acl.yang (version 1.2.2) and openconfig-network-instance.yang (version 1.4.0).
[See Mapping OpenConfig Firewall Filter Commands to Junos Configuration.]
-
VLAN telemetry support for VLAN group name (EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100-48MP, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-48T, EX4100-F-24T, EX4100-F-12P, EX4100-F-12T, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, and EX4650-48Y-VC—Starting in Junos OS Release 23.4R1, we now support the new leaf
vlan-group-name
. Use the sensor /state/protocols/dot1x/interfaces/interface/authenticated-sessions/authenticated-session/<vlan-group-name> in a subscription to stream this value from a Juniper device to a collector.[For sensors, see Junos YANG Data Model Explorer.]
- Per-group TCAM utilization telemetry, CLI, and syslog support
(EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100-48MP, EX4100-24MP,
EX4100-48P, EX4100-48T, EX4100-24P, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-48T,
EX4100-F-24T, EX4100-F-12P, EX4100-F-12T, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T,
EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, and EX4400-48T)—Starting in Junos OS
Release 23.4R1, we now support per- group TCAM utilization statistics. In network
environments with high throuput and low latency, Packet Forwarding Engine errors,
statistics, and status are critical. This feature provides per-group TCAM statistics and
also triggers a system log when TCAM consumption reaches approximately 90% for a group.
To stream statistics to a collector, subscribe with the sensor /junos/system/linecard/npu/memory/. To specify groups to export, use the existing Junos configuration statement
set forwarding-options pfe-sensor npu-memory resource-list resource-list
. If you do not specify groups, the default action exports all active groups in the system.You can use the Junos operational mode command
show pfe filter hw summary
to see group information, too.[See Junos YANG Data Model Explorer for sensors and show pfe filter hw summary and resource-list].
-
New native data model supporting DHCP security (EX2300-VC, EX3400-VC, EX4100-48MP, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-24T, EX4100-F-12P, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, and EX4400-48T)—Starting in Junos OS Release 23.4R1, we support the new native data model junos-state-dhcp-security.
[For state sensors, see Junos YANG Data Model Explorer.]
-
STP OpenConfig and operational state sensor support (ACX710, ACX5448, ACX5448-M, ACX5448-D, EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100-48MP, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-48T, EX4100-F-24T, EX4100-F-12P|EX4100-F-12T, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, EX4650-48Y-VC, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, QFX10002, QFX10002-60C, QFX10008, and QFX10016)—Starting in Junos OS Release 23.4R1, we support OpenConfig STP configurations and sensors based on the OpenConfig data model openconfig-spanning-tree (Version 1, Revision 0.3.1).
[For OpenConfig configuration, see Mapping OpenConfig STP Commands to Junos Configuration. For state sensors, see Junos YANG Data Model Explorer.]