close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Flow Monitoring and Flow Collection Services
play_arrow Flow Capture Services
- play_arrow Dynamically Capturing Packet Flows Using Junos Capture Vision
- play_arrow Detecting Threats and Intercepting Flows Using Junos Flow-Tap and FlowTapLite Services
play_arrow Inline Monitoring Services and Inband Network Telemetry
- play_arrow Inline Monitoring Services
  - Inline Monitoring Services Configuration
- play_arrow Flow-Based Telemetry
  - Flow-Based Telemetry (EX4100, EX4100-F, and EX4400 Series)
  - Flow-Based Telemetry for VXLANs (QFX5120)
- play_arrow Inband Flow Analyzer 2.0
  - Inband Flow Analyzer (IFA) 2.0 Probe for Real-Time Flow Monitoring
- play_arrow Juniper Resiliency Interface
  - Juniper Resiliency Interface
play_arrow Sampling and Discard Accounting Services
play_arrow Real-Time Performance Monitoring and Video Monitoring Services
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

keyboard_arrow_right

Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats

date_range 13-Jan-21

arrow_backward

arrow_forward

You can configure MX Series routers with MS-MPCs, MS-MICs, and MX-SPC3s to log network address translation (NAT) events using the Junos Traffic Vision (previously known as Jflow) version 9 or IPFIX (version 10) template format. NAT event logger generates logs or template records in flow monitoring format and transmits them to the specified external collector or server for various NAT events, such as NAT44 and NAT64 session creation and deletion, and NAT44 and NAT64 binding information base events.

Note:

This functionality is supported on MX Series routers with Junos OS Extension-Provider packages installed and configured on the device, and on MS-MPCs, MS-PICs, and MX-SPC3s. It is not supported on MS-DPCs with MX Series routers.

You can configure the mechanism to record logging messages in flow monitoring format for NAT events. You need to define collectors, and template profiles that contain the properties for flow monitoring logs. You can create a template profile for a particular NAT service on an MX Series router with MS-MPCs, MS-MICs, or MX-SPC3s, or for a service set, which applies for all of the NAT services. You can define a template profile to generate flow monitoring logs in a specific flow template format and associate the specified template profile with a service set.

To enable the flow monitoring log capability for NAT events and configure the transmission of logs to collectors at a service level:

Define the flow monitoring log service to be applied on an interface to control the maximum number of flow monitoring logs generated for NAT error events.

content_copy zoom_out_map
[edit] 
user@host# set interfaces ms-fpc/pic/port services-options jflow-log message-rate-limit messages-per-second

For example:

content_copy zoom_out_map
[edit] 
user@host# set interfaces ms-5/0/0 services-options jflow-log message-rate-limit 50

Configure the collectors and collector groups.

content_copy zoom_out_map
[edit] 
user@host# set services jflow-log collector collector-name destination-address address destination-port port-number source-ip address
user@host# set services jflow-log collector-group collector-group-name collector [ collector-name1 collector-name2] 

For example:

content_copy zoom_out_map
[edit] 
user@host# set services jflow-log collector c1 destination-address 203.0.113.3 destination-port 1 source-ip 192.0.2.1
user@host# set services jflow-log collector-group cg1 collector c1 

Configure the template profiles and associate the template profile with the collector or collector group.

content_copy zoom_out_map
[edit] 
user@host# set services jflow-log template-profile template-profile-name collector collector-name version (ipfix | v9) template-type nat refresh-rate packets packets seconds seconds
user@host# set services jflow-log template-profile template-profile-name collector-group collector-group-name version (ipfix | v9) template-type nat refresh-rate packets packets seconds seconds

For example:

content_copy zoom_out_map
[edit] 
user@host# set services jflow-log template-profile t1 collector c1 version ipfix template-type nat refresh-rate packets 20 seconds 20 
user@host# set services jflow-log template-profile t1 collector-group cg1
user@host# set services jflow-log template-profile t2 collector c2 version v9 template-type nat refresh-rate packets 20 seconds 20 

Associate the template profile with the service set.

content_copy zoom_out_map
[edit]
user@host# set services service-set service-set-name jflow-log template-profile template-profile-name

For example:

content_copy zoom_out_map
[edit]
user@host# set services service-set sset_0 jflow-log template-profile t1

arrow_backward PREVIOUS Mapping Between Field Values for IPFIX Flow Templates and Logs Exported From an MX Series Router or NFX250

NEXT arrow_forward Example: Configuring Logs in Flow Monitoring Format for NAT Events on MX Series Routers for Troubleshooting

Monitoring, Sampling, and Collection Services Interfaces User Guide

Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats

Stay in touch

Helped me install or use the product
Accelerated my deployment

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

Monitoring, Sampling, and Collection Services Interfaces User Guide

Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats

Related Documentation

Stay in touch