Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface)

Starting in Junos OS Evolved Release 21.4R1, streaming statistics by means of gRPC and gNMI is supported on PTX10008 and PTX10016 routers.

Sensor for Internet Key Exchange (IKE) security statistics.

When you configure a subscription request, use the reporting-interval parameter to configure the interval (in seconds) in which statistics are reported.

Starting with Junos OS Release 18.1R1, MX Series routers are supported.

• remote-ip

• local-ip

• number-ipsec-sa-created

• number-ipsec-sa-deleted

• number-ipsec-sa-rekey

• exchange-type

• in-bytes

• in-packets

• out-bytes

• out-packets

• delete-payload-received

• delete-payload-transmitted

• dpd-request-payload-received

• dpd-request-payload-transmitted

• dpd-response-payload-received

• dpd-response-payload-transmitted

• dpd-response-payload-missed

• dpd-response-payload-maximum-delay

• dpd-response-seq-payload-missed

• invalid-spi-notify-received

• invalid-spi-notify-transmitted

• routing-instance

Sensor for kernel routing table socket (RTSOCK) information.

Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253, MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000, PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, and PTX5000 with RE-PTX-X8-64G are supported.

You can also add the following as the end path for /junos/kernel/rtsock/:

• total-error-cnt

• total-veto-cnt

Starting with Junos OS Release 19.1R1, periodic streaming on QFX10002 switches and PTX10002 routers is supported.

Sensor for the health monitoring configuraiton.

Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Sensor for health monitoring data.

Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Sensor for Packet Forwarding Engine dynamic tunnels statistics.

The statistics are used to report various network element performance metrics in a scalable and efficient way, providing visibility into Packet Forwarding Engine errors and drops.

A timestamp indicating when the counters were last reset is included with all the exported data to allow collectors to determine if and when a reset event happened; for example, if the Packet Forwarding Engine hardware restarted.

Exported statistics are similar to the output of the operational mode command show nhdb hw dynamic-ip-tunnels.

Starting with Junos OS Release 17.4R1, MX Series devices are supported on gRPC services, with the exception of MX80 and MX104 routers. These routers support UDP export only for this sensor. To configure UDP export, include the sensor /junos/services/ip-tunnel/usage/ in the sensor (Junos Telemetry Interface) configuration statement at the [edit services analytics] hierarchy level.

Sensor for LSP statistics. On MX Series routers only, the following are also supported: bidirectional LSPs for ultimate-hop popping (UHP).

Starting with Junos OS Release 17.2R1, QFX10000 switches and PTX1000 routers are also supported.

Starting with Junos OS Release 17.3R1, EX9200 switches are also supported.

Starting with Junos OS Release 17.4R1 on MX Series and PTX Series routers only, statistics for bypass LSPs are also exported. Previously, only statistics for ingress LSPs were exported.

Starting with Junos OS Release 18.2R1, QFX5100, QFX5110, and QFX5200 switches are also supported.

Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650 switches are also supported.

Starting with Junos OS Release 18.4R1, EX4600 switches are also supported.

Starting with Junos OS Release 19.1R1, PTX10001-20C routers support RSVP bypass LSPs originating at the transit node

Starting with Junos OS Release 19.1R1, periodic streaming on QFX10002 switches and PTX10002 routers is supported.

Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported.

Starting with Junos OS Release 19.2R1, ACX6360 routers are supported.

Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services.

Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.

Starting with Junos OS Evolved Release 20.2R1, periodic streaming using gRPC services with PTX10001 routers is supported.

For bypass LSPs, the following are exported:

• Bypass LSP originating at the ingress router of the protected LSP.

• Bypass LSP originating at the transit router of the protected LSP.

• Bypass LSP protecting the transit LSP as well as the locally originated LSP.

When the bypass LSP is active, traffic is exported both on the bypass LSP and the ingress (protected) LSP.

Sensor for error monitoring configuration.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Sensor for error monitoring counters.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Sensor for interface burst monitoring.

Starting in Junos OS Evolved Release 19.3R1, QFX5220-128C and QFX5220-32CD switches are supported for streaming statistics on gRPC services.

You can also add the following to the end of the path to stream specific statistics for interface burst monitoring:

• rx_bytes-Total number of bytes received during the export interval.

• tx_bytes-Total number of bytes transmitted during the export interval.

• start_ts-Start timestamp for the data collection window.

• rx_peak_byte_rate-Maximum bytes rate per millisecond received from all the sampling intervals in the export interval.

• rx_peak_ts-Timestamp of the first burst.

• tx_peak_byte_rate-Maximum bytes rate per millisecond, transmitted from all the sampling intervals in the export interval.

• tx_peak_byte_ts-Timestamp of the first transmit burst.

Sensor for network processing unit (NPU) memory.

Supported on EX4650, QFX5110, QFX5120-48Y, QFX5200, and QFX5210 switches starting with Junos OS Release 21.4R1 for exporting telemetry information using gRPC or gNMI services.

You can also add the following leaves to the end of the path to stream specific statistics:

• resource_name

• size

• allocated

• utilization

Sensor for network processing unit (NPU) memory.

Supported on MX Series routers with MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards starting with Junos OS Release 19.3R1 for exporting telemetry information using gRPC services. This feature provides a different level of exported statistics in comparison to previous releases because it use the OpenConfig AFT model.

Supported on MX2010 and MX2020 routers with MX2K-MPC11E line cards starting with Junos OS Release 20.1R1 for streaming telemetry information using gRPC services.

You can also add the following to the end of the path to stream specific statistics for NPU memory:

• mem-util-edmem-size

• mem-util-edmem-allocated

• mem-util-edmem-utilization

• mem-util-idmem-size

• mem-util-idmem-allocated

• mem-util-idmem-utilization

• mem-util-bulk-dmem-size

• mem-util-bulk-dmem-allocated

• mem-util-bulk-dmem-utilization

• mem-util-next-hop-edmem-size

• mem-util-next-hop-edmem-allocated

• mem-util-next-hop-edmem-utilization

• mem-util-next-hop-bulk-dmem-size

• mem-util-next-hop-bulk-dmem-allocated

• mem-util-next-hop-bulk-dmem-utilization

• mem-util-next-hop-idmem-size

• mem-util-next-hop-idmem-allocated

• mem-util-next-hop-inline-services-free-count

• mem-util-next-hop-mobile:-timing-profile-bytes-allocated

• mem-util-next-hop-mobile:-timing-profile-allocation-count

• mem-util-next-hop-mobile:-timing-profile-free-count

• mem-util-next-hop-packet-reassembly-(rw)-bytes-allocated

• mem-util-next-hop-packet-reassembly-(rw)-allocation-count

• mem-util-next-hop-packet-reassembly-(rw)-free-count

• mem-util-next-hop-packet-reassembly---persistent-(rw)-bytes-allocated

• mem-util-next-hop-packet-reassembly---persistent-(rw)-allocation-count

• mem-util-next-hop-packet-reassembly---persistent-(rw)-free-count

• mem-util-next-hop-ml-bundle-bytes-allocated

• mem-util-next-hop-ml-bundle-allocation-count

• mem-util-next-hop-ml-bundle-free-count

• mem-util-next-hop-ddos-scfd-params-bytes-allocated

• mem-util-next-hop-ddos-scfd-params-allocation-count

• mem-util-next-hop-ddos-scfd-params-free-count

• mem-util-next-hop-vbf-bytes-allocated

• mem-util-next-hop-vbf-allocation-count

• mem-util-next-hop-vbf-free-count

• mem-util-next-hop-ptp-ieee-1588-nhs-bytes-allocated

• mem-util-next-hop-ptp-ieee-1588-nhs-allocation-count

• mem-util-next-hop-ptp-ieee-1588-nhs-free-count

• mem-util-next-hop-cos-bytes-allocated

• mem-util-next-hop-cos-allocation-count

• mem-util-next-hop-cos-free-count

• mem-util-next-hop-inline-hash-sessions-bytes-allocated

• mem-util-next-hop-inline-hash-sessions-allocation-count

• mem-util-next-hop-inline-hash-sessions-free-count

• mem-util-next-hop-inline-mdi-bytes-allocated

• mem-util-next-hop-inline-mdi-allocation-count

• mem-util-next-hop-inline-mdi-free-count

• mem-util-next-hop-cos-enhanced-priority-bytes-allocated

• mem-util-next-hop-cos-enhanced-priority-allocation-count

• mem-util-next-hop-cos-enhanced-priority-free-count

• mem-util-firewall-fw-bytes-allocated

• mem-util-firewall-fw-allocation-count

• mem-util-firewall-fw-free-count

• mem-util-counters-fw-counter-bytes-allocated

• mem-util-counters-fw-counter-allocation-count

• mem-util-counters-fw-counter-free-count

• mem-util-counters-fw-policer-bytes-allocated

• mem-util-counters-fw-policer-allocation-count

• mem-util-counters-fw-policer-free-count

• mem-util-counters-ifd-error-cntr-bytes-allocated

• mem-util-counters-ifd-error-cntr-allocation-count

• mem-util-counters-ifd-error-cntr-free-count

• mem-util-counters-nh-cntr-bytes-allocated

• mem-util-counters-nh-cntr-allocation-count

• mem-util-counters-nh-cntr-free-count

• mem-util-counters-ifl-cntr-bytes-allocated

• mem-util-counters-ifl-cntr-allocation-count

• mem-util-counters-ifl-cntr-free-count

• mem-util-counters-bridge-domain-counter0-bytes-allocated

• mem-util-counters-bridge-domain-counter0-allocation-count

• mem-util-counters-bridge-domain-counter0-free-count

• mem-util-counters-bridge-domain-counter0-free-count

• mem-util-counters-bridge-domain-cntr-bytes-allocated

• mem-util-counters-bridge-domain-cntr-allocation-count

• mem-util-counters-bridge-domain-cntr-free-count

• mem-util-counters-sample-inline-params-bytes-allocated

• mem-util-counters-sample-inline-params-allocation-count

• mem-util-counters-sample-inline-params-free-count

• mem-util-counters-services-counters-bytes-allocated

• mem-util-counters-services-counters-allocation-count

• mem-util-counters-services-counters-free-count

• mem-util-counters-exception-counter-bytes-allocated

• mem-util-counters-exception-counter-allocation-count

• mem-util-counters-exception-counter-free-count

• mem-util-counters-issu-policer-bytes-allocated

• mem-util-counters-issu-policer-allocation-count

• mem-util-counters-issu-policer-free-count

• mem-util-counters-ddos-scfd-counters-bytes-allocated

• mem-util-counters-ddos-scfd-counters-allocation-count

• mem-util-counters-ddos-scfd-counters-free-count

• mem-util-counters-ip-reassembly-counter-bytes-allocated

• mem-util-counters-ip-reassembly-counter-allocation-count

• mem-util-counters-ip-reassembly-counter-free-count

• mem-util-hash-hash-edmem-overhead-bytes-allocated

• mem-util-hash-hash-edmem-overhead-bytes-allocated

• mem-util-hash-hash-edmem-overhead-bytes-allocated

• mem-util-hash-hash-edmem-overhead-bytes-allocated

• mem-util-hash-hash-edmem-overhead-bytes-allocated

• mem-util-hash-hash-edmem-overhead-allocation-count

• mem-util-hash-hash-edmem-overhead-free-count

• mem-util-hash-hash-edmem-bkt-bytes-allocated

• mem-util-hash-hash-edmem-bkt-allocation-count

• mem-util-hash-hash-edmem-bkt-free-count

• mem-util-hash-hash-edmem-rec-bytes-allocated

• mem-util-hash-hash-edmem-rec-allocation-count

• mem-util-hash-hash-edmem-rec-free-count

• mem-util-hash-hash-edmem-sideband-bytes-allocated

• mem-util-hash-hash-edmem-sideband-allocation-count

• mem-util-hash-hash-edmem-sideband-free-count

• mem-util-hash-hash-dmem-bkt-bytes-allocated

• mem-util-hash-hash-dmem-bkt-allocation-count

• mem-util-hash-hash-dmem-bkt-free-count

• mem-util-hash-hash-dmem-rec-bytes-allocated

• mem-util-hash-hash-dmem-rec-allocation-count

• mem-util-hash-hash-dmem-rec-free-count

• mem-util-hash-hash-dmem-sideband-bytes-allocated

• mem-util-hash-hash-dmem-sideband-allocation-count

• mem-util-hash-hash-dmem-sideband-free-count

• mem-util-encaps-ueid-bytes-allocated

• mem-util-encaps-ueid-allocation-count

• mem-util-encaps-ueid-free-count

• mem-util-encaps-ueid-shared-bytes-allocated

• mem-util-encaps-ueid-shared-bytes-allocated

• mem-util-encaps-ueid-shared-allocation-count

• mem-util-encaps-ueid-shared-free-count

• mem-util-encaps-fabric-bytes-allocated

• mem-util-encaps-fabric-allocation-count

• mem-util-encaps-fabric-free-count

• mem-util-services-nh-inline-jflow-sample-rr-(svcs)-bytes-allocated

• mem-util-services-nh-inline-jflow-sample-rr-(svcs)-allocation-count

• mem-util-services-nh-inline-jflow-sample-rr-(svcs)-free-count

• mem-util-services-nh-inline-jflow-sample-nh-(svcs)-bytes-allocated

• mem-util-services-nh-inline-jflow-sample-nh-(svcs)-allocation-count

• mem-util-services-nh-inline-jflow-sample-nh-(svcs)-free-count

Sensor for network processing unit (NPU) memory, NPU memory utilization, and total memory available for each memory type.

Supported on QFX10000 switches and PTX1000 routers starting with Junos OS Release 17.2R1.

Supported on EX9200 switches starting with Junos OS Release 17.3R1.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers and PTX1000 and PTX10000 routers are supported on gRPC and gNMI services.

The OpenConfig path is /components/component[name="FPC<fpc-id>:NPU<npu-id>"] /properties/property/

You can also add the following to the end of the path to stream specific statistics for NPU memory:

• [name="mem-util-<memory-name>-size"]/value

• [name="mem-util-<memory-name>-bytes-allocated"]/value

• [name="mem-util-<memory-name>-utilization"]/value

• [name="mem-util-<partition-name>-< app-name>-allocation-count"]/value

• [name="mem-util-<partition-name>-< app-name>-bytes-allocated"]/value

• [name="mem-util-<partition-name>-< app-name>-free-count"]/value

You can also add the following to the end of the path to stream specific statistics for NPU:

• [name="util-<memory-name>-average-util">/value

• [name="util-<memory-name>-highest-util">/value

• [name="util-<memory-name>-lowest-util">/value

• [name="util-<memory-name>-average-cache-hit-rate">/value

• [name="util-<memory-name>-lowest-cache-hit-rate">/value

• [name="util-<packet-identifier>-rate">/value

You can also export the following statistics for NPU memory for PTX routers only

• pfe_name

• combined_pool_name

• combined_size

• combined_usage_cnt

• combined_utilization

• global_pool_name

• global_usage_cnt

• global_alloc_cnt

• global_free_cnt

• local_pool_name

• local_usage_cnt

• local_alloc_cnt

• local_free_cnt

Sensor to export abstracted fabric (AF) interface-specific load-balancing and fabric queue statistics. This sensor is only supported for in node virtualization configurations on MX routers with an AF Interface as the connecting link between guest network functions (GNFs).The sensor also reports aggregated statistics across all AF interfaces hosted on a source packet forwarding engine of local guest GNFs along with the fabric statistics for all traffic ingressing from and egressing to the fabric from that the packet forwarding engine.

Supported on MX480, MX960, MX2010, MX2020, MX2008 and MX-ELM routers with Junos OS Release 18.4R1.

Sensor for CPU memory. This sensor exports the CPU and memory utilization per process and CPU usage for threads per process. The current implementation is Linux-based; therefore, the export information and gathered output format differs significantly from this sensor’s performance on previous platforms.

Supported on MX Series routers with MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards starting with Junos OS Release 19.3R1 for exporting telemetry information using gRPC services. This feature provides a different level of exported statistics in comparison to previous releases because it use the OpenConfig AFT model.

Supported on MX2010 and MX2020 routers with MX2K-MPC11E line cards starting with Junos OS Release 20.1R1 for streaming telemetry information using gRPC services.

Supported on EX2300, EX2300-MP, and EX3400 switches starting with Junos OS Release 20.2R1 and later for streaming telemetry information using gRPC services.

Supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1 and later for INITIAL_SYNC statistics using gNMI services.

The statistics exported from this sensor are found in the following operational mode commands: show system info, show system processes, and show system cpu.

Sensor for CPU memory.

Supported on QFX10000 switches and PTX1000 routers starting with Junos OS Release 17.2R1.

Supported on EX9200 switches starting with Junos OS Release 17.3R1.

Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1.

Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1.

Supported on EX4600 switches starting with Junos OS Release 18.4R1.

Periodic streaming is supported on on QFX10002 switches and PTX10002 routers starting with Junos OS Release 19.1R1.

Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services.

Periodic streaming using gRPC services is supported on EX4300-MP switches starting with Junos OS Release 19.4R1,

Periodic streaming using gRPC services is supported on EX2300, EX2300-MP, and EX3400 switches starting with Junos OS Release 20.2R1.

You can also include the following to end of the resource path for CPU memory:

• [name="mem-util-<memory-name>-size"]/value

• [name="mem-util-<memory-name>-bytes-allocated"]/value

• [name="mem-util-<memory-name>-utilization"]/value

• [name="mem-util-<memory-name>-< app-name>-allocations"]/value

• [name="mem-util-<memory-name>-< app-name>-frees"]/value

• [name="mem-util-<memory-name>-< app-name>-allocations-failed"]/value

Sensor for NPU Memory utilization statistics.

Shown below, statistics are exported for the default FPC (FPC0). Multiples FPCs are supported. The component values and property values are names (like interface names).

Starting in Junos OS Evolved Release 19.4R1, streaming statistics using gRPC and gNMI services on PTX10008 routers is supported.

Starting in Junos OS Release 20.2R1, INITIAL_SYNC statistics using gNMI services on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches are supported.

Starting in Junos OS Evolved Release 21.4R1, streaming statistics by means of gRPC and gNMI is supported on PTX10001-36MR, PTX10004, and PTX10008 routers.

The following statistics are exported:

• /components-memory/component[name='FPC0:NPU17']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-epp-mapid-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-epp-mapid-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-epp-mapid-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-l2domain-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-l2domain-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-l2domain-utilizationn']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash00-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash00-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash00-utilization']/

• :/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash10-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash10-allocatedd']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash10-utilization']/

• :/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-slu-my-mac-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-slu-my-mac-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-slu-my-mac-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-dlu-idb-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-dlu-idb-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-dlu-idb-utilization']/ }

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-final-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-final-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-final-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-remap-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-remap-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-remap-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-refbits-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-refbits-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-refbits-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-nh-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-nh-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-nh-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-mpls-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-mpls-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name=' mem-util-jnh-mpls-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-loadbal-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-loadbal-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-loadbal-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-egress-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-egress-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-egress-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jtree-memory-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jtree-memory-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jtree-memory-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-vfilter-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-vfilter-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-vfilter-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-phyfilter-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-phyfilter-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-phyfilter-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-action-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-action-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-action-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-tcam-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name=' mem-util-flt-tcam-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-tcam-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-0-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-0-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-0-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-1-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-1-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-1-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-2-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-2-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-2-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-3-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-3-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-3-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-4-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-4-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-4-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-scv-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-scv-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-scv-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-0-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-0-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-0-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-1-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-1-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-1-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-2-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-2-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-2-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-3-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-3-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-3-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-4-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-4-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-4-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-5-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-5-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-5-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-6-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-6-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-6-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-7-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-7-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-7-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name=' mem-util-flt-beta-1-bank-0-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-0-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-0-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-1-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-1-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-1-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-2-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-2-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-2-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-3-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-3-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-3-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-4-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-4-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-4-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-5-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-5-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-5-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-6-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-6-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-6-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-7-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-7-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-7-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-kht-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-kht-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-kht-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-bft-0-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-bft-0-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-bft-0-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-plt-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-plt-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-plt-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-kht-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-kht-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-kht-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-bft-0-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-bft-0-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-bft-0-utilization']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-plt-size']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-plt-allocated']/

• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-plt-utilization']/

Sensor for NPU utilization on the Packet Forwarding Engine.

Packet Forwarding Engine utilization is exported exported as a percentage using input notifications.

The following packet statistics are also exported as part of this field:

• Loopback (pps)

• Recirculation (pps)

• WAN and host inject (pps)

• ASIC to host (pps)

Shown below, statistics are exported for the default FPC (FPC0). Multiples FPCs are supported. The component values and property values are names (like interface names).

Starting in Junos OS Evolved Release 19.4R1, streaming statistics using gRPC and gNMI services on PTX10008 routers is supported.

The following statistics are exported:

• /components-utilization/component[name='FPC0:NPU17'

• /components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-metric']

• /components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-Loopback-packet-rate']

• components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-Recirculation-packet-rate']

• /components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-Wan and Host inject-packet-rate']

• /components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-ASIC to host-packet-rate']

Packet Forwarding Engine sensor for NPU processor utilization.

Supported on MX Series routers with MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards starting with Junos OS Release 19.3R1 for streaing telemetry information using gRPC services. This feature provides a different level of exported statistics in comparison to previous releases because it uses the OpenConfig AFT model.

Supported on MX2010 and MX2020 routers with MX2K-MPC11E line cards starting with Junos OS Release 20.1R1 for streaming telemetry information using gRPC services.

Supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1 and later for INITIAL_SYNC statistics using gNMI services.

You can also include the following to the end of the resource path for NPU utilization:

• util-metric

• util-Disp 0 Pkts-packet-rate

• util-Disp 0 Pkts-average-instructions-per-packet

• util-Disp 0 Pkts-average-wait-cycles-per-packet

• util-Disp 0 Pkts-average-cycles-per-packet

• util-Disp 1 Pkts-packet-rate

• util-Disp 1 Pkts-average-instructions-per-packet

• util-Disp 1 Pkts-average-wait-cycles-per-packet

• util-Disp 1 Pkts-average-cycles-per-packet

• util-Disp 2 Pkts-packet-rate

• util-Disp 2 Pkts-average-instructions-per-packet

• util-Disp 2 Pkts-average-wait-cycles-per-packet

• util-Disp 2 Pkts-average-cycles-per-packet

• util-Disp 3 Pkts-packet-rate

• util-Disp 3 Pkts-average-instructions-per-packet

• util-Disp 3 Pkts-average-wait-cycles-per-packet

• util-Disp 3 Pkts-average-cycles-per-packet

• mem-util-EDMEM-average-util

• mem-util-EDMEM-highest-util

• mem-util-EDMEM-lowest-util

• mem-util-EDMEM-average-cache-hit-rate

• mem-util-EDMEM-highest-cache-hit-rate

• mem-util-EDMEM-lowest-cache-hit-rate

• mem-util-IDMEM-average-util

• mem-util-IDMEM-highest-util

• mem-util-IDMEM-lowest-util

• mem-util-IDMEM-average-cache-hit-rate

• mem-util-IDMEM-highest-cache-hit-rate

• mem-util-IDMEM-lowest-cache-hit-rate

• mem-util-Bulk DMEM-average-util

• mem-util-Bulk DMEM-highest-util

• mem-util-Bulk DMEM-lowest-util

• mem-util-Bulk DMEM-average-cache-hit-rate

• mem-util-Bulk DMEM-highest-cache-hit-rate

• mem-util-Bulk DMEM-lowest-cache-hit-rate

Packet Forwarding Engine sensor for NPU processor utilization.

Periodic streaming is supported on PTX10002 routers starting with Junos OS Release 19.1R1.

Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers and PTX1000 and PTX10000 routers are supported on gRPC and gNMI services.

Starting in Junos OS Evolved Release 21.4R1, streaming statistics by means of gRPC and gNMI is supported on PTX10001-36MR, PTX10004, and PTX10008 routers.

Packet Forwarding Engine sensor for physical interface traffic.

Supported on PTX Series routers starting with Junos OS Release 15.1F3. Supported on MX Series routers starting with Junos OS Release 15.1F5.

Supported on QFX10000 switches and PTX1000 routers starting with Junos OS Release 17.2R1.

Supported on EX9200 switches and MX150 routers starting with Junos OS Release 17.3R1.

Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1.

Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1.

Supported on EX4600 switches Starting with Junos OS Release 18.4R1.

Periodic streaming is supported on QFX10002 switches and PTX10002 routers starting with Junos OS Release 19.1R1.

Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches with Junos OS Release 19.2R1 on gRPC and gNMI services.

Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft.

Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported.

Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1.

Periodic streaming using gRPC services is supported on EX2300, EX2300-MP, and EX3400 switches starting with Junos OS Release 20.2R1.

INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1.

Streaming statistics using gRPC services or gNMI services is supported on PTX10008 routers starting with Junos OS Release 20.2R1.

Packet Forwarding Engine sensor for logical interface statistics.

Supported in Junos OS Release 15.1F5.

Supported QFX10000 switches starting with on Junos OS Release 17.2R1.

Supported on EX9200 switches and MX150 routers starting with Junos OS Release 17.3R1.

Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1.

Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1.

Supported on EX4600 switches starting with Junos OS Release 18.4R1.

Starting with Junos OS Release 19.1R1, periodic streaming is supported on QFX10002 switches and PTX10002 routers.

Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches with Junos OS Release 19.2R1 on gRPC and gNMI services.

Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services.

Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft.

Starting with Junos OS Release 19.4R1, periodic streaming using gRPC services with EX4300-MP switches is supported.

Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1.

Periodic streaming using gRPC services is supported on EX3400 switches starting with Junos OS Release 20.2R1.

INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1.

Sensor for interface queue statistics.

Starting with Junos OS Release 18.3R1, when a subscription is made to /interfaces on MX, EX, QFX, PTX, and ACX platforms, traffic and queue statistics are delivered in two separate sensors:

• /junos/system/linecard/interface/traffic/

• /junos/system/linecard/interface/queue/

This can reduce the reap time for non-queue data for platforms supporting Virtual Output Queues (VOQ), such as PTX Series routers.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft.

Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1.

INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1.

Sensor for interface traffic, exporting all fields except queue statistics.

Starting with Junos OS Release 18.3R1, when a subscription is made to /interfaces on MX, EX, QFX, PTX, and ACX platforms, traffic and queue statistics are delivered in two separate sensors:

• /junos/system/linecard/interface/traffic/

• /junos/system/linecard/interface/queue/

This can reduce the reap time for non-queue data for platforms supporting Virtual Output Queues (VOQ), such as PTX Series routers.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft.

Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1.

INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1.

Streaming statistics using gRPC services or gNMI services is supported on PTX10008 routers starting with Junos OS Release 20.2R1.

Sensor for physical interface express statistics.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Sensor for optical alarms. Configure this sensor for et-type-fpc/pic/port (100-Gigabit Ethernet) interfaces.

Supported on ACX6360 Universal Metro, MX Series, and PTX Series routers with a CFP2-DCO optics module starting with Junos OS Release 18.3R1. This module provides a high-density, long-haul OTN transport solution with MACSec capability.

Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services.

Sensor for G.709 optical transport network (OTN) alarms. Configure this sensor on ot-type-fpc/pic/port interfaces.

Supported on ACX6360 Universal Metro, MX Series, and PTX Series routers with a CFP2-DCO optics module starting with Junos OS Release 18.3R1. This module provides a high-density, long-haul OTN transport solution with MACSec capability.

Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services.

Sensor for congestion and latency monitoring statistics.

Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1.

Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1.

Supported on EX4600 switches starting with Junos OS Release 18.4R1.

Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services.

Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services.

Periodic streaming using gRPC services with EX4300-MP switches is supported starting with Junos OS Release 19.4R1.

Periodic streaming using gRPC services is supported on EX3400 switches starting with Junos OS Release 20.2R1.

INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1.

Sensor for inline active flow monitoring services statistics.

Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services.

When configuring inline active flow monitoring in Junos, you can apply version 9 or IPFIX flow templates to define a flow record template suitable for IPv4 or IPv6 MPLS and bridging traffic. For more information, see Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9 Flow Templates.

Supported on MX Series operating with MPC10E-15C-MRATE line-rate cards starting with Junos OS Release 19.2R1.

Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft.

Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1.

Periodic streaming using gRPC services on PTX10008 routers is supported starting with Junos OS Evolved Release 20.1R1.

/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/irb-interfaces/

Local integrated routing and bridging (IRB) interface information sensor.

Use the Telemetry Explorer tool to see leafs for this resource path.

Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.

Overlay VX-LAN tunnel information sensor. This sensor also delivers VTEP information ON_CHANGE leafs:

• source_ip_address

• remote_ip_address

• status

• mode

• nexthop-index

• event-type

• source-interface

Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.

EVPN MAC table information sensor.

Use the Telemetry Explorer tool to see leafs for this resource path.

Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.

MAC-IP or ARP-ND table sensor.

Use the Telemetry Explorer tool to see leafs for this resource path.

Starting with Junos OS Release 20.2R1, streaming statistics is supported using gRPC services with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016 switches.

Sensor for firewall filter counters and policer counters. Each line card reports counters separately.

Supported on QFX10000 switches starting with Junos OS Release 17.2R1.

Supported on PTX1000 routers and EX9200 switches starting with Junos OS Release 17.3R1.

Supported on QFX5100, QFX5110, and QFX5200 switches starting with Junos OS Release 18.2R1.

Supported on QFX5120-48Y and EX4650 switches starting with Junos OS Release 18.3R1.

Supported on EX4600 switches starting with Junos OS Release 18.4R1.

Starting with Junos OS Release 19.1R1, periodic streaming is supported on QFX10002 switches and PTX10002 routers.

Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Supported on QFX5200 switches starting with Junos OS Release 19.2R1 for streaming telemetry information using gNMI services.

Supported on MX240, MX480, and MX960 routers starting with Junos OS Release 19.3R1 for exporting telemetry information using gNMI services. This feature includes support to export telemetry data for integration with AFTTelemetry and LibTelemetry libraries with the OpenConfig model openconfig-aft.

Periodic streaming using gRPC services with EX4300-MP switches is supported starting with Junos OS Release 19.4R1.

Periodic streaming using gNMI services with PTX10003 routers is supported starting with Junos OS Evolved Release 19.4R1.

Periodic streaming using gNMI services on MX2K-MPC11E line cards on MX2010 and MX2020 routers is supported starting with Junos OS Release 20.1R1.

Periodic streaming using gRPC services is supported on EX2300, EX2300-MP, and EX3400 switches starting with Junos OS Release 20.2R1.

INITIAL_SYNC statistics using gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 20.2R1.

The following OpenConfig paths are supported:

• junos/firewall/firewall-stats/[name='filter-name']/timestamp

• /junos/firewall/firewall-stats/[name='filter-name']/ memory-usage/[name='memory-type']/allocated

• /junos/firewall/firewall-stats/[name='filter-name']/ counter-stats/[name='counter-name']/packets

• /junos/firewall/firewall-stats/[name='filter-name']/ counter-stats/[name='couner-name']/bytes

• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/out-of-spec-packets

• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/out-of-spec-bytes

• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/offered-packets

• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/offered-bytes

• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/transmitted-packets

• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/transmitted-bytes

• /junos/firewall/firewall-stats/[name='filter-name']/ hierarchical-policer-stats/[name='hierarchical-policer-name']/premium-packets (MX Series only)

• /junos/firewall/firewall-stats/[name='filter-name']/ hierarchical-policer-stats/[name='hierarchical-policer-name']/premium-bytes (MX Series only)

• /junos/firewall/firewall-stats/[name='filter-name']/ hierarchical-policer-stats/[name='hierarchical-policer-name']/aggregate-packets (MX Series only)

• /junos/firewall/firewall-stats/[name='filter-name']/ hierarchical-policer-stats/[name='hierarchical-policer-name']/aggregate-bytes (MX Series only)

Interface express sensor.

This sensor leverages statistics out of the physical interface sensor, providing faster and more frequent operational status statistics. Only the physical interfaces’ operational status from the Flexible PIC Concentrator (FPC) is collected and reported. Statistics from the Routing Engine interface are not reported.

Supported on PTX1000, PTX3000, PTX5000, and PTX10000 starting with Junos OS Release 18.1R1.

Supported on MX960, MX2010, and MX2020 routers starting with Junos OS Release 19.3R1.

Sensor for various optical interface performance metrics, such as transmit and receive power levels.

Supported on QFX10000 switches starting with Junos OS Release 17.2R1.

Supported on PTX1000 routers and EX9200 switches starting with Junos OS Release 17.3R1.

Supported on EX4650 switches starting with Junos OS Release 18.3R1.

Supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches starting with Junos OS Release 19.2R1 on gRPC and gNMI services.

Sensor to export the path name for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs.

This sensor is supported on indicated platforms up to and including Junos OS Release 17.3R1. See the following resource paths for LSP support in Junos OS Release 17.4R1 and higher:

• /network-instances/network-instance[name='instance-name']/mpls/lsps-constrained-path/tunnels/tunnel/p2p-tunnel-attributes/p2p-primary-paths/

• /network-instances/network-instance[name='instance-name']/mpls/signaling-protocols/rsvp-te/sessions/session/state/notify-status

Supported on PTX Series routers, MX Series routers , and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1.

Sensor to export LSP properties for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs

Supported on PTX Series routers, MX Series routers, and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1.

The following end paths are also supported for the resource path:

• bandwidth

• metric

• max-average-bandwidth

• explicit-route-objects

• record-route-objects

Sensor to export statistics for LDP LSP transit traffic.

Supported on MX Series routers starting with Junos OS Release 20.2R1.

Sensor to export statistics for LDP LSP ingress traffic.

Supported on MX Series routers starting with Junos OS Release 20.2R1.

Sensor to export statistics for multipoint LDP LSP traffic.

Supported on MX Series routers starting with Junos OS Release 20.2R1.

Sensor to export statistics for multipoint LDP egress traffic per interface.

Supported on MX Series routers starting with Junos OS Release 20.2R1.

Sensor to export statistics for multipoint LDP egress traffic per interface.

Supported only on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards line cards on MX Series routers starting with Junos OS Release 20.3R1.

Sensor to export statistics for multipoint LDP ingress traffic per interface.

Supported on MX Series routers starting with Junos OS Release 20.2R1.

Sensor to export statistics for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs.

ON_CHANGE support for LSP events is only activated when the reporting interval is set to 0 in the subscription request.

Supported on PTX Series routers, MX Series routers, and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1.

The following events are exported under this resource path:

• PATHERR_RECEIVED

  • TTL_EXPIRED

  • NON_RSVP_CAPABLE_ROUTER

  • RESVTEAR_RECEIVED

  • PATH_MTU_CHANGE

Sensor to export events for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs.

Starting in Junos OS Evolved Release 19.2R1, PTX10003 routers support streaming statistics.

The following end paths are also supported:

• interface-attributes/interface/bandwidth-reservations/state/active-reservations-count

• interface-attributes/interface/bandwidth-reservations/state/available-bandwidth

• interface-attributes/interface/bandwidth-reservations/state/highwater-mark

• interface-attributes/interface/bandwidth-reservations/state/reserved-bandwidth

• interface-attributes/interface/counters/in-ack-messages

• interface-attributes/interface/counters/in-hello-messages

• interface-attributes/interface/counters/in-path-messages

• interface-attributes/interface/counters/in-path-tear-messages

• interface-attributes/interface/counters/in-reservation-error-messages

• interface-attributes/interface/counters/in-reservation-messages

• interface-attributes/interface/counters/in-reservation-tear-messages

• interface-attributes/interface/counters/in-srefresh-messages

• interface-attributes/interface/counters/out-path-tear-messages

• interface-attributes/interface/counters/out-ack-messages

• interface-attributes/interface/counters/out-hello-messages

• interface-attributes/interface/counters/out-path-messages

• interface-attributes/interface/counters/out-reservation-error-messages

• interface-attributes/interface/counters/out-reservation-messages

• interface-attributes/interface/counters/out-reservation-tear-messages

• interface-attributes/interface/counters/out-srefresh-messages

• neighbors/neighbor/state/neighbor-status

• sessions/session/record-route-objects/record-route-object

• sessions/session/state/destination-address

• sessions/session/state/label-in

• sessions/session/state/label-out

• sessions/session/state/lsp-id

Sensor for traffic statistics for both ingress IP traffic and transit MPLS traffic..

Supported on MX Series and PTX Series routers starting with Junos OS Release 18.3R1.

The following end points are also supported and specify BGP Segment Routing traffic Engineering (SR-TE) transit statistics:

• /sr-te-bsid-policies/sr-te-bsid-policy[binding-sid=‘80001’, to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/packets

• /sr-te-bsid-policies/sr-te-bsid-policy[binding-sid=‘80001’, to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/bytes

The following end points are also supported and specify BGP Segment Routing traffic Engineering (SR-TE) ingress statistics:

• /sr-te-ip-policies/sr-te-ip-policy[to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/packets

• /sr-te-ip-policies/sr-te-ip-policy[to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/bytes

In addition to configuring the sensor, you must enable statistics collection using the statistics statement at the [[edit protocols source-packet-routing telemetry statistics] hierarchy level.

Sensor for Packet Forwarding Engine Statistics. This sensor exports statistics for counters and provides visibility into Packet Forwarding Engine error and drop statistics.

This sensor is supported starting on MX Series and PTX Series routers starting with Junos OS Release 17.4R1.

Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers are supported.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Starting with Junos OS Evolved Release 19.4R1, periodic streaming using gNMI services with PTX10003 routers is supported.

Sensor for Packet Forwarding Engine Statistics. This sensor exports statistics and provides visibility into Packet Forwarding Engine error and drop statistics. Statistics include counters (CC, CPU, and NPU) for traffic data. Note that NPU statistics are different than those streamed from the sensors /junos/system/linecard/npu/memory/ and /junos/system/linecard/npu/utilization/ . Sensor output is comparable to the output using the operational mode command show pfe statistics traffic.

Shown below, statistics are exported for the default FPC (FPC0). Multiples FPCs are supported. The component values and property values are names (like interface names).

Starting in Junos OS Evolved Release 19.4R1, streaming statistics using gRPC and gNMI services on PTX10008 routers is supported.

Starting in Junos OS Release 20.2R1, INITIAL_SYNC statistics using gNMI services on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches are supported.

Starting in Junos OS Evolved Release 21.4R1, streaming statistics by means of gRPC and gNMI is supported on PTX10001-36MR, PTX10004, and PTX10008 routers.

The following paths are also supported:

• :/components/component[name='FPC0:CC0']/properties/property[name='ts-input-packets']/

• /components/component[name='FPC0:CC0']/properties/property[name='ts-output-packets']/

• //components/component[name='FPC0:CC0']/properties/property[name='ts-input-packets-pps']/

• /components/component[name='FPC0:CC0']/properties/property[name='ts-output-packets-pps']/

• /components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-input-packets']/

• /components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-input-packets-pps']/

• /components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-output-packets']/

• /components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-output-packets-pps']/

• /components/component[name='FPC0:CPU0']/properties/property[name='lts-input-packets']/

• /components/component[name='FPC0:CPU0']/properties/property[name='lts-output-packets']/

• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-control-drops']/

• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-high-drops']/

• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-medium-drops']/

• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-low-drops']/

• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-output-low-drops']/

• /components/component[name='FPC0:CPU0']/properties/property[name='lts-hw-input-drops']/

• /components/component[name='FPC0:NPU0']/properties/property[name='hwdsNormal']/

• /components/component[name='FPC0:NPU0']/properties/property[name='hwds-data-error']/

• /components/component[name='FPC0:NPU0']/properties/property[name='hwds-tcp-error']/

• /components/component[name='FPC0:NPU0']/properties/property[name='hwds-illegal-nh']/

• /components/component[name='FPC0:NPU0']/properties/property[name='hwds-invalid-iif']/

  //components/component[name='FPC0:NPU0']/properties/property[name='hwds-fabric']/

Sensors for aggregate segment routing traffic with IS-IS.

This sensor is supported on MX Series and PTX5000 routers starting with Junos OS Release 17.4R1.

Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Statistics are exported separately for each routing instance.

The first path exports inbound traffic. The second path exports outbound traffic. The third path exports inbound segment routing traffic for each segment identifier.

The following OpenConfig paths are supported:

• /network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/in-pkts

• /network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/in-octets

• /network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/out-octets

• /network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/out-pkts

• /network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/in-octets

• /network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/in-pkts

• /network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/out-octets

• /network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/out-pkts

• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/in-octets

• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/in-pkts

• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/out-octets

• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/out-pkts

• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/in-octets

• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/in-pkts

• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/out-octets

• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/out-pkts

Sensors for aggregate segment routing traffic with IS-IS.

This sensor is supported on PTX3000 routers and PTX5000 routers with FPC2 starting with Junos OS Release 19.1R1.

Statistics are exported separately for each routing instance.

The first path exports inbound traffic. The second path exports outbound traffic. The third path exports inbound segment routing traffic for each segment identifier.

Packet Forwarding Engine sensor for ingress segment routing traffic engineering statistics.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Starting in Junos OS Evolved Release 21.4R1,PTX10001-36MR, PTX10003, PTX10004, PTX10008,and PTX10016 routers are supported on gRPC and gNMI services.

Packet Forwarding Engine sensor for ingress segment routing traffic engineering statistics.

Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, and QFX5100 and QFX5200 switches are supported on gRPC and gNMI services.

Starting in Junos OS Evolved Release 21.4R1,PTX10001-36MR, PTX10003, PTX10004, PTX10008,and PTX10016 routers are supported on gRPC and gNMI services.

Sensor for Segment Routing Traffic Engineering (SR-TE) per Label Switched Path (LSP) route statistics.

You can stream SR-TE telemetry statistics for uncolored SR-TE policies to an outside collector. Ingress statistics include statistics for all traffic steered by means of an SR-TE LSP. Transit statistics include statistics for traffic to the Binding-SID (BSID) of the SR-TE policy.

To enable these statistics, include the per-source per-segment-list option at the [edit protocols source-packet-routing telemetry statistics] hierarchy level.

Starting in Junos OS Release 20.1R1, MX Series and PTX Series routers support streaming statistics using gRPC services.

Starting in Junos OS Release 20.2R1, MX240. MX480, MX960, MX2010, and MX2020 with MPC-10E or MPC-11E routers support streaming statistics using gRPC services.

When a subscription is made to these resource paths, the following output format is displayed:

• /mpls/signaling-protocols/segment-routing/sr-te-per-lsp-ingress-policies/sr-te-ingress-lsp-policy\[tunnel-name='srtelsp1' and source='st' and origin='0' and distinguisher='f' and lsp-name='sr1'\]/state/counters\[name='.*'\]/packets

• /mpls/signaling-protocols/segment-routing/sr-te-per-lsp-transit-policies/sr-te-transit-lsp-policy\[tunnel-name='srtelsp1' and source='st' and origin='0' and distinguisher='f' and lsp-name='sr1'\]/state/counters\[name='.*'\]/packets

For the output format above, the field source, values can be ST (static tunnel) or PC (PCEP tunnel). For the field lsp-name, the value is the transit output. Other fields, such as Origin and Distinguisher are fixed for uncolored tunnels.

INITIAL_SYNC support for OpenConfig data model openconfig-platform.yang and openconfig-alarms.yang. This feature lets the collector have a complete view of the current state of every sensor it is subscribed to. INITIAL_SYNC requires that at least one copy of all the sensors be sent to the collector.

Starting in Junos OS Evolved Release 21.4R1, streaming statistics by means of gRPC and gNMI is supported on PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016 routers.

Virtual chassis port counter sensor.

The sensor includes these statistics:

• Input packets

• Output packets

• Input bytes

• Output bytes

Starting with Junos OS Release 20.2R1, streaming statistics from a virtual chassis is supported using gRPC services with MX480, MX960, MX10003, MX2010, and MX2020 routers.

Sensor for subscriber interface information.

ON-CHANGE streaming is supported.

The following end paths are supported:

• interface-index-The system assigned interface index for the interface.

• session-type-The type of client session (e.g VLAN, DHCP, PPPoE).

• user-name-The login name for this interface and session.

• profile-name-The name of the client profile used to create the interface.

• underlying-interface-name-The name of the associated underlying interface.

• cvlan-tag-The innermost VLAN tag value associated with the interface.

• svlan-tag-The outermost VLAN tag value associated with the interface.

Sensor for actual accounting statistics for dynamic subscriber interfaces.

The following end paths are supported:

• ip-in-packets-The number of actual transit IPv4 & IPv6 packets received by the interface.

• ip-out-packets-The number of actual transit IPv4 & IPv6 packets sent to the interface.

• ip-in-bytes-The number of actual transit IPv4 & IPv6 bytes received by the interface.

• ip-out-bytes-The number of actual transit IPv4 & IPv6 bytes received by the interface.

• ipv6-in-packets-The number of actual transit IPv6 packets received by the interface.

• ipv6-out-packets-The number of actual transit IPv6 packets sent to the interface.

• ipv6-in-bytes-The number of actual transit IPv6 bytes received by the interface.

• ipv6-out-bytes-The number of actual transit IPv6 bytes sent to the interface.

This PFE sensor exports the statistics of DDOS from MPC1, MPC2, MPC3, MPC5, MPC6, MPC7, MPC8, and MPC9 line cards.