- 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 RFC2544-Based Benchmarking Tests on an MX104 Router for Layer 2 E-LAN Services in Bridge Domains
This example shows how to configure benchmarking tests for the Layer 2 E-LAN services in bridge domains. The example covers the four basic tests: throughput, frame-loss, back-to-back, and latency.
Requirements
MX Series routers support only the reflector function in RFC2544-based benchmarking tests. This example uses the MX104 3D Universal Edge Router as the reflector. You can also configure benchmarking tests on MX80 Series routers and MX240, MX480, and MX960 Series routers with MPC1, MPC2, and 16-port 10-gigabit Ethernet MPC from Junos OS Release 16.1 or later. To configure RFC2544-based benchmarking tests on MX240, MX480, MX960 Series routers, see Enabling Support for RFC 2544-Based Benchmarking Tests on MX Series Routers.
This example uses the following hardware and software components:
An MX104 (reflector)
An ACX Series router (initiator)
Junos OS Release 14.2 or later for MX Series routers
Overview
Consider a sample topology in which an ACX Series router functions as an initiator and terminator of the test frames for an RFC2544-based benchmarking test. ACX Series router is connected to a customer edge device CE1, on one side and is connected over a Layer 2 network to an MX104 Series router. The MX104 Series router functions as a reflector to reflect the test frames it receives from the ACX Series initiator back to the initiator. The MX04 Series router is also connected to a customer edge device CE2.
When Layer 2 reflection is enabled on an interface, filters are configured internally to block the ingress and egress traffic except test traffic through the test interface.
Figure 1 shows the sample topology to perform all four RFC2544-based benchmarking tests (throughput, back-to-back frames, latency, and frame-loss) for the UNI direction on a Layer 2 bridge network.
On the ACX Series router, ge-1/2/1.0 is the Layer 2 NNI interface and ge-1/1/3.0 is the Layer 2 UNI interface. On the MX104 Series router, ge-1/1/6.0 is the Layer 2 NNI interface and ge-1/1/5.0 is the Layer 2 UNI interface. The benchmarking tests are used to compute the performance attributes for an E-LAN service on a bridge domain.
Test packets can be identified using the destination MAC address, source MAC address, and test interface. Both tagged and untagged interfaces are supported. For tagged interfaces, the test interface is the VLAN sub interface. For untagged interfaces, the physical port represents the test interface. Traffic through other VLAN sub interfaces, present in the same physical port, is not affected when you configure the benchmarking test on one of the sub interfaces.
Configuration
In this example, you configure the benchmarking tests for the UNI direction for an E-LAN service on a Layer 2 bridge domain that is enabled between two routers to detect and analyze the performance of the interconnected routers. In this example, we start by configuring the ACX Series router. On the ACX Series router, you first configure each test by specifying the test profile, the test attributes, and then define the test by associating the test with the test profile with the relevant attributes. You can then configure the interface. On the MX104 Series router, you perform the same steps. However, a few attributes such as the outer VLAN ID, source UDP port, destination UDP port, the duration of each iteration, and their values are only applicable to the initiator or the ACX Series router.
When you configure the Layer 2 reflection, you can specify the service type under test as ELINE if you want to simulate an ELINE service using bridge encapsulation.
- CLI Quick Configuration
- Configuring Throughput Benchmarking Test Parameters on the ACX Series Router
- Configuring Back-to-Back Frames Benchmarking Test Parameters on the ACX Series Router
- Configuring Latency Benchmarking Test Parameters on the ACX Series Router
- Configuring Frame Loss Benchmarking Test Parameters on the ACX Series Router
- Configuring Other Benchmarking Test Parameters on the ACX Series Router
- Configuring Benchmarking Test Parameters on the MX104 Router
- Configuring Other Benchmarking Test Parameters on the MX104 Router
- 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 the ACX Series Router
set services rpm rfc2544-benchmarking profiles test-profile tput test-type throughput set services rpm rfc2544-benchmarking profiles test-profile tput packet-size 128 set services rpm rfc2544-benchmarking profiles test-profile tput bandwidth-kbps 900000 set services rpm rfc2544-benchmarking profiles test-profile b2bt test-type back-back-frames set services rpm rfc2544-benchmarking profiles test-profile b2bt packet-size 512 set services rpm rfc2544-benchmarking profiles test-profile b2bt bandwidth-kbps 950000 set services rpm rfc2544-benchmarking profiles test-profile lty test-type latency set services rpm rfc2544-benchmarking profiles test-profile lty packet-size 512 set services rpm rfc2544-benchmarking profiles test-profile lty bandwidth-kbps 1000000 set services rpm rfc2544-benchmarking profiles test-profile frloss test-type frame-loss set services rpm rfc2544-benchmarking profiles test-profile frloss packet-size 1600 set services rpm rfc2544-benchmarking profiles test-profile frloss bandwidth-kbps 1000000 set services rpm rfc2544-benchmarking tests test-name tput-test test-profile tput set services rpm rfc2544-benchmarking tests test-name tput-test source-mac-address 00:00:5e:00:53:11 set services rpm rfc2544-benchmarking tests test-name tput-test destination-mac-address 00:00:5e:00:53:22 set services rpm rfc2544-benchmarking tests test-name tput-test ovlan-id 400 set services rpm rfc2544-benchmarking tests test-name tput-test service-type elan set services rpm rfc2544-benchmarking tests test-name tput-test mode initiate-and-terminate set services rpm rfc2544-benchmarking tests test-name tput-test family bridge set services rpm rfc2544-benchmarking tests test-name tput-test direction egress set services rpm rfc2544-benchmarking tests test-name tput-test source-udp-port 200 set services rpm rfc2544-benchmarking tests test-name tput-test destination-udp-port 200 set services rpm rfc2544-benchmarking tests test-name tput-test test-iterator-duration 20 set services rpm rfc2544-benchmarking tests test-name tput-test test-interface ge-1/1/3.0 set services rpm rfc2544-benchmarking tests test-name b2b-test test-profile b2bt set services rpm rfc2544-benchmarking tests test-name b2b-test source-mac-address 00:00:5e:00:53:11 set services rpm rfc2544-benchmarking tests test-name b2b-test destination-mac-address 00:00:5e:00:53:22 set services rpm rfc2544-benchmarking tests test-name b2b-test ovlan-id 400 set services rpm rfc2544-benchmarking tests test-name b2b-test service-type elan set services rpm rfc2544-benchmarking tests test-name b2b-test mode initiate-and-terminate set services rpm rfc2544-benchmarking tests test-name b2b-test family bridge set services rpm rfc2544-benchmarking tests test-name b2b-test direction egress set services rpm rfc2544-benchmarking tests test-name b2b-test test-iterator-duration 20 set services rpm rfc2544-benchmarking tests test-name b2b-test test-interface ge-1/1/3.0 set services rpm rfc2544-benchmarking tests test-name lty-test test-profile lty set services rpm rfc2544-benchmarking tests test-name lty-test source-mac-address 00:00:5e:00:53:11 set services rpm rfc2544-benchmarking tests test-name lty-test destination-mac-address 00:00:5e:00:53:22 set services rpm rfc2544-benchmarking tests test-name lty-test ovlan-id 400 set services rpm rfc2544-benchmarking tests test-name lty-test service-type elan set services rpm rfc2544-benchmarking tests test-name lty-test mode initiate-and-terminate set services rpm rfc2544-benchmarking tests test-name lty-test family bridge set services rpm rfc2544-benchmarking tests test-name lty-test direction egress set services rpm rfc2544-benchmarking tests test-name lty-test source-udp-port 200 set services rpm rfc2544-benchmarking tests test-name lty-test destination-udp-port 200 set services rpm rfc2544-benchmarking tests test-name lty-test test-iterator-duration 20 set services rpm rfc2544-benchmarking tests test-name lty-test test-interface ge-1/1/3.0 set services rpm rfc2544-benchmarking tests test-name frloss-test test-profile frloss set services rpm rfc2544-benchmarking tests test-name frloss-test source-mac-address 00:00:5e:00:53:11 set services rpm rfc2544-benchmarking tests test-name frloss-test destination-mac-address 00:00:5e:00:53:22 set services rpm rfc2544-benchmarking tests test-name frloss-test ovlan-id 400 set services rpm rfc2544-benchmarking tests test-name frloss-test service-type elan set services rpm rfc2544-benchmarking tests test-name frloss-test mode initiate-and-terminate set services rpm rfc2544-benchmarking tests test-name frloss-test family bridge set services rpm rfc2544-benchmarking tests test-name frloss-test direction egress set services rpm rfc2544-benchmarking tests test-name frloss-test source-udp-port 200 set services rpm rfc2544-benchmarking tests test-name frloss-test destination-udp-port 200 set services rpm rfc2544-benchmarking tests test-name frloss-test test-iterator-duration 20 set services rpm rfc2544-benchmarking tests test-name frloss-test test-interface ge-1/1/3.0 set interfaces ge-1/2/1 flexible-vlan-tagging set interfaces ge-1/2/1 mtu 9192 set interfaces ge-1/2/1 encapsulation flexible-ethernet-services set interfaces ge-1/2/1 unit 0 encapsulation vlan-bridge set interfaces ge-1/2/1 unit 0 vlan-id 400 set interfaces ge-1/1/3 flexible-vlan-tagging set interfaces ge-1/1/3 mtu 9192 set interfaces ge-1/1/3 encapsulation flexible-ethernet-services set interfaces ge-1/1/3 unit 0 encapsulation vlan-bridge set interfaces ge-1/1/3 unit 0 vlan-id 400 set bridge-domains bd1 vlan-id 600 set bridge-domains bd1 interface ge-1/2/1.0 set bridge-domains bd1 interface ge-1/1/3.0
Configuring Benchmarking Test Parameters on the MX104 Router
set services rpm rfc2544-benchmarking tests test-name l2b-reflector source-mac-address 00:00:5e:00:53:11 set services rpm rfc2544-benchmarking tests test-name l2b-reflector destination-mac-address 00:00:5e:00:53:22 set services rpm rfc2544-benchmarking tests test-name l2b-reflector service-type elan set services rpm rfc2544-benchmarking tests test-name l2b-reflector mode reflect set services rpm rfc2544-benchmarking tests test-name l2b-reflector family bridge set services rpm rfc2544-benchmarking tests test-name l2b-reflector direction egress set services rpm rfc2544-benchmarking tests test-name l2b-reflector test-interface ge-1/1/5.0 set interfaces ge-1/1/6 flexible-vlan-tagging set interfaces ge-1/1/6 mtu 9192 set interfaces ge-1/1/6 encapsulation flexible-ethernet-services set interfaces ge-1/1/6 unit 0 encapsulation vlan-bridge set interfaces ge-1/1/6 unit 0 vlan-id 400 set interfaces ge-1/1/5 flexible-vlan-tagging set interfaces ge-1/1/5 mtu 9192 set interfaces ge-1/1/5 encapsulation flexible-ethernet-services set interfaces ge-1/1/5 unit 0 encapsulation vlan-bridge set interfaces ge-1/1/5 unit 0 vlan-id 400 set bridge-domains bd1 domain-type bridge set bridge-domains bd1 vlan-id 500 set bridge-domains bd1 interface ge-1/1/6.0 set bridge-domains bd1 interface ge-1/1/5.0
Configuring Throughput Benchmarking Test Parameters on the ACX Series Router
Step-by-Step Procedure
The following configuration requires you to configure a test profile for the throughput test and reference the test-profile in a unique test-name. The test-name defines the parameters for the throughput test to be performed on the ACX Series router.
To configure the throughput test parameters on the ACX Series router:
In configuration mode, at the [
edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.content_copy zoom_out_map[edit] user@host# edit services rpm rfc2544-benchmarking
Define a name for the first test profile—for example,
tputfor the throughput test profile.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking] user@host# set profiles test-profile tput
Configure the type of test to be performed as throughput, specify the packet size as 128 bytes, and define the theoretical maximum bandwidth for the test in kilobits per second (Kbps), with a value from 1 Kbps through 1,000,000 Kbps.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile tput] user@host# set test-type throughput packet-size 128 bandwidth-kbps 900000
Enter the
upcommand twice to go to the [edit services rpm rfc2544-benchmarking] level in the configuration hierarchy.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile tput ] user@host# up user@host# up
Define a name for the throughput test—for example,
tput-test. The test name can be up to 32 characters in length.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking ] user@host# set tests test-name tput-test
Specify the name of the test profile,
tput, to be associated with the test name.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name tput-test] user@host# set test-profile tput
Configure the source and destination MAC address for the test packet.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name tput-test] user@host# set source-mac-address 00:00:5e:00:53:11 destination-mac-address 00:00:5e:00:53:22
Configure the outer VLAN ID for the test frames and specify the service type under test to be E-LAN.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name tput-test] user@host# set ovlan-id 400 service-type elan
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 tput-test] user@host# set mode initiate-and-terminate
Configure the family type,
bridge, for the benchmarking test and specify the direction, egress. Also, specify the source and destination UDP port to be used in the UDP headers of the test packet.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name tput-test] user@host# set family bridge direction egress source-udp-port 200 destination-udp-port 200
Specify the duration of each iteration in seconds, with a value from 10 seconds to 1,728,000 seconds, and specify the logical interface, ge-0/2/1.0, on which the RFC2544-benchmarking tests are run.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name tput-test] user@host# set test-iterator-duration 20 test-interface ge-1/1/3.0
Configuring Back-to-Back Frames Benchmarking Test Parameters on the ACX Series Router
Step-by-Step Procedure
The following configuration requires you to configure a test profile for the back to back frames test and reference the test-profile in a unique test-name. The test-name defines the parameters for the back to back frames test to be performed on the ACX Series router.
To configure the back-to-back frames test parameters on the ACX Series router:
In configuration mode, at the [
edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.content_copy zoom_out_map[edit] user@host# edit services rpm rfc2544-benchmarking
Define a name for the back-to-back test profile—for example,
b2bt.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking] user@host# set profiles test-profile b2bt
Configure the type of test to be performed as back-to-back frames, specify the packet size as 128 bytes, and 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 b2bt] user@host# set test-type back-toback-frames packet-size 4444 bandwidth-kbps 950000
Enter the
upcommand twice to go to the [edit services rpm rfc2544-benchmarking] level in the configuration hierarchy.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile b2bt ] user@host# up user@host# up
Define a name for the back-to-back frames test—for example,
b2bt-test. The test name can be up to 32 characters in length.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking ] user@host# set tests test-name b2bt-test
Specify the name of the test profile,
b2bt, to be associated with the test name.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name b2bt-test] user@host# set test-profile b2bt
Configure the source and destination MAC address for the test packet.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name b2bt-test] user@host# set source-mac-address 00:00:5e:00:53:11 destination-mac-address 00:00:5e:00:53:22
Configure the outer VLAN ID for the test frames and specify the service type under test.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name b2bt-test] user@host# set ovlan-id 400 service-type elan
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 b2bt-test] user@host# set mode initiate-and-terminate
Configure the family type,
bridge, for the benchmarking test and specify the direction, egress.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name b2bt-test] user@host# set family bridge direction egress
Specify the duration of each iteration in seconds, with a value from 10 seconds to 1,728,000 seconds. Also, specify the logical interface, ge-0/2/1.0, on which the RFC2544-based benchmarking test is run.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name b2bt-test] user@host# set test-iterator-duration 20 test-interface ge-1/1/3.0
Configuring Latency Benchmarking Test Parameters on the ACX Series Router
Step-by-Step Procedure
The following configuration requires you to configure a test profile for the latency test and reference the test-profile in a unique test-name. The test-name defines the parameters for the latency test to be performed on the ACX Series router.
To configure the latency test parameters on the ACX Series router:
In configuration mode, at the [
edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.content_copy zoom_out_map[edit] user@host# edit services rpm rfc2544-benchmarking
Define a name for the latency test profile—for example,
lty.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking] user@host# set profiles test-profile lty
Configure the type of test to be performed as latency, specify the packet size of the test packet, and define the maximum bandwidth for the test in kilobits per second, with a value form 1 Kbps through 1,000,000 Kbps.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles] user@host# set test-profile lty test-type latency packet-size 512 bandwidth-kbps 1000000
Enter the
upcommand twice to go to the previous level in the configuration hierarchy.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile lty] user@host# up user@host# up
Define a name for the latency test—for example,
lty-test. The test name can be up to 32 characters in length.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking ] user@host# set tests test-name lty-test
Specify the name of the test profile,
lty, to be associated with the test name.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name lty-test] user@host# set test-profile lty
Configure the source and destination MAC address for the test packet.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name lty-test] user@host# set source-mac-address 00:00:5e:00:53:11 destination-mac-address 00:00:5e:00:53:22
Configure the outer VLAN ID for the test frames and specify the service type under test.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name lty-test] user@host# set ovlan-id 400 service-type elan
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 lty-test] user@host# set mode initiate-and-terminate
Configure the family type,
bridge, for the benchmarking test and specify the direction, egress. Also, specify the source and destination UDP port to be used in the UDP headers of the test packet.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name lty-test] user@host# set family bridge direction egress source-udp-port 200 destination-udp-port 200
Specify the duration of each iteration in seconds, with a value from 10 seconds to 1,728,000 seconds. Also, specify the logical interface, ge-0/2/1.0, on which the RFC2544-based benchmarking test is run.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name lty-test] user@host# set test-iterator-duration 20 test-interface ge-1/1/3.0
Configuring Frame Loss Benchmarking Test Parameters on the ACX Series Router
Step-by-Step Procedure
The following configuration requires you to configure a test profile for the frame loss test and reference the test-profile in a unique test-name. The test-name defines the parameters for the frame loss test to be performed on the ACX Series router.
To configure the frame loss test parameters on the ACX Series router:
In configuration mode, at the [
edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.content_copy zoom_out_map[edit] user@host# edit services rpm rfc2544-benchmarking
Define a name for the frame loss test profile—for example,
frloss.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking] user@host# set profiles test-profile frloss
Configure the type of test performed as frame loss, specify the packet size of the test packet, and define the 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] user@host# set test-profile frloss test-type frame-loss packet-size 1600 bandwidth-kbps 1000000
Enter the
upcommand to go to 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 frame loss test—for example,
frloss-test. The test name can be up to 32 characters in length.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking ] user@host# set tests test-name frloss-test
Specify the name of the test profile,
frloss, to be associated with the test name.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name frloss-test] user@host# set test-profile frloss
Configure the source and destination MAC address for the test packet.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name frloss-test] user@host# set source-mac-address 00:00:5e:00:53:11 destination-mac-address 00:00:5e:00:53:22
Configure the outer VLAN ID for the test frames and specify the service type under test.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name frloss-test] user@host# set ovlan-id 400 service-type elan
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 frloss-test] user@host# set mode initiate-and-terminate
Configure the family type,
bridge, for the benchmarking test and specify the direction, egress. Also, specify the source and destination UDP port to be used in the UDP headers of the test packet.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name frloss-test] user@host# set family bridge direction egress source-udp-port 200 destination-udp-port 200
Specify the duration of each iteration in seconds, with a value from 10 seconds to 1,728,000 seconds. Also, specify the logical interface, ge-0/2/1.0, on which the RFC2544-based benchmarking test is run.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name frloss-test] user@host# set test-iterator-duration 20 test-interface ge-1/1/3.0
Enter the
exitcommand to go to the [edit] hierarchy level.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name test4 ] user@host# exit
Configuring Other Benchmarking Test Parameters on the ACX Series Router
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 interface and bridge domain on the ACX Series router:
Configure the Layer 2 NNI interface on which the tests must be run from the [
edit] hierarchy level.content_copy zoom_out_map[edit] user@host# edit interfaces ge-1/2/1
Configure flexible VLAN tagging for the transmission of untagged frames or 802.1Q single-tagged and dual-tagged frames on the logical interface. You can also specify the maximum transmission unit (MTU) size for the interface and the encapsulation.
content_copy zoom_out_map[edit interfaces ge-1/2/1] user@host# set flexible-vlan-tagging mtu 9192 encapsulation flexible-ethernet-services
Configure a logical unit for the interface, specify the encapsulation, and configure the VLAN ID on the logical interfaces.
content_copy zoom_out_map[edit interfaces ge-1/2/1] user@host# set unit 0 encapsulation vlan-bridge vlan-id 400
Configure the Layer 2 UNI interface.
content_copy zoom_out_map[edit] user@host# edit interfaces ge-1/1/3
Configure flexible VLAN tagging for transmission of non-tagged frames or 802.1Q single-tag and dual-tag frames on the logical interface. You can also specify the maximum transmission unit (MTU) size for the interface and the encapsulation.
content_copy zoom_out_map[edit interfaces ge-1/1/3] user@host# set flexible-vlan-tagging mtu 9192 encapsulation flexible-ethernet-services
Configure a logical unit for the interface and specify the encapsulation and configure the VLAN ID on the logical interfaces.
content_copy zoom_out_map[edit interfaces ge-1/1/3] user@host# set unit 0 encapsulation vlan-bridge vlan-id 400
Configure the bridge domain, bd1, and specify the VLAN ID associated with the bridge domain and the associated interfaces from the [
edit] hierarchy level.content_copy zoom_out_map[edit] user@host# set bridge-domains bd1 vlan-id 600 interface ge-1/2/1.0 user@host# set bridge-domains bd1 vlan-id 600 intreface ge-1/1/3.0
Configuring Benchmarking Test Parameters on the MX104 Router
Step-by-Step Procedure
The following configuration requires you to configure a unique test-name for the benchmarking test on the MX104 Series router. The test-name defines the parameters for the benchmarking test to be performed. Because the test interface and test MAC addresses are the same, you can create a single test configuration at the reflector (MX104).
To configure the benchmarking test parameters on the MX104 Series router:
In configuration mode, at the [
edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.content_copy zoom_out_map[edit] user@host# edit services rpm rfc2544-benchmarking
Define a name for the test—for example,
l2b-reflector. The test name can be up to 32 characters in length.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking ] user@host# set tests test-name l2b-reflector
Specify the source and destination MAC addresses of the test packet.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking test-name l2b-reflector] user@host# set source-mac-address 00:00:5e:00:53:11 destination-mac-address 00:00:5e:00:53:22
Specify the service type under test and the mode, which is
reflect, at the reflector.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking test-name l2b-reflector] user@host# set service-type elan
Specify the mode which is reflect at the reflector.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking test-name l2b-reflector] user@host# set mode reflect
Configure the family type,
bridge, and specify the direction, egress, for the benchmarking test. Also, specify the logical interface, ge-1/1/5.0, on which the RFC2544-based benchmarking test is being run.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name l2b-reflector] user@host# set family bridge direction egress test-interface ge-1/1/5.0
Configuring Other Benchmarking Test Parameters on the MX104 Router
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 interface and bridge domain on the MX104 Series router:
Configure the Layer 2 NNI interface on which the tests must be run.
content_copy zoom_out_map[edit] user@host# edit interfaces ge-1/1/6
Configure flexible VLAN tagging for transmission of untagged frames or 802.1Q single-tagged and dual-tagged frames on the logical interface. You can also specify the maximum transmission unit (MTU) size for the interface and the encapsulation.
content_copy zoom_out_map[edit interfaces ge-1/1/6] user@host# set flexible-vlan-tagging mtu 9192 encapsulation flexible-ethernet-services
Configure a logical unit for the interface, specify the encapsulation, and configure the VLAN ID on the logical interface.
content_copy zoom_out_map[edit interfaces ge-1/1/6] user@host# set unit 0 encapsulation vlan-bridge vlan-id 400
Configure the Layer 2 NNI interface.
content_copy zoom_out_map[edit] user@host# edit interfaces ge-1/1/5
Configure flexible VLAN tagging for transmission of untagged frames or 802.1Q single-tagged and dual-tagged frames on the logical interface. You can also specify the maximum transmission unit (MTU) size for the interface and the encapsulation.
content_copy zoom_out_map[edit interfaces ge-1/1/5] user@host# set flexible-vlan-tagging mtu 9192 encapsulation flexible-ethernet-services
Configure a logical unit for the interface, specify the encapsulation, and configure the VLAN ID on the logical interfaces.
content_copy zoom_out_map[edit interfaces ge-1/1/5] user@host# set unit 0 encapsulation vlan-bridge vlan-id 400
Configure the bridge domain, bd1, and specify the VLAN ID associated with the bridge domain, and the associated interfaces from the [
edit] hierarchy level.content_copy zoom_out_map[edit] user@host# set bridge-domains bd1 vlan-id 500 interface ge-1/1/6.0 user@host# set bridge-domains bd1 vlan-id 500 interface ge-1/1/5.0
Start the benchmarking test on the reflector.
content_copy zoom_out_mapuser@host> test services rpm rfc2544-benchamrking test l2b-reflector start
After the test is successfully completed at the initiator, you can stop the test at the reflector by entering the
test services rpm rfc2544-benchmarking test l2b-reflector stopcommand.
Results
In configuration mode, confirm your configuration on
the ACX Series router and the MX104 Series router by entering the show command. If the output does not display the intended configuration,
repeat the configuration instructions in this example to correct it.
Benchmarking Test Parameters on the ACX Series router :
[edit interfaces]
ge-1/2/1 {
flexible-vlan-tagging;
mtu 9192;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 400;
}
}
ge-1/1/3 {
flexible-vlan-tagging;
mtu 9192;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 400;
}
}
[edit bridge-domains]
bd1 {
vlan-id 600;
interface ge-1/2/1.0;
interface ge-1/1/3.0;
}
[edit services rpm]
rfc2544-benchmarking {
profiles {
test-profile tput {
test-type throughput
packet-size 128;
bandwidth-kbps 900000;
}
test-profile b2bt {
test-type back-back-frames
packet-size 512;
bandwidth-kbps 950000;
}
test-profile lty {
test-type latency
packet-size 512;
bandwidth-kbps 100000;
}
test-profile frloss {
test-type frameloss
packet-size 1600;
bandwidth-kbps 1000000;
}
}
tests {
test-name tput-test {
interface ge-1/1/3.0;
test-profile tput;
mode initiate-and-terminate;
source-mac-address 00:00:5e:00:53:11;
destination-mac-address 00:00:5e:00:53:22;
ovlan-id 400;
service-type elan;
family bridge;
direction egress;
source-udp-port 200;
destination-udp-port 200;
test-iterator-duration 20;
}
test-name b2b-test {
interface ge-1/1/3.0;
test-profile b2bt;
mode initiate-and-terminate;
source-mac-address 00:00:5e:00:53:11;
destination-mac-address 00:00:5e:00:53:22;
ovlan-id 400;
service-type elan;
family bridge;
direction egress;
test-iterator-duration 20;
}
test-name lty-test {
interface ge-1/1/3.0;
test-profile lty;
mode initiate-and-terminate;
source-mac-address 00:00:5e:00:53:11;
destination-mac-address 00:00:5e:00:53:22;
ovlan-id 400;
service-type elan;
family bridge;
direction egress;
source-udp-port 200;
destination-udp-port 200;
test-iterator-duration 20;
}
test-name frloss-test {
interface ge-1/1/3.0;
test-profile frloss;
mode initiate-and-terminate;
source-mac-address 00:00:5e:00:53:11;
destination-mac-address 00:00:5e:00:53:22;
ovlan-id 400;
service-type elan;
family bridge;
direction egress;
source-udp-port 200;
destination-udp-port 200;
test-iterator-duration 20;
}
}
}Benchmarking Test Parameters on the MX104 Series router:
[edit interfaces]
ge-1/1/6 {
flexible-vlan-tagging;
mtu 9192;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 400;
}
}
ge-1/1/5 {
flexible-vlan-tagging;
mtu 9192;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 400;
}
}
}
[edit bridge-domains]
bd1 {
vlan-id 500;
interface ge-1/1/6.0;
interface ge-1/1/5.0;
}
[edit services rpm]
rfc2544-benchmarking {
# Note, When in reflector mode, test profile is not needed
tests {
test-name l2b-reflector {
interface ge-1/1/5.0;
source-mac-address 00:00:5e:00:53:11;
destination-mac-address 00:00:5e:00:53:22;
family bridge;
mode reflect;
service-type elan;
family bridge;
direction egress;
}
}
}
Verifying the Results of the Benchmarking Tests for Layer 2 Services (E-LAN) in Bridge Domains
Examine the results of the benchmarking tests that are performed on the configured service between the ACX Series router and the MX104 Series router. Start the test on the reflector first and then start the test on the initiator.
- Verifying the Throughput Benchmarking Test Results
- Verifying the Back-to-Back Benchmarking Test Results
- Verifying the Frame Loss Benchmarking Test Results
- Verifying the Latency Benchmarking Test Results
Verifying the Throughput Benchmarking Test Results
Purpose
Verify that the necessary and statistical values are displayed for the benchmarking tests that are run on the configured service between the ACX Series router and the MX104 Series router.
Action
In operational mode, enter the show services rpm
rfc2544-benchmarking test-id test-id-number detail command on the ACX Series router.
user@host> show services rpm rfc2544-benchmarking test-id 1 detail
Test information :
Test id: 1, Test name: tput_test, Test type: Throughput
Test mode: Initiate-and-Terminate
Test packet size: 128
Test state: TEST_STATE_COMPLETED
Status: Test-Completed
Test start time: 2014-09-24 22:21:09 PDT
Test finish time: 2014-09-24 22:21:33 PDT
Counters last cleared: Never
Test-profile Configuration:
Test-profile name: tput
Test packet size: 128
Theoretical max bandwidth : 900000 kbps
Test Configuration:
Test mode: Initiate-and-Terminate
Duration in seconds: 20
Test finish wait duration in seconds: 1
Test family: Bridge
Test iterator pass threshold: 0.50 %
Test receive failure threshold: 0.00 %
Test transmit failure threshold: 0.50 %
Bridge family Configuration:
Interface : ge-1/1/3.0
Test direction: Egress
Source mac address: 00:00:5e:00:53:11
Destination mac address: 00:00:5e:00:53:22
Outer vlan-id: 400
Outer vlan priority: 0
Outer vlan cfi: 0
Outer tag protocol id: 0x8100
Source ipv4 address: 192.168.1.10
Destination ipv4 address: 192.168.1.20
Source udp port: 200
Destination udp port: 200
Rfc2544 throughput test information :
Initial test load percentage : 100.00 %
Test iteration mode : Binary
Test iteration step : 50.00 %
Theoretical max bandwidth : 900000 kbps
Test packet size: 128
Iteration Internal Duration Elapsed -------- Throughput ---------
Overhead (sec) time Theoretical Transmit Measured
1 0 20 20 100.00 % 100.00 % 100.00 %
Result of the iteration runs : Throughput Test complete for packet size 128
Best iteration : 1, Best iteration (pps) : 760135
Best iteration throughput : 100.00 %
RFC2544 Throughput test results summary:
----------------------------------------
Packet Internal Theoretical Transmit Tx Rx Measured Measured
Size overhead rate (pps) pps Packets Packets throughput % bandwidth (kbps)
128 0 760135 760135 15202700 15202700 100.00 % 900000 In operational mode, enter the show services rpm rfc2544-benchmarking
test-id test-id-number detail command on
the MX104 Series router.
user@host> show services rpm rfc2544-benchmarking test-id 1 detail
Test information :
Test id: 1, Test name: l2b-reflector, Test type: Reflect
Test mode: Reflect
Test packet size: 0
Test state: TEST_STATE_RUNNING
Status: Running
Test start time: 2014-09-24 22:20:54 PDT
Test finish time: TEST_RUNNING
Counters last cleared: Never
Test Configuration:
Test mode: Reflect
Duration in seconds: 864000
Test finish wait duration in seconds: 1
Test family: Bridge
Test iterator pass threshold: 0.50 %
Test receive failure threshold: 0.00 %
Test transmit failure threshold: 0.50 %
Bridge family Configuration:
Interface : ge-1/1/5.0
Test direction: Egress
Source mac address: 00:00:5e:00:53:11
Destination mac address: 00:00:5e:00:53:22
Service type: Elan
Elapsed Reflected Reflected
time Packets Bytes
61 15202700 1945945600You can also use the show services rpm rfc2544-benchmarking
(aborted-test | active-tests | completed-tests | summary) command
to display information about the results of each category or state
of the RFC2544-based benchmarking 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.
Verifying the Back-to-Back Benchmarking Test Results
Purpose
Verify that the necessary and statistical values are displayed for the benchmarking tests that are run on the configured service between the ACX Series router and the MX104 Series router.
Action
In operational mode, enter the show services rpm
rfc2544-benchmarking test-id test-id-number detail command on the ACX Series router.
user@host> show services rpm rfc2544-benchmarking test-id 4 detail
Test information :
Test id: 4, Test name: b2b-test, Test type: Back-Back-Frames
Test mode: Initiate-and-Terminate
Test packet size: 128 512
Test state: TEST_STATE_COMPLETED
Status: Test-Completed
Test start time: 2014-09-24 22:30:16 PDT
Test finish time: 2014-09-24 22:31:03 PDT
Counters last cleared: Never
Test-profile Configuration:
Test-profile name: b2bt
Test packet size: 128 512
Theoretical max bandwidth : 950000 kbps
Test Configuration:
Test mode: Initiate-and-Terminate
Duration in seconds: 20
Test finish wait duration in seconds: 1
Test family: Bridge
Test iterator pass threshold: 0.50 %
Test receive failure threshold: 0.00 %
Test transmit failure threshold: 0.50 %
Bridge family Configuration:
Interface : ge-1/1/3.0
Test direction: Egress
Source mac address: 00:00:5e:00:53:11
Destination mac address: 00:00:5e:00:53:22
Outer vlan-id: 400
Outer vlan priority: 0
Outer vlan cfi: 0
Outer tag protocol id: 0x8100
Source ipv4 address: 192.168.1.10
Destination ipv4 address: 192.168.1.20
Source udp port: 4040
Destination udp port: 4041
Rfc2544 Back-Back test information :
Initial burst length: 20 seconds at 950000 kbps
Test iteration mode : Binary
Test iteration step : 50.00 %
Test packet size: 128
Iteration Theoretical Transmit Internal Duration Elapsed
burst length burst length overhead time
(packets) (packets)
1 16047280 16047280 0 20 20
Result of the iteration runs : Back-Back Test complete for packet size 128
Best iteration : 1
Measured burst (num sec) : 20 sec
Measured burst (num pkts) : 16047280 packets
Test packet size: 512
Iteration Theoretical Transmit Internal Duration Elapsed
burst length burst length overhead time
(packets) (packets)
1 4464280 4464280 0 20 20
Result of the iteration runs : Back-Back Test complete for packet size 512
Best iteration : 1
Measured burst (num sec) : 20 sec
Measured burst (num pkts) : 4464280 packets
RFC2544 Back-Back test results summary:
----------------------------------------
Packet Measured Burst Time
Size length (Packets) (seconds)
128 16047280 20
512 4464280 20 In operational mode, enter the show services rpm rfc2544-benchmarking
test-id test-id-number detail command on
the MX104 Series router.
user@host> show services rpm rfc2544-benchmarking test-id 4 detail
Test information :
Test id: 4, Test name: l2b-reflector, Test type: Reflect
Test mode: Reflect
Test packet size: 0
Test state: TEST_STATE_RUNNING
Status: Running
Test start time: 2014-09-24 22:30:07 PDT
Test finish time: TEST_RUNNING
Counters last cleared: Never
Test Configuration:
Test mode: Reflect
Duration in seconds: 864000
Test finish wait duration in seconds: 1
Test family: Bridge
Test iterator pass threshold: 0.50 %
Test receive failure threshold: 0.00 %
Test transmit failure threshold: 0.50 %
Bridge family Configuration:
Interface : ge-1/1/5.0
Test direction: Egress
Source mac address: 00:00:5e:00:53:11
Destination mac address: 00:00:5e:00:53:22
Service type: Elan
Elapsed Reflected Reflected
time Packets Bytes
58 20511560 4339763200You can also use the show services rpm rfc2544-benchmarking
(aborted-test | active-tests | completed-tests | summary) command
to display information about the results of each category or state
of the RFC2544-based benchmarking 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.
Verifying the Frame Loss Benchmarking Test Results
Purpose
Verify that the necessary and statistical values are displayed for the benchmarking tests that are run on the configured service between the ACX Series router and the MX104 Series router.
Action
In operational mode, enter the show services rpm
rfc2544-benchmarking test-id test-id-number detail command on the ACX Series router.
user@host> show services rpm rfc2544-benchmarking test-id 3 detail
Test information :
Test id: 3, Test name: frloss-test, Test type: Frame-Loss
Test mode: Initiate-and-Terminate
Test packet size: 1600
Test state: TEST_STATE_COMPLETED
Status: Test-Completed
Test start time: 2014-09-24 22:26:45 PDT
Test finish time: 2014-09-24 22:27:55 PDT
Counters last cleared: Never
Test-profile Configuration:
Test-profile name: frloss
Test packet size: 1600
Theoretical max bandwidth : 1000000 kbps
Test Configuration:
Test mode: Initiate-and-Terminate
Duration in seconds: 20
Test finish wait duration in seconds: 1
Test family: Bridge
Test iterator pass threshold: 0.50 %
Test receive failure threshold: 0.00 %
Test transmit failure threshold: 0.50 %
Bridge family Configuration:
Interface : ge-1/1/3.0
Test direction: Egress
Source mac address: 00:00:5e:00:53:11
Destination mac address: 00:00:5e:00:53:22
Outer vlan-id: 400
Outer vlan priority: 0
Outer vlan cfi: 0
Outer tag protocol id: 0x8100
Source ipv4 address: 192.168.1.10
Destination ipv4 address: 192.168.1.20
Source udp port: 200
Destination udp port: 200
Rfc2544 frame-loss test information :
Initial test load percentage : 100.00 %
Test iteration mode : step-down
Test iteration step : 10 %
Theoretical max bandwidth : 1000000 kbps
Test packet size: 1600
Iteration Internal Duration Elapsed -------- Throughput --------- Frame-loss
Overhead (sec) time Theoretical Transmit Measured rate %
1 0 20 20 100.00 % 100.00 % 100.00 % 0.00 %
2 0 20 20 100.00 % 100.00 % 100.00 % 0.00 %
3 0 20 20 100.00 % 100.00 % 100.00 % 0.00 %
Result of the iteration runs : Frame-loss test complete for packet size 1600
Percentage throughput transmitted: 100.00 %
Frame-loss rate (percent) : 0.00 %
RFC2544 Frame-loss test results summary:
----------------------------------------
Packet Internal Theoretical Transmit Transmit Tx Rx Frame Loss
Size overhead rate (pps) pps throughput Packets Packets rate percent
1600 0 77160 77160 100.00 % 1543200 1543200 0.00 % In operational mode, enter the show services rpm rfc2544-benchmarking
test-id test-id-number detail command on
the MX104 Series router.
user@host> show services rpm rfc2544-benchmarking test-id 3 detail
Test information :
Test id: 3, Test name: l2b-reflector, Test type: Reflect
Test mode: Reflect
Test packet size: 0
Test state: TEST_STATE_RUNNING
Status: Running
Test start time: 2014-09-24 22:25:36 PDT
Test finish time: TEST_RUNNING
Counters last cleared: Never
Test Configuration:
Test mode: Reflect
Duration in seconds: 864000
Test finish wait duration in seconds: 1
Test family: Bridge
Test iterator pass threshold: 0.50 %
Test receive failure threshold: 0.00 %
Test transmit failure threshold: 0.50 %
Bridge family Configuration:
Interface : ge-1/1/5.0
Test direction: Egress
Source mac address: 00:00:5e:00:53:11
Destination mac address: 00:00:5e:00:53:22
Service type: Elan
Elapsed Reflected Reflected
time Packets Bytes
95 1624361 2598977600You can also use the show services rpm rfc2544-benchmarking
(aborted-test | active-tests | completed-tests | summary) command
to display information about the results of each category or state
of the RFC2544-based benchmarking 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.
Verifying the Latency Benchmarking Test Results
Purpose
Verify that the necessary and statistical values are displayed for the benchmarking tests that are run on the configured service between the ACX Series router and the MX104 Series router.
Action
In operational mode, enter the show services rpm
rfc2544-benchmarking test-id test-id-number detail command on the ACX Series router.
user@host> show services rpm rfc2544-benchmarking test-id 5 detail
Test information :
Test id: 5, Test name: lty-test, Test type: Latency
Test mode: Initiate-and-Terminate
Test packet size: 512
Test state: TEST_STATE_COMPLETED
Status: Test-Completed
Test start time: 2014-09-24 22:33:05 PDT
Test finish time: 2014-09-24 22:40:46 PDT
Counters last cleared: Never
Test-profile Configuration:
Test-profile name: lty
Test packet size: 512
Theoretical max bandwidth : 1000000 kbps
Test Configuration:
Test mode: Initiate-and-Terminate
Duration in seconds: 20
Test finish wait duration in seconds: 1
Test family: Bridge
Test iterator pass threshold: 0.50 %
Test receive failure threshold: 0.00 %
Test transmit failure threshold: 0.50 %
Bridge family Configuration:
Interface : ge-1/1/3.0
Test direction: Egress
Source mac address: 00:00:5e:00:53:11
Destination mac address: 00:00:5e:00:53:22
Outer vlan-id: 400
Outer vlan priority: 0
Outer vlan cfi: 0
Outer tag protocol id: 0x8100
Source ipv4 address: 192.168.1.10
Destination ipv4 address: 192.168.1.20
Source udp port: 200
Destination udp port: 200
Rfc2544 latency test information :
Theoretical max bandwidth : 1000000 kbps
Initial test load percentage : 100.00 %
Duration in seconds: 20
Measurement unit for timestamp: Nanoseconds
Test packet size: 512
Iteration Duration Elapsed Theoretical Transmit Throughput ------------------ Latency --------------------
(sec) time rate (pps) pps percent Minimum Average Maximum Probe
1 20 20 234962 234962 100.00 % 44008 45253 47424 45096
2 20 20 234962 234962 100.00 % 44008 45237 47456 45256
3 20 20 234962 234962 100.00 % 43864 45198 46976 45144
4 20 20 234962 234962 100.00 % 43832 45243 47088 45096
5 20 20 234962 234962 100.00 % 44072 45261 46976 45176
6 20 20 234962 234962 100.00 % 43784 45214 46864 45032
7 20 20 234962 234962 100.00 % 44024 45259 47216 45240
8 20 20 234962 234962 100.00 % 44072 45290 46864 45192
9 20 20 234962 234962 100.00 % 43976 45272 46792 45208
10 20 20 234962 234962 100.00 % 44024 45206 46976 45112
11 20 20 234962 234962 100.00 % 44040 45198 47088 45176
12 20 20 234962 234962 100.00 % 44008 45223 46976 45160
13 20 20 234962 234962 100.00 % 44088 45257 47408 45176
14 20 20 234962 234962 100.00 % 43976 45183 46832 45080
15 20 20 234962 234962 100.00 % 44024 45198 47088 45112
16 20 20 234962 234962 100.00 % 43864 45206 46912 45208
17 20 20 234962 234962 100.00 % 44056 45209 46960 45176
18 20 20 234962 234962 100.00 % 44008 45198 46912 45112
19 20 20 234962 234962 100.00 % 43816 45175 47248 45000
20 20 20 234962 234962 100.00 % 43912 45202 46992 45192
Result of the iteration runs : Latency Test complete for packet size 512
Internal overhead per packet: 0
Avg (min) Latency : 43972
Avg (avg) latency : 45224
Avg (Max) latency : 47052
Avg (probe) latency : 45147
RFC2544 Latency test results summary:
----------------------------------------
Packet Internal Theoretical Transmit Tx Rx ------------------ Latency --------------------
Size overhead rate (pps) pps Packets Packets Minimum Average Maximum Probe
512 0 234962 234962 93984800 93984800 43972 45224 47052 45147
In operational mode, enter the show services rpm rfc2544-benchmarking
test-id test-id-number detail command on
the MX104 Series router.
user@host> show services rpm rfc2544-benchmarking test-id 5 detail
Test information :
Test id: 5, Test name: l2b-reflector, Test type: Reflect
Test mode: Reflect
Test packet size: 0
Test state: TEST_STATE_RUNNING
Status: Running
Test start time: 2014-09-24 22:32:55 PDT
Test finish time: TEST_RUNNING
Counters last cleared: Never
Test Configuration:
Test mode: Reflect
Duration in seconds: 864000
Test finish wait duration in seconds: 1
Test family: Bridge
Test iterator pass threshold: 0.50 %
Test receive failure threshold: 0.00 %
Test transmit failure threshold: 0.50 %
Bridge family Configuration:
Interface : ge-1/1/5.0
Test direction: Egress
Source mac address: 00:00:5e:00:53:11
Destination mac address: 00:00:5e:00:53:22
Service type: Elan
Elapsed Reflected Reflected
time Packets Bytes
426 84586320 43308195840
You can also use the show services rpm rfc2544-benchmarking
(aborted-test | active-tests | completed-tests | summary) command
to display information about the results of each category or state
of the RFC2544-based benchmarking 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 show services rpm rfc2544-benchmarking
operational mode command, see show services rpm
rfc2544-benchmarking topic in the CLI Explorer.
