Monitoring, Sampling, and Collection Services Interfaces User Guide

keyboard_arrow_up

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

Configuring Actively Monitored Interfaces on M, MX and T Series Routers

date_range 13-Jan-21

arrow_backward

arrow_forward

Configure the input interfaces and apply the firewall filter that you defined earlier. Unlike passive flow monitoring, the input interfaces for active flow monitoring are not restricted, so you can select most standard network interfaces (such as ATM1 or Ethernet-based interfaces) as the input.

If you configure active flow monitoring with sampling, you can configure an interface filter in place of a firewall filter with the sampling statement at the [edit interfaces interface-name-fpc/pic/port unit unit-number family inet] hierarchy level.

content_copy zoom_out_map
[edit]
interfaces {
    so-2/2/0 {
        unit 0 {
            family inet {
                filter {
                    input active_filter;
                }
                address 10.36.11.2/32 {
                    destination 10.36.11.1;
                }
                sampling {
                    (input | output | [input output]);
                }
            }
        }
    }
}

arrow_backward PREVIOUS Configuring Active Flow Monitoring on PTX Series Packet Transport Routers

NEXT arrow_forward Collecting Flow Records

footer-navigation

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

Configuring Actively Monitored Interfaces on M, MX and T Series Routers

Stay in touch