close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Subscriber-Aware and Application-Aware Traffic Treatment Overview
- play_arrow Subscriber-Aware and Application-Aware Traffic Treatment Overview
  - Subscriber-Aware and Application-Aware Traffic Treatment Overview
  - Configuring Subscriber-Aware and Application-Aware Traffic Treatment Overview
play_arrow Applying Subscriber-Aware and Application-Aware Policies and Services
play_arrow Configuring Reporting for Subscriber-Aware Data Sessions
- play_arrow Configuring Reporting
play_arrow Modifying Subscriber-Aware Configuration
- play_arrow Modifying Subscriber-Aware Configuration in Maintenance Mode
play_arrow Monitoring and Troubleshooting
- play_arrow Monitoring and Troubleshooting
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Configuring an LRF Profile for Subscribers

date_range 06-Dec-23

arrow_backward

arrow_forward

Note:

Starting in Junos OS Release 19.3R1, LRF profiles are also supported for Broadband Subscriber Management if Next Gen Services are enabled on the MX-SPC3 services card.

Configure an LRF profile to specify a set of logging and reporting parameters, which includes data templates, collectors, and LRF rules.

To configure an LRF profile:

Configuring the LRF Profile Name

An LRF profile is identified by a name, which you later specify in the service set for the subscribers.

Configure a name for the LRF profile.

content_copy zoom_out_map
[edit services lrf]
user@host# set profile profile-name

For example:

content_copy zoom_out_map
[edit services lrf] 
user@host# set profile lrf_profile1

Configuring Policy-Based Logging

Policy-based logging causes the LRF rules to be activated by PCC rules in a static PCEF profile.

Configure policy-based logging in the LRF profile.

content_copy zoom_out_map
[edit services lrf profile profile-name]
user@host# set policy-based-logging

For example:

content_copy zoom_out_map
[edit services lrf profile  lrf_profile1]
user@host# set policy-based-logging

(Optional) Configuring HTTP Transaction Logging

Configure HTTP transaction logging if you want the HTTP metadata generated and sent separately for each transaction of a data session. This option is only relevant if the template specified in an LRF rule includes http in the template-type.

Configure HTTP transaction logging in the LRF profile.

content_copy zoom_out_map
[edit services lrf profile profile-name]
user@host# set  http-log-multiple-transactions

For example:

content_copy zoom_out_map
[edit services lrf profile  lrf_profile1]
user@host# set  http-log-multiple-transactions

Configuring Collectors

Configure one or more collectors that you want to receive logging and reporting data when an LRF rule is activated. You can configure up to eight collectors for an LRF profile. For each collector:

Configure a name for the collector.

content_copy zoom_out_map
[edit services lrf profile profile-name]
user@host# set collector collector-name

For example:

content_copy zoom_out_map
[edit services lrf profile lrf_profile1]
user@host# set collector collector1

Specify the destination IP address of the collector.

content_copy zoom_out_map
[edit services lrf profile profile-name collector collector-name destination]
user@host# set address collector-address

For example:

content_copy zoom_out_map
[edit services lrf profile  lrf_profile1 collector collector1 destination]
user@host# set address 192.0.2.5

Specify the destination port of the collector.

content_copy zoom_out_map
[edit services lrf profile profile-name collector collector-name destination]
user@host# set port collector-port-number

For example:

content_copy zoom_out_map
[edit services lrf profile  lrf_profile1 collector collector1 destination]
user@host# set port 4739

Configure the source address to be used when exporting data to the collector.

content_copy zoom_out_map
[edit services lrf profile profile-name collector collector-name]
user@host# set source-address source-address

For example:

content_copy zoom_out_map
[edit services lrf profile lrf_profile1 collector collector1]
user@host# set source-address 10.1.1.1

Configuring Templates

Configure one or more templates, each of which specifies a set of data to be transmitted when an LRF rule is activated. You can configure up to 16 templates for an LRF profile. For each template:

Configure a name for the template.

content_copy zoom_out_map
[edit services lrf profile profile-name]
user@host# set template template-name

For example:

content_copy zoom_out_map
[edit services lrf profile lrf_profile1]
user@host# set template template1

Configure a format for the template. Only the IPFIX format is supported for this release.

content_copy zoom_out_map
[edit services lrf profile profile-name template template-name]
user@host# set format ipfix

For example:

content_copy zoom_out_map
[edit services lrf profile lrf_profile1 template template1]
user@host# set format ipfix

Configure the template types, which specify the data fields to include. You must configure at least one type, and you can configure multiple types.
```
[edit services lrf profile profile-name template template-name]
user@host# set template-type template-type
```
For example:
```
[edit services lrf profile lrf_profile1 template template1]
user@host# set template-type http ipv4 
```
This example results in a template that includes fields from both the HTTP and IPv4 templates.

Note:
If you have enabled Next Gen Services on the MX-SPC3 services card, then the DNS, IFL subscriber, IPv4 extended, IPv6 extended, mobile subscriber, video, and wireline subscriber templates are not supported.
If you used the ipflow-tcp-ts template type, identify it as an IBM template to avoid a commit warning.
```
[edit services lrf profile profile-name]
user@host# set vendor-support ibm
```
Configure the interval, in seconds, at which you want the template to be retransmitted to the collector. The interval can be from 10 through 600, and the default is 60.
```
[edit services lrf profile profile-name template template-name]
user@host# set template-tx-interval tx-time
```
For example:
```
[edit services lrf profile lrf_profile1 template template1]
user@host# set template-tx-interval 100
```
Configure the type of trigger that causes the generation of data records and transmission to the collector. You can specify the trigger type as either the closing of the data session (default) or a data volume limit. The data volume limit value is specified within an LRF rule.
```
[edit services lrf profile profile-name template template-name]
user@host# set trigger-type (session-close | volume)
```
For example:
```
[edit services lrf profile lrf_profile1 template template1]
user@host# set trigger-type volume
```

Configuring Logging and Reporting Rules

Configure one or more LRF rules, which control how data sessions are logged and reported. You can configure up to 32 LRF rules for an LRF profile. For each LRF rule:

Configure a name for the LRF rule.
```
[edit services lrf profile profile-name]
user@host# set rule lrf-rule-name
```
For example:
```
[edit services lrf profile lrf_profile1]
user@host# set rule rule1
```
You cannot use the same LRF rule name in multiple LRF profiles.

Specify the collector that you want to receive the data if this rule is matched.

content_copy zoom_out_map
[edit services lrf profile profile-name rule lrf-rule-name ]
user@host# set then report collector collector-name

For example:

content_copy zoom_out_map
[edit services lrf profile lrf_profile1 rule rule1]
user@host# set then report collector collector1

Specify the template that identifies the type of data to report if this rule is matched.

content_copy zoom_out_map
[edit services lrf profile profile-name rule lrf-rule-name]
user@host# set then report template template-name

For example:

content_copy zoom_out_map
[edit services lrf profile lrf_profile1 rule rule1]
user@host# set then report template template1

If you specified volume for the template’s trigger type in Step 6 of Configuring Templates, configure the data volume limit to be used for reporting by this rule.
```
[edit services lrf profile profile-name rule lrf-rule-name]
user@host# set then report volume-limit volume
```
The data volume, in megabytes, can be from 1 through 1024.

For example:
```
[edit services lrf profile lrf_profile1 rule rule1]
user@host# set then report volume-limit 4
```
If you specified time for the template’s trigger type in Step 6 of Configuring Templates, configure the time limit to be used for reporting by this rule.
```
[edit services lrf profile profile-name rule lrf-rule-name]
user@host# set then report time-limit time-interval
```
The time limit, in seconds, can be from 60 through 1800. The default is 300.

For example:
```
[edit services lrf profile lrf_profile1 rule rule1]
user@host# set then report time-limit 360
```

arrow_backward PREVIOUS Configuring Logging and Reporting for Junos OS Subscriber Aware

NEXT arrow_forward Assigning an LRF Profile to Subscribers

Subscriber-Aware and Application-Aware Traffic Treatment User Guide

ON THIS PAGE

Configuring an LRF Profile for Subscribers

Configuring the LRF Profile Name

Configuring Policy-Based Logging

(Optional) Configuring HTTP Transaction Logging

Configuring Collectors

Configuring Templates

Configuring Logging and Reporting Rules

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Subscriber-Aware and Application-Aware Traffic Treatment User Guide

ON THIS PAGE

Configuring an LRF Profile for Subscribers

Configuring the LRF Profile Name

Configuring Policy-Based Logging

(Optional) Configuring HTTP Transaction Logging

Configuring Collectors

Configuring Templates

Configuring Logging and Reporting Rules

Related Documentation

Stay in touch