export-profile (Junos Telemetry Interface)
Syntax
export-profile name {
dscp value;
forwarding-class (assured-forwarding | best-effort | expedited-forwarding | network-control);
local-address ip-address;
local-port source-port-number;
loss-priority (high | low | medium-high | medium-low);
<payload-size bytes>;
reporting-rate seconds;
routing-instance routing-instance-name
dialout-type (native-udp-gpb | native-udp-compact | native-grpc-gpb)
}
Hierarchy Level
[edit services analytics]
Description
Configure the parameters of the export process for data generated through Junos Telemetry sensors. You can create one or more export profiles. Each profile can be associated with one or more sensors that define the system resource to monitor and stream data. You can associate only one export profile with a specific sensor configuration.
The IP layer delivers the exported data to the remote server. The export profile configuration allows you to specify the rate which the system generates data, the local source port and IP address that are used to define the transport headers in the exported packets, and the type of dial-out connection.
To enable Junos Telemetry , you must also configure a sensor that defines the parameters of the
system resource to monitor and stream data, and a server to collect the data. To
configure a sensor, include the sensor
sensor-name statement at the [edit services
analytics] hierarchy level. To configure the server that functions as a
data collector, include streaming-server
server-name statement at the [edit services
analytics] hierarchy level.
Junos Telemetry Interface was introduced in Junos OS Release 15.1F3 on MX Series routers with interfaces configured on MPC1 through MPC6E and on PTX Series routers with interfaces configured on FPC3. Starting in Junos OS Release 15.1F5, Junos Telemetry Interface is also supported on MPC7E, MPC8E, and MPC9E on MX Series routers.
Starting with Junos OS Release 16.1R3, FPC1 and FPC2 on PTX Series routers are also supported.
Starting with Junos OS Release 17.2R1, QFX10000 switches and PTX1000 routers are also supported.
Options
| name | Name of export profile. Note:
To associate this export profile with a configured sensor, include the |
| dscp value | Specify the DSCP value for the exported packets.
|
| forwarding-class (assured-forwarding | best-effort | expedited-forwarding | network-control) | (Packet Forwarding Engine sensors only) Specify the forwarding class for exported packets.
|
| loss-priority (high | low | medium-high | medium-low) (MX Series only) | Specify the loss priority for exported packets. Loss priority settings help determine which packets are dropped from the network during periods of congestion. |
| local-address ip-address | Specify the source address of exported packets. |
| local-port number | Specify the source port for the exported packets. |
| payload-size bytes (Optional) | Specify the maximum size of exported packets. Note:
The
|
| reporting-rate seconds | Specifies the interval, in seconds, at which the Junos Telemetry Interface (JTI) sensor exports data to the collector.
Note:
Starting with Junos OS and Junos Evolved 23.4R2, the minimum supported value for
|
| dialout-type (native-udp-gpb | native-udp-compact | native-grpc-gpb) | Specify the type of dial-out connection.
Note: The
format and
transport options are deprecated. |
| routing-instance rounting-instance-name | Specify the routing instance to be used for grpc transport. The |
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.
payload-size bytes option introduced in Junos OS Release 16.1R3.
loss-priority option introduced in Junos OS Release 17.3R1 for MX Series routers only.
Statement introduced in Junos OS Release 17.4R1 for virtual MX Series (vMX) routers.
dialout-type option introduced in Junos OS Release 25.4R1.
Options deprecated in Junos OS Release 25.4R1 are format and
transport.