ENT-AN1105 Application Note Service OAM Configurationww1.microchip.com/downloads/en/Appnotes/VPPD-03588_ENT-AN1105.pdf · Service OAM Configuration ENT-AN1105 Application Note Revision

ENT-AN1105 Application NoteService OAM Configuration

VPPD-03588. 1.1 1/16

Microsemi Corporate HeadquartersOne Enterprise, Aliso Viejo,CA 92656 USA

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

Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of semiconductorand system solutions for communications, defense & security, aerospace and industrialmarkets. Products include high-performance and radiation-hardened analog mixed-signalintegrated circuits, FPGAs, SoCs and ASICs; power management products; timing andsynchronization devices and precise time solutions, setting the world's standard for time; voiceprocessing devices; RF solutions; discrete components; security technologies and scalableanti-tamper products; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well ascustom design capabilities and services. Microsemi is headquartered in Aliso Viejo, Calif, andhas approximately 3,600 employees globally. Learn more at www.microsemi.com.

© 2015 Microsemi Corporation. Allrights reserved. Microsemi and theMicrosemi logo are trademarks ofMicrosemi Corporation. All othertrademarks and service marks are theproperty of their respective owners.

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

mailto:[email protected]

www.microsemi.com

ENT-AN1105 Application Note Revision 1.1 iii

Contents

1 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Revision 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 Revision 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 Service OAM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1 Understanding Service OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.2 Service OAM Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.2.1 Port OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.2.2 VLAN OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.2.3 EVC OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2.4 Port Protection with Service OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2.5 Ring Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2.6 Ring Interconnection Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.3 Service OAM Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.1 Restore Default Setup using CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.2 Restore Default Setup using WebGUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.3 Port OAM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.4 VLAN OAM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3.5 EVC OAM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3.6 E-TREE OAM Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.3.7 Port Protection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.3.8 Ring Protection Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.3.9 Ring Protection with MEP Relation Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . 522.3.10 Ring Interconnection Protection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

ENT-AN1105 Application Note Revision 1.1 iv

Figures

Figure 1 Maintenance End Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Figure 2 Maintenance Entity Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Figure 3 Nested Maintenance Entity Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Figure 4 Port Domain Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Figure 5 VLAN Domain Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Figure 6 EVC Domain Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Figure 7 E-TREE Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Figure 8 Basic Port Protection Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Figure 9 Port Protection with Service OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Figure 10 Basic Ring Protection Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Figure 11 Ring Protection with Service OAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Figure 12 Alternative SSF Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 13 Ring Interconnection Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 14 Factory Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 15 Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 16 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 17 Add MEP instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 18 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 19 Global VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 20 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 21 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 22 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 23 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 24 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 25 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 26 EVC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 27 ECE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 28 Global VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 29 QoS Ingress Port Tag Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 30 QoS Egress Port Tag Remarking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 31 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 32 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 33 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 34 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 35 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 36 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 37 E-Tree Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 38 EVC Control List Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 39 NNI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 40 EVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 41 Leaf Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 42 Leaf Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 43 ECE Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 44 UNI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 45 Ingress Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 46 Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 47 MAC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 48 Egress & Ingress Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 49 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 50 Up-MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 51 Up-MEP Leaf Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 52 Loop Protection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

ENT-AN1105 Application Note Revision 1.1 v

Figure 53 STP CIST Port Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 54 Global VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 55 Global VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 56 QoS Ingress Port Tag Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 57 QoS Egress Port Tag Remarking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 58 EVC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 59 ECE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 60 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 61 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 62 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 63 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 64 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 65 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 66 EPS List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 67 EPS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 68 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 69 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 70 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 71 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 72 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 73 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 74 Loop Protection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 75 STP CIST Port Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 76 Global VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 77 Global VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 78 Global VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 79 QoS Egress Port Tag Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 80 QoS Egress Port Tag Remarking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 81 EVC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 82 ECE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 83 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 84 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 85 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 86 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 87 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 88 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 89 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 90 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 91 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 92 ERPS Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Figure 93 ERPS Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 94 ERPS VLAN List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 95 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 96 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 97 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 98 MEP instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 99 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 100 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 101 Ethernet Ring Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 102 ERPS Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 103 ERPS VLAN List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 104 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 105 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Figure 106 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Figure 107 Global VLAN List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Figure 108 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Figure 109 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Figure 110 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 111 MEP Instance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

ENT-AN1105 Application Note Revision 1.1 vi

Figure 112 Add MEP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 113 MEP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Figure 114 Add New Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Revision History

ENT-AN1105 Application Note Revision 1.1 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.1In revision 1.1 of this document, configuration examples using WebGUI were added.

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

Service OAM Configuration


2 Service OAM Configuration

This document shows how to set up Service OAM (Y.1731 and IEEE802.1ag) using the Industrial Command Line Interface (ICLI) commands and web interface. The Microsemi Service OAM model on the Serval1 platform is outlined to describe the possible configurations.

This document is based on the ICLI Configuration guide that describes the basic usage of the Microsemi ICLI and the Service OAM reference guide that describes the Service OAM ICLI commands.

The following sections explain the OAM Model with a few configuration examples.

2.1 Understanding Service OAMService OAM is based on the IEEE 802.1ag and Y.1731 standards. Based upon these standards, the Metro Ethernet Forum has defined the MEF17 standard, which specifies the requirements and framework for Service OAM within MEF compliant Metro Ethernet networks.

The service OAM mechanism enables point-to-point or point-to-multi point Fault Management (FM) and Performance Monitoring (PM) in an Ethernet network using Maintenance End Points (MEP) and Maintenance Intermediate Points (MIP) as the building blocks.

• An MEP can be either an up-MEP or a Down-MEP.• A Down-MEP is injecting/terminating OAM against a port.• An up-MEP is injecting/terminating OAM against the forwarding plane.

In the following illustrations, MEP is represented by a triangle and MIP by a circle.

Figure 1 • Maintenance End Points

In a flow, at least two MEPs exchange OAM PDU to achieve the FM and PM functionality. A number of MEPs in the same flow can form a group called a Maintenance Entity Group (MEG).

Figure 2 • Maintenance Entity Group

In a flow, all MEPs in an MEG are on the MEG's level. Multiple MEGs can be nested in a flow in such a manner that an MEG on a higher level is able to encapsulate an MEG on a lower level. The lower level MEG is transparent to the higher level MEG PDU.

Forwarding plane

Down-MEPUp-MEP

Port Port



Figure 3 • Nested Maintenance Entity Group

Note: Before starting the ICLI configuration, please prepare a serial RS-232 cable and terminal console software for accessing the Microsemi device on the management platform. Please refer to Chapter 4.

2.2 Service OAM ModelIn the Microsemi OAM model, an MEP instance can be created in three different domains.

• Port: associated with a port• VLAN: associated with a VLAN• EVC: associated with an EVC

On a classified VID, only one OAM domain can exist. As both VLAN and EVC use a classified VID, EVC OAM and VLAN OAM cannot coexist on the same VID.

Note: Multiple MEPs in the same domain have shared MEG level. Multiple MEPs in different domains have independent MEG levels.

2.2.1 Port OAMThe following illustration shows MEPs created in the port domain. MEPs can also be created in VLAN and EVC domains.

Figure 4 • Port Domain Model

• An MEP can be created on any port as either a software-based or Microsemi OAM Engine (VOE)-based MEP.

• The port domain is untagged.

2.2.2 VLAN OAMThe following illustration shows a VLAN MEP configuration. This is in addition to the port domain MEPs.

Level n + 1

Level n

Port 1

Port 2

Port 3

Port 4



Figure 5 • VLAN Domain Model

• VLAN MEPs configured on the same VLAN have shared MEG levels.• VLAN OAM is only supported in a two-port VLAN, such as a VLAN based E-Line.• Up-MEP can be configured on one port only.• Down-MEP can be configured on both ports.• For each possible up/down-MEP, one software and one VOE based MEP can be configured.• VOE down-MEP is on a higher level than software down-MEP.• VOE up-MEP is on a lower level than software up-MEP.• Down-MEP is on a lower level than up-MEP

2.2.3 EVC OAMThe following illustration shows an EVC MEP configuration. This is in addition to the port domain MEPs.

Figure 6 • EVC Domain Model

• EVC MEPs configured in the same EVC have shared MEG levels.

SW VOE VOE SW

Level A

Level B

Level C

Level D

Port 2Port 4

SW

Level C

VOE

Level D

SW VOE VOE SW

Level A

Level B

Level C

Level D

Port 2UNI

Port 4NNI

SW SW



• EVC OAM is only supported in an E-Line.• There is only EVC up-MEP on the UNI port. There is only MIP on UNI. This is a subscriber flow MIP

that belongs to a subscriber MEG, and not the EVC MEG.• There is no EVC down-MEP on a port with EVC up-MEP.• There is one VOE and one software-based MEP on each port.• VOE down-MEP is on a higher level than software down-MEP.• VOE up-MEP is on a lower level than software up-MEP.• Down-MEP is on a lower level than up-MEP.

2.2.3.1 E-TREEAn E-Tree is a special configuration of an EVC. In an E-Tree all UNIs are either a root or leaf UNI. Service frames arriving on a leaf UNI can only be forwarded to root UNIs. Service frames arriving on a root UNI can be forwarded to other root UNIs or to leaf UNIs.

An EVC up-MEP created on a root UNI becomes a root MEP. An EVC up-MEP created on a leaf UNI becomes a leaf MEP. The following illustration shows how the root and leaf MEPs inject and extract frames in different VLANs.

Figure 7 • E-TREE Model

A root MEP has all root/leaf MEPs as peers and a leaf MEP has all root MEPs as peers.

It is only possible to have UNI software up-MEP in an E-Tree. In case of more up-MEP in same E-Tree, they must all be on the same level.

2.2.3.2 Port ProtectionPort protection is a linear protection according to G.8031.

2.2.3.3 Basic Port Protection ModelA port domain Ethernet Linear Protection Switching (ELPS) instance protects all classified VID on a (working) port. The classified VID can be related to either a VLAN or an EVC.

Leaf (UNI)

Leaf VLAN Root VLAN

Root(UNI) Root + Leaf VLAN

Root VLAN

Node 1

NNI

NNI

Root (UNI)

Root VLAN

NNI

NNI

Root + Leaf VLAN

Leaf VLAN

Root VLAN

Node 2

NNI

NNI

Leaf(UNI)

Leaf VLAN

Root VLAN

Leaf(UNI)

Node 3



Figure 8 • Basic Port Protection Model

• Port ELPS requires a working and protecting port MEP for Server Signal Fail (SSF) calculation based on continuity check and link state (G.8021), and for LAPS <-> APS PDU conversion.

• LAPS protocol information is handled by the ELPS function as specified in G.8031(11/2009).• VLAN OAM, page 3 and EVC OAM, page 4 models can be protected by this ELPS.

2.2.4 Port Protection with Service OAMThe protected classified VID can be related to either a VLAN or an EVC, and each of these can have MEPs configured. The following illustration shows a port ELPS protecting two different classified VIDs,

one related to a VLAN and another related to an EVC. In the VLAN a down-MEP is configured and in the EVC an up-MEP is configured.

Port 2

Working PortPort 4

Protecting PortPort 5

ELPS

SSF

SSF

LAPS

Port 1

Port 3



Figure 9 • Port Protection with Service OAM

2.2.5 Ring ProtectionRing protection is a VLAN protection according to G.8032.

2.2.5.1 Basic Ring Protection ModelAn Ethernet Ring Protection Switching (ERPS) instance protects the configured classified VIDs, as a node in a ring topology, through the two ring links 0/1.

Working PortPort 4

Protecting PortPort 5

ELPS

SSF

SSF

LAPS

Port 1

Port 3

Port 2

EVCUp-MEP

VLANDown-MEP



Figure 10 • Basic Ring Protection Model

• Ring link0 and link1 are ports. The ERPS requires a port MEP on link0 and link1 port for SSF calculation based on continuity check and link state (G.8021). It also requires a control VLAN down-MEP on link0 and link1 port for RAPS <-> APS PDU conversion.

• The RAPS protocol information is handled by the ERPS function as specified in G.8032(03/2010).• VLAN OAM and EVC OAM models can be protected by this ERPS.

2.2.5.2 Ring Protection with Service OAMProtected classified VIDs can be related to either a VLAN or an EVC, and each of these can have MEPs configured. The following illustration shows an ERPS protecting two different classified VIDs, one related to a VLAN and the other related to an EVC. In the VLAN and the EVC, both a down-MEP and an up-MEP are configured.

Note: VLAN/EVC down-MEPs are not protected by the ring. These are segment MEPs that can cover a section of a ring, if desired.

Port 2

Ring link0Port 4

ERPS

SSFTSF

RAPS

Ring link1Port 5

SSFTSF

RAPS

Port 3

Port 1

ERPS

Control VLANDown-MEP




Figure 11 • Ring Protection with Service OAM

2.2.5.3 Alternative SSF SourceAccording to G.8032 the Signal Fail can be taken from a test trail. In the Microsemi solution it is possible to take SSF from any created MEP instance. The following illustration shows that the control VLAN down-MEP calculates the SSF to enable multiple ring instances per port using independent continuity check functions (SSF generation).

Port 2

Ring link0Port 4

ERPS

SSFTSF

RAPS

Ring link1Port 5

SSFTSF

RAPS

Port 3

Port 1

ERPS

VLANUp-MEP

EVCUp-MEP


VLANDown-MEP


EVCDown-MEP



Figure 12 • Alternative SSF Source

2.2.6 Ring Interconnection ProtectionIn the following illustration, the virtual channel RAPS is handled by a control VLAN up-MEP resident on the sub-ring port. The ring interconnected ring model can be with or without virtual control channel through major ring.

Port 2

Ring link0Port 4

ERPS

SSF

RAPS

Ring link1Port 5

RAPS

Port 3

Port 1

ERPS



SSF



Figure 13 • Ring Interconnection Protection

• The sub-ring link is a port. The sub-ERPS instance requires a port MEP on sub-ring link port for SSF calculation based on continuity check and link state (G.8021). It also requires a control VLAN down-MEP on sub-ring port for RAPS <-> APS PDU conversion.

• The virtual control VLAN up-MEP used for RAPS handling must be a softare-based MEP.

2.3 Service OAM Configuration ExamplesThis section describes ICLI configuration examples. For more information about the models, see Service OAM Model.

2.3.1 Restore Default Setup using CLIUse the following commands to restore default settings before starting to configure any of the examples in the following sections.

1. Initiate MEP Configuration and Ensure IS1 Key Type(config)# interface GigabitEthernet 1/1-5(config-if)# evc key double-tag(config-if)# exit#

2.3.2 Restore Default Setup using WebGUIUse the following steps to restore default settings before starting to configure any of the examples in the following sections.

1. Click Maintenance > Factory Defaults.

Figure 14 • Factory Defaults

2. Click Yes.

Sub-Ring PortPort 2

Ring link0Port 4

ERPS

SSFTSF

RAPS

Ring link1Port 5

SSFTSF

RAPS

Port 3

Port 1

ERPS

RAPS

TSF

RAPS

SSF

Sub-ERPS




Virtual ControlVLAN

Up-MEP



3. Click Configuration > Ethernet Services > Ports.4. Select the Key Type to Double Tag for Ports 1 to 5.

Figure 15 • Port Configuration

2.3.2.0.1 Display all MEP Commands and Parameters! Show all MEP related ‘configuration’ commands# configure terminal(config)# mep ??mep <inst> [mip] {up | down} domain {port | evc | vlan | tp-link | tunnel-tp | pw | lsp} [vid <vid>] [flow <flow>] level <level> [interface <port_type> <port>]mep <inst> ais [fr1s | fr1m] [protect]mep <inst> aps <prio> [multi | uni] {laps | {raps [octet <octet> ]}}mep <inst> bfd cc-period <cc_period> [mode {coordinated | independent rx-flow <rx_flow>}] [cc-only] [tx-auth key <tx_key_id>] [rx-auth]mep <inst> cc <prio> [fr300s | fr100s | fr10s | fr1s | fr6m | fr1m | fr6h]mep <inst> ccm-tlvmep <inst> client domain {evc | vlan | lsp} flow <cflow> [level <level>] [ais-prio [<aisprio> | ais-highest]] [lck-prio [<lckprio> | lck-highest]]mep <inst> dm <prio> [multi | {uni mep-id <mepid>}] [single | dual] [rdtrp | flow] interval <interval> last-n <lastn>mep <inst> dm bin fd <num_fd_var>mep <inst> dm bin ifdv <num_ifdv_var>mep <inst> dm bin threshold <threshold_var>mep <inst> dm nsmep <inst> dm overflow-resetmep <inst> dm proprietarymep <inst> dm syncronizedmep <inst> lb <prio> [dei] [multi | {uni {{mep-id <mepid>} | {mac <mac>}}} | mpls ttl <mpls_ttl>] count <count> size <size> interval <interval>mep <inst> lck [fr1s | fr1m]mep <inst> level <level>



mep <inst> link-state-trackingmep <inst> lm <prio> [multi | uni] [single | dual] [fr10s | fr1s | fr6m | fr1m | fr6h] [flr <flr>]mep <inst> lm flow-countingmep <inst> lm oam-counting {[y1731 | all]}mep <inst> lt <prio> {{mep-id <mepid>} | {mac <mac>}} ttl <ttl>mep <inst> meg-id <megid> {itu | itu-cc | {ieee [name <name>]}}mep <inst> mep-id <mepid>mep <inst> peer-mep-id <mepid> [mac <mac>]mep <inst> performance-monitoringmep <inst> rt <tc> [src-id-tlv] [dst-id-tlv] [pad-tlv type {drop | copy} length <pad_tlv_len>] [flags {[V] [T] [R]}] [ttl <ttl_val>]mep <inst> syslogmep <inst> tst <prio> [dei] mep-id <mepid> [sequence] [all-zero | all-one | one-zero] rate <rate> size <size>mep <inst> tst rxmep <inst> tst txmep <inst> vid <vid>mep <inst> voemep bfd auth-key <key_id> {simple-pwd | md5 | sha1} key <auth_key>mep os-tlv oui <oui> sub-type <subtype> value <value>(config) #

2.3.2.0.2 Get MEP Status and Configuration Overview! Show all MEP related ‘show’ commands# sh mep ?show mep [<inst>] [peer | cc | lm | dm | lt | lb | tst | aps | client | ais | lck | pm | syslog | tlv | bfd | rt | lst] [detail]show mep bfd-auth-key [ <inst> ]

2.3.2.0.3 Show Command! Show status of all enabled MEP# show mepMEP state is: Inst cLevel cMeg cMep cAis cLck cSsf aBlk aTsf Peer MEP cLoc cRdi cPeriod cPrio 11 False False False False False True False True 3 False False False False

! Show status and configuration of all enabled MEP# show mep detailMEP state is: Inst cLevel cMeg cMep cAis cLck cSsf aBlk aTsf Peer MEP cLoc cRdi cPeriod cPrio 11 False False False False False True False True 3 False False False False

MEP Basic Configuration is: Inst Mode Voe PM Vola Direct Port Dom Level Format 11 Mep Voe Down GigabitEthernet 1/2 Port 2 IEEE String

! Show configuration of a selected ‘feature’# show mep cc detail

MEP CC Configuration is: Inst Prio Rate 11 4 1s



2.3.3 Port OAM Configuration According to the Port OAM, page 3 service model a down-MEP can be created on a port.

Use the following parameters to create a VOE-based port domain down-MEP.

Instance number: 1Residence port: Gigabit Ethernet port 4Level: 0MEG format: ITUMEG-ID: ICC000MEG0001MEP-ID: 1Peer MEP-ID: 2

Continuity check is enabled on priority 0 at rate 300 f/s.

2.3.3.1 Configure Port Domain OAM Down-MEP using CLI1. Enable the MEP instance.(config)# mep 1 down domain port level 0 interface GigabitEthernet 1/42. Configure the MEG-ID.(config)# mep 1 meg-id ICC000MEG0001 itu3. Configure the MEP-ID.(config)# mep 1 mep-id 14. Make it VOE-based.(config)# mep 1 voe5. Configure a peer MEP.(config)# mep 1 peer-mep-id 26. Enable Continuity check.(config)# mep 1 cc 0 fr300s7. Run the following commands to verify the configuration. (config)# do show running-config[...]mep os-tlv oui 0xC sub-type 0x1 value 0x2 mep 1 down domain port level 0 interface GigabitEthernet 1/4mep 1 meg-id ICC000MEG0001 itumep 1 voemep 1 peer-mep-id 2mep 1 cc 0 fr300s[...](config)# do show mep detailMEP state is: Inst cLevel cMeg cMep cAis cLck cSsf aBlk aTsf Peer MEP cLoc cRdi cPeriod cPrio 1 False False False False False True False True 2 False False False FalseMEP Basic Configuration is: Inst Mode Voe Direct Port Dom Level Format Meg id Mep id Flow 1 Mep Voe Down 1/4 Port 0 ITU ICC ICC000MEG0001 1 4 (config)# do show mep cc detailMEP CC Configuration is: Inst Prio Rate 1 0 300s

2.3.3.2 Configure Port Domain OAM Down-MEP using WebGUIUse the following steps to configure the port domain OAM down-MEP:



1. Click Configuration > MEP.

Figure 16 • MEP Instance List

2. Click Add New MEP to create a new MEP instance:3. Select Domain, Mode, Direction, Port and Level for the MEP instance and click Save.

Figure 17 • Add MEP instance

4. Click the MEP Instance to add details to the MEP.5. Select parameters such as MEP ID, MEG ID, and VOE. To add Peer MEP detail click the Add New

Peer MEP.6. Select parameters such as Continuity Check configuration Enable, Priority, and Frame Rate. 7. Click Save.

Figure 18 • MEP Configuration

2.3.4 VLAN OAM ConfigurationAccording to the VLAN OAM, page 3 service model both up- and down-MEP can be created in a VLAN. Before up- or down-MEP is created, create VLAN. A VLAN 111 is created with port members 1 and 4.

2.3.4.1 Configure Global VLAN using CLI1. Create the VLAN 111(config)# vlan 1112. Make port 1 and 4 member of VLAN 111.(config-vlan)# interface GigabitEthernet 1/1,4(config-if)# switchport hybrid allowed vlan 111(config-if)# switchport mode hybrid(config-if)# exit

In VLAN 111 a down-MEP can be created.



Use the following parameters to create a VOE-based VLAN domain down-MEP.



2.3.4.2 Configure Global VLAN using WebGUIUse the following steps to configure a global VLAN.

1. Click Configuration >VLANs.

Figure 19 • Global VLAN Configuration

2. Add 111 to Allowed Access VLANs 3. Update Allowed VLANs for port 1 and 4 with 111. 4. Set the mode for port 1 and 4 to Hybrid.

2.3.4.3 Configure VLAN Domain OAM Down-MEP using CLI1. Enable the MEP instance.(config)# mep 2 down domain vlan flow 111 level 0 interface GigabitEthernet 1/42. Configure the MEG-ID.(config)# mep 2 meg-id ICC000MEG0001 itu3. Configure the MEP-ID.(config)# mep 2 mep-id 14. Make it VOE-based.(config)# mep 2 voe5. Configure a peer MEP.(config)# mep 2 peer-mep-id 26. Enable Continuity check.(config)# mep 2 cc 7 fr1s7. Run the following commands to verify the configuration.(config)# do show running-config[...]mep os-tlv oui 0xC sub-type 0x1 value mep 2 down domain vlan flow 111 level 0 interface GigabitEthernet 1/4mep 2 meg-id ICC000MEG0001 itumep 2 voemep 2 peer-mep-id 2mep 2 cc 7[...](config)# do show mep detail



MEP state is: Inst cLevel cMeg cMep cAis cLck cSsf aBlk aTsf Peer MEP cLoc cRdi cPeriod cPrio 2 False False False False False True False True 2 False False False FalseMEP Basic Configuration is: Inst Mode Voe Direct Port Dom Level Format Meg id Mep id Flow 2 Mep Voe Down 1/4 Vlan 0 ITU ICC ICC000MEG0001 1 111 (config)# do show mep cc detailMEP CC Configuration is: Inst Prio Rate 2 7 1s

In VLAN 111 an up-MEP can be created.

Use the following parameters to create a VOE-based VLAN domain up-MEP.

Instance number: 3Residence port: Gigabit Ethernet port 1Level: 3MEG format: IEEEDomain Name: DOMAIN000MEG-ID: ICC000MEG0001MEP-ID: 1Peer MEP-ID: 2


2.3.4.4 Configure VLAN Domain OAM Down-MEP using WebGUIUse the following steps o configure the VLAN domain OAM down-MEP perform the:

1. Click Configuration >MEP.


2. Click Add New MEP to create a new MEP instance.3. Select parameters such as Domain, Mode, Direction, Port, and Level for the MEP instance and

click Save.

Figure 21 • Add MEP Instance

4. Click the MEP Instance to add details on the MEP.5. Select MEP ID, MEG ID, and VOE. To add Peer MEP detail click Add New Peer MEP.6. Select Continuity Check configuration Enable, Priority, and Frame Rate.7. Click Save to update the MEP instance.




2.3.4.5 Configure VLAN Domain OAM Up-MEP using CLI# configure terminal! Enable the MEP instance(config)# mep 3 up domain vlan flow 111 level 3 interface GigabitEthernet 1/1! Configure the MEG-ID(config)# mep 3 meg-id IEEE000MEG0001 ieee name DOMAIN000! Configure the MEP-ID(config)# mep 3 mep-id 1! Make it VOE-based(config)# mep 3 voe! Configure a peer MEP(config)# mep 3 peer-mep-id 2! Enable Continuity check(config)# mep 3 cc 7 fr300s

Run the following commands to verify the configuration.

(config)# do show running-config[...]mep 3 up domain vlan flow 111 level 3 interface GigabitEthernet 1/1mep 3 meg-id IEEE000MEG0001 ieee name DOMAIN000mep 3 voemep 3 peer-mep-id 2mep 3 cc 7 fr300s[...](config)# do show mep detailMEP state is: Inst cLevel cMeg cMep cAis cLck cSsf aBlk aTsf Peer MEP cLoc cRdi cPeriod cPrio 3 False False False False False True False True 2 False False False FalseMEP Basic Configuration is: Inst Mode Voe Direct Port Dom Level Format Name Meg id Mep id Flow 3 Mep Voe Up 1/1 Vlan 3 IEEE String DOMAIN000 IEEE000MEG0001 1 111 (config)# do show mep cc detail



MEP CC Configuration is: Inst Prio Rate 3 7 300

2.3.4.6 Configure VLAN Domain OAM Up-MEP using WebGUIUse the following steps to configure the VLAN domain OAM up-MEP.



2. Click Add New MEP to create a new MEP instance.3. Select Domain, Mode, Direction, Port, and Level for the MEP instance and click Save to add the

MEP instance.


4. Click the MEP Instance to add details on the MEP5. Select MEP ID, MEG ID, and VOE. To add Peer MEP detail click the Add New Peer MEP.6. Select parameters such as Continuity Check configuration Enable, Priority, and Frame Rate.7. Click Save.


2.3.5 EVC OAM ConfigurationAccording to the EVC OAM service model both up- and down-MEP can be created in an EVC.



2.3.5.1 Configure an EVC Instance using CLIUse the following steps to create an EVC instance 1 with port 4 as NNI, port 3 as UNI, and 222 as internal VID.

1. Create the EVC.evc 1 vid 222 ivid 222 interface GigabitEthernet 1/42. Map any frame on UNI to COS 4 in the EVC.evc ece 1 interface GigabitEthernet 1/3 outer-tag add pcp-mode mapped pcp 4 cos 4

2.3.5.2 Configure an EVC Instance using WebGUIUse the following steps to create an EVC instance 1 with port 4 as NNI, port 3 as UNI, and 222 as internal VID.

1. Click Configuration >Ethernet Services > EVCs.2. Click Add New EVC to create a new EVC instance. 3. Select EVC ID, NNI Port, VID, and IVID as shown in the following figure.

Figure 26 • EVC Configuration

4. Click Configuration >Ethernet Services > ECEs.5. To add new ECE, Click Add New ECE. Select different ECE parameters as shown in the following

figure, and click Save.



Figure 27 • ECE Configuration

2.3.5.3 Set UNI PVID to Unused VLAN using CLIUse the following steps to set UNI PVID to an unused VLAN to discard non-classified frames, exclude UNI port from the VLAN OAM VID, and configure UNI as C-port.

1. Change to interface 3 (UNI) sub-mode.interface GigabitEthernet 1/32. Set the port based classified VID to an unused value.switchport hybrid native vlan 40953. Exclude this port from the VLAN OAM VID.switchport forbidden vlan add 1114. Make the UNI a C port.switchport hybrid port-type c-port5. Make the UNI a hybrid port.switchport mode hybrid

2.3.5.4 Set NNI PVID to Unused VLAN using CLIUse the following steps to set the NNI PVID to an unused VLAN to discard non-classified frames and

configure NNI as S-port.



1. Change to interface 4 (NNI) sub-mode.interface GigabitEthernet 1/42. Set the port based classified VID to an unused value.switchport hybrid native vlan 40953. Make the NNI an S port.switchport hybrid port-type s-port4. Make the NNI a hybrid port.switchport mode hybrid

2.3.5.5 Set NNI PVID to Unused VLAN using WebGUIUse the following steps to set the NNI PVID to an unused VLAN to discard non-classified frames and

configure NNI as S-port.

1. Click Configuration >VLAN > Configuration.2. Set the Mode, Port VLAN, Port type, and Forbidden VLANs for port 3 and 4 as shown in the

following figure.


2.3.5.6 Enable Ingress Mapping from PCP to CoS on UNI and NNI using CLIUse the following steps to enable ingress one-to-one mapping from PCP to CoS on UNI and NNI.

1. Change to interface 3,4 sub-mode.interface GigabitEthernet 1/3,42. Set Trust configuration.qos trust tag3. Configure PCP and DEI mapping to one-to-one.qos map tag-cos pcp 0 dei 0 cos 0 dpl 0qos map tag-cos pcp 0 dei 1 cos 0 dpl 1qos map tag-cos pcp 1 dei 0 cos 1 dpl 0qos map tag-cos pcp 1 dei 1 cos 1 dpl 1exit

2.3.5.7 Enable Ingress Mapping from PCP to CoS on UNI and NNI using WebGUIUse the following steps to enable ingress one-to-one mapping from PCP to CoS on UNI and NNI.



1. Click Configuration >QOS > Port Classification > Tag Class (for Port 3). Set the parameters as shown in the following figure.

Figure 29 • QoS Ingress Port Tag Classification

2. Repeat step 1 to configure port 4.

2.3.5.8 Enable Ingress Mapping from CoS to PCP on UNI and NNI using CLIUse the following steps to enable ingress one-to-one mapping from CoS to PCP on UNI and NNI.

1. Change to interface 3,4 sub-mode.interface GigabitEthernet 1/3,42. Set Tag remarking configuration.qos tag-remark mapped3. Configure PCP and DEI mapping to one-to-one.qos map cos-tag cos 0 dpl 0 pcp 0 dei 0qos map cos-tag cos 0 dpl 1 pcp 0 dei 1qos map cos-tag cos 1 dpl 0 pcp 1 dei 0qos map cos-tag cos 1 dpl 1 pcp 1 dei 1exit

In EVC 1 a down-MEP can be created.

Use the following parameters to create a software-based EVC domain down-MEP.



2.3.5.9 Enable Ingress Mapping from CoS to PCP on UNI and NNI using WebGUIUse the following steps to enable ingress one-to-one mapping from CoS to PCP on UNI and NNI.

1. Click Configuration >QOS > Port Tag Remarking.2. Click Port 3 and set the parameters such as Tag Remarking Mode, QOS Class, and DP level.



Figure 30 • QoS Egress Port Tag Remarking

2.3.5.10 EVC Domain OAM Down-MEP Configuration using CLIUse the following steps to configure EVC domain OAM down-MEP.

1. Enable the MEP instance.mep 4 down domain evc flow 1 level 0 interface GigabitEthernet 1/42. Configure the MEG-ID.mep 4 meg-id ICC000MEG0001 itu3. Configure the MEP-ID.mep 4 mep-id 14. Configure a peer MEP.mep 4 peer-mep-id 25. Enable continuity check.mep 4 cc 4 fr1s

Run the following commands to verify the configuration

(config)# do show running-config[...]mep 4 down domain evc flow 1 level 0 interface GigabitEthernet 1/4mep 4 meg-id ICC000MEG0001 itumep 4 peer-mep-id 2mep 4 cc 4 [...](config)# do show mep detailMEP state is: Inst cLevel cMeg cMep cAis cLck cSsf aBlk aTsf Peer MEP cLoc cRdi cPeriod cPrio 4 False False False False False True False True 2 False False False FalseMEP Basic Configuration is: Inst Mode Voe Direct Port Dom Level Format Meg id Mep id Flow 4 Mep Down 1/4 Evc 0 ITU ICC ICC000MEG0001 1 1 (config)# do show mep cc detailMEP CC Configuration is: Inst Prio Rate



4 4 1s

In EVC 1 an up-MEP can be created. Use the following parameters to create a VOE-based EVC domain up-MEP.

Instance number: 5Residence port: Gigabit Ethernet port 3Level: 7MEG format: IEEEDomain Name: DOMAIN000MEG-ID: IEEE000MEG0001MEP-ID: 1Peer MEP-ID: 2


2.3.5.11 EVC Domain OAM Down-MEP Configuration using WebGUIUse the following steps to configure EVC domain OAM down-MEP.



2. Click Add New MEP to create a new MEP instance.3. Select Domain, Mode, Direction, Port, and Level for the MEP instance and click Save.


4. Click the MEP Instance to add details on the MEP.5. Select MEP ID, MEG ID, and VOE. To add Peer MEP detail click Add New Peer MEP.6. Select Continuity Check configuration Enable, Priority, and Frame Rate.7. Click Save.




2.3.5.12 EVC Domain OAM Up-MEP Configuration using CLIUse the following steps to configure a VOE based EVC domain OAM up-MEP.

1. Enable the MEP instance.(config)# mep 5 up domain evc flow 1 level 7 interface GigabitEthernet 1/32. Configure the MEG-ID.(config)# mep 5 meg-id ICC000MEG0001 ieee name DOMAIN0003. Configure the MEP-ID.mep 5 mep-id 14. Make MEP-ID VOE based.mep 5 voe5. Configure a peer MEP.mep 5 peer-mep-id 26. Enable continuity check.mep 5 cc 4 fr300s


(config)# do show running-config[...]mep 5 up domain evc flow 1 level 7 interface GigabitEthernet 1/3mep 5 meg-id ICC000MEG0001 ieee name DOMAIN000mep 5 voemep 5 peer-mep-id 2mep 5 cc 4 fr300s[...](config)# do show mep detailMEP state is: Inst cLevel cMeg cMep cAis cLck cSsf aBlk aTsf Peer MEP cLoc cRdi cPeriod cPrio 5 False False False False False True False True 2 False False False FalseMEP Basic Configuration is:



Inst Mode Voe Direct Port Dom Level Format Name Meg id Mep id Flow 5 Mep Voe Up 1/3 Evc 7 IEEE String DOMAIN000 IEEE000MEG0001 1 1 (config)# do show mep cc detailMEP CC Configuration is: Inst Prio Rate 5 4 300s

2.3.5.13 Configure EVC Domain OAM Up-MEP using WebGUIUse the following steps to configure EVC domain OAM Up-MEP.



2. Click Add New MEP to create a new MEP instance.3. Select Domain, Mode, Direction, Port, and Level for the MEP instance and click Save.


4. Click MEP Instance (instance 5 for this example) to add details on the MEP.5. Select MEP ID, MEG ID, and VOE. To add Peer MEP detail click Add New Peer MEP.6. Select Continuity Check configuration Enable, Priority, and Frame Rate.7. Click Save.




2.3.6 E-TREE OAM Configuration Example

2.3.6.1 Configure E-TREE OAM using CLIThis section shows the commands used to complete the following tasks.

1. Set up an E-tree service (no-bundling) on a leaf UNI (port 2) for CEVLAN ID 73.2. Set up an E-tree service (no-bundling) on a root UNI (port 3) for CEVLAN ID 73.3. On NNI egress, add one tag: outer VID = 103 (loot), VID = 104 (Leaf).4. On NNI ingress, pop one tag5. Match on an NNI (port 4) for root VID = 103 or leaf VID = 104, and inner VID=73.6. Create a root up-MEP of instance 5, EVC flow 6, and service level 7. 7. Create a Leaf up-MEP of instance 6, EVC flow 6, and service level 7.



Figure 37 • E-Tree Configuration

2.3.6.1.1 Creating EVC1. Create EVC.evc 6 vid 103 ivid 103 interface GigabitEthernet 1/1 leaf vid 104 ivid 104 interface GigabitEthernet 1/2 learning policer none2. Create an ECE for UNI#1 (leaf UNI).evc ece 1 interface GigabitEthernet 1/2 outer-tag match type tagged vid 73 evc 6 policer none cc 43. Create an ECE for UNI#2 (root UNI).evc ece 2 interface GigabitEthernet 1/3 outer-tag match type tagged vid 73 evc 6 policer none cc 4

2.3.6.1.2 Creating Root Up-MEP1. Enable the Up-MEP instancemep 5 up domain evc flow 6 level 7 interface GigabitEthernet 1/32. Configure the MEG-ID.(config)# mep 5 meg-id ICC000MEG0001 ieee name DOMAIN0003. Configure the MEP-ID.mep 5 mep-id 14. Configure a peer MEP.mep 5 peer-mep-id 25. Enable continuity check.mep 5 cc 4 fr1s

2.3.6.1.3 Creating Leaf Up-MEP1. Enable the Up-MEP instancemep 6 up domain evc flow 6 level 7 interface GigabitEthernet 1/22. Configure the MEG-ID.mep 6 meg-id ICC000MEG0002 ieee name DOMAIN001 3. Configure the MEP-ID.mep 6 mep-id 24. Configure a peer MEP.mep 6 peer-mep-id 35. Enable continuity check.mep 6 cc 4 fr1s

VID73

VID73 VID73

VID73 VID104

VID103

Leaf UNI

Root UNI

Preserve

NNI

RemoveAdd

Preserve

Remove

NNI

Add




(config)# do show running-config[...]mep 5 up domain evc flow 6 level 7 interface GigabitEthernet 1/3mep 5 meg-id ICC000MEG0001 ieee name DOMAIN000mep 5 peer-mep-id 2mep 5 cc 4mep 6 up domain evc flow 6 level 7 interface GigabitEthernet 1/2mep 6 meg-id ICC000MEG0002 ieee name DOMAIN001mep 6 mep-id 2mep 6 peer-mep-id 3mep 6 cc 4[...]

(config)# do show mep detail

MEP state is:Inst cLevel cMeg cMep cAis cLck cLoop cConf cDeg cSsf aBlk aTsd aTsf Peer MEP cLoc cRdi cPeriod cPrio 5 False True False False False False False False True True False True 2 False False False False 6 False True False False False False False False True True False True 3 False False False False

MEP Basic Configuration is:Inst Mode Voe Direct Port Dom Level Format Name Meg id Mep id Vid Flow Eps MAC 5 Mep Root 1/3 Evc 7 IEEE String DOMAIN000 ICC000MEG0001 1 0 6 0 00-01-C1-00-AF-B3 6 Mep Leaf 1/2 Evc 7 IEEE String DOMAIN001 ICC000MEG0002 2 0 6 0 00-01-C1-00-AF-B2

(config)# do show mep cc detailMEP CC Configuration is:Inst Prio Rate Tlv5 4 1s6 4 1s

2.3.6.2 E-TREE OAM Configuration using WebGUI

2.3.6.2.1 Creating EVCUse the following steps to configure EVC from the web interface. Click Help to display information on the available fields and configuration options.

1. Click Configuration > Ethernet Services > EVCs.

The EVC Control List Configuration page opens.

Figure 38 • EVC Control List Configuration

2. To add a new EVC, click Add New EVC on the EVC Control List Configuration page.

The EVC Configuration page opens.

3. To assign Leaf NNIs for E-Tree, select an appropriate NNI port from under the NNI Ports section in the EVC Configuration page.



Figure 39 • NNI Ports

4. To set the EVC parameters, provide the appropriate details under the EVC Parameters section in the EVC Configuration page as shown in the following figure.

Figure 40 • EVC Parameters

5. To set the leaf parameters, provide the appropriate details under the Leaf Parameters section in the EVC Configuration page.

Figure 41 • Leaf Parameters

6. To assign the leaf ports, select the appropriate ports from under the Leaf Ports section in the EVC Configuration page.

Figure 42 • Leaf Ports

7. Click Save.

2.3.6.2.2 Configure ECEUse the following steps to configure ECEs for the Leaf and Root UNIs from the web interface. Click Help to display information on the available fields and configuration options.

1. Click Configuration > Ethernet Services > ECEs.

The ECE Control List Configuration page opens.

Figure 43 • ECE Control List



2. To add new ECE, click Add New ECE in the ECE Control List Configuration page.

The ECE Configuration page opens.

3. To assign Leaf/Root UNIs for E-Tree, select an appropriate UNI port from under the UNI Ports section in the ECE Configuration page.

Figure 44 • UNI Ports

Only UNIs selected as Leaf are treated as Leaf UNIs, and the other UNIs in the configuration are automatically treated as Root UNIs.

4. To set the Ingress matching, provide the appropriate details under the Ingress Matching section in the ECE Configuration page.

Figure 45 • Ingress Matching

5. To set the appropriate actions, provide the appropriate details under the Actions section in the ECE Configuration page.

Figure 46 • Actions

6. To set the MAC parameters, provide the appropriate details under the MAC Parameters section, in the ECE Configuration page.

Figure 47 • MAC Parameters



7. To set the MAC parameters, provide the appropriate details under the MAC Parameters section, in the ECE Configuration page.

Figure 48 • Egress & Ingress Setting

8. Click Save.

2.3.6.2.3 Creating Root and Leaf up-MEPUse the following steps to create Root and Leaf up-MEP. Click Help to display information on the available fields and configuration options.

1. Under Configuration, Click MEP. The Maintenance Entity Point page opens.


2. To add a new Root up-MEP, Click Add New MEP. Provide the Root up-MEP details.

Figure 50 • Up-MEP Configuration

3. Click Save.4. To add a new Leaf up-MEP, Click Add New MEP. Provide the Leaf up-MEP details.

Figure 51 • Up-MEP Leaf Configuration

5. Click Save.

2.3.7 Port Protection Configuration

2.3.7.1 Disable Loop Protection and Spanning Tree using CLIPort protection is a linear protection according to G.8031.

The following configuration example shows how MEP is used for linear protection. For more information, see Port Protection with Service OAM, page 6.

Loop protection and spanning tree must be disabled for ELPS to work. Any previously created MEP must be deleted using command no mep <inst>.



1. Change to interface 4,5 sub-mode.(config)# interface GigabitEthernet 1/4,52. Disable Loop Protection.(config-if)# no loop-protect3. Disable Spanning Tree.(config)# no spanning-tree(config-if)# exit

2.3.7.2 Disable Loop Protection and Spanning Tree using WebGUIUse the following steps to configure MEP for linear protection.

1. Click Configuration >Loop Protection.2. Clear Enable option corresponding to ports 4 and 5.

Figure 52 • Loop Protection Configuration

3. Click Configuration >Spanning Tree >CIST Ports.4. Clear STP Enabled to port 4 and 5.

Figure 53 • STP CIST Port Protection

2.3.7.3 Configure Port Protected VLAN using CLIConfigure the VLAN to be port protected. For more information, see VLAN OAM Configuration, page 15.

1. Create VLAN 111.(config)# vlan 1112. Configure the VLAN aggregation port.(config)# interface GigabitEthernet 1/1(config-if)# switchport hybrid native vlan 111(config-if)# switchport hybrid allowed vlan 111(config-if)# switchport hybrid port-type c-port(config-if)# switchport mode hybrid(config-if)# exit



3. Configure the VLAN protection ports.(config)# interface GigabitEthernet 1/4,5(config-if)# switchport hybrid native vlan 4095(config-if)# switchport hybrid allowed vlan 111(config-if)# switchport hybrid port-type s-port(config-if)# switchport mode hybrid(config-if)# exit

2.3.7.4 Configure Port Protected VLAN using WebGUIUse the following steps to configure VLAN for port protection.

1. Click Configuration >VLAN > Configuration.2. Set the Mode, Port VLAN, Port type and Forbidden VLANs for ports 1, 4, and 5 as shown in the

following figure.


2.3.7.5 Configure Port Protected EVC using CLIConfigure the EVC to be port protected. For more information, see VLAN OAM, page 3.

1. Configure the UNI port.(config)# interface GigabitEthernet 1/3(config-if)# switchport hybrid native vlan 4095(config-if)# switchport forbidden vlan add 111(config-if)# switchport hybrid port-type c-port(config-if)# switchport mode hybrid(config-if)# exit2. Configure PCP and DEI mapping to one-to-one on UNI and the protection ports.(config)# interface GigabitEthernet 1/1,3,4,5(config-if)# qos trust tag(config-if)# qos map tag-cos pcp 0 dei 0 cos 0 dpl 0(config-if)# qos map tag-cos pcp 0 dei 1 cos 0 dpl 1(config-if)# qos map tag-cos pcp 1 dei 0 cos 1 dpl 0(config-if)# qos map tag-cos pcp 1 dei 1 cos 1 dpl 1(config-if)# qos map cos-tag cos 0 dpl 0 pcp 0 dei 0(config-if)# qos map cos-tag cos 0 dpl 1 pcp 0 dei 1(config-if)# qos map cos-tag cos 1 dpl 0 pcp 1 dei 0(config-if)# qos map cos-tag cos 1 dpl 1 pcp 1 dei 1(config-if)# exit3. Create the EVC.(config)# evc 1 vid 222 ivid 222 interface GigabitEthernet 1/4,5(config)# evc ece 1 interface GigabitEthernet 1/3 outer-tag add pcp-mode mapped pcp 4 cos 4Configure Port Protected EVC using WebGUI

Use the following steps to configure the EVC to be port protected.



1. Click Configuration >VLAN > Configuration.2. Set the Mode, Port VLAN, Port type and Forbidden VLANs for ports 3 as shown in the following

figure.


3. To configure PCP and DEI mapping to one-to-one on UNI and the protection ports, Click Configuration > QOS > Port Classification > Tag Class (for Port 3) and set the parameters as shown in the following figure.

4. Set port 1, 4, and 5 to use the following configuration.

Figure 56 • QoS Ingress Port Tag Classification.

5. Click Configuration> QOS >Port Tag Remarking.6. Set Tag Remarking Mode, QOS Class, and DP level parameters for port 1, 3, 4, and 5 to use the

following configuration.7. Similarly, configure port 1, 4, and 5.




8. Click Configuration >Ethernet Services > EVCs.9. To add new EVC, click the Add New EVC. 10. Set EVC ID, NNI Port, VID, IVID as shown in the following figure.


11. Click Configuration > Ethernet Services > ECEs12. To add new ECE, click Add New ECE. 13. Set the ECE parameters to use the following configuration.




2.3.7.6 Create Down-MEP on Protecting Port using CLICreate port down-MEP on working and protecting port. For more information, see Port OAM Configuration, page 14.

1. Configure Down-MEP on working port.(config)# mep 1 down domain port level 0 interface GigabitEthernet 1/4(config)# mep 1 meg-id ICC000MEG0001 itu(config)# mep 1 mep-id 1(config)# mep 1 voe(config)# mep 1 peer-mep-id 2(config)# mep 1 cc 0 fr300s2. Configure Down-MEP on protecting port.(config)# mep 2 down domain port level 0 interface GigabitEthernet 1/5(config)# mep 2 meg-id ICC000MEG0001 itu(config)# mep 2 mep-id 1(config)# mep 2 voe(config)# mep 2 peer-mep-id 2(config)# mep 2 cc 0 fr300s

Create 1:1 port protection instance with revertive enabled. Port 4 is the working port and port 5 is the protecting port. For more information, see Port Protection with Service OAM, page 6.



2.3.7.7 Create Down-MEP on Protecting Port using WebGUIUse the following steps to create the Down-MEP on Protecting Port.



2. To create a new MEP instance, click Add New MEP. Select Domain, Mode, Direction, Port, and Level for the MEP instance.

3. Click Save.


4. To add details to the MEP instance 1, click the MEP Instance and select MEP ID, MEG ID, and VOE. 5. To add Peer MEP detail, click Add New Peer MEP. Select Continuity Check configuration Enable,

Priority, and Frame Rate. 6. Click Save.


2.3.7.8 Configure Down-MEP on Protecting Port using CLI1. Configure Down-MEP on protecting port.(config)# mep 2 down domain port level 0 interface GigabitEthernet 1/5(config)# mep 2 meg-id ICC000MEG0001 itu(config)# mep 2 mep-id 1(config)# mep 2 voe(config)# mep 2 peer-mep-id 2(config)# mep 2 cc 0 fr300s



2.3.7.9 Configure Down-MEP on Protecting Port using WebGUIUse the following steps to configure the Down-MEP on Protecting Port.




3. Click Save.


4. To add details on the MEP, click the MEP Instance and select MEP ID, MEG ID, and VOE. 5. To add Peer MEP detail, click Add New Peer MEP. Select Continuity Check configuration Enable,



2.3.7.10 Configure Port Protection with MEP Relation using CLI1. Create the ELPS instance.(config)# eps 1 domain port architecture 1for1 work-flow GigabitEthernet 1/4 protect-flow GigabitEthernet 1/52. Configure the working MEP, Protecting MEP and APS MEP relations.(config)# eps 1 mep-work 1 mep-protect 2 mep-aps 2 ! Configure the WTR timer



(config)# eps 1 revertive 10s3. Run the following commands to verify the configuration.(config)# do show running-config[...]eps 1 domain port architecture 1for1 work-flow GigabitEthernet 1/4 protect-flow GigabitEthernet 1/5eps 1 mep-work 1 mep-protect 2 mep-aps 2eps 1 revertive 10s[...](config)# do show eps detailEPS state is: Inst State Wstate Pstate TxAps r b RxAps r b FopPm FopCm FopNr FopNoAps 1 SfP Sf Sf SFp 0 0 NR 0 0 False False False FalseEPS Configuration is: Inst Dom Archi Wflow Pflow Wmep Pmep APSmep Direct Revert Wtr Hold Aps 1 Port 1for1 4 5 1 2 2 Bidir True w10s 0 True

2.3.7.11 Configure Port Protection with MEP Relation using WebGUIUse the following steps to configure Down-MEP on Protected Port.

1. Click Configuration and then click Add New EPS to create an EPS instance.

Figure 66 • EPS List

2. Click the EPS ID (1 in this Example) and select the Revertive option and set WTR Time to 10s.

Figure 67 • EPS Configuration

2.3.7.12 Create Protected VLAN Down-MEP on Protected Port using CLICreate a protected VLAN down-MEP on the protected port. For more information, see Configure VLAN Domain OAM Down-MEP using CLI, page 16.

1. Enable the VLAN Down-MEP instance.(config)# mep 3 down domain vlan flow 111 level 0 interface GigabitEthernet 1/4(config)# mep 3 meg-id ICC000MEG0001 itu(config)# mep 3 mep-id 1(config)# mep 3 voe(config)# mep 3 peer-mep-id 2(config)# mep 3 cc 7 fr300s



2.3.7.13 Create Protected VLAN Down-MEP on Protected Port using WebGUIUse the following step to create protected VLAN down-MEP on Protected Port.




3. Click Save.





2.3.7.14 Create Protected VLAN Up-MEP on UNI using CLICreate protected EVC Up-MEP on the UNI. For more information, see EVC Domain OAM Up-MEP Configuration using CLI, page 26.

1. Enable the EVC Up-MEP instance.(config)# mep 4 up domain evc flow 1 level 7 interface GigabitEthernet 1/3



(config)# mep 4 meg-id ICC000MEG0001 ieee name DOMAIN000(config)# mep 4 mep-id 1(config)# mep 4 peer-mep-id (config)# mep 4 cc 4 fr300s

2.3.7.15 Create Protected VLAN Up-MEP on UNI using WebGUIUse the following step to create protected VLAN Down-MEP on Protected Port.




3. Click Save.







2.3.8 Ring Protection Configuration ExamplesA ring protection is a VLAN protection according to G.8032.

2.3.8.1 Disable Loop Protection and Spanning Tree using CLIThe following configuration example, related to the Service OAM, shows how MEP is used for ring protection. For more information, see Ring Protection with Service OAM, page 8.

Loop protection and spanning tree must be disabled for ERPS to work.

1. Change to interface 4,5 sub-mode.(config)# interface GigabitEthernet 1/4,52. Disable Loop Protection.(config-if)# no loop-protect3. Disable Spanning Tree.(config)# no spanning-tree

2.3.8.2 Disable Loop Protection and Spanning Tree using WebGUIUse the following step to configure MEP for Ring Protection.

1. Click Configuration > Loop Protection.2. Clear Enable foe port 4 and port 5.

Figure 74 • Loop Protection Configuration

3. Click Configuration > Spanning Tree > CIST Ports.4. Clear STP Enabled from port 4 and port 5.

Figure 75 • STP CIST Port Configuration

2.3.8.3 Configure Ring Protection for VLAN using CLIConfigure the VLAN to be ring protected. For more information, see VLAN OAM Configuration, page 15.



1. Create VLAN 111.(config)# vlan 1112. Configure the VLAN aggregation port.(config)# interface GigabitEthernet 1/1(config-if)# switchport hybrid native vlan 111(config-if)# switchport hybrid allowed vlan 111(config-if)# switchport hybrid port-type c-port(config-if)# switchport mode hybrid(config-if)# exit3. Configure the VLAN ring ports.(config)# interface GigabitEthernet 1/4,5(config-if)# switchport hybrid native vlan 4095(config-if)# switchport hybrid allowed vlan 111(config-if)# switchport hybrid port-type s-port(config-if)# switchport mode hybrid(config-if)# exit

2.3.8.4 Configure Ring Protection for VLAN using WebGUIUse the following step to configure MEP for Ring Protection.

1. Click Configuration > VLANs > Configuration.2. Set the parameters such as Mode, Port VLAN, Port type, and Allowed VLANs port 4 and port 5 to

use the following configuration.


2.3.8.5 Configure ERPS Control VLAN using CLIConfigure the ERPS control VLAN.

1. Create ERPS control VLAN 333.(config)# vlan 3332. Configure the ERPS control VLAN on the ring ports.(config)# interface GigabitEthernet 1/4,5(config-if)# switchport hybrid allowed vlan 333(config-if)# switchport mode hybrid(config-if)# exit

2.3.8.6 Configure ERPS Control VLAN using WebGUIUse the following step to configure ERPS Control VLAN.

1. Click Configuration > VLANs > Configuration. 2. Set the parameters such as Mode, Port VLAN, Port type, and Allowed VLANs for port 4 and port

5 to use the following configuration.




[

2.3.8.7 Configure Ring Protection for EVC using CLIConfigure an EVC to be ring protected. For more information, see EVC OAM Configuration, page 19.

1. Configure the UNI port.(config)# interface GigabitEthernet 1/3(config-if)# switchport hybrid native vlan 4095(config-if)# switchport forbidden vlan add 111(config-if)# switchport hybrid port-type c-port(config-if)# switchport mode hybrid(config-if)# exit2. Configure PCP and DEI mapping to one-to-one on UNI and the protection ports.(config)# interface GigabitEthernet 1/1,3,4,5(config-if)# qos trust tag(config-if)# qos map tag-cos pcp 0 dei 0 cos 0 dpl 0(config-if)# qos map tag-cos pcp 0 dei 1 cos 0 dpl 1(config-if)# qos map tag-cos pcp 1 dei 0 cos 1 dpl 0(config-if)# qos map tag-cos pcp 1 dei 1 cos 1 dpl 1(config-if)# qos map cos-tag cos 0 dpl 0 pcp 0 dei 0(config-if)# qos map cos-tag cos 0 dpl 1 pcp 0 dei 1(config-if)# qos map cos-tag cos 1 dpl 0 pcp 1 dei 0(config-if)# qos map cos-tag cos 1 dpl 1 pcp 1 dei 1(config-if)# exit3. Create the EVC.(config)# evc 1 vid 222 ivid 222 interface GigabitEthernet 1/4,5(config)# evc ece 1 interface GigabitEthernet 1/3 outer-tag add pcp-mode mapped pcp 4 cos 4

2.3.8.8 Configure Ring Protection for EVC using WebGUIUse the following step to configure an EVC to be ring protected.

1. Click Configuration > VLANs > Configuration. 2. Set the parameters such as Mode, Port VLAN, Port type, and Allowed VLANs for port 3 to use the

following configuration.




3. Click Configuration > QOS > Port Classification > Tag Class and set the parameters for ports 1, 3, 4, and 5 to use the following configuration.

Figure 79 • QoS Egress Port Tag Classification

4. Click Configuration > QOS > Port Tag Remarking.5. Click Port 3 and set Tag Remarking Mode, QOS Class, and DP level parameters to use the

following configuration.6. Similarly, set the parameters for ports 1, 4, and 5 by changing the port number to 1, 4, and 5

respectively.




7. Click Configuration >Ethernet Services > EVCs.8. To add new EVC, click Add New EVC. 9. Set EVC ID, NNI Port, VID, IVID to use the following configuration.


10. Click Configuration >Ethernet Services > ECEs.11. To add new ECE, click Add New ECE.12. Set the ECE parameters to the following configuration.




2.3.8.9 Create Port Down-MEP on Ring Link Port 0 and 1 using CLICreate port down-MEP on ring link 0 and ring link 1 port. For more information, see Configure Port Domain OAM Down-MEP using CLI, page 14.

1. Configure Down-MEP on ring link 0 port.(config)# mep 1 down domain port level 0 interface GigabitEthernet 1/4(config)# mep 1 meg-id ICC000MEG0001 itu(config)# mep 1 mep-id 1(config)# mep 1 voe(config)# mep 1 peer-mep-id 2(config)# mep 1 cc 0 fr300s

2.3.8.10 Create port Down-MEP on Ring Link Port 0 and 1 using WebGUIUse the following step to create Down-MEP on ring link port 0 and 1.






3. Click Save.





2.3.8.11 Configure Down-MEP on Ring Link Port 1 using CLI

1. Configure Down-MEP on ring link 1 port.(config)# mep 2 down domain port level 0 interface GigabitEthernet 1/5(config)# mep 2 meg-id ICC000MEG0001 itu(config)# mep 2 mep-id 1(config)# mep 2 voe(config)# mep 2 peer-mep-id 2(config)# mep 2 cc 0 fr300s

2.3.8.12 Configure Down-MEP on Ring Link Port 1 using WebGUIUse the following step to configure down-MEP on ring link port 1.





2. To create a new MEP instance, click Add New MEP. 3. Set Domain, Mode, Direction, Port, and Level for the MEP instance.4. Click Save.


5. To add details to the MEP instance 2, click the MEP Instance and select MEP ID, MEG ID, and VOE. 6. To add Peer MEP detail, click Add New Peer MEP. Set Continuity Check configuration Enable,



2.3.8.13 Create ERPS control VLAN Down-MEP on Ring Link 0 and 1 using CLICreate ERPS control VLAN down-MEP on ring link 0 and ring link 1. For more information, see Configure VLAN Domain OAM Down-MEP using CLI, page 16.

1. Enable the control VLAN Down-MEP with enabled RAPS on ring link 0.(config)# mep 3 down domain vlan flow 333 level 0 interface GigabitEthernet 1/4(config)# mep 3 aps 0 raps2. Enable the control VLAN Down-MEP with enabled RAPS on ring link 1(config)# mep 4 down domain vlan flow 333 level 0 interface GigabitEthernet 1/5(config)# mep 4 aps 0 raps



In this implementation, the ring link0 and link1 are ports. The ERPS ICLI command parameter for this is port0 and port1.

Create a major ring protection instance as RPL owner, protecting VLAN 111 and EVC 1. Ring link port0 is Port 1/4 and ring link port1 is Port 1/5.

2.3.8.14 Create ERPS control VLAN Down-MEP on Ring Link 0 and 1 using WebGUI1. Click Configuration > MEP.


2. To create a new MEP instance, click Add New MEP. Set Domain, Mode, Direction, Port, and Level for the MEP instance.

3. Click Save.


4. To add MEP detail to MEP instance 4, click the MEP instance. Set APS Protocol details, Continuity Check configuration Enable, Priority, and Frame Rate.

5. Click Save.


2.3.9 Ring Protection with MEP Relation Configuration Example

2.3.9.1 Configure Ring Protected VLANS using CLI1. Create the ERPS instance.(config)# erps 1 major port0 interface GigabitEthernet 1/4



port1 interface GigabitEthernet 1/52. Configure the Port-0 and Port-1 SF/APS MEP relations.(config)# erps 1 mep port0 sf 1 aps 3 port1 sf 2 aps 43. Configure the RPL port.(config)# erps 1 rpl owner port04. Configure the protected VLAN’s.(config)# erps 1 vlan 111,2225. Run the following commands to verify the configuration.(config)# do show running-config[...]erps 1 major port0 interface GigabitEthernet 1/4 port1 interface GigabitEthernet 1/5erps 1 mep port0 sf 1 aps 3 port1 sf 2 aps 4erps 1 rpl owner port0erps 1 vlan 111,222[...](config)# do show erps detailGrp# Port 0 Port 1 RPL:Role Port Blocking 1 Gi 1/4 Gi 1/5 Owner Port 0 Blocked Protected VLANS: 222 111 Protection Group State :Active Port 0 SF MEP :1 Port 1 SF MEP :2 Port 0 APS MEP :3 Port 1 APS MEP :4 WTR Timeout :1 WTB Timeout :5500 Hold-Off Timeout :0 Guard Timeout :500 Node Type :Major Reversion :Revertive Version :2 ERPSv2 Administrative Command :None FSM State :PROTECTED Port 0 Link Status :Link Down Port 1 Link Status :Link Down Port 0 Block Status :BLOCKED Port 1 Block Status :BLOCKED R-APS Transmission :SF BPR 0 R-APS Port 0 Reception :NONE R-APS Port 1 Reception :NONE FOP Alarm :OFFEPS Configuration is:

2.3.9.2 Configure Ring Protected VLANS using WebGUIUse the following steps to configure the ring protected VLANS.

1. Click Configuration > ERPS.2. To create an RPRS instance, click Add New Protection Group. 3. Set Port 0, Port 1, APS MEP, SF MEP details to the following configuration.

Figure 92 • ERPS Instance List

4. Click the ERPS instance (1 in this example). Update the RPL Owner as Port 0.



Figure 93 • ERPS Configuration

5. To add VLANs, click VLAN Config. Add VLANs 111 and 222 to the VLAN list.

Figure 94 • ERPS VLAN List

2.3.9.3 Create Protected VLAN Up-MEP on VLAN Aggregation Port using CLICreate protected VLAN up-MEP on the VLAN aggregation port. For more information, see Configure VLAN Domain OAM Up-MEP using CLI, page 18.

1. Enable the VLAN Up-MEP instance.(config)# mep 5 up domain vlan flow 111 level 3 interface GigabitEthernet 1/1(config)# mep 5 meg-id ICC000MEG0001 itu(config)# mep 5 mep-id 1(config)# mep 5 voe(config)# mep 5 peer-mep-id 2(config)# mep 5 cc 7 fr300s

2.3.9.4 Create Protected VLAN Up-MEP on VLAN Aggregation Port using WebGUIUse the following steps to create protected VLAN up-MEP on the VLAN aggregation port.



2. To create an MEP instance, click Add New MEP. 3. Set Domain, Mode, Direction, Port, and Level details to the following configuration.




4. To add MEP details for instance 5, click the MEP instance (5 in this example). Set VOE, Continuity Check configuration Enable, Priority, Frame Rate, and set Peer MEP details.

5. Click Save to update the MEP instance.


2.3.9.5 Create Protected EVC Up-MEP on VLAN Aggregation Port using CLI

Create protected EVC up-MEP on the UNI port. For more information, see EVC Domain OAM Up-MEP Configuration using CLI, page 26.

1. Enable the EVC Up-MEP instance(config)# mep 6 up domain evc flow 1 level 7 interface GigabitEthernet 1/3(config)# mep 6 meg-id ICC000MEG0001 ieee name DOMAIN000(config)# mep 6 mep-id 1(config)# mep 6 voe(config)# mep 6 peer-mep-id 2(config)# mep 6 cc 4 fr1s

2.3.9.6 Create Protected EVC Up-MEP on VLAN Aggregation Port using WebGUIUse the following steps to create protected VLAN up-MEP on the VLAN aggregation port.


Figure 98 • MEP instance List

2. To create an MEP instance, click Add New MEP. 3. Set Domain, Mode, Direction, Port and Level details to the following configuration.




4. To add MEP details for MEP instance 6, click the MEP instance (6 in this example). Select VOE, Continuity Check configuration Enable, Priority, Frame Rate, and set Peer MEP details.

5. Click Save.


2.3.10 Ring Interconnection Protection ConfigurationA ring interconnected protection is a VLAN protection according to G.8032.

2.3.10.1 Configure Ring Protected VLAN Instance using CLIThe following configuration example builds on the configuration in Ring Protection, page 7 except that the major ring instance must be created slightly different. it also shows how MEP is used for interconnected ring protection. For more information, see Ring Interconnection Protection, page 10.

Create a major ring protection instance as interconnected and protecting sub-ring control VLAN.

1. Create the ERPS instance.(config)# erps 1 major port0 interface GigabitEthernet 1/4 port1 interface GigabitEthernet 1/5 interconnect2. Configure the Port-0 and Port-1 SF/APS MEP relations.(config)# erps 1 mep port0 sf 1 aps 3 port1 sf 2 aps 43. Configure the RPL port.(config)# erps 1 rpl owner port04. Configure the protected VLAN’s including sub-ring control VLAN 444.(config)# erps 1 vlan 111,222,444

2.3.10.2 Configure Ring Protected VLAN Instance using WebGUIUse the following steps to configure a major ring protection instance as interconnected and protecting sub-ring control VLAN.



1. Click Configuration >ERPS.2. To create an ERPS instance, click Add New Protection Group.3. Select Port 0, Port 1, APS MEP, SF MEP details to the following configuration. Also select

Interconnected Node for this ERPS instance.

Figure 101 • Ethernet Ring Protection Switching

4. Click the ERPS instance (1 in this example). Update the RPL Owner to Port 0.

Figure 102 • ERPS Configuration

5. To add VLANs, click VLAN Config. Add VLANs such as 111, 222, and 444 to the VLAN list.

Figure 103 • ERPS VLAN List

2.3.10.3 Create Port Down-MEP on Sub-ring Link Port using CLICreate a port down-MEP on sub-ring link port. For more information, see Configure Port Domain OAM Down-MEP using CLI, page 14.

1. Configure Down-MEP on sub-ring link port.(config)# mep 7 down domain port level 0 interface GigabitEthernet 1/2(config)# mep 7 meg-id ICC000MEG0001 itu(config)# mep 7 mep-id 1(config)# mep 7 voe(config)# mep 7 peer-mep-id 2(config)# mep 7 cc 0 fr300s

2.3.10.4 Create Port Down-MEP on Sub-ring Link Port using WebGUIUse the following steps to create port down-MEP on sub-ring link port.



2. To create an MEP instance, click Add New MEP.



3. Set Domain, Mode, Direction, Port and Level details to the following configuration.


4. Click Save.5. To add MEP details for MEP instance 7, click the MEP instance (7 in this example). Select VOE,

Continuity Check configuration Enable, Priority, Frame Rate.


6. Click Save.

2.3.10.5 Create Sub-ring Control VLAN using CLICreate a sub-ring control VLAN based on the configuration in Ring Protection, page 7.

1. Create VLAN 444.(config)# vlan 4442. Configure the VLAN sub-ring link port.(config)# interface GigabitEthernet 1/2(config-if)# switchport hybrid allowed vlan 444(config-if)# switchport hybrid port-type s-port(config-if)# switchport mode hybrid(config-if)# exit3. Configure the VLAN ring ports.(config)# interface GigabitEthernet 1/4,5(config-if)# switchport hybrid allowed vlan 111,333,444(config-if)# switchport hybrid port-type s-port(config-if)# switchport mode hybrid(config-if)# exit



2.3.10.6 Create Sub-ring Control VLAN using WebGUIUse the following steps to create a sub-ring control VLAN based on the configuration in Ring Protection, page 7

1. Click Configuration >VLANs >Configuration.2. Set the Mode, Port VLAN, Port type, and Allowed VLANs for port 2,4 and 5 to the following

configuration.

Figure 107 • Global VLAN List

2.3.10.7 Create Sub-ring Control VLAN Down-MEP and Up-MEP using CLICreate a sub-ring control VLAN down-MEP and up-MEP (virtual channel) on sub-ring link port.

1. Enable the VLAN Down-MEP instance on sub-ring link port.(config)# mep 8 down domain vlan flow 444 level 0 interface GigabitEthernet 1/2(config)# mep 8 aps 0 raps

2.3.10.8 Create Sub-ring Control VLAN Down-MEP and Up-MEP using WebGUIUse the following steps to create a sub-ring control VLAN down-MEP and up-MEP (virtual channel) on sub-ring link port.



2. To create an MEP instance, click Add New MEP. 3. Set Domain, Mode, Direction, Port and Level details to the following configuration.


4. Click Save.5. To add MEP details for MEP instance 8, click the MEP instance (8 in this example). Select APS

details.6. Click Save.




2.3.10.9 Enable VLAN Up-MEP Instance on Sub-Ring Virtual Channel using CLI1. Enable the VLAN Up-MEP instance on sub-ring virtual channel.(config)# mep 9 up domain vlan flow 444 level 0 interface GigabitEthernet 1/2(config)# mep 9 aps 0 raps

2.3.10.10 Enable VLAN Up-MEP Instance on Sub-Ring Virtual Channel using WebGUIUse the following steps to Enable the VLAN Up-MEP instance on sub-ring virtual channel.



2. To create an MEP instance, click Add New MEP.3. Set Domain, Mode, Direction, Port and Level details to the following configuration.


4. Click Save.5. To add MEP details for MEP instance 9, click the MEP instance (9 in this example). Select APS

details.6. Click Save.




2.3.10.11 Configure Ring Interconnected Protection with MEP Relation using CLI1. Create the ERPS sub-ring instance.(config)# erps 2 sub port0 interface GigabitEthernet 1/2 interconnect 1 virtual-channel2. Configure the Port-0 and virtual Port-1 SF/APS MEP relations.(config)# erps 2 mep port0 sf 7 aps 8 port1 aps 93. Run the following commands to verify the configuration.(config)# do show running-config[...]erps 1 major port0 interface GigabitEthernet 1/4 port1 interface GigabitEthernet 1/5 interconnecterps 1 mep port0 sf 1 aps 3 port1 sf 2 aps 4erps 1 rpl owner port0erps 1 vlan 111,222,444erps 2 sub port0 interface GigabitEthernet 1/2 interconnect 1 virtual-channelerps 2 mep port0 sf 7 aps 8 port1 aps 9[...](config)# do show erps detailGrp# Port 0 Port 1 RPL:Role Port Blocking 1 Gi 1/4 Gi 1/5 Owner Port 0 Blocked Protected VLANS: 111 222 Protection Group State :Active Port 0 SF MEP :1 Port 1 SF MEP :2 Port 0 APS MEP :3 Port 1 APS MEP :4 WTR Timeout :1 WTB Timeout :5500 Hold-Off Timeout :0 Guard Timeout :500 Node Type :Major-Interconnected Reversion :Revertive Version :2 ERPSv2 Administrative Command :None FSM State :PROTECTED



Port 0 Link Status :Link Down Port 1 Link Status :Link Down Port 0 Block Status :BLOCKED Port 1 Block Status :BLOCKED R-APS Transmission :SF BPR 0 R-APS Port 0 Reception :NONE R-APS Port 1 Reception :NONE FOP Alarm :OFFGrp# Port 0 Port 1 RPL:Role Port Blocking 2 Gi 1/2 - - - - Protected VLANS: None Protection Group State :Active Port 0 SF MEP :7 Port 1 SF MEP :0 Port 0 APS MEP :8 Port 1 APS MEP :9 WTR Timeout :1 WTB Timeout :5500 Hold-Off Timeout :0 Guard Timeout :500 Node Type :Sub-Interconnected Major Ring ID :1 Topology change propagation :Disabled Virtual Channel :Yes Reversion :Revertive Version :2 ERPSv2 Administrative Command :None FSM State :PROTECTED Port 0 Link Status :Link Down Port 1 Link Status :Link Down Port 0 Block Status :BLOCKED Port 1 Block Status :BLOCKED R-APS Transmission :SF DNF BPR 0 R-APS Port 0 Reception :NONE R-APS Port 1 Reception :NONE FOP Alarm :OFF

2.3.10.12 Configure Ring Interconnected Protection with MEP Relation using WebGUIUse the following steps to configure Ring Interconnected Protection with MEP Relation.

1. Click Configuration >ERPS.2. To create an ERPS instance, click Add New Protection Group.3. Set the Port 0, Port 1, APS MEP, SF MEP details to the following configuration. Also set

Interconnected Node option for this ERPS instance.

Figure 114 • Add New Protection Group

Documents

ENT-AN1105 Application Note Service OAM Configurationww1.microchip.com/downloads/en/Appnotes/VPPD-03588_ENT-AN1105.pdf · Service OAM Configuration ENT-AN1105 Application Note Revision