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

Processing IPv4 traffic on an M, MX or T Series Router Using Monitoring services, Adaptive services or Multiservices Interfaces

date_range 13-Jan-21

arrow_backward

arrow_forward

You configure the monitoring services, adaptive services, or multiservices interfaces with the family inet statement so they can process IPv4 traffic. However, you must remember that a monitoring services interface uses an mo- prefix and adaptive services and multiservices interfaces use an sp- prefix.

content_copy zoom_out_map
[edit]
interfaces {
    sp-2/0/0 {
        unit 0 {
            family inet {
                address 10.36.100.1/32 {
                    destination 10.36.100.2;
                }
            }
        }
    }
}

Active flow monitoring records leave the router through an export interface to reach the flow monitoring server.

content_copy zoom_out_map
[edit]
interfaces {
    fe-1/0/0 {
        unit 0 {
            family inet {
                address 10.60.2.2/30;
            }
        }
    }
}

arrow_backward PREVIOUS Defining a Firewall Filter on M, MX and T Series Routers to Select Traffic for Active Flow Monitoring

NEXT arrow_forward Replicating M, MX and T Series Routing Engine-Based Sampling to Multiple Flow Servers

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

Processing IPv4 traffic on an M, MX or T Series Router Using Monitoring services, Adaptive services or Multiservices Interfaces

Stay in touch