Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    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 Junos OS Release 17.2R1, QFX10000 switches, QFX5200 switches, and PTX1000 routers are also supported.

    Starting with Junos OS Release 17.3R1, QFX5110 switches, EX4600 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.

    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.

    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

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

    mpls/lsps/constrained-path/tunnels/tunnel/

    Sensor for LSP statistics. Only ingress LSPs are supported. 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.

    You can also specify an LSP name and source IP address at the end of the path: [name='lsp-name', source=ip-address]

    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.

    /mpls/lsps/

    /mpls/signaling-protocols/

    Sensor for LSP events and properties.

    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.

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

    The following paths are also supported:

    • /mpls/lsps/constrained-path/tunnels/tunnel/
      p2p-tunnel-attributes/p2p-primary-paths/lsp-instances/state/notify-status
    • /mpls/lsps/constrained-path/tunnels/tunnel/
      p2p-tunnel-attributes/p2p-primary-paths/state/notify-status
    • /mpls/signaling-protocols/rsvp-te/
      sessions/session/state/notify-status
    • /mpls/lsps/constrained-path/tunnels/tunnel/
      p2p-tunnel-attributes/p2p-primary-paths/lsp-instances/state/bandwidth
    • /mpls/lsps/constrained-path/tunnels/tunnel/
      p2p-tunnel-attributes/p2p-primary-paths/lsp-instances/state/metric
    • /mpls/lsps/constrained-path/tunnels/tunnel/
      p2p-tunnel-attributes/p2p-primary-paths/state/explicit-path-name
    • /mpls/lsps/constrained-path/tunnels/tunnel/
      p2p-tunnel-attributes/p2p-primary-paths/lsp-instances/state/max-avg-bandwidth

    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.

    /junos/npu-memory/

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

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

    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.

    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/cpu/memory/

    /components/component [name="FPC<fpc-id>:CPU0"]/properties/property/

    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.

    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

    /bgp/neighbors/neighbor/

    /bgp/peer-groups/peer-group/

    /bgp/global/

    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:
    /network-instances/network-instance[name_'instance-name']/
    protocols/protocol/

    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 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, 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 /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 /bgp/global/:

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

    You can also include the following at the end path to /bgp/peer-groups/peer-group/:

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

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

    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/

    /junos/firewall/firewall-stats/

    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.

    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 paths are also 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.

    The following paths are also supported:

    • /interfaces/interface[name='interface-name']/parent_ae_name
    • /interfaces/interface[name='interface-name']/oper-status
    • /interfaces/interface[name='interface-name']/carrier-transitions
    • /interfaces/interface[name='interface-name']/last-change
    • /interfaces/interface[name='interface-name']/high-speed
    • /interfaces/interface[name='interface-name']/counters/out-octets
    • /interfaces/interface[name='interface-name']/counters/out-unicast-pkts
    • /interfaces/interface[name='interface-name']/counters/out-multicast-pkts
    • /interfaces/interface[name='interface-name']/counters/out-broadcast-pkts
    • /interfaces/interface[name=''interface-name']/counters/out-errors
    • /interfaces/interface[name='interface-name']/counters/in-octets
    • /interfaces/interface[name='interface-name']/counters/in-unicast-pkts
    • /interfaces/interface[name='interface-name']/counters/in-multicast-pkts
    • /interfaces/interface[name='interface-name']/
    • /interfaces/interface[name='interface-name']/counters/in-broadcast-pkts
    • /interfaces/interface[name='interface-name']/counters/in-errors
    • /interfaces/interface[name='interface-name']/in-pause-pkts
    • /interfaces/interface[name='interface-name']/out-pause-pkts
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/ pkts
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/bytes
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/tail-drop-pkts
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/ rl-drop-pkts
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/ rl-drop-bytes
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/avg-buffer-occupancy
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/cur-buffer-occupancy
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/peak-buffer-occupancy
    • /interfaces/interface[name='interface-name']/in-queue [queue-number=quene_number]/allocated-buffer-size
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/pkts
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/bytes
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/tail-drop-pkts
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/rl-drop-pkts
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/ rl-drop-bytes
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/red-drop-pkts
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/red-drop-bytes
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/avg-buffer-occupancy
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/cur-buffer-occupancy
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/ peak-buffer-occupancy
    • /interfaces/interface[name='interface-name']/out-queue [queue-number=quene_number]/allocated-buffer-size

    /interfaces/interface/subinterfaces/

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

    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.

    The following paths are also supported:

    • /interfaces/interface/subinterfaces/subinterface/name
    • /interfaces/interface/subinterfaces/subinterface/ifindex
    • /interfaces/interface/subinterfaces/subinterface/snmp_index
    • /interfaces/interface/subinterfaces/subinterface/admin_status
    • /interfaces/interface/subinterfaces/subinterface/oper_status
    • /interfaces/interface/subinterfaces/subinterface/last_change
    • /interfaces/interface/subinterfaces/subinterface/high_speed
    • /interfaces/interface/subinterfaces/subinterface/description
    • /interfaces/interface/subinterfaces/subinterface/enabled
    • /interfaces/interface/subinterfaces/subinterface/subunit
    • /interfaces/interface/subinterfaces/subinterface/oob_states/in_octets
    • /interfaces/interface/subinterfaces/subinterface/oob_states/in_unicast_pkts
    • /interfaces/interface/subinterfaces/subinterface/oob_states/in_broadcast_pkts
    • /interfaces/interface/subinterfaces/subinterface/oob_states/in_multicast_pkts
    • /interfaces/interface/subinterfaces/subinterface/oob_states/in_discards
    • /interfaces/interface/subinterfaces/subinterface/oob_states/in_errors
    • /interfaces/interface/subinterfaces/subinterface/oob_states/in_unknown_protos
    • /interface/subinterfaces/subinterface/oob_states/out_octets
    • /interfaces/interface/subinterfaces/subinterface/oob_states/out_unicast_pkts
    • /interfaces/interface/subinterfaces/subinterface/oob_states/out_broadcast_pkts
    • /interfaces/interface/subinterfaces/subinterface/oob_states/out_multicast_pkts
    • /interfaces/interface/subinterfaces/subinterface/oob_states/out_discards
    • /interfaces/interface/subinterfaces/subinterface/oob_states/out_errors
    • /interfaces/interface/subinterfaces/subinterface/oob_states/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.

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

    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/component/

    /chassis-inventory/chassis-modules/chassis-module/

    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.

    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.

    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.

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

    • state/
    • state/enabled
    • state/hello-timer
    • state/system-name
    • state/system-description
    • state/chassis-id
    • state/loc-port-id-type
    • interfaces/interface[name='interface-name']/state/
    • interfaces/interface[name='interface-name']/state/counters/
    • interfaces/interface[name='interface-name']/neighbors/

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

    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.

    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.

    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

    /junos/system/subscriber-management/

    aaa/authentication-statistics/

    Three sensors that track authentication, authorization, and accounting (AAA) authentication, pre-authentication, and re-authentication statistics.

    You can also add the following to the end path for /junos/system/subscriber-management/

    aaa/authentication-statistics/:

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

    You can also add the following to the end path for /junos/system/subscriber-management/aaa/dynamic-request-statistics/:

    • dynamic-req-received
    • dynamic-req-success
    • dynamic-req-error
    • dynamic-req-silently-drop

    /junos/system/subscriber-management/client-protocols/dhcp/v4/

    Sensor for DHCPv4 telemetry.

    The following end paths are also supported:

    • 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

    /junos/system/subscriber-management/client-protocols/dhcp/v4/

    routing-instances/routing-instance[ri-name=’routing-instance-name’]/server/statistics/

    Sensor for DHCPv4 telemetry for server statistics for a specific routing-instance.

    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-iinstance-name is default.

    The following end paths are also supported:

    • 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[ri-name=’routing-instance-name’]/relay/statistics/

    Sensor for DHCPv4 telemetry for relay statistics for a specific routing-instance.

    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-iinstance-name is default.

    The following end paths are also supported:

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

    routing-instances/routing-instance[ri-name=’routing-instance-name’]/server/statistics/

    Sensor for server statistics for a specific DHCPv6 routing-instance.

    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:

    • 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[ri-name=’routing-instance-name’]/relay/statistics/

    Sensor for relay statistics for a specific DHCPv6 routing-instance.

    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:

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

    You can also add the following to the end path for /junos/system/subscriber-management/client-protocols/l2tp/summary/:

    • 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

    /junos/system/subscriber-management/client-protocols/ppp/statistics/

    Sensors for PPP telemetry information.

    You can also add the following to the end path for /junos/system/subscriber-management/client-protocols/ppp/statistics/:

    • 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 from /junos/system/subscriber-management/client-protocols/pppoe/statistics/:

    • padi-packets-sent
    • padi-packets-received
    • pado-packets-sent
    • pado-packets-received
    • padr-packets-sent
    • padr-packets-received
    • pads-packets-sent
    • pads-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

    /junos/system/subscriber-management/infra/resource-monitor/

    fpcs/fpc[slot=’ slot number’]/statistics/

    Sensor for FPC resource statistics.

    You can also add the following to the end path for junos/system/subscriber-management/infra/resource-monitor/

    /fpcs/fpc[slot=’slotNum’]/statistics/:

    • heap-memory-used
    • client-session-denied-count
    • service-session-denied-count

    /junos/system/subscriber-management/infra/resource-monitor/

    fpcs/fpc/statistics/pfes/pfe[pfe-no=’pfe number’]/

    Sensor for FPC resource statistics at the packet forwarding engine level. Periodically tracks line card statistics and packet forwarding engine statistics..

    You can also add the following to the end path for /junos/system/subscriber-management/infra/resource-monitor/

    fpcs/fpc/statistics/pfes/pfe[pfe-no=’pfeNum’]/:

    • pfe-no
    • filter-memory-used
    • ifl-memory-used
    • expansion-memory-used
    • nh-memory

    /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 from /junos/system/subscriber-management/

    infra/network/dhcp/:

    • 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 path is also supported from /junos/system/subscriber-management/

    infra/network/dvlan/:

    • 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 from /junos/system/subscriber-management/

    infra/network/io/:

    • 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 path is also supported from /junos/system/subscriber-management/

    infra/network/dvlan/:

    • 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 from /junos/system/subscriber-management/

    infra/network/l2tp/:

    • 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 from /junos/system/subscriber-management/infra/network/ppp/:

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

    This is a periodic sensor.

    The following end paths are also supported from /junos/system/subscriber-management/

    infra/network/pppoe/:

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

    You can also add the following to the end path for /junos/system/subscriber-management/

    infra/sdb/statistics/client-type/:

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

    You can also add the following to the end path for /junos/system/subscriber-management/

    infra/sdb/statistics/state/:

    • 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 17.3R1, QFX5110 switches, EX4600 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-iinstance-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-iinstance-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 Junos OS Release 17.2R1, QFX10000 switches, QFX5200 switches, and PTX1000 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.

    Modified: 2017-10-03