sensor (Junos Telemetry Interface)
Syntax
sensor sensor-name {
export-name export-profile-name;
polling-interval seconds;
resource resource-string;
<resource-filter regular expression>;
server-name [ streaming-server-names ];
}
Hierarchy Level
[edit services analytics]
Description
Configure a Junos telemetry interface sensor, which defines the parameters of a system resource to monitor and stream data. 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-name |
Specify a name that defines the sensor configuration. For example, for a
sensor configuration that monitors all LSP events, you might choose the
name |
| export-name export-profile-name |
Specify the name of an export profile that you configured at the
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. |
| polling-interval seconds |
Specify the interval at which the Junos Telemetry Interface sensor generates data to export to the collector. As the configured interval expires, the most recent sample collected by the sensor is gathered and forwarded to the server configured to collect data. Note:
For Packet Forwarding Engine sensors, the minimum reporting rate is 2 seconds.
|
| resource resource-string |
Enable 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
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.
You can also use the Telemetry Explorer
tool to search for and view information about
resource-identifier-string.
|
resource string |
Description |
Release Information |
|---|---|---|
|
/interfaces/interface/ethernet/state/counters/jnx-pfc-statistics |
Transport statistics providing pause frame receive and transmit counter support. |
Junos OS Evolved Release 21.4R1 and later on PTX10001-36MR, PTX10004, PTX10008, and PTX10016 routers. |
|
/junos/events |
System events sensor. Starting with Junos OS Release 18.1R1, this sensor corresponds to system log messages (syslog). The sensor must be used with an To subscribe for specific events, you can subscribe for /junos/events/event[id=‘EVENT_NAME’] where event EVENT_NAME is the event id that you are interested in. Alternatively, you can subscribe to any XPATH Many event names can be found in the messages log file. |
Junos OS 18.1R1 and later on all JTI platforms. |
|
/junos/services/ip-tunnel/usage/ |
Packet Forwarding Engine packet statistics sensor. The statistics are used to report various network element performance metrics in a scalable and efficient way, providing visibility into Packet Forwarding Engine errors and drops. A timestamp indicating when the counters were last reset is included with all the exported data to allow collectors to determine if and when a reset event happened; for example, if the Packet Forwarding Engine hardware restarted. Exported statistics are similar to the output of the operational
mode command |
Junos OS 17.4R1 and later on MX Series devices. |
|
/junos/services/label-switched-path/usage/ |
Packet Forwarding Engine sensor for LSP statistics. 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. For bypass LSPs, the following are exported:
When the bypass LSP is active, traffic is exported both on the bypass LSP and the ingress (protected) LSP. On MX Series routers only, bidirectional LSPs for ultimate-hop popping (UHP) are also supported. Note:
You can modify
When you enable a sensor for LSP statistics, you must also
configure the |
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 and QFX5110 switches. Junos OS Release 18.2R1 and later on QFX5100, QFX5110, and QFX5200 switches Junos OS Release 18.3R1 and later on QFX5120-48Y and EX4650 switches Junos OS Release 18.4R1 and later on EX4600 switches Junos OS Release 19.1R1 and later on QFX10002 switches and PTX10002 routers |
|
/junos/services/ldp/label-switched-path/ingress/usage/ |
Packet Forwarding Engine sensor for LDP LSP ingress statistics. When you enable a sensor for LDP statistics, you must also
configure the On PTX Series routers, this feature is not supported for the following variants:
|
Junos OS Release 20.2R1 for MX series and PTX series routers. Junos OS Release 20.3R1 on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards. |
|
/junos/services/ldp/label-switched-path/transit/usage/ |
Packet Forwarding Engine sensor for LDP LSP transit statistics. On PTX Series routers, this feature is not supported for the following variants:
|
Junos OS Release 20.2R1 for MX series and PTX series routers. Junos OS Release 20.3R1 on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards. |
|
/junos/services/ldp/p2mp/interface/receive/usage/ |
Packet Forwarding Engine sensor for LDP P2MP receive statistics. On PTX Series routers, this feature is not supported for the following variants:
|
Junos OS Release 20.2R1 for MX series and PTX series routers. Junos OS Release 20.3R1 on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards. |
|
/junos/services/ldp/p2mp/interface/transmit/usage/ |
Packet Forwarding Engine sensor for LDP P2MP transmit statistics. On PTX Series routers, this feature is not supported for the following variants:
|
Junos OS Release 20.2R1 for MX series and PTX series routers. Junos OS Release 20.3R1 on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards. |
|
/junos/services/ldp/p2mp/label-switched-path/usage/ |
Packet Forwarding Engine sensor for LDP P2MP LSP statistics. On PTX Series routers, this feature is not supported for the following variants:
|
Junos OS Release 20.2R1 for MX series and PTX series routers. Junos OS Release 20.3R1 on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards. |
|
/junos/services/segment-routing/sid/usage/ |
Source Packet Routing in Networking (SPRING) sensorSfor transit statistics. SPRING is also known as segment routing. Before statistics can be exported, you must first enable them by
including the |
Junos OS Release 19.1R1 and later on PTX3000 routers and PTX5000 with FPC2 |
|
/junos/services/spu/delegated-rpm/ |
Delegated Realtime Performance Monitoring (RPM) service sensor. Delegated RPM is a mode where RPM probe generation and measurement calculation are done by MS-MIC and MS-MPC cards. This hardware assistance allows a very high scale of concurrent RPM probes. You can use the resulting data from this sensor to improve network design and optimize traffic engineering. Data can also be used to detect problems in individual devices as well as in the overall network and the traffic carried by it. JTI sensor support for other RPM modes was added in Junos OS Release 18.3R1. This sensor has the following limitations:
|
Junos OS Release 19.1R1 and later on MX Series routers operating with MS-MIC and MS-MPC |
|
/junos/services/spu/ipsec-vpn |
UDP-based PIC sensors. Starting with Junos OS Release 18.1R1, this sensor provides visibility for IPSec services on different service complexes and nodes. Exported data is defined using an IP address and a UDP port. When an export interval expires, the most recent statistics collected by the sensors are gathered, placed in the payload of a UDP packet, and forwarded to a collector. A timestamp indicating when counters are read is included with the exported data to allow collectors to collate data. The timestamp also can determine if and when an event happened, such as a PIC hardware restart or if counters were cleared by means of the CLI. |
Junos OS 18.1R1 on MX Series with MS-MICs and MS-MPCs |
|
/junos/services/spu/servicesets |
Sensor to export service set statistics. These sensors provide visibility for services on different service complexes and nodes (for example, IPSec services). Exported data is defined using an IP address and a UDP port. When an export interval expires, the most recent statistics collected by the sensors are gathered, placed in the payload of a UDP packet, and forwarded to a collector. A timestamp indicating when counters are read is included with the exported data to allow collectors to collate data. The timestamp also can determine if and when an event happened, such as a PIC hardware restart or if counters were cleared by means of the CLI. |
Junos OS 18.2R1 on MX Series with MS-MICs and MS-MPCs |
|
/junos/services/spu/sessions |
Sensor to export session statistics. These sensors provide visibility for services on different service complexes and nodes (for example, IPSec services). Exported data is defined using an IP address and a UDP port. When an export interval expires, the most recent statistics collected by the sensors are gathered, placed in the payload of a UDP packet, and forwarded to a collector. A timestamp indicating when counters are read is included with the exported data to allow collectors to collate data. The timestamp also can determine if and when an event happened, such as a PIC hardware restart or if counters were cleared by means of the CLI. |
Junos OS 18.2R1 on MX Series with MS-MICs and MS-MPCs |
|
/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 a node virtualization configuration on MX series 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 GNFs along with the fabric statistics for all traffic ingressing from and egressing to the fabric from that the packet forwarding engine. |
Junos OS Release 18.4R1 and later on MX480, MX960, MX2008, MX2010, MX2020, and MX-ELM routers |
|
/junos/system/linecard/cos/interface/interface-set/output/queue/ |
Sensor for logical interface (IFL)-set. The sensor streams queue statistics using Juniper proprietary gRPC and gNMI or by means of UDP. Zero suppression (suppressing zero values in statistics from streamed data) is also supported. |
Junos OS Release 22.3R1and later on MX204, MX240, MX304, MX480, MX960, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016 routers with Trio chipset EA, ZT, and YT-based fixed systems and modular systems linecards. |
|
/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 and QFX5110 switches. Junos OS Release 18.2R1 and later on QFX5100, QFX5110, and QFX5200 witches Junos OS Release 18.3R1 and later on QFX5120-48Y and EX4650 switches Junos OS Release 18.4R1 and later on EX4600 switches Junos OS Release 19.1R1 and later on QFX10002 switches and PTX10002 Routers Junos OS Release 20.2R1 and later on EX2300, EX2300-MP, and EX3400 switches |
|
/junos/system/linecard/ddos/ |
Distributed denial of service (DDoS) sensor. This sensor supports the Openconfig data model junos/ui/openconfig/yang/ and junos-ddos.yang. You can stream information using Juniper proprietary gRPC or UDP (native) export. There are 45 packet types for DDoS. To maintain a reasonably sized data stream, data is exported for all protocols that have seen traffic using the zero-suppression model. On QFX5000 platforms, multiple protocols can share the same CPU queue. DDoS configurations are applied at the CPU queue level. Consequently, DDoS statistics fetched from the CPU queue will return the aggregate value of all protocols using that queue. For example, if BGP, LDP, and RSVP protocols are using a particular CPU queue, but the DDoS limit is violated only by the BGP protocol, the DDoS violation reported will include all three protocols: BGP, LDP, and RSVP. This information will be exported to the collector with the DDoS sensor. |
Junos OS Release 22.1R1 and later on EX4650, QFX5110, QFX5120-48Y, QFX5200 and QFX5210 switches Junos OS Evolved Release 22.3R1 and later on PTX10001-36MR, PTX10003, PTX10004, PTX10008 and PTX10016 routers. |
|
/junos/system/linecard/environment/ |
FPC environment sensor
|
Junos OS Release 22.4R1 and later on MX10004 routers. |
|
/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 and QFX5110 switches. Junos OS Release 18.2R1 and later on QFX5100, QFX5110, and QFX5200 switches Junos OS Release 18.3R1 and later on QFX5120-48Y and EX4650 switches Junos OS Release 18.4R1 and later on EX4600 switches Junos OS Release 20.2R1 and later on EX2300, EX2300-MP, and EX3400 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 |
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, QFX5110 switches and MX150 routers. Junos OS Release 18.2R1 and later on QFX5100, QFX5110, and QFX5200 switches Junos OS Release 18.3R1 and later on QFX5120-48Y and EX4650 switches Junos OS Release 18.4R1 and later on EX4600 switches Junos OS Release 19.1R1 and later on QFX10002 Switches and PTX10002 routers Junos OS Release 20.2R1 and later on EX2300, EX2300-MP, and EX3400 switches Junos OS Evolved Release 20.2R1 and later on PTX10008 routers. UDP streaming is not supported over the management interface. |
|
/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 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 and QFX5110 switches Junos OS Release 18.2R1 and later on QFX5100, QFX5110, and QFX5200 switches Junos OS Release 18.3R1 and later on QFX5120-48Y and EX4650 switches Junos OS Release 18.4R1 and later on EX4600 switches Junos OS Release 20.2R1 and later on EX3400 switches Junos OS Evolved Release 20.2R1 and later on PTX10008 routers. UDP streaming is not supported over the management interface. |
|
/junos/system/linecard/interface/queue/ |
Packet Forwarding Engine sensor for physical interface traffic.
Exports all queue fields from
To export traffic and queue data for physical interfaces, use
|
Junos OS Release 18.3R1 and later on PTX Series and ACX Series routers and EX Series, MX Series, and QFX Series switches. |
|
/junos/system/linecard/interfaces/logical/usage/ |
Packet Forwarding Engine sensor for logical interface statistics. |
Junos OS Evolved Release 21.4R1 and later on PTX10001-36MR, PTX10004, PTX10008, and PTX10016 routers. |
|
/junos/system/linecard/interfaces/traffic/ |
Packet Forwarding Engine sensor for physical interface traffic. Exports traffic fields only |
Junos OS Evolved Release 21.4R1 and later on PTX10001-36MR, PTX10004, PTX10008, and PTX10016 routers. |
|
/junos/system/linecard/intf-exp/ |
Interface express sensor. This sensor leverages statistics out of the physical interface sensor, providing faster and more frequent operational status statistics. Only the physical interfaces’ operational status from the Flexible PIC Concentrator (FPC) is collected and reported. Statistics from the Routing Engine interface are not reported. |
Junos OS Release 18.1R1 and later on PTX1000, PTX3000, PTX5000, and PTX10000 routers. Junos OS Release 19.3R1 and later on MX960, MX2010, and MX2020 routers. |
|
/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 OS Release 19.1R1 and later on PTX10002 routers. Junos OS Evolved Release 20.2R1 and later on PTX10008 routers. UDP streaming is not supported over the management interface. Junos OS Release 21.4R1 and later on EX4650, QFX5110, QFX5120-48Y, QFX5200, and QFX5210 switches. |
|
/junos/system/linecard/npu/utilization/ |
Packet Forwarding Engine sensor for NPU processor utilization. |
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 OS Release 19.1R1 and later on PTX10002 routers. Junos OS Evolved Release 20.2R1 and later on PTX10008 routers. UDP streaming is not supported over the management interface. |
|
/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 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 17.1R1 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. |
|
|
Sensor for Packet Forwarding Engine error and drop statistics. Use these statistics to optimize traffic engineering and improve your network design. When you include the resource path
|
Junos OS Release 22.1R1 and later on PTX1000 and PTX5000 routers and QFX10002-60C switches using Juniper proprietary gRPC. |
|
/junos/system/linecard/qmon/ |
Sensor for queue depth statistics for ingress and egress queue traffic. Statistics are exported directly from the line card. This sensor only supports single -streaming. Configuring this sensor to stream to multiple servers is not supported. If multiple servers are configured, no data is sent to any of the configured servers. The following example shows a configuration for single-streaming that will send data: sensor qmon {
server-name TEMP;
export-name export-common;
resource /junos/system/linecard/qmon/;
}
The following example shows a multiple-server configuration that will not send data: sensor qmon {
server-name TEMP;
server-name digi1;
server-name digi2;
export-name export-common;
resource /junos/system/linecard/qmon/;
}
Note:
Issuing an operational |
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. Note:
virtual MX Series (vMX) routers are not supported. |
|
/junos/system/linecard/qmon-sw/ |
Sensor for congestion and latency monitoring statistics. |
Junos OS Release 18.2R1 and later on QFX5100, QFX5110, and QFX5200 Switches Junos OS Release 18.3R1 and later on QFX5120-48Y and EX4650 Switches Junos OS Release 18.4R1 and later on EX4600 switches Junos OS Release 20.2R1 and later on EX3400 switches Junos OS Release 21.2R1 and later on PTX5000, PTX1000, PTX10002, PTX10008, and PTX10016 routers and QFX10002, QFX10008, and QFX10016 switches |
|
/junos/system/linecard/fabric/ |
Sensor for fabric statistics. The following types of statistics can be exported:
|
Junos OS Release 17.2R1 and later on MX Series routers only. Junos OS Evolved Release 20.2R1 and later on PTX10008 routers. UDP streaming is not supported over the management interface. Note:
virtual MX Series (vMX) routers are not supported. |
|
/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. |
Junos OS Release 17.4R1 and later on MX Series and PTX Series routers |
|
/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. 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 |
Junos OS Release 17.4 and later on MX Series and PTX5000 routers. |
|
|
Sensor for policy and charging rules function (PCRF) statistics for subscribers. |
Junos OS Release 19.3R1 on MX5, MX10, MX40, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, and MX100016 routers. |
|
|
Sensor for Online Charging System (OCS) statistics for subscribers. |
Junos OS Release 19.3R1 on MX5, MX10, MX40, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, and MX100016 routers. |
|
|
Sensor for Network Access Server Application (NASREQ) statistics for subscribers. |
Junos OS Release 19.3R1 on MX5, MX10, MX40, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, and MX100016 routers. |
|
|
Diameter peer sensor that provides response time measurements for messages exchanged between an MX router and the peer for PCRF statistics. This sensor includes response-time and delay measurements in milliseconds. Note:
The delay measurements are made over a 60-second measurement interval. As the reporting interval may be as much as 59 seconds out of phase with the measurement interval, the response time values may not be aligned with the reporting interval. |
Junos OS Release 19.3R1 on MX5, MX10, MX40, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, and MX100016 routers. |
|
|
Diameter peer sensor that provides response time measurements for messages exchanged between an MX router and the peer for OCS statistics. This sensor includes response-time and delay measurements in milliseconds. Note:
The delay measurements are made over a 60-second measurement interval. As the reporting interval may be as much as 59 seconds out of phase with the measurement interval, the response time values may not be aligned with the reporting interval. |
Junos OS Release 19.3R1 on MX5, MX10, MX40, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, and MX100016 routers. |
|
|
Diameter peer sensor that provides response time measurements for messages exchanged between an MX router and the peer for NASREQ statistics. This sensor includes response-time and delay measurements in milliseconds. Note:
The delay measurements are made over a 60-second measurement interval. As the reporting interval may be as much as 59 seconds out of phase with the measurement interval, the response time values may not be aligned with the reporting interval. |
Junos OS Release 19.3R1 on MX5, MX10, MX40, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, and MX100016 routers. |
|
|
This PFE sensor exports the statistics of DDOS from MPC1, MPC2, MPC3, MPC5, MPC6, MPC7, MPC8, and MPC9 line cards. |
Junos OS Release 21.1R1 on MX Series routers. |
|
|
Page drop statistics include page drop counter, interface and queue details. |
Junos OS Evolved Release 22.3R1 on PTX10003 routers. |
| 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:
|
| server-name [ streaming- server-names ] |
Specify one or more servers to transport data for collection. Include at
least one server-name configured at the 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.
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 19.1R1 for PTX3000 routers and PTX5000 routers with FPC2.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.