- 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 an RFC 2544-Based Benchmarking Test for NNI Direction of Ethernet Pseudowires
This example shows how to configure the benchmarking test for a network-to-network interface (NNI) direction of an Ethernet pseudowire service.
Requirements
This example uses the following hardware and software components:
An ACX Series router
Junos OS Release 12.3X52 or later
Overview
Consider a sample topology in which a router, Router A, functions as an initiator and terminator of the test frames for an RFC 2544-based benchmarking test. Router A operates as a provider edge device, PE1, which is connected to a customer edge device, CE1, on one side and over an Ethernet pseudowire to another router, Router B, which functions as a reflector to reflect back the test frames it receives from Router A. Router B operates as a provider edge device, PE2, which is the remote router located at the other side of the service provider core. The UNI direction of CE1 is connected to the NNI direction of PE1. An MPLS tunnel connects PE1 and PE2 over the Ethernet pseudowire or the Ethernet line (E-LINE).
This benchmarking test is used to compute the performance attributes in the network-to-network interface (NNI) direction of an Ethernet pseudowire service between Router A and Router B. The logical interface under test on Router A is the CE1 interface with UNI as the direction, and the logical interface under test on Router B is the CE2 interface with NNI as the direction. Data traffic arriving from UNI towards NNI is ignored while the test is in progress. Packets from NNI are not sent toward the customer edge because all packets are assumed to be test frames. The CCC family and NNI direction are configured on routers A and B.
Figure 1 shows the sample topology to perform an RFC 2544 test for the NNI direction of an Ethernet pseudowire service.
Configuration
In this example, you configure the benchmarking test for the NNI direction of an Ethernet pseudowire service that is enabled between two routers to detect and analyze the performance of the interconnecting routers.
- CLI Quick Configuration
- Configuring Benchmarking Test Parameters on Router B
- Configuring Benchmarking Test Parameters on Router B
- Results
CLI Quick Configuration
To quickly configure this example, copy the
following commands, paste them in 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:
Configuring Benchmarking Test Parameters on Router A
set interfaces ge-0/0/0 vlan-tagging set interfaces ge-0/0/0 unit 0 encapsulation vlan-ccc set interfaces ge-0/0/0 unit 0 vlan-id 101 set services rpm rfc2544-benchmarking profiles test-profile throughput test-type throughput set services rpm rfc2544-benchmarking profiles test-profile throughput packet-size 64 set services rpm rfc2544-benchmarking profiles test-profile throughput test-duration 20 set services rpm rfc2544-benchmarking profiles test-profile throughput bandwidth-kbps 500 set services rpm rfc2544-benchmarking tests test-name test1 interface ge-0/0/0.1 set services rpm rfc2544-benchmarking tests test-name test1 test-profile throughput set services rpm rfc2544-benchmarking tests test-name test1 mode initiate-and-terminate set services rpm rfc2544-benchmarking tests test-name test1 family ccc set services rpm rfc2544-benchmarking tests test-name test1 direction nni
Configuring Benchmarking Test Parameters on Router B
set interfaces ge-0/0/4 vlan-tagging set interfaces ge-0/0/4 unit 0 encapsulation vlan-ccc set interfaces ge-0/0/4 unit 0 vlan-id 101 set services rpm rfc2544-benchmarking tests test-name test1 interface ge-0/0/4.1 set services rpm rfc2544-benchmarking tests test-name test1 mode reflect set services rpm rfc2544-benchmarking tests test-name test1 reflector-port 25 set services rpm rfc2544-benchmarking tests test-name test1 mode family ccc set services rpm rfc2544-benchmarking tests test-name test1 direction uni
Configuring Benchmarking Test Parameters on Router B
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode.
To configure the test parameters on Router A:
In configuration mode, go to the
[edit interfaces]hierarchy level:content_copy zoom_out_map[edit] user@host# edit interfaces
Configure the interface on which the test must be run.
content_copy zoom_out_map[edit interfaces] user@host# edit ge-0/0/0
Configure VLAN tagging for transmission and reception of 802.1Q VLAN-tagged frames.
content_copy zoom_out_map[edit interfaces ge-0/0/0] user@host# set vlan-tagging
Configure a logical unit for the interface.
content_copy zoom_out_map[edit interfaces ge-0/0/0] user@host# edit unit 0
Specify the encapsulation for Ethernet VLAN circuits.
content_copy zoom_out_map[edit interfaces ge-0/0/0 unit 0] user@host# set encapsulation vlan-ccc
Configure the VLAN ID on the logical interface.
content_copy zoom_out_map[edit interfaces ge-0/0/0 unit 0] user@host# set vlan-id 101
Go to the top level of the configuration command mode.
content_copy zoom_out_map[edit interfaces ge-0/0/0 unit 0] user@host# top
In configuration mode, go to the
[edit services]hierarchy level.content_copy zoom_out_map[edit] user@host# edit services
Configure a real-time performance monitoring service (RPM) instance.
content_copy zoom_out_map[edit services] user@host# edit rpm
Configure an RFC 2544-based benchmarking test for the RPM instance.
content_copy zoom_out_map[edit services rpm] user@host# edit rfc2544-benchmarking
Define a name for a test profile—for example, throughput.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking] user@host# edit profiles test-profile throughput
Configure the type of test to be performed as throughput.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile throughput] user@host# set test-type throughput
Specify the size of the test packet as 64 bytes.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile throughput] user@host# set test-type packet-size 64
Specify the period—for example, 20 minutes—for which the test is to be performed in hours, minutes, or seconds by specifying a number followed by the letter h (for hours), m (for minutes), or s (for seconds).
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile throughput] user@host# set test-type test-duration 20m
Define the theoretical maximum bandwidth for the test in kilobits per second, with a value from 1 Kbps through 1,000,000 Kbps.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile throughput] user@host# set test-type bandwidth-kbps 500
Enter the
upcommand to go the previous level in the configuration hierarchy.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile throughput] user@host# up
Enter the
upcommand to go the previous level in the configuration hierarchy.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles] user@host# up
Define a name for the test—for example, test1. The test name identifier can be up to 32 characters in length.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking] user@host# edit tests test-name test1
Specify the name of the test profile—for example, throughput—to be associated with a particular test name.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test1] user@host# set test-profile throughput
Specify the logical interface, ge-0/0/0.1, on which the RFC 2544-based benchmarking test is run.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test1] user@host# set test-interface ge-0/0/0.1
Specify the test mode for the packets that are sent during the benchmarking test as initiation and termination.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test1] user@host# set mode initiate-and-terminate
Configure the address type family,
ccc, for the benchmarking test.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test1] user@host# set family ccc
Specify the direction of the interface on which the test must be run, which is NNI in this example.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test1] user@host# set direction nni
Configuring Benchmarking Test Parameters on Router B
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode.
To configure the test parameters on Router B:
In configuration mode, go to the
[edit interfaces]hierarchy level:content_copy zoom_out_map[edit] user@host# edit interfaces
Configure the interface on which the test must be run.
content_copy zoom_out_map[edit interfaces] user@host# edit ge-0/0/4
Configure VLAN tagging for transmission and reception of 802.1Q VLAN-tagged frames.
content_copy zoom_out_map[edit interfaces ge-0/0/4] user@host# set vlan-tagging
Configure a logical unit for the interface.
content_copy zoom_out_map[edit interfaces ge-0/0/4] user@host# edit unit 0
Specify the encapsulation for Ethernet VLAN circuits.
content_copy zoom_out_map[edit interfaces ge-0/0/4 unit 0] user@host# set encapsulation vlan-ccc
Configure the VLAN ID on the logical interface.
content_copy zoom_out_map[edit interfaces ge-0/0/4 unit 0] user@host# set vlan-id 101
Go to the top level of the configuration command mode.
content_copy zoom_out_map[edit interfaces ge-0/0/4 unit 0] user@host# top
In configuration mode, go to the
[edit services]hierarchy level.content_copy zoom_out_map[edit] user@host# edit services
Configure a real-time performance monitoring service (RPM) instance.
content_copy zoom_out_map[edit services] user@host# edit rpm
Configure an RFC 2544-based benchmarking test for the RPM instance.
content_copy zoom_out_map[edit services rpm] user@host# edit rfc2544-benchmarking
Define a name for the test—for example, test1. The test name identifier can be up to 32 characters in length.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking] user@host# edit tests test-name test1
Specify the logical interface, ge-0/0/4.1, on which the RFC 2544-based benchmarking test is run.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test1] user@host# set test-interface ge-0/0/4.1
Specify
reflectas the test mode for the packets that are sent during the benchmarking test.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test1] user@host# set mode reflect
Configure the address type family,
ccc, for the benchmarking test.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test1] user@host# set family ccc
Specify the direction of the interface on which the test must be run, which is NNI in this example.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test1] user@host# set direction nni
Results
In configuration mode, confirm your configuration on
Router A and Router B by entering the show command. If
the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
Configuring Benchmarking Test Parameters on Router A:
[edit interfaces]
ge-0/0/0 {
vlan-tagging;
unit 0 {
encapsulation vlan-ccc;
vlan-id 101;
}
}
[edit services rpm]
rfc2544-benchmarking {
profiles {
test-profile throughput {
test-type throughput
packet-size 64;
test-duration 20m;
bandwidth-kbps 500;
}
}
tests {
test-name test1 {
interface ge-0/0/0.1;
test-profile throughput;
mode initiate-and-terminate;
family ccc;
direction nni;
}
}
}
Configuring Benchmarking Test Parameters on Router B:
[edit interfaces]
ge-0/0/4 {
vlan-tagging;
unit 0 {
encapsulation vlan-ccc;
vlan-id 101;
}
}
[edit services rpm]
rfc2544-benchmarking {
# Note, When in reflector mode, test profile is not needed
tests {
test-name test1 {
interface ge-0/0/4.1;
mode reflect;
family ccc;
direction nni;
}
}
}
After you have configured the device, enter the commit command in configuration mode.
Verifying the Results of the Benchmarking Test for NNI Direction of an Ethernet Pseudowire Service
Examine the results of the benchmarking test that is performed on the configured service between Router A and Router B.
Verifying the Benchmarking Test Results
Purpose
Verify that the necessary and desired statistical values are displayed for the benchmarking test that is run on the configured service between Router A and Router B.
Action
In operational mode, enter the run show services
rpm rfc2544-benchmarking (aborted-tests | active-tests | completed-tests
| summary) command to display information about the results
of each category or state of the RFC 2544-based benchmarking test,
such as terminated tests, active tests, and completed tests, for each
real-time performance monitoring (RPM) instance.
Meaning
The output displays the details of the benchmarking
test that was performed. For more information about the run show
services rpm rfc2544-benchmarking operational command, see show services rpm rfc2544-benchmarking in the CLI Explorer.
