Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

jflow-log (Services)

date_range 19-Nov-23

Syntax

content_copy zoom_out_map
jflow-log {
    collector collector-name {
        source-ip address;
        destination-address address;
        destination-port port-number; 
    }
    collector-group collector-group-name {
        [collector-name1 collector-name2];
    }
    template-profile template-profile-name {
        collector collector-name ;
        collector-group collector-group-name ;
        template-type nat;
        version (ipfix | v9);
        refresh-rate packets packets seconds seconds;
    message-rate-limit messages-per-second

Hierarchy Level

content_copy zoom_out_map
[edit services]

Description

Enable the mechanism to record logging messages in flow monitoring format for NAT events. For this transmission of flow monitoring logs to work properly, the services PIC interface must have an IP address and appropriate logging options configured.

You can configure MX Series routers with MS-MPCs and MS-MICs to log network address translation (NAT) events using the Junos Traffic Vision (previously known as Jflow) version 9 or IPFIX (version 10) template format. This method of generating flow monitoring records for NAT events, such as NAT44 and NAT64 session creation and deletion, and NAT44 and NAT64 binding information base events, enables cohesive and streamlined analysis of NAT traffic and troubleshooting of NAT-related problems.

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 14.2R2.

footer-navigation