Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

template-type (LRF Profile)

Syntax

Hierarchy Level

Description

Configure the template types for the template, which specify the data fields to include. You must configure at least one type, and you can configure multiple types.

If Next Gen Services is enabled, then the template types dns, ifl-subscriber, ipv4-extended, ipv6-extended, mobile-subscriber, video, and wireline-subscriber are not available.

Options

template-type

Template type. You must configure at least one of the following types, and you can configure multiple types:

  • device-data—Use data fields specific to the device collecting the logging feed.

  • dns—(Not available if Next Gen Services is enabled) Use the DNS response time data field.

  • flow-id—Use the Flow ID data field.

  • http—Use data fields for the HTTP metadata from header fields.

  • ifl-subscriber—(Not available if Next Gen Services is enabled) Use data fields specific to interface-based subscribers.

  • ipflow—Use data fields for the uplink and downlink octets and bytes.

  • ipflow-extended—Use data fields for the service set name, routing instance, and payload timestamps.

  • ipflow-tcp—Use data fields for TCP-related timestamps.

  • ipflow-tcp-ts—Use IBM-specific data fields for TCP-related timestamps.When configuring a ipflow-tcp-ts template, configure vendor-support ibm at the [edit services lrf profile profile-name] hierarchy level to avoid a commit warning.

  • ipflow-ts—Use data fields for the flow start and end timestamps.

  • ipv4—Use data fields for the basic source and destination IPv4 information.

  • ipv4-extended—(Not available if Next Gen Services is enabled) Use data fields for the elements of IPv4 extended fields.

  • ipv6—Use data fields for the basic source and destination IPv6 information.

  • ipv6-extended—(Not available if Next Gen Services is enabled) Use data fields for the elements of IPv6 extended fields.

  • l7-app—Use data fields for the Layer 7 application.

  • mobile-subscriber—(Not available if Next Gen Services is enabled) Use data fields specific to mobile subscribers.

  • pcc—Use the PCC rule name data field.

  • status-code-dist—Use data fields for the HTTP or DNS status codes.

  • subscriber-data—Use data fields for Generic Subscriber information that can be included with wireless (mobile) subscribers or wireline subscribers.

  • transport-layer—Use data fields for the transport layer.

  • video—(Not available if Next Gen Services is enabled) Use data fields for video traffic.

  • wireline-subscriber—(Not available if Next Gen Services is enabled) Use the UserName data field for wireline subscribers.

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

Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series.