Application Note 130 RFC-2544 Testing PDF

AN187 V-NID Backup and Restore
AN130 RFC 2544 Testing

Application Note
May 2017 l Document Revision 4

Publication Information
AN130 RFC-2544 Testing, revision 4
Publication date: May 4, 2017
Trademark Information
© 2017 Accedian Networks Inc. All rights reserved. Accedian, Accedian Networks, the Accedian logo, airMODULE,
antMODULE, EtherNID, Experience ● Performance, FlowBROKER, FlowMETER, MetroNID, MetroNODE, NanoNID,
Network State+, Performance Assurance Agent (PAA), PERFORMANT, Plug & Go, R FLO, SkyLIGHT, SkyLIGHT Director,
SkyLIGHT Director License Server, SkyLIGHT VCX Controller, SyncMETER, Traffic-Meter Vision Suite, Vision Collect,
Vision EMS, Vision Flow, Vision SP, VisionMETRIX and V-NID are trademarks or registered trademarks of Accedian
Networks Inc.
SevOne is a trademark of SevOne, Inc. SevOne Accedian Edition is a joint trademark of Accedian Networks Inc. and
SevOne, Inc.
All other company and product names may be trademarks of their respective companies. Accedian may, from time
to time, make changes to the products or specifications contained herein without notice. Some certifications may
be pending final approval; please contact Accedian for current certifications.
Accedian’s products are protected by patents as indicated on Accedian’s website, located at
http://www.accedian.com/en/legal.html
The mention of any product herein does not constitute an endorsement by Accedian Networks Inc.
The content of this publication is provided for informational use only, is subject to change without notice and should
not be construed as a commitment by Accedian Networks Inc. Accedian Networks Inc. assumes no responsibility or
liability for any errors or inaccuracies that may appear in this document.
Except as permitted by such lease agreement, no part of this publication may be reproduced, stored in any retrieval
system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without prior
written consent of Accedian Networks Inc.
Changes are periodically made to the information herein; these changes will be incorporated into new editions of
this publication. Accedian Networks Inc. may make improvements and/or changes in the products and/or software
programs described in this publication at any time.
Contact
If you have comments regarding this manual or the products it describes, address them to:
Accedian Networks Inc.
Attention: Technical Publications
2351 Alfred-Nobel Blvd., Suite N-410
Saint-Laurent, Québec
Canada H4S 2A9
Tel: 514-331-6181
Fax: 514-331-2210
Toll free: 1-866-685-8181
accedian.com
Document Revision 4 l May 2017 1

Application Note AN130 RFC-2544 Testing
Contents
1 Introduction ....................................................................................................... 4
1.1 Setting up the Traffic Generator ................................................................................................. 4
1.2 Setting up the Traffic Monitor ..................................................................................................... 5
1.3 Setting up a Test Suite ................................................................................................................. 5
2 Configuration Examples ..................................................................................... 6
2.1 Example 1: Out-of-Service Layer-2 Throughput Testing using the Traffic Generator ................. 6
2.1.1 Get the MAC Address of the Loopback Device PE .......................................................... 7
2.1.2 Configure the Test Generator PE .................................................................................... 7
2.1.3 Perform the Test ............................................................................................................. 9
2.2 Example 2: Out-of-Service Layer-3 Throughput Testing using the Traffic Generator ............... 12
2.2.1 Test Configuration ........................................................................................................ 12
2.2.2 Configure the Generator Unit ...................................................................................... 12
2.2.3 Configure the Loopback Device .................................................................................... 14
2.2.4 Perform the Test ........................................................................................................... 18
2.3 Example 3: In-service Layer-2 Throughput Testing using the Traffic Generator and Monitor . 19
2.3.1 Get the MAC address of the traffic monitor unit ......................................................... 20
2.3.2 Configure the Bandwidth Regulator on the Traffic Generator Unit ............................. 20
2.4 Example 4: IP Multicast Testing using the Traffic Generator and Monitor ............................... 27
2.4.1 Configure MetroNID 1 (Traffic Generator) ................................................................... 27
2.4.2 Configure MetroNID 2 (Monitor) ................................................................................. 29
2.4.3 Configure MetroNID 3 (Additional Monitor) ................................................................ 29
2.4.4 Perform the Test ........................................................................................................... 29
2.5 Example 5: Layer-2 Testing with the RFC 2544 Test Suite ........................................................ 32
Appendix 1: Troubleshooting ................................................................................. 37
Layer-2 Generator Test Not Receiving Test Packets ............................................................................ 37
Delay Measurements Equal to Zero (0) ............................................................................................... 37
Layer-3 Test Stops Immediately .......................................................................................................... 37
Layer-3 Test Suite Not Receiving Test Packets .................................................................................... 38
Packet Loss for Test Suite with Large Frames...................................................................................... 38
Test Suite Fails for Specific Frame size ................................................................................................ 38

Appendix 2: Types of Test Traffic for RFC 2544 ..................................................... 39

Out-Of-Service ..................................................................................................................................... 39
In-Service ............................................................................................................................................. 40
Layer-3 ................................................................................................................................................. 40
Appendix 3: Example of RFC 2544 test suite report............................................... 41

1 Introduction
This document describes how to use Accedian Network Performance Elements (PEs or simply
“units”) to perform end-to-end testing and monitoring. This allows you to pinpoint devices or
network problems or to measure current throughput, packet delay and packet-delay variation
on a specific network segment. The possible tests include ones specified in RFC 2544. This
document also includes common RFC 2544 troubleshooting information.
Advanced traffic generation and analysis capabilities allow you to perform fully automated
and documented turn-up tests. The test capabilities include in-service tests as well as out-of-
service tests.
For out-of-service tests, you must pair the traffic generator with another unit that loops the
traffic back. The PEs contain pre-programmed RFC 2544 loopbacks for certain types of Layer-
2 frames. When testing with Layer-2 generic frames or Layer-3 packets (UDP), you must
configure the peer unit with a loopback that matches the test traffic, and with a swapping
action on the source/destination MAC addresses, IP addresses and UDP port numbers. For IP
multicast traffic, you must use the RFC monitor in the remote unit.
The next figure illustrates a typical network for traffic generation and analysis tests:
You may use the test generator to generate one or two flows of test traffic and provide
separate results for each flow. Each flow has specific characteristics, such as traffic type and
bit rate. You have the following choices when setting up each flow:
• Layer 2 (three types), Layer 3, and IP multicast traffic
• VLAN or VLAN-in-VLAN encapsulation of test traffic
• Different traffic types, frame/packet sizes, and payload patterns
1.1 Setting up the Traffic Generator

You can set up the traffic generator to send one or two traffic flows, each having a different
traffic type, VLAN, and patterns.

1.2 Setting up the Traffic Monitor

You can set up the traffic monitor to receive and analyze one specific traffic flow, which can
vary in traffic type, VLAN and patterns. The traffic monitor is used in conjunction with the
generator to perform in-service RFC 2544 non-intrusive throughput tests, while end-user
traffic continues flowing without interruption.
You configure the traffic monitor from the remote unit. Note that the in-service test is
unidirectional, as opposed to the out-of-service test, which is bidirectional (round-trip).
1.3 Setting up a Test Suite

You can run a test suite to determine whether a network section or a specific device conforms
to a service level agreement (SLA) or to an Ethernet standard. You can define a total of 16 test
suites and store up to 32 test reports. When configuring a test suite, you have the choice of
enabling one or more of the following tests:
• Throughput
• Frame Loss
• Delay
• Back-to-back
You must also set information pertaining to the remote peer (Peer settings) and the test
packet contents. Various parameters are configurable, depending on the type of test traffic.

2 Configuration Examples
We will discuss the following examples:

• Example 1: Out-of-service Layer-2 throughput testing using the traffic generator
• Example 2: Out-of-service Layer-3 throughput testing using the traffic generator
• Example 3: In-service Layer-2 throughput testing using the traffic generator and
monitor
• Example 4: IP multicast testing using the traffic generator and monitor
• Example 5: Layer-2 testing with the RFC 2544 test suite
2.1 Example 1: Out-of-Service Layer-2 Throughput Testing using the

Traffic Generator
The standard (out-of-service) RFC 2544 method is widely used as a turn-up solution for testing
a circuit’s throughput prior to enabling customer traffic. This testing method can also be used
when customers report bandwidth-related problems, or when new equipment is installed in
the network. You must bring the circuit down to use this testing method.
The figure below shows a typical network for testing the throughput of a circuit at Layer 2.
The basic steps involved in out-of-service testing at Layer 2 are:

1. Get the MAC Address of the loopback device PE
2. Configure the test generator PE
3. Perform the test
Each of these steps is described in more detail below.

This example will use the following test configuration:
Test Configuration
Element Value
Circuit throughput 15 Mbps
Traffic type Layer 2
Frame size 1024 bytes
VLAN 1 ID 100
VLAN 1 priority 7
2.1.1 Get the MAC Address of the Loopback Device PE

1. Login to the loopback device PE.
2. Open Port > Configuration.
3. Take note of the MAC address for the network port that connects to the Generator. We
will need it to configure the RFC 2544 generator flow. An example of a MAC address is
shown in the next figure.
2.1.2 Configure the Test Generator PE

1. Login to the test generator PE.
2. Open Traffic > Configuration.
3. Set the Generator working rate to Layer-2, as shown in the next figure.

Note: When the working rate is set to Layer 2, rate calculations include only Layer-2
Ethernet frames. When the working rate is set to Layer 1, rate calculations include
Layer-1 Ethernet frames plus the Interframe Gap (IFG), preamble, and Start Frame
Delimiter (SFD).
4. Open SAT > RFC 2544 > Generator > Configuration.
5. Set up the generator as follows. See also the figure below.
a. Set the Outgoing port and check Enable first flow.
b. Open the First packet header settings. Set the traffic Type to layer-2. In the MAC
destination field, type the MAC address of the Loopback unit’s RJ45-B port you noted
earlier. This will allow the test traffic to be automatically looped back by the loopback
device.
Note: Refer to Appendix 2: Types of Test Traffic for RFC 2544 Appendix 2.
c. Check Enable VLAN 1 header, set VLAN 1 ID to 100, VLAN 1 priority to 7, and VLAN 1
Ethernet type to C-VLAN.
d. Open First flow profile settings and optionally enter a Flow name and Flow
description.
e. If there is a Flow type drop-down box, Set Flow type to Out-of-service.
Note: if the drop-down box is not present, then the Flow type is Out of service by
default.
f. Set the Traffic type to constant and the Bit rate to 15000 kbps.
g. Set frame Size type to fixed and Size to 1024 bytes.
h. Set the test Duration type to continuous.
Note: Leave the default values for the other parameters.

6. Click Apply.
2.1.3 Perform the Test

1. Open SAT > RFC 2544 > Generator > Results.
2. Click the Start button. Press F5 to refresh the screen. You should see a screen similar to
the following:

3. Click on details to get more test results, as shown in the figure below. We see that the
measured L2 rate is 15 Mbps. The transmission and reception rates are the same, which
validates that the circuit throughput is 15 Mbps. This screen also displays the Layer-1
rates.
4. Return to the previous screen and click the Stop button.

This stops the test and displays the details again, as shown in the figure below. Since the
number of transmitted packets is the same as the number of received packets, we can
conclude that there has been no packet loss during the test. We also see information about
the two-way delay measured during the test.


2.2 Example 2: Out-of-Service Layer-3 Throughput Testing using the

Traffic Generator
This example describes how to test the throughput of a circuit at Layer 3. A Layer-3 test
requires that IP interfaces be configured on both units, i.e., the test generator and the remote
loopback device. Loopback must be configured manually on the remote device.
The physical setup is the same as for Example 1: Out-of-service Layer-2 throughput testing
using the traffic generator.
The basic steps involved in out-of-service testing at Layer 3 are:
• Configure the Generator Unit
• Configure the Loopback Unit
• Perform the Test
This example will use the following test configuration:
2.2.1 Test Configuration

Element Value
Circuit throughput 15 Mbps
Traffic type Layer 3
Frame size 1024 bytes
Ports (UDP) Source: 5000
Destination: 5000
Generator unit IP address 10.10.10.11/24 (on port SFP-1-1)
Loopback unit IP address 10.10.10.12/24 (on port RJ-45-B)
2.2.2 Configure the Generator Unit

1. Login to the Generator Unit.
2. Open System > Configuration > Interface.
3. Click the upper Add button to add a new interface.
4. Set up the new interface as shown in the figure below.
a. Set State to Enable.
b. Enter Network_Gen for the Interface name.
c. Set the Interface type to Standard.
d. Set On port to SFP-1-1.

e. Set IPv4 to Manual configuration.

f. Enter 10.10.10.11 for the IP address.
5. Click Apply.
7. Set up the generator as shown in the figure below.
a. Set the Outgoing port to SFP-1-1 and check the box for Enable first flow.
b. Open the First packet header settings. Set the traffic Type to layer-3. Set the
Destination IP address to 10.10.10.12. Set the Source port and Destination port to
5000.
c. Open the First flow profile settings and optionally enter a Flow name and Flow
description.
d. Set the Traffic type to constant and the Bit rate to 15000 kbps.
e. Set frame Size type to fixed and Size to 1024 bytes.
f. Set the test Duration type to continuous.

8. Click Apply.
2.2.3 Configure the Loopback Device

For the loopback device, there are three things to configure: the IP interface, the filter, and
the loopback.
First, we need to configure an IP interface to match the destination IP that was set in the
traffic generator. Here are the steps:
1. Login to the Loopback device.
2. Open to System > Configuration > Interface.

3. Add a new interface.

4. Set up the new interface as shown in the figure below:
a. Set the State to Enable.
b. Enter Network for the Interface name.
c. Set the Interface type to Standard.
d. Set On port to Network.
e. Set IPv4 to Manual configuration.
f. Enter 10.10.10.12 for the IP address.
5. Click Apply.
Next, we need to configure a Layer-3 filter that matches the test traffic. Here are the steps:
1. Open Traffic > Filters > IPv4 filters.
2. Click the Add button. Set up the filter as shown in the figure below.
Note: The filter can use any parameter that is specific to the test traffic. In this
example, we will use the UDP port number (5000).
a. Enter UDP_5000 for the IPv4 filter name.
b. In IPv4 header settings, set the Protocol to UDP 17.
c. In UDP/TCP ports settings, set Source port and Destination port to 5000.

3. Click Apply.
Finally, we need to configure the manual loopback as follows:

1. Open OAM > Configuration.
2. Click the Add button.
3. Set up the new OAM instance as shown in the figure below.
a. Enter L3_Loopback for the Name.
b. Set the Port to Network.

4. Open OAM > Loopback.

5. Click the name of the OAM instance you just created, which was L3_Loopback.
6. Set up the loopback as shown in the figure below, using the name of the filter you just
created, which was UDP_5000.
a. Enter L3_Loopback for the Name.
b. Check Loopback enable.
c. Set the Type to Custom.
d. Set the Filter type to IPv4 filter.
e. Select the IPv4 filter you have just created, i.e., UDP_5000.
f. Check the three Actions boxes: Swap MAC addresses, Swap IP addresses, and Swap
TCP/UDP ports.
g. If you want the loopback to automatically terminate after a certain period, then enter
a Loopback timeout. In our example, we have set this to 5 minutes.
Note: Using the loopback timeout is a good practice if you want to validate your
configuration before making it permanent. When you are sure the loopback works as
desired, you can set the timeout to 0 and it will then make the loopback permanent.


1. Open SAT > RFC 2544 > Generator > Results.
2. Click the Start button. Press F5 to refresh the screen. The results should be displayed in
the same format shown in Example 1: Out-of-service Layer-2 Throughput Testing Using
the Traffic Generator.

2.3 Example 3: In-service Layer-2 Throughput Testing using the

Traffic Generator and Monitor
As part of its end-to-end live Ethernet SLA verification, the Network Performance Elements
allow you to remotely run in-service RFC 2544 validation non-intrusively, i.e., the end-user
traffic continues to flow, unaffected by the in-service test.
In this example, we will validate the maximum throughput of a circuit in one direction, while
the end-customer traffic remains completely unaffected.
The following figure shows a typical network for in-service throughput testing.
Here are some notes on the test:

• The test requires two units: we will set up one unit as the Generator and another unit
as the Monitor.
• The traffic generator can be any unit that supports in-service testing. For example,
the TE performance element 6.4.3 or higher supports in-service testing. The GX, GT,
and LT performance elements 7.4 or higher also support this feature.
• We will send test traffic (shown in red) from the generator to the monitor along with
any customer traffic (shown in white). The test traffic will fill any part of the link or
EVC that is not carrying customer traffic. The Monitor will receive the test traffic and
display the results.
• If you are measuring one-way delay, you should synchronize the clocks of the two
units to get accurate results.
This document explains in detail a variation of the above test. The variation is based on a “lab
test” scenario, with customer traffic emulated by an external traffic generator. The emulated
customer traffic goes through the traffic generator to the traffic monitor. See the following
notes as well as the figure below.
• The traffic generator will test a committed information rate (CIR) of 200 Mbps to the
traffic monitor. This means you must configure it to send a 200-Mbps flow, combining
the (emulated) customer traffic with test traffic. The generator uses a 200-Mbps
regulator to monitor the incoming customer traffic (50 Mbps) on the client port and
to add the necessary outgoing test traffic, i.e. 150 Mbps.

• Accordingly, the traffic monitor should show 150 Mbps of test traffic being received,
matching what the traffic generator is sending. The remaining 50 Mbps is customer
traffic and will not be measured by the monitor.
Note: It is important to bind the regulator to the policy receiving the customer
traffic. For example, if customer traffic is being received on the client port on policy
1-7, then you must bind the regulator to this port and policy.
The basic steps for in-service testing at Layer 2 are:
1. Get the MAC address of the traffic monitor unit
2. Configure the bandwidth regulator on the traffic generator unit
3. Configure the traffic generator
4. Configure the traffic monitor
5. Perform the test
2.3.1 Get the MAC address of the traffic monitor unit

Login to the traffic monitor and get its MAC address, by following the procedure described in
“Example 1: Out-of-service Layer-2 throughput testing using the traffic generator”.
See 2.2 Example 2: Out-of-Service Layer-3 Throughput Testing using the Traffic Generator on
page 12.
2.3.2 Configure the Bandwidth Regulator on the Traffic Generator Unit

In-service throughput testing requires a bandwidth regulator. This regulator will be used by
the traffic generator and will be bound to the traffic policy receiving the customer traffic.
The purpose of the regulator is to establish a limit for testing. In most cases, we want to set
the regulator to match the bandwidth of the link or EVC we are testing. If we want to test an
EVC or service above the agreed CIR value, we would set a flow to have a value superior to
the regulator.
In this example, we will configure the regulator with a committed information rate (CIR) of
200 Mbps.
1. Login to the traffic generator unit.

2. Open Traffic > Regulators > Configuration.

3. Click the Add button to add a new regulator.
4. Set up the regulator as shown in the figure below.
a. Enter 200Mbps for the Traffic regulator name.
b. Set the Committed Information Rate to 200000.
c. Set the Committed Burst Size to 8.
d. Set the Excess Information Rate to 0.
e. Set the Excess Burst Size to 8.
5. Click Apply.
2.3.2.1 Configure the Bandwidth Regulator on the Traffic Generator Unit

2. Set up the generator as shown in the figure below.
a. Set Outgoing port to Network and check Enable first flow.
b. Open First packet header settings.
c. Set the traffic Type to layer-2.
d. In the MAC destination field, enter the address of the RJ45-B port (Network) you
noted previously. This will allow the test traffic to be automatically looped back by
the MetroNID.
See 2.1.1 Get the MAC Address of the Loopback Device PE on page 7.
Refer to Appendix 2: Types of Test Traffic for RFC 2544 for a description of the
various types of test traffic.
e. Open First flow profile settings.
f. Set Flow type to In-service and Regulator to 200Mbps.
g. Optionally, enter a Flow name and a Flow description.
h. Set Traffic type to constant and Bit rate to 200000 kbps.

i. Set frame Size type to fixed and Size to 1024 bytes.

j. Set the test Duration type to continuous.
3. Click Apply.
2.3.2.2 Configure the Traffic Monitor

1. Login to the traffic monitor unit.
2. Open SAT > RFC 2544 > Monitor > Configuration.
a. Check Enable.

b. Optionally, enter a Monitor name and Monitor description. Below, we show Monitor
name set to FirstMonitor.
c. Set Monitor mode to Terminal. In this mode, the test traffic will terminate in this unit
(i.e., will not pass through it).
d. Set the Incoming port to Network, i.e., the port receiving the test traffic from the
generator.
e. Under the Packet header settings, set Type to layer-2 and MAC destination to the
address of the Network port (i.e. use same parameters as on the Generator).
3. Click Apply.
2.3.2.3 Perform the test

When performing an In-Service test, you must start the traffic monitor before starting the
traffic generator.
Perform the test as follows:
1. Start the external traffic generator to emulate the customer traffic (constant 50 Mbps).
2. Login to the traffic monitor.
3. Open SAT > RFC 2544 > Monitor > Results and then click Start.
4. Login to the traffic generator.
5. Open SAT > RFC 2544 > Generator > Results and then click Start.
6. Click on details of the first flow to view the FirstMonitor results. Press F5 to refresh the
screen. You should see a screen similar to the following one.

In the figure above, we see that the generator is transmitting a flow of 150 Mbps (L2 rate). It
is adding 150 Mbps of test traffic to the customer traffic flow of 50 Mbps for a total of 200
Mbps.
8. Open SAT > RFC 2544 > Monitor > Results. Press F5 to refresh the screen. You should see
a screen similar to the following:

The figure above confirms that the monitor named FirstMonitor is receiving 150 Mbps (L2
rate) of test traffic from the generator.
Note: In a real customer network, the traffic rate constantly fluctuates over time, so
you should expect the reception rate to vary as well, as the In-Service Generator
adapts the outgoing test traffic rate to the incoming customer traffic rate.
Stop the test and verify the results as follows:
1. Login to the traffic generator.
2. Open SAT > RFC 2544 > Generator > Results and then click Stop.
3. Click details of the first flow to view the First flow results. You should see a screen like
the following one. Take note of the number of transmitted packets so we can compare
with the monitor results.

5. Open SAT > RFC 2544 > Monitor > Results.
6. Click on details of the first flow to view the First flow results. You should see a screen
similar to the following:

We see that the receive statistics of the monitor match the transmit statistics of the
generator. This confirms that the circuit successfully passed 200 Mbps of traffic without any
packet loss. This screen also displays the one-way delay and one-way delay variation
measured during the test.

2.4 Example 4: IP Multicast Testing using the Traffic Generator and

Monitor
The IP multicast test allows you to perform an out-of-service unidirectional throughput test
for multiple units simultaneously. The traffic generator sends IP multicast packets on the
network. Each remote site monitors the traffic it receives. The test results display the received
rate, packet counts, and one-way delay information.
The following figure illustrates the network for a simple example, where we have one
generator and two monitors.
Note: Since you are measuring one-way delay, you should synchronize the clocks of
the two units to get accurate results.
The basic steps for in-service multicast testing are:
• Configure MetroNID 1 (Traffic Generator)
• Configure MetroNID 2 (Monitor)
• Configure MetroNID 3 (Additional Monitor)
• Perform the Test
Each of these steps is described in more detail below
2.4.1 Configure MetroNID 1 (Traffic Generator)

1. Connect to MetroNID 1.
3. Set up the generator as follows. This is shown in the figure below.
a. Enter a Test description, e.g. IP_Multicast_Test.
b. Set the Outgoing port to Network and check Enable first flow.

c. Open the First packet header settings. Set the traffic Type to IP multicast. In the
Destination IP address field, type a valid multicast address (e.g. 230.0.0.10 ). In the
Source IP address field, type a valid unicast address (e.g. 10.10.10.10).
Refer to Appendix 2: Types of Test Traffic for RFC 2544 Appendix2: Types of Test
Traffic for RFC 2544.
d. In the First flow profile settings, set the Flow type to Out-of-service.
e. Enter the Flow name and Flow description desired.
f. Set the Traffic type to constant and the Bit rate to 10000 kbps.
g. Set frame Size type to fixed and Size to 1024 bytes.
h. Set the test Duration type to continuous.
Note: Leave the other parameters set to their default values.
4. Click Apply.

2.4.2 Configure MetroNID 2 (Monitor)

2. Open SAT > RFC 2544 > Monitor > Configuration.
3. Click the FirstMonitor and set up the monitor as follows. This is shown in the figure below.
a. Check the Enable box.
b. Enter a Monitor name and Monitor description.
c. Set the Monitor mode to Terminal. In this mode, the test traffic will terminate in this
unit (i.e. will not pass through it).
d. Set the Incoming port to Network, i.e. the port receiving the test traffic from the
generator.
e. Under the Packet header settings, set the Type to layer-3 and the Destination IP
address to 230.0.0.10 (i.e. same as in the Generator).
f. Enter 5000 for the Source port and for the Destination port.
2.4.3 Configure MetroNID 3 (Additional Monitor)

Repeat all steps above, as explained for MetroNID 2, for each additional monitor unit.

When performing a unidirectional test using the RFC 2544 Monitor, you must start the Traffic
Monitor before starting the Generator.
Perform the test as follows:

1. Connect to MetroNID 2 (traffic monitor).

2. Open SAT > RFC 2544 > Monitor > Results and then click Start.
3. Connect to each additional monitor unit and start the test.
4. Connect to MetroNID 1 (traffic generator).
5. Open SAT > RFC 2544 > Generator > Results and then click Start.
6. Click on details of the first flow to view the First flow results. Press F5 to refresh the
screen. You should see a screen like the following one.
In the figure above, we see that the generator is transmitting a flow of 10 Mbps (L2 rate) of
test traffic.
8. Open SAT > RFC 2544 > Monitor > Results. Press F5 to refresh the screen.
You should see a screen like the following one.

The figure above confirms that the Monitor is receiving 10 Mbps (L2 rate) of test traffic from
the generator.
If you stop the generator in MetroNID 1 and look at the monitor statistics in MetroNID 2 (and
MetroNID 3), you can compare the number of packets sent by the generator versus the
number of packets received in each monitor. If the numbers are the same, you can conclude
there was no packet loss during the test.

2.5 Example 5: Layer-2 Testing with the RFC 2544 Test Suite
In this example, we will set up a test suite for throughput, delay, delay variation, frame loss,
and back to back testing at Layer 2.
The basic steps for using a test suite are:

Each of these steps is described in more detail below
2.5.1.1 Get the MAC Address of Loopback Device

1. Connect to RFC-2544 Test Suite and get its MAC address following the procedure
described in Example 1: Out-of-Service Layer-2 Throughput Testing Using the Traffic
Generator.
2.5.1.2 Configure the Test Suite

1. Connect to RFC-2544 Test Suite.
2. Open SAT > RFC 2544 > Testsuite > Configuration and then click the Add button.
3. Set up the Test suite as shown in the figure below.
a. Enter a Suite name and Suite description.
b. Under the Peer settings, set the Type to layer-2 and the MAC destination to the
address of the remote MetroNID port facing the generator. This will allow the test
traffic to be automatically looped back.
c. Under the Throughput settings, set up all setting required by subsequent tests: delay,
delay variation, frame loss, and back to back.

4. Set up Delay and delay variation settings, Frame loss settings and Back to back settings
as shown in the figure below.

5. Click Apply.
2.5.1.3 Configure the Test Report and Run the Test Suite
Once you have set up a test suite, you can run it and view its report. Since each test is
associated with one test report, you must configure a new report each time you want to run
a new test. You can run a specific test suite many times provided you configure a new report
each time. Remember that you can store a maximum of 32 test reports in the memory.
1. Open SAT > RFC-2544 > Testsuite > Reports.
2. Click Start new testsuite to configure a new report. This displays the screen shown in the
figure below.

3. Fill in the File name, Description and Testsuite configuration and then click Run.
4. Open SAT > RFC 2544 > Testsuite > Report. This displays the screen shown in the figure
below.
5. Click the name of the test suite report to view it. An example report is shown in the figure
below.
Note: You can use the scroll bar to view the report as it is running. Refreshing the
browser screen (F5) will update the report.
6. Click the Save button to save the report to your workstation. Once the test is complete,
this report screen will look as follows:

To see an example of a complete report for a RFC 2544 test suite, refer to Appendix 3: Example
of RFC 2544 Test Suite Report.

Appendix 1: Troubleshooting
Layer-2 Generator Test Not Receiving Test Packets

Problem: After you start the RFC 2544 Traffic Generator in a Layer-2 test, it transmits packets,
but does not receive any.
Solution: For Layer-2 or Layer-2 Accedian, verify whether the test flows are set up with the
correct peer unit MAC address so that the traffic can be automatically looped back. For Layer-
2 generic test traffic, verify that the remote unit is set up with a manual loopback that
performs MAC address swapping.
Delay Measurements Equal to Zero (0)

Problem : When a unidirectional RFC 2544 test is running, all delay measurement values are
equal to zero (0)
Solution: To be able to run delay measurement tests, the clock status must be Synchronized.
Verify the clock status. If it is Not synchronized, the test will display "0" values. Once the clock
status is Synchronized, you will be able to measure delay.
Layer-3 Test Stops Immediately

Problem: After you start the RFC 2544 generator in a Layer-3 test, the test stops immediately
and does not show any results.
Solution: This could be due to a mis-configuration of the interfaces. Verify whether you can
ping the remote unit from the generator unit. To do so, open System > Maintenance > System
tools in the generator unit and then ping the IP address of the loopback interface. If
everything is properly configured, you should get a successful ping response, as shown in the
figure below:
If the ping is not successful, verify the interface configuration on both units.

Layer-3 Test Suite Not Receiving Test Packets

Problem: After you start the RFC 2544 test at Layer 3, it transmits packets, but does not
receive any.
Solution: Verify that the remote unit is set up with a manual Layer-3 loopback that swaps
MAC addresses, IP addresses, and UPD ports.
Packet Loss for Test Suite with Large Frames

Problem: When an RFC 2544 test suite is running on a VLAN, the tests always fail for a frame
size of 1518 Bytes. The MTU on each interface is set to 1518 bytes.
Solution: This might be an MTU issue. Verify that the MTU is large enough on all the devices
through which the test traffic flows, including the unit generating the RFC 2544 test suite and
the loopback unit.
Test Suite Fails for Specific Frame size

Problem: When running an RFC 2544 test suite on a VLAN, the tests always fail for a frame
size of 1518 Bytes. The MTU on all interfaces are set to 1518 bytes.
Solution: When running a test on VLAN, you must account for the extra 4 bytes used for the
VLAN tag. Therefore, the MTU in the network should be set to at least 1522 bytes (1518 + 4).

Appendix 2: Types of Test Traffic for RFC 2544
Various types of test traffic can be used with the RFC 2544 Traffic Generator and test suite.
Out-Of-Service
The following types of test traffic are available in the Test suite and Generator for out-of-
service testing.
Layer-2
The "classic" Layer-2 frame type has frames that are Y.1731-compliant LBM/LBR.
LBM: opcode 03/ethertype 0x8902
LBR: opcode 02/ethertype 0x8902
When an Accedian device receives this type of LBM frame with its own MAC address as the
destination MAC, it automatically loops the frame back as an LBR, after swapping the source
and destination MAC addresses.
Layer-2 Accedian
These frames are similar to Y.1731 LBM/LBR LBMs, but the ethertype is set to 0x88FC
(Accedian):
LBM: opcode 03/ethertype 0x88FC
LBR: opcode 02/ethertype 0x88FC
As with classic Layer-2 frames, when these frames contain the appropriate MAC destination
address, they are also automatically looped back by any Accedian devices.
Layer-2 Generic
These frames are modified Y.1731 frames where the opcode is changed to 11 (hex 0B) and
the ethertype is 0x88FC (Accedian). When these frames go across the network, they will not
affect any Y.1731-aware device, i.e. they will pass through it transparently.
However, the remote device (Accedian or other brand) must be configured to loop the frames
back and swap the MAC addresses for the source and destination.
Layer-3
Layer-3 test packets are UDP packets, with a user-defined source and destination UDP
port numbers.

In-Service
The In-Service RFC 2544 Generator test being unidirectional, LBM/LBR frames are not used in
this case. When configured for an In-Service Layer 2 throughput test, the RFC 2544 Generator
uses the following types of test frames.
Layer-2
This is configuration uses Y.1731 TST frames.
TST: opcode 37/ethertype 0x8902.
Layer-2 Accedian
These frames are similar to Y.1731 TST frames, but the ethertype is 0x88FC (Accedian). When
these frames go across the network, they will not affect any Y.1731-aware device, i.e. they
will pass through transparently.
Layer-2 Generic
These frames are modified Y.1731 frames, where the opcode is changed to 11 (hex 0B) and
the ethertype is 0x88FC (Accedian). When these frames go across the network, they will not
affect any Y.1731-aware device, i.e. they will pass through it transparently.
Layer-3
Layer-3 test packets are UDP packets, with user-defined source and destination UDP port
numbers.

Appendix 3: Example of RFC 2544 test suite report
********************************************************************
************
* RFC-2544 Conformance testsuite.
********************************************************************
************
General settings:
File name : Test_1
Technician name :
Description : RFC-2544 _test_example
Note :
Working rate : Layer 1
Product name : AMN-1000-TE-S

Unit identifier : G261-3646
Firmware version : sqa_AEN_6.4.3_37025-S2
Operation mode : Standard
Serial number : G261-3646
Assembly : 500-015-07:7:9:0B
********************************************************************
************
Testsuite settings:
Name : Test_1
Description : RFC-2544 _test_example
Throughput test : Enabled
Delay test : Enabled
Frame loss test : Enabled
Back-to-back test: Enabled
Strict failure : Disabled
Verbose report : Disabled
********************************************************************
************
Peer settings:
Testing layer : Layer-2

Peer MAC address : 00:15:AD:00:00:00

NID MAC address : 00:15:AD:11:EE:AF
Ethertype : 0x8902
Opcode : 3
MEG level : 7
********************************************************************
************
Error codes:
Binary search failure (1), Out Of Order or duplicate failure (2),
Frame loss failure (3), Loss of connection with peer (4),
********************************************************************
************
Throughput settings:
Trial duration : 10 secs
Maximum rate : 80 Mbps
Minimum rate : 40 Mbps
Step size : 5 Mbps
Frame loss : 0.0%
Fine stepping : False
Binary duration : 2 secs
Frame sizes : 64 128 256 512 1024 1280 1518 Bytes
Started at : 1970-01-15 18:44:34+00:00
********************************************************************
************
Frame Tx Tx Rx Rx Frame Status
Size rate rate rate rate loss
(bytes) (Mbps) (frames/sec) (Mbps) (frames/sec) (%)
------- --------- ------------ --------- ------------ ------ ------
64 80 119,048 80 119,048 0.0 Pass
128 80 67,568 80 67,568 0.0 Pass
256 80 36,232 80 36,232 0.0 Pass
512 80 18,797 80 18,797 0.0 Pass

1024 80 9,579 80 9,579 0.0 Pass

1280 80 7,692 80 7,692 0.0 Pass
1518 80 6,502 80 6,502 0.0 Pass
********************************************************************
************
Delay settings:
Minimum rate : 40 Mbps
Step size : 5 Mbps
Frame loss : 0.0%
Started at : 1970-01-15 18:46:51+00:00
********************************************************************
************
Frame Tx Minimum Average Maximum Minimum Average Maximum Frame
Status
Size rate delay delay delay DV DV DV loss
(bytes) (Mbps) (usec) (usec) (usec) (usec) (usec) (usec) (%)
------- --------- ------- ------- ------- ------- ------- ------- ---
--- ------
64 80 9 9 10 0 0 0 0.0 Pass
128 80 9 9 10 0 0 0 0.0 Pass
256 80 9 9 10 0 0 0 0.0 Pass
512 80 9 9 10 0 0 0 0.0 Pass
1024 80 11 11 14 0 0 3 0.0 Pass
1280 80 13 13 14 0 0 0 0.0 Pass
1518 80 15 15 16 0 0 0 0.0 Pass
********************************************************************
************
Frame loss settings:


Step size : 5 Mbps
Started at : 1970-01-15 19:01:58+00:00
********************************************************************
************
Frame Tx Tx Rx Rx Frame Status
Size rate rate rate rate loss
(bytes) (Mbps) (frames/sec) (Mbps) (frames/sec) (%)
------- --------- ------------ --------- ------------ ------ ------
64 80 119,048 80 119,048 0.0 Pass
64 75 111,607 75 111,607 0.0 Pass
128 80 67,568 80 67,568 0.0 Pass
128 75 63,345 75 63,345 0.0 Pass
256 80 36,232 80 36,232 0.0 Pass
256 75 33,967 75 33,967 0.0 Pass
512 80 18,797 80 18,797 0.0 Pass
512 75 17,622 75 17,622 0.0 Pass
1024 80 9,579 80 9,579 0.0 Pass
1024 75 8,980 75 8,980 0.0 Pass
1280 80 7,692 80 7,692 0.0 Pass
1280 75 7,212 75 7,212 0.0 Pass
1518 80 6,502 80 6,502 0.0 Pass
1518 75 6,096 75 6,096 0.0 Pass
********************************************************************
************
Back-to-back settings:
Trial duration : 2000 milli-secs
Repeat : 50 times
Started at : 1970-01-15 19:17:14+00:00

********************************************************************
************
Frame Port Average Repeat Status
Size speed Burst
(bytes) (Mbps) (frames)
------- ---------- ------------ ------ ------
64 1000 2,223,903 50 Pass
128 1000 210,344 50 Pass
256 1000 110,635 50 Pass
512 1000 58,641 50 Pass
1024 1000 29,501 50 Pass
1280 1000 23,438 50 Pass
1518 1000 20,487 50 Pass
********************************************************************
************
Ended at : 1970-01-15 19:36:51+00:00
Testsuite status : Completed
********************************************************************
************

Application Note 130 RFC-2544 Testing PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Application Note 130 RFC-2544 Testing PDF

Încărcat de

Drepturi de autor:

Formate disponibile

AN187 V-NID Backup and Restore

AN130 RFC 2544 Testing

May 2017 l Document Revision 4

Document Revision 4 l May 2017 1

Document Revision 4 l May 2017 2

Appendix 2: Types of Test Traffic for RFC 2544 ..................................................... 39

Document Revision 4 l May 2017 3

1.1 Setting up the Traffic Generator

Document Revision 4 l May 2017 4

1.2 Setting up the Traffic Monitor

1.3 Setting up a Test Suite

Document Revision 4 l May 2017 5

We will discuss the following examples:

2.1 Example 1: Out-of-Service Layer-2 Throughput Testing using the

The basic steps involved in out-of-service testing at Layer 2 are:

Document Revision 4 l May 2017 6

This example will use the following test configuration:

Circuit throughput 15 Mbps

Traffic type Layer 2

Frame size 1024 bytes

2.1.1 Get the MAC Address of the Loopback Device PE

2.1.2 Configure the Test Generator PE

Document Revision 4 l May 2017 7

Document Revision 4 l May 2017 8

2.1.3 Perform the Test

Document Revision 4 l May 2017 9

4. Return to the previous screen and click the Stop button.

Document Revision 4 l May 2017 10

Document Revision 4 l May 2017 11

2.2 Example 2: Out-of-Service Layer-3 Throughput Testing using the

2.2.1 Test Configuration

2.2.2 Configure the Generator Unit

Document Revision 4 l May 2017 12

e. Set IPv4 to Manual configuration.

Document Revision 4 l May 2017 13

2.2.3 Configure the Loopback Device

Document Revision 4 l May 2017 14

3. Add a new interface.

Document Revision 4 l May 2017 15

Finally, we need to configure the manual loopback as follows:

Document Revision 4 l May 2017 16

4. Open OAM > Loopback.

Document Revision 4 l May 2017 17

2.2.4 Perform the Test

Document Revision 4 l May 2017 18

2.3 Example 3: In-service Layer-2 Throughput Testing using the

Here are some notes on the test:

Document Revision 4 l May 2017 19

2.3.1 Get the MAC address of the traffic monitor unit

2.3.2 Configure the Bandwidth Regulator on the Traffic Generator Unit

Document Revision 4 l May 2017 20

2. Open Traffic > Regulators > Configuration.

2.3.2.1 Configure the Bandwidth Regulator on the Traffic Generator Unit

Document Revision 4 l May 2017 21

i. Set frame Size type to fixed and Size to 1024 bytes.

2.3.2.2 Configure the Traffic Monitor

Document Revision 4 l May 2017 22

2.3.2.3 Perform the test

Document Revision 4 l May 2017 23

Document Revision 4 l May 2017 24

4. Login to the traffic monitor.

Document Revision 4 l May 2017 25

Document Revision 4 l May 2017 26