- 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 Benchmarking Tests to Measure SLA Parameters for E-LAN Services on an MX104 Router Using VPLS
This example shows how to configure benchmarking tests for the E-LAN services using BGP-based VPLS. The example covers the four benchmarking tests: throughput, frame loss, back-to-back frames, and latency.
Requirements
MX Series routers support only the reflector function in RFC2544-based benchmarking tests.
This example uses the following hardware and software components:
An MX104 3D Universal Edge Router (reflector)
Any MX Series router
Any ACX Series router (initiator)
Junos OS Release 15.1 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. The ACX Series router is connected to a provider edge router, PE1 (an MX Series router). The PE1 router is configured with a VPLS routing instance and is connected over a Layer 2 network to another provider edge router, PE2 (an MX104 Series router). A simple VPLS network with BGP signaling is created between routers PE1 and PE2. The MX104 Series router also functions as a reflector to reflect the test frames it receives from the ACX Series router back to the initiator.
Benchmarking tests compute the performance attributes in the user-to-network interface (UNI) direction of the Layer 2 E-LAN service between the ACX Series router and the MX104 Series router. To measure SLA parameters for E-LAN services using VPLS, configure specific benchmarking tests. In this example, all four benchmarking tests (throughput, back-to-back frames, latency, and frame-loss) are configured.
Figure 1 shows the sample topology to perform all four RFC2544-based benchmarking tests for the UNI direction on a Layer 2 network using VPLS.
On the ACX Series router, ge-0/2/1.0 is the Layer 2 NNI interface and ge-0/2/0.0 is the Layer 2 UNI interface. For each benchmarking test configured on the ACX Series router, specify the source MAC address as 00:00:5e:00:53:11 and 00:00:5e:00:53:22 as the destination MAC address. Also, specify the VLAN ID as 512. On the MX Series router, ge-0/3/0.0 is the Layer 2 NNI interface and ge-0/2/1.0 is the UNI interface. On the MX104 Series router, ge-0/2/5.0 is the Layer 2 NNI interface and ge-0/3/1.0 is the Layer 2 UNI interface. The benchmarking tests are used to compute the performance attributes for an E-LAN service using VPLS.
Configuration
In this example, you configure the benchmarking tests for the UNI direction for a Layer 2 E-LAN service using VPLS between two routers (initiator and reflector) to detect and analyze the performance of the interconnected routers. The initiator and reflector routers are not directly connected to each other. The initiator is connected to a provider edge router (PE1), which is in turn connected to the reflector. In this example, the ACX Series router is the initiator, an MX Series router is PE1, and the MX104 router is the other provider edge router (PE2) and reflector. Start by configuring the initiator. On the ACX Series router, you first configure each test by specifying the test profile and 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 MX Series router, configure the VPLS parameters to enable VPLS on the router. On the MX104 Series router, configure the benchmarking parameters and the VPLS parameters.
When you configure Layer 2 reflection, you can specify the service type under test as ELINE if you want to simulate an Eline service by using bridge encapsulation.
- CLI Quick Configuration
- Configuring Throughput Benchmarking Test Parameters on the ACX Series Router (Initiator)
- 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 the VPLS Parameters on the MX Series Router (PE1)
- Configuring Benchmarking Test Parameters on the MX104 Router (Reflector)
- Configuring Other Benchmarking Test Parameters on the MX104 Router (Reflector)
- Configuring VPLS Parameters on the MX104 Router (Reflector)
- 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 (Initiator)
set services rpm rfc2544-benchmarking profiles test-profile tput test-type throughput set services rpm rfc2544-benchmarking profiles test-profile tput packet-size 256 set services rpm rfc2544-benchmarking profiles test-profile tput bandwidth-kbps 600000 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 9104 set services rpm rfc2544-benchmarking profiles test-profile b2bt bandwidth-kbps 600000 set services rpm rfc2544-benchmarking profiles test-profile lty test-type latency set services rpm rfc2544-benchmarking profiles test-profile lty packet-size 1024 set services rpm rfc2544-benchmarking profiles test-profile lty bandwidth-kbps 6000000 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 6000000 set services rpm rfc2544-benchmarking profiles test-profile frloss step-percent 5 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 512 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 400 set services rpm rfc2544-benchmarking tests test-name tput-test test-iterator-duration 250 set services rpm rfc2544-benchmarking tests test-name tput-test test-interface ge-0/2/0.0 set services rpm rfc2544-benchmarking tests test-name b2bt-test test-profile b2bt set services rpm rfc2544-benchmarking tests test-name b2bt-test source-mac-address 00:00:5e:00:53:11 set services rpm rfc2544-benchmarking tests test-name b2bt-test destination-mac-address 00:00:5e:00:53:22 set services rpm rfc2544-benchmarking tests test-name b2bt-test ovlan-id 512 set services rpm rfc2544-benchmarking tests test-name b2bt-test service-type elan set services rpm rfc2544-benchmarking tests test-name b2bt-test mode initiate-and-terminate set services rpm rfc2544-benchmarking tests test-name b2bt-test family bridge set services rpm rfc2544-benchmarking tests test-name b2bt-test direction egress set services rpm rfc2544-benchmarking tests test-name b2bt--test destination-udp-port 400 set services rpm rfc2544-benchmarking tests test-name b2bt-test test-iterator-duration 10 set services rpm rfc2544-benchmarking tests test-name b2b-test test-interface ge-0/2/0.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 512 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 400 set services rpm rfc2544-benchmarking tests test-name lty-test test-iterator-duration 10 set services rpm rfc2544-benchmarking tests test-name lty-test test-interface ge-0/2/0.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 512 set services rpm rfc2544-benchamrking tests test-name frloss-test ovlan-priority 7 set services rpm rfc2544-benchamrking tests test-name frloss-test ovlan-cfi 1 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 400 set services rpm rfc2544-benchmarking tests test-name frloss-test test-iterator-duration 30 set services rpm rfc2544-benchmarking tests test-name frloss-test test-interface ge-0/2/0.0 set interfaces ge-0/2/0 flexible-vlan-tagging set interfaces ge-0/2/0 mtu 9192 set interfaces ge-0/2/0 encapsulation flexible-ethernet-services set interfaces ge-0/2/0 unit 0 encapsulation vlan-bridge set interfaces ge-0/2/0 unit 0 vlan-id 512 set interfaces ge-0/2/1 flexible-vlan-tagging set interfaces ge-0/2/1 mtu 9192 set interfaces ge-0/2/1 encapsulation flexible-ethernet-services set interfaces ge-0/2/1 unit 0 encapsulation vlan-bridge set interfaces ge-0/2/1 unit 0 vlan-id 512 set bridge-domains bd1 vlan-id 10 set bridge-domains bd1 interface ge-0/2/1.0 set bridge-domains bd1 interface ge-0/2/0.0
Configuring VPLS Parameters on the MX Router (Provider Edge Router PE1)
set chassis fpc 0 pic 2 tunnel-services set interfaces ge-0/2/1 flexible-vlan-tagging set interfaces ge-0/2/1 mtu 9192 set interfaces ge-0/2/1 encapsulation vlan-vpls set interfaces ge-0/2/1 unit 0 encapsulation vlan-vpls set interfaces ge-0/2/1 unit 0 vlan-id 512 set interfaces ge-0/3/0 mtu 9192 set interfaces ge-0/3/0 unit 0 family inet address 192.0.2.1/24 set interfaces ge-0/3/0 unit 0 family mpls set interfaces lo0 unit 0 family inet address 198.51.100.1/32 set routing-options router-id 198.51.100.1 set routing-options autonomous-system 65100 set protocols mpls interface ge-0/3/0.0 set protocols bgp group test type internal set protocols bgp group test local-address 198.51.100.1 set protocols bgp group test family l2vpn signaling set protocols bgp group test neighbor 198.51.100.2 set protocols ospf traffic-engineering set protocols ospf reference-bandwidth 1g set protocols ospf area 0.0.0.0 interface ge-0/3/0.0 set protocols ospf area 0.0.0.0 interface lo0.0 set protocols ldp interface ge-0/3/0.0 set protocols ldp interface lo0.0 set routing-instances vpls-pe1 instance-type vpls set routing-instances vpls-pe1 interface ge-0/2/1.0 set routing-instances vpls-pe1 no-local-switching set routing-instances vpls-pe1 route-distinguisher 198.51.100.1:101 set routing-instances vpls-pe1 vrf-target target:1:2 set routing-instances vpls-pe1 protocols vpls site-range 8 set routing-instances vpls-pe1 protocols vpls no-tunnel-services set routing-instances vpls-pe1 protocols vpls site HUB site-identifier 1 set routing-instances vpls-pe1 protocols vpls vpls-id 1 set routing-instances vpls-pe1 protocols vpls neighbor 198.51.100.2
Configuring Benchmarking Test Parameters and VPLS Parameters on the MX104 Router (Provider Edge Router PE2)
set services rpm rfc2544-benchmarking tests test-name l2v-reflector source-mac-address 00:00:5e:00:53:11 set services rpm rfc2544-benchmarking tests test-name l2v-reflector destination-mac-address 00:00:5e:00:53:22 set services rpm rfc2544-benchmarking tests test-name l2v-reflector service-type elan set services rpm rfc2544-benchmarking tests test-name l2v-reflector in-service set services rpm rfc2544-benchmarking tests test-name l2v-reflector ip-swap set services rpm rfc2544-benchmarking tests test-name l2v-reflector udp-tcp-port-swap set services rpm rfc2544-benchmarking tests test-name l2v-reflector mode reflect set services rpm rfc2544-benchmarking tests test-name l2v-reflector family vpls set services rpm rfc2544-benchmarking tests test-name l2v-reflector reflect-etype 2048 set services rpm rfc2544-benchmarking tests test-name l2v-reflector direction egress set services rpm rfc2544-benchmarking tests test-name l2v-reflector source-udp-port 200 set services rpm rfc2544-benchmarking tests test-name l2v-reflector destination-udp-port 200 set services rpm rfc2544-benchmarking tests test-name l2v-reflector test-interface ge-0/3/1.0 set interfaces ge-0/2/5 mtu 9192 set interfaces ge-0/2/5 unit 0 family inet address 203.0.113.1/24 set interfaces ge-0/2/5 unit 0 family mpls set interfaces ge-0/3/1 flexible-vlan-tagging set interfaces ge-0/3/1 mtu 9192 set interfaces ge-0/3/1 encapsulation vlan-vpls set interfaces ge-0/3/1 unit 0 encapsulation vlan-vpls set interfaces ge-0/3/1 unit 0 vlan-id 512 set interfaces ge-0/3/1 unit 0 family vpls filter input portmirror set interfaces ge-0/3/1 unit 0 family vpls filter output portmirror set interfaces ge-0/3/2 flexible-vlan-tagging set interfaces ge-0/3/2 mtu 9192 set interfaces ge-0/3/2 encapsulation vlan-vpls set interfaces ge-0/3/2 unit 0 encapsulation vlan-vpls set interfaces ge-0/3/2 unit 0 vlan-id 512 set interfaces lo0 unit 0 family inet address 198.51.100.2/32 set forwarding-options port-mirroring input rate 1 set forwarding-options port-mirroring family vpls output interface ge-0/3/3.0 set forwarding-options port-mirroring family vpls output no-filter-check set forwarding-options port-mirroring instance pm1 input rate 10000 set forwarding-options port-mirroring instance pm1 family vpls output interface ge-0/3/3.0 set routing-options router-id 198.51.100.2 set routing-options autonomous-system 65100 set protocols mpls interface ge-0/2/5.0 set protocols bgp group test type internal set protocols bgp group test local-address 198.51.100.2 set protocols bgp group test family l2vpn signaling set protocols bgp group test neighbor 198.51.100.1 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface ge-0/2/5.0 set protocols ospf area 0.0.0.0 interface lo0.0 set protocols ldp interface ge-0/2/5.0 set protocols ldp interface lo0.0 set firewall family vpls filter portmirror term 1 then count pm1 set firewall family vpls filter portmirror term 1 then accept set firewall family vpls filter portmirror term 1 then port-mirror set routing-instances vpls-pe2 instance-type vpls set routing-instances vpls-pe2 interface ge-0/3/1.0 set routing-instances vpls-pe2 interface ge-0/3/3.0 set routing-instances vpls-pe2 no-local-switching set routing-instances vpls-pe2 route-distinguisher 198.51.100.2:102 set routing-instances vpls-pe2 vrf-target target:1:2 set routing-instances vpls-pe2 protocols vpls site-range 8 set routing-instances vpls-pe2 protocols vpls no-tunnel-services set routing-instances vpls-pe2 protocols vpls site SPOKE site-identifier 2 set routing-instances vpls-pe2 protocols vpls vpls-id 1 set routing-instances vpls-pe2 protocols vpls neighbor 198.51.100.1
Configuring Throughput Benchmarking Test Parameters on the ACX Series Router (Initiator)
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,
tput—for 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 256 bytes, and define the theoretical maximum bandwidth for the test as 600000 Kbps. You can specify any value from 1 Kbps through 1,000,000 Kbps for the maximum bandwidth.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile tput] user@host# set test-type throughput packet-size 256 bandwidth-kbps 600000
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 addresses 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 512 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 ports 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 400
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/0.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 250 test-interface ge-0/2/0.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 9104 bytes, and specify the theoretical maximum bandwidth for the test as 600000 Kbps. You can specify any value from 1 Kbps through 1,000,000 Kbps as the maximum bandwidth.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking profiles test-profile b2bt] user@host# set test-type back-toback-frames packet-size 9104 bandwidth-kbps 600000
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 addresses 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 as E-LAN.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name b2bt-test] user@host# set ovlan-id 512 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/0.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 10 test-interface ge-0/2/0.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 initiator (ACX Series router).
To configure the latency test parameters on the initiator:
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 as 1024, and specify the maximum bandwidth for the test in Kbps, 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 lty test-type latency packet-size 1024 bandwidth-kbps 600000
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 addresses 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 512 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 400
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/0.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 10 test-interface ge-0/2/0.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 600000
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, priority, and the canonical format indicator (cfi) value for the test frames. Together, the four added bytes, priority (3 bits) and canonical format indicator (1 bit) form the VLAN tag. Also, 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 512 ovlan-priority 7 ovlan-cfi 1 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 400
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 30 test-interface ge-0/2/0.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 in the CLI User Guide.
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-0/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-0/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-0/2/1] user@host# set unit 0 encapsulation vlan-bridge vlan-id 512
Configure the Layer 2 UNI interface.
content_copy zoom_out_map[edit] user@host# edit interfaces ge-0/2/0
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-0/2/0] 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-0/2/0] user@host# set unit 0 encapsulation vlan-bridge vlan-id 512
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 10 interface ge-0/2/1.0 user@host# set bridge-domains bd1 vlan-id 10 interface ge-0/2/0.0
Configuring the VPLS Parameters on the MX Series Router (PE1)
Step-by-Step Procedure
The following configuration requires you to enable a simple VPLS topology between the PE1 and PE2 routers. In this example, PE1 is a MX Series router. On the PE1 router, configure the tunnel services interface and prepare the router for VPLS by configuring the BGP, MPLS, OSPF protocols.
To configure the VPLS parameters on the MX Series router:
Configure tunnel services.
content_copy zoom_out_map[edit] user@host# set chassis fpc 0 pic 2 tunnel-services
Configure the VPLS VLAN encapsulation on the router.
content_copy zoom_out_map[edit] user@host# set interfaces ge-0/2/1 flexible-vlan-tagging user@host# set interfaces ge-0/2/1 mtu 9192 user@host# set interfaces ge-0/2/1 encapsulation vlan-vpls user@host# set interfaces ge-0/2/1 unit 0 encapsulation vlan-vpls user@host# set interfaces ge-0/2/1 unit 0 vlan-id 512
Configure the routing interface and the loopback interface on the router.
content_copy zoom_out_map[edit] user@host# set interfaces ge-0/3/0 mtu 9192 user@host# set interfaces ge-0/3/0 unit 0 family inet address 192.0.2.1/24 user@host# set interfaces ge-0/3/0 unit 0 family mpls user@host# set interfaces lo0 unit 0 family inet address 198.51.100.1/32
Configure the routing options on the router.
content_copy zoom_out_map[edit] user@host# set routing-options router-id 198.51.100.1 user@host# set routing-options autonomous-system 65100
Configure MPLS on the router to advertise the Layer 2 VPN interface that communicates with the PE2 router.
content_copy zoom_out_map[edit] user@host# set protocols mpls interface ge-0/3/0.0
Configure BGP as the signaling protocol on the router to enable carrying of Layer 2 VPLS messages.
content_copy zoom_out_map[edit] user@host# set protocols bgp group test type internal user@host# set protocols bgp group test local-address 198.51.100.1 user@host# set protocols bgp group test family l2vpn signaling user@host# set protocols bgp group test neighbor 198.51.100.2
Configure OSPF on the router to enable exchange of routing information.
content_copy zoom_out_map[edit] user@host# set protocols ospf traffic-engineering user@host# set protocols ospf reference-bandwidth 1g user@host# set protocols ospf area 0.0.0.0 interface ge-0/3/0.0 user@host# set protocols ospf area 0.0.0.0 interface lo0.0
Configure LDP on the router to enable LDP for all connections
content_copy zoom_out_map[edit] user@host# set protocols ldp interface ge-0/3/0.0 user@host# set protocols ldp interface lo0.0
Create and configure the VPLS routing interface
vpls-pe1.content_copy zoom_out_map[edit] user@host# set routing-instances vpls-pe1 instance-type vpls user@host# set routing-instances vpls-pe1 interface ge-0/2/1.0 user@host# set routing-instances vpls-pe1 no-local-switching user@host# set routing-instances vpls-pe1 route-distinguisher 198.51.100.1:101 user@host# set routing-instances vpls-pe1 vrf-target target:1:2 user@host# set routing-instances vpls-pe1 protocols vpls site-range 8 user@host# set routing-instances vpls-pe1 protocols vpls no-tunnel-services user@host# set routing-instances vpls-pe1 protocols vpls site HUB site-identifier 1 user@host# set routing-instances vpls-pe1 protocols vpls vpls-id 1 user@host# set routing-instances vpls-pe1 protocols vpls neighbor 198.51.100.2
Configuring Benchmarking Test Parameters on the MX104 Router (Reflector)
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,
l2v-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 l2v-reflector
Specify the source and destination MAC addresses of the test packet.
content_copy zoom_out_map[edit services rpm rfc2544-benchmarking test-name l2v-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 in which the test is executed, which is
in-service, at the reflector. Also, specify if the IP address, TCP and UDP port must be swapped.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking test-name l2v-reflector] user@host# set service-type elan in-service ip-swap udp-tcp-port-swap
Specify the mode, which is
reflect, at the reflector.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking test-name l2v-reflector] user@host# set mode reflect
Configure the family type,
vpls, specify the direction, egress, and specify the protocol being transported in the Ethernet frame, for the benchmarking test. Also, specify the source and destination UDP ports and specify the logical interface, ge-0/3/1.0, on which the RFC2544-based benchmarking test is being run.content_copy zoom_out_map[edit services rpm rfc2544-benchmarking tests test-name l2v-reflector] user@host# set family vpls direction egress source-udp-port 200 destination-udp-port 200 test-interface ge-0/3/1.0
Configuring Other Benchmarking Test Parameters on the MX104 Router (Reflector)
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 in the CLI User Guide.
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-0/3/1.0
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-0/3/1.0] user@host# set flexible-vlan-tagging mtu 9192 encapsulation vlan-vpls
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-0/3/1.0] user@host# set unit 0 encapsulation vlan-vpls vlan-id 512
Configure the Layer 2 UNI interface.
content_copy zoom_out_map[edit] user@host# edit interfaces ge-0/3/2.0
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-0/3/2.0] user@host# set flexible-vlan-tagging mtu 9192 encapsulation vlan-vpls
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-0/3/2.0] user@host# set unit 0 encapsulation vlan-vpls vlan-id 512
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 intreface ge-1/1/5.0
Start the benchmarking test on the reflector.
content_copy zoom_out_mapuser@host> test services rpm rfc2544-benchamrking test l2v-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 l2v-reflector stopcommand.
Configuring VPLS Parameters on the MX104 Router (Reflector)
Step-by-Step Procedure
The following configuration requires you to enable a simple VPLS topology between the PE1 and PE2 routers. In this example, PE2 is a MX104 Series router. On the PE2 router, configure the tunnel services interface and prepare the router for VPLS by configuring the BGP, MPLS, OSPF protocols to complement the configuration on PE1.
Configure tunnel services.
content_copy zoom_out_map[edit] user@host# set chassis fpc 0 pic 2 tunnel-services
Configure the VPLS VLAN encapsulation on the router.
content_copy zoom_out_map[edit] user@host# set interfaces ge-0/2/5 flexible-vlan-tagging user@host# set interfaces ge-0/2/5 mtu 9192 user@host# set interfaces ge-0/2/5 encapsulation vlan-vpls user@host# set interfaces ge-0/2/5 unit 0 encapsulation vlan-vpls user@host# set interfaces ge-0/2/5 unit 0 vlan-id 512
Configure the routing interface and the loopback interface on the router.
content_copy zoom_out_map[edit] user@host# set interfaces ge-0/3/0 mtu 9192 user@host# set interfaces ge-0/3/0 unit 0 family inet address 192.0.2.1/24 user@host# set interfaces ge-0/3/0 unit 0 family mpls user@host# set interfaces lo0 unit 0 family inet address 198.51.100.1/32
Configure the routing options on the router.
content_copy zoom_out_map[edit] user@host# set routing-options router-id 198.51.100.1 user@host# set routing-options autonomous-system 100
Configure MPLS on the router to advertise the Layer 2 VPN interface that communicates with the PE1 router.
content_copy zoom_out_map[edit] user@host# set protocols mpls interface ge-0/2/5.0
Configure BGP as the signaling protocol on the router to enable carrying of Layer 2 VPLS messages.
content_copy zoom_out_map[edit] user@host# set protocols bgp group test type internal user@host# set protocols bgp group test local-address 198.51.100.1 user@host# set protocols bgp group test family l2vpn signaling user@host# set protocols bgp group test neighbor 198.51.100.2
Configure OSPF on the router to enable exchange of routing information.
content_copy zoom_out_map[edit] user@host# set protocols ospf traffic-engineering user@host# set protocols ospf reference-bandwidth 1g user@host# set protocols ospf area 0.0.0.0 interface ge-0/2/5.0 user@host# set protocols ospf area 0.0.0.0 interface lo0.0
Configure LDP on the router to enable LDP for all interfaces.
content_copy zoom_out_map[edit] user@host# set protocols ldp interface ge-0/2/5.0 user@host# set protocols ldp interface lo0.0
Create and configure the VPLS routing interface,
vpls-pe2.content_copy zoom_out_map[edit] user@host# set routing-instances vpls-pe2 instance-type vpls user@host# set routing-instances vpls-pe2 interface ge-0/3/1.0 user@host# set routing-instances vpls-pe2 no-local-switching user@host# set routing-instances vpls-pe2 route-distinguisher 198.51.100.1:101 user@host# set routing-instances vpls-pe2 vrf-target target:1:2 user@host# set routing-instances vpls-pe2 protocols vpls site-range 8 user@host# set routing-instances vpls-pe2 protocols vpls no-tunnel-services user@host# set routing-instances vpls-pe2 protocols vpls site SPOKE site-identifier 1 user@host# set routing-instances vpls-pe2 protocols vpls vpls-id 1 user@host# set routing-instances vpls-pe2 protocols vpls neighbor 198.51.100.2
Results
In configuration mode, confirm your configuration on the ACX Series router, the
MX 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-0/2/0 {
flexible-vlan-tagging;
mtu 9192;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 512;
}
}
ge-0/2/1 {
flexible-vlan-tagging;
mtu 9192;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 512;
}
}
[edit bridge-domains]
bd1 {
vlan-id 600;
interface ge-0/2/1.0;
interface ge-0/2/0.0;
}
[edit services rpm]
rfc2544-benchmarking {
profiles {
test-profile tput {
test-type throughput
packet-size 256;
bandwidth-kbps 600000;
}
test-profile b2bt {
test-type back-back-frames
packet-size 9104;
bandwidth-kbps 600000;
}
test-profile lty {
test-type latency
packet-size 1024;
bandwidth-kbps 600000;
}
test-profile frloss {
test-type frameloss
packet-size 1600;
bandwidth-kbps 6000000;
}
tests {
test-name tput-test {
interface ge-0/2/0.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 512;
service-type elan;
family bridge;
direction egress;
source-udp-port 200;
destination-udp-port 400;
test-iterator-duration 250;
}
test-name b2b-test {
interface ge-0/2/0.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 512;
service-type elan;
family bridge;
direction egress;
destination-udp-port 400;
test-iterator-duration 10;
}
test-name lty-test {
interface ge-0/2/0.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 512;
service-type elan;
family bridge;
direction egress;
source-udp-port 200;
destination-udp-port 400;
test-iterator-duration 10;
}
test-name frloss-test {
interface ge-0/2/0.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 512;
service-type elan;
family bridge;
direction egress;
source-udp-port 200;
destination-udp-port 400;
test-iterator-duration 30;
}
}
}
VPLS Parameters on the MX Series router:
[edit routing-instances]
vpls-instance vpls-pe1{
instance-type vpls;
interface ge-0/2/1.0;
route-distinguisher 198.51.100.1:101;
vrf-target target:1:2;
}
[edit]
protocols {
vpls {
vpls-id 1;
neighbor 198.51.100.2;
site-range 8;
no-tunnel-services;
site HUB {
site-identifier 1;
}
}
}Benchmarking Test Parameters and VPLS Parameters on the MX104 Series router:
[edit interfaces]
ge-0/3/1 {
flexible-vlan-tagging;
mtu 9192;
encapsulation vlan-vpls;
unit 0 {
encapsulation vlan-vpls;
vlan-id 512;
}
}
ge-0/2/5 {
flexible-vlan-tagging;
mtu 9192;
unit 0 {
family inet address 203.0.113.1/24;
family mpls;
}
}
[edit services rpm]
rfc2544-benchmarking {
# Note, When in reflector mode, test profile is not needed
tests {
test-name l2v-reflector {
interface ge-0/3/1.0;
source-mac-address 00:00:5e:00:53:11;
destination-mac-address 00:00:5e:00:53:22;
mode reflect;
service-type elan;
in-service;
ip-swap;
udp-tcp-port swap;
family vpls;
reflect-etype 2048;
direction egress;
source-udp-port 200;
destination-udp-port 200;
}
}
}
[edit routing-instances]
vpls-instance vpls-pe2 {
instance-type vpls;
interface ge-0/3/1;
route-distinguisher 198.51.100.2:102;
vrf-target target:1:2;
}
[edit]
protocols {
vpls {
vpls-id 1;
neighbor 198.51.100.1;
site-range 8;
no-tunnel-services;
site SPOKE {
site-identifier 2;
}
}
After you have configured the device, enter the commit command,
in configuration mode.
Verifying the Results of the Benchmarking Test for Layer 2 ELAN Services Using VPLS
Examine the results of the benchmarking test that is performed on the configured service between the ACX Series router and the MX104 Series router.
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 the ACX Series router and the MX104 Series router.
Action
In operational mode, enter the 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 show services rpm
rfc2544-benchmarking operational command, see show
services rpm rfc2544-benchmarking topic in the CLI
Explorer.
