ent-an1111-3.66 application note rfc2544 benchmark...

ENT-AN1111-3.66 Application NoteRFC2544 Benchmark Tests

VPPD-04406. 1.0 1/17

Microsemi Corporate HeadquartersOne Enterprise, Aliso Viejo,CA 92656 USAWithin the USA: +1 (800) 713-4113 Outside the USA: +1 (949) 380-6100Fax: +1 (949) 215-4996Email: [email protected]

©2015–2017 Microsemi Corporation. All rights reserved. Microsemi and the Microsemi logo are trademarks of Microsemi Corporation. All other trademarks and service marks are the property of their respective owners.

Microsemi makes no warranty, representation, or guarantee regarding the information contained herein or the suitability of its products and services for any particular purpose, nor does Microsemi assume any liability whatsoever arising out of the application or use of any product or circuit. The products sold hereunder and any other products sold by Microsemi have been subject to limited testing and should not be used in conjunction with mission-critical equipment or applications. Any performance specifications are believed to be reliable but are not verified, and Buyer must conduct and complete all performance and other testing of the products, alone and together with, or installed in, any end-products. Buyer shall not rely on any data and performance specifications or parameters provided by Microsemi. It is the Buyer's responsibility to independently determine suitability of any products and to test and verify the same. The information provided by Microsemi hereunder is provided “as is, where is” and with all faults, and the entire risk associated with such information is entirely with the Buyer. Microsemi does not grant, explicitly or implicitly, to any party any patent rights, licenses, or any other IP rights, whether with regard to such information itself or anything described by such information. Information provided in this document is proprietary to Microsemi, and Microsemi reserves the right to make any changes to the information in this document or to any products and services at any time without notice.

About Microsemi

Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of semiconductor and system solutions for aerospace & defense, communications, data center and industrial markets. Products include high-performance and radiation-hardened analog mixed-signal integrated circuits, FPGAs, SoCs and ASICs; power management products; timing and synchronization devices and precise time solutions, setting the world's standard for time; voice processing devices; RF solutions; discrete components; enterprise storage and communication solutions, security technologies and scalable anti-tamper products; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well as custom design capabilities and services. Microsemi is headquartered in Aliso Viejo, California, and has approximately 4,800 employees globally. Learn more at www.microsemi.com.

mailto:[email protected]

http://www.microsemi.com



ENT-AN1111-3.66 Application Note Revision 1.0 iii

Contents

1 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Revision 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 RFC2544 Benchmark Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1 Quick Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.1.1 OAM-Unaware Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1.2 OAM-Aware Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2 Understanding Microsemi RFC2544 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2.1 RFC2544 Test Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2.2 RFC2544 Test Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3 Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.1 Creating and Viewing an RFC2544 Test Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.2 Starting an RFC2544 Test and View the Test Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4 TT-Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.5 Supported RFC2544 Test and TT-Loop Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

ENT-AN1111-3.66 Application Note Revision 1.0 iv

Figures

Figure 1 OAM-Unaware RFC2544 Test Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Figure 2 OAM-Aware RFC2544 Test Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Figure 3 Test Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Figure 4 RFC2544 Profile Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 5 RFC2544 Profile Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 6 RFC2544 Test Execution Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 7 RFC2544 Test Execution - Executing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 8 RFC2544 Test Execution - Passed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 9 Completed Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 10 Test Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 11 Add a New TT-Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 12 TT-Loop Administration for a Mac-Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

ENT-AN1111-3.66 Application Note Revision 1.0 v

Tables

Table 1 Supported RFC2544 and TT-Loop Configuration Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Revision History

ENT-AN1111-3.66 Application Note Revision 1.0 1

1 Revision History

The revision history describes the changes that were implemented in the document. The changes are listed by revision, starting with the most current publication.

1.1 Revision 1.0Revision 1.0 was the first publication of this document.

RFC2544 Benchmark Tests


2 RFC2544 Benchmark Tests

This document explains the concept of Microsemi RFC2544 benchmark test feature supported by the CEservices software package running on the Microsemi Serval-1 and Serval-1 lite switches.

It describes RFC2544 test profile and test report regarding benchmark testing, and gives examples on how to configure and execute RFC2544 test by using Microsemi's Graphical User Interface (GUI) through the web and the Industrial Command Line Interface (ICLI).

2.1 Quick ConfigurationThe following sections describe how to do quick RFC2544 OAM unaware and aware tests.

2.1.1 OAM-Unaware TestThe following ICLI commands are used to do a quick RFC2544 test on an Ethernet link between port 3 of the two switches connected directly as shown in the following illustration.

Switch 2 in the following illustration should be configured with a Traffic Test Loop (TT-Loop) of MAC type and facility direction. Thus, switch 2 loops back all frames while swapping the SMAC and DMAC fields.

Figure 1 • OAM-Unaware RFC2544 Test Setup

2.1.1.1 On Switch 2Create and enable a TT-Loop on Switch 2.

! Create a facility loop of type mac-loop in port domain on port 3.(config)# traffic-test-loop 1 type mac-loop interface GigabitEthernet 1/3 direction facility domain port! Enable the TT-Loop just created.(config)# traffic-test-loop 1 admin-state enable(config)# end#

2.1.1.2 On Switch 1Create an rfc2544 test profile named MyProfile.

! Create an rfc2544 test profile named MyProfile.(config)# rfc2544 profile MyProfile! Traffic send from port3.(config-rfc2544-profile)# test-interface GigabitEthernet 1/3! Set DMAC, test frame size, only do throughput test and allow frame loss of 30‰.! Leave all other parameters to the default.(config-rfc2544-profile)# dmac 00-00-00-00-00-02(config-rfc2544-profile)# no latency(config-rfc2544-profile)# frame-size 128(config-rfc2544-profile)# throughput allowed-loss 30



(config-rfc2544-profile)# end#

2.1.1.3 Start RFC2544 Test on Switch 1! Start RFC2544 test and save the test report to a file named MyReport.# rfc2544 start MyReport profile MyProfile

! Check test progress.# show rfc2544 reportReport Name Created Status ------------- ------------------------- ------------MYReport 1970-01-03T02:59:16+00:00 In progress

! Check again.# show rfc2544 report

Report Name Created Status ------------- ------------------------- ------------MYReport 1970-01-03T02:59:16+00:00 Succeeded

! Show test report.# show rfc2544 report MyReport***************************************************************************** RFC2544 Conformance Test Suite****************************************************************************Software configuration: Version : CEServices (standalone) Version 3.66 Build xxxx

Build date : 2016-xx-xx T16:57:36+02:00 Code revision : a46c4e5f20b2a6a2ddb59992d258d5b669b75d6d

Report configuration: Report name : MyReport Description :

Overall execution status: Started at : 1970-01-03T02:59:16+00:00 Ended at : 1970-01-03T03:00:18+00:00 Status : Succeeded

Common configuration: Profile name : MyProfile Description : DST is OAM aware : No MEG Level : 7 Egress interface : GigabitEthernet 1/3 Sequence number check: Disabled Dwell time : 2000 milliseconds Type : Port Down-MEP Destination MAC : 00-00-00-00-00-02 Source MAC : 00-01-c1-01-00-03 Frame sizes : 128 Throughput test : Enabled Latency test : Disabled Frame loss test : Disabled Back-to-back test : Disabled

***************************** Throughput Test ****************************



Throughput configuration: Trial duration : 60 seconds Minimum rate : 800 permille Maximum rate : 1000 permille Accuracy : 2 permille Allowed frame loss : 30 permille

Throughput status: Started at : 1970-01-03T02:59:16+00:00 Ended at : 1970-01-03T03:00:18+00:00 Status : Succeeded

Frame Appl. Actual Actual Actual Actual Tx Rx Frame StatusSize TxRate TxRate RxRate TxRate RxRate Frames Frames Loss [bytes] [Mbps] [Mbps] [Mbps] [fps] [fps] [%] ------- ------ ------ ------ ------- ------- ---------- ---------- ----- ------128 999.9 1000.0 1000.0 844659 844659 50679581 50679581 0.0 PASS ********************** Overall Result ************************ Ended at : 1970-01-03T03:00:18+00:00 Status : Succeeded****************************************************************************

2.1.2 OAM-Aware TestThe following ICLI commands are used to do a quick RFC2544 OAM aware test on an Ethernet link between port 3 of the two switches connected directly as shown in the following illustration.

The 3.66 software release supports only OAM-Loop in the EVC domain, so an EVC at the remote switch must be created and an OAM loop in that EVC domain must be created. Then at the RFC2544 source switch configure the RFC2544 test traffic to be VLAN-based with a VLAN tag that matches the EVC at the remote end. With this configuration, traffic received by Switch 2 will be mapped into the EVC, and then get looped by the OAM-loop instance created on that EVC.

Switch 2 in the following illustration should be configured with a Traffic Test Loop (TT-Loop) of OAM type and facility direction, which replies to LMM/DMM with LMR/DMR.

Figure 2 • OAM-Aware RFC2544 Test Setup

2.1.2.1 On Switch 2Create an EVC with Port 3 as the NNI port and Port 1 as the UNI port.

# configure terminal

! Exclude UNI/NNI ports from all VLAN and set PVID to an unused VLAN! UNI is C-port, NNI is S-port(config)# interface GigabitEthernet 1/1(config-if)# switchport hybrid native vlan 4095(config-if)# switchport hybrid allowed vlan none



(config-if)# switchport hybrid port-type c-port(config-if)# switchport mode hybrid(config-if)# exit

(config)# interface GigabitEthernet 1/3(config-if)# switchport hybrid native vlan 4095(config-if)# switchport hybrid allowed vlan none(config-if)# switchport hybrid port-type s-port(config-if)# switchport mode hybrid(config-if)# exit

! EVC configuration! Add EVC 10 using S-VID 1000, disable learning.(config)# vlan 1000(config-vlan)#exit! Setup NNI port(config)# evc 10 vid 1000 ivid 1000 interface GigabitEthernet 1/3! Setup port UNI port(config)# evc ece 1 interface GigabitEthernet 1/1 outer-tag add mode enable vid 1000 evc 10(config-if)# exit

Create and enable a TT-Loop on Switch 2.

! Create a facility loop of type oam-loop in EVC 10 on port 3.(config)# traffic-test-loop 1 type oam-loop interface GigabitEthernet 1/3 direction facility domain evc 10 level 7! Enable the TT-Loop just created.(config)# traffic-test-loop 1 admin-state enable(config)# end#

2.1.2.2 On Switch 1Create an rfc2544 test profile named MyProfile_oam_aware.

# Config terminal(config)# vlan 1000(config-vlan)# exit(config)# interface GigabitEthernet 1/3(config-if)# switchport mode hybrid(config-if)# switchport hybrid port-type s-port (config-if)# exit! Create an rfc2544 test profile named MyProfile_oam_aware.(config)# rfc2544 profile MyProfile_oam_aware(config-rfc2544-profile)# dst-oam-aware(config-rfc2544-profile)# meg-level 7 (config-rfc2544-profile)# test-vlan 1000! Traffic send from port3.(config-rfc2544-profile)# test-interface GigabitEthernet 1/3! Set DMAC, test frame size, only do throughput test and allow frame loss of 30‰.! Leave all other parameters to the default.! DMAC must match the MAC address of the OAM loop on the remote switch. It can ! also be specified during test-start.(config-rfc2544-profile)# dmac 00-01-c1-00-b5-11(config-rfc2544-profile)# no latency(config-rfc2544-profile)# frame-size 128(config-rfc2544-profile)# throughput allowed-loss 30(config-rfc2544-profile)# end#



2.1.2.3 Start RFC2544 Test on Switch 1! Start RFC2544 test and save the test report to a file named MyReport.# rfc2544 start MyReport_oam_aware profile MyProfile_oam_aware

2.2 Understanding Microsemi RFC2544RFC2544 defines a number of tests that can be used to describe the performance characteristics of a network interconnect devices. The purpose is to certify that a Service Level Agreement (SLA) between a customer and a service provider is met. With Microsemi CEservices software running on Carrier Ethernet switch platforms it is possible to do RFC2544 benchmark tests without need for any external test equipment. The test frame generation and checking are all done by the switch hardware and software. The following RFC2544 performance tests are supported:

• Throughput – Measure the maximum rate at which at most a certain percentage of frames are lost (configurable, but usually set to 0.0%).

• Latency – Measure the round-trip time taken by a 1DM frame to exit the traffic generator port and re-enter it. By transmitting more than two 1DM frames in one latency test, it is possible to calculate the delay variation.

• Frame Loss rate – Measure the frame loss at various transmission rates.• Back-to-Back – Measure the maximum number of frames in a burst with minimum inter-frame gaps

that the service network can handle without loss of any frame.

In addition, the software will include a test suite tool that allows for creating, saving, and executing test profiles and captures and reports results. The implementation assumes a setup similar to the following illustration.

Figure 3 • Test Setup

The Local Node acts as frame generator and checker, it is the device where the CEservices software is running and RFC2544 test is executed.

However, for RFC2544 to function properly, the Remote Node must support either an MAC_LOOP which loops the test frames with flipping of DMAC/SMAC of the test frames for OAM (Operations, Administration and Management) unaware test, or an OAM_LOOP which responds to Y.1731 Loopback Message (LBM) and Delay Measurement Message (DMM) PDUS for OAM aware test. If the remote node is a Microsemi Carrier Ethernet device, the loop can be configured by creating a traffic test loop instance as described in TT-Loop, page 16.

2.2.1 RFC2544 Test ProfileTest profile must be prepared before an rfc2544 test can be executed. an rfc2544 test profile contains all the parameters associated with one test, where one test may be a combination of one or more of sub-tests (Throughput, Latency, Frame Loss, Back-to-Back).

Common and sub-test specific parameters in a test profile are listed below:

• Common parameters:• Profile name - Each profile must have a name of up to 32 characters to associate with. Default:

"New profile".• Profile description - A text description up to 128 characters associated with the profile. Default:

blank.

Local Node

Network/Impairment Tool

Remote Node



• DST is OAM aware - The frame types used in the RFC2544 tests are Y.1731 OAM. When "DST is OAM aware" is checked, the device transmits Y.1731 LBM/DMM frames, and expects the remote end to return Y.1731 Loopback Reply (LBR)/Delay Measurement Reply (DMR) frames. When "DST is OAM aware" is unchecked, the device transmits Y.1731 Test Signal (TST)/1DM frames, and expects the remote end to loop this traffic while swapping DMAC and SMAC only.

• MEG (Maintenance Entity Group) level - On which MEG level the RFC2544 test is running. Default: MEG level 7.

• Egress port - On which egress port of the device the RFC2544 test frames are generated and checked. Default: the first port of the device.

• Sequence number check - Generated frame sequence number will be checked. Default: Disabled.

• Dwell time - Number of seconds to wait after each trial for the system to settle before reading statistics from the hardware Default: 2 seconds.

• Type - Select between two types of traffic: Port Down-MEP and VLAN-based Down-MEP. With VLAN-based Down-MEP a configurable VLAN tag will be inserted into the test frames generated. The egress port on which RFC2544 test frames are sent should be a member of the VLAN when VLAN-based Down-MEP is selected. And the port doing traffic loop should also have configured to be a member of the same VLAN.

• VLAN ID - Specify the VLAN ID if VLAN-based Down-MEP is configured.• PCP (Priority Code Point) - Specify the PCP value if VLAN-based Down-MEP is configured.• DEI (Drop Eligible Indicator) -- Specify the DEI value if VLAN-based Down-MEP is configured.• DMAC - Specify the DMAC of the generated frames for both Port-based and VLAN-based

Down-MEP.• Frame size - Specify the frame sizes each test must be repeated with: 64, 128, 256, 512, 1024,

1280, 1518, 2000, and 9600 bytes. Default: all but 9600.• Sub-tests to run - Specify the sub-tests to run in the profile (Throughput, Latency, Frame Loss,

Back-to-Back). Default: throughput and latency. • Parameters for Throughput test:

• Trial duration - The number of seconds that one trial will run. Valid range is [1~1800] seconds. Default: 60 seconds

• Minimum and maximum rate - Specify the maximum and minimum rates that define the range of rates to search in the range of [1~1000] ‰.

• Accuracy - Specify the granularity to search within the minimum and maximum rates define above. All three input parameters are specified in ‰ of the egress port's actual link speed and in the range of [1~1000] ‰ with a granularity of 1‰. Defaults: minimum is 800‰ of link speed, maximum is 1000‰ of link speed, and step size is 2‰ of link speed.

• Allowed frame loss - Specify the allowable frame loss. Valid value is in the range of [0~1000] ‰ with a granularity of 1‰. Default: 0‰.

• Parameters for Latency test:• Trial duration -- Specify the number of seconds that one trial will run. Valid range is [10~1800]

seconds. Default: 120 seconds.• Delay measurement interval -- Specify the number of seconds between each delay

measurement. Valid range is [1~60] seconds in steps of 1 second. Default: 10 seconds.• Allowed frame loss -- Specify the pass criterion of an allowable frame loss. Valid values must be

in the range of [0~10]% with a granularity of 0.1%. Default: 0%.• Parameters for Frame Loss test:

• Trial duration -- Specify the number of seconds that one trial will run. Valid range is [1~1800] seconds. Default: 60 seconds.

• Minimum and maximum rate - Specify the maximum and minimum rates that define the range of rates to search in the range of [1~1000] ‰.

• Rate step - Specify the granularity to search within the minimum and maximum rates define above. All three input parameters must be specified in ‰ of the egress port's actual link speed and be in the range of [1~1000] ‰ with a granularity of 1‰. Defaults: minimum is 800‰ of link speed, maximum is 1000‰ of link speed, and step size is 5‰ of link speed.

• Parameters for Back-to-Back test:• Trial duration -- Specify the number of seconds that one burst will run. Valid range is

[100~10000] milliseconds. Default: 2000 milliseconds.• Trial count -- Specify the number of times the trial will be executed. Valid range is [1~100].

Default: 50.



Note: Up to 16 profiles can be created and saved in the device's flash memory.

2.2.2 RFC2544 Test Reportan rfc2544 test report is generated after an rfc2544 test profile has been executed. The test report is in clear text format and contains all the input parameters defined by the associated test profile as well as all the measurement results. The test report is used to certify to the customer that an SLA is met or not.

The last 10 test reports are kept in the flash memory of the device. They can be viewed through ICLI or be downloaded to a PC through TFTP.

Below is an example of a test report names myreport which has been generated after a test profile myprofile was executed.

The first part of the test report lists the general information of the software version, test report name, execution date/time and status. It also lists the associated test profile information with all the common configuration parameters of that test profile.

***************************************************************************** RFC2544 Conformance Test Suite****************************************************************************Software configuration: Version : CEServices (standalone) Version 3.66 Build xxxx Build date : 2016-xx-xx T16:57:36+02:00 Code revision : a46c4e5f20b2a6a2ddb59992d258d5b669b75d6d

Report configuration: Report name : myreport Description :


Common configuration: Profile name : myprofile Description : enable all sub-tests DST is OAM aware : No MEG Level : 7 Egress interface : GigabitEthernet 1/1 Sequence number check: Enabled Dwell time : 2 seconds Type : Port Down-MEP Destination MAC : 00-00-00-00-00-04 Source MAC : 00-01-c1-00-b4-21 Frame sizes : 64 128 256 512 1024 1280 1518 2000 Throughput test : Enabled Latency test : Enabled Frame loss test : Enabled Back-to-back test : Enabled

Following are the general information of the configurations and test results of each RFC2544 sub-test.

The test report for the Throughput sub-test lists the configuration parameters for the throughput test and the execution date/time and status. Each row is the measurement result of each throughput test trial for a special frame size enabled through the test profile. The measured throughput as well as the frame transmission, the reception rates, the number of frames been sent and received for each trial, and the frame loss rate are listed.

******************************* Throughput Test ****************************Throughput configuration:



Trial duration : 60 seconds Minimum rate : 800 permille Maximum rate : 1000 permille Rate step : 2 permille Allowed frame loss : 0 permille

Throughput status: Started at : 1970-01-01T22:18:29+00:00 Ended at : 1970-01-01T22:26:45+00:00 Status : Succeeded

Frame Appl. Actual Actual Actual Actual Tx Rx Frame StatusSize TxRate TxRate RxRate TxRate RxRate Frames Frames Loss[bytes] [Mbps] [Mbps] [Mbps] [fps] [fps] [%]------- ------ ------ ------ ------- ------- ---------- ---------- ----- ------ 64 994.5 954.4 954.4 1420330 1420330 85219859 85219859 0.0 PASS 128 998.4 970.5 970.5 819694 819694 49181666 49181666 0.0 PASS 256 996.9 985.6 985.6 446411 446411 26784716 26784716 0.0 PASS 512 996.7 990.1 990.1 232638 232638 13958319 13958319 0.0 PASS 1024 988.0 942.5 942.5 112848 112848 6770897 6770897 0.0 PASS 1280 999.6 995.3 995.3 95703 95703 5742195 5742195 0.0 PASS 1518 959.7 941.2 941.2 76502 76502 4590163 4590163 0.0 PASS 2000 998.6 979.3 979.3 60602 60602 3636132 3636132 0.0 PASS

The test report for the Latency sub-test lists the configuration parameters for the latency test and the execution date/time and status. Each row lists the measured delay and delay variation with a special frame size enabled through the test profile. It also lists the frame sending rate and also the number of frames been sent and received for each trial.

********************************* Latency Test *****************************Latency configuration: Trial duration : 120 seconds Delay meas. interval : 10 seconds Allowed frame loss : 0 permille

Latency status: Started at : 1970-01-01T22:26:45+00:00 Ended at : 1970-01-01T22:43:01+00:00 Status : Succeeded

Frame Tx Tx Rx Min/Avg/Max Min/Avg/Max StatusSize Rate Frames Frames Delay Delay Var. [bytes] [Mbps] [usecs] [usecs] ------- ------ ---------- ---------- ----------------- ----------------- ----- 64 999.7 178532323 178532323 3/3/3 0/0/0 PASS 128 999.7 101329475 101329475 3/3/3 0/0/0 PASS 256 999.7 54336108 54336108 4/4/4 0/0/0 PASS 512 999.7 28189582 28189582 6/6/6 0/0/0 PASS 1024 999.7 14364885 14364885 10/10/10 0/0/0 PASS 1280 999.7 11536065 11536065 12/12/12 0/0/0 PASS 1518 999.7 9750940 9750940 14/14/14 0/0/0 PASS 2000 999.7 7424184 7424184 13/18/18 0/0/5 PASS

The test report for the Frame Loss sub-test lists the configuration parameters for the Frame Loss test and the execution date/time and status. Each row lists the frame loss rate with a special frame size enabled through the test profile. It also lists the frame sending and receiving rates and also the number of frames been sent and received for each trial.

******************************* Frame Loss Test *****************************Frame loss configuration: Trial duration : 60 seconds



Minimum rate : 800 permille Maximum rate : 1000 permille Rate step : 5 permille

Frame Loss status: Started at : 1970-01-01T22:43:01+00:00 Ended at : 1970-01-01T22:59:33+00:00 Status : Succeeded

Frame Tx Rx Tx Rx Tx Rx Frame StatusSize Rate Rate Rate Rate Frames Frames Loss[bytes] [Mbps] [Mbps] [fps] [fps] [%]------- ------ ------ ------- ------- ---------- ---------- ----- ------ 64 999.9 999.9 1488064 1488064 89283848 89283848 0.0 PASS 64 994.9 994.9 1480630 1480630 88837833 88837833 0.0 PASS 128 999.9 999.9 844581 844581 50674865 50674865 0.0 PASS 128 994.9 994.9 840361 840361 50421665 50421665 0.0 PASS 256 999.9 999.9 452890 452890 27173435 27173435 0.0 PASS 256 994.9 994.9 450629 450629 27037742 27037742 0.0 PASS 512 999.9 999.9 234958 234958 14097535 14097535 0.0 PASS 512 994.9 994.9 233786 233786 14027162 14027162 0.0 PASS 1024 999.9 999.9 119729 119729 7183796 7183796 0.0 PASS 1024 994.9 994.9 119133 119133 7148017 7148017 0.0 PASS 1280 999.9 999.9 96152 96152 5769126 5769126 0.0 PASS 1280 994.9 994.9 95672 95672 5740378 5740378 0.0 PASS 1518 999.9 999.9 81272 81272 4876360 4876360 0.0 PASS 1518 994.9 994.9 80867 80867 4852071 4852071 0.0 PASS 2000 999.9 999.9 61879 61879 3712772 3712772 0.0 PASS 2000 994.9 994.9 61571 61571 3694279 3694279 0.0 PASS

The test report for the Back-to-Back sub-test lists the configuration parameters for the Back-to-Back test and the execution date/time and status. Each row lists the maximum number of frames in a burst with minimum inter-frame gaps that the remote node can handle without loss of any frame with specific frame size enabled through the test profile. It also lists the frame sending and receiving rates for each trial.

****************************** Back-to-back Test ****************************Back-to-back configuration: Trial duration : 2000 milliseconds Trial count : 50

Back-to-back status: Started at : 1970-01-01T22:59:33+00:00 Ended at : 1970-01-01T23:26:13+00:00 Status : Succeeded

Frame Appl. Actual Actual Actual Actual Tx Rx Frame StatusSize TxRate TxRate RxRate TxRate RxRate Frames Frames Loss[bytes] [Mbps] [Mbps] [Mbps] [fps] [fps] [%]------- ------ ------ ------ ------- ------- ---------- ---------- ----- ------ 64 994.5 953.7 953.7 1419259 1419259 2838518 2838518 0.0 PASS 64 994.5 953.7 953.7 1419302 1419302 2838605 2838605 0.0 PASS 64 994.5 953.7 953.7 1419286 1419286 2838573 2838573 0.0 PASS 64 994.5 953.7 953.7 1419285 1419285 2838570 2838570 0.0 PASS 64 994.5 953.7 953.7 1419288 1419288 2838577 2838577 0.0 PASS 64 994.5 953.7 953.7 1419302 1419302 2838604 2838604 0.0 PASS 64 994.5 953.7 953.7 1419268 1419268 2838536 2838536 0.0 PASS 64 994.5 953.7 953.7 1419253 1419253 2838507 2838507 0.0 PASS 64 994.5 953.7 953.7 1419282 1419282 2838565 2838565 0.0 PASS 64 994.5 953.7 953.7 1419297 1419297 2838595 2838595 0.0 PASS 64 994.5 953.7 953.7 1419290 1419290 2838580 2838580 0.0 PASS



64 994.5 953.7 953.7 1419327 1419327 2838654 2838654 0.0 PASS 64 994.5 953.7 953.7 1419334 1419334 2838668 2838668 0.0 PASS

At the end of the test report provides the information of the date/time when the test profile has been finished execution and the overall result of the test.

******************************** Overall Result ***************************** Ended at : 1970-01-01T23:26:13+00:00 Status : Succeeded****************************************************************************

2.3 Configuration ExamplesIn this section, configuration examples for an rfc2544 test are given according to the concepts described in Quick Configuration, page 2 and Understanding Microsemi RFC2544, page 6.

Note: It is recommended to do a restore to default before starting to configure any of the examples in the following sections.

# reload defaults#

2.3.1 Creating and Viewing an RFC2544 Test Profile To create and configure Test profile, perform the following steps.

1. Click Configuration > Traffic Test > RFC2544 > Profiles, and then click the Add New Profile button. The configuration page for the new profile opens as shown in the following illustration.

Figure 4 • RFC2544 Profile Configuration Management



2. Under the Common Parameters section, set up Profile Name, Description, Egress Port, Sequence Number Check, and DMAC as shown in the previous illustration.

3. Setup Frame Size to include 64 only as shown in the previous illustration.4. Under the Throughput Test Parameters section, setup Enable, Trial Duration, and Allowed

Frame Loss as shown in the previous illustration.5. Clear Enable for Latency Test Parameters as shown in the previous illustration.6. Click Save.

The equivalent ICLI commands are:

! Go to configuration mode.# configure terminal

! Create an rfc2544 test profile and name it "myprofile".! If a profile named "myprofile" already exists, the commands that follows will! modify the existing profile instead of creating a new profile.(config)# rfc2544 profile myprofile

! Add a description to the profile.(config-rfc2544-profile)# description This is an rfc2544 test profile example

! Configure the egress port on which test frames are generated.! In this example we use egress port 1(config-rfc2544-profile)# test-interface GigabitEthernet 1/1

! Configure DMAC address for the test frames(config-rfc2544-profile)# dmac 00-00-00-00-00-10

! We will only enable throughput test in this example. Since both throughput and ! Latency tests are enabled by default so we only need to disable latency test.(config-rfc2544-profile)# no latency

! We only test with 64byte frame size(config-rfc2544-profile)# frame-size 64

! We enable sequence number checking for the tests.(config-rfc2544-profile)# sequence-check

! We change the duration of the throughput test to 30 seconds and the allowed frame loss to be 20‰.(config-rfc2544-profile)# throughput duration 30 allowed-loss 20

! We then keep all the other parameters as their default and finish the profile(config-rfc2544-profile)# end#

The RFC2544 profile, myprofile, has now been created and saved. We can check the RFC2544 profile summary:

! Show all the RFC2544 profiles that saved in the flash.# show rfc2544 profileProfile Name Description --------------- -------------------------------------- Myprofile This is an rfc2544 test profile example

We can also view the content of a profile by appending the profile name to the show rfc2544 command:

# show rfc2544 profile myprofileCommon configuration: Profile name : myprofile Description : This is an rfc2544 test profile example



DST is OAM aware : No MEG Level : 7 Egress interface : GigabitEthernet 1/1 Sequence number check : Enabled Dwell time : 2000 milliseconds Type : Port Down-MEP Destination MAC : 00-00-00-00-00-10 Source MAC : 00-01-c1-00-b4-21 Frame sizes : 64 Throughput test : Enabled Latency test : Disabled Frame Loss test : Disabled Back-to-Back test : Disabled

Throughput configuration: Trial duration : 30 seconds Minimum rate : 800 permille Maximum rate : 1000 permille Rate step : 2 permille Allowed frame loss : 20 permille

#

To view or update an RFC2544 profile using the web GUI, click the profile name (myprofile in this case). The profile can be deleted by clicking the Delete button.

Figure 5 • RFC2544 Profile Overview

The equivalent CLI commands are:

# configure terminal(config)# no rfc2544 profile myprofile

2.3.2 Starting an RFC2544 Test and View the Test ReportTo ensure RFC2544 functions properly, the Remote Node (as shown in Figure 1, page 2) must support looping of the test frames with flipping of DMAC/SMAC of the test frames. If the remote node is a Microsemi Serval-1 switch the loop can be created by a traffic loop instance as described in TT-Loop, page 16.

An RFC2544 test is triggered by starting the RFC2544 profile and specify the report name.

! Start RFC2544 test profile "myprofile" and specify the test report named ! "myreport"# rfc2544 start myreport profile myprofile

To execute an RFC2544 test through the web GUI, perform the following steps.

1. Click the Start New Test button.2. Click Configuration > Traffic Test > RFC2544 > Report, and specify a report name and select a

test profile as shown in the following illustration.



Figure 6 • RFC2544 Test Execution Page

3. Click Run.

It also allows for adding a short description to the test report and overriding the destination MAC address specified in the profile. DMAC is used by the network in between the RFC2544 source and destination switch so that test traffic is forwarded properly back and forth between the source and destination switch. DMAC is matched against the OAM-loop in OAM-aware test so it must be configured with the MAC address of the OAM-loop instance created at the remote end. If left as a zero MAC address, no overriding will take place, and the DMAC specified in the profile will be used.

Adding description and overriding DMAC at test time using CLI are also allowed. The following example initiates an rfc2544 test and generates test report named myreport with description as just for a demo. The DMAC of the test frames for this test is 00-00-00-00-00-01 instead of the DMAC specified in the profile.

! Start RFC2544 test profile "myprofile" and generate a test report named ! "myreport". There will be a description "just for a demo" in the test report. ! DMAC in the profile will be overridden by 00-00-00-00-00-01 for this test.# rfc2544 start myreport profile myprofile dmac 00-00-00-00-00-01 desc just for a demo

The profile will be executed immediately afterward. By showing all the test reports saved in the flash, we can get to know if the RFC2544 test we just triggered is still ongoing or have finished.

# show rfc2544 reportReport Name Created Status ------------ ------------------------- ------------- myreport 1970-01-02T00:12:49+00:00 In progress

The In Progress status indicates that the test is still ongoing. When the status changes to Succeeded or Failed, it indicates that the test is finished and a report has been generated. At this moment, the content of the report can be viewed by appending the report name to the show rfc2544 command.

# show rfc2544 report myreport***************************************************************************** RFC2544 Conformance Test Suite****************************************************************************Software configuration: Version : CEServices (standalone) Version 3.66 Build XXXX Build date : 2016-xx-xx T16:57:36+02:00 Code revision : a46c4e5f20b2a6a2ddb59992d258d5b669b75d6d

Report configuration: Report name : myreport Description :


Common configuration: Profile name : myprofile



Description : This is an RFC2544 test profile example MEG Level : 7 Egress interface : GigabitEthernet 1/1 Sequence number check: Enabled Dwell time : 2 seconds...(Report is partially shown due to space constraints.)

To know more about the format of a test report, see RFC2544 Test Report, page 8.

An ongoing test can be stopped by the following command specified with the report name:

# rfc2544 stop myreport

A test report can be deleted using rfc2544 delete command by specifying the report name:

# rfc2544 delete myreport

To monitor the test progress through web GUI, perform the following steps.

1. On the top-right corner of the RFC2544 Reports Overview page, click the Refresh button (or check Auto-refresh). The status of the ongoing test will be shown as Executing as shown in the previous illustration.

Figure 7 • RFC2544 Test Execution - Executing

2. When the test is finished the status will be either Passed or Failed as shown in the following illustration.

Figure 8 • RFC2544 Test Execution - Passed

3. To stop an ongoing test execution, click the Stop button.

Figure 9 • Completed Test

4. To display the test report as the test execution completes, click the report name (myreport in this case).



Figure 10 • Test Report

5. Click Delete to delete a test report or click Save to save it as a text file.

2.4 TT-LoopBecause the dual end test is not supported by the software revision 3.66, TT-Loop must be enabled at the destination switch before any RFC2544 test can be started. A test loop matches frames it receives at certain point of the switch with the configured parameter and sends the frames back, so that the RFC2544 test SRC can gather statistics for the test.

To create configure a TT-Loop, perform the following steps.

1. Click Configuration > Traffic Test > Loop, the Traffic Test Loop page opens as shown in the following illustration.

Figure 11 • Add a New TT-Loop



2. To create a new TT-Loop, click Add New TT-LOOP button and enter the following parameters:• Instance ID: The ID of the new TT-Loop. Once a TT-Loop is created the parameters of it can be

modified by clicking the ID.• Domain: Selection between Port, EVC, or VLAN domain:

• Port: A TT-Loop in the Port Domain so it matches all received frames on that port. Flow presents the port number used in the TT-Loop.

• EVC: A TT-Loop in the EVC Domain, where Flow is an EVC number. The EVC must be created before configuring the TT-Loop, and the TT-Loop only matches frames received on the configured EVC.

• VLAN: A TT-Loop in the VLAN Domain, where Flow is a VLAN. The VLAN must be created before configuring the TT-Loop, and the TT-Loop only matches frames received on the configured VLAN.

• Flow: Depending on the selection of domain. Port number if domain is Port, EVC ID if domain is EVC, VLAN ID if domain is VLAN.

• Type: Selection between Mac-Loop and Oam-Loop. A Mac-Loop matches all frames belong to the configured domain and swaps the SMAC and DMAC field before looping them back. An Oam-Loop is actually a MEP which matches and responds to OAM frames intended for him. Peer-mac and MEG-level must be configured correctly for an Oam-Loop to work. The Oam-Loop responds to a LBM frame with a LBR frame and a DMM frame with a DMR frame.

• Direction: Selection between Facility loop (looping is done from ingress to egress) and Terminal loop (looping is done from egress to ingress). Remember that for the Serval-1 switch the loop_port version of the software needs to be used if the support for the terminal loop is needed.

• Residence Port: The port where the TT-Loop is resident. For a EVC loop the port must be a port in the EVC. For a VLAN loop the port must be the VLAN's member.

3. Click Save.4. Click the TT-Loop instance ID, on the Traffic Test Loop Instance Configuration page perform the

following tasks.• Give the instance a name.• Enable the TT-Loop instance.

Figure 12 • TT-Loop Administration for a Mac-Loop

The equivalent ICLI commands are:

(config)# traffic-test-loop 1 type mac-loop interface GigabitEthernet 1/1 direction facility domain port(config)# traffic-test-loop 1 admin-state enable

Note: A Mac-loop is OAM-unaware. It just loops back all the received frames and swaps the SMAC and the SMAC address for any received frame. Peer-mac and MEG level are irrelevant to a mac-loop. But an Oam-loop is different, an Oam-loop is actually a real MEP. It only responds to OAM frames that are destined to it, so the MEG level and peer-mac must be configured correctly for an Oam-loop. The software creates a special MEP automatically after an Oam-loop is enabled. The peer-mac address of the Oam-loop can be found out, which is required to start a Y.1564 test.



The 3.66 software only supports OAM-loops in the EVC domain so an EVC at the remote switch should be created and an OAM-loop in that EVC domain can be created afterwards. Then at the RFC2544 source switch, configure the RFC2544 test traffic to be VLAN based with a VLAN tag that matches the EVC at the remote end. When the test traffic is received by the remote end, it will be mapped into that EVC and the OAM-loop instance created on the EVC will take care of responding to the OAM traffic.

2.5 Supported RFC2544 Test and TT-Loop CombinationsThe following table lists the supported RFC2544 test and TT-Loop combinations.

Table 1 • Supported RFC2544 and TT-Loop Configuration Combinations

RFC2544 TT-Loop

Test TrafficDST is OAM aware Type Domain Type Direction

No Port-based Down-MEP Port Mac-Loop Facility Y.1731 TST/1DM

No VLAN-based Down-MEP VLAN Mac-Loop Facility Y.1731 TST/1DM

Yes VLAN-based Down-MEP EVC Oam-Loop Facility Y.1731 LBM/DMM

ent-an1111-3.66 application note rfc2544 benchmark...

Documents