Y.1564 Software Configuration Guideww1.microchip.com/downloads/en/Appnotes/ENT-AN1124_VPPD... · 2019-10-29 · Software configuration: Version : CEServices (standalone) dev-build

.ENT-AN1124-4.6

Application NoteY.1564 Software Configuration Guide

Released

September 2018

Contents

1 Revision History.................................................................................................................................1

2 Software Configuration Y.1564..........................................................................................................22.1 Quick Configuration Guide..................................................................................................................................22.2 Create EVC for Both the Switches.......................................................................................................................32.3 Create Y.1564 Test Profile on Switch1.................................................................................................................32.4 Configure Traffic Test Loop (TT-Loop).................................................................................................................42.5 Start Y.1564 Test on Switch1...............................................................................................................................4

2.5.1 Y.1564 Test with OAM Aware Traffic....................................................................................................92.6 Understanding ITU-T Y.1564.............................................................................................................................102.7 Y.1564 Test Types..............................................................................................................................................12

2.7.1 CIR Configuration Test........................................................................................................................132.7.2 EIR Configuration Test........................................................................................................................132.7.3 Traffic Policing Test.............................................................................................................................132.7.4 Service Performance Test...................................................................................................................13

2.8 Y.1564 Test Profile.............................................................................................................................................132.8.1 Common Parameters.........................................................................................................................142.8.2 SAC.....................................................................................................................................................162.8.3 CIR Configuration Test Parameters....................................................................................................162.8.4 EIR Configuration Test Parameters.....................................................................................................17

2.9 Start Y.1564 Test................................................................................................................................................202.10 TT-Loop Configuration....................................................................................................................................222.11 Y.1564 Test Report and Troubleshooting........................................................................................................24

2.11.1 Configurations of Y.1564 Test...........................................................................................................242.11.2 Overall Status and Table Legends....................................................................................................252.11.3 CIR Test Results and Troubleshooting..............................................................................................262.11.4 EIR Test Results and Troubleshooting..............................................................................................292.11.5 Policer Test Results..........................................................................................................................322.11.6 PerformanceTest..............................................................................................................................33

2.12 Saving the Report...........................................................................................................................................342.13 Supported Y.1564 Test and Loop Parameters.................................................................................................34

iiVPPD-04305 ENT-AN1124-4.6 Application Note Revision 1.1

Contents

Figures

Figure 1 • Y.1564 OAM Unaware Test with Mac-Loop..........................................................................................................2Figure 2 • OAM Aware Test and OAM-Loop.........................................................................................................................9Figure 3 • Y.1564 Test Flow Model at SRC..........................................................................................................................11Figure 4 • Traffic Test Loop at DST—Facility Loop..............................................................................................................11Figure 5 • Traffic Test Loop at DST—Terminal Loop............................................................................................................11Figure 6 • Test Flow Model at SRC—Egress Direction........................................................................................................12Figure 7 • Y.1564 Test Flow Model at SRC—Ingress Direction (Serval-1 Switch)................................................................12Figure 8 • High-Level Service Activation Methodology......................................................................................................12Figure 9 • Y.1564 Profile Overview Web Page....................................................................................................................14Figure 10 • Common Parameters.......................................................................................................................................14Figure 11 • Service Acceptance Criteria.............................................................................................................................16Figure 12 • CIR Configuration Test Parameters...................................................................................................................16Figure 13 • EIR Configuration Test Parameters...................................................................................................................17Figure 14 • Policer Mode of EVC CoS ID Policer.................................................................................................................18Figure 15 • Traffic Policing Test Parameters.......................................................................................................................18Figure 16 • Performance Test Parameters..........................................................................................................................18Figure 17 • Y.1564 Report Overview Page..........................................................................................................................20Figure 18 • Y.1564 Test Start Page......................................................................................................................................20Figure 19 • Y.1564 Test Report Preview Window...............................................................................................................21Figure 20 • Y.1564 Test Execution Status............................................................................................................................22Figure 21 • Add a New Traffic Test Loop.............................................................................................................................22Figure 22 • Enable a Mac-Loop..........................................................................................................................................23Figure 23 • Software Create MEP for Oam-Loop................................................................................................................23Figure 24 • Oam-Loop Instance Configuration Page..........................................................................................................24Figure 25 • Overall Status and Table Legends....................................................................................................................26Figure 26 • CIR Configuration Test......................................................................................................................................26Figure 27 • EVC Statistics....................................................................................................................................................27Figure 28 • Creating an MEP..............................................................................................................................................29Figure 29 • Configuring an MEP.........................................................................................................................................29Figure 30 • MEF Policer Configuration...............................................................................................................................30Figure 31 • Ingress Map Configuration...............................................................................................................................31Figure 32 • Egress Map Configuration................................................................................................................................31Figure 33 • Egress Map Key Configuration.........................................................................................................................32Figure 34 • Ingress Map Key Configuration........................................................................................................................32

iiiVPPD-04305 ENT-AN1124-4.6 Application Note Revision 1.1

Figures

Tables

Table 1 • Common Parameters...........................................................................................................................................14Table 2 • Service Acceptance Criteria Parameters..............................................................................................................16Table 3 • CIR Configuration Test Parameters......................................................................................................................17Table 4 • EIR Configuration Test Parameters......................................................................................................................17Table 5 • Traffic Policing Test Parameters...........................................................................................................................18Table 6 • Performance Test Parameters.............................................................................................................................19Table 7 • Traffic Test Loop Parameters...............................................................................................................................22Table 8 • EVC Statistics and Troubleshooting for OAM Aware Test (DST-is-OAM-Aware Checked)....................................27Table 9 • EVC Statistics and Trouble Shooting for OAM Unaware Test (DST-is-OAM-Aware Unchecked)..........................28Table 10 • EVC Statistics and Troubleshooting for OAM Aware Test (DST-is-OAM-Aware Checked)..................................35

ivVPPD-04305 ENT-AN1124-4.6 Application Note Revision 1.1

Tables

1 Revision History

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

Revision 1.1Revision 1.1 was published in September 2018. In revision 1.1 of this document, the Saving the Reportsection was added. For more information, see Saving the Report on page 34.

Revision 1.0Revision 1.0 was published in November 2016. It was the first publication of this document.

1VPPD-04305 ENT-AN1124-4.6 Application Note Revision 1.1

Revision History

2 Software Configuration Y.1564

This application note describes the Y.1564 test feature supported by theMicrosemi switch software runningon the Microsemi Carrier Ethernet switches. It explains the basic concepts of Y.1564 testing and how toexecute Y.1564 test on the Microsemi Carrier Ethernet switches. Examples for configuration and executionof the Y.1564 test, through either theweb graphical user interface (GUI) or industrial command line interface(ICLI), are provided.

2.1 Quick Configuration GuideThe following ICLI commands complete a quick Y.1564 test on an Ethernet private line (EPL) Ethernet virtualconnection (EVC) between two switches directly connected. Specifically, the following illustration showsthe setup for the Y.1564 test with operations, administration, and management (OAM) unaware test traffic(DST-OAM-Aware is unchecked in the test profile) and a mac-loop configured at Switch 2. It also shows thesetup up for a Y.1564 OAM aware test (DST-OAM-Aware is checked in the test profile) and an OAM-loopis configured at Switch 2.

Figure 1 • Y.1564 OAM Unaware Test with Mac-Loop

Port 1 is the user network interface (UNI) port for both switches. Port 3 is the network-to-network interface(NNI) port. The single-ended test is used with Switch 1 configured as Y.1564 SRC and Switch 2 configuredas a remote traffic test loop.


Software Configuration Y.1564

2.2 Create EVC for Both the SwitchesThe following commands create the EVC on which Y.1564 tests are executed. The EVC configurations arethe same for both Switch 1 and Switch 2, but the metro Ethernet forum (MEF) policers are only configuredand enabled on Switch 1 so that the test frameswill not be dropped or re-colored at the remote loop switch.

#configure terminal! Disable STP and LLDP on UNI/NNI ports(config)# interface GigabitEthernet 1/1,3(config-if)# no lldp receive(config-if)# no lldp transmit(config-if)# no spanning-tree(config-if)# exit! 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! QOS map! Ingress mapping(config)# qos map ingress 20(config-qos-map-ingress)# key pcp-dei(config-qos-map-ingress)# action class dpl(config-qos-map-ingress)# map pcp 0 dei 1 to dpl 1(config-qos-map-ingress)# map pcp 1 dei 0 to class 1(config-qos-map-ingress)# map pcp 1 dei 1 to class 1 dpl 1(config-qos-map-ingress)# exit! Egress mapping(config)# qos map egress 30(config-qos-map-egress)# key class-dpl(config-qos-map-egress)# action dei pcp(config-qos-map-egress)# map class 0 dpl 1 to dei 1(config-qos-map-egress)# map class 1 dpl 0 to pcp 1(config-qos-map-egress)# map class 1 dpl 1 to dei 1 pcp 1(config-qos-map-egress)# exit! EVC configuration! Add EVC 10 using S-VID 1000, disable learning.(config)# evc 10 vid 1000 ivid 1000 nni ingress-map 20 egress-map 30! Setup port role for UNI(config)# interface GigabitEthernet 1/1(config-if)# evc rule 10 role root(config-if)# exit! Setup port role for NNI(config)# interface GigabitEthernet 1/3(config-if)# evc rule 10 role nni(config-if)# exit! Add ECE 1 mapping all frames on UNI to EVC 10(config)# evc ece 1 interface GigabitEthernet 1/1 evc 10 ingress-map 20! Enable MEF policers for EVC 10! Only configured on switch1(config)# interface GigabitEthernet 1/1(config-if)# evc policer 10 class 0 enable rate-type line cir 1000 eir 1000(config-if)# evc policer 10 class 1 enable rate-type line cir 2000 eir 2000(config-if)# end#

2.3 Create Y.1564 Test Profile on Switch1The following commands create two test profiles on Switch 1. The test profile namedmyprofile-OAMunawareuses customer-simulated traffic. The test profile namedmyprofile-OAMaware uses Y.1731 loopbackmessage(LBM) and delay measurement message (DMM) traffic.



For the myprofile-OAMunaware test, select customer-simulated traffic and allow up to 30 % frame loss.Only enable the committed information rate (CIR) test. Keep all the other parameters at their default values.

# configure terminal! Create a test profile named myprofile-OAMunaware(config)# y1564 profile myprofile-OAMunaware! Use customer-simulated traffic, allow up to 30‰ frame loss! Only enable CIR test(config-y1564-profile)# traffic-type customer-simulated(config-y1564-profile)# acceptable-flr 30(config-y1564-profile)# no eir-test(config-y1564-profile)# no traffic-policing-test(config-y1564-profile)# no performance-test(config-y1564-profile)# exit(config)#

For the myprofile-OAMaware test, select dst-OAM-aware and Y.1731 OAM traffic, setting maintenanceentity group (MEG) level to 7. Allow up to 30 % frame loss and only enable the CIR test. Keep all otherparameters at their default value.

! Create a test profile named myprofile-OAMaware(config)# y1564 profile myprofile-OAMaware! Set DST is OAM aware,use y1731 LBM and DMM traffic,and MEG level 7! Allow upto 30‰ frame loss and only enable CIR test(config-y1564-profile)# dst-oam-aware(config-y1564-profile)# traffic-type oam(config-y1564-profile)# meg-level 7(config-y1564-profile)# acceptable-flr 30(config-y1564-profile)# no eir-test(config-y1564-profile)# no traffic-policing-test(config-y1564-profile)# no performance-test(config-y1564-profile)# end#

2.4 Configure Traffic Test Loop (TT-Loop)To match the two test profiles on Switch 1, create two TT-Loops on Switch 2. For the OAMunaware testprofile using customer-simulated traffic, create a facility loop of type mac-loop on Port 3 (NNI port on theEVC) of Switch 2 on EVC 10.

# configure terminal! Create TT-Loop instance 1 for OAM unaware test! mac-loop on port 3 evc domain with evc id 10(config)# traffic-test-loop 1 type mac-loop interface GigabitEthernet 1/3direction facility domain evc 10

For the OAM aware test using Y.1731 LBM and DMM traffic, create an oam-loop on the EVC. The loopshould be a terminal loop on the UNI port for a Jaguar2/Serval-2/Serval-T device, or a facility loop on theNNI port for a Serval-1 device.

! Create TT-Loop instance 2 for OAMaware test! oam-loop on port 1 evc domain with evc id 10 direction terminal(config)# traffic-test-loop 2 type oam-loop interface GigabitEthernet 1/1direction terminal domain evc 10 level 7! Set the oam-loop in subscriber "ALL" domain(config)# traffic-test-loop 2 subscribe all(config)# end#

2.5 Start Y.1564 Test on Switch1Connect an Ethernet cable between Port 3 of the two switches then start the Y.1564 test on Switch 1.



The following commands enable the TT-Loop instance 1 and start Y.1564 test with profile namedmyprofile-OAMunaware.

On Switch 2:

# configure terminal! Enable tt-loop instance 1(facility loop, mac-loop)(config)# traffic-test-loop 1 admin-state enable(config)# end#



On Switch 1:



# configure terminal! Test with two test flows for COSID 0 and 1 of EVC 10(config)# y1564 start myreport-OAMunaware profile myprofile-OAMunaware evc 10 ece 1! Check y1564 test progress(config)# do show y1564 report

Report Name Created Status--------------------- ------------------------- -----------------myreport-OAMunaware 1970-01-01T04:12:21+00:00 In progress

! Check y1564 test progress again(config)# do show y1564 report

Report Name Created Status-------------------- ------------------------- -----------------myreport-OAMunaware 1970-01-01T04:12:21+00:00 Succeeded

! View test report after test complete

(config)# do show y1564 report myreport-OAMunaware

****************************************** Y.1564 SAM Test ******************************************************************Software configuration:Version : CEServices (standalone) dev-build by [email protected] 2016-05-23T10:23:56+02:00 Config:ce_serval2 SDK:v01.66-smb Build 772Build date : 2016-05-23T10:23:56+02:00Code revision : df88d21+Profile configuration:Profile name : myprofile-OAMunawareDescription : Measurement type : Single-ended (DST loops traffic)DST is OAM aware : NoBackground traffic type : Simulated customer trafficDelay measurement type : Y.1731 1DMMEG Level : 7Dwell time : 500 msecsFrame size : 512 (EMIX=d)User-defined frame size : 2000 bytesCIR configuration test : EnabledEIR configuration test : DisabledTraffic policing test : DisabledService performance test : DisabledAcceptable FLR : 30 permilleAcceptable FTD : Check disabledAcceptable FDV : Check disabledReport configuration:Report name : myreport-OAMunawareDescription :Peer MAC : 00-00-00-00-00-01EVC ID : 10ECE IDs on EVC : 1ECE IDs under test : 1Configuration for UNI interface GigabitEthernet 1/1:Link state : DownSpeed : 1000 MbpsMTU : 10240 bytesMAC : 00-01-c1-01-00-01Configuration for NNI interface GigabitEthernet 1/3:Link state : UpSpeed : 1000 MbpsMTU : 10240 bytesConfiguration for Policer on UNI Interface GigabitEthernet 1/1 COS-ID 0:ECE use count : 1/1CIR/EIR : 1.000/1.000 MbpsCBS/EBS : 0/0 bytesRate Type : Layer 1 (line)Mode : Color BlindConfiguration for ECE ID 1:Under test : YesVLAN Tag Type : AnyUNI interface : GigabitEthernet 1/1 (Auto)CoS : 0CIR/EIR : 1.000/1.000 MbpsVLAN ID : 1 (Auto)PCP : 0 (Auto)



DEI : 0 (Auto)DSCP : N/AFrame size : 516 bytesFrame : 00 00 00 00 00 01 00 01 c1 01 00 01 81 00 00 01 : 06 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 : ... : 00 00 00 00 00 00 00 0a 00 00 00 01 xx xx xx xxTx table legend:Pol ID : Policer ID used by this ECEECE ID : Either an ECE ID or a sum of all ECEs that use this policerCoS : Class of Service that this ECE maps to Color/Step # : Color of frame flow (G = Green, Y = Yellow) and step number in CIR configuration testColor : Color of frame flowUnder Test : Indicates whether this ECE was selected to be tested when the test was initiatedUNI Ingr, Requested : Requested traffic rate on UNI, in Line Rate (L1) and Data Rate (L2)UNI Ingr, Applied : Hardware doesn't always support the requested rate. This is the rate and total frame count : that hardware tells software it supports. Unfortunately, other factors like number of : flows and frame sizes also impact the actually achievable rate. If the rate coming through the : policer is unexpectedly low compared to applied rate, an error stating that : 'In-service UNI ingress rate is too low' will appear. This error may also be because : of hardware limitations. In such cases, retry with fewer ECEs enabled for testing.UNI Ingr, In-service : The applied rate and frame count after policing on the UNI. This is the rate supposed : to egress NNIUNI Egr : Actual NNI->UNI frame count after looping (may be 0 if counted on another ECE)Status : PASS or FAIL. May be empty if not testable on its ownRx table legend:PCP : PCP of NNI outer tag when Tx Lookup is 'VID-PCP'. 'Any' otherwiseStep # : Step number in CIR configuration testColor : Color of frame flowUNI Ingr, In-service : Sum of all 'UNI Ingr In-service' frames from theTx table that are expected to hit this PCPUNI Egr : Actual NNI->UNI frame count that hits this PCPFrame Loss : Percentage of frames lost between UNI Ingr and UNI EgrStatus : PASS or FAIL. May be empty if not testable on its ownDM table legend:CoS : Class of Service that this row shows DM forStep # : Step number in CIR configuration testDM Tx : Number of transmitted Delay Measurement framesDM Rx : Number of received Delay Measurement framesMin/Avg/Max Delay : Minimum, average, and maximum delay seen on the DM framesMin/Avg/Max Delay Var. : Minimum, average, and maximum delay variation seen on the DM framesStatus : PASS or FAILOverall execution status:Started at : 1970-01-01T04:12:21+00:00Ended at : 1970-01-01T04:13:03+00:00Status : Succeeded*************************** CIR configuration test **************************Configuration:Duration per step : 10 secondsDelay meas. interval : 500 msecsStep count : 4Status:Started at : 1970-01-01T04:12:21+00:00Ended at : 1970-01-01T04:13:03+00:00Status : SucceededTest data transmission:--- --- ------ ----- ----------------- ----------------- ------------ -------ECE CoS Color/ Under UNI Ingr (L1/L2) UNI Ingr (L1/L2) UNI Ingr UNI Ingr (L1/L2) UNI Ingr UNI Egr StatusID Step # Test Requested Applied Applied In-service In-service [Mbps] [Mbps] [Frames] [Mbps]



[Frames] [Frames]--- --- ------ ----- ----------------- ----------------- ------------ -------------- ---------- -------- ------ 1 0 G/1 Yes 0.250/0.240 0.248/0.239 579 0.249/0.239 582 582 PASS 1 0 Y/1 Yes 0.000/0.000 0 0 PASS 1 0 G/2 Yes 0.500/0.481 0.498/0.480 1163 0.499/0.480 1165 1165 PASS 1 0 Y/2 Yes 0.000/0.000 0 0 PASS 1 0 G/3 Yes 0.750/0.722 0.748/0.721 1747 0.749/0.721 1749 1749 PASS 1 0 Y/3 Yes 0.000/0.000 0 0 PASS 1 0 G/4 Yes 1.000/0.962 0.998/0.961 2329 0.998/0.960 2331 2331 PASS 1 0 Y/4 Yes 0.000/0.000 0 0 PASS

Delay Measurements:--- ------ -------- -------- ----------------- ----------------- ------CoS Step # DM Tx DM Rx Min/Avg/Max Min/Avg/Max Status Delay Delay Var. [Frames] [Frames] [usecs] [usecs]--- ------ -------- -------- ----------------- ----------------- ------0 1 20 20 9/10/10 0/0/0 PASS0 2 20 20 9/10/10 0/0/0 PASS0 3 20 20 9/9/10 0/0/0 PASS0 4 20 20 9/9/10 0/0/0 PASS******************************** Overall Result *************************Ended at : 1970-01-01T04:13:03+00:00Status : Succeeded****************************************************************************(config)# end#

2.5.1 Y.1564 Test with OAM Aware TrafficThe following illustration shows that a terminal loop of type oam-loop on the UNI port of the EVC is usedon Switch 2.

Figure 2 • OAM Aware Test and OAM-Loop

Specify the peer-mac when starting the Y.1564 test. The peer-mac is the MAC address of the switch portwhere the oam-loop is created on. In this example, the MAC address is Port 1 of Switch 2.

On Switch 2:

# configure terminal! Disable any other traffic-loop unrelated to the OAM aware test(config)# traffic-test-loop 1 admin-state disable! Enable the instance 2(the oam-loop that has already been created)(config)# traffic-test-loop 2 admin-state enable(config)# end#



On Switch 1:

# configure terminal! Test with two flows for COSID 0 and 1(config)# y1564 start myreport-OAMaware profile myprofile-OAMaware evc 10peer-mac 00-01-c1-00-ff-72 ece 1! Check y1564 test progress(config)# do show y1564 reportReport Name Created Status-------------------------------- ------------------------- ----------------myreport-OAMunaware 1970-01-01T04:12:21+00:00 Succeededmyreport-OAMaware 1970-01-01T04:12:21+00:00 In progress! Check y1564 test progress again(config)# do show y1564 reportReport Name Created Status-------------------------------- ------------------------- ----------------myreport-OAMunaware 1970-01-01T04:12:21+00:00 Succeededmyreport-OAMaware 1970-01-01T04:12:21+00:00 Succeeded(config)# end#

2.6 Understanding ITU-T Y.1564ITU-T Y.1564, sometimes called Y.156samor Ethernet service activationmethodology (EtherSAM) is a qualityof service (QoS) and network performance ITU-T Ethernet-based service test methodology.

These out-of-service testing procedures test service turn-up, installation, and troubleshooting ofEthernet-based services with the goal of assuring and verifying committed service level agreement (SLA)performances.

Prior to Y.1564, the most widely used testing tool to assess performance of Ethernet-based services wasIETF RFC 2544 (RFC 2544 test is also supported by Microsemi CE switches and CE-service software. Referto AN1111—software configuration guide on RFC2544 test), whichwas created to evaluate the performancecharacteristics of network devices in a lab. It includes throughput, burstability (back-to-back test), frameloss and latency tests, and is used for Ethernet-networks globally. However, it does not include all requiredmeasurements, such as packet delay variation, QoSmeasurement with bandwidth profiles (CIR, committedburst size (CBS), excess information rate (EIR), excess burst size (EBS), and color mode), and multipleconcurrent service levels. Contrary to RFC2544, Y.1564 allows simultaneous testing of multiple Ethernetservices and measures if they qualify to the committed SLA attributes. It also validates the different QoSmechanisms provisioned in the network to prioritize the different service types—allowing service providersfaster deployment and easier service and network troubleshooting.

Y.1564 defines test streams, or flows, with service attributes aligned to the MEF definitions. These testflows can be classified using various mechanisms, such as 802.1q VLAN, 802.1ad, differentiated servicecode points (DSCP), class of service (CoS) profiles, and map to EVC. These services are defined at the UNIlevel with different frame and bandwidth profile, such as CIR and EIR in a single test.

Microsemi Y.1564 is a Carrier Ethernet switch feature supported by both hardware and software. The testflows are generated and injected by the hardware of a switch based on an OAM engine at an UNI ingressat the source switch. The test flows are then looped back at the destination switch by a hardware-basedTT-Loop, and gathered again at theUNI egress at the source switch. Nanosecond-accurate delaymeasurement(DM) is made possible with the hardware based timestamp engine. The following illustration is the block



diagram of the test flow model of the Y.1564 SRC switch on the ingress direction forJaguar-2/Serval-2/Serval-T switches.

Figure 3 • Y.1564 Test Flow Model at SRC

Test flow is generated and inserted into the UNI ingress direction by a hardware-based OAM engine. Thetest flow is processed by the analyzer and then matched in the EVC control entry (ECE) table for a serviceID. It is further mapped in the ingress QoS mapping table to get the CoS ID and passed through the per CoSMEF policer. After that, the frames are counted in the EVC statistics block and pushed into the EVC.

Along the EVC, the test flow traverses through the network and arrives at the Y.1564 DST switch where aTT-Loop is located to loop the test flow traffic back to the Y.1564 SRC switch. The TT-Loop is either a facilityloop located on theNNI port or a terminal loop located on theNNI port. The facility loop can be an oam-loopor an mac-loop as show in the following illustration.

Figure 4 • Traffic Test Loop at DST—Facility Loop

A terminal loop can only be an oam-loop as show in the following illustration.

Figure 5 • Traffic Test Loop at DST—Terminal Loop



When the test flow is looped all the way back to the Y.1564 SRC switch, it is forwarded along the EVC pathto the UNI port where it originated. Here, loss and delay measurements are made by the OAM engine onthe UNI port. This is shown in the following illustration.

Figure 6 • Test Flow Model at SRC—Egress Direction

A Serval-1 switch has a slightly different architecture, so the Y.1564 test flowmodel becomes what is shownin the following illustration.

Figure 7 • Y.1564 Test Flow Model at SRC—Ingress Direction (Serval-1 Switch)

2.7 Y.1564 Test TypesY.1564 test methodology has two main objectives:• Validate correct configuration of each Ethernet-based service.• Validate service quality delivered to the end-user.

Therefore, themethodology comprises a service configuration test and a service performance test as shownin the following illustration.

Figure 8 • High-Level Service Activation Methodology



The goal of the service configuration test is to validate that the services are configured as intended. Serviceconfiguration testing comprises of CIR, EIR, and traffic policing tests. Those tests, together with serviceperformance test, are described individually in the following sections.

2.7.1 CIR Configuration TestStep load is used for the CIR test to gradually reach the CIR. When step count is 4 (as default) and a testflow will transmit at 25% of CIR at SRC, measure the received information rate (IR), frame loss ratio (FLR),frame transfer delay (FTD), and frame delay variations (FDV). FLRsac is the FLR limit, as specified in theservice acceptance criteria (SAC). If the FLR (including error frames), FTD, and FDV are all within the limitsspecified by the SAC, increase the transmitted IR and repeat the test (at 50%, 75%, and 100% of CIR), orother user-configured steps. If 100% of the CIR has been reached successfully within the SAC limits, thenthe result is pass.

2.7.2 EIR Configuration TestFor the color aware test, transmit frames marked green and yellow into the measurement point at a rateequal to CIR for the green frames and EIR for the yellow frames. Measure the following received rates:• IR-G for green frames• IR-Y for yellow frames• IR-T for the total combined rate

Also, measure:• FLR-G frame loss ratio of the green frames• FTD-G frame transfer delay of the green frames• FDV-G frame delay variation of the green frames

If FLR-G, FTD-G, and FDV-G are all within the SAC limits, then the result is pass.

For the non-color-aware test, transmit at an IR equal to CIR+EIR, and measure the received IR-T. Alsomeasure FLR, FTD, and FDV. If CIR*(1-FLRsac) <= IR-T <= CIR+EIR, then the result is pass.

2.7.3 Traffic Policing TestFor the color aware test, transmit green frames at an information rate equal to CIR and transmit yellowframes at an information rate of 125% EIR. Measure the received IR. Measure IR-G, IR-Y, and IR-T. Alsomeasure FLR-G, FTD-G, and FDV-G. If all are within the SAC limits, and IR-T <= CIR + EIR + M (Mfor the effect of the traffic policer's CBS and EBS settings), then the result is pass.

For the non-color-aware test, transmit at the source with an IR equal to CIR+125% EIR, measure the IR, andFLR, FTD, FDV. IfCIR*(1-FLRsac) <= IR-T <= CIR+EIR+M (M for the effect of the traffic policer'sCBS and EBS settings), then the result is pass.

2.7.4 Service Performance TestThe service performance test validates the quality of the services up to 24 hours. All services must transmitgreen frames of an IR equal to CIR. Measure the received IR, FLR, FTD, FDV, and service availability. Theservices must operate at or above the SAC performance levels for the service to be accepted.

2.8 Y.1564 Test ProfileA test profile must be created and properly configured before a Y.1564 test can be started. A Y.1564 testprofile contains all the parameters associated with a combination of one or more sub-tests, including theCIR, EIR, traffic policing test, and a service performance test.

Tomanage the saved Y.1564 test profiles listed on the Y.1564 Profiles Overview page, perform the followingsteps:



1. Click Configuration > Traffic Test > Y.1564 > Profiles, and click the specific profile name to view all theconfigurations of any existing test profile.

2. Click Delete to delete the profile.

3. To create a new profile, click Add New Profile. On the Profile Configuration page, set up the requiredparameters for the new test as shown in the following figure.

Figure 9 • Y.1564 Profile Overview Web Page

Test profiles can also be shown using the following ICLI command.

# show y1564 profile

To create a new Y.1564 profile or rename an existing profile through ICLI, enter configuration mode. Thefollowing example creates a new Y.1564 profile, MyProfile:

! Get into configuration mode# configure terminal! Create a Y.1564 test profile and name it "MyProfile".! If a profile named "MyProfile" already exists, the command that follows will! modify the existing profile instead of creating a new profile.(config)# y1564 profile MyProfile(configure-y1564-profile)#

2.8.1 Common ParametersIn the profile configuration web page, all the common parameters and sub-test specific parameters in atest profile are shown graphically. The configuration is straightforward.

Figure 10 • Common Parameters

The following table lists all the common parameters.

Table 1 • Common Parameters

DescriptionParameters

A unique profile name up to 32 characters.Profile name




Default: NewProfile

A textual description up to 128 characters associated with the profile.Description

Default: blank

When this option is selected, the test flows are generated at SRC and statistics are gathered at DST. Test trafficonly travels the network once. This requires a networkmanagement station (NMS) to control traffic, gather results,

Dual-ended

and create a test report. Dual-ended test is not yet supported with CEservice 4.00. In the current software thischeck box must be unchecked so that the single ended tests will be used—SRC transmits traffic and expects alooped version to return at the SRC again for statistics gathering.

When the option is selected, the device transmits Y.1731 LBM frames as background traffic, and expects the remoteend to return Y.1731 loopback reply (LBR) frames. When the option is cleared, the device transmits Y.1731 test

DST is OAM-aware

signal (TST) frames as background traffic, and expects the remote end to loop this traffic while swapping DMACand SMAC only. For delay measurements, the device transmits Y.1731 DMM frames if DST is OAMaware checked,and Y.1731 1DM frames if DST is OAMunaware is unchecked.

When the drop-down box is set to Y.1731 OAM, the Y.1731 OAM frame will be used as background traffic. In thecurrent version of software, only one ECE can be tested at a time in this mode. When set to simulated customer

Traffic type

traffic software generates a traffic-pattern per ECE that hits the ECE, and uses the ECE's counters to determinepass/fail criteria. Up to eight ECEs may be tested simultaneously.

Specifies the MEG level the Y.1564 test will be running. Default: MEG level 7. The MEG level is only useful for OA-M aware test with an oam-loop at the remote switch.

MEG level

Specifies the frame sizes for each test. Select: 64, 128, 256, 512, 1024, 1280, 1518, MTU, or user-defined.Frame size

Default: 512 bytes.

Specifies the programmable frame size when user-defined frame size is selected in the previous step.User-definedframe Default: 2000 btyes.size

Specifies wait time (ms) after each trial for the test to settle before reading statistics from the hardware.Dwell time

Default: 500 ms

The previous common parameters for a Y.1564 test profile can also be configured through the ICLI interface.The following example configures the common parameters for test profile, MyProfile.

! Edit the y1564 test profile named "MyProfile" (config)# y1564 profile MyProfile ! Add a description to the profile (config-y1564-profile)# description This is an test profile example ! Set traffic type to Y.1731 OAM frames instead of simulated customer traffic (config-y1564-profile)# traffic-type oam ! Set destination to be oam aware so that Y.1731 LBM and DMM frames will be used (config-y1564-profile)# dst-oam-aware ! Set MEG level (config-y1564-profile)# meg-level 7 ! Set dwell time to be 500 ms (config-y1564-profile)# dwell-time 500 ! Set user defined frame size to be 1000 bytes (config-y1564-profile)# user-defined-frame-size 1000



2.8.2 SACService acceptance criteria (SAC) is a set of criteria that ensures the service meets its functionality andquality requirements, and that the service provider is ready to operate the new service when it has beendeployed. It is also used as the pass criteria for each of the Y.1564 sub-tests.

Figure 11 • Service Acceptance Criteria

The following table lists all the service acceptance criteria parameters.Table 2 • Service Acceptance Criteria Parameters


The maximum acceptable frame loss rate in the range [1:1000].Acceptable F-LR The number is used for each of the enabled sub-tests. If the policer belonging to the ECE under test is non-color-

aware and the test is injecting traffic above CIR (which can occur in the EIR configuration and the traffic policingtests), method 1 is used when calculating the pass/fail criterion. Otherwise, method 2 is used.

• Method 1: The expected total received (Rx) frame count is computed based on the policer rate andthe duration of the trial. If the actual Rx frame count is less than the expected minus the acceptableframe loss set with this parameter, the test fails. Otherwise, it succeeds.

• Method 2: The actual frame drop is computed as the transmitted (Tx) count minus the Rx count. Ifthis number exceeds the acceptable frame drop (computed from this parameter), the test fails. Other-wise, it succeeds.

Method 2 cannot always be used because the non-color-aware tests only transmit the green frames. Method 1, which doesn't use actual Tx frame count,must be used because the injection for the aforementioned tests occursabove CIR, so the frames may get dropped. This is also explained in EIR Configuration Test on page 13 and TrafficPolicing Test on page 13.

Specifies the maximum transfer delay in milliseconds.Acceptable F-TD

Specifies the maximum delay variation in milliseconds. gathering.Acceptable F-DV

The SAC parameters can be entered in the web GUI as shown in the previous figure or through ICLI usingthe following commands.

! Set frame delay vriation to be 100 ms (config-y1564-profile)# acceptable-fdv 100 ! Set frame loss ratio to be 50 % (config-y1564-profile)# acceptable-flr 50 ! Set frame transfer delay to be 200 ms (config-y1564-profile)# acceptable-ftd 200

2.8.3 CIR Configuration Test ParametersThe following figure and table show CIR configuration test parameters.

Figure 12 • CIR Configuration Test Parameters



The following table lists all the CIR configuration test parameters.Table 3 • CIR Configuration Test Parameters


Select the option to enable the CIR configuration test.Enable

Specifies the number of seconds each step will run.Stepduration

Default: 10 seconds

Specifies the number of milliseconds between each delay measurement.DM interval

Default: 500 milliseconds

Specifies the number of steps for step load CIR test.Step count

The following example enables a CIR test. Set dwell time to 400 ms, step duration to 10 seconds, and stepcount to 5 (so that traffic rates of 20%, 40%, 60%, 80%, 100% * CIR will be tested).

(config-y1564-profile)# cir-test dm-interval 400 duration 10 step-count 5

2.8.4 EIR Configuration Test ParametersThe following figure and table show the CIR configuration test parameters.

Figure 13 • EIR Configuration Test Parameters

The following table lists all the EIR configuration test parameters.Table 4 • EIR Configuration Test Parameters


Enables the EIR configuration test.Enable


Default: 10 seconds



The following example enables the EIR test. Set DM interval to 400 ms and set test duration to 10 seconds.

(config-y1564-profile)# eir-test dm-interval 400 duration 10

Color aware or color blind test mode will automatically be decided by the software, according to customerselection of the MEF policer mode on the ECE where the Y.1564 test is executed.

To display the MEF policer configuration on each EVC/ECE, perform the following step.



• Click Configuration > Ethernet Services > CoS ID Policer, and select the EVC ID and Port number asshown in the following figure

Figure 14 • Policer Mode of EVC CoS ID Policer

2.8.4.1 Traffic Policing Test Parameters

The following figure and table the traffic policing test parameters.

Figure 15 • Traffic Policing Test Parameters

The following table lists all the traffic policing test parameters.Table 5 • Traffic Policing Test Parameters


Select the option to enable the EIR configuration test.Enable


Default: 10 seconds



The following example enables the traffic policing test. Set DM interval to 400 ms and step duration to 10seconds.

(config-y1564-profile)# traffic-policing-test dm-interval 400 duration 10

Color aware or color blind test mode will automatically be selected by the software as for the EIR test.

2.8.4.2 Performance Test Parameters

The following figure and table show the performance test parameters.

Figure 16 • Performance Test Parameters

The following table lists all the performance test parameters.



Table 6 • Performance Test Parameters


Enables the performance test.Enable

Specifies the number of seconds the performance test will run. Supported durations: 15 minutes, 2 hours, 24hours, and user-defined.

Duration

Default: 15 minutes

Specifies the user-defined test duration in seconds if the user-defined duration mode is selected in the previousstep.

User-definedduration

Default: 900 seconds



The following example enables the traffic policing test. Set DM interval to 400 ms and step duration to 2hours, then finish the configuration of the profile.

(config-y1564-profile)# performance-test dm-interval 400 duration 7200(config-y1564-profile)# exit(config)#exit#

The configured Y.1564 test profile can be shown using the show command followed by the profile name:

# show y1564 profile MyProfileProfile configuration:Profile name : MyProfileDescription :Measurement type : Single-ended (DST loops traffic)DST is OAM aware : NoBackground traffic type : Simulated customer trafficDelay measurement type : Y.1731 1DMMEG Level : 7Dwell time : 500 msecsFrame size : 512 (EMIX=d)User-defined frame size : 2000 bytesCIR configuration test : EnabledEIR configuration test : EnabledTraffic policing test : EnabledService performance test : EnabledAcceptable FLR : 30 permilleAcceptable FTD : Check disabledAcceptable FDV : Check disabledConfiguration:Duration per step : 10 secondsDelay meas. interval : 500 msecsStep count : 4Configuration:Duration : 10 secondsDelay meas. interval : 500 msecsConfiguration:Duration : 10 secondsDelay meas. interval : 500 msecsConfiguration:Duration : 900 secondsDelay meas. interval : 500 msecs

If the Y.1564 profile is configured in the web GUI, click the Save button at the bottom of the Y.1564 ProfileConfiguration page to save the profile. All parameters of the current profile can be reset to their defaultvalues by clicking the Reset button, or the editing can be aborted (exit without saving) by clicking the Cancelbutton.

Once saved, the web GUI returns to the Y.1564 Profile Overview page, and the new profile is listed in thetable of all test profiles. Up to 16 test profiles can be created and saved in the flash memory of the switch.



2.9 Start Y.1564 TestA new Y.1564 test report is automatically generated and saved after each Y.1564 test is executed. Tomanagethe test reports, perform the following steps.

1. Click Configuration > Traffic Test > Y.1564 > Reports, the Y.1564 Report Overview page opens. Thecontents of any test report can be viewed by clicking the report name.

2. To delete a test report, click Delete.

3. To download a test report and save it as a TXT file, click Save for any test report.

Figure 17 • Y.1564 Report Overview Page

Note:

The existing test reports can also be shown with the following ICLI commands: #show y1564 report

Note:

The content of any test report can be viewed by appending the file name of the testreport to the previous command.

4. To open the Y.1564 Test Start page and to prepare a new Y.1564 test, click Start New Test as shown inthe following figure.

Figure 18 • Y.1564 Test Start Page

The following can be selected on the Y.1564 Test Start page:• Test report file name generated by this test.• Description of the test report: Default: blank.• A Y.1564 test profile (created and saved as described in Service Performance Test on page 13). Default:

the first saved test profile.• Peer MAC address of the test flows. Default: 00-00-00-00-00-00. When the test traffic is configured as

DST is OAM aware, the peer-mac must be correctly specified. It is the MAC address of the switch porton which the oam-loop is created.



• The EVC ID on which the Y.1564 will be executed. Default: the lowest configured EVC ID.• The ECE ID and CoS on which a test flow must be generated and measured.

Once the EVC ID has been selected, a list of ECE/CoS entries associated with that EVC is displayed on theY.1564 test start page. ECE/CoS entries are configured and saved during the creation of that EVC. ECEs arewhere all the UNI-related service attributes for that EVC are kept. One or more ECEs may map to a singleEVC with different CoS ID and bandwidth profiles. A Y.1564 test flow should be generated and measuredfor each ECE/CoS combination of an EVC. Test flows can be generated automatically by the software. Thesoftware generated test flow will try to match the parameters of the corresponding ECE configured andsaved on the same switch. To enable the Y.1564 test for each ECE/CoS, each ECE/CoS check box can beselected or the UNI port, VLAN tagging, and DSCP value for the test flows can be specified manually.

Dual-ended Y.1564 test is not yet supported with the current software revision. Therefore, the TT-Loopmust be configured at the remote switch before the Run button can be clicked to start a Y.1564 test.

Once the Run is clicked, a Y.1564 test starts and a test report preview window opens immediately with livedisplay of the status and statistics of the currently running sub-test.

Figure 19 • Y.1564 Test Report Preview Window

After all the sub-tests are completed, the final test report can be viewed by clicking the report name. TheY.1564 test can also be started from the ICLI management interface by the following command:

# y1564 start NewReport profile MyProfile evc 10 ece 1

If the test profile has DST and OAM aware selected, specify the peer-mac address of the oam-loop at theremote switch.

# y1564 start NewReport profile MyProfile evc 10 peer-mac 00-01-c1-00-ff-72 ece 1

The status of the test report will be shown In Progress before the test has completed. The test can beaborted using the stop command:

# y1564 stop MyReport



The test can be stopped immediately and the report status changes to canceled.

The test can also be stopped through the web interface by clicking Stop for the executing test on the Y.1564Report Overview page as shown in the following figure.

Figure 20 • Y.1564 Test Execution Status

The test report status appear as succeeded or failed once all of the sub-tests are complete.

2.10 TT-Loop ConfigurationThe dual-end test is not yet supported by the software revision 4.00. Therefore, the traffic test loop (TT-Loop)must be enabled at the destination switch before any Y.1564 test is started. A test loop matches the frameit receives at a certain point of the switch with the configured parameter and sends the frames back, sothat the Y.1564 test SRC can gather statistics for the test.

To configure a TT-Loop, perform the following steps:

1. Click Configuration > Traffic Test > Loop. The Traffic Test Loop page opens as shown in the followingfigure.

Figure 21 • Add a New Traffic Test Loop

2. To create and configure a new TT-Loop, click Add New TT-LOOP and configure the parameters listed inthe following table.Table 7 • Traffic Test Loop Parameters


The ID of the new TT-LOOP. Once a TT-LOOP is created, the parameters can be modified by clicking the ID.Instance ID

Select Port, EVC, or VLAN domain:Domain

• Port: This is a TT-Loop in the Port Domain so it matches all received frames on that port.

• EVC: This is a TT-Loop in the EVC Domain. Flow is an EVC number. The EVCmust be created beforeconfiguring the TT-Loop. The TT-Loop only matches frames received on the configured EVC.

• VLAN: This is a TT-Loop in the VLAN Domain. Flow is a VLAN. The VLAN must be created beforeconfiguring the TT-Loop. The TT-Loop only matches frames received on the configured VLAN.

Depending upon the selection of domain: Port number if domain is Port, EVC ID if domain is EVC, VLAN ID ifdomain is VLAN.

Flow

Select either mac-loop or oam-loop. A mac-loop matches all frames belonging to the configured domain andswaps the SMAC and DMAC fields before looping them back. An oam-loop is actually an MEP that matches

Type

and responds to OAM frames intended for it. Peer-mac and MEG-level must be configured correctly for anoam-loop to work. The oam-loop responds to a LBM frame with a LBR frame and a DMM frame with a delaymeasurement reply (DMR) frame.




Select either facility loop (looping is done from ingress to egress) or terminal loop (looping is done fromegressto ingress).

Direction

The port where the TT-LOOP is resident. For an EVC loop the port must be a port in the EVC. For a VLAN loop,the port must be a VLAN member.

Residenceport

After a TT-Loop instance is created and saved, its operational statuswill still be down, unless all the resourcesare available for that loop instance and the administration state of the loop instance is enabled. In the webGUI, clicking the loop instance ID goes to the TT-Loop instance configuration page where the instance canbe given a name and enabled, as shown in the following figure.

Figure 22 • Enable a Mac-Loop

The loop type in the previous example is amac-loop. If it is an oam-loop, specify theMEG level and subscriberdomain.

The previous TT-Loop can also be created through ICLI:

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

A mac-loop is OAM unaware. It loops back all received frames and swaps the SMAC and DMAC address forany received frames. Peer-mac andMEG level are irrelevant to amac-loop. But an oam-loop is different—anoam-loop is actually a real MEP. It only responds to OAM frames that are destined to it, MEG level andpeer-macmust be configured correctly for an oam-loop. The softwarewill create a specialMEP automaticallyafter you enable an oam-loop. The peer-mac address of the oam-loop is required to start a Y.1564 test.

To find the automatically created MEP, click Configuration >MEP.

Figure 23 • Software Create MEP for Oam-Loop

MEG level for an oam-loop is configured by clicking the Instance ID of the oam-loop and selecting throughthe Level drop down manual as shown in the following figure.

Subscriber domain is selected through the same configuration page that tells which domain PDUs theoam-loop apply to. It is a drop down manual with the following options:• None: This EVC OAM TT-Loop is OAM aware of EVC domain PDUs.• All: This EVC OAM TT-Loop is OAM aware of all subscriber domain (double-tagged) PDUs.



• Test: This EVC OAM TT-Loop is OAM aware of LBM subscriber domain (double-tagged) PDU. OtherPDUs are EVC domain (single-tagged).

Figure 24 • Oam-Loop Instance Configuration Page

2.11 Y.1564 Test Report and TroubleshootingA Y.1564 test report includes all tests and test result information, including each sub-test status and detailedstatistics. This section explains each part of the test report and troubleshooting techniques, such as usingdetailed statistics to find where a sub-test failed.

2.11.1 Configurations of Y.1564 TestThe first part of the test report lists all the key configurations of the test, such as the software reversion,test profile parameters, test report file name and the EVC/ECE/CoS on which the test was executed, theUNI/NNI configurations and status when the test was executed, and also MEF policers information on the



test flows that were generated. If customer-simulated traffic was used, the test report also shows thecontent of the software generated simulated frame for each test flow.

************************************* Y.1564 SAM Test ************************************Software configuration:Version : CEServices (standalone) dev-build by jenkins@softblade7.

dk.vitesse.com 2016-05-23T10:23:56+02:00 Config:ce_serval2 SDK:v01.66- smb Build 772Build date : 2016-05-23T10:23:56+02:00Code revision : df88d21+Profile configuration:Profile name : NewProfileOAMDescription :Measurement type : Single-ended (DST loops traffic)DST is OAM aware : YesBackground traffic type : Y.1731 LBMDelay measurement type : Y.1731 DMMMEG Level : 7Dwell time : 500 msecsFrame size : 512 (EMIX=d)User-defined frame size : 2000 bytesCIR configuration test : EnabledEIR configuration test : EnabledTraffic policing test : EnabledService performance test : DisabledAcceptable FLR : 30 permilleAcceptable FTD : Check disabledAcceptable FDV : Check disabledReport configuration:Report name : myReport-OAMawareDescription :Peer MAC : 00-01-c1-00-ff-72EVC ID : 10ECE IDs on EVC : 1ECE IDs under test : 1Configuration for UNI interface GigabitEthernet 1/1:Link state : DownSpeed : 1000 MbpsMTU : 10240 bytesMAC : 00-01-c1-01-00-01Configuration for NNI interface GigabitEthernet 1/3:Link state : UpSpeed : 1000 MbpsMTU : 10240 bytesConfiguration for Policer on UNI Interface GigabitEthernet 1/1 COS-ID 0:ECE use count : 1/1CIR/EIR : 10.000/10.000 MbpsCBS/EBS : 0/0 bytesRate Type : Layer 1 (line)Mode : Color AwareConfiguration for ECE ID 1:Under test : YesVLAN Tag Type : AnyUNI interface : GigabitEthernet 1/1 (Auto)CoS : 0CIR/EIR : 10.000/10.000 MbpsVLAN ID : 1 (Auto)PCP : 0DEI : 0 and 1 (Auto)DSCP : N/AFrame size : 516 bytes

If the status of the Y.1564 test is Failed, then this is the first place to check for any configuration issues.

2.11.2 Overall Status and Table LegendsThis part of the test report shows the table legends that will be listed in the statistics table for each sub-test. It will help to understand the meaning of all numbers in the table for each sub-tests.



The overall execution status of the whole test will be shown following the table legends. The status will be“Succeeded” when all the sub-tests are passed.

Figure 25 • Overall Status and Table Legends

2.11.3 CIR Test Results and TroubleshootingThis part of the test report shows the test result of the CIR sub-test. The statistics table shows the rate andnumber of frames sent from the Y.1564 SRC for each step for each test flow (ECE/CoS combination). It alsoshows how many frames were received back at each step. The CIR of the MEF policer of the followingexample was set to 10 Mbps line rate in color blind mode. So only green frames are sent at 2.5 Mbps/5Mbps/7.5 Mbps/10Mbps for each step. The number of frames sent at each step were also shown togetherwith the number of frames received at each step. Frame delay measurement frames were also sentinterleaved with the frame loss measurement traffic at each step. Frame delay test results were shown ina separate table followed by the frame loss table. It shows the number of delay measurement frames sentand received together with the measured min/avg/max time and the delay variation for each step.

Figure 26 • CIR Configuration Test

The CIR test is the first sub-test in the series of Y.1564 sub-tests after the test was started. If there was anyconnectivity or configuration issue the CIR test will most likely to be failed so that the whole test will bestopped. Therefore, the CIR test result is often the only information used for troubleshooting any possibleissues. The following are some situations and recommended techniques that might be helpful to find outthe root cause:• No frame was sent from the UNI.



As shown in the following statistics table, the UNI ingress in-service rate and frame counter are all 0.

This means no frame was actually sent from the UNI. Possible causes could be:◦ NNI port link down (however, the UNI port is allowed to be down during Y.1564 test).◦ EVC configuration error.◦ VLAN configuration error.◦ No frame was received back.

As shown in the following statistics table, theUNI ingress in-service rate and frame counter are non-zero,but the UNI egress frame counter was 0.

Thismeans the test frameswere sent, but theywere all lost somewhere along the test frame forwardingpath. The CIR test result does not say where the frameswere lost, so selectMonitor > Ethernet Service> EVC Statistics. Select the port number and the statistics per EVC ID per CoS ID appear as shown inthe following figure.

Figure 27 • EVC Statistics

The EVC statistics can also be accessed through CLI commands. The following command shows theTX/RX frame number for EVC 10 on the UNI port (Port 1).

# show evc statistics 10 interface Gigabit Ethernet 1/1

EVC statistics are useful for troubleshooting when it is know how an undropped test frame is countedalong the forwarding path. For the OAM aware test indicated in Figure 1 on page 9, a test frame willbe counted in an order shown in the following table. For the OAM unaware test indicated in Figure 1on page 2, a test frame will be counted in an order shown in Table 2 on page 28.

The two tables also show the possible causes of unexpected counting.Table 8 • EVC Statistics and Troubleshooting for OAM Aware Test (DST-is-OAM-Aware Checked)

Oam-Loop Switch 2: NNIOam-Loop Switch 2: UNIY.1564 SRC Switch 1: NNIY.1564 SRC Switch 1: UNI

RX counts EVC configura-tion NNI port link down

TX counts EVC configuration

RX counts Cable connec-tion EVC configuration





RX counts EVC configurationPeer MAC, MEG level erroroam-loop configuration admin-state Subscriber domain

TX counts EVC configura-tion

RX counts EVC configuration


Table 9 • EVC Statistics and Trouble Shooting forOAMUnaware Test (DST-is-OAM-AwareUnchecked)


RX counts EVC configura-tion


RX counts Cable connec-tion EVC configuration

TX countsMac-loop config-uration admin-state

RX counts EVC configuration


EVC configuration error is a common issue responsible for a Y.1564 test failure. It is suggested to testthe EVC with a pair of MEPs on the two switches before a Y.1564 test is executed to ensure correctEVC configuration. MEP can be created and configured through Configuration > MEP in the web GUI,as shown in the following figures. Either Down-MEP or Up-MEP can be created according to the traffic



type and test path of a Y.1564 test. To troubleshoot an OAM aware Y.1564, testing an Up-MEP issuggested.

Figure 28 • Creating an MEP

Figure 29 • Configuring an MEP

• Partial frame loss

The following example shows 5822 green frameswere sent, but only 2427 green frameswere received.2426 yellow frames were received unexpectedly. In the delay measurement, 20 measurement frameswere sent, but only 8 were received. The status showed as Failed and the details showed “Delaymeasurements: Acceptable frame loss exceeded”.

The previous statistics suggest that frames were lost along the forwarding path. The EVC statistics,shown in Table 1 on page 27 and Table 2 on page 28 can compare counters in the forwarding orderto find where the counter was reduced, or where frames were lost. Counters per color—especiallyred, because red frames are dropped by a policer—should be closely monitored.

The statistics in the above example was captured when a MEF policer was mistakenly enabled at theremote switch that a TT-Loop was configured. Therefore, the dropped frames were counted as red.

2.11.4 EIR Test Results and TroubleshootingEIR test is a color aware test if the MEF policer's mode is configured in color aware mode.

To find MEP policers, perform the following step.



• Click Configuration > Ethernet Service > CoS ID Policers, and then from the Policer Mode list, selecteither Color Aware or Color Blindmode as shown in the following figure.

Figure 30 • MEF Policer Configuration

The EIR test is only done once, and yellow frames are sent and counted separatelywhen received. Otherwise,the EIR test delay measurement and result is similar to that of the CIR test. Furthermore, traffic is only sentonce at the configured CIR and EIR rates. In the following example, these rates are each 10 Mbps, so bothgreen and yellow frames are sent at 10 Mbps simultaneously. The number of Tx/Rx frames for both colorsare captured and compared.

A frequent EIR test failure is shown in the following example. The status reads, “Receivedmore green framesthan were transmitted”.

The following statistics show that 2328 green and 2326 yellow frames, or 4654 frames in total, were sent.The software, which expected to receive the same number of green and yellow frames, received 4654 greenframes and no yellow ones. Overall, no framewas dropped, but the yellow frameswere re-colored to green.

The EVC statistics tool, as explained in CIR Test Results and Troubleshooting on page 26, can show wherethe frame re-coloring started—at either the MEF policer or where QoS mapping is done. The MEF policercan only change a green frame to a yellow one, so the root cause is likely to be a configuration issue on theQoS mapping.

QoS mapping, which includes ingress mapping (Figure 2 on page 31) and egress mapping (Figure 3 on page31), is assigned to the EVC during EVC configuration. Using the Y.1564 test examples, a test frame will firstapply the ingressmap at the UNI SRC switch, then the egressmap at the NNI SRC switch. Then, in this order:the ingress map of the NNI DST switch, the egress map of NNI DST switch if it is a facility loop, the ingressmap of the NNI SRC switch, and lastly the egressmap of the UNI SRC switch. TheQoSmapping configuration



should ensure that green/yellow frames will still be mapped to green/yellow frames passing through thewhole forwarding path.

Figure 31 • Ingress Map Configuration

Figure 32 • Egress Map Configuration

Please be alert that the ingress and egress map key must be configured correctly according to the mappingrule being created. The root cause of the EIR test failure in the example is that it is supposed tomap PCP/DEIto CoSID/DPL on the ingress and CoSID/DPL to PCP/DEI on the egress. In the example, the ingress map key



was left at the default PCP only and the egress map key was left at the default CoSID only—all frames weregreen when received. The following figure show the solution to this problem.

Figure 33 • Egress Map Key Configuration

Figure 34 • Ingress Map Key Configuration

2.11.5 Policer Test ResultsThe traffic policer test applies a larger yellow frame rate than EIR test. In the following example, the UNIingress applied traffic is 12.5 Mbps = 125% * EIR rate. After the policer the UNI ingress in-service rate waslimited to 10 Mbps. Policer test frame delay measurement is similar to that of the CIR and EIR test.



Code Figure

The traffic policer test is likely to pass if the CIR and EIR tests pass. CheckMEF policer configurations if thereare any problems.

2.11.6 PerformanceTestService performance test, as shown in the following example, validates the service quality up to 24 hours.Only green frames are sent and counted. Delay measurement is similar to that of earlier sub-tests.



2.12 Saving the ReportThe report can be saved on a remote system in two ways:• Press Save in the web interface to save it as a local file on your PC.• Use the CLI to save the report on a remote host using a variety of transfer protocols. Use the following

command for this:

# y1564 save <reportname> <protocol>://[<username>[:<password>]@]<host>[:<port>][/<path>]>

Where,◦ <reportname>—the name of the report.◦ <protocol>—denotes the transfer protocol to use. Can be one of [http, tftp, ftp, scp, sftp].◦ <username>—the username on the remote host. Required for SCP and SFTP. Optional for HTTP

and FTP.◦ <password>—the password for the given <username>. See above for details.◦ <host>—the IP address or hostname for the remote host.◦ <port>—the TCP or UDP port number for the selected transfer protocol. If omitted the default

value for the transfer protocol wŁill be used.◦ <path>—the path to the remote file. Note that the slash character ('/') between the host-port

part and the path path is not considered part of the path. If you need to provide an absolute paththat starts with a slash you need to add another one like this:ftp://myhost//home/kenneth/files/myfŁile.txt

2.13 Supported Y.1564 Test and Loop ParametersThe configurations for the Y.1564 SRC switch must match the configurations of the remote TT-Loop switch.Not all combinations are possible or supported by the current 4.00 CEservices software revision. Thefollowing table shows the supported combinations.



Table 10 • EVC Statistics and Troubleshooting for OAM Aware Test (DST-is-OAM-Aware Checked)

TT-Loop S-witch

Y.1564 SRC S-witch

DirectionTypeDomainDelayMeasure-ment

Test TrafficDST is OAM A-ware

Dual- Ended1

Facilitymac-loopPort1DM PDUY.1731 TST PDUNoNo

Facilitymac-loopPort1DM PDUSimulated cus-tomer

NoNo

Facilitymac-loopEVC1DM PDUY.1731 TST PDUNoNo

Facilitymac-loopEVC1DM PDUSimulated cus-tomer

NoNo

Facility/terminal3

mac-loopEVC-Sub 2DDM PDUY.1731 LBM PDUYesNo

Note:

1. Dual-ended test is not supported in software revision 4.00.

2. EVC subscriber domain All or Test should be configured.

3. In revision 4.00, the EVC-SUB OAM Loop is Facility on Serval-1 and Terminal onJaguar2/Serval-2/Serval-T.



Microsemi makes no warranty, representation, or guarantee regarding the information containedherein or the suitability of its products and services for any particular purpose, nor doesMicrosemiassume any liability whatsoever arising out of the application or use of any product or circuit. Theproducts sold hereunder and any other products sold by Microsemi have been subject to limitedtesting and should not be used in conjunctionwithmission-critical equipment or applications. Anyperformance specifications are believed to be reliable but are not verified, and Buyermust conductand complete all performance and other testing of the products, alone and together with, orinstalled in, any end-products. Buyer shall not rely on any data and performance specifications orparameters provided by Microsemi. It is the Buyer's responsibility to independently determinesuitability of any products and to test and verify the same. The information provided byMicrosemihereunder is provided "as is, where is" and with all faults, and the entire risk associated with suchinformation is entirely with the Buyer. Microsemi does not grant, explicitly or implicitly, to anyparty any patent rights, licenses, or any other IP rights, whether with regard to such informationitself or anything described by such information. Information provided in this document isproprietary toMicrosemi, andMicrosemi reserves the right tomake any changes to the informationin this document or to any products and services at any time without notice.

Microsemi HeadquartersOne Enterprise, Aliso Viejo,CA 92656 USA

Within the USA: +1 (800) 713-4113Outside the USA: +1 (949) 380-6100Sales: +1 (949) 380-6136Fax: +1 (949) 215-4996Email: [email protected]

© 2019 Microsemi. All rights reserved.Microsemi and the Microsemi logo aretrademarks of Microsemi Corporation. Allother trademarks and service marks are theproperty of their respective owners.

Microsemi, awholly owned subsidiary ofMicrochip Technology Inc. (Nasdaq:MCHP),offers a comprehensive portfolio of semiconductor and system solutions foraerospace&defense, communications, data center and industrialmarkets. Productsinclude high-performance and radiation-hardened analog mixed-signal integratedcircuits, FPGAs, SoCs and ASICs; power management products; timing andsynchronization devices and precise time solutions, setting the world's standardfor time; voice processing devices; RF solutions; discrete components; enterprisestorage and communication solutions; security technologies and scalable anti-tamperproducts; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well ascustom design capabilities and services. Microsemi is headquartered in Aliso Viejo,California, and has approximately 4,800 employees globally. Learn more atwww.microsemi.com.

VPPD-04305


Legal

Documents

Y.1564 Software Configuration Guideww1.microchip.com/downloads/en/Appnotes/ENT-AN1124_VPPD... · 2019-10-29 · Software configuration: Version : CEServices (standalone) dev-build