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

    Related Documentation

     

    sensor (Junos Telemetry Interface)

    Syntax

    sensor sensor-name {export-name export-profile-name;resource resource-string;<resource-filter regular expression>;server-name [ streaming-server-names ];}

    Hierarchy Level

    [edit services analytics]

    Release Information

    Statement introduced in Junos OS Release 15.1F3.

    Support for MPC7E, MPC8E, and MPC9E on MX Series routers added in Junos OS Release 15.1F5.

    Support for FPC1 and FPC2 on PTX Series routers added in Junos OS Release 16.1R3.

    Statement introduced in Junos OS Release 17.2R1 for QFX10000 switches and PTX1000 routers.

    Statement introduced in Junos OS Release 17.3R1 for the Routing and Control Board (RCB) on PTX3000 routers, EX9200 switches, and MX150 routers.

    Description

    Configure a Junos Telemetry Interface sensor, which defines the parameters of a system resource to monitor and stream data. You can configure more than one sensor to stream data for the same system resource. For example, you might want to configure different parameters for exporting data for the same system resource. Additionally, you can use regular expressions to filter the data collected. Examples include filters for logical and physical interfaces and LSP messages. To apply different filters to the same system resource, you configure multiple sensors. For example, you can configure multiple logical interface sensors and apply a different interface filter to each one.

    Options

    Each sensor configuration requires you to specify the following: sensor name, an export profile name, a resource identifier string that enables monitoring and streaming of data for the specified system resource, and a server name to collect data. A regular expression to filter data for the specified resource is optional.

    sensor-nameSpecify a name that defines the sensor configuration. For example, for a sensor configuration that monitors all LSP events, you might choose the name lsp-mon-global. For a sensor configuration that monitors events only for an LSP named A2B, you might choose the name lsp-mon-A2B.
    export-name export-profile-nameSpecify the name of an export profile that you configured at the [edit services analytics export-profile name] hierarchy level to associate with the sensor. This export profile defines the parameters for exporting telemetry data, such as a format for exported data and the rate at which data is generated for export.

    Note: You can apply only one export profile to each sensor configuration.

    The only supported transport protocol when you configure a sensor through the CLI is UDP.

    resource resource-stringEnable the system resource to monitor and stream data. Each string corresponds to a specific system resource. The format is a file path and must be entered exactly. You can associate only one resource-string with a sensor-name. Configure a separate sensor for each system resource you want to monitor. The resource string to enable LSP monitoring can be modified to specify a specific LSP.

    Note: You can configure more than one sensor to monitor the same system resource. Configuring different sensors for the same system resource allows you configure different parameters for monitoring that resource.

    Table 1 lists each supported resource-identifier-string, a description of the system resource monitored, and additional configuration information.

    Table 1: resource statement Options

    resource string

    Description

    Release Information

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

    Packet Forwarding Engine sensor for LSP statistics. Only ingress LSPs are supported. Bypass LSPs, including those configured as ingress LSPs, are not supported. On MX Series routers only, bidirectional LSPs for ultimate-hop popping (UHP) are also supported.

    Note: You can modify /junos/services/label-switched-path/usage/ to specify a specific LSP. Add __instance__/lsp-name to the end of the resource string identifier. For example, to monitor and stream data for LSP statistics for an LSP named mirror-to-murano-1, enter the following: /junos/services/label-switched-path/usage/
    __instance__/mirror-to-murano-1
    . If you do not specify a specific LSP name, the system resource monitors and streams data for all LSPs.

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

    Junos OS Release 15.1F6 and later.

    Junos OS Release 17.2R1 and later on QFX10000 switches and PTX1000 routers.

    Junos OS Release 17.3 and later on EX9200 switches.

    /junos/system/linecard/cpu/memory/

    Packet Forwarding Engine sensor for CPU memory.

    Junos OS Release 16.1R3 and later.

    Junos OS Release 17.2R1 and later on QFX10000 switches and PTX1000 routers.

    Junos OS Release 17.3R1 and later on EX9200 switches.

    /junos/system/linecard/firewall/

    Packet Forwarding Engine sensor for firewall filter counters and policer counters. Each line card reports counters separately.

    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 filer is attached is down.

    Junos OS Release 15.1F5 and later.

    Junos OS Release 17.2R1 and later on QFX10000 switches.

    Junos OS Release 17.3R1 and later on PTX1000 routers and EX9200 switches.

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

    Junos OS Release 15.1F3 and later on PTX Series routers only. Support introduced for MX Series routers in Junos OS Release 15.1F5.

    Junos OS Release 17.2R1 and later on QFX10000 switches and PTX1000 routers.

    Junos OS Release 17.3R1 and later on EX9200 switches and MX150 routers.

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

    Packet Forwarding Engine sensor for logical interface traffic.

    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.

    Junos OS Release 15.1F5 and later.

    Junos OS Release 17.2R1 and later on QFX10000 switches.

    Junos OS Release 17.3R1 and later on EX9200 switches

    /junos/system/linecard/npu/memory/

    Packet Forwarding Engine sensor for network processing unit (NPU) memory.

    Junos OS Release 16.1R3 and later.

    Junos OS Release 17.2R1 and later on QFX10000 switches.

    Junos OS Release 17.3R1 and later on EX9200 switches.

    /junos/system/linecard/npu/utilization/

    Packet Forwarding Engine sensor for NPU memory utilization and total memory available for each memory type.

    Junos OS Release 16.1R3 and later.

    Junos OS Release 17.2R1 and later on QFX10000 switches.

    Junos OS Release 17.3R1 and alter on EX9200 switches.

    /junos/npu-memory/

    Sensor that exports both NPU memory statistics from the Packet Forwarding Engine and flow-label statistics from the Routing Engine.

    To export only flow-label statistics, include the junos/npu-memory/flabel-memory/ resource string.

    To export only Packet Forwarding Engine NPU memory statistics, include /junos/system/linecard/npu/memory/ resource string.

    Junos OS Release 16.1R3 and later on PTX Series routers only.

    Note: Junos OS Release 17.2R1 and later on PTX1000 routers.

    /junos/system/linecard/services/inline-jflow/

    Packet Forwarding Engine sensor for performance metrics of the inline flow sampling process, such as the number of active flows and the number of exported flows.

    Junos OS Release 16.1R3 and later on MX series and PTX series routers only.

    Junos OS Release and later on EX9200 switches, PTX1000 routers, and MX150 routers.

    /junos/system/linecard/optics/

    Packet Forwarding Engine sensor for various optical performance metrics, such as transmit and receive power levels.

    Junos OS Release 16.1R3 and later.

    Junos OS Release and later 17.2R1 on QFX10000 switches.

    Junos OS Release 17.3R1 and later on EX9200 switches and PTX1000 routers.

    /junos/system/linecard/qmon/

    Sensor for queue depth statistics for ingress and egress queue traffic. Statistics are exported directly from the line card.

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

    Junos OS Release 17.1R1 and later on MX Series routers on MPC7E, MPC8E, and MPC9E only.

    Junos OS 17.3R1 and later on EX9200 switches.

    /junos/system/linecard/fabric/

    Sensor for fabric statistics

    The following types of statistics can be exported:

    • Fabric statistics for Packet Forwarding Engine pairs (resource-filter option is not supported)
    • FPC fabric statistics
    • Control Board and Switch Fabric Board fabric statistics.

    Junos OS Release 17.2R1 and later on MX Series routers only.

    Junos OS Release 17.3R1 and later on EX9200 switches.

    resource-filter regular-expression(Optional) Specify a regular expression to filter data for a specific resource. For example, you can filter for a specific set of logical or physical interfaces, firewall filters, or LSP messages. When you configure a system resource to monitor and stream data globally—that is, systemwide—you do not need to include a regular expression.

    Examples of regular expressions to filter data exported through sensor configuration:

    • Logical interface statistics sensor—et-2/0/7:1*
    • LSP events sensor—lsp-from-A-to-B*
    • Firewall filter counters sensor—f_testl*
    server-name [ streaming- server-names ] Specify one or more servers to transport data for collection. Include at least one server-name configured at the [edit services analytics streaming-server server-name] hierarchy level.

    Note: Starting in Junos OS Release 15.1F6, you can configure as many as four streaming servers for a single sensor configuration. In previous releases, you can specify only one streaming server for each configured sensor. To specify more than one streaming server for a sensor, you must enclose the names in brackets.

    Required Privilege Level

    interface—To view this statement in the configuration.

    interface-control—To add this statement to the configuration.

     

    Related Documentation

     

    Modified: 2017-08-21