- play_arrow Flow Monitoring and Flow Collection Services
- play_arrow Understanding Flow Monitoring
- play_arrow Monitoring Traffic Using Active Flow Monitoring
- Configuring Active Flow Monitoring
- Active Flow Monitoring System Requirements
- Active Flow Monitoring Applications
- Active Flow Monitoring PIC Specifications
- Active Flow Monitoring Overview
- Active Flow Monitoring Overview
- Example: Configuring Active Monitoring on an M, MX or T Series Router’s Logical System
- Example: Configuring Flow Monitoring on an MX Series Router with MS-MIC and MS-MPC
- Configuring Services Interface Redundancy with Flow Monitoring
- Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250
- Configuring Flow Offloading on MX Series Routers
- Configuring Active Flow Monitoring on PTX Series Packet Transport Routers
- Configuring Actively Monitored Interfaces on M, MX and T Series Routers
- Collecting Flow Records
- Configuring M, MX and T Series Routers for Discard Accounting with an Accounting Group
- Configuring M, MX and T Series Routers for Discard Accounting with a Sampling Group
- Configuring M, MX and T Series Routers for Discard Accounting with a Template
- Defining a Firewall Filter on M, MX and T Series Routers to Select Traffic for Active Flow Monitoring
- Processing IPv4 traffic on an M, MX or T Series Router Using Monitoring services, Adaptive services or Multiservices Interfaces
- Replicating M, MX and T Series Routing Engine-Based Sampling to Multiple Flow Servers
- Replicating Version 9 Flow Aggregation From M, MX and T Series Routers to Multiple Flow Servers
- Configuring Routing Engine-Based Sampling on M, MX and T Series Routers for Export to Multiple Flow Servers
- Example: Copying Traffic to a PIC While an M, MX or T Series Router Forwards the Packet to the Original Destination
- Configuring an Aggregate Export Timer on M, MX and T Series Routers for Version 8 Records
- Example: Sampling Configuration for M, MX and T Series Routers
- Associating Sampling Instances for Active Flow Monitoring with a Specific FPC, MPC, or DPC
- Example: Sampling Instance Configuration
- Example: Sampling and Discard Accounting Configuration on M, MX and T Series Routers
- play_arrow Monitoring Traffic Using Passive Flow Monitoring
- Passive Flow Monitoring Overview
- Passive Flow Monitoring System Requirements for T Series, M Series and MX Series Routers
- Passive Flow Monitoring Router and Software Considerations for T Series, M Series and MX Series Routers
- Understanding Passive Flow Monitoring on T Series, M Series and MX Series Routers
- Enabling Passive Flow Monitoring on M Series, MX Series or T Series Routers
- Configuring Passive Flow Monitoring
- Example: Passive Flow Monitoring Configuration on M, MX and T Series Routers
- Configuring a Routing Table Group on an M, MX or T Series Router to Add Interface Routes into the Forwarding Instance
- Using IPSec and an ES PIC on an M, MX or T Series Router to Send Encrypted Traffic to a Packet Analyzer
- Applying a Firewall Filter Output Interface on an M, MX or T Series Router to Port-mirror Traffic to PICs or Flow Collection Services
- Monitoring Traffic on a Router with a VRF Instance and a Monitoring Group
- Specifying a Firewall Filter on an M, MX or T Series Router to Select Traffic to Monitor
- Configuring Input Interfaces, Monitoring Services Interfaces and Export Interfaces on M, MX or T Series Routers
- Establishing a VRF Instance on an M, MX or T Series Router for Monitored Traffic
- Configuring a Monitoring Group on an M, MX or T Series Router to Send Traffic to the Flow Server
- Configuring Policy Options on M, MX or T Series Routers
- Stripping MPLS Labels on ATM, Ethernet-Based and SONET/SDH Router Interfaces
- Using an M, MX or T Series Router Flow Collector Interface to Process and Export Multiple Flow Records
- Example: Configuring a Flow Collector Interface on an M, MX or T Series Router
- play_arrow Processing and Exporting Multiple Records Using Flow Collection
- play_arrow Logging Flow Monitoring Records with Version 9 and IPFIX Templates for NAT Events
- Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250
- Configure Active Flow Monitoring Logs for NAT44/NAT64
- Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series Router or NFX250
- Exporting Syslog Messages to an External Host Without Flow Monitoring Formats Using an MX Series Router or NFX250
- Exporting Version 9 Flow Data Records to a Log Collector Overview Using an MX Series Router or NFX250
- Understanding Exporting IPFIX Flow Data Records to a Log Collector Using an MX Series Router or NFX250
- Mapping Between Field Values for Version 9 Flow Templates and Logs Exported From an MX-Series Router or NFX250
- Mapping Between Field Values for IPFIX Flow Templates and Logs Exported From an MX Series Router or NFX250
- Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats
- Example: Configuring Logs in Flow Monitoring Format for NAT Events on MX Series Routers for Troubleshooting
-
- 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
- Understanding the FlowTap and FlowTapLite Services
- Understanding FlowTap and FlowTapLite Architecture
- Configuring the FlowTap Service on MX Series Routers
- Configuring a FlowTap Interface on MX Series Routers
- Configuring FlowTap and FlowTapLite Security Properties
- FlowTap and FlowTapLite Application Restrictions
- Examples: Configuring the FlowTapLite Application on MX Series and ACX Series Routers
- Configuring FlowTapLite on MX Series Routers and M320 Routers with FPCs
-
- play_arrow Inline Monitoring Services and Inband Network Telemetry
- play_arrow Inline Monitoring Services
- play_arrow Flow-Based Telemetry
- play_arrow Inband Flow Analyzer 2.0
- play_arrow Juniper Resiliency Interface
-
- play_arrow Sampling and Discard Accounting Services
- play_arrow Sampling Data Using Traffic Sampling and Discard Accounting
- play_arrow Sampling Data Using Inline Sampling
- Understand Inline Active Flow Monitoring
- Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250
- Configuring Inline Active Flow Monitoring on MX80 and MX104 Routers
- Configuring Inline Active Flow Monitoring on PTX Series Routers
- Inline Active Flow Monitoring of MPLS-over-UDP Flows on PTX Series Routers
- Inline Active Flow Monitoring on IRB Interfaces
- Example: Configuring Inline Active Flow Monitoring on MX Series and T4000 Routers
- play_arrow Sampling Data Using Flow Aggregation
- Understanding Flow Aggregation
- Enabling Flow Aggregation
- Configuring Flow Aggregation on MX, M and T Series Routers and NFX250 to Use Version 5 or Version 8 cflowd
- Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9 Flow Templates
- Configuring Flow Aggregation on PTX Series Routers to Use Version 9 Flow Templates
- Configuring Inline Active Flow Monitoring to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series Switches, NFX Series Devices, and SRX Series Firewalls
- Configuring Flow Aggregation to Use IPFIX Flow Templates on PTX Series Routers
- Configuring Observation Domain ID and Source ID for Version 9 and IPFIX Flows
- Configuring Template ID and Options Template ID for Version 9 and IPFIX Flows
- Including Fragmentation Identifier and IPv6 Extension Header Elements in IPFIX Templates on MX Series Routers
- Directing Replicated Flows from M and T Series Routers to Multiple Flow Servers
- Logging cflowd Flows on M and T Series Routers Before Export
- Configuring Next-Hop Address Learning on MX Series and PTX Series Routers for Destinations Accessible Over Multiple Paths
-
- play_arrow Configuration Statements and Operational Commands
Example: Configuring TWAMP Client and Server on MX Series Routers
This example shows how to configure the TWAMP client and server and contains the following sections.
Requirements
This example uses the following hardware and software components:
MX Series routers.
Junos OS Release 15.1 or later.
Overview
This example explains the Two-Way Active Measurement Protocol (TWAMP). TWAMP is an open protocol for measuring network performance between any two devices supporting the TWAMP protocol. The TWAMP-Control protocol is used to set up performance measurement sessions. The TWAMP-Test protocol is used to send and receive performance measurement probes.
The TWAMP architecture is composed of the following entities that are responsible for starting a monitoring session and exchanging packets:
The control client initiates all requested test sessions with a start sessions message, and the server acknowledges. When necessary, the control client sends a message to stop all test sessions.
The session sender and the session reflector exchange test packets according to the TWAMP-Test protocol for each active session. On receiving a TWAMP-Test packet, the session reflector only reflects a measurement packet and does not collect packet statistics in TWAMP.
The TWAMP server is an end system that manages one or more TWAMP sessions and is also capable of configuring per-session ports. The server listens on the TCP port. The session reflector and server make up the TWAMP responder in an IP service-level agreement operation.
For 15.1, both the control client and session sender would be residing on the same Juniper router. The client design does not mandate the server and the session reflector to be on the same system. Hence the Juniper TWAMP client will also be capable of working with a third-party server implementation.
Configuration for TWAMP client
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI, at the [edit] hierarchy level, of SG1 router.
Configuring Chassis
set chassis fpc 4 pic 1 inline-services bandwidth 1g
Configuring Interfaces
set interfaces si-4/1/0 unit 0 family inet set interfaces si-4/1/0 unit 10 rpm twamp-client set interfaces si-4/1/0 unit 10 family inet address 10.60.60.1/32
Configuring Services
set services rpm twamp client control-connection c1 destination-interface si-4/1/0.10 set services rpm twamp client control-connection c1 history-size 500 set services rpm twamp client control-connection c1 target-address 10.70.70.1 set services rpm twamp client control-connection c1 test-count 1 set services rpm twamp client control-connection c1 test-interval 1 set services rpm twamp client control-connection c1 traps test-iteration-done set services rpm twamp client control-connection c1 traps control-connection-closed set services rpm twamp client control-connection c1 test-session t1 target-address 10.70.70.1 set services rpm twamp client control-connection c1 test-session t1 data-fill-with-zeros set services rpm twamp client control-connection c1 test-session t1 data-size 1400 set services rpm twamp client control-connection c1 test-session t1 probe-count 55 set services rpm twamp client control-connection c1 test-session t1 probe-interval 1
Configuring TWAMP client
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy.
Configure the chassis.
content_copy zoom_out_map[edit chassis] user@router1# set fpc 4 pic 1 inline-services bandwidth 1g
Configure the interfaces.
content_copy zoom_out_map[edit interfaces] user@router1# set si-4/1/0 unit 0 family inet user@router1# set si-4/1/0 unit 10 rpm twamp-client user@router1# set si-4/1/0 unit 10 family inet address 10.60.60.1/32
Configure the services.
content_copy zoom_out_map[edit services] user@router1# set rpm twamp client control-connection c1 destination-interface si-4/1/0.10 user@router1# set rpm twamp client control-connection c1 history-size 500 user@router1# set rpm twamp client control-connection c1 target-address 10.70.70.1 user@router1# set rpm twamp client control-connection c1 test-count 1 user@router1# set rpm twamp client control-connection c1 test-interval 1 user@router1# set rpm twamp client control-connection c1 traps test-iteration-done user@router1# set rpm twamp client control-connection c1 traps control-connection-closed user@router1# set rpm twamp client control-connection c1 test-session t1 target-address 10.70.70.1 user@router1# set rpm twamp client control-connection c1 test-session t1 data-fill-with-zeros user@router1# set rpm twamp client control-connection c1 test-session t1 data-size 1400 user@router1# set rpm twamp client control-connection c1 test-session t1 probe-count 55 user@router1# set rpm twamp client control-connection c1 test-session t1 probe-interval 1
Results
From the configuration mode of Router 1, confirm your configuration by
entering the show chassis, show
interfaces, and show services rpm twamp commands.
If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.
user@router1# show chassis
fpc 4 {
pic 1 {
inline-services {
bandwidth 1g;
}
}
}
user@router1# show interfaces
si-4/1/0 {
unit 0 {
family inet;
}
unit 10 {
rpm twamp-client;
family inet {
address 10.60.60.1/32;
}
}
}
user@router1# show services rpm twamp
client {
control-connection c1 {
destination-interface si-4/1/0.10;
history-size 500;
target-address 10.70.70.1;
test-count 1;
test-interval 1;
traps {
test-iteration-done;
control-connection-closed;
}
test-session t1 {
target-address 10.70.70.1;
data-fill-with-zeros;
data-size 1400;
probe-count 55;
probe-interval 1;
}
}
}
Configuration for TWAMP server
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI, at the [edit] hierarchy level, of SG1 router.
Configuring Chassis
set chassis fpc 2 pic 1 inline-services bandwidth 1g
Configuring Interfaces
set interfaces si-2/1/0 unit 0 family inet set interfaces si-2/1/0 unit 10 rpm twamp-server set interfaces si-2/1/0 unit 10 family inet address 10.70.70.1/32
Configuring Services
set services rpm twamp server authentication-mode none set services rpm twamp server port 862 set services rpm twamp server client-list Client1 address 10.60.60.1/32
Configuring TWAMP server
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy.
Configure the chassis.
content_copy zoom_out_map[edit chassis] user@router1# set fpc 2 pic 1 inline-services bandwidth 1g
Configure the interfaces.
content_copy zoom_out_map[edit interfaces] user@router1#set si-2/1/0 unit 0 family inet user@router1#set si-2/1/0 unit 10 rpm twamp-server user@router1#set si-2/1/0 unit 10 family inet address 10.70.70.1/32
Configure the services.
content_copy zoom_out_map[edit services] user@router1# set rpm twamp server authentication-mode none user@router1# set rpm twamp server port 862 user@router1# set rpm twamp server client-list Client1 address 10.60.60.1/32
Results
From the configuration mode of Router 1, confirm your configuration by
entering the show chassis, show
interfaces, and show services rpm twamp server
commands. If the output does not display the intended configuration, repeat
the instructions in this example to correct the configuration.
user@router1# show chassis
fpc 2 {
pic 1 {
inline-services {
bandwidth 1g;
}
}
}
user@router1# show interfaces
si-2/1/0 {
unit 0 {
family inet;
}
unit 10 {
rpm twamp-server;
family inet {
address 10.70.70.1/32;
}
}
}
user@router1# show services rpm twamp server
authentication-mode none;
port 862;
client-list Client1 {
address {
10.60.60.1/32;
}
}
Verification
Verifying TWAMP server sessions
Purpose
Verify that the TWAMP server sessions are established.
Action
From operational mode, enter the show services rpm twamp server
session command.
user@router1> show services rpm twamp server session
Session Connection Sender Sender Reflector Reflector
ID ID address port address port
4 44 10.1.1.1 12345 192.168.219.203 890
78 44 10.22.1.55 345 10.22.2.2 89022
234 423 192.168.219.203 2345 10.2.22.2 3333
5 423 10.4.1.1 82345 10.2.2.2 45909
1 423 192.168.1.1 645 10.32.2.2 2394
Verifying TWAMP client sessions
Purpose
Verify that the TWAMP client sessions are established.
Action
From operational mode, enter the show services rpm twamp client
session command.
user@router1> show services rpm twamp client session
Connection Session Sender Sender Reflector Reflector
Name Name address port address port
c2 t1 10.60.60.1 10008 10.70.70.1 10008
