Guidelines for gRPC Sensors (Junos Telemetry Interface)

 

Starting with Junos OS Release 16.1R3, the Junos Telemetry Interface supports gRPC remote procedure calls (gRPC) to provision sensors and to subscribe to and receive telemetry data on MX Series routers and PTX3000 and PTX5000 routers.

Starting with JunosOS Release 17.2R1, QFX10002, QFX10008, and QFX10016 switches, QFX5200 switches, and PTX1000 and PTX10008 routers are also supported.

Starting with Junos OS Release 17.3R1, QFX5110 switches, EX4600, EX4600-VC, and EX9200 switches and the Routing and Control Board (RCB) on PTX3000 routers are also supported.

Starting with Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensors are supported.

Starting with Junos OS Release 18.2R1, PTX10002 routers are also supported.

Starting with Junos OS Release 17.4R1, PTX10016 routers and virtual MX Series (vMX) routers are also supported.

Starting with Junos OS Release 18.1R1, QFX5210-64C switches and QFX5100 switches are also supported.

Starting with Junos OS Release 18.1R1, ON_CHANGE streaming of ARP, ND, and IP sensor information associated with interfaces is supported through gRPC for MX Series routers and PTX Series routers.

Starting with Junos OS Release 18.3R1, ON_CHANGE streaming of LLDP telemetry sensor information is supported through gRPC for MX Series and PTX Series routers.

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

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

Starting with Junos OS Release 18.4R1, MX480, MX960, MX2010, MX2020, MX2008 and MX-ELM routers are also supported.

Starting with Junos OS Release 19.1R1, MX Series routers operating with MS-MIC and MS-MPC, QFX10002 switches, and PTX10002 routers are also supported.

Starting with Junos OS Release 19.1R1, PTX3000 routers and PTX5000 routers with FPC2 are also supported.

See Table 1 for information about which sensors are supported with gRPC and on which platforms.

See Table 2 for a description of supported broadband edge (BBE) gRPC sensors, which are supported on all platforms supporting gRPC unless otherwise noted.

You can also use the Telemetry Explorer tool to search for and view information about telemetry sensors.

To activate a sensor, use the corresponding resource path. Each resource path enables data streaming for the system resource globally, that is, systemwide. You can also modify each resource path, such as to specify a specific logical or physical interface. For example, to specify a specific interface, include the following at the end of the path: [name='interface-name']/

Supported gRPC Sensors

See Table 1 for a description of supported gRPC sensors and Table 2 for a description of supported broadband edge (BBE) gRPC sensors, including the subscription path you use to provision the sensors.

Table 1: gRPC Sensors

resource path

Description

/components/component/

Sensor for chassis components.

ON_CHANGE notification is triggered if a component (FPC) is inserted or removed or if a component’s power is on or off (FPC is online or offline). Instant reporting of such events is handled with this sensor.

ON_CHANGE streaming is supported on MX960, MX2010, MX2020, PTX-5000, PTX1000, and PTX10000 routers starting with Junos OS Release 18.4R1.

You can also add the following endpoints to the path to stream specific statistics:

  • name

  • state/id

  • state/description

  • state/serial-no

  • state/part-no

  • state/type-Identifies the ON_CHANGE event type. Event types are: FRU_ADD, FRU_REMOVE, FRU_POWERON, and FRU_POWEROFF.

For more information about ON_CHANGE streaming, see Understanding OpenConfig and gRPC on Junos Telemetry Interface.

/components/component/subcomponents/subcomponent[name='FPCid:NPUid’ ]/properties/property/[name=’ counter’]/state/value

Sensor for packet forwarding engine statistics. The subcomponent name npu-id refers to the number of the packet forwarding engine. This sensor provides visibility into packet forwarding engine errors and drops.

Supported on MX Series routers and PTX Series routers starting with Junos OS Release 17.4R1.MX960|MX2010|MX2020|PTX-5000|PTX1000|PTX10000

The value for counter is one of the following;

  • lts-hw-input-drops

  • hwds-normal

  • hwds-fabric

  • hwds-info-cell

  • hwds-timeout

  • hwds-truncated-key

  • hwds-bits-to-test

  • hwds-stack-underflow

  • hwds-stack-overflow

  • hwds-inet6-bad-route

  • hwds-inet-bad-route

  • hwds-filter-discard

  • hwds-dlu-not-routable

  • hwds-data-error

  • hwds-extended

  • hwds-invalid-iif

  • hwds-input-checksum

  • hwds-output-mtu

  • lts-input-packets

  • lts-output-packets

  • lts-sw-input-control-drops

  • lts-sw-input-high-drops

  • lts-sw-input-medium-drops

  • lts-sw-input-low-drops

  • lts-sw-output-low-drops

/components/component/subcomponents/subcomponent[name='FPCID:CCid’ ]/properties/property/[name=’ counter’]/state/value

Sensor for packet forwarding engine statistics. The subcomponent name cc-id refers to the center chip. This sensor provides visibility into packet forwarding engine errors and drops.

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

The value for counter is one of the following;

  • ts-fabric-input-pps

  • ts-fabric-output-pps

  • ts-fabric-input-packets

  • ts-fabric-output-packets

  • lpbk-packets

  • lpbk-pps

  • lpbk-bytes

  • lpbk-pps

  • lpbk-drop-packets

  • lpbk-drop-pps

  • lpbk-drop-bytes

  • lpbk-drop-bps

/components/component/subcomponents/subcomponent[name='FPCID’]/properties/property/[name=’ counter’]/state/value

Sensor for packet forwarding engine statistics. The subcomponent name FPCid refers to the number of the Flexible PIC Concentrator. This sensor provides visibility into packet forwarding engine errors and drops. This sensor pulls CPU counters.

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

The value for counter is one of the following;

  • lts-hw-input-drops

  • lts-input-packets

  • lts-output-packets

  • lts-sw-input-control-drops

  • lts-sw-input-high-drops

  • lts-sw-input-medium-drops

  • lts-sw-input-low-drops

  • lts-sw-output-low-drops

/junos/chassis/gres/

Sensor for graceful Routing Engine switchover (GRES) information.

Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported.

You can also add the following as the end path for /junos/chassis/gres/:

  • configured-state

  • error-state

  • gres-time

  • master-kernel-ready

  • slave-connect-time

  • slave-kernel-ready

/junos/chassis/issu/

Sensor for in-service software upgrade (ISSU) information.

Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported.

You can also add the following as the end path for /junos/chassis/issu/:

  • failure-stage

  • current-issu-stage

/junos/kernel/peer-infra/

Sensor for PFEMAN connection information.

Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported.

You can also add the following as the end path for /junos/kernel/peer-infra/:

  • pfeman-conn-drops

  • spurious-ppt-wkups

/junos/kernel/record-meta-data/record_time

Sensor for system time at which Routing Engine metadata is created.

Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported.

/junos/kernel-ifstate

Sensor for Routing Engine ifstate information.

Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported.

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

  • alive-clients-cnt

  • alive-ifstates-cnt

  • client-limit-reached

  • dead-clients-cnt

  • dead-ifstates-cnt

  • delayed-unrefs-cnt

  • delayed-unrefs-max

  • stuck-clients-cnt

/junos/kernel-ifstate/stats/churn-rate

Sensor for Routing Engine network object churn rate statistics.

Starting in Junos OS Release 18.2R1, MX Series and PTX Series switches are supported.

  • overall-churn-rate

  • route-add-rate

  • route-change-rate

  • route-delete-rate

  • nexthop-add-rate

  • nexthop-change-rate

  • nexthop-delete-rate

/junos/kernel-ifstate/stats/peer-consumption-rate

Sensor for Routing Engine network object peer consumption rate statistics.

Starting in Junos OS Release 18.2R1, MX Series and PTX Series switches are supported.

  • peer-index

  • consumption-rate-counter

  • consumption-route-add-rate

  • consumption-route-delete-rate

  • consumption-nexthop-add-rate

  • consumption-nexthop-change-rate

  • consumption-nexthop-delete-rate

/junos/kernel-ifstate/stats/record-seq-num

Sequence number of a statistic or record.

/junos/kernel-ifstate/stats/record-time

System time at which a statistic or record is created.

/junos/kernel-ifstate/stats/vetos-statistics

Sensor for Routing Engine state statistics.

Starting in Junos OS Release 18.2R1, MX Series and PTX Series switches are supported.

  • veto-vm-page-count-severe

  • veto-ifstate-memory

  • veto-memory-overconsumed

  • veto-pfe-veto-max-routes

  • veto-too-many-delayed-unrefs

  • veto-nh-memory-usage

  • veto-mbuf-cluster

  • veto-flabel-space-exhaustion

  • veto-flabel-space-consumption

/junos/ike-security-associations/ike-security-association/routing-instance [name=’ routing-instance-name]

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

junos/rpm/probe-results/probe-test-results/

Sensor for probe test results for Real time Performance Monitoring (RPM) statistics. These statistics provide RPM monitoring data results collected by Juniper devices. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering.

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

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

  • owner

  • test-name

  • target-address

  • target-url

  • source-address

  • destination-interface

  • probe-type

  • icmp-id

  • routing-instance-name

  • test-size

  • http-status

  • loss-thresh-total

  • loss-thresh-succ

  • rtt-thresh

  • rtt-jitter-thresh

  • rtt-stddev-thresh

  • igr-thresh

  • igr-jitter-thresh

  • igr-stddev-thresh

  • egr-thresh

  • egr-jitter-thresh

  • egr-stddev-thresh

  • probe-tests-hw-ts-err/invalid-client-recv-ts-cntr

  • probe-tests-hw-ts-err/invalid-client-nots-cntr

  • probe-tests-hw-ts-err/invalid-server-send-ts-cntr

  • probe-tests-hw-ts-err/invalid-server-spent-time-cntr

  • probe-single-results

  • probe-single-results/probe-time

  • probe-single-results/probe-sent-time

  • probe-single-results/probe-status

  • probe-single-results/hardware-timestamp-status

  • probe-single-results/rtt

  • probe-single-results/egress

  • probe-single-results/ingress

  • probe-single-results/round-trip-jitter

  • probe-single-results/egress-jitter

  • probe-single-results/round-trip-interarrival-jitter

  • probe-single-results/egress-interarrival-jitter

  • probe-single-results/ingress-interarrival-jitter

  • probe-test-generic-result

  • probe-test-generic-results/results-scope

  • probe-test-generic-results/probes-sent

  • probe-test-generic-results/probe-responses

  • probe-test-generic-results/loss-percentage

  • probe-test-generic-measurements

  • probe-test-generic-measurements/samples

  • probe-test-generic-measurements/min-delay

  • probe-test-generic-measurements/max-delay

  • probe-test-generic-measurements/avg-delay

  • probe-test-generic-measurements/jitter-delay

  • probe-test-generic-measurements/stddev-delay

  • probe-test-generic-measurements/sum-delay

/junos/rpm/history-results/history-single-test-results/

Sensor for history results for Real time Performance Monitoring (RPM) statistics. These statistics provide RPM monitoring data results collected by Juniper devices. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering.

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

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

  • owner

  • test-name

  • target-address

  • target-url

  • source-address

  • destination-interface

  • probe-type

  • icmp-id

  • test-size

  • http-status

  • routing-instance-name

  • loss-thresh-total

  • loss-thresh-succ

  • rtt-thresh

  • rtt-jitter-thresh

  • rtt-stddev-thresh

  • igr-thresh

  • igr-jitter-thresh

  • igr-stddev-thresh

  • egr-thresh

  • egr-jitter-thresh

  • egr-stddev-thresh

  • probe-single-results

  • probe-single-results/probe-time

  • probe-single-results/probe-sent-time

  • probe-single-results/probe-status

  • probe-single-results/hardware-timestamp-status

  • probe-single-results/rtt

  • probe-single-results/egress

  • probe-single-results/ingress

  • probe-single-results/round-trip-jitter

  • probe-single-results/egress-jitter

  • probe-single-results/ingress-jitter

  • probe-single-results/round-trip-interarrival-jitter

  • probe-single-results/egress-interarrival-jitter

  • probe-single-results/ingress-interarrival-jitter

/junos/rpm/server/

Sensor for server results for Real time Performance Monitoring (RPM) statistics. These statistics provide RPM monitoring data results collected by Juniper devices. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering.

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

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

  • active-servers

  • active-servers/protocol

  • active-servers/port

  • active-servers/dst-interface

/junos/security/veriexec-state

Sensor for Veriexec state information.

Starting with Junos OS Release 19.1R1, EX9200, EX9251, EX9253, MX Series, and PTX Series are supported.

/junos/services/label-switched-path/usage/

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, QFX10002 switches and PTX10002 routers are 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.

Note: When you enable a sensor for LSP statistics only, you must also configure the sensor-based-stats statement at the [edit protocols mpls] hierarchy level. MX Series routers should operate in enhanced mode. If not enabled by default, include either the enhanced-ip statement or the enhanced-ethernet statement at the [edit chassis network-services] hierarchy level.

/junos/twamp/client/control-connection/

Sensor for client control connection results for Two-Way Active Management Protocol (TWAMP). TWAMP (described in RFC 5357). Used to measure traffic performance between end-points, you can use this information to assure service level agreements, improve network design, and optimize traffic engineering.

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

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

  • control-name

  • client-address

  • client-port

  • server-address

  • server-port

  • session-count

  • auth-mode

  • server-address

  • server-port

  • test-session/session-name

  • test-session/sender-address

  • test-session/sender-port

  • test-session/reflector-address

  • test-session/reflector-port

/junos/twamp/client/probe-test-results/

Sensor for client probe test results for Two-Way Active Management Protocol (TWAMP). TWAMP (described in RFC 5357) is used to measure traffic performance between end-points. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering.

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

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

  • owner

  • test-name

  • destination-interface

  • test-size

  • server-address

  • server-port

  • client-address

  • client-port

  • reflector-address

  • reflector-port

  • sender-address

  • sender-port

  • loss-thresh-total

  • loss-thresh-succ

  • rtt-thresh

  • rtt-jitter-thresh

  • rtt-stddev-thresh

  • igr-thresh

  • igr-jitter-thresh

  • igr-stddev-thresh

  • egr-thresh

  • egr-jitter-thresh

  • egr-stddev-thresh

  • probe-tests-hw-ts-err/invalid-client-recv-ts-cntr

  • probe-tests-hw-ts-err/invalid-client-nots-cntr

  • probe-tests-hw-ts-err/invalid-server-send-ts-cntr

  • probe-tests-hw-ts-err/invalid-server-spent-time-cntr

  • probe-single-results/

  • probe-single-results/probe-time

  • probe-single-results/probe-sent-time

  • probe-single-results/probe-status

  • probe-single-results/hardware-timestamp-status

  • probe-single-results/rtt

  • probe-single-results/egress

  • probe-single-results/ingress

  • probe-single-results/round-trip-jitter

  • probe-single-results/egress-jitter

  • probe-single-results/ingress-jitter

  • probe-single-results/round-trip-interarrival-jitter

  • probe-single-results/egress-interarrival-jitter

  • probe-single-results/ingress-interarrival-jitter

  • probe-test-generic-results/

  • probe-test-generic-results/results-scope

  • probe-test-generic-results/probes-sent

  • probe-test-generic-results/probe-responses

  • probe-test-generic-results/loss-percentage

  • probe-test-generic-results/probe-test-rtt

  • probe-test-generic-results/probe-test-generic-measurements/

  • probe-test-generic-results/probe-test-generic-measurements//probe-measurement-type

  • probe-test-generic-results/probe-test-generic-measurements/samples

  • probe-test-generic-results/probe-test-generic-measurements/min-delay

  • probe-test-generic-results/probe-test-generic-measurements/max-delay

  • probe-test-generic-results/probe-test-generic-measurements/avg-delay

  • probe-test-generic-results/probe-test-generic-measurements/jitter-delay

  • probe-test-generic-results/probe-test-generic-measurements/stddev-delay

  • probe-test-generic-results/probe-test-generic-measurements/sum-delay

/junos/twamp/client/history-test-results/history-single-test-results/

Sensor for client history test results for Two-Way Active Management Protocol (TWAMP). TWAMP (described in RFC 5357) is used to measure traffic performance between end-points. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering.

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

  • owner

  • test-name

  • destination-interface

  • test-size

  • server-address

  • server-port

  • client-address

  • client-port

  • reflector-address

  • reflector-port

  • sender-address

  • sender-port

  • loss-thresh-total

  • loss-thresh-succ

  • rtt-thresh

  • rtt-jitter-thresh

  • rtt-stddev-thresh

  • igr-thresh

  • igr-jitter-thresh

  • igr-stddev-thresh

  • egr-thresh

  • egr-jitter-thresh

  • egr-stddev-thresh

  • probe-single-results/

  • probe-single-results/probe-time

  • probe-single-results/probe-sent-time

  • probe-single-results/probe-status

  • probe-single-results/hardware-timestamp-status

  • probe-single-results/rtt

  • probe-single-results/egress

  • probe-single-results/ingress

  • probe-single-results/round-trip-jitter

  • probe-single-results/egress-jitter

  • probe-single-results/ingress-jitter

  • probe-single-results/round-trip-interarrival-jitter

  • probe-single-results/egress-interarrival-jitter

  • probe-single-results/ingress-interarrival-jitter

/junos/twamp/server/control-connection/

Sensor for control connection results for servers for Two-Way Active Management Protocol (TWAMP). TWAMP (described in RFC 5357) is used to measure traffic performance between end-points. You can use this information to assure service level agreements, improve network design, and optimize traffic engineering.

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

  • control-name

  • client-address

  • client-port

  • server-address

  • server-port

  • session-count

  • auth-mode

  • test-session/

  • test-session/session-name

  • test-session/sender-address

  • test-session/sender-port

  • test-session/reflector-address

  • test-session/reflector-port

/network-instances/network-instance[name='instance-name']/mpls/lsps/constrained-path/container-tunnels/container-tunnel[name='name']state/

Sensor for container tunnel streaming notifications and normalization status.

Starting with Junos OS Release 19.1R1, this sensor is supported on all platforms supporting JTI.

The following paths are also supported:

  • name

  • oper-state

  • member-count

  • minimum-lsp-count

  • maximum-lsp-count

  • normalize-timer

  • normalize-threshold

  • aggregate-bandwidth

  • sampled-aggregate-bandwidth

  • max-signaling-bandwidth

  • min-signaling-bandwidth

  • splitting-bandwidth

  • merging-bandwidth

  • incremental-normalization

  • failover-normalization

  • time-to-normalize

  • sampling/sampling-outlier-cutoff

  • sampling/sampling-mode

  • sampling/sampling-percentile

  • normalization-status which includes normalize-init, normalize-complete, and avoid-normalize.

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

Sensor for LSP events and properties.

LSP events and properties are exported for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs.

Note: Starting with Junos OS Release 17.4R1, telemetry data for LSP events and properties is reported separately for each routing instance. To export data for LSP events and properties, you must now include /network-instances/network-instance[name='instance-name']/ in front of all supported paths. .

Supported on MX Series and PTX Series routers and QFX10000 switches starting with Junos OS Release 17.2R1.

Supported on EX4600 and EX9200 switches and QFX5110 and QFX5200 switches starting with Junos OS Release 17.3R1.

Starting with Junos OS Release 18.1R1, QFX5100 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.

The following paths are also supported:

  • lsp-instances/state/notify-status/initiated

  • lsp-instances/state/notify-status/lsp-up

  • lsp-instances/state/notify-status/lsp-down

  • lsp-instances/state/notify-status/lp-available

  • lsp-instances/state/notify-status/lp-unavailable

  • lsp-instances/state/notify-status/autobw-success

  • lsp-instances/state/notify-status/autobw-fail

  • lsp-instances/state/notify-status/patherr-recv

  • lsp-instances/state/notify-status/tunnel-local-repaired

  • lsp-instances/state/bandwidth

  • lsp-instances/state/metric

  • lsp-instances/state/max-avg-bandwidth

  • /state/associated-rsvp-sessions/associated-rsvp-session[local-index ='index-number']/

  • state/notify-status

  • state/notify-status/select-active-path

  • state/notify-status/deselect-active-path

  • state/notify-status/change-active-path

  • state/notify-status/originate-mbb

  • state/notify-status/cspf-noroute

  • state/notify-status/cspf-success

  • state/notify-status/gr-recovery-fail

  • state/explicit-path-name

Note: To specify a specific LSP name and source address, include [name='lsp-name',source='address'] after mpls/lsp/constrained-path-tunnels/tunnel/ in any of the supported paths. If do not include a specific LSP name, data is exported for all configured LSPs.

/network-instances/network-instance[name='instance-name']/mpls/lsps/constrained-path/tunnels/tunnel[name='name']/p2p-tunnel-attributes/p2p-primary-paths/p2p-primary-path[name='path-name'][local-index=’local-index’]/state/notify-status

Sensor for self-ping failure. This sensor supports self-ping logs. Starting with Junos OS Release 19.1R1, this sensor is supported on all platforms supporting JTI.

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

Starting with Junos OS Release 17.4R1, telemetry data for LSP events and properties is reported separately for each routing instance.

Supported on MX Series and PTX Series routers and QFX10000 switches starting with Junos OS Release 17.2R1.

Supported on EX4600 and EX9200 switches and QFX5110 and QFX5200 switches starting with Junos OS Release 17.3R1.

Starting with Junos OS Release 18.1R1, QFX5100 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.

The following paths are also supported:

  • detour-up

  • detour-down

  • patherr-recv

  • patherr-recv/admission_control_failure

  • patherr-recv/session_preeempted

  • patherr-recv/bad_loose_route

  • patherr-recv/bad_strict_route

  • patherr-recv/label_allocation_failure

  • patherr-recv/non_rsvp_capable_router

  • patherr-recv/ttl_expired

  • patherr-recv/routing_loop_detected

  • patherr-recv/requested_bandwidth_unavailable

  • patherr-recv/ttl_expired

  • pathmtu-change

/junos/npu-memory/junos/system/linecard/npu/memory/

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.

Note: Starting with Junos Release 17.4R1, FPC1 and FCP2 on PTX Series routers export data for NPU memory and NPU memory utilization. Previously, this sensor was supported only on FPC 3.

Starting with Junos OS Release 18.3R1, EX4650 switches are supported.

Starting with Junos OS Release 19.1R1, QFX10002 switches and PTX10002 routers are supported.

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 add the following to the end of the path to stream specific statistics for NPU utilization:

  • [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

/junos/system/linecard/node-slicing/af-fab-stats/

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.

/junos/system/linecard/cpu/memory/

Sensor for CPU memory.

Note: On PTX Series routers, FPC1 and FPC2 are not supported.

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.

Supported on QFX10002 switches and PTX10002 routers starting with Junos OS Release 19.1R1.

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

/junos/system/linecard/interface/

Packet Forwarding Engine sensor for physical interface traffic.

Note: For PTX Series routers, for a specific interface, queue statistics are exported for each line card. For MX series routers, interface queue statistics are exported only from the slot on which an interface is configured.

For Aggregated Ethernet interfaces, statistics are exported for the member physical interfaces. You must aggregate the counters at the destination server, or collector.

If a physical interface is administratively down or operationally down, interface counters are not exported.

Issuing an operational clear command, such as clear interfaces statistics all, does not reset statistics exported by the line card.

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, QFX5110 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.

Supported on QFX10002 switches and PTX10002 routers starting with Junos OS Release 19.1R1.

/junos/system/linecard/interface/logical/usage

Packet Forwarding Engine sensor for logical interface statistics.

Note: If a logical interface is operationally down, interface statistics continue to be exported.

Issuing an operational clear command, such as clear interfaces statistics all, does not reset statistics exported by the line card.

Note: Locally injected packets from the Routing Engine are not exported.

Supported in Junos OS Release 15.1F5.

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

Supported on EX9200 switches, QFX5110 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.

/junos/system/linecard/optical

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.

/junos/system/linecard/otn

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.

/junos/system/linecard/qmon-sw/

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.

/network-instances/network-instance/protocols/protocol/bgp/

Note: Starting with Junos OS Release 17.4R1 on MX Series and PTX Series routers, you can provision Junos Telemetry Interface sensors to export data for BGP routing tables (RIBs) for IPv4 and IPv6 routes.

For BGP routing table paths, the /network-instances/network-instance/ path is not supported.

Each address family supports exporting data for five different tables, a main routing table, and four per-neighbor tables:

  • local-rib— main BGP routing table for the main routing instance.

  • adj-rib-in-pre— NLRI updates received from the neighbor before any local input policy filters have been applied.

  • adj-rib-in-post— routes received from the neighbor eligible for best-path selection after local input policy filters have been applied.

  • adj-rib-out-pre— routes eligible for advertising to the neighbor before output policy filters have been applied.

  • adj-rib-out-post— routes eligible for advertising to the neighbor after output policy filters have been applied.

Use the following paths to export data for each BGP routing table. You can specify to export data either for IPv4 or IPv6 for each table:

  • /bgp-rib/afi-safis/afi-safi/ipv4-unicast/loc-rib/

  • /bgp-rib/afi-safis/afi-safi/ipv6-unicast/loc-rib/

  • /bgp-rib/afi-safis/afi-safi/ipv4-unicast/

    neighbors/neighbor/adj-rib-in-pre/

  • /bgp-rib/afi-safis/afi-safi/ipv6-unicast/

    neighbors/neighbor/adj-rib-in-pre/

  • /bgp-rib/afi-safis/afi-safi/ipv4-unicast/

    neighbors/neighbor/adj-rib-in-post/

  • /bgp-rib/afi-safis/afi-safi/ipv6-unicast/

    neighbors/neighbor/adj-rib-in-post/

  • /bgp-rib/afi-safis/afi-safi/ipv4-unicast/

    neighbors/neighbor/adj-rib-out-pre/

  • /bgp-rib/afi-safis/afi-safi/ipv6-unicast/

    neighbors/neighbor/adj-rib-out-pre/

  • /bgp-rib/afi-safis/afi-safi/ipv4-unicast/

    neighbors/neighbor/adj-rib-out-post/

  • /bgp-rib/afi-safis/afi-safi/ipv6-unicast/

    neighbors/neighbor/adj-rib-out-post/

Sensor for BGP peer information.

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

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

Starting with Junos OS Release 18.1R1, QFX5100 switches are also supported.

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

Note: Starting with Junos OS Release 17.3R1, telemetry data streamed through gRPC for BGP peers is reported separately for each configured routing instance.

If your Juniper Network device is running Junos OS Release 17.3R1 or later, you must prepend the following to the beginning of any path you specify to stream statistics for BGP, with the exception of paths for routing tables:

/network-instances/network-instance[name_'instance-name']/

protocols/protocol/

Starting with Junos OS Release 17.3R1, the following paths are also supported:

  • /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/afi-safis/afi-safi/state/prefixes/accepted

  • /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/afi-safis/afi-safi/state/prefixes/rejected

    /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/afi-safis/afi-safi/state/active

  • /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/afi-safis/afi-safi/state/queues/output

  • /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/afi-safis/afi-safi/state/queues/input

  • /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/snmp-peer-index

  • /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/state/ImportEval

  • /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/state/ImportEvalPending

  • /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/state/messages/received/notification

    /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/state/messages/sent/notification

    /network-instances/network-instance/protocols/protocol/

    bgp/transport/state/remote-port

    /network-instances/network-instance/protocols/protocol/

    bgp/neighbors/neighbor/state/supported-capabilities

Note: For all the following paths, with the exception of paths for routing tables, if your Juniper Networks device is running Junos OS Release 17.3R1 or later, you must prepend the following in front of the path:

/network-instances/network-instance[name_'instance-name']/protocols/protocol/

You can also include the following at the end path to /network-instances/network-instance[name_'instance-name']/protocols/protocol/

bgp/neighbors/neighbor/
:

  • state/session-state

  • state/messages/sent/update

  • state/messages/received/update

  • transport/state/local-address

  • transport/state/remote-address

  • state/peer-as

  • afi-safis/afi-safi/state/prefix-limit/state/max-prefixes

  • afi-safis/afi-safi/state/active

  • state/session-status

  • state/session-admin-status

  • state/session-established-transitions

  • state/interface-error

  • state/prefix-limited-exceeded

  • state/last-established

  • established-transitions

You can also include the following at the end path to /network-instances/network-instance[name_'instance-name']/protocols/protocol/

/bgp/global/
:

  • afi-safis/afi-safi/state/total-prefixes

You can also include the following at the end path to /network-instances/network-instance[name_'instance-name']/protocols/protocol/

/bgp/peer-groups/peer-group[name_'peer-group-name]/
:

  • afi-safis/afi-safi/add-paths/eligible-prefix-policy

  • state/peer-count/

Note: For paths that export data for BGP routing tables, which are supported starting with Junos OS Release 17.4R1, you can apend the following to each of the paths:

  • /num-routes

  • /routes/route/prefix

  • /routes/route/attributes

  • /routes/route/attributes/origin

  • /routes/route/attributes/as-path

  • /routes/route/attributes/next-hop

  • /routes/route/attributes/med

  • /routes/route/attributes/local-pref

  • /routes/route/attributes/atomic-aggr

  • /routes/route/attributes/aggregator/as

  • /routes/route/attributes/aggregator/as4

  • /routes/route/attributes/aggregator/address

  • /routes/route/ext-attributes/

  • /routes/route/ext-attributes/community

  • /routes/route/ext-attributes/originator-id

  • /routes/route/ext-attributes/cluster-list

  • /routes/route/ext-attributes/extended-community

  • /routes/route/ext-attributes/aigp

  • /routes/route/ext-attributes/path-id

  • /routes/route/ext-attributes/unknown-attribute

  • /routes/route/ext-attributes/unknown-attribute/attr-type

  • /routes/route/ext-attributes/unknown-attribute/attr-len

  • /routes/route/ext-attributes/unknown-attribute/attr-value

  • /routes/route/last-modified-date

  • /routes/route/last-update-received

  • /routes/route/valid-route

  • /routes/route/invalid-reason

  • /routes/route/best-path

/junos/task-memory-information/

Sensor for memory utilization for routing protocol task.

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

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

Starting with Junos OS Release 18.1R1, QFX5100 switches are also supported.

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

You can also include the following at the end path to /junos/task-memory-information/:

  • task-memory-overall-report/task-size-block-list/task-size-block/tsb-size

  • task-memory-overall-report/task-size-block-list/task-size-block/tsb-alloc-bytes

  • task-memory-overall-report/task-size-block-list/task-size-block/tsb-allocs

  • task-memory-overall-report/task-size-block-list/task-size-block/tsb-max-allocs

  • task-memory-overall-report/task-size-block-list/task-size-block/tsb-max-bytes

  • task-memory-overall-report/task-size-block-list/task-size-block/tsb-free-bytes

  • task-memory-overall-report/task-memory-total-bytes

  • task-memory-overall-report/task-memory-total-max-bytes

  • task-memory-information/task-memory-overall-report/task-memory-total-free-bytes

  • task-memory-allocator-report/task-block-list/task-block/tb-name

  • task-memory-allocator-report/task-block-list/task-block/tb-size

  • task-memory-allocator-report/task-block-list/task-block/tb-alloc-size

  • task-memory-allocator-report/task-block-list/task-block/tb-alloc-blocks

  • task-memory-allocator-report/task-block-list/task-block/tb-alloc-bytes

  • task-memory-allocator-report/task-block-list/task-block/tb-max-alloc-blocks

  • task-memory-allocator-report/task-lite-page-list/task-lite-page/tlp-name

  • task-memory-allocator-report/task-lite-page-list/task-lite-page/tlp-alloc-bytes

  • task-memory-allocator-report/task-memory-total-bytes

  • task-memory-information/task-memory-allocator-report/task-memory-total-max-bytes

  • task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-name

  • task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-allocs

  • task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-alloc-bytes

  • task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-max-allocs

  • task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-max-alloc-bytes

  • task-memory-malloc-usage-report/task-malloc-list/task-malloc/tm-function-calls

  • task-memory-malloc-usage-report/task-memory-total-bytes

  • task-memory-malloc-usage-report/task-memory-total-max-bytes

  • task-memory-max-dynamic-allocs

  • task-memory-bss-bytes

  • task-memory-max-bss-bytes

  • task-memory-page-data-bytes

  • task-memory-max-page-data-bytes

  • task-memory-dir-bytes

  • task-memory-max-dir-bytes

  • task-memory-total-bytes-in-use

  • task-memory-total-bytes-percent

/junos/system/linecard/firewall/

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.

Note: Hierarchical policer statistics are collected for MX Series routers only. Traffic-class counter statistics are collected for PTX Series routers and QFX10000 switches only.

Firewall counters are exported even if the interface to which the firewall filter is attached is operationally down.

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)

/interfaces/interface/

Sensor for physical interface traffic.

Note: For PTX Series routers, for a specific interface, queue statistics are exported for each line card. For MX series routers, interface queue statistics are exported only from slot on which an interface is configured.

For Aggregated Ethernet interfaces, statistics are exported for the member physical interfaces. You must aggregate the counters at the destination server, or collector.

If a physical interface is administratively down or operationally down, interface counters are not exported.

Only fields with a non-zero value are exported.

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.

Starting with Junos OS Release 18.1R1, QFX5100 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 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. This can reduce the reap time for non-queue data for platforms supporting Virtual Output Queues (VOQ), such as PTX Series routers.

The two sensors are:

  • /junos/system/linecard/interface/traffic/ exports all fields except queue statistics.

  • /junos/system/linecard/interface/queue/ exports queue statistics.

Note: End paths supporting ON_CHANGE streaming are indicated.

The following paths are also supported:

  • /interfaces/interface[name='interface-name']/state/parent_ae_name

  • /interfaces/interface[name='interface-name']/state/admin-status

    ON_CHANGE streaming supported

  • /interfaces/interface[name='interface-name']/state/counters/carrier-transitions

  • /interfaces/interface[name='interface-name']/state/last-change

  • /interfaces/interface[name='interface-name']/state/high-speed

  • /interfaces/interface[name='interface-name']/state/counters/out-octets

  • /interfaces/interface[name='interface-name']/state/counters/out-unicast-pkts

  • /interfaces/interface[name='interface-name']/state/counters/out-multicast-pkts

  • /interfaces/interface[name='interface-name']/state/counters/out-broadcast-pkts

  • /interfaces/interface[name='interface-name']/state/counters/out-errors

  • /interfaces/interface[name='interface-name']/state/counters/in-octets

  • /interfaces/interface[name='interface-name']/state/counters/in-unicast-pkts

  • /interfaces/interface[name='interface-name']/state/counters/in-multicast-pkts

  • /interfaces/interface[name='interface-name']/state/

  • /interfaces/interface[name='interface-name']/state/counters/in-broadcast-pkts

  • /interfaces/interface[name='interface-name']/state/counters/in-errors

  • /interfaces/interface[name='interface-name']/state/in-pause-pkts

  • /interfaces/interface[name='interface-name']/state/out-pause-pkts

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/ pkts

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/bytes

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/tail-drop-pkts

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/ rl-drop-pkts

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/ rl-drop-bytes

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/avg-buffer-occupancy

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/cur-buffer-occupancy

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/peak-buffer-occupancy

  • /interfaces/interface[name='interface-name']/state/counters/in-queue [queue-number=queue_number]/allocated-buffer-size

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/pkts

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/bytes

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/tail-drop-pkts

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/rl-drop-pkts

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/ rl-drop-bytes

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/red-drop-pkts

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/red-drop-bytes

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/avg-buffer-occupancy

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/cur-buffer-occupancy

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/ peak-buffer-occupancy

  • /interfaces/interface[name='interface-name']/state/counters/out-queue [queue-number=queue_number]/allocated-buffer-size

  • /interfaces/interface[name='interface-name']/state/description

    ON_CHANGE streaming supported

  • /interfaces/interface[name='interface-name']/state/enabled

  • /interfaces/interface[name='interface-name']/state/ifindex

  • /interfaces/interface[name='interface-name']/state/last-change

  • /interfaces/interface[name='interface-name']/state/mtu

  • /interfaces/interface[name='interface-name']/state/name

  • /interfaces/interface[name='interface-name']/state/oper-status

    ON_CHANGE streaming supported

  • /interfaces/interface[name='interface-name']/state/type

/interfaces/interface/subinterfaces//interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']

Sensor for logical interface traffic.

Note: If a logical interface is operationally down, interface statistics continue to be exported.

Note: Locally injected packets from the Routing Engine are not exported.

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.

Starting with Junos OS Release 18.1R1, QFX5100 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.

Note: End paths supporting ON_CHANGE streaming are indicated.

The following paths are also supported:

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/name

    ON_CHANGE streaming supported. This value does not change with an event, but will be streamed on event creation and deletion.

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/ifindex

    ON_CHANGE streaming supported. This value does not change with an event, but will be streamed on event creation and deletion.

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/index

    ON_CHANGE streaming supported. This value does not change with an event, but will be streamed on event creation and deletion.

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/snmp_index

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/admin_status

    ON_CHANGE streaming supported

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oper_status

    ON_CHANGE streaming supported

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/last_change

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/description

    ON_CHANGE streaming supported

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/enabled

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/in_octets

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/in_unicast_pkts

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/in_broadcast_pkts

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/in_multicast_pkts

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/in_discards

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/in_errors

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/in_unknown_protos

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/out_octets

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/out_unicast_pkts

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/out_broadcast_pkts

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/out_multicast_pkts

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/out_discards

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/out_errors

  • /interfaces/interface[name='interface-name']/subinterfaces/subinterface[index='unit']state/oounters/last_clear

/junos/system/linecard/optics/

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.

/junos/rsvp-interface-information/

Sensor for events and properties for RSVP interfaces.

Note: For 100 RSVP logical interfaces, configure a sampling interval equal to 60 seconds. For 200 RSVP logical interfaces, configure a sampling interval equal to 180 seconds.

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

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

Supported on QFX5100 switches starting with Junos OS Release 18.1R1.

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.

You can also add the following to the end path for /junos/rsvp-interace-information/:

  • active-count

  • rsvp-interface/interface-name

  • rsvp-interface/index

  • rsvp-interface/rsvp-status

  • rsvp-interface/authentication-flag

  • rsvp-interface/aggregate-flag

  • rsvp-interface/ack-flag

  • rsvp-interface/protect-flag

  • rsvp-interface/hello-interval

  • rsvp-interface/interface-address

  • message-statistics/rsvp-message

  • rsvp-interface/message-statistics/messages-sent

  • rsvp-interface/message-statistics/messages-received

  • rsvp-interrface/message-statistics/messages-sent-5seconds

  • rsvp-interface/message-statistics/messages-received-5seconds

  • rsvp-interface/rsvp-telink/active-reservation

  • rsvp-interface/rsvp-telink/preemption-count

  • rsvp-interface/rsvp-telink/update-threshold

  • rsvp-interface/rsvp-telink/subscription

  • rsvp-interface/rsvp-telink/static-bandwidth

  • rsvp-interface/rsvp-telink/available-bandwidth

  • rsvp-interface/rsvp-telink/reserved-bandwidth/bandwidth-priority

  • rsvp-interface/rsvp-telink/reserved-bandwidth/total-reserved-bandwidth

/components/

Sensor for operational state of Routing Engines, power supply modules, Switch Fabric Boards, Control Boards, Switch Interface Boards, Modular Interface Cards, and Physical Interface Cards.

Note:

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

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

Supported on QFX5100 switches starting with Junos OS Release 18.1R1.

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.

You can also add the following to each of the paths:

  • name

  • cidx

  • version

  • part_number

  • serial_number

  • description

  • clei_code

  • model

  • vendor_name

  • properties/property/state

  • properties/property/state_offline_reason (MX Series only)

  • properties/property/power_usage

  • properties/property/power_maximum

  • properties/property/temperature_intake

  • properties/property/temperature_exhaust_a (not supported on PTX1000 and PTX3000 routers)

  • properties/property/temperature_exhaust_b (not supported on PTX1000 and PTX3000 routers)

  • properties/property/temperature_exhaust (not supported on PTX1000 and PTX5000 routers)

  • properties/property/cpu_utilization_total

  • properties/property/ memory_dram_used

  • properties/property/memory_utilization_heap

  • properties/property/memory_utilization_buffer

  • properties/property/uptime

The following paths are also supported only for Routing Engine statistics:

  • properties/property/mastership-state

  • properties/property/mastership-priority

  • properties/property/temperature-cpu

  • properties/property/memory-dram-installed

  • properties/property/cpu-utilization-user

  • properties/property/cpu-utilization-background

  • properties/property/cpu-utilization-kernel

  • properties/property/cpu-utilization-idle

  • properties/property/reboot-reason

The following paths are also supported for power modules:

  • properties/property/power-zone-upper-capacity

  • properties/property/power-zone-upper-maximum

  • properties/property/power-zone-upper-allocated

  • properties/property/power-zone-upper-remaining

  • properties/property/power-zone-upper-usage

  • properties/property/power-zone-lower-capacity

  • properties/property/power-zone-lower-maximum

  • properties/property/power-zone-lower-allocated

  • properties/property/power-zone-lower-remaining

  • properties/property/power-zone-lower-usage

  • properties/property/power-zone-0-capacity

  • properties/property/power-zone-0-maximum

  • properties/property/power-zone-0-allocated

  • properties/property/power-zone-0-remaining

  • properties/property/power-zone-0-usage

  • properties/property/power-zone-1-capacity

  • properties/property/power-zone-1-maximum

  • properties/property/power-zone-1-allocated

  • properties/property/power-zone-1-remaining

  • properties/property/power-zone-1-usage

  • properties/property/power-system-capacity

  • properties/property/power-system-allocated

  • properties/property/power-system-remaining

  • properties/property/power-system-usage

  • properties/property/temperature-ambient

The following paths are supported for either Switch Fabric Board or Control Boards or both:

  • properties/property/temperature-zone-0-intake (SFB only)

  • properties/property/temperature-zone-0-intake-a (both SFB and CB)

  • properties/property/temperature-zone-1-intake-b (both SFB and CB)

  • properties/property/temperature-zone-0-exhaust (SFB only)

  • properties/property/temperature-zone-1-exhaust (SFB only)

  • properties/property/temperature-zone-0-intake-c (CB only)

  • properties/property/temperature-zone-0-exhaust-a (CB only)

  • properties/property/temperature-zone-1-exhaust-b (CB only)

/lacp/

Sensor for operational state of aggregated Ethernet interfaces configured with the Link Aggregation Control Protocol.

Supported on QFX10000 switches and QFX5200 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 switches starting with Junos OS Release 18.1R1.

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

Supported on EX4600 switches starting with unos OS Release 18.4R1,

You can also add the following to the end of the path for /lacp/:

  • state/system-priority

  • interfaces/interface[name='aggregate-interface-name']/state/

  • interfaces/interface[name='aggregate-interface-name']

    /members/member[interface='interface-name']/state/

  • interfaces/interface[name='aggregate-interface-name']

    /members/member[interface='interface-name']/state/counters/

  • interfaces/interface[name='aggregate-interface-name']

    /members/member[interface='interface-name']/state/port-num

  • interfaces/interface[name='aggregate-interface-name']

    /members/member[interface='interface-name']/state/partner-port-num

  • interfaces/interface[name='aggregate-interface-name']

    /members/member[interface='interface-name']/state/mux-state

/lldp/

Sensor for operational state of Ethernet interfaces enabled with the Link Layer Discovery Protocol.

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

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

Supported on QFX5100 switches starting with Junos OS Release 18.1R1.

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..

ON_CHANGE streaming is supported on MX Series and PTX Series routers, starting with Junos OS Release 18.3R1.

You can also add the following to the end of the path for /lldp/:

Note: End paths supporting ON_CHANGE streaming are indicated.

  • state/

  • state/enabled

    ON_CHANGE streaming supported

  • state/hello-timer

    ON_CHANGE streaming supported

  • state/system-name

    ON_CHANGE streaming supported

  • state/system-description

    ON_CHANGE streaming supported

  • state/chassis-id

    ON_CHANGE streaming supported

  • state/chassis-id-type

    ON_CHANGE streaming supported

  • state/loc-port-id-type

  • interfaces/interface[name='interface-name']/state/

  • interfaces/interface[name='interface-name']/state/counters/

  • interfaces/interface[name='interface-name']/state/enabled

    ON_CHANGE streaming supported

  • interfaces/interface[name='interface-name']/state/name

    ON_CHANGE streaming supported

  • interfaces/interface[name='interface-name']/neighbors/

  • interfaces/interface[name='interface-name']/neighbors/neighbor/capabilities

    ON_CHANGE streaming supported

  • interfaces/interface[name='interface-name']/neighbors/neighbor/state/chassis-id

    ON_CHANGE streaming supported. This resource path does not change with an event, but will be streamed on creation and deletion.

  • interfaces/interface[name='interface-name']/neighbors/neighbor/state/chassis-id-type

    ON_CHANGE streaming supported. This resource path does not change with an event, but will be streamed on creation and deletion.

  • interfaces/interface[name='interface-name']/neighbors/neighbor/state/port-id

    ON_CHANGE streaming supported

  • interfaces/interface[name='interface-name']/neighbors/neighbor/state/port-id-type

    ON_CHANGE streaming supported

  • interfaces/interface[name='interface-name']/neighbors/neighbor/state/port-description

    ON_CHANGE streaming supported

  • interfaces/interface[name='interface-name']/neighbors/neighbor/state/system-name

    ON_CHANGE streaming supported. This resource path does not change with an event, but will be streamed on creation and deletion.

  • interfaces/interface[name='interface-name']/neighbors/neighbor/state/system-description

    ON_CHANGE streaming supported

  • interfaces/interface[name='interface-name']/neighbors/neighbor/state/management-address

    ON_CHANGE streaming supported

  • interfaces/interface[name='interface-name']/neighbors/neighbor/state/management-address-type

    ON_CHANGE streaming supported

/mpls/lsps/constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/lsp-instances[index='local-index']/state/notify-status

Sensor to export events 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.

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/p2p-primary-path

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

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

The following events are exported under this resource path:

  • INITIATED

  • CONCLUDED_UP

  • CONCLUDED_TORN_DOWN

  • PROTECTION_AVAILABLE

  • PROTECTION_UNAVAILABLE

  • AUTOBW_SUCCESS

  • AUTOBW_FAIL

  • TUNNEL_LOCAL_REPAIRED

  • PATHERR_RECEIVED

    • ADMISSION_CONTROL_FAILURE

    • SESSION_PREEMPTED

    • BAD_LOOSE_ROUTE

    • BAD_STRICT_ROUTE

    • LABEL_ALLOCATION_FAILURE

    • ROUTING_LOOP_DETECTED

    • REQUESTED_BANDWIDTH_UNAVAILABLE

/mpls/lsps/constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/state/notify-status

Sensor to export events 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.

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/p2p-primary-path

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

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

The following events are exported under this resource path:

  • DESELECT_ACTIVE_PATH

  • CHANGE_ACTIVE_PATH

  • SELECT_ACTIVE_PATH

  • ORIGINATE_MBB

  • CSPF_NO_ROUTE

  • CSPF_SUCCESS

  • RESTART_RECOVERY_FAIL

/mpls/lsps/constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/state/name

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 switches, and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1.

/mpls/lsps/constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/lsp-instances[index='local-index']/state/

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 switches, 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

/mpls/lsps/signaling-protocols/rsvp-te/sessions/session[local-index='foo-index']/state/notify-status

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 switches, 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

/network-instances/network-instance/mpls/signaling-protocols/rsvp-te/sessions/session/state/notify-status

Supported on Junos OS Release through 17.4R1 and higher.

Sensor to export events 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 switches, and QFX10002, QFX10008, and QFX10016 switches starting with Junos OS Release 17.2R1.

The following events are exported under this resource path:

  • DETOUR-UP

  • DETOUR-DOWN

  • PATHERR-RECV

  • PATHERR-RECV/ADMISSION_CONTROL_FAILURE

  • PATHERR-RECV/SESSION_PREEMPTED

  • PATHERR-RECV/BAD_LOOSE_ROUTE

  • PATHERR-RECV/BAD_STRICT_ROUTE

  • PATHERR-RECV/LABEL_ALLOCATION_FAILURE

  • PATHERR-RECV/NON_RSVP_CAPABLE_ROUTER

  • PATHERR-RECV/TTL_EXPIRED

  • PATHERR-RECV/ROUTING_LOOP_DETECTED

  • PATHERR-RECV/REQUESTED_BANDWIDTH_UNAVAILABLE

  • PATHMTU-CHANGE

/mpls/signaling-protocols/segment-routing/

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.

/arp-information/

Sensor for Address Resolution Protocol (ARP) statistics.

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

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

Supported on QFX5100 switches starting with Junos OS Release 18.1R1.

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.

You can also add the following to the end path for /arp-information/

  • ipv4

  • ipv4/neighbors

  • ipv4/neighbors/neighbor

  • ipv4/neighbors/neighbor/ip

  • ipv4/neighbors/neighbor/link-layer-address

  • pv4/neighbors/neighbor/origin

  • ipv4/neighbors/neighbor/host-name

  • ipv4/neighbors/neighbor/rtb-id

  • ipv4/neighbors/neighbor/state

  • ipv4/neighbors/neighbor/expiry

  • ipv4/neighbors/neighbor/ispublish

  • ipv4/neighbors/neighbor/interface-name

  • ipv4/neighbors/neighbor/logical-router-id

/interfaces/interface[name='interface-name']/

Sensor for Routing Engine internal interfaces.

Note: On MX Series routers, you can specify the following interfaces: fxp0, em0, and em1

On PTX Series routers, you can specify the following interfaces: em0, ixlv0, ixlv1

On PTX Series routers with dual Routing Engines, you can specify the following interfaces: em0, ixgbe0, ixgbe1

Support on PTX1000 routers starting with Junos OS Release 17.3R1.

The following end paths are also supported:

  • interfaces/interface/state/type

  • /interfaces/interface/state/mtu

  • /interfaces/interface/state/name

  • /interfaces/interface/state/description

  • /interfaces/interface/state/enabled

  • /interfaces/interface/state/ifindex

  • /interfaces/interface/state/admin-status

  • /interfaces/interface/state/oper-status

  • /interfaces/interface/state/last-change

  • /interfaces/interface/state/speed

  • /interfaces/interface/state/counters/in-octets

  • /interfaces/interface/state/counters/in-unicast-pkts

  • /interfaces/interface/state/counters/in-broadcast-pkts

  • /interfaces/interface/state/counters/in-multicast-pkts

  • /interfaces/interface/state/counters/in-discards

  • /interfaces/interface/state/counters/in-errors

  • /interfaces/interface/state/counters/in-unknown-protos

  • /interfaces/interface/state/counters/out-octets

  • /interfaces/interface/state/counters/out-unicast-pkts

  • /interfaces/interface/state/counters/out-broadcast-pkts

  • /interfaces/interface/state/counters/out-multicast-pkts

  • /interfaces/interface/state/counters/out-discards

  • /interfaces/interface/state/counters/out-errors

  • /interfaces/interface/state/counters/last-clear

  • /interfaces/interface/state/counters/in-pkts

  • /interfaces/interface/state/counters/in-sec-pkts

  • /interfaces/interface/state/counters/in-sec-octets

  • /interfaces/interface/state/counters/in-pause-pkts

  • /interfaces/interface/state/counters/out-pkts

  • /interfaces/interface/state/counters/out-sec-pkts

  • /interfaces/interface/state/counters/out-sec-octets

  • /interfaces/interface/state/counters/out-pause-pkts

  • /interfaces/interface/state/counters/in-drops

  • /interfaces/interface/state/counters/in-frame-errors

  • /interfaces/interface/state/counters/in-runts

  • /interfaces/interface/state/counters/in-lchan-errors

  • /interfaces/interface/state/counters/in-l-mismatch-errors

  • /interfaces/interface/state/counters/in-fifo-errors

  • /interfaces/interface/state/counters/in-giants

  • /interfaces/interface/state/counters/in-resource-errors

  • /interfaces/interface/state/counters/out-drops

  • /interfaces/interface/state/counters/carrier-transitions

  • /interfaces/interface/state/counters/mtu-errors

  • /interfaces/interface/state/counters/out-resource-errors

  • /interfaces/interface/subinterfaces/subinterface/index

  • /interfaces/interface/subinterfaces/subinterface/state/index

  • /interfaces/interface/subinterfaces/subinterface/state/name

  • /interfaces/interface/subinterfaces/subinterface/state/description

  • /interfaces/interface/subinterfaces/subinterface/state/enabled

  • /interfaces/interface/subinterfaces/subinterface/state/ifindex

  • /interfaces/interface/subinterfaces/subinterface/state/admin-status

  • /interfaces/interface/subinterfaces/subinterface/state/oper-status

  • /interfaces/interface/subinterfaces/subinterface/state/last-change

  • /interfaces/interface/subinterfaces/subinterface/state/counters/in-pkts

  • /interfaces/interface/subinterfaces/subinterface/state/counters/in-octets

  • /interfaces/interface/subinterfaces/subinterface/state/counters/in-unicast-pkts

  • /interfaces/interface/subinterfaces/subinterface/state/counters/in-broadcast-pkts

  • /interfaces/interface/subinterfaces/subinterface/state/counters/in-multicast-pkts

  • /interfaces/interface/subinterfaces/subinterface/state/counters/in-discards

  • /interfaces/interface/subinterfaces/subinterface/state/counters/in-errors

  • /interfaces/interface/subinterfaces/subinterface/state/counters/in-unknown-protos

  • /interfaces/interface/subinterfaces/subinterface/state/counters/out-octets

  • /interfaces/interface/subinterfaces/subinterface/state/counters/out-unicast-pkts

  • /interfaces/interface/subinterfaces/subinterface/state/counters/out-broadcast-pkts

  • /interfaces/interface/subinterfaces/subinterface/state/counters/out-multicast-pkts

  • /interfaces/interface/subinterfaces/subinterface/state/counters/out-discards

  • /interfaces/interface/subinterfaces/subinterface/state/counters/out-errors

  • /interfaces/interface/subinterfaces/subinterface/state/counters/last-clear

  • /interfaces/interface/subinterfaces/subinterface/state/counters/out-pkts

/nd6-information/

Sensor for Network Discovery Protocol (NDP) table state.

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

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

Supported on QFX5100 switches starting with Junos OS Release 18.1R1.

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.

You can also add the following to the end path for nd6-information/

  • ipv6

  • ipv6/neighbors

  • ipv6/neighbors/neighbor

  • ipv6/neighbors/neighbor/ip

  • ipv6/neighbors/neighbor/link-layer-address

  • ipv6/neighbors/neighbor/origin

  • ipv6/neighbors/neighbor/isrouter

  • ipv6/neighbors/neighbor/state

  • ipv6/neighbors/neighbor/rtb-id

  • ipv6/neighbors/neighbor/issecure

  • ipv6/neighbors/neighbor/ispublish

  • ipv6/neighbors/neighbor/expiry

  • ipv6/neighbors/neighbor/interface-name

  • ipv6/neighbors/neighbor/logical-router-id

/ipv6-ra/

Sensor for NDP router-advertisement statistics.

/junos/system/linecard/packet/usage/

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.

/network-instances/network-instance/protocols/protocol/isis/levels/level/

/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/levels/level/

Sensor for IS-IS routing protocol statistics. Statistics are exported separately for each routing instance.

To specify a routing-instance name:

/network-instances/network-instance[name_'instance-name']/protocols/protocol/isis/levels/level/

/network-instances/network-instance[name_'instance-name']/protocols/protocol/isis/interfaces/interface/levels/level/

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

The following paths are also supported:

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/lsp/received

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/lsp/processed

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/lsp/dropped

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/lsp/sent

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/lsp/retransmit

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/iih/received

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/iih/processed

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/iih/dropped

  • /network-instances/network-instance/protocols/protocol

    /isis/interfaces/interface/levels/level/packet-counters/iih/sent

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/iih/retransmit

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/psnp/received

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/psnp/processed

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/psnp/dropped

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/psnp/sent

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/psnp/retransmit

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/cnsp/received

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/cnsp/processed

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/cnsp/dropped

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interface/levels/level/packet-counters/cnsp/sent

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/corrupted-lsps

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/database-overloads

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/manual-address-drop-from-area

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/exceeded-max-seq-nums

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/seq-num-skips

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/own-lsp-purges

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/id-len-mismatch

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/part-changes

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/max-area-address-mismatches

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/auth-fails

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/spf-runs

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/auth-type-fails

  • /network-instances/network-instance/protocols/protocol/

    isis/levels/level/system-level-counters/state/lsp-errors

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/circuit-counters/state/adj-changes

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/circuit-counters/state/adj-number

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/circuit-counters/state/auth-fails

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/circuit-counters/state/auth-type-fails

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/circuit-counters/state/id-field-len-mismatches

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/circuit-counters/state/lan-dis-changes

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/circuit-counters/state/max-area-address-mismatch

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/circuit-counters/state/rejected-adj

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/system-id

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/dis-system-id

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/local-extended-system-id

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-extended-system-id

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/adjacency-state

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-circuit-type

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-ipv4-address

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-ipv6-address

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/neighbor-snpa

  • /network-instances/network-instance/protocols/protocol/

    isis/interfaces/interfaces/levels/levels/level/adjacencies/adjacency/state/priority

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/remaining-hold-time

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/restart-status

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/restart-support

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/restart-suppress

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/up-time

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interface/levels/level/adjacencies/adjacency/state/nlpid

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interface/levels/level/adjacencies/adjacency/state/area-address

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/topologies

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/multi-topology

  • /network-instances/network-instance/protocols/protocol/isis/

    interfaces/interfaces/levels/level/adjacencies/adjacency/state/adjacency-type

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/

    prefixes/prefix/state/ipv4-prefix

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    extended-ipv4-reachability/prefixes/prefix/state/up-down

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    extended-ipv4-reachability/prefixes/prefix/state/s-bit

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    extended-ipv4-reachability/prefixes/prefix/state/metric

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/flags

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/ipv4-source-router-id

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/

    ipv6-source-router-id/state/ipv6-source-router-id

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/tag64

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    extended-ipv4-reachability/prefixes/prefix/subtlvs/subtlv/flags/state/tag32

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/

    prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/type

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/

    prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/length

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/

    prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/value

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/

    prefixes/prefix/subtlvs/subtlv/prefix-sid/sid/state/value

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/

    prefixes/prefix/subtlvs/subtlv/flags/state/flags

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/extended-ipv4-reachability/

    prefixes/prefix/subtlvs/subtlv/flags/state/algorithm

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/

    tlvs/tlv/ipv6-reachability/prefixes/prefix/state/ipv6-prefix

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/

    tlvs/tlv/ipv6-reachability/prefixes/prefix/state/up-down

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    ipv6-reachability/prefixes/prefix/state/s-bit

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    ipv6-reachability/prefixes/prefix/state/x-bit

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    ipv6-reachability/prefixes/prefix/state/metric

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    ipv6-reachability/prefixes/prefix/state/ipv6-prefix

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/

    prefixes/prefix/subtlvs/subtlv/ipv4-source-router-id/state/ipv4-source-router-id

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/

    prefixes/prefix/subtlvs/subtlv/ipv6-source-router-id/state/ipv6-source-router-id

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    ipv6-reachability/prefixes/prefix/subtlvs/subtlv/tag64/state/tag64

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/

    prefixes/prefix/subtlvs/subtlv/tag64/state/tag32

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/

    prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/type

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/

    prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/length

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/

    prefixes/prefix/undefined-subtlvs/undefined-subtlv/state/value

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    ipv6-reachability/prefixes/prefix/subtlvs/subtlv/prefix-sid/sid/state/value

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/

    prefixes/prefix/subtlvs/subtlv/prefix-sid/sid/state/flags

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/ipv6-reachability/

    prefixes/prefix/subtlvs/subtlv/prefix-sid/sid/state/algorithm

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    router-capabilities/router-capability/state/flags

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/tlvs/tlv/

    router-capabilities/router-capability/state/rtr-id

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/lsp/undefined-tlvs/undefined-tlv/state/type

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/

    lsp/undefined-tlvs/undefined-tlv/state/length

  • /network-instances/network-instance/protocols/protocol/isis/

    levels/level/link-state-database/

    lsp/undefined-tlvs/undefined-tlv/state/value

/junos/services/segment-routing/interface/ingress/usage/

/junos/services/segment-routing/interface/egress/usage/

/junos/services/segment-routing/sid/usage/

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.

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.

Note: When you enable a sensor for segment routing statistics, you must also configure the sensor-based-stats statement at the [edit protocols isis source-packet-routing] hierarchy level.

All MX and PTX5000 routers with FPC3 onwards support enhanced mode. If enhanced mode is not enabled, configure either the enhanced-ip statement or the enhanced-ethernet statement at the [edit chassis network-services] hierarchy level. On PTX Series routers, configure the enhanced-mode statement at the [edit chassis network-services] hierarchy level.

Note: Currently, MPLS labels correspond only to only one instance, instance 0. Since each SID corresponds to a single instance_identifier, no aggregation is required to be done by the collector. The instance_identifier is stamped as 0.

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

/junos/services/segment-routing/sid/usage/

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.

Note: When you enable a sensor for segment routing statistics, you must also configure the sensor-based-stats statement at the [edit protocols isis source-packet-routing] hierarchy level.

Table 2: Broadband Edge gRPC Sensors

resource path

Description

/junos/system/subscriber-management/aaa/accounting-statistics/

Sensor that tracks accounting statistics by means of a protocol exchange with accounting servers.

You can also add the following to the end path for /junos/system/subscriber-management/aaa/accounting-statistics/:

  • acct-req-received

  • acct-req-timeout

  • acct-resp-failure

  • acct-resp-success

  • acct-req-start

  • acct-req-interim

  • acct-req-stop

  • acct-resp-total

  • acct-resp-start

  • acct-resp-interim

  • acct-resp-stop

  • acct-resp-total

/junos/system/subscriber-management/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance/pools/pool

For Authentication, Authorization, and Accounting, this sensor tracks address pool utilization.

The resource path can be refined to select a logical system routing instance by using a logical system routing instance filter:

/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance [lsri-name=’ lsName:riName’]/pools/pool[pool-name=’ poolName’]

The resource path can be refined to select a specific pool by using a pool filter:

/junos/system/subscriber-management/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance/pools/pool[pool-name=’ poolName’]

The resource path can be refined to select both a logical routing instance and a pool by using a logical system routing instance filter and a pool filter:

/junos/system/subscriber-management/aaa/address-assignment-statistics/logical-system-routing-instances/logical-system-routing-instance/[lsri-name=’ lsName:riName’]/pools/pool[pool-name=’ poolName’]

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

  • pool-name

  • out-of-memory

  • out-of-address

  • address-total

  • address-in-use

  • address-usage-percent

  • linked-pool-name-The next address pool in the chain of linked pools. If there is no next address pool, the value is empty.

  • linked-pool-head-The first address pool in a chain of linked pools. If this pool is not part of a linked address pool, the value is empty.

/junos/system/subscriber-management/access-network/ancp/adapter

Sensors that track statistics associated with Access Node Control Protocol (ANCP) adapter.

mapped-dynamic-subscriber-countNumber of ANCP subscribers mapped to dynamic interfaces by ANCP adapter.

/junos/system/subscriber-management/access-network/ancp/protocol

Sensors that track statistics associated with ANCP protocol.

establishing-neighbor-countNumber of neighbors in the process of establishing adjacency.
established-neighbor-countNumber of neighbors in the process of establishing adjacency
total-neighbor-countTotal number of neighbors in all states.
mapped-static-subscriber-countNumber of ANCP subscribers mapped to static interfaces by ANCP protocol.
port-up-countTotal number of port ups received.
port-down-count Total number of port downs received.

/junos/system/subscriber-management/aaa/authentication-statistics/

Sensors that track authentication, authorization, and accounting (AAA) authentication, pre-authentication, and re-authentication statistics.

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

  • req-received

  • req-accepted

  • req-rejected

  • req-challenge

  • req-timeout

  • pre-authen-req-received

  • pre-authen-req-accepted

  • pre-authen-req-rejected

  • pre-authen-req-challenge

  • pre-authen-req-timeout

  • re-authen-req-received

  • re-authen-req-accepted

  • re-authen-req-rejected

  • re-authen-req-internal-errors

  • re-authen-req-challenge

  • re-authen-req_timeout

/junos/system/subscriber-management/aaa/dynamic-request-statistics/

Sensor tracks dynamic request statistics from AAA server-initiated requests, including Change of Authorization (CoA) and RADIUS-initiated Disconnect (RID).

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

  • dynamic-req-received

  • dynamic-req-success

  • dynamic-req-error

  • dynamic-req-silently-drop

/junos/system/subscriber-management/aaa/radius-servers/radius-server/response-time/

Sensor for RADIUS server response time statistics for a specific server.

A request sent to the RADIUS server is counted as a message sent. Similarly, a response to the request is counted as a message received. A timeout during the measurement interval does not impact the minimum, average, or maximum response time statistics, but the event is counted as a no response.

The delay measurements are made over a 60-second measurement interval. The reporting interval can be as much as 59 seconds out of phase with the measurement interval. At reporting time, the values from the last update interval are reported. The response time values are not aligned with the reporting interval.

The resource path can be refined to select a specific RADIUS server by adding a server address filter to the resource path:

/junos/system/subscriber-management//aaa/radius-servers/radius-server[server-address=’radiusIpv4Address’]/response-time/

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

  • one-minute-minimum-response-time

  • one-minute-average-response-time

  • one-minute-maximum-response-time

  • one-minute-messages-sent

  • one-minute-messages-received

  • one-minute-messages-no-response

/junos/system/subscriber-management/aaa/radius-servers/radius-server/statistics/

Sensor for RADIUS server statistics for a specific server.

The resource path can be refined to select a specific RADIUS server by adding a server address filter to the resource path:

/junos/system/subscriber-management//aaa/radius-servers/radius-server[server-address=’radiusIpv4Address’]/statistics/

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

  • server-address

  • server-last-rtt

  • auth-access-requests

  • auth-rollover-requests

  • auth-retransmissions

  • auth-access-accepts

  • auth-access-rejects

  • auth-access-challenges

  • auth-malformed-responses

  • auth-bad-authenticators

  • auth-req-pending

  • auth-request-timeouts

  • auth-unknown-responses

  • auth-packets-dropped

  • preauth-access-requests

  • preauth-rollover-requests

  • preauth-retransmissions

  • preauth-access-accepts

  • preauth-access-rejects

  • preauth-access-challenges

  • preauth-malformed-responses

  • preauth-bad-authenticators

  • preauth-req-pending

  • preauth-request-timeouts

  • preauth-unknown-responses

  • preauth-packets-dropped

  • acct-start-requests

  • acct-interim-requests

  • acct-stop-requests

  • acct-rollover-requests

  • acct-retransmissions

  • acct-start-responses

  • acct-interim-responses

  • acct-stop-responses

  • acct-malformed-responses

  • acct-bad-authenticators

  • acct-req-pending

  • acct-request-timeouts

  • acct-unknown-responses

  • acct-packets-dropped

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/relay/bindings/

Sensor for DHVPv4 relay binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance name:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[name=’ routing-instance-name]/relay/bindings/

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

  • binding-state-v4relay-binding

  • binding-state-v4relay-init

  • binding-state-v4relay-bound

  • binding-state-v4relay-selecting

  • binding-state-v4relay-requesting

  • binding-state-v4relay-renew

  • binding-state-v4relay-release

  • binding-state-v4relay-restoring

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/relay/servers/server/response-time

Sensor for DHVPv4 server delay. The sensor periodically measures the minimum, average, and maximum delay or response time from the upstream DHCP server(s), as seen by the relay.

DHCP relay does not track the state of the server. The no-response statistics are the difference between the messages sent and received during the measurement interval.

The delay measurements are made over a 60-second measurement interval. Because the reporting interval can be as much as 59 seconds out of phase with the measurement interval, there is no design to align the response time values with the reporting interval.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[name=’ routing-instance-name]/relay/servers/server/response-time

The resource path can be refined to select a specific DHCP server by adding a server filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/relay/servers/server[server-ip=’ server-ip’]/response-time

The resource path can be refined to select a specific DHCP server in a specific routing instance by adding both a routing instance filter and a server filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[name=’ routing-instance-name]/relay/servers/server[server-ip=’ server-ip’]/response-time

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

  • one-minute-minimum-response-time

  • one-minute-average-response-time

  • one-minute-maximum-response-time

  • one-minute-messages-sent

  • one-minute-messages-received

  • one-minute-messages-no-response

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/server/bindings/

Sensor for DHVPv4 server binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[name=’ routing-instance-name]/server/bindings/

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

  • binding-state-v4server-binding

  • binding-state-v4server-init

  • binding-state-v4server-bound

  • binding-state-v4server-selecting

  • binding-state-v4server-requesting

  • binding-state-v4server-renew

  • binding-state-v4server-release

  • binding-state-server-restoring

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/server/statistics/

Sensor for DHCPv4 telemetry for server statistics for a specific routing-instance.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics/

For example, the following resource path defines server statistics for the default:n000015k routing instance: /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ n000015k]/server/statistics

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’] /server/statistics/ the only value supported for routing-instance-name is default.

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

  • dropped-v4server-total

  • dropped-v4server-bad-hware

  • dropped-v4server-bootp-pkt

  • dropped-v4server-bad-bootp-opcode

  • dropped-v4server-bad-options

  • dropped-v4server-bad-address

  • dropped-v4server-no-address

  • dropped-v4server-no-interface-cfg

  • dropped-v4server-no-local-address

  • dropped-v4server-short-pkt

  • dropped-v4server-no-bad-send

  • dropped-v4server-no-option60

  • dropped-v4server-no-option82

  • dropped-v4server-authentication

  • dropped-v4server-dynamic-profile

  • dropped-v4server-no-license

  • dropped-v4server-no-bad-dhcp-opcode

  • dropped-v4server-no-options

  • dropped-v4server-hop-limit

  • dropped-v4server-ttl-expired

  • dropped-v4server-bad_udp-checksum

  • dropped-v4server-inactive-vlan

  • dropped-v4server-era-start-ailed

  • dropped-v4server-client-lookup

  • dropped-v4server-lease-time-violation

  • offer-delayed

  • offer-delay-in-progress

  • offer-delay-total

  • msg-recv-v4server-boot-request

  • msg-recv-v4server-decline

  • msg-recv-v4server-discover

  • msg-recv-v4server-inform

  • msg-recv-v4server-release

  • msg-recv-v4server-request

  • msg-recv-v4server-renew

  • msg-recv-v4server-rebind

  • msg-recv-v4server-lease-query

  • msg-recv-v4server-bulklease-query

  • msg-sent-v4server-boot-reply

  • msg-sent-v4server-offer

  • msg-sent-v4server-boot-ack

  • msg-sent-v4server-nak

  • msg-sent-v4server-force-renew

  • msg-sent-v4server-unassigned

  • msg-sent-v4server-unknown

  • msg-sent-v4server-active

  • msg-sent-v4server-query-done

/junos/system/subscriber-management/client-protocols/dhcp/v4/

Sensor for DHCPv4 telemetry.

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

  • dropped-total

  • dropped-bad-read

  • dropped-ip-header

  • dropped-short-packet

  • dropped-no-interface

  • dropped-no-routing-instance

  • dropped-no-memory

  • dropped-recovery-in-progress

  • era-inflight-count

  • era-reported-failures

  • era-reported-successes

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/server/statistics/

Sensor for DHVPv4 server statistics

The resource path can be refined to select a specific routing instance by adding a routing instance name:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics/

For example, the following resource path defines server statistics for the default:n000015k routing instance: /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ n000015k]/server/statistics

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-ancpinstance[ri-name=’ routing-instance-name’] /server/statistics/ the only value supported for routing-instance-name is default.

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

  • dropped-v4server-total

  • dropped-v4server-bad-hware

  • dropped-v4server-bootp-pkt

  • dropped-v4server-bad-bootp-opcode

  • dropped-v4server-bad-options

  • dropped-v4server-bad-address

  • dropped-v4server-no-address

  • dropped-v4server-no-interface-cfg

  • dropped-v4server-no-local-address

  • dropped-v4server-short-pkt

  • dropped-v4server-no-bad-send

  • dropped-v4server-no-option60

  • dropped-v4server-no-option82

  • dropped-v4server-authentication

  • dropped-v4server-dynamic-profile

  • dropped-v4server-no-license

  • dropped-v4server-no-bad-dhcp-opcode

  • dropped-v4server-no-options

  • dropped-v4server-hop-limit

  • dropped-v4server-ttl-expired

  • dropped-v4server-bad_udp-checksum

  • dropped-v4server-inactive-vlan

  • dropped-v4server-era-start-ailed

  • dropped-v4server-client-lookup

  • dropped-v4server-lease-time-violation

  • offer-delayed

  • offer-delay-in-progress

  • offer-delay-total

  • msg-recv-v4server-boot-request

  • msg-recv-v4server-decline

  • msg-recv-v4server-discover

  • msg-recv-v4server-inform

  • msg-recv-v4server-release

  • msg-recv-v4server-request

  • msg-recv-v4server-renew

  • msg-recv-v4server-rebind

  • msg-recv-v4server-lease-query

  • msg-recv-v4server-bulklease-query

  • msg-sent-v4server-boot-reply

  • msg-sent-v4server-offer

  • msg-sent-v4server-boot-ack

  • msg-sent-v4server-nak

  • msg-sent-v4server-force-renew

  • msg-sent-v4server-unassigned

  • msg-sent-v4server-unknown

  • msg-sent-v4server-active

  • msg-sent-v4server-query-done

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance/relay/statistics/

Sensor for DHVPv4 relay binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics/

For example, the following resource path defines relay statistics for the default:n000015k routing instance: /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ n000015k]/relay/statistics

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics/ the only value supported for the value routing-instance-name is default.

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

  • dropped-v4relay-total

  • dropped-v4relay-bad-hardware

  • dropped-v4relay-bootp-packet

  • dropped-v4relay-bad-bootp-opcode

  • dropped-v4relay-bad-options

  • dropped-v4relay-bad-address

  • dropped-v4relay-no-address

  • dropped-v4relay-no-interface-cfg

  • dropped-v4relay-no-local-address

  • dropped-v4relay-short-packet

  • dropped-v4relay-bad-send

  • dropped-v4relay-option-60

  • dropped-v4relay-relay-option

  • dropped-v4relay-option-82

  • dropped-v4relay-authentication

  • dropped-v4relay-dynamic-profile

  • dropped-v4relay-dynamic-profile

  • dropped-v4relay-license

  • dropped-v4relay-bad-dhcp-opcode

  • dropped-v4relay-no-options

  • dropped-v4relay-hop-limit

  • dropped-v4relay-ttl-expired

  • dropped-v4relay-bad-udp-checksum

  • dropped-v4relay-inactive-vlan

  • dropped-v4relay-era-start-failed

  • dropped-v4relay-client-lookup

  • dropped-v4relay-proxy-no-server-addr

  • dropped-v4relay-lease-time-violation

  • dropped-v4relay-leasequery-repl-no-circuitid

  • dropped-v4relay-leasequery-repl-with-error-code

  • dropped-v4relay-leasequery-repl-with-query-term

  • dropped-v4relay-older-leasequery-reply

  • dropped-v4relay-abort-leasequery-reply-proc

  • dropped-v4relay-during-leasequery-reply

  • dropped-v4relay-relay-source-no-lpbk-interface

  • v4relay-bootp-request-rcvd

  • msg-recv-v4relay-decline

  • msg-recv-v4relay-discover

  • msg-recv-v4relay-inform

  • msg-recv-v4relay-release

  • msg-recv-v4relay-request

  • msg-recv-v4relay-leaseactive

  • msg-recv-v4relay-leaseunassigned

  • msg-recv-v4relay-leaseunknown

  • msg-recv-v4relay-leasequerydone

  • v4relay-bootp-reply-rcvd

  • msg-recv-v4relay-offer

  • msg-recv-v4relay-ack

  • msg-recv-v4relay-nak

  • msg-recv-v4relay-forcerenew

  • v4relay-bootp-reply-sent

  • msg-sent-v4relay-offer

  • msg-sent-v4relay-ack

  • msg-sent-v4relay-nak

  • msg-sent-v4relay-forcerenew

  • msg-sent-v4relay-leasequery

  • msg-sent-v4relay-bulkleasequery

  • v4relay-bootp-request-sent

  • msg-sent-v4relay-decline

  • msg-sent-v4relay-discover

  • msg-sent-v4relay-inform

  • msg-sent-v4relay-release

  • msg-sent-v4relay-request

  • v4relay-bootp-forwarded-total

  • v4relay-bootp-request-fwd

  • v4relay-bootp-reply-fwd

/junos/system/subscriber-management/client-protocols/dhcp/v6/

Sensor for DHCPv6 statistics.

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

  • era-inflight-count

  • era-reported-failures

  • era-reported-successes

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/relay/bindings/

Sensor for DHVPv6 relay binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance name:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[name=’ routing-instance-name]/relay/bindings/

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

  • binding-state-v6relay-binding

  • binding-state-v6relay-init

  • binding-state-v6relay-bound

  • binding-state-v6relay-selecting

  • binding-state-v6relay-requesting

  • binding-state-v6relay-renew

  • binding-state-v6relay-release

  • binding-state-relay-restoring

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/relay/servers/server/response-time

Sensor for DHVPv6 server delay. The sensor periodically measures the minimum, average, and maximum delay or response time from the upstream DHCP server(s), as seen by the relay.

DHCP relay does not track the state of the server. The no-response statistics are the difference between the messages sent and received during the measurement interval.

The delay measurements are made over a 60-second measurement interval. Because the reporting interval can be as much as 59 seconds out of phase with the measurement interval, there is no design to align the response time values with the reporting interval.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[name=’ routing-instance-name]/relay/servers/server/response-time

The resource path can be refined to select a specific DHCP server by adding a server address filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/relay/servers/server[server-ip=’ server-ip’]/response-time

The resource path can be refined to select a specific DHCP server in a specific routing instance by adding both a routing instance filter and a server filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[name=’ routing-instance-name]/relay/servers/server [server-ip=’ server-ip’]/response-time

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

  • one-minute-minimum-response-time

  • one-minute-average-response-time

  • one-minute-maximum-response-time

  • one-minute-messages-sent

  • one-minute-messages-received

  • one-minute-messages-no-response

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/server/bindings/

Sensor for DHVPv6 binding state statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[name=’ routing-instance-name]/server/bindings/

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

  • binding-state-v6server-binding

  • binding-state-v6server-init

  • binding-state-v6server-bound

  • binding-state-v6server-selecting

  • binding-state-v6server-requesting

  • binding-state-v6server-renew

  • binding-state-v6server-release

  • binding-state-server-restoring

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/server/statistics/

Sensor for DHCPv6 server statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics/

For example, the following resource path defines server statistics for the default:n000015k routing instance: /junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[ri-name=’ n000015k]/server/statistics

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics the only value supported for routing-instance-name is default.

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

  • dropped-v6server-total

  • dropped-v6server-no-routing-instance

  • dropped-v6server-bad-send

  • dropped-v6server-short-packet

  • dropped-v6server-bad-msgtype

  • dropped-v6server-bad-options

  • dropped-v6server-bad-srcaddress

  • dropped-v6server-relay-hop-count

  • dropped-v6server-bad-udp-checksum

  • dropped-v6server-no-client-id

  • dropped-v6server-strict-reconfigure

  • dropped-v6server-option-18

  • dropped-v6server-authentication{

  • dropped-v6server-dynamic-profile

  • dropped-v6server-license

  • dropped-v6server-inactive-vlan

  • dropped-v6server-era-start-failed

  • dropped-v6server-client-lookup

  • dropped-v6server-lease-time-violation

  • advertise-delayed

  • advertise-queued

  • advertise-total

  • msg-recv-v6server-dhcpv6-decline

  • msg-recv-v6server-dhcpv6-solicit

  • msg-recv-v6server-dhcpv6-information-request

  • msg-recv-v6server-dhcpv6-release

  • msg-recv-v6server-dhcpv6-request

  • msg-recv-v6server-dhcpv6-confirm

  • msg-recv-v6server-dhcpv6-renew

  • msg-recv-v6server-dhcpv6-rebind

  • msg-recv-v6server-dhcpv6-relay-forw

  • msg-recv-v6server-dhcpv6-leasequery

  • msg-sent-v6server-advertise

  • msg-sent-v6server-reply

  • msg-sent-v6server-logical_nak

  • msg-sent-v6server-reconfigure

  • msg-sent-v6server-relay-repl

  • msg-sent-v6server-leasequery-repl

  • msg-sent-v6server-leasequery-data

  • msg-sent-v6server-leasequery-done

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance/relay/statistics/

Sensor for DHVPv6 relay statistics.

The resource path can be refined to select a specific routing instance by adding a routing instance filter to the resource path:

/junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics/

For example, the following resource path defines relay statistics for the default:n000015k routing instance: /junos/system/subscriber-management/client-protocols/dhcp/v6/routing-instances/routing-instance[ri-name=’ n000015k]/relay/statistics

In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics the only value supported for routing-instance-name is default.

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

  • dropped-v6relay-total

  • dropped-v6relay-no-safd

  • dropped-v6relay-no-routing-instance

  • dropped-v6relay-bad-send

  • dropped-v6relay-short-packet

  • dropped-v6relay-bad-msgtype

  • dropped-v6relay-bad-options

  • dropped-v6relay-bad-srcaddress

  • dropped-v6relay-relay-hop-count

  • dropped-v6relay-bad-udp-checksum

  • dropped-v6relay-no-client-id

  • dropped-v6relay-strict-reconfigure

  • dropped-v6relay-relay-option

  • dropped-v6relay-option-18

  • dropped-v6relay-option-37

  • dropped-v6relay-authentication

  • dropped-v6relay-dynamic-profile

  • dropped-v6relay-license

  • dropped-v6relay-inactive-vlan

  • dropped-v6relay-era-start-failed

  • dropped-v6relay-client-lookup

  • dropped-v6relay-lease-time-violation

  • dropped-v6relay-leasequery-repl-no-client-data

  • dropped-v6relay-leasequery-repl-no-interfaceid

  • dropped-v6relay-leasequery-repl-with-client-link

  • dropped-v6relay-leasequery-repl-no-relay-data

  • dropped-v6relay-leasequery-repl-with-hop-cnt

  • dropped-v6relay-leasequery-repl-with-error-code

  • dropped-v6relay-leasequery-repl-with-query-term

  • dropped-v6relay-older-leasequery-reply

  • dropped-v6relay-abort-leasequery-reply-proc

  • dropped-v6relay-during-leasequery-reply

  • dropped-v6relay-relay-source-no-lpbk-interface

  • msg-recv-v6relay-decline

  • msg-recv-v6relay-solicit

  • msg-recv-v6relay-information-request

  • msg-recv-v6relay-release

  • msg-recv-v6relay-request

  • msg-recv-v6relay-confirm

  • msg-recv-v6relay-renew

  • msg-recv-v6relay-rebind

  • msg-recv-v6relay-relay-forw

  • msg-recv-v6relay-leasequery-repl

  • msg-recv-v6relay-leasequery-data

  • msg-recv-v6relay-leasequery-done

  • msg-recv-v6relay-advertise

  • msg-recv-v6relay-reply

  • msg-recv-v6relay-reconfigure

  • msg-recv-v6relay-relay-repl

  • msg-recv-v6relay-leasequery

  • msg-sent-v6relay-reply

  • msg-sent-v6relay-reconfigure

  • msg-sent-v6relay-relay-repl

  • msg-sent-v6relay-leasequery

  • msg-sent-v6relay-decline

  • msg-sent-v6relay-solicit

  • msg-sent-v6relay-information-request

  • msg-sent-v6relay-release

  • msg-sent-v6relay-request

  • msg-sent-v6relay-confirm

  • msg-sent-v6relay-renew

  • msg-sent-v6relay-rebind

  • msg-sent-v6relay-relay-forw

  • msg-sent-v6relay-leasequery-repl

  • msg-sent-v6relay-leasequery-data

  • msg-sent-v6relay-leasequery-done

  • v6relay-fwd-total

  • v6relay-fwd-request

  • v6relay-fwd-reply

/junos/system/subscriber-management/client-protocols/l2tp/summary/

Sensor for L2TP telemetry information.

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

  • l2tp-stats-total-tunnels

  • l2tp-stats-total-sessions

  • l2tp-stats-control-rx-packets

  • l2tp-stats-control-rx-bytes

  • l2tp-stats-control-tx-packets

  • l2tp-stats-control-tx-bytes

  • l2tp-era-type-icrq-inflight-count

  • l2tp-era-type-icrq-reported-successes

  • l2tp-era-type-icrq-reported-failures

  • l2tp-era-type-sccrq-inflight-count

  • l2tp-era-type-sccrq-reported-successes

  • l2tp-era-type-sccrq-reported-failures

/junos/system/subscriber-management/client-protocols/ppp/statistics/

Sensors for PPP telemetry information.

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

  • ppp-stats-total-subscriber-sessions

  • ppp-stats-sessions-disable-phase

  • ppp-stats-sessions-establish-phase

  • ppp-stats-sessions-network-phase

  • ppp-stats-sessions-authenticate-phase

/junos/system/subscriber-management/client-protocols/pppoe/statistics/

Sensors for PPPoE counts.

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

  • padi-packets-sent

  • padi-packets-received

  • pado-packets-sent

  • pado-packets-received

  • padr-packets-sent

  • padr-packets-received

  • pads-packets-sent

  • pads-packets-received

  • padt-packets-sent

  • padt-packets-received

  • service-error-sent

  • service-error-received

  • ac-error-sent

  • ac-error-received

  • generic-error-sent

  • generic-error-received

  • malformed-packets-received

  • unknown-packets-received

  • era-inflight-count

  • era-reported-successes

  • era-reported-failures

  

/junos/system/subscriber_management/dynamic-interfaces/interface-sets/meta-data/interface-set[container-id='container-id-value']/

Sensor for subscriber interface-set information.

This sensor is supported on MX Series routers starting with Junos OS Release 18.4R1.

ON-CHANGE streaming is supported.

The following end paths are supported:

  • cos-egress-tcp-name-The egress traffic control profile associated with this interface-set.

  • cos-egress-tcp-remainder-name-The egress remainder traffic control profile associated with this interface-set.

  • interface-set-name-The name of the interface-set as supplied by AAA or as constructed by the topology relationship (ACI string or interface stacking).

  • interface-set-type-The type of interface-set (determines structure of interface-set-name).

  • device-name-The name of the underlying device or port (e.g. ge-1/0/0 or ae1). This leaf is empty if the interface-set-type is not a physical interface-set type.

  • stag-The outer VLAN tag. The value is 0 if interface-set-type is not a VLAN type.

  • ctag-The inner VLAN tag. The value is 0 if interface-set-type is not a VLAN type.

/junos/system/subscriber_management/dynamic-interfaces/interface-sets/meta-data/interface[sid-id='sid-value']/

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.

/junos/system/subscriber_management/dynamic-interfaces/interface-sets/meta-data/interface[sid-id='sid-value']/

Sensor for actual accounting statistics for dynamic subscriber interfaces.

ON-CHANGE streaming is supported.

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.

/junos/system/subscriber_management/dynamic-interfaces/interfaces/queue-statistics/interface[sid-id='sid-value']/fpcs/fpc[slot=’slot-value’]/queues/queue/[queue-no=’queue-no-value’]/

Sensor for queue statistics for dynamic interfaces.

ON-CHANGE streaming is supported.

The following end paths are supported:

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

  • transmitted-bytes-Total bytes enqueued for this queue.

  • dropped-packets-Total packets dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

  • dropped-bytes-Total bytes dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

/junos/system/subscriber_management/dynamic-interfaces/interface-sets/queue-statistics/interface-set[container-id='container-id-value']/fpcs/fpc[slot=’slot-value’]/queues/queue/[queue-no=’queue-no-value’]/

Sensor for queue statistics for dynamic interface-sets.

ON-CHANGE streaming is supported.

The following end paths are supported:

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

  • transmitted-bytes-Total bytes enqueued for this queue.

  • dropped-packets-Total packets dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

  • dropped-bytes-Total bytes dropped (because of RED, rate-limited, tail-drop, etc.) for the queue.

/junos/system/subscriber-management/infra/resource-monitor/chassis

Sensor for chassis resource statistics.

The crossing of chassis thresholds maintained by the resource monitor can be incremented. For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

Unless limits are configured using configured-subscriber-limit, configured and current limit counts will not be visible.

The following end paths are supported for chassis threshold crossing statistics:

  • subscriber-limit-exceeded

  • subscriber-limit-nominal

  • configured-subscriber-limit

  • current-subscriber-count

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc/statistics/

Sensor for FPC resource statistics, including statistics for throttled sessions due to exceeding the line card load threshold (as measured by the routing engine to FPC round trip delay).

The resource path can be refined to select a specific slot by adding a slot number filter to the resource path:

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc[slot=’ slot number’]/statistics/

Using the slot number filter, the crossing of FPC thresholds maintained by the resource monitor can be incremented. For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

Unless limits are configured using configured-subscriber-limit, configured and current limit counts will not be visible.

The following end paths are supported for FPC threshold crossing statistics:

  • mem-heap-exceeded

  • mem-heap-nominal

  • subscriber-limit-exceeded

  • subscriber-limit-nominal

  • configured-subscriber-limit

  • current-subscriber-count

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

  • heap-memory-used

  • client-session-denied-count

  • service-session-denied-count

  • rtt-throttled-sub-count-client

  • rtt-throttled-sub-count-client

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc/statistics/pfes/pfe

Sensor for FPC resource statistics at the Packet Forwarding Engine level. Periodically tracks line card statistics and Packet Forwarding Engine statistics.

The resource path can be refined to select a specific Packet Forwarding Engine by adding a Packet forwarding Engine filter to the resource path:

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc/statistics/pfes/pfe[pfe-no=’ pfe number’]/

The resource path can be refined to select a specific Packet Forwarding Engine by adding a slot number filter to the resource path:

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc [slot=’ slot number’]/statistics/pfes/pfe[pfe-no=’ pfe number’]/

Using the slot number filter, the crossing of packet forwarding engine thresholds maintained by the resource monitor can be incremented. For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

The following end paths are supported for packet forwarding threshold crossing statistics:

  • mem-ifl-exceeded

  • mem-ifl-nominal

  • mem-expansion-exceeded

  • mem-expansion-nominal

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

  • pfe-no

  • filter-memory-used

  • ifl-memory-used

  • expansion-memory-used

  • nh-memory

/junos/system/subscriber-management/infra/resource-monitor/rsmon-infra/fpcs/fpc[slot=’ slot number’]/

Sensor for FPC resource statistics.

Using the slot number filter, the crossing of FPC thresholds maintained by the resource monitor can be incremented. For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

The following end paths are supported for FPC threshold crossing statistics:

  • delay-round-trip-exceeded

  • delay-round-trip-nominal

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc [slot=’ slot number’]/statistics/pfes/pfe[pfe-no=’ pfe number’]/sched-blocks/sched-block[sblock-no=’ schedBlockNumber’]/

Sensor for counts of CoS utilization threshold crossing events above (exceeded) and below (nominal).

For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

The following end paths are supported for CoS utilization threshold crossing statistics:

  • cos-utilization-exceeded

  • cos-utilization-nominal

The following end paths are supported for statistical data:

  • queues-max

  • queues-allocated

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc [slot=’ slot number’]/pics/pic[pic-no=’ pic number’]/

Sensor for PIC threshold crossing.

For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

Unless limits are configured using configured-subscriber-limit, configured and current limit counts will not be visible.

The following end paths are supported for PIC threshold crossing statistics:

  • subscriber-limit-exceeded

  • subscriber-limit-nominal

  • configured-subscriber-limit

  • current-subscriber-count

/junos/system/subscriber-management/infra/resource-monitor/fpcs/fpc [slot=’ slot number’]/pics/pic[pic-no=’ pic number’]/ports/port[port-no=’ port number’]/

Sensor for port threshold crossing.

For each threshold, a count is maintained of rising and falling threshold crossings. As the consumed resource exceeds the threshold, the threshold exceeded count is incremented. As the consumed resource drops below the threshold, the threshold nominal count is incremented.

Unless limits are configured using configured-subscriber-limit, configured and current limit counts will not be visible.

The following end paths are supported for port utilization threshold crossing statistics:

  • subscriber-limit-exceeded

  • subscriber-limit-nominal

  • configured-subscriber-limit

  • current-subscriber-count

/junos/system/subscriber-management/infra/network/dhcp/

Sensor for network stack DHCP. Periodically tracks packets processed by the BBE network stack to and from the DHCP application.

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

  • rx-packet-cnt

  • era-drops

  • rx-no-connection

  • rx-malformed-cnt

  • rx-no-if-cnt

  • rx-ifl-invalid

  • rx-send-failed

  • tx-packet-cnt

  • packets-transmitted

  • tx-malformed-cnt

  • tx-null-pkt

  • tx-no-if-cnt

  • tx-no-iff-cnt

  • tx-no-rtt-cnt

  • tx-arp-failed

  • tx_arp_failed

  • tx-if-invalid

  • tx-send-failed

  • rx-while-not-connected

/junos/system/subscriber-management/infra/network/dvlan/

Sensor for network stack dynamic VLAN. Periodically maintains a count of the number of packets received that triggered dynamic VLAN interface creations.

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

  • rx-packet-cnt

/junos/system/subscriber-management/infra/network/io/

Sensor for network stack IO. Periodcally provides basic network stack input and output and tracks network stack packet statistics.

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

  • l2-rx-packets-cnt

  • l2-rx-packets-failed

  • l2-rx-malformed-cnt

  • l2-rx-ifd-invalid

  • l2-rx-ifl-invalid

  • l2-rx-no-iff-cnt

  • l2-rx-if-create-failed

  • l2-bbe-io-rcv-l3-unknown-address-family

  • l2-rx-unsupported-inet-protocol

  • l2-rx-unsupported-inet6-protocol

  • l2-rx-unsupported-udp-protocol

  • l2-rx-unsupported-punt-af

  • l2-rx-v4-data-path-punt-pkt

  • l2-rx-v4-data-path-punt-pkt-drop

  • l2-rx-v6-data-path-punt-pkt

  • l2-rx-v6-data-path-punt-pkt-drop

  • l2-tx-packets-cnt

  • l2-tx-malformed-cnt

  • l2-tx-no-ifd-cnt

  • l2-tx-ifl-invalid

  • l2-bbe-io-send-tx-failed

  • l2-bbe-io-send-tx-failed-partial

  • l2-tx-v4-out-error-local-intf

  • l2-tx-v6-out-error-local-intf

  • l3-rx-packet-cnt

  • l3-rx-unsupported-protocol

  • l3-tx-packet-cnt

  • l3-tx-send-failed

  • l3-tx-v4-kernel-forward

  • l3-tx-v4-kernel-forward-drops

  • l3-tx-v6-kernel-forward

  • l3-tx-v6-kernel-forward-drops

/junos/system/subscriber-management/infra/network/dvlan/

Sensor for network stack dynamic VLAN. Periodically maintains a count of the number of packets received that triggered dynamic VLAN interface creations.

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

  • rx-packet-cnt

/junos/system/subscriber-management/infra/network/l2tp/

Sensor network stack L2TP. Periodically tracks L2TP packets processed by the BBE network stack to and from the L2TP application.

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

  • rx-cnt

  • rx-pkt-cnt

  • ppp-rx-pkt-cnt

  • tx-pkt-cnt

  • ppp-rx-lcp-conf-req-count

  • ppp-rx-lcp-conf-ack-count

  • ppp-rx-lcp-conf-nack-count

  • ppp-rx-lcp-term-req-count

  • ppp-rx-lcp-term-ack-count

  • ppp-rx-lcp-echo-req-count

  • ppp-rx-lcp-echo-resp-count

  • ppp-rx-pap-req-count

  • ppp-rx-pap-ack-count

  • ppp-rx-pap-nack-count

  • ppp-rx-chap-challenge-count

  • ppp-rx-chap-resp-count

  • ppp-rx-chap-success-count

  • ppp-rx-chap-fail-count

  • ppp-rx-ipcp-conf-req-count

  • ppp-rx-ipcp-conf-ack-count

  • ppp-rx-ipcp-conf-nack-count

  • rx-malformed-cnt

  • ppp-rx-unknown-protocol

  • rx-msg-cnt

  • rx-msg-processd-cnt

  • rx-msg-err

  • rx-invalid-msg-cnt

  • tx-cnt

  • ppp-tx-lcp-conf-req-count

  • ppp-tx-lcp-conf-ack-count

  • ppp-tx-lcp-conf-nack-count

  • ppp-tx-lcp-echo-req-count

  • ppp-tx-lcp-echo-resp-count

  • ppp-tx-lcp-term-req-count

  • ppp-tx-lcp-term-ack-count

  • ppp-tx-pap-req-count

  • ppp-tx-pap-ack-count

  • ppp-tx-pap-nack-count

  • ppp-tx-chap-challenge-count

  • ppp-tx-chap-resp-count

  • ppp-tx-chap-success-count

  • ppp-tx-chap-fail-count

  • ppp-tx-ipcp-conf-req-count

  • ppp-tx-ipcp-conf-ack-count

  • ppp-tx-ipcp-conf-nack-count

  • ppp-tx-unknown-protocol

  • tx-pkt-send-failed

  • tx-pkt-err

  • tx-msg-cnt

  • tx-msg-err

/junos/system/subscriber-management/infra/network/ppp/

Sensor network stack PPP. Periodically tracks PPP packets processed by the BBE network stack to and from the PPP application.

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

  • rx-network-pkt-cnt

  • rx-plugin-pkt-cnt

  • rx-lcp-conf-req-cnt

  • rx-lcp-conf-ack-cnt

  • rx-lcp-conf-nack-cnt

  • rx-lcp-conf-rej-cnt

  • rx-lcp-term-req-cnt

  • rx-lcp-term-ack-cnt

  • rx-lcp-code-rej-cnt

  • rx-lcp-protocol-rej-cnt

  • rx-lcp-echo-req-cnt

  • rx-lcp-echo-reply-cnt

  • rx-pap-req-cnt

  • rx-pap-ack-cnt

  • rx-pap-nack-cnt

  • rx-chap-challenge-cnt

  • rx-chap-resp-cnt

  • rx-chap-success-cnt

  • rx-chap-failure-cnt

  • rx-ipcp-req-cnt

  • rx-ipcp-ack-cnt

  • rx-ipcp-nack-cnt

  • rx-ipv6cp-req-cnt

  • rx-ipv6cp-ack-cnt

  • rx-ipv6cp-nack-cnt

  • rx-malformed-cnt

  • rx-no-if-cnt

  • rx-unsupported

  • tx-cnt

  • tx-lcp-conf-req-cnt

  • tx-lcp-conf-ack-cnt

  • tx-lcp-conf-nack-cnt

  • tx-lcp-echo-req-cnt

  • tx-lcp-echo-reply-cnt

  • tx-lcp-term-req-cnt

  • tx-lcp-term-ack-cnt

  • tx-pap-req-cnt

  • tx-pap-ack-cnt

  • tx-pap-nack-cnt

  • tx-chap-challenge-cnt

  • tx-chap-resp-cnt

  • tx-chap-success-cnt

  • tx-chap-failure-cnt

  • tx-ipcp-req-cnt

  • tx-ipcp-ack-cnt

  • tx-ipcp-nack-cnt

  • tx-ipv6cp-req-cnt

  • tx-ipv6cp-ack-cnt

  • tx-ipv6cp-nack-cnt

  • tx-unknown-pkt-cnt

  • tx-send-failed

  • tx-malformed-cnt

/junos/system/subscriber-management/infra/network/pppoe/

Sensor for network stack PPPoE statistics. PPPoE packets processed by the BBE network stack to and from the PPPoE application are tracked.

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

  • rx-cnt

  • rx-padi-cnt

  • rx-padr-cnt

  • rx-ppp-cnt

  • rx-malformed-cnt

  • rx-no-if-cnt

  • rx-unsupported

  • rx-padi-era-discards

  • tx-cnt

  • tx-send-failed

/junos/system/subscriber-management/infra/sdb/statistics/client-type/

Sensor for session database resources session counts by client type.

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

  • dhcp-client-count

  • vlan-client-count

  • ppp-client-count

  • pppoe-client-count

  • l2tp-client-count

  • static-client-count

  • vpls-pw-client-count

  • mlppp-client-count

  • essm-client-count

  • total-client-count

/junos/system/subscriber-management/infra/sdb/statistics/state/

Sensor for session database resources tracking session counts by state.

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

  • init-state-count

  • configured-state-count

  • active-state-count

  • terminating-state-count

  • terminated-state-count

  • total-state-count

Release History Table
Release
Description
Starting with Junos OS Release 19.1R1, MX Series routers operating with MS-MIC and MS-MPC, QFX10002 switches, and PTX10002 routers are also supported.
Starting with Junos OS Release 19.1R1, PTX3000 routers and PTX5000 routers with FPC2 are also supported.
Starting with Junos OS Release 18.4R1, MX480, MX960, MX2010, MX2020, MX2008 and MX-ELM routers are also supported.
Starting with Junos OS Release 18.3R1, ON_CHANGE streaming of LLDP telemetry sensor information is supported through gRPC for MX Series and PTX Series routers.
Starting with Junos OS Release 18.3R1, QFX5120-AY and EX4650 switches are also supported.
Starting with Junos OS Release 18.4R1, EX4600 switches are also supported.
Starting with Junos OS Release 18.2R1, PTX10002 routers are also supported.
Starting with Junos OS Release 18.1R1, QFX5210-64C switches and QFX5100 switches are also supported.
Starting with Junos OS Release 18.1R1, ON_CHANGE streaming of ARP, ND, and IP sensor information associated with interfaces is supported through gRPC for MX Series routers and PTX Series routers.
Starting with Junos OS Release 17.4R1, PTX10016 routers and virtual MX Series (vMX) routers are also supported.
Starting with Junos OS Release 17.3R1, QFX5110 switches, EX4600, EX4600-VC, and EX9200 switches and the Routing and Control Board (RCB) on PTX3000 routers are also supported.
Starting with Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensors are supported.
In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’] /server/statistics/ the only value supported for routing-instance-name is default.
In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-ancpinstance[ri-name=’ routing-instance-name’] /server/statistics/ the only value supported for routing-instance-name is default.
In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics/ the only value supported for the value routing-instance-name is default.
In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics the only value supported for routing-instance-name is default.
In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics the only value supported for routing-instance-name is default.
Starting with JunosOS Release 17.2R1, QFX10002, QFX10008, and QFX10016 switches, QFX5200 switches, and PTX1000 and PTX10008 routers are also supported.
Starting with Junos OS Release 16.1R3, the Junos Telemetry Interface supports gRPC remote procedure calls (gRPC) to provision sensors and to subscribe to and receive telemetry data on MX Series routers and PTX3000 and PTX5000 routers.