Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configuring an LRF Profile for Subscribers

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.

For example:

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.

For example:

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

For example:

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:

  1. Configure a name for the collector.

    For example:

  2. Specify the destination IP address of the collector.

    For example:

  3. Specify the destination port of the collector.

    For example:

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

    For example:

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:

  1. Configure a name for the template.

    For example:

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

    For example:

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

    For example:

    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.

  4. If you used the ipflow-tcp-ts template type, identify it as an IBM template to avoid a commit warning.
  5. 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.

    For example:

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

    For example:

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:

  1. Configure a name for the LRF rule.

    For example:

    You cannot use the same LRF rule name in multiple LRF profiles.

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

    For example:

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

    For example:

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

    The data volume, in megabytes, can be from 1 through 1024.

    For example:

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

    The time limit, in seconds, can be from 60 through 1800. The default is 300.

    For example:

Related Documentation