Technical Specification MEF 36. Service OAM SNMP MIB for Performance Monitoring. January 2012

Technical Specification Service OAM SNMP MIB for Performance Monitoring January 2012 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of

Disclaimer The information in this publication is freely available for reproduction and use by any recipient and is believed to be accurate as of its publication date. Such information is subject to change without notice and the Metro Ethernet Forum (MEF) is not responsible for any errors. The MEF does not assume responsibility to update or correct any information in this publication. No representation or warranty, expressed or implied, is made by the MEF concerning the completeness, accuracy, or applicability of any information contained herein and no liability of any kind shall be assumed by the MEF as a result of reliance upon such information. The information contained herein is intended to be used without modification by the recipient or user of this document. The MEF is not responsible or liable for any modifications to this document made by any other party. The receipt or any use of this document or its contents does not in any way create, by implication or otherwise: any express or implied license or right to or under any patent, copyright, trademark or trade secret rights held or claimed by any MEF member company which are or may be associated with the ideas, techniques, concepts or expressions contained herein; nor any warranty or representation that any MEF member companies will announce any product(s) and/or service(s) related thereto, or if such announcements are made, that such announced product(s) and/or service(s) embody any or all of the ideas, technologies, or concepts contained herein; nor any form of relationship between any MEF member companies and the recipient or user of this document. Implementation or use of specific Metro Ethernet standards or recommendations and MEF specifications will be voluntary, and no company shall be obliged to implement them by virtue of participation in the Metro Ethernet Forum. The MEF is a non-profit international organization accelerating industry cooperation on Metro Ethernet technology. The MEF does not, expressly or otherwise, endorse or promote any specific products or services. The Metro Ethernet Forum 2012. All Rights Reserved. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of

Table of Contents 1. Abstract... 1 2. Terminology... 1 3. Scope... 4 4. Compliance Levels... 5 5. Introduction... 5 5.1 The Basic Need... 5 5.2 The General Structure... 5 5.3 The Foundational Elements... 6 5.4 Overview of the Performance Monitoring Process... 7 6. SOAM PM MIB Overview... 10 6.1 PM MIB Per MEP Objects... 10 6.2 PM MIB Loss Measurement (LM) Objects... 10 6.2.1 LM Configuration Table... 10 6.2.2 LM Measured Statistic Table... 12 6.2.3 LM Current Availability Statistic Table... 12 6.2.4 LM Current Statistic Table... 13 6.2.5 LM Availability History Statistic Table... 14 6.2.6 LM History Statistic Table... 15 6.3 PM MIB Delay Measurement (DM) Objects... 15 6.3.1 DM Configuration Table... 15 6.3.2 DM Configuration Bin Table... 17 6.3.3 DM Measured Statistic Table... 17 6.3.4 DM Current Statistic Table... 18 6.3.5 DM Current Statistic Bins Table... 19 6.3.6 DM History Statistic Table... 19 6.3.7 DM History Bin Statistic Table... 20 6.4 PM MIB Threshold Configuration Objects... 20 6.4.1 Threshold Above... 20 6.4.2 Threshold Set/Clear... 21 6.4.3 LM Thresholds... 21 6.4.4 DM Thresholds... 22 6.5 PM MIB Notifications... 23 6.6 PM MIB Conformance and Compliance... 24 7. SOAM PM MIB Requirements... 25 8. SOAM PM MIB Definitions... 30 9. References... 150 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page i

List of Figures Figure 1 Generalized OSS/BSS-NMS-EMS-NE Model... 6 Figure 2 Relationship between 802.1 CFM MIBs, UML Models, and SOAM MIBs... 7 Figure 3 - Relationship Between Different Timing Parameters... 8 Figure 4 - Relationship Between Measurement Interval and Repetion Time... 9 List of Tables Table 1 Terminology... 4 Table 2 Delay Measurement Bin Boundaries... 17 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page ii

1 2 3 4 5 6 7 8 9 1. Abstract This document specifies the Performance Monitoring (PM) Management Information Base (MIB) necessary to manage Service Operations, Administration, and Maintenance (OAM) implementations that satisfy the Service OAM requirements and framework specified by MEF 17 [10], the Service OAM Performance Monitoring requirements as specified by SOAM-PM [13], and the Service OAM management objects as specified by MEF 7.1 [6] which are applicable to Performance Monitoring functions. Two non-mef documents serve as the baseline documents for this work: ITU-T Y.1731 [20] and IEEE 802.1ag [23]. 2. Terminology Term Definition Source Availability A measure of the percentage of time within a specified MEF 10.2.1 [7] Performance time interval during which the frame loss is small Backward OAM information sent from the Responder MEP to the SOAM-PM [13] Controller MEP. For LM it indicates the frame counts/loss from the Responder MEP to the Controller MEP. For DM is indicates the delay and delay variation from the Responder MEP to the Controller MEP. BSS Business Support System CCM Continuity Check Message IEEE Std 802.1ag [23] CFM Connectivity Fault Management IEEE Std 802.1ag [23] CHLI Consecutive High Loss Interval, a sequence of small MEF 10.2.1 [7] time intervals contained in T, each with high frame loss ratio Controller The Controller MEP initiates SOAM PDUs, and receives SOAM-PM [13] MEP responses from the Responder MEP. CoS Class of Service MEF 10.2 [8] DM Delay Measurement Dual-Ended A type of process where a MEP sends measurement SOAM-PM [13] information to a peer MEP that will perform the calculations. EMS Element Management System MEF 7.1 [6] ETH-DM Ethernet Delay Measurement function ITU-T Y.1731 [20] ETH-LM Ethernet Loss Measurement function ITU-T Y.1731 [20] ETH-SLM Ethernet Synthetic Frame Loss Measurement function ITU-T Y.1731 [20] EVC Ethernet Virtual Connection MEF 10.2 [8] FD Frame Delay MEF 10.2.1 [7] FDR Frame Delay Range MEF 10.2.1 [7] FLR Frame Loss Ratio MEF 10.2.1 [7] FM Fault Management MEF 17 [10] contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 1

Term Definition Source Forward OAM information sent from the Controller MEP to the SOAM-PM [13] Responder MEP. For LM it indicates the frame counts/loss from the Controller MEP to the Responder MEP. For DM is indicates the delay and delay variation from the Controller MEP to the Responder MEP. HLI High Loss Interval, a small time interval contained in T MEF 10.2.1 [7] with a high frame loss ratio IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force IFDV Inter-Frame Delay Variation MEF 10.2.1 [7] ITU-T International Telecommunication Union - Telecommunication Standardization Bureau LAN Local Area Network MEF 4 [5] LM Loss Measurement ITU-T Y.1731 [20] MAC Media Access Control IEEE Std 802.3 [24] MA Maintenance Association (equivalent to a MEG) IEEE Std 802.1ag [23] MD Maintenance Domain (equivalent to a OAM Domain in IEEE Std 802.1ag [23] MEF 17) MD Level Maintenance Domain Level (equivalent to a MEG level) IEEE Std 802.1ag [23] ME Maintenance Entity IEEE Std 802.1ag [23] Measurement Bin A Measurement Bin is a counter that stores the number of performance measurements falling within a specified SOAM-PM [13] Measurement Interval range, during a Measurement Interval. A period of time during which measurements are taken. Measurements initiated during one Measurement Interval are kept separate from measurements taken during other Measurement Intervals. It is important to note that this is different from T. SOAM-PM [13] MEF Metro Ethernet Forum MEG Maintenance Entity Group (equivalent to a MA) ITU-T Y.1731 [20] MEG Level Maintenance Entity Group Level (equivalent to MD ITU-T Y.1731 [20] Level) MEN Metro Ethernet Network MEF 4 [5] MEP Maintenance association End Point or MEG End Point IEEE Std 802.1ag [23], ITU-T Y.1731 [20] MFD Mean Frame Delay MEF 10.2.1 [7] MIB Management Information Base RFC 2578 [2] MIP Maintenance domain Intermediate Point or MEG Intermediate Point IEEE Std 802.1ag [23], ITU-T Y.1731 [20] MP Maintenance Point. One of either a MEP or a MIP. IEEE Std 802.1ag [23] NE Network Element MEF 4 [5] NMS Network Management System MEF 7.1 [6] OAM Operations, Administration, and Maintenance MEF 17 [10] contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 2

Term Definition Source On-Demand OAM actions that are initiated via manual intervention RFC 5951 [27] for a limited time to carry out diagnostics. On-Demand OAM can result in singular or periodic OAM actions during the diagnostic time interval One-way A measurement performed in the forward or backward SOAM-PM [13] direction. For example from MEP A to MEP B or from MEP B to MEP A. OSS Operations Support System ITU-T Y.1731 [20] PDU Protocol Data Unit IEEE Std 802.1ag [23] PM Performance Monitoring SOAM-PM [13] PM Function A MEP capability specified for performance monitoring SOAM-PM [13] purposes (e.g., Single-Ended Delay, Single-Ended Synthetic Loss) PM Session A PM Session is the application of a given PM Function SOAM-PM [13] between a given pair of MEPs and using a given CoS Frame Set over some (possibly indefinite) period of time. PM Solution A PM Solution is a set of related requirements that SOAM-PM [13] when implemented allow a given set of performance metrics to be measured using a given set of PM functions. PM Tool A generic term used to discuss the application of a PM SOAM-PM [13] Function. Proactive OAM actions that are carried on continuously to permit RFC 5951 [27] timely reporting of fault and/or performance status. Resiliency The number of High Loss Intervals and Consecutive MEF 10.2.1 [7] Performance High Loss Intervals in T Responder MEP In a single-ended session, the Responder MEP receives SOAM PDUs, from the Controller MEP, and transmits a response to the Controller MEP. SOAM-PM [13] RFC Service Frame Request for Comment An Ethernet frame transmitted across the UNI toward the Service Provider or an Ethernet frame transmitted across the UNI toward the Subscriber Single-Ended A type of process where a MEP sends a measurement request and the peer MEP replies with the requested information so the originating MEP can calculate the measurement. Sink MEP In a dual-ended session, the Sink MEP receives SOAM PDUs, from the Controller MEP and performs the performance calculations. MEF 10.2 [8] SOAM-PM [13] SOAM-PM [13] SLM Synthetic Loss Measurement SOAM-PM [13] SNMP Simple Network Management Protocol RFC 1157 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 3

10 11 12 13 14 15 16 17 18 Term Definition Source SNMP Agent An SNMP entity containing one or more command responder RFC 3411 [3] and/or notification originator applications (along with their associated SNMP engine). Typically implemented in an NE. SNMP Manager An SNMP entity containing one or more command RFC 3411 [3] generator and/or notification receiver applications (along with their associated SNMP engine). Typically implemented in an EMS or NMS. SOAM Service OAM MEF 17 [10] SOAM PDU Service OAM frame, or Protocol Data Unit. Specifically, those PDUs defined in [IEEE 802.1ag], [ITU-T Y.1731], or MEF specifications. SOAM-FM [12] Synthetic Traffic T SOAM traffic that emulates service traffic in order to measure the performance experience. Delay measurements must use synthetic traffic, because user traffic does not contain standardized timestamp fields. Other measurements, such as Frame Loss, may also use synthetic frames for certain advantages (e.g., ability to measure loss in multipoint services). Time Interval for SLS Metrics. The time over which a Performance Metric is defined. T is at least as large as the Measurement Interval, and generally consists of multiple Measurement Intervals. SOAM-PM [13] MEF 10.2.1 [7] TC Textual Conventions RFC 4181 [4] TLV Type Length Value, a method of encoding Objects Two-way A measurement of the performance of frames that flow from the Controller MEP to the Responder MEP and back again. SOAM-PM [13] UML Unified Modeling Language Object Management Group (OMG) UTC Coordinated Universal Time SOAM-PM [13] UNI User-to-Network Interface MEF 4 [5] VLAN Virtual LAN IEEE Std 802.1Q [21] 3. Scope Table 1 Terminology The scope of this document is to provide the SNMP PM MIB that supports the Service OAM (SOAM) Performance Monitoring functions that have been defined in MEF 17 [10], the Service OAM Requirements & Framework Phase 1, SOAM-PM [13], the Service OAM Performance Monitoring Phase 1 Implementation Agreement, and MEF 7.1 [6], the EMS-NMS Information Model. This document includes the MIB necessary to support the MEF SOAM PM functionality: the MEF-SOAM-PM-MIB that includes the SOAM PM MIB objects necessary to implement the contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 4

19 20 21 22 23 24 25 26 27 28 29 30 SOAM PM Implementation Agreement [13] and the SOAM PM concepts as presented in ITU-T Y.1731 [20]. The primary purpose of this document is to provide a mechanism to enhance interoperability between equipment/software vendors and between Service Providers and/or Operators. This document provides the Metro Ethernet Forum (MEF) SOAM PM functionality within the Metro Ethernet Networks (MEN) via SNMP MIBs. 4. Compliance Levels The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in RFC 2119 [1]. All key words must be in upper case, bold text. 5. Introduction 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 5.1 The Basic Need One of the aspects of defining Metro Ethernet Networks (MEN) is the need to ensure the compatibility between equipment/software vendors and equipment operators in order to facilitate interoperability in local, metro, national, and international networks. One of the common ways to do this is through a common management interface using publically available or enterprise specific SNMP MIBs. A MIB is a collection of managed objects that can be used to provision an entity, query an entity for status information, or define notifications that are sent to a Network Management System (NMS) or an Element Management System (EMS). Collections of related objects are defined in MIB modules which are written using an adapted subset of OSI's Abstract Syntax One, or ASN.1 [26]. Standards for MIB modules are set by IETF and documented in various RFCs, primary of which are RFC 2578 Structure of Management Information Version 2 (SMIv2) and RFC 4181 Guidelines for Authors and Reviewers of MIB Documents. 5.2 The General Structure A generalized system model is shown by Figure 1 that illustrates the relationship between the OSS/BSS, NMS, EMS, and Network Elements (NE). The primary focus of this specification defines the interaction between the EMS and the NE via SNMP using the MIB module defined in this specification. Object names in the figure are for example only. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 5

49 50 Figure 1 Generalized OSS/BSS-NMS-EMS-NE Model 51 52 53 54 55 56 57 58 59 60 61 62 63 5.3 The Foundational Elements MEF 10.2 [8] and MEF 10.2.1 [7] describe the Ethernet Service Attributes at the UNI reference point including the performance attributes of Frame Delay (FD), Mean Frame Delay (MFD), Frame Delay Range (FDR), Inter-Frame Delay Variation (IFDV), Frame Loss Ratio (FLR), Availability Performance, and Resiliency Performance. MEF 17 [10] provides the Service OAM requirements and framework. It defines the OAM components and Service OAM requirements. SOAM-FM [12] further defines the aspects of Service OAM requirements that deal with Fault Management (FM) and their extensions as needed to support MEF SOAM FM requirements. SOAM-FM builds upon two existing documents: Connectivity Fault Management as defined in IEEE 802.1ag [23] and extended in ITU-T Y.1731 [20]. Service OAM Fault Management objects that provide the baseline for MIB objects defined in this specification are found in MEF 7.1 [6]. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 6

64 65 66 67 68 69 70 71 72 73 74 75 SOAM-PM [13] further defines the aspects of Service OAM requirements that focus on Performance Monitoring (PM) and their extensions as needed to support MEF SOAM PM requirements. SOAM-PM builds upon two existing documents the ITU-T Y.1731 and ITU-T G.8021/Y.1341 [17]. MEF 7.1 draws heavily upon the models defined in ITU-T Q.840 [19]. The MEF-SOAM-TC MIB [15] defines the necessary global MEF SOAM Textual Conventions used in this MIB. The relationship between the various documents and the PM MIB presented in this specification is illustrated by Figure 2. The UML models found in MEF 7.1 and G.8052 provide a baseline for the SOAM MIBs. A number of the tables/objects in the MIB extend the IEEE CFM MIB objects as well as providing new objects from ITU-T Y.1731 and the SOAM PM IA documents. SOAM PM MIB 76 77 Figure 2 Relationship between 802.1 CFM MIBs, UML Models, and SOAM MIBs 78 79 80 81 82 83 84 5.4 Overview of the Performance Monitoring Process The Performance Monitoring process is made up of a number of Performance Monitoring instances, known as PM Sessions. A PM Session can be initiated between two MEPs in a MEG and be defined as either a Loss Measurement (LM) session or Delay Measurement (DM) session. The LM session can be used to determine the performance metrics FLR, Availability, and Resiliency. The DM session can be used to determine the performance metrics FD, IFDV, FDR, and MFD. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 7

85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 The PM Session is defined by the specific PM function (PM tool) being run, Start Time, Stop Time, Message Period, Measurement Interval, and Repetition Time. The relationship of these different items are depicted in Figure 3 and Figure 4 (Refer to section 9.1 in SOAM PM [13]). The Start Time is the time that the PM session begins and is applicable to On-Demand PM sessions. For Proactive PM sessions the start time is not applicable as the PM session begins as soon as the PM session is configured and enabled. The Stop Time is the time that the measurement ends and is applicable to On-Demand PM sessions. For Proactive PM sessions the stop time is not applicable as the PM session stops only when the PM session is disabled or deleted. The Message Period is the SOAM PDU transmission frequency (the time between SOAM PDU transmissions). The Measurement Interval is the time period over which measurements are gathered and then summarized. The Measurement Interval can align with the PM Session duration, but it doesn't need to. SOAM PDUs during a PM Session are only transmitted during a Measurement Interval. The Repetition Time is the time between the start times of the Measurement Intervals. 101 102 Figure 3 - Relationship Between Different Timing Parameters contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 8

103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 Figure 4 - Relationship Between Measurement Interval and Repetion Time To execute performance measurements, a PM Session is created through the use of the configuration items in either the LM or DM tables. The PM Session can be configured to run forever (Proactive/On-Demand) or for a period of time (On-Demand). On-Demand types have a definitive start and stop time that can be relative or absolute or can have a stop time of forever. Proactive types begin immediately when a PM Session is configured and enabled and end when the PM Session is deleted or disabled. When a PM Session is completed, either through the session being disabled or the Stop Time being reached, the current Measurement Interval is stopped, if it in process at the time, and all the in process calculations are finalized. A PM Session can be dual-ended or single-ended. In a single-ended session a Controller MEP sends SOAM PDUs towards a Responder MEP. The Responder MEP sends SOAM PDUs towards the Controller MEP in response to receiving SOAM PDUs from the Controller MEP. Results from the Controller MEP to the Responder MEP are known as forward results and results from the Responder MEP to the Controller MEP are backward results. All performance calculations are performed by the Controller MEP, and results are only available on the Controller MEP. In a dual-ended session a Controller MEP sends SOAM PDUs towards a Sink MEP. There are no responses sent towards the Controller MEP. Results from the Controller MEP to Sink MEP are known as forward results. All performance calculations are performed by the Sink MEP, and results are only available on the Sink MEP. PM Sessions of type LMM/LMR, SLM/SLR, or DMM/DMR are single-ended types. PM Sessions of type 1DM and CCM are dual-ended types. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 9

127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 Controller MEPs send SOAM PDUs of type LMM, SLM, DMM, CCM, or 1DM and receive SOAM PDUs of type LMR, SLR, and DMR. Responder MEPs send SOAM PDUs of type LMR, SLR, or DMR and receive SOAM PDUs of type LMM, SLM, or DMM. Sink MEPs receive SOAM PDUs of type CCM or 1DM. 6. SOAM PM MIB Overview The SOAM PM MIB is divided into a number of different object groupings: the PM MIB MEP Objects, PM MIB Loss Measurement Objects, PM MIB Delay Measurement Objects, and SOAM PM notifications. This document treats the terms 'average' and 'arithmetic mean' as synonymous terms and consistently uses 'average' in object names and definitions. 6.1 PM MIB Per MEP Objects The PM MIB Per MEP Objects are defined in the mefsoampmmeptable. The mefsoampmmeptable augments the dot1agcfmmepentry found in the CFM MIB. It includes objects that are locally defined for an individual MEP that are used throughout the specific PM Sessions associated with the particular MEP. mefsoampmmepopernextindex - indicates the next available index for row creation in the LM and DM configuration tables of a PM session on a MEP mefsoampmmeplmsingleendedresponder - indicates whether single-ended Loss Measurements (LMM) Responders are enabled on a MEP mefsoampmmepslmsingleendedresponder - indicates whether single-ended Synthetic Loss Measurements (SLM) Responders are enabled on a MEP mefsoampmmepdmsingleendedresponder - indicates whether single-ended Delay Measurements (DMM) Responders are enabled on a MEP 6.2 PM MIB Loss Measurement (LM) Objects The Loss Measurement Objects are defined in six separate tables: mefsoamlmcfgtable, meflmmeasuredstatstable, mefsoamlmcurrentavailstatstable, mefsoamlmcurrentstatstable, mefsoamlmhistoryavailstatstable, and mefsoamlmhistorystatstable. 6.2.1 LM Configuration Table The mefsoamlmcfgtable includes configuration objects for the Loss Measurement PM session. It uses the same indexes that a MEP configuration does: dot1agcfmmdindex, dot1agcfmmaindex, and dot1agcfmmepidentifier, as well as mefsoamlmcfgindex, the specific LM session number on a MEP. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 10

162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 A Loss Measurement session is created on an existing MEP by first accessing the mefsoampmmepopernextindex object and using this value as the mefsoamlmcfgindex during row creation. A single Loss Measurement session can be used to measure Frame Loss, Frame Loss Ratio, and Availability between a given pair of MEPs, for a given CoS Frame Set. Configuration/status options are organized into eight general categories. LM Session type, version, session enable, and counter enables: o mefsoamlmcfgtype o mefsoamcfgversion o mefsoamlmcfgenabled o mefsoamlmcfgmeasurementenable o mefsoamlmcfgsessiontype LM Session PDU transmission frequency and Measurement Interval size: o mefsoamlmcfgmessageperiod o mefsoamlmcfgmeasurementinterval o mefsoamlmcfgnumintervalsstored LM Session PDU composition and length: o mefsoamlmcfgpriority o mefsoamlmcfgframesize o mefsoamlmcfgdatapattern o mefsoamlmcfgtesttlvincluded o mefsoamlmcfgtesttlvpattern LM Session peer partner selection: o mefsoamlmcfgdestmacaddress o mefsoamlmcfgdestmepid o mefsoamlmcfgdestismepid LM Session start, stop, and repetition selection: o mefsoamlmcfgalignmeasurementintervals o mefsoamlmcfgalignmeasurementoffset o mefsoamlmcfgstarttimetype o mefsoamlmcfgfixedstartdateandtime o mefsoamlmcfgrelativestarttime o mefsoamlmcfgstoptimetype contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 11

195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 o mefsoamlmcfgfixedstopdateandtime o mefsoamlmcfgrelativestoptime o mefsoamlmcfgrepetitiontime LM Session availability configuration: o mefsoamlmcfgavailabilitymeasurementinterval o mefsoamlmcfgavailabilitynumconsecutivemeaspdus o mefsoamlmcfgavailabilityflrthreshold o mefsoamlmcfgavailabilitynumconsecutiveintervals o mefsoamlmcfgavailabilitynumconsecutivehighflr LM Session parameters for status: o mefsoamlmcfgsessionstatus LM Session history statistic table clear: o mefsoamlmcfghistoryclear Alignment with MEF 10.2.1 is supported via the LM Session Availability configuration parameters where: mefsoamlmcfgavailabilitynumconsecutiveintervals is equivalent to MEF 10.2.1 parameter n. mefsoamlmcfgavailabilityflrthreshold is equivalent to MEF 10.2.1 parameter C. mefsoamlmcfgavailabilitynumconsecutivehighflr is equivalent to p. mefsoamlmcfgavailabilitynumconsecutivemeaspdus times mefsoamlmcfgmessageperiod for SLM/LMM/CCM is equivalent to MEF 10.2.1 parameter t. 6.2.2 LM Measured Statistic Table The LM Measured Statistic Table, mefsoamlmmeasuredstatstable, is created automatically when a LM session is created and contains the Loss Measurement statistic information from the last received SOAM PDU. It uses the same indexes as the mefsoamlmcfgtable table. It includes the forward and backward FLR stats, mefsoamlmmeasuredstatsforwardflr and mefsoamlmmeasuredstatsbackwardflr, availability indicators mefsoamlmmeasuredstatsavailforwardstatus and mefsoamlmmeasuredstatsavailbackwardstatus, and last availability transition times, mefsoamlmmeasuredstatsavailforwardlasttransitiontime and mefsoamlmmeasuredstatsavailbackwardlasttransitiontime. 6.2.3 LM Current Availability Statistic Table The LM Current Availability Statistic Table, mefsoamlmcurrentavailstatstable, is created automatically when a LM session is created and contains the Availability statistics for the current contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 12

230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 availability Measurement Interval. It uses the same indexes as the mefsoamlmcfgtable table, but the Measurement Interval (mefsoamlmcfgavailabilitymeasurementinterval) is independent of the interval used for the mefsoamlmcurrentstatstable (mefsoamlmcfgmeasurementinterval). At the beginning of each availability Measurement Interval the values in the Current Availability Statistic Table are copied to a new row in the mefsoamlmhistoryavailstatstable and the Current Availability Statistic Table counter and status values are reset to zero and the start time is updated to the new Measurement Interval start time. The LM Current Availability Statistic Table objects are organized into four categories. LM Availability interval start time and elapsed time: o mefsoamlmcurrentavailstatsstarttime o mefsoamlmcurrentavailstatselapsedtime LM Availability interval suspect status: o mefsoamlmcurrentavailstatssuspect LM Availability high loss, and consecutive high loss: o mefsoamlmcurrentavailstatsforwardhighloss o mefsoamlmcurrentavailstatsbackwardhighloss o mefsoamlmcurrentavailstatsforwardconsecutivehighloss o mefsoamlmcurrentavailstatsbackwardconsecutivehighloss LM Availability available and unavailable indicator counters o mefsoamlmcurrentavailstatsforwardavailable o mefsoamlmcurrentavailstatsbackwardavailable o mefsoamlmcurrentavailstatsforwardunavailable o mefsoamlmcurrentavailstatsbackwardunavailable LM Availability flr counters o mefsoamlmcurrentavailforwardminflr o mefsoamlmcurrentavailforwardmaxflr o mefsoamlmcurrentavailforwardavgfl o mefsoamlmcurrentavailbackwardminflr o mefsoamlmcurrentavailbackwardmaxflr o mefsoamlmcurrentavailbackwardavgflr 6.2.4 LM Current Statistic Table The LM Current Statistic Table, mefsoamlmcurrentstatstable, is created automatically when a LM session is created and contains the currently enabled statistic counters and statuses for the contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 13

264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 current Measurement Interval. It uses the same indexes as the mefsoamlmcfgtable table, but the Measurement Interval (mefsoamlmcfgmeasurementinterval) is independent of the interval used for the mefsoamlmcurrentavailstatstable (mefsoamlmcfgavailabilitymeasurementinterval). At the beginning of each Measurement Interval the values in the Current Statistic Table are copied to a new row in the mefsoamlmhistorystatstable and the Current Statistic Table counter and status values are reset to zero and the start time is updated to the Measurement Interval start time. The LM Current Statistic Table objects are organized into five categories. LM interval start time and elapsed time: o mefsoamlmcurrentstatsstarttime o mefsoamlmcurrentstatselapsedtime LM interval suspect status: o mefsoamlmcurrentstatssuspect LM forward transmitted/received frames, minimum, maximum and average (arithmetic mean) frame loss ratio, available and unavailable counters: o mefsoamlmcurrentstatsforwardtransmittedframes o mefsoamlmcurrentstatsforwardreceivedframes o mefsoamlmcurrentstatsforwardminflr o mefsoamlmcurrentstatsforwardmaxflr o mefsoamlmcurrentstatsforwardavgflr LM backward transmitted/received frames, minimum, maximum and average (arithmetic mean) frame loss ratio, available and unavailable counters o mefsoamlmcurrentstatsbackwardtransmittedframes o mefsoamlmcurrentstatsbackwardreceivedframes o mefsoamlmcurrentstatsbackwardminflr o mefsoamlmcurrentstatsbackwardmaxflr o mefsoamlmcurrentstatsbackwardavgflr LM initiated and received measurement counts: o mefsoamlmcurrentstatssoampdussent o mefsoamlmcurrentstatssoampdusreceived 6.2.5 LM Availability History Statistic Table The LM Availability History Statistic Table, mefsoamlmhistoryavailstatstable, is created automatically when the first availability Measurement Interval completes in a LM session. A new row is created as each availability Measurement Interval is completed with the information from contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 14

299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 the completed mefsoamlmcurrentavailstatstable entry. The duration of each availability Measurement Interval is determined by mefsoamlmcfgavailabilitymeasurementinterval and is independent of the Measurement Interval used for the mefsoamlmhistorystatstable. The oldest row can be deleted after a period of time, but is mandatory to be persistent for 32 completed Measurement Intervals and recommended to be persistent for 96 completed Measurement Intervals. The LM Availability History Statistic Table uses the same indexes as the mefsoamlmcfgtable table as well as the one additional index, the mefsoamlmhistoryavailstatsindex number. The LM History Statistic Table contains the same four categories as the mefsoamlmcurrentavailstatstable table, except the first category is interval end time and elapsed time. The objects are the same except they are listed as History instead of Current. 6.2.6 LM History Statistic Table The LM History Statistic Table, mefsoamlmhistorystatstable, is created automatically when the first Measurement Interval completes in a LM session. A new row is created as each Measurement Interval is completed with the information from the completed mefsoamlmcurrentstatstable entry. The duration of each Measurement Interval is determined by mefsoamlmcfgmeasurementinterval and is independent of the availability Measurement Interval used for the mefsoamlmhistoryavailstatstable. The oldest row can be deleted after a period of time, but is mandatory to be persistent for 32 completed Measurement Intervals and recommended to be persistent for 96 completed Measurement Intervals. The LM History Statistic Table uses the same indexes as the mefsoamlmcfgtable table as well as the one additional index, the mefsoamlmhistorystatsindex number. The LM History Statistic Table contains the same five categories as the mefsoamlmcurrentstatstable table, except the first category is interval end time and elapsed time. The objects are the same except they are listed as History instead of Current. 6.3 PM MIB Delay Measurement (DM) Objects The Delay Measurement Objects are defined in three pairs of tables: mefsoamdmcfgtable and mefsoamdmcfgmeasbintable, mefsoamdmcurrentstatstable and mefsoamdmcurrentstatsbinstable, and mefsoamdmhistorystatstable and mefsoamdmhistorystatsbinstable, and the mefdmmeasuredstatstable. 6.3.1 DM Configuration Table The mefsoamdmcfgtable includes configuration objects for the Delay Measurement PM session. It uses the same indexes that a MEP configuration does: dot1agcfmmdindex, dot1agcfmmaindex, and dot1agcfmmepidentifier, as well as mefsoamdmcfgindex, the specific DM session number on a MEP. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 15

336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 A Delay Measurement session is created on an existing MEP by first accessing the mefsoampmmepopernextindex object and using this value as the mefsoamdmcfgindex during row creation. A single Delay Measurement session tracks Frame Delay and Frame Delay Variation. Configuration/status options are organized into eight general categories. DM Session type, session enable, and counter enables: o mefsoamdmcfgtype o mefsoamdmcfgversion o mefsoamdmcfgenabled o mefsoamdmcfgmeasurementenable o mefsoamdmcfgsessiontype DM Session PDU transmission frequency and Measurement Interval size: o mefsoamdmmessageperiod o mefsoamdmcfgmeasurementinterval o mefsoamdmcfgnumintervalsstored DM Session PDU composition and length: o mefsoamdmcfgpriority o mefsoamdmcfgframesize o mefsoamdmcfgdatapattern o mefsoamdmcfgtesttlvincluded o mefsoamdmcfgtesttlvpattern DM Session peer partner selection: o mefsoamdmcfgdestmacaddress o mefsoamdmcfgdestmepid o mefsoamdmcfgdestismepid o mefsoamdmcfgsourcemacaddress DM Session start, stop, and repetition selection: o mefsoamdmcfgalignmeasurementintervals o mefsoamdmcfgalignmeasurementoffset o mefsoamdmcfgstarttimetype o mefsoamdmcfgfixedstartdateandtime o mefsoamdmcfgrelativestarttime o mefsoamdmcfgstoptimetype contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 16

369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 o mefsoamdmcfgfixedstopdateandtime o mefsoamdmcfgrelativestoptime o mefsoamdmcfgrepetitiontime DM Session status: o mefsoamdmcfgsessionstatus DM Session measurement bin configuration: o mefsoamdmcfgnummeasbinsperframedelayinterval o mefsoamdmcfgnummeasbinsperinterframedelayvariationinterval o mefsoamdmcfginterframedelayvariationselectionoffset o mefsoamdmcfgnummeasbinsperframedelayrangeinterval DM Session history statistic table clear: o mefsoamdmcfghistoryclear 6.3.2 DM Configuration Bin Table The mefsoamdmcfgmeasbintable includes configuration objects for the Delay Measurement Bin PM Session. It uses the same indexes as the mefsoamdmcfgtable as well as the mefsoamdmcfgmeasbintype and mefsoamdmcfgmeasbinnumber. For each row the mefsoamdmcfgmeasbinlowerbound is selected, which defines the lower boundary of each bin. The set of bin boundaries indicates the time range for each of the defined bins. The selection of five bins via either the mefsoamdmcfgnummeasbinsperframedelayinterval or mefsoamdmcfgnummeasbinsperinterframedelayvariationinterval or mefsoamdmcfgnummeasbinsperframedelayrangeinterval objects, results in the set of values for the mefsoamdmcfgmeasbinlowerbound of {0, 5000, 10000, 15000, 20000. These values creates bins with the following lower and upper boundaries: Bin number mefsoamdmcfg MeasBinLowerBound Lower boundary Upper boundary 1 0 0µs < 5,000µs 2 5000 5,000µs < 10,000µs 3 10000 10,000µs < 15,000µs 4 15000 15,000µs < 20,000µs 5 20000 20,000µs < infinity Table 2 Delay Measurement Bin Boundaries 394 6.3.3 DM Measured Statistic Table contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 17

395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 The DM Measured Statistic Table, mefsoamdmmeasuredstatstable, is created automatically when a DM session is created and contains the Delay Measurement statistic information from the last received SOAM PDU. It uses the same indexes as the mefsoamdmcfgtable table. It includes the one-way and two-way measurement stats, mefsoamdmmeasuredstatsframedelaytwoway, mefsoamdmmeasuredstatsframedelayforward, mefsoamdmmeasuredstatsframedelaybackward, the frame variation measurement stats, mefsoamdmmeasuredstatsifdvtwoway, mefsoamdmmeasuredstatsifdvforward, and mefsoamdmmeasuredstatsifdvbackward. 6.3.4 DM Current Statistic Table The DM Current Statistic Table, mefsoamdmcurrentstatstable, is created automatically when a DM session is created and contains the currently enabled statistic counters and statuses for the current Measurement Interval. It uses the same indexes as the mefsoamdmcfgtable table. At the beginning of each Measurement Interval the values in the Current Statistic Table are copied to a new row in the mefsoamdmhistorystatstable and the Current Statistic Table values and statuses are reset to zero and the start time is updated to the Measurement Interval start time. The DM Current Statistic Table objects are organized into six categories. DM interval start time and elapsed time: o mefsoamdmcurrentstatsstarttime o mefsoamdmcurrentstatselapsedtime DM interval suspect status: o mefsoamdmcurrentstatssuspect DM frame delay two-way, forward, and backward min, max, and average (arithmetic mean) counters: o mefsoamdmcurrentstatsframedelaytwowaymin o mefsoamdmcurrentstatsframedelaytwowaymax o mefsoamdmcurrentstatsframedelaytwowayavg o mefsoamdmcurrentstatsframedelayforwardmin o mefsoamdmcurrentstatsframedelayforwardmax o mefsoamdmcurrentstatsframedelayforwardavg o mefsoamdmcurrentstatsframedelaybackwardmin o mefsoamdmcurrentstatsframedelaybackwardmax o mefsoamdmcurrentstatsframedelaybackwardavg DM inter frame delay variation two-way, forward, and backward min, max, and average (arithmetic mean) counters: o mefsoamdmcurrentstatsifdvforwardmin contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 18

431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 o mefsoamdmcurrentstatsifdvforwardmax o mefsoamdmcurrentstatsifdvforwardavg o mefsoamdmcurrentstatsifdvbackwardmin o mefsoamdmcurrentstatsifdvbackwardmax o mefsoamdmcurrentstatsifdvbackwardavg o mefsoamdmcurrentstatsifdvtwowaymin o mefsoamdmcurrentstatsifdvtwowaymax o mefsoamdmcurrentstatsifdvtwowayavg DM frame delay range two-way, forward, and backward, max, and average (arithmetic mean) counters: o mefsoamdmcurrentstatsframedelayrangeforwardmax o mefsoamdmcurrentstatsframedelayrangeforwardavg o mefsoamdmcurrentstatsframedelayrangebackwardmax o mefsoamdmcurrentstatsframedelayrangebackwardavg o mefsoamdmcurrentstatsframedelayrangetwowaymax o mefsoamdmcurrentstatsframedelayrangetwowayavg DM initiated and received measurement counts: o mefsoamdmcurrentstatssoampdussent o mefsoamdmcurrentstatssoampdusreceived 6.3.5 DM Current Statistic Bins Table The DM Current Statistic Bins Table, mefsoamdmcurrentstatsbinstable, is created automatically when a DM session is created and contains the currently enabled statistic bin counters for the current Measurement Interval. It uses the same indexes as the mefsoamdmcfgmeasbintable. At the beginning of each Measurement Interval the values in the Current Bin Statistic Table are copied to a new row, one for each bin number, in the mefsoamdmhistorystatsbinstable and the Current Statistic Bins Table values are reset to zero. The DM Current Bin Statistic Table contains one object per row per bin, mefsoamdmcurrentstatsbinscounter, which indicates a count in the specific bin. 6.3.6 DM History Statistic Table The DM History Statistic Table, mefsoamdmhistorystatsbinstable, is created automatically when the first Measurement Interval completes in a DM session. A new row is created as each Measurement Interval is completed with the information from the completed mefsoamdmcurrentstatstable entry. The oldest row can be deleted after a period of time, but contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 19

465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 is mandatory to be persistent for 32 completed Measurement Intervals and recommended to be persistent for 96 completed Measurement Intervals. The DM History Statistic Table uses the same indexes as the mefsoamdmcfgtable table as well as the one additional index, the mefsoamdmhistorystatsindex number. The DM History Statistic Table contains the same five categories as the mefsoamdmcurrentstatstable table, except the first category is interval end time and elapsed time. The objects are the same except they are listed as History instead of Current. 6.3.7 DM History Bin Statistic Table The DM History Bin Statistic Table, mefsoamdmhistorystatsbintable, is created automatically when the first Measurement Interval completes in a DM session. One row for each bin is created as each Measurement Interval is completed with the information from the completed mefsoamdmcurrentstatsbinstable entry. The oldest rows can be deleted after a period of time, but it is mandatory to be persistent for 32 completed Measurement Intervals and recommended to be persistent for 96 completed Measurement Intervals. The DM History Statistic Bins Table uses the same indexes as the mefsoamdmcfgbinstable table as well as the one additional index the mefsoamdmhistorystatsindex number. The DM History Bin Statistic Table contains the same object as the mefsoamdmcurrentstatsbinstable table, except it is listed as History instead of Current. 6.4 PM MIB Threshold Configuration Objects There are two threshold configuration tables: the mefsoamdmthresholdcfgtable, used for DM thresholds, and the mefsoamlmthresholdcfgtable, used for the LM thresholds. Each table configures a specific threshold for either the DM or LM PM Session. The main purpose of the threshold notifications is to indicate when a specific performance parameter has not been met and to notify the EMS via an alarm. If two managers try to create the same row at the same time, the first creation attempt would succeed, the second creation attempt would result in an error. The second creation attempt would then need to select a new index value to create a new row. Two types of threshold crossings are supported: one that is generated when the value is above the threshold during every Measurement Interval; and one that is generated when a threshold is exceeded (set) and again when the values falls below the threshold (clear). These two types are described further below. Both types of threshold crossing alarms can be supported. 6.4.1 Threshold Above When a measurement value is above the threshold within a Measurement Interval and the specific measurement counter is enabled and the specific threshold is enabled and the threshold above contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 20

501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 alarm is enabled and a PM MIB Above threshold notification has not already been generated during this Measurement Interval, a PM MIB Above threshold notification is generated. 6.4.2 Threshold Set/Clear When a measurement value exceeds the the threshold and the specific measurement counter is enabled and the specific threshold is enabled and the threshold set-clear alarm is enabled and the previous measurement value did not exceed the threshold a PM MIB Set threshold notification is generated. When a measurement value does not exceed the the threshold and the specific measurement counter is enabled and the specific threshold is enabled and the threshold set-clear alarm is enabled and the previous measurement value exceeded the threshold a PM MIB Clear threshold notification is generated. In the case of thresholds applied to a maximum or average (arithmetic mean) measurement counter, the previous measurement value is the value of the counter at the end of the preceding Measurement Interval. In the case of thresholds applied to the last measured value, it is the previous measured value. 6.4.3 LM Thresholds The mefsoamlmthresholdcfgtable is configured after the LM instance is configured. Rows are not automatically created. Each threshold enable is configured via the mefsoamlmthresholdcfgenable object, one bit for each type of threshold. The following LM thresholds are supported: mefsoamlmthresholdcfgmeasuredflrforwardthreshold mefsoamlmthresholdcfgmaxflrforwardthreshold mefsoamlmthresholdcfgavgflrforwardthreshold mefsoamlmthresholdcfgmeasuredflrbackwardthreshold mefsoamlmthresholdcfgmaxflrbackwardthreshold mefsoamlmthresholdcfgavgflrbackwardthreshold mefsoamlmthresholdcfgforwardhighlossthreshold mefsoamlmthresholdcfgforwardconsecutivehighlossthreshold mefsoamlmthresholdcfgbackwardhighlossthreshold mefsoamlmthresholdcfgbackwardconsecutivehighlossthreshold mefsoamlmthresholdcfgforwardunavailcountthreshold mefsoamlmthresholdcfgforwardavailratiothreshold mefsoamlmthresholdcfgbackwardunavailcountthreshold mefsoamlmthresholdcfgbackwardavailratiothreshold contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 21

535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 Maximum FLR, Unavailability, HLI, CHLI and Measured FLR thresholds are evaluated after each measurement, and threshold crossings generate a notification immediately when the threshold crossing is detected. Average FLR thresholds and Availability Ratio are evaluated at the end of each Measurement Interval and threshold crossings generate a notification at the end of the Measurement Interval when the threshold crossing is detected. For Set/Clear thresholds, the same threshold is used for setting and clearing (no hysteresis), and no objects are defined for clearing the threshold by a management action. 6.4.4 DM Thresholds The mefsoamdmthresholdcfgtable is configured after the DM instance is configured. Rows are not automatically created. Each threshold enable is configured via the mefsoamdmthresholdcfgenable object, one bit for each type of threshold. The following DM thresholds are supported: mefsoamdmthresholdcfgmeasuredframedelaytwowaythreshold mefsoamdmthresholdcfgmaxframedelaytwowaythreshold mefsoamdmthresholdcfgavgframedelaytwowaythreshold mefsoamdmthresholdcfgmeasuredifdvtwowaythreshold mefsoamdmthresholdcfgmaxifdvtwowaythreshold mefsoamdmthresholdcfgavgifdvtwowaythreshold mefsoamdmthresholdcfgmaxframedelayrangetwowaythreshold mefsoamdmthresholdcfgavgframedelayrangetwowaythreshol mefsoamdmthresholdcfgmeasuredframedelayforwardthreshold mefsoamdmthresholdcfgmaxframedelayforwardthreshold mefsoamdmthresholdcfgavgframedelayforwardthreshold mefsoamdmthresholdcfgmeasureifdvforwardthreshold mefsoamdmthresholdcfgmaxifdvforwardthreshold mefsoamdmthresholdcfgavgifdvforwardthreshold mefsoamdmthresholdcfgmaframedelayrangeforwardthreshold mefsoamdmthresholdcfgavgframedelayrangeforwardthreshold mefsoamdmthresholdcfgmeasuredframedelaybackwardthreshold mefsoamdmthresholdcfgmaxframedelaybackwardthreshold mefsoamdmthresholdcfgavgframedelaybackwardthreshold mefsoamdmthresholdcfgmeasuredifdvbackwardthreshold contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 22

568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 mefsoamdmthresholdcfgmaxifdvbackwardthreshold mefsoamdmthresholdcfgavgifdvbackwardthreshold mefsoamdmthresholdcfgmaxframedelayrangebackwardthreshold mefsoamdmthresholdcfgavgframedelayrangebackwardthreshold Maximum Frame Delay and IFDV and Measured Frame Delay and IFDV thresholds are evaluated after each measurement, and threshold crossings generate a notification immediately when the threshold crossing is detected. Average Frame Delay and IFDV, and the Average and Maximum Frame Delay Range thresholds are evaluated at the end of each Measurement Interval, and threshold crossings generate a notification at the end of the Measurement Interval when the threshold crossing is detected. For Set/Clear thresholds, the same threshold is used for setting and clearing (no hysteresis), and no objects are defined for clearing the threshold by a management action. 6.5 PM MIB Notifications The following objects are specific to notifications and are included in the list of objects for the specific SOAM PM notifications: mefsoampmnotificationobjdateandtime - contains the time and date at the time that the notification event is detected mefsoampmnotificationobjthresholdid - contains the Object Identifier of the object that caused the generation of the threshold notification mefsoampmnotificationobjthresholdconfig - contains the configured threshold value of the object that caused the generation of the threshold notification mefsoampmnotificationobjthresholdvalue - contains the measured value of the object at the time of generation of the notification mefsoampmnotificationobjsuspect - contains the suspect flag for the current Measurement Interval in which the notification was generated mefsoampmnotificationobjcrossingtype - contains the type of notification crossing mefsoampmnotificationobjdestinationmep - contains the MAC address of the destinion MEP associated with the notification event mefsoampmnotificationobjpriority - contains the CoS priority associated with the notification event The following objects configure notifications: mefsoampmnotificationcfgalarminterval - contains the shortest time interval in seconds between the generation of the same notification type per PM Session. mefsoampmnotificationcfgalarmenable - Enables/Disables specific types of notification. The following SOAM PM notifications can be generated: contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 23

604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 mefsoamavailabilitychange - is sent when the state of the availability of the indicated service changes mefsoamlmsessionstartstop - is sent when the state of the LM session changes mefsoamdmsessionstartstop - is sent when the state of the DM session changes mefsoampmthresholdcrossing - is sent when the value of the threshold crossing object from mefsoamlmthresholdcfgtable or mefsoamdmthresholdcfgtable as indicated by the mefsoampmnotificationthresholdid is crossed. For a notification to be sent the applicable measurement counter needs to be enabled and for threshold crossing notifications a threshold needs to be configured and crossed during a Measurement Interval. 6.6 PM MIB Conformance and Compliance There are two conformances items: the mefsoampmmibcompliances section and the mefsoampmmibgroups conformance group. The units of conformance are organized into the following mandatory groups: mefsoampmmepmandatorygroup mefsoamlmcfgmandatorygroup mefsoamlmmeasuredstatsmandatorygroup mefsoamlmcurrentavailstatsmandatorygroup mefsoamlmcurrentstatsmandatorygroup mefsoamlmhistoryavailstatsmandatorygroup mefsoamlmhistorystatsmandatorygroup mefsoamdmcfgmandatorygroup mefsoamdmcfgmeasbinmandatorygroup mefsoamdmcurrentstatsmandatorygroup mefsoamdmcurrentstatsbinsmandatorygroup mefsoamdmhistorystatsmandatorygroup mefsoamdmhistorystatsbinsmandatorygroup mefsoamlmthresholdmandatorygroup mefsoamdmthresholdmandatorygroup mefsoampmnotificationsmandatorygroup mefsoampmnotificationcfgmandatorygroup mefsoampmnotificationobjmandatorygroup The units of conformance are organized into the following optional groups: contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 24

637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 mefsoampmmepoptionalgroup mefsoamlmcfgoptionalgroup mefsoamlmmeasuredstatsoptionalgroup mefsoamlmcurrentavailstatsoptionalgroup mefsoamlmcurrentstatsoptionalgroup mefsoamlmhistoryavailstatsoptionalgroup mefsoamlmhistorystatsoptionalgroup mefsoamdmcfgoptionalgroup mefsoamdmmeasuredstatsoptionalgroup mefsoamdmcurrentstatsoptionalgroup mefsoamdmhistorystatsoptionalgroup mefsoamlmthresholdoptionalgroup mefsoamdmthresholdoptionalgroup mefsoampmnotificationsoptionalgroup mefsoampmnotificationobjoptionalgroup There is one compliance group, mefsoampmmibcompliance, that contains all the units of conformance groups. 7. SOAM PM MIB Requirements The SOAM PM MIB defines the managed objects necessary to support SOAM PM functionality. Its primary point of reference is the SOAM-PM Implementation Agreement [13]. The SOAM PM MIB implements the SOAM PM functionality as defined in the MEF 17 [10] and the SOAM PM Implementation Agreement [13]. It includes much of the PM functionality defined in ITU-T Y.1731 [20]. The SOAM PM MIB is divided into the following groups: mefsoampmmep - defines the SOAM PM local MEP objects necessary to support the general setup and configuration of SOAM PM functions at a MEP mefsoampmlmobjects - defines the configuration objects necessary to the support the Loss Measurement session and the current and history results tables mefsoampmdmobjects - defines the configuration objects necessary to support the Delay Measurement session and the current and history results tables mefsoampmnotificationcfg defines the configuration objects necessary to control generation of SOAM PM notifications mefsoampmnotificationobj - defines the notification objects necessary to fully define and report SOAM PM notifications contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 25

671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 mefsoampmnotifications - defines the notifications necessary to implement the SOAM PM functionality [R1] [D1] [R2] [D2] [R3] [D3] [R4] [D4] [R5] The mefsoampmmep group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoampmmeplmsingleendedresponder object. The mefsoampmmep group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamlmcfgtable of the mefsoampmlmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoamlmcfgversion, mefsoamlmcfgtesttlvincluded, mefsoamlmcfgtesttlvpattern, mefsoamlmcfgalignmeasurementintervals, mefsoamlmcfgavailabilitynumconsecutivehighflr, mefsoamlmcfgalignmeasurementoffset objects. The mefsoamlmcfgtable of the mefsoampmlmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamlmmeasuredstatstable of the mefsoampmlmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoamlmmeasuredstatsforwardflr, mefsoamlmmeasuredstatsbackwardflr, mefsoamlmmeasuredstatsavailforwardstatus, mefsoamlmmeasuredstatsavailbackwardstatus objects. The mefsoamlmmeasuredstatstable of the mefsoampmlmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamlmcurrentavailstatstable of the mefsoampmlmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoamlmcurrentavailstatsforwardhighloss, mefsoamlmcurrentavailstatsbackwardhighloss, mefsoamlmcurrentavailstatsforwardconsecutivehighloss, mefsoamlmcurrentavailstatsbackwardconsecutivehighloss, mefsoamlmcurrentavailstatsforwardminflr, mefsoamlmcurrentavailstatsforwardmaxflr, mefsoamlmcurrentavailstatsforwardavgflr, mefsoamlmcurrentavailstatsbackwardminflr, mefsoamlmcurrentavailstatsbackwardmaxflr, mefsoamlmcurrentavailstatsbackwardavgflr objects. The mefsoamlmcurrentavailstatstable of the mefsoampmlmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamlmcurrentstatstable of the mefsoampmlmobjects group SHALL be supported for devices that are compliant with SOAM PM function- contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 26

713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 [D5] [R6] [D6] [R7] [D7] ality except for the mefsoamlmcurrentstatsforwardtransmittedframes, mefsoamlmcurrentstatsforwardreceivedframes, mefsoamlmcurrentstatsbackwardtransmittedframes, mefsoamlmcurrentstatsbackwardreceivedframes, mefsoamlmcurrentstatsforwardminflr, mefsoamlmcurrentstatsforwardmaxflr, mefsoamlmcurrentstatsforwardavgflr, mefsoamlmcurrentstatsbackwardminflr, mefsoamlmcurrentstatsbackwardmaxflr, mefsoamlmcurrentstatsbackwardavgflr, objects. The mefsoamlmcurrentstatstable of the mefsoampmlmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamlmhistoryavailstatstable of the mefsoampmlmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoamlmhistoryavailstatsforwardhighloss, mefsoamlmhistoryavailstatsbackwardhighloss, mefsoamlmhistoryavailstatsforwardconsecutivehighloss, mefsoamlmhistoryavailstatsbackwardconsecutivehighloss, mefsoamlmhistoryavailstatsforwardminflr, mefsoamlmhistoryavailstatsforwardmaxflr, mefsoamlmhistoryavailstatsforwardavgflr, mefsoamlmhistoryavailstatsbackwardminflr, mefsoamlmhistoryavailstatsbackwardmaxflr, mefsoamlmhistoryavailstatsbackwardavgflr objects. The mefsoamlmhistoryavailstatstable of the mefsoampmlmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamlmhistorystatstable of the mefsoampmlmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoamlmhistorystatsforwardtransmittedframes, mefsoamlmhistorystatsforwardreceivedframes, mefsoamlmhistorystatsbackwardtransmittedframes, mefsoamlmhistorystatsbackwardreceivedframes, mefsoamlmhistorystatsforwardminflr, mefsoamlmhistorystatsforwardmaxflr, mefsoamlmhistorystatsforwardavgflr, mefsoamlmhistorystatsbackwardminflr, mefsoamlmhistorystatsbackwardmaxflr, mefsoamlmhistorystatsbackwardavgflr, objects. The mefsoamlmhistorystatstable of the mefsoampmlmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 27

756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 [R8] [D8] [R9] [D9] [R10] [D10] [R11] [R12] [D11] [R13] [R14] The mefsoamdmcfgtable of the mefsoampmdmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoamdmcfgversion, mefsoamdmcfgtesttlvincluded, mefsoamdmcfgtesttlvpattern, mefsoamdmcfgsourcemacaddress, mefsoamdmcfgalignmeasurementoffset, mefsoamdmcfginterframedelayvariationselectionoffset objects. The mefsoamdmcfgtable of the mefsoampmdmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamdmcfgmeasbintable of the mefsoampmdmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality. The mefsoamdmmeasuredstatstable of the mefsoampmdmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamdmcurrentstatstable of the mefsoampmdmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoamdmcurrentstatsifdvtwowaymin, mefsoamdmcurrentstatsifdvtwowaymax, mefsoamdmcurrentstatsifdvtwowayavg, mefsoamdmcurrentstatsframedelayrangetwowaymax, mefsoamdmcurrentstatsframedelayrangetwowayavg objects. The mefsoamdmcurrentstatstable of the mefsoampmdmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamdmcurrentstatsbinstable of the mefsoampmdmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality. The mefsoamdmhistorystatstable of the mefsoampmdmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoamdmhistorystatsifdvtwowaymin, mefsoamdmhistorystatsifdvtwowaymax, mefsoamdmhistorystatsifdvtwowayavg, mefsoamdmhistorystatsframedelayrangetwowaymax, mefsoamdmhistorystatsframedelayrangetwowayavg objects. The mefsoamdmhistorystatstable of the mefsoampmdmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamdmhistorystatsbinstable of the mefsoampmdmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality. The mefsoamlmthresholdcfgtable of the mefsoampmlmobjects group SHALL be supported for devices that are compliant with SOAM PM function- contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 28

798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 [D12] [R15] [D13] [R16] [R17] [D14] [R18] [D15] ality except for the mefsoamlmthresholdcfgforwardhighlossthreshold, mefsoamlmthresholdcfgforwardconsecutivehighlossthreshold, mefsoamlmthresholdcfgbackwardhighlossthreshold, mefsoamlmthresholdcfgbackwardconsecutivehighlossthreshold, mefsoamlmthresholdcfgmeasuredflrforwardthreshold, mefsoamlmthresholdcfgmeasuredflrbackwardthreshold objects. The mefsoamlmthresholdcfgtable of the mefsoampmlmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoamdmthresholdcfgtable of the mefsoampmdmobjects group SHALL be supported for devices that are compliant with SOAM PM functionality except for the mefsoamdmthresholdcfgmeasuredifdvtwowaythreshold, mefsoamdmthresholdcfgmeasuredframedelayforwardthreshold, mefsoamdmthresholdcfgmeasuredifdvforwardthreshold, mefsoamdmthresholdcfgmeasuredframedelaybackwardthreshold, mefsoamdmthresholdcfgmeasuredifdvbackwardthreshold, mefsoamdmthresholdcfgmeasuredframedelaytwowaythreshold, mefsoamdmthresholdcfgmaxifdvtwowaythreshold, mefsoamdmthresholdcfgavgifdvtwowaythreshold, mefsoamdmthresholdcfgmaxframedelayrangetwowaythreshold, mefsoamdmthresholdcfgavgframedelayrangetwowaythreshold objects. The mefsoamdmthresholdcfgtable of the mefsoampmdmobjects group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoampmnotificationcfg group SHALL be supported for devices that are compliant with SOAM PM functionality. The mefsoampmnotificationobj group SHALL be supported for devices that are compliant with SOAM PM functionality, except for the mefsoampmnotificationobjthresholdconfig, mefsoampmnotificationobjthresholdid, mefsoampmnotificationobjthresholdvalue, mefsoampmnotificationobjcrossingtype objects. The mefsoampmnotificationobj group SHOULD be supported for devices that are compliant with SOAM PM functionality. The mefsoampmnotifications group SHALL be supported for devices that are compliant with SOAM PM functionality, except for the mefsoampmthresholdcrossingalarm object. The mefsoampmnotifications group SHOULD be supported for devices that are compliant with SOAM PM functionality. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 29

839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 8. SOAM PM MIB Definitions MEF-SOAM-PM-MIB DEFINITIONS ::= BEGIN IMPORTS NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Gauge32, enterprises FROM SNMPv2-SMI -- RFC 2578 RowStatus, TruthValue, MacAddress, DateAndTime, TimeInterval FROM SNMPv2-TC -- RFC 2579 OBJECT-GROUP, NOTIFICATION-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF -- RFC 2580 dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, dot1agcfmmepentry, Dot1afCfmIndexIntegerNextFree, Dot1agCfmMepIdOrZero FROM IEEE8021-CFM-MIB -- IEEE 802.1ag IEEE8021PriorityValue FROM IEEE8021-TC-MIB -- IEEE 802.1ap MefSoamTcOperationTimeType, MefSoamTcDataPatternType, MefSoamTcTestPatternType, MefSoamTcAvailabilityType, MefSoamTcDelayMeasurementBinType, MefSoamTcMeasurementPeriodType, MefSoamTcSessionType, MefSoamTcStatusType FROM MEF-SOAM-TC-MIB; mefsoampmmib MODULE-IDENTITY LAST-UPDATED 201201131200Z -- January 13, 2012 ORGANIZATION Metro Ethernet Forum CONTACT-INFO Web URL: http://metroethernetforum.org/ E-mail: mibs@metroethernetforum.org Postal: Metro Ethernet Forum 6033 W. Century Boulevard, Suite 830 Los Angeles, CA 90045 U.S.A. Phone: +1 310-642-2800 Fax: +1 310-642-2808 This MIB module contains the management objects for the management of Ethernet Services Operations, Administration and Maintenance for Performance Monitoring. Copyright 2010, 2011, 2012 Metro Ethernet Forum All rights reserved. **************************************************************************** Reference Overview A number of base documents have been used to create the Textual Conventions MIB, the SOAM-PM MIB and SOAM-FM extension MIB. The following are the abbreviations for the baseline documents: [CFM] refers to 'Connectivity Fault Management', IEEE 802.1ag-2007, December 2007 [MEF7.1] refers to MEF 7.1 'Phase 2 EMS-NMS Information Model', October 2009 [MEF17] refers to MEF 17 'Service OAM Requirements & Framework - Phase 1', April 2007 [MEF10.2.1] refers to MEF 10.2.1 'Ethernet Services Attributes Phase 2', January 2011 [MEF SOAM-PM] refers to MEF 35 'Service OAM Performance Monitoring Implementation Agreement', January 2012 [MEF SOAM-FM] refers to MEF 30 'Service OAM Fault Management Implementation Agreement', January 2011 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 30

899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 [Q.840.1] refers to 'ITU-T Requirements and analysis for NMS-EMS management interface of Ethernet over Transport and Metro Ethernet Network (EoT/MEN)', March 2007 [Y.1731] refers to ITU-T Y.1731 'OAM functions and mechanisms for Ethernet based networks', February 2011 **************************************************************************** Abbreviations Used Term Definition Availability Performance A measure of the percentage of time within a specified time interval during which the frame loss is small Backward OAM information sent from the Responder MEP to the Controller MEP. For LM it indicates the frame counts/loss from the Responder MEP to the Controller MEP. For DM is indicates the delay and delay variation from the Responder MEP to the Controller MEP. BSS Business Support System CCM Continuity Check Message CFM Connectivity Fault Management CHLI Consecutive High Loss Interval, a sequence of small time intervals contained in T, each with high frame loss ratio Controller MEP The Controller MEP initiates SOAM PDUs, and receives responses from the Responder MEP. CoS Class of Service DM Delay Measurement Dual-Ended A type of process where a MEP sends measurement information to a peer MEP that will perform the calculations. EMS Element Management System ETH-DM Ethernet Delay Measurement function ETH-LM Ethernet Loss Measurement function ETH-SLM Ethernet Synthetic Frame Loss Measurement function EVC Ethernet Virtual Connection FD Frame Delay FDR Frame Delay Range FLR Frame Loss Ratio FM Fault Management Forward OAM information sent from the Controller MEP to the Responder MEP. For LM it indicates the frame counts/loss from the Controller MEP to the Responder MEP. For DM is indicates the delay and delay variation from the Controller MEP to the Responder MEP. HLI High Loss Interval, a small time interval contained in T with a high frame loss ratio IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force IFDV Inter-Frame Delay Variation ITU-T International Telecommunication Union - Telecommunication Standardization Bureau LAN Local Area Network LM Loss Measurement MAC Media Access Control MA Maintenance Association (equivalent to a MEG) MD Maintenance Domain (equivalent to a OAM Domain in MEF 17) MD Level Maintenance Domain Level (equivalent to a MEG level) ME Maintenance Entity Measurement Bin A Measurement Bin is a counter that stores the number of performance measurements falling within a specified range, during a Measurement Interval Measurement Interval A period of time during which measurements are taken. Measurements initiated during one Measurement Interval are kept separate from measurements taken during other Measurement Intervals. It is important to note that this is different from T. MEF Metro Ethernet Forum MEG Maintenance Entity Group (equivalent to a MA) MEG Level Maintenance Entity Group Level (equivalent to MD Level) contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 31

963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 MEN Metro Ethernet Network MEP Maintenance Association End Point or MEG End Point MFD Mean Frame Delay MIB Management Information Base MIP Maintenance Domain Intermediate Point or MEG Intermediate Point MP Maintenance Point. One of either a MEP or a MIP NE Network Element NMS Network Management System OAM Operations, Administration, and Maintenance On-Demand OAM actions that are initiated via manual intervention for a limited time to carry out diagnostics. On-Demand OAM can result in singular or periodic OAM actions during the diagnostic time interval One-way A measurement performed in the forward or backward direction. For example from MEP A to MEP B or from MEP B to MEP A. OSS Operations Support System PDU Protocol Data Unit PM Performance Monitoring PM Function A MEP capability specified for performance monitoring purposes (e.g., Single-Ended Delay, Single-Ended Synthetic Loss) PM Session A PM Session is the application of a given PM Function between a given pair of MEPs and using a given CoS Frame Set over some (possibly indefinite) period of time. PM Solution A PM Solution is a set of related requirements that when implemented allow a given set of performance metrics to be measured using a given set of PM functions. PM Tool A generic term used to discuss the application of a PM Function. Proactive OAM actions that are carried on continuously to permit timely reporting of fault and/or performance status. Resiliency Performance The number of High Loss Intervals and Consecutive High Loss Intervals in T Responder MEP In a single-ended session, the Responder MEP receives SOAM PDUs, from the Controller MEP, and transmits a response to the Controller MEP. SOAM-PM RFC Request for Comment Service Frame An Ethernet frame transmitted across the UNI toward the Service Provider or an Ethernet frame transmitted across the UNI toward the Subscriber Single-Ended A type of process where a MEP sends a measurement request and the peer MEP replies with the requested information so the originating MEP can calculate the measurement. Sink MEP In a dual-ended session, the Sink MEP receives SOAM PDUs, from the Controller MEP and performs the performance calculations. SLM Synthetic Loss Measurement SNMP Simple Network Management Protocol SNMP Agent An SNMP entity containing one or more command responder and/or notification originator applications (along with their associated SNMP engine). Typically implemented in an NE. SNMP Manager An SNMP entity containing one or more command generator and/or notification receiver applications (along with their associated SNMP engine). Typically implemented in an EMS or NMS. SOAM Service OAM SOAM PDU Service OAM frame, or Protocol Data Unit. Specifically, those PDUs defined in [IEEE 802.1ag], [ITU-T Y.1731], or MEF specifications Synthetic Traffic SOAM traffic that emulates service traffic in order to measure the performance experience. Delay measurements must use synthetic traffic, because user traffic does not contain standardized timestamp fields. Other measurements, such as Frame Loss, may also use synthetic frames for certain advantages (e.g., ability to measure loss in multipoint services). T Time Interval for SLS Metricss. The time over which a Performance Metric is defined. T is at least as large as the Measurement Interval, and generally consists of multiple Measurement contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 32

1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 TC TLV Two-way UML UTC UNI VLAN Intervals. Textual Conventions Type Length Value, a method of encoding Objects A measurement of the performance of frames that flow from the Controller MEP to Responder MEP and back again. Unified Modeling Language Coordinated Universal Time User-to-Network Interface Virtual LAN REVISION 201201131200Z -- January 13, 2012 Initial Version. ::= { enterprises mef(15007) mefsoam(1) 3 -- ***************************************************************************** -- Object definitions in the SOAM PM MIB Module -- ***************************************************************************** mefsoampmnotifications OBJECT IDENTIFIER ::= { mefsoampmmib 0 mefsoampmmibobjects OBJECT IDENTIFIER ::= { mefsoampmmib 1 mefsoampmmibconformance OBJECT IDENTIFIER ::= { mefsoampmmib 2 -- ***************************************************************************** -- Groups in the SOAM PM MIB Module -- ***************************************************************************** mefsoampmmep OBJECT IDENTIFIER ::= { mefsoampmmibobjects 1 mefsoampmlmobjects OBJECT IDENTIFIER ::= { mefsoampmmibobjects 2 mefsoampmdmobjects OBJECT IDENTIFIER ::= { mefsoampmmibobjects 3 mefsoampmnotificationcfg OBJECT IDENTIFIER ::= { mefsoampmmibobjects 4 mefsoampmnotificationobj OBJECT IDENTIFIER ::= { mefsoampmmibobjects 5 -- ***************************************************************************** -- Ethernet MEP Performance Monitoring Configuration -- ***************************************************************************** mefsoampmmeptable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamPmMepEntry MAX-ACCESS not-accessible This table is an extension of the dot1agcfmmeptable and rows are automatically added or deleted from this table based upon row creation and destruction of the dot1agcfmmeptable. This table represents the local MEP PM configuration table. The primary purpose of this table is provide local parameters for the SOAM PM function found in [Y.1731] and [MEF SOAM-PM] and instantiated at a MEP. [Y.1731], [MEF SOAM-PM] ::= { mefsoampmmep 1 mefsoampmmepentry OBJECT-TYPE SYNTAX MefSoamPmMepEntry MAX-ACCESS not-accessible The conceptual row of mefsoampmmeptable. AUGMENTS { dot1agcfmmepentry ::= { mefsoampmmeptable 1 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 33

1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 MefSoamPmMepEntry ::= SEQUENCE { mefsoampmmepopernextindex mefsoampmmeplmsingleendedresponder mefsoampmmepslmsingleendedresponder mefsoampmmepdmsingleendedresponder Dot1afCfmIndexIntegerNextFree, TruthValue, TruthValue, TruthValue mefsoampmmepopernextindex OBJECT-TYPE SYNTAX Dot1afCfmIndexIntegerNextFree This object contains an unused value for a PM session number on a MEP that can be used for either LM or DM sessions, or a zero to indicate that none exist. This value needs to be read in order to find an available index for row-creation of a PM session on a MEP and then used when a row is created. This value is automatically updated by the SNMP Agent after the row is created. Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never to be reused for other PM sessions on the same MEP while this session is active, or until it wraps to zero. The index value keeps increasing up to that time. This is to facilitate access control based on a fixed index for an EMS, since the index is not reused. This object is an extension of the dot1agcfmmeptable and the object is automatically added or deleted based upon row creation and destruction of the dot1agcfmmeptable. ::= { mefsoampmmepentry 1 mefsoampmmeplmsingleendedresponder OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write This object specifies whether the Loss Measurement (LMM) single-ended Responder is enabled. The value 'true' indicates the single-ended Loss Measurement Responder is enabled and if a LMM message is received a LMR will be sent in reply. The value 'false' indicates the single-ended Loss Measurement Responder is disabled. If a LMM message is received no response will be sent and the message will be discarded. This object needs to be persistent upon reboot or restart of a device. A MEP can be both a single-ended Responder and Controller simultaneously. DEFVAL { true ::= { mefsoampmmepentry 2 mefsoampmmepslmsingleendedresponder OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write This object specifies whether the Synthetic Loss Measurement (SLM) single-ended Responder is enabled. The value 'true' indicates the single-ended SLM Responder is enabled and contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 34

1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 if a SLM message is received a SLR will be sent in reply. The value 'false' indicates the single-ended SLM Responder is disabled. If a SLM message is received no response will be sent and the message will be discarded. This object needs to be persistent upon reboot or restart of a device. A MEP can be both a single-ended Responder and Controller simultaneously. DEFVAL { true ::= { mefsoampmmepentry 3 mefsoampmmepdmsingleendedresponder OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write This object specifies whether the Delay Measurement (DMM) single ended Responder is enabled. The value 'true' indicates the single-ended Delay Measurement Responder is enabled and if a DMM message is received a DMR will be sent in reply. The value 'false' indicates the single-ended Delay Measurement Responder is disabled. If a DMM message is received no response will be sent and the message will be discarded. This object needs to be persistent upon reboot or restart of a device. A MEP can be both a single-ended Responder and Controller simultaneously. DEFVAL { true ::= { mefsoampmmepentry 4 -- ***************************************************************************** -- Ethernet Loss Measurement Configuration Table -- ***************************************************************************** mefsoamlmcfgtable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamLmCfgEntry MAX-ACCESS not-accessible This table includes configuration objects and operations for the Frame Loss Measurement function defined in [Y.1731] and [MEF SOAM-PM]. Each row in the table represents a Loss Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. A Loss Measurement session is created on an existing MEP by first accessing the mefsoampmmepopernextindex object and using this value as the mefsoamlmcfgindex in the row creation. Some writable objects in this table are only applicable in certain cases (as described under each object), and attempts to write values for them in other cases will be ignored. The writable objects in this table need to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R68; [Y.1731] contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 35

1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 ::= { mefsoampmlmobjects 1 mefsoamlmcfgentry OBJECT-TYPE SYNTAX MefSoamLmCfgEntry MAX-ACCESS not-accessible The conceptual row of mefsoamlmcfgtable. INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamlmcfgindex ::= { mefsoamlmcfgtable 1 MefSoamLmCfgEntry ::= SEQUENCE { mefsoamlmcfgindex mefsoamlmcfgtype mefsoamlmcfgversion mefsoamlmcfgenabled mefsoamlmcfgmeasurementenable mefsoamlmcfgmessageperiod mefsoamlmcfgpriority mefsoamlmcfgframesize mefsoamlmcfgdatapattern mefsoamlmcfgtesttlvincluded mefsoamlmcfgtesttlvpattern mefsoamlmcfgmeasurementinterval mefsoamlmcfgnumintervalsstored mefsoamlmcfgdestmacaddress mefsoamlmcfgdestmepid mefsoamlmcfgdestismepid mefsoamlmcfgstarttimetype mefsoamlmcfgfixedstartdateandtime mefsoamlmcfgrelativestarttime mefsoamlmcfgstoptimetype mefsoamlmcfgfixedstopdateandtime mefsoamlmcfgrelativestoptime mefsoamlmcfgrepetitiontime mefsoamlmcfgalignmeasurementintervals mefsoamlmcfgalignmeasurementoffset mefsoamlmcfgavailabilitymeasurementinterval mefsoamlmcfgavailabilitynumconsecutivemeaspdus mefsoamlmcfgavailabilityflrthreshold mefsoamlmcfgavailabilitynumconsecutiveintervals mefsoamlmcfgavailabilitynumconsecutivehighflr mefsoamlmcfgsessiontype mefsoamlmcfgsessionstatus mefsoamlmcfghistoryclear mefsoamlmcfgrowstatus mefsoamlmcfgindex OBJECT-TYPE (1..4294967295) MAX-ACCESS not-accessible Unsigned32, INTEGER, Unsigned32, TruthValue, BITS, MefSoamTcMeasurementPeriodType, IEEE8021PriorityValue, Unsigned32, MefSoamTcDataPatternType, TruthValue, MefSoamTcTestPatternType, Unsigned32, Unsigned32, MacAddress, Dot1agCfmMepIdOrZero, TruthValue, MefSoamTcOperationTimeType, DateAndTime, TimeInterval, MefSoamTcOperationTimeType, DateAndTime, TimeInterval, Unsigned32, TruthValue, Unsigned32, Unsigned32, Unsigned32, Unsigned32, Unsigned32, Unsigned32, MefSoamTcSessionType, MefSoamTcStatusType, TruthValue, RowStatus contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 36

1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 An index to the Loss Measurement Configuration table which indicates the specific measurement session for the MEP. mefsoampmmepopernextindex needs to be inspected to find an available index for row-creation. Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused for other PM sessions on the same MEP while this session is active. The index value keeps increasing until it wraps to 0. This is to facilitate access control based on a fixed index for an EMS, since the index is not reused. ::= { mefsoamlmcfgentry 1 mefsoamlmcfgtype OBJECT-TYPE SYNTAX INTEGER { lmlmm (1), lmslm (2), lmccm (3) This object specifies what type of Loss Measurement will be performed. lmlmm(1) lmslm(2) lmccm(3) LMM SOAM PDU generated and received LMR responses tracked SLM SOAM PDU generated and received SLR responses tracked CCM SOAM PDU generated and received CCM PDUs tracked The lmslm value is required. The lmlmm and lmccm values are optional. The lmccm loss measurement values are only valid for a point-to-point MEG. Multipoint MEGs may give unreliable loss measurements. This object can only be written at row creation time and cannot be modified once it has been created. [Y.1731] [MEF SOAM-PM] R51, R68, O7, R102 DEFVAL { lmslm ::= { mefsoamlmcfgentry 2 mefsoamlmcfgversion OBJECT-TYPE This object indicates the version of the PDUs used to perform Loss Measurement. The value is placed in the Version field of the PDU and indicates that the PDU format used is the format defined in Y.1731 with that version. The exact PDUs to use are specified by this object in combination with mefsoamlmcfgtype. This object can only be written at row creation time and cannot be modified once it has been created. [Y.1731] contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 37

1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 DEFVAL { 0 ::= { mefsoamlmcfgentry 3 mefsoamlmcfgenabled OBJECT-TYPE SYNTAX TruthValue This object specifies whether the Loss Measurement session is enabled. The value 'true' indicates the Loss Measurement session is enabled and SOAM PDUs are sent and/or measurements are collected when the session is running according to the scheduling objects (start time, stop time, etc.). The value 'false' indicates the Loss Measurement session is disabled and SOAM PDUs are not sent and/or measurements collected. For a Loss Measurement session to be removed the row is deleted in order to release internal resources. This object can written/modified after row creation time. If the LM session is enabled it resumes after shutdown/restart. If the LM session is disabled the current Measurement Interval is stopped, if it in process at the time, and all the in process calculations for the partially completed Measurement Interval are finalized. This object does not affect whether the single-ended Responder is enabled or not, which is enabled or disabled by the mefsoampmmeplmsingleendedresponder and mefsoampmmepslmsingleendedresponder objects. [MEF SOAM-PM] R4, R5, R6, O1, R12, R14 DEFVAL { true ::= { mefsoamlmcfgentry 4 mefsoamlmcfgmeasurementenable OBJECT-TYPE SYNTAX BITS { bforwardtransmitedframes(0), bforwardreceivedframes(1), bforwardminflr(2), bforwardmaxflr(3), bforwardavgflr(4), bbackwardtransmitedframes(5), bbackwardreceivedframes(6), bbackwardminflr(7), bbackwardmaxflr(8), bbackwardavgflr(9), bsoampdussent(10), bsoampdusreceived (11), bavailforwardhighloss(12), bavailforwardconsecutivehighloss(13), bavailforwardavailable(14), bavailforwardunavailable(15), bavailforwardminflr(16), bavailforwardmaxflr(17), bavailforwardavgflr(18), bavailbackwardhighloss(19), contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 38

1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 bavailbackwardconsecutivehighloss(20), bavailbackwardavailable(21), bavailbackwardunavailable(22), bavailbackwardminflr(23), bavailbackwardmaxflr(24), bavailbackwardavgflr(25), bmeasuredstatsforwardmeasuredflr(26), bmeasuredstatsbackwardmeasuredflr(27), bmeasuredstatsavailforwardstatus(28), bmeasuredstatsavailbackwardstatus(29) A vector of bits that indicates the type of SOAM LM counters found in the mefsoamlmmeasuredstatstable, mefsoamlmcurrentstatstable, mefsoamlmhistorystatstable, mefsoamlmcurrentavailstatstable and mefsoamlmhistoryavailstatstable that are enabled. A bit set to '1' enables the specific SOAM LM counter. A bit set to '0' disables the SOAM LM counter. If a particular SOAM LM counter is not supported the BIT value is set to '0'. Not all SOAM LM counters are supported for all SOAM LM types. This object can only be written at row creation time and cannot be modified once it has been created. bforwardtransmitedframes (0) Enables/disables the mefsoamlmcurrentstatsforwardtransmittedframes and mefsoamlmhistorystatsforwardtransmittedframes counters. bforwardreceivedframes(1) Enables/disables the mefsoamlmcurrentstatsforwardreceivedframes and mefsoamlmhistorystatsforwardreceivedframes counters. bforwardminflr(2) Enables/disables the mefsoamlmcurrentstatsforwardminflr and mefsoamlmhistorystatsforwardminflr counters. bforwardmaxflr(3) Enables/disables the mefsoamlmcurrentstatsforwardmaxflr and mefsoamlmhistorystatsforwardmaxflr counters. bforwardavgflr(4) Enables/disables the mefsoamlmcurrentstatsforwardavgflr and mefsoamlmhistorystatsforwardavgflr counters. bbackwardtransmitedframes(5) Enables/disables the mefsoamlmcurrentstatsbackwardtransmittedframes and mefsoamlmhistorystatsbackwardtransmittedframes counters. bbackwardreceivedframes(6) Enables/disables the mefsoamlmcurrentstatsbackwardreceivedframes and mefsoamlmhistorystatsbackwardreceivedframes counters. bbackwardminflr(7) Enables/disables the mefsoamlmcurrentstatsbackwardminflr and mefsoamlmhistorystatsbackwardminflr counters. bbackwardmaxflr(8) Enables/disables the mefsoamlmcurrentstatsbackwardmaxflr and mefsoamlmhistorystatsbackwardmaxflr counters. bbackwardavgflr(9) Enables/disables the mefsoamlmcurrentstatsbackwardavgflr and mefsoamlmhistorystatsbackwardavgflr counters. bsoampdussent (10) Enables/disables the mefsoamlmcurrentstatssoampdussent and mefsoamlmhistorystatssoampdussent counters. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 39

1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 bsoampdusreceivedbreceivedmeasurements (11) Enables/disables the mefsoamlmcurrentstatssoampdusreceived and mefsoamlmhistorystatssoampdusreceived counters. bavailforwardhighloss(12) Enables/disables the mefsoamlmcurrentavailstatsforwardhighloss and mefsoamlmhistoryavailstatsforwardhighloss counters. bavailforwardconsecutivehighloss(13) Enables/disables the mefsoamlmcurrentavailstatsforwardconsecutivehighloss and mefsoamlmhistoryavailstatsforwardconsecutivehighloss counters. bavailforwardavailable(14) Enables/disables the mefsoamlmcurrentavailstatsforwardavailable and mefsoamlmhistoryavailstatsforwardavailable counters. bavailforwardunavailable(15) Enables/disables the mefsoamlmcurrentavailstatsforwardunavailable and mefsoamlmhistoryavailstatsforwardunavailable counters. bavailforwardminflr(16) Enables/disables the mefsoamlmcurrentavailstatsforwardminflr and mefsoamlmhistoryavailstatsforwardminflr counters. bavailforwardmaxflr(17) Enables/disables the mefsoamlmcurrentavailstatsforwardmaxflr and mefsoamlmhistoryavailstatsforwardmaxflr counters. bavailforwardavgflr(18) Enables/disables the mefsoamlmcurrentavailstatsforwardavgflr and mefsoamlmhistoryavailstatsforwardavgflr counters. bavailbackwardhighloss(19) Enables/disables the mefsoamlmcurrentavailstatsbackwardhighloss and mefsoamlmhistoryavailstatsbackwardhighloss counters. bavailbackwardconsecutivehighloss(20) Enables/disables the mefsoamlmcurrentavailstatsbackwardconsecutivehighloss and mefsoamlmhistoryavailstatsbackwardconsecutivehighloss counters. bavailbackwardavailable(21) Enables/disables the mefsoamlmcurrentavailstatsbackwardavailable and mefsoamlmhistoryavailstatsbackwardavailable counters. bavailbackwardunavailable(22) Enables/disables the mefsoamlmcurrentavailstatsbackwardunavailable and mefsoamlmhistoryavailstatsbackwardunavailable counters. bavailbackwardminflr(23) Enables/disables the mefsoamlmcurrentavailstatsbackwardminflr and mefsoamlmhistoryavailstatsbackwardminflr counters. bavailbackwardmaxflr(24) Enables/disables the mefsoamlmcurrentavailstatsbackwardmaxflr and mefsoamlmhistoryavailstatsbackwardmaxflr counters. bavailbackwardavgflr(25) Enables/disables the mefsoamlmcurrentavailstatsbackwardavgflr and mefsoamlmhistoryavailstatsbackwardavgflr counters. bmeasuredstatsforwardmeasuredflr(26) Enables/disables the mefsoamlmmeasuredstatsforwardflr counter. bmeasuredstatsbackwardmeasuredflr(27) Enables/disables the mefsoamlmmeasuredstatsbackwardflr counter. bmeasuredstatsavailforwardstatus(28) Enables/disables the mefsoamlmmeasuredstatsavailforwardstatus counter. bmeasuredstatsavailbackwardstatus(29) Enables/disables the mefsoamlmmeasuredstatsavailbackwardstatus counter. [Y.1731] DEFVAL { { ::= { mefsoamlmcfgentry 5 mefsoamlmcfgmessageperiod OBJECT-TYPE SYNTAX MefSoamTcMeasurementPeriodType contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 40

1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 UNITS ms This object specifies the interval between Loss Measurement OAM message transmission. For Loss Measurement monitoring applications the default value is 1 sec. This object is not applicable if mefsoamlmcfgtype is set to lmccm and is ignored for that Loss Measurement Type. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R76, R77, D29, D30 DEFVAL { 1000 ::= { mefsoamlmcfgentry 6 mefsoamlmcfgpriority OBJECT-TYPE SYNTAX IEEE8021PriorityValue This object specifies the Loss Measurement OAM message priority as well as the priority of the service/oam traffic to be monitored. Only frames of the same Class of Service are counted. The default value is to be the value which yields the lowest frame loss. This object is not applicable if mefsoamlmcfgtype is set to lmccm. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R1, R2, R71, D28, R72, R73, R105-R109, D45; [MEF 10.2.1] Section 6.8 ::= { mefsoamlmcfgentry 7 mefsoamlmcfgframesize OBJECT-TYPE (64..9600) UNITS bytes This object specifies the Loss Measurement frame size between 64 bytes and the maximum transmission unit of the EVC. The range of frame sizes from 64 through 2000 octets need to be supported, and the range of frame sizes from 2001 through 9600 octets is suggested be supported. The adjustment to the frame size of the standard frame size is accomplished by the addition of a Data or Test TLV. A Data or Test TLV is only added to the frame if the frame size is greater than 64 bytes. This object is only valid for the entity transmitting the Loss Measurement frames, type 'lmslm', and is ignored by the entity receiving frames. It is not applicable for the 'lmccm' or 'lmlmm' types. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 41

1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R78, R79, D31, D32 [Y.1731] DEFVAL { 64 ::= { mefsoamlmcfgentry 8 mefsoamlmcfgdatapattern OBJECT-TYPE SYNTAX MefSoamTcDataPatternType This object specifies the LM data pattern included in a Data TLV when the size of the LM frame is determined by the mefsoamlmframesize object and mefsoamlmtesttlvincluded is 'false'. If the frame size object does not define the LM frame size or mefsoamlmtesttlvincluded is 'true' the value of this object is ignored. This object can only be written at row creation time and cannot be modified once it has been created. DEFVAL { zeropattern ::= { mefsoamlmcfgentry 9 mefsoamlmcfgtesttlvincluded OBJECT-TYPE SYNTAX TruthValue Indicates whether a Test TLV or Data TLV is included when the size of the LM frame is determined by the mefsoamlmframesize object. A value of 'true' indicates that the Test TLV is to be included. A value of 'false' indicates that the Data TLV is to be included. If the frame size object does not define the LM frame size the value of this object is ignored. This object can only be written at row creation time and cannot be modified once it has been created. [Y.1731] 9.3 DEFVAL { false ::= { mefsoamlmcfgentry 10 mefsoamlmcfgtesttlvpattern OBJECT-TYPE SYNTAX MefSoamTcTestPatternType This object specifies the type of test pattern to be sent in the LM frame Test TLV when the size of LM PDU is determined by the mefsoamlmframesize object and mefsoamlmtesttlvincluded is 'true'. If the frame size object does not define the LM frame size or mefsoamlmtesttlvincluded is 'false' the value of this object is ignored. This object can only be written at row creation time and cannot be modified once it has been created. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 42

1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 DEFVAL { null ::= { mefsoamlmcfgentry 11 mefsoamlmcfgmeasurementinterval OBJECT-TYPE (1..525600) UNITS minutes This object specifies the Measurement Interval for FLR statistics, in minutes. A Measurement Interval of 15 minutes needs to be supported, other intervals may be supported. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R16, R17, R110, R111, D46 DEFVAL { 15 ::= { mefsoamlmcfgentry 12 mefsoamlmcfgnumintervalsstored OBJECT-TYPE (2..1000) This object specifies the number of completed Measurement Intervals to store in the history statistic table (mefsoamlmhistorystatstable) and the history availability statistic table (mefsoamlmhistoryavailstatstable). At least 32 completed Measurement Intervals need to be stored. 96 Measurement Intervals are recommended to be stored. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R21, D8, D9 DEFVAL { 32 ::= { mefsoamlmcfgentry 13 mefsoamlmcfgdestmacaddress OBJECT-TYPE SYNTAX MacAddress The Target or Destination MAC Address Field to be transmitted. If mefsoamlmcfgtype is 'lmccm', the destination MAC address is always a multicast address indicating the level of the MEG: 01-80-c2-00-00-3y, where y is the level of the MEG. An error is returned if this object is set to any other value. If mefsoamlmcfgtype is 'lmlmm' or 'lmslm', the destination address is the unicast address of the destination MEP. An error is returned if this object is set to a multicast address. This address will be used if the value of the object mefsoamlmdestismepid is 'false'. This object is only valid for the entity transmitting the SOAM LM frames and is ignored by the entity receiving contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 43

1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 SOAM LM frames. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R70, R104 ::= { mefsoamlmcfgentry 14 mefsoamlmcfgdestmepid OBJECT-TYPE SYNTAX Dot1agCfmMepIdOrZero The Maintenance Association End Point Identifier of another MEP in the same Maintenance Association to which the SOAM LM frame is to be sent. This address will be used if the value of the column mefsoamlmdestismepid is 'true'. A value of zero means that the destination MEP ID has not been configured. This object is only valid for the entity transmitting the Loss Measurement frames, types 'lmlmm' and 'lmslm'. It is not applicable for the 'lmccm' type. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R70, R104 DEFVAL { 0 ::= { mefsoamlmcfgentry 15 mefsoamlmcfgdestismepid OBJECT-TYPE SYNTAX TruthValue A value of 'true' indicates that MEPID of the target MEP is used for SOAM LM frame transmission. A value of 'false' indicates that the MAC address of the target MEP is used for SOAM LM frame transmission. This object is only valid for the entity transmitting the Loss Measurement frames, types 'lmlmm' and 'lmslm'. It is not applicable for the 'lmccm' type. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R70, R104 DEFVAL { true ::= { mefsoamlmcfgentry 16 mefsoamlmcfgstarttimetype OBJECT-TYPE SYNTAX MefSoamTcOperationTimeType This object specifies the type of start time of the SOAM LM session. The start time can be disabled (none), immediate, relative, contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 44

1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 or fixed. The value of 'none' is illegal and a write error will be returned if this value is used. The value of 'immediate' starts the SOAM LM session when the mefsoamlmcfgenabled is true. The value of 'fixed' starts the SOAM LM session when the mefsoamlmfixedstartdateandtime is less than or equal to the current system date and time and mefsoamlmcfgenabled is true. This value is used to implement an On-Demand fixed time PM session. The value of 'relative' starts the SOAM LM session when the current system date and time minus the mefsoamlmrelativestarttime is greater than or equal to the system date and time when the mefsoamlmstarttimetype object was written and mefsoamlmcfgenabled is true. This value is used to implement an On-Demand relative time PM session. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R3, R7, R8, D1 DEFVAL { immediate ::= { mefsoamlmcfgentry 17 mefsoamlmcfgfixedstartdateandtime OBJECT-TYPE SYNTAX DateAndTime This object specifies the fixed start date/time for the SOAM Loss Measurement session. This object is used only used if mefsoamlmstarttimetype is 'fixed' and is ignored otherwise. The default value is year 0000, month 01, day 01, time 00:00:00.00. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R9 DEFVAL { '0000010100000000'H ::= { mefsoamlmcfgentry 18 mefsoamlmcfgrelativestarttime OBJECT-TYPE SYNTAX TimeInterval This object specifies the relative start time, from the current system time, for the SOAM LM session. This object is used only if mefsoamlmstarttimetype is 'relative' and is ignored otherwise. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R9 DEFVAL { 0 ::= { mefsoamlmcfgentry 19 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 45

1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 mefsoamlmcfgstoptimetype OBJECT-TYPE SYNTAX MefSoamTcOperationTimeType This object specifies the type of stop time to terminate the SOAM LM session. The stop time can be forever (none), relative, or fixed. The value of 'none' indicates that the SOAM LM session never ends once it has started unless it the session is disabled. The value of 'immediate' is illegal and a write error will be returned if this value is used. The value of 'fixed' stops the SOAM LM session when the mefsoamlmfixedstopdateandtime is less than or equal to the current system date and time. This value is used to implement an On-Demand fixed time PM session. The value of 'relative' stops the SOAM LM session when the time indicated by mefsoamlmrelativestoptime has passed since the session start time as determined by the mefsoamlmcfgstarttimetype, mefsoamlmcfgfixedstartdateandtime and mefsoamlmcfgrelativestarttime objects. This value is used to implement an On-Demand relative time PM session. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R3, R10, D2 DEFVAL { none ::= { mefsoamlmcfgentry 20 mefsoamlmcfgfixedstopdateandtime OBJECT-TYPE SYNTAX DateAndTime This object specifies the fixed stop date/time for the SOAM Loss Measurement session. This object is used only used if mefsoamlmstoptimetype is 'fixed' and is ignored otherwise. The default value is year 0000, month 01, day 01, time 00:00:00.00. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R10, R13 DEFVAL { '0000010100000000'H ::= { mefsoamlmcfgentry 21 mefsoamlmcfgrelativestoptime OBJECT-TYPE SYNTAX TimeInterval This object specifies the relative stop time, from the session start time, to stop the SOAM LM session. This object is used only if mefsoamlmstoptimetype is 'relative' and is ignored otherwise. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 46

1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R11 DEFVAL { 0 ::= { mefsoamlmcfgentry 22 mefsoamlmcfgrepetitiontime OBJECT-TYPE (0..31536000) UNITS seconds This object specifies a configurable repetition time between Measurement Intervals in a Loss Measurement session, in seconds. If the value is 0 (none), there is no time gap between the end of one Measurement Interval and the start of a new Measurement Interval. This is the normal usage case. If the value is greater than 0 but less than or equal to the measurement interval, an error is returned. If the value is greater than one Measurement Interval there is time gap between the end of one Measurement Interval and the start of the next Measurement Interval. The repetition time specifies the time between the start of consecutive Measurement Intervals; hence the gap between the end of one Measurement Interval and the start of the next is equal to the difference between the repetition time and the measurement interval. During this gap, no SOAM PDUs are sent for this session and no measurements are made. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R18, D3, R19, R20 DEFVAL { 0 ::= { mefsoamlmcfgentry 23 mefsoamlmcfgalignmeasurementintervals OBJECT-TYPE SYNTAX TruthValue This object specifies whether the Measurement Intervals for the Loss Measurement session are aligned with a zero offset to real time. The value 'true' indicates that each Measurement Interval starts at a time which is aligned to NE time source hour, if the repetition time (or the Measurement Interval, if the repetition time is 0) is a factor of an hour, i.e. 60min/15min = 4. For instance, a Measurement Interval/repetition time of 15 minutes would stop/start the Measurement Interval at 0, 15, 30, and 45 minutes of an hour. A Measurement Interval/Repetition Time of 7 minutes would not align to the hour since 7 minutes is NOT a factor of an hour, i.e. 60min/7min = 8.6. In this case the behavior is the same as if the object is set to 'false'. The value 'false' indicates that the first Measurement Interval starts at an arbitrary time and each subsequent Measurement Interval starts at a time which is determined by mefsoamlmcfgrepetitiontime. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 47

1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] D4, D5, D6 DEFVAL { true ::= { mefsoamlmcfgentry 24 mefsoamlmcfgalignmeasurementoffset OBJECT-TYPE (0..525600) UNITS minutes This object specifies the offset in minutes from the time of day value if mefsoamlmcfgalignmeasurementintervals is 'true' and the repetition time is a factor of 60 minutes. If not, the value of this object is ignored. If the Measurement Interval is 15 minutes and mefsoamlmcfgalignmeasurementintervals is true and if this object was set to 5 minutes, the Measurement Intervals would start at 5, 20, 35, 50 minutes past each hour. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] D7 DEFVAL { 0 ::= { mefsoamlmcfgentry 25 mefsoamlmcfgavailabilitymeasurementinterval OBJECT-TYPE (1..525600) UNITS minutes This object specifies the availability Measurement Interval in minutes. A Measurement Interval of 15 minutes is to be supported, other intervals can be supported. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R16, R17 DEFVAL { 15 ::= { mefsoamlmcfgentry 26 mefsoamlmcfgavailabilitynumconsecutivemeaspdus OBJECT-TYPE (1..1000000) This object specifies a configurable number of consecutive loss measurement PDUs to be used in evaluating the availability/unavailability status of each availability indicator per MEF 10.2.1. Loss Measurement PDUs (LMMs, CCMs or SLMs) are sent regularly with a period defined by mefsoamlmcfgmessageperiod. Therefore, this object, when contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 48

2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 multiplied by mefsoamlmcfgmessageperiod, is equivalent to the Availability parameter of 'delta_t' as specified by MEF 10.2.1. If the mefsoamlmcfgtype is lmlmm or lmccm, this object defines the number of LMM or CCM PDUs transmitted during each 'delta_t' period. The Availability flr for a given 'delta_t' can be calculated based on the counters in the last LMM/R or CCM during this 'delta_t' and the last LMM/R or CCM in the previous 'delta_t'. If the mefsoamlmcfgtype is lmslm, this object defines the number of SLM PDUs transmitted during each 'delta_t' period. The Availability flr for a given 'delta_t' is calculated based on the number of those SLM PDUs that are lost. If the mefsoamlmcfgtype is lmlmm or lmccm, the number range of 1 through 10 must be supported. The number range of 10 through 1000000 may be supported, but is not mandatory. If the mefsoamlmcfgtype is lmslm, the number range of 10 through 100 must be supported. The number range of 100 through 1000000 may be supported, but is not mandatory. This object can only be written at row creation time and cannot be modified once it has been created. [MEF 10.2.1] Section 7.9.8; [MEF SOAM-PM] R80, D33, R81 DEFVAL { 10 ::= { mefsoamlmcfgentry 27 mefsoamlmcfgavailabilityflrthreshold OBJECT-TYPE (0..100000) UNITS milli-percent This object specifies a configurable availability threshold to be used in evaluating the availability/unavailability status of an availability indicator per MEF 10.2.1. The availability threshold range of 0.00 (0) through 1.00 (100000) is supported. This parameter is equivalent to the Availability parameter of 'C' as specified by MEF 10.2.1. Units are in milli-percent, where 1 indicates 0.001 percent. This object can only be written at row creation time and cannot be modified once it has been created. [MEF 10.2.1] Section 7.9.8; [MEF SOAM-PM] R81, R82, D34 DEFVAL { 50000 ::= { mefsoamlmcfgentry 28 mefsoamlmcfgavailabilitynumconsecutiveintervals OBJECT-TYPE (1..1000) This object specifies a configurable number of consecutive availability indicators to be used to determine a change in the availability status as indicated by MEF 10.2.1. This parameter is equivalent to the Availability parameter of 'n' as specified by MEF 10.2.1. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 49

2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 The number range of 1 through 10 must be supported. The number range of 1 through 1000 may be supported, but is not mandatory. This object can only be written at row creation time and cannot be modified once it has been created. [MEF 10.2.1] Section 7.9.8; [MEF SOAM-PM] R80, D33 DEFVAL { 10 ::= { mefsoamlmcfgentry 29 mefsoamlmcfgavailabilitynumconsecutivehighflr OBJECT-TYPE (1..1000) This object specifies a configurable number of consecutive availability indicators to be used for assessing CHLI. This parameter is equivalent to the Resilency parameter of 'p' as specified by MEF 10.2.1. mefsoamlmcfgavailabilitynumconsecutivehighflr must be strictly less than mefsoamlmcfgavailabilitynumconsecutiveintervals. If not, the count of high loss intervals over time, mefsoamlmavailabilityhighloss, and the count of consecutive high loss levels, mefsoamlmavailabilityconsecutivehighloss, is disabled. The number range of 1 through 10 must be supported. The number range of 1 through 1000 may be supported, but is not mandatory. This object can only be written at row creation time and cannot be modified once it has been created. [MEF 10.2.1] Section 7.9.8; [MEF SOAM-PM] R86, D35, D36 DEFVAL { 5 ::= { mefsoamlmcfgentry 30 mefsoamlmcfgsessiontype OBJECT-TYPE SYNTAX MefSoamTcSessionType This object indicates whether the current session is defined to be 'Proactive' or 'On-Demand'. A value of 'proactive' indicates the current session is 'Proactive'. A value of 'ondemand' indicates the current session is 'On-Demand'. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R3 DEFVAL { proactive ::= { mefsoamlmcfgentry 31 mefsoamlmcfgsessionstatus OBJECT-TYPE SYNTAX MefSoamTcStatusType This object indicates the current status of the LM session. A value of 'active' indicates the current LM session is active, i.e. the current time lies between the start time and the stop time, and contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 50

2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 mefsoamlmcfgenabled is true. A value of 'notactive' indicates the current LM session is not active, i.e. it has not started yet, has stopped upon reaching the stop time, or is disabled. ::= { mefsoamlmcfgentry 32 mefsoamlmcfghistoryclear OBJECT-TYPE SYNTAX TruthValue This object when written clears the Loss Measurement history Table (mefsoamlmhistorystatstable) - all rows are deleted. When read the value always returns 'false'. Writing this value does not change the current stat table, nor any of the items in the configuration table. Writing this value during row creation has no effect. DEFVAL { false ::= { mefsoamlmcfgentry 33 mefsoamlmcfgrowstatus OBJECT-TYPE SYNTAX RowStatus The status of the row. The writable columns in a row cannot be changed if the row is active, except for mefsoamlmcfghistoryclear and mefsoamlmcfgenabled objects. All columns must have a valid value before a row can be activated. ::= { mefsoamlmcfgentry 34 -- ***************************************************************************** -- Ethernet Loss Measurement Measured Statistic Table -- ***************************************************************************** mefsoamlmmeasuredstatstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamLmMeasuredStatsEntry MAX-ACCESS not-accessible This object contains the last measured results for a SOAM Loss Measurement session. Each row in the table represents a Loss Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. Instances of this managed object are created automatically by the SNMP Agent when the Loss Measurement session is running. Each object in this table applies only if the corresponding bit is set in mefsoamlmcfgmeasurementenable. The objects in this table do not need to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R7, R15, 8D18 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 51

2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 ::= { mefsoampmlmobjects 2 mefsoamlmmeasuredstatsentry OBJECT-TYPE SYNTAX MefSoamLmMeasuredStatsEntry MAX-ACCESS not-accessible The conceptual row of mefsoamlmmeasuredstatstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamlmcfgindex ::= { mefsoamlmmeasuredstatstable 1 MefSoamLmMeasuredStatsEntry ::= SEQUENCE { mefsoamlmmeasuredstatsforwardflr Unsigned32, mefsoamlmmeasuredstatsbackwardflr Unsigned32, mefsoamlmmeasuredstatsavailforwardstatus MefSoamTcAvailabilityType, mefsoamlmmeasuredstatsavailbackwardstatus MefSoamTcAvailabilityType, mefsoamlmmeasuredstatsavailforwardlasttransitiontime DateAndTime, mefsoamlmmeasuredstatsavailbackwardlasttransitiontime DateAndTime mefsoamlmmeasuredstatsforwardflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the last frame loss ratio in the forward direction calculated by this MEP. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmmeasuredstatsentry 1 mefsoamlmmeasuredstatsbackwardflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the last frame loss ratio in the backward direction calculated by this MEP. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmmeasuredstatsentry 2 mefsoamlmmeasuredstatsavailforwardstatus OBJECT-TYPE SYNTAX MefSoamTcAvailabilityType contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 52

2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 This object indicates the availability status (the outcome of the last known availability indicator) in the forward direction. Note that the status of an availability indicator is not known until the loss for a number of subsequent availability indicators has been calculated (as determined by mefsoamlmcfgavailabilitynumconsecutiveintervals) [MEF SOAM-PM] R83 ::= { mefsoamlmmeasuredstatsentry 3 mefsoamlmmeasuredstatsavailbackwardstatus OBJECT-TYPE SYNTAX MefSoamTcAvailabilityType This object indicates the availability status (the outcome of the last availability indicator) in the backward direction. Note that the status of an availability indicator is not known until the loss for a number of subsequent availability indicators has been calculated (as determined by mefsoamlmcfgavailabilitynumconsecutiveintervals) [MEF SOAM-PM] R83 ::= { mefsoamlmmeasuredstatsentry 4 mefsoamlmmeasuredstatsavailforwardlasttransitiontime OBJECT-TYPE SYNTAX DateAndTime This object indicates the time of the last transition between available and unavailable in the forward direction. If there have been no transitions since the Loss Measurement Session was started, this is set to 0. [MEF SOAM-PM] R83 ::= { mefsoamlmmeasuredstatsentry 5 mefsoamlmmeasuredstatsavailbackwardlasttransitiontime OBJECT-TYPE SYNTAX DateAndTime This object indicates the time of the last transition between available and unavailable in the backward direction. If there have been no transitions since the Loss Measurement Session was started, this is set to 0. [MEF SOAM-PM] R83 ::= { mefsoamlmmeasuredstatsentry 6 -- ***************************************************************************** -- Ethernet Loss Measurement Current Availability Statistic Table -- ***************************************************************************** mefsoamlmcurrentavailstatstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamLmCurrentAvailStatsEntry MAX-ACCESS not-accessible contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 53

2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 This object contains the current results for a SOAM Loss Measurement session for availability statistics gathered during the interval indicated by mefsoamlmcfgavailabilitymeasurementinterval. Each row in the table represents a Loss Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. Instances of this managed object are created automatically by the SNMP Agent when the Loss Measurement session is running. The objects in this table apply regardless of the value of mefsoamlmcfgtype unless otherwise specified in the object description. Except for mefsoamlmcurrentavailstatsindex, mefsoamlmcurrentavailstatsstarttime, mefsoamlmcurrentavailstatselapsedtime and mefsoamlmcurrentavailstatssuspect, each object in this table applies only if the corresponding bit is set in mefsoamlmcfgmeasurementenable. The objects in this table may be persistent upon reboot or restart of a device. [MEF SOAM-PM] D9, D18 ::= { mefsoampmlmobjects 3 mefsoamlmcurrentavailstatsentry OBJECT-TYPE SYNTAX MefSoamLmCurrentAvailStatsEntry MAX-ACCESS not-accessible The conceptual row of mefsoamlmcurrentavailstatstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamlmcfgindex ::= { mefsoamlmcurrentavailstatstable 1 MefSoamLmCurrentAvailStatsEntry ::= SEQUENCE { mefsoamlmcurrentavailstatsindex mefsoamlmcurrentavailstatsstarttime mefsoamlmcurrentavailstatselapsedtime mefsoamlmcurrentavailstatssuspect Unsigned32, DateAndTime, TimeInterval, TruthValue, mefsoamlmcurrentavailstatsforwardhighloss Unsigned32, mefsoamlmcurrentavailstatsbackwardhighloss Unsigned32, mefsoamlmcurrentavailstatsforwardconsecutivehighloss Unsigned32, mefsoamlmcurrentavailstatsbackwardconsecutivehighloss Unsigned32, mefsoamlmcurrentavailstatsforwardavailable Gauge32, mefsoamlmcurrentavailstatsbackwardavailable Gauge32, mefsoamlmcurrentavailstatsforwardunavailable Gauge32, mefsoamlmcurrentavailstatsbackwardunavailable Gauge32, mefsoamlmcurrentavailstatsforwardminflr Unsigned32, mefsoamlmcurrentavailstatsforwardmaxflr Unsigned32, mefsoamlmcurrentavailstatsforwardavgflr Unsigned32, mefsoamlmcurrentavailstatsbackwardminflr Unsigned32, mefsoamlmcurrentavailstatsbackwardmaxflr Unsigned32, mefsoamlmcurrentavailstatsbackwardavgflr Unsigned32 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 54

2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 mefsoamlmcurrentavailstatsindex OBJECT-TYPE The index for the current availability Measurement Interval for this PM session. This value will become the value for mefsoamlmhistoryavailstatsindex once the Measurement Interval is completed. The duration of the Measurement Interval is specified by mefsoamlmcfgavailabilitymeasurementinterval. Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1. ::= { mefsoamlmcurrentavailstatsentry 1 mefsoamlmcurrentavailstatsstarttime OBJECT-TYPE SYNTAX DateAndTime The time that the current Measurement Interval started. [MEF SOAM-PM] R87, R112 ::= { mefsoamlmcurrentavailstatsentry 2 mefsoamlmcurrentavailstatselapsedtime OBJECT-TYPE SYNTAX TimeInterval The time that the current Measurement Interval has been running, in 0.01 seconds. [MEF SOAM-PM] R24, R87, R112 ::= { mefsoamlmcurrentavailstatsentry 3 mefsoamlmcurrentavailstatssuspect OBJECT-TYPE SYNTAX TruthValue Whether the Measurement Interval has been marked as suspect. The object is set to false at the start of a measurement interval. It is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following: 1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service [MEF SOAM-PM] R39, R40, R41 ::= { mefsoamlmcurrentavailstatsentry 4 mefsoamlmcurrentavailstatsforwardhighloss OBJECT-TYPE contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 55

2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 This object is the number of high loss intervals (HLI) over time in the forward direction. The value starts at 0 and increments for every HLI that occurs. This parameter is equivalent to 'L Sub T' found in MEF 10.2.1. [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87 ::= { mefsoamlmcurrentavailstatsentry 5 mefsoamlmcurrentavailstatsbackwardhighloss OBJECT-TYPE This object is the number of high loss intervals (HLI) over time in the backwards direction. The value starts at 0 and increments for every HLI that occurs. This parameter is equivalent to 'L Sub T' found in MEF 10.2.1. [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87 ::= { mefsoamlmcurrentavailstatsentry 6 mefsoamlmcurrentavailstatsforwardconsecutivehighloss OBJECT-TYPE This object is the number of consecutive high loss intervals (CHLI) over time in the forward direction. The value starts at 0 and increments for every HLI that occurs that is determined to fall within a CHLI. This parameter is equivalent to 'B Sub T' found in MEF 10.2.1. [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87 ::= { mefsoamlmcurrentavailstatsentry 7 mefsoamlmcurrentavailstatsbackwardconsecutivehighloss OBJECT-TYPE This object is the number of consecutive high loss intervals (CHLI) over time in the backward direction. The value starts at 0 and increments for every HLI that occurs that is determined to fall within a CHLI. This parameter is equivalent to 'B Sub T' found in MEF 10.2.1. [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87 ::= { mefsoamlmcurrentavailstatsentry 8 mefsoamlmcurrentavailstatsforwardavailable OBJECT-TYPE SYNTAX Gauge32 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 56

2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 This object contains the number of availability indicators evaluated as available in the forward direction by this MEP during this Measurement Interval. [MEF SOAM-PM] R87; [MEF 10.2.1] ::= { mefsoamlmcurrentavailstatsentry 9 mefsoamlmcurrentavailstatsbackwardavailable OBJECT-TYPE SYNTAX Gauge32 This object contains the number of availability indicators evaluated as available in the backward direction by this MEP during this Measurement Interval. [MEF SOAM-PM] R87 ::= { mefsoamlmcurrentavailstatsentry 10 mefsoamlmcurrentavailstatsforwardunavailable OBJECT-TYPE SYNTAX Gauge32 This object contains the number of availability indicators evaluated as unavailable in the forward direction by this MEP during this Measurement Interval. [MEF SOAM-PM] R87 ::= { mefsoamlmcurrentavailstatsentry 11 mefsoamlmcurrentavailstatsbackwardunavailable OBJECT-TYPE SYNTAX Gauge32 This object contains the number of availability indicators evaluated as unavailable in the backward direction by this MEP during this Measurement Interval. [MEF SOAM-PM] R87 ::= { mefsoamlmcurrentavailstatsentry 12 mefsoamlmcurrentavailstatsforwardminflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the minimum one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 57

2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentavailstatsentry 13 mefsoamlmcurrentavailstatsforwardmaxflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the maximum one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentavailstatsentry 14 mefsoamlmcurrentavailstatsforwardavgflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the average one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentavailstatsentry 15 mefsoamlmcurrentavailstatsbackwardminflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the minimum one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 58

2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentavailstatsentry 16 mefsoamlmcurrentavailstatsbackwardmaxflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the maximum one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentavailstatsentry 17 mefsoamlmcurrentavailstatsbackwardavgflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the average one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentavailstatsentry 18 -- ***************************************************************************** -- Ethernet Loss Measurement Current Statistic Table -- ***************************************************************************** mefsoamlmcurrentstatstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamLmCurrentStatsEntry MAX-ACCESS not-accessible This table contains the results for the current Measurement Interval in a SOAM Loss Measurement session gathered during the interval indicated by mefsoamlmcfgmeasurementinterval. A row in this table is created automatically by the SNMP Agent when the Loss Measurement session is configured. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 59

2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 Each row in the table represents the current statistics for a Loss Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. There may be more than one LM session per MEP. The main use case for this is to allow multiple CoS instances to be operating simultaneously for a MEP. The objects in this table apply regardless of the value of mefsoamlmcfgtype unless otherwise specified in the object description. Except for mefsoamlmcurrentstatsindex, mefsoamlmcurrentstatsstarttime, mefsoamlmcurrentstatselapsedtime and mefsoamlmcurrentstatssuspect, each object in this table applies only if the corresponding bit is set in mefsoamlmcfgmeasurementenable. The objects in this table do not need to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R7, R15, D9, D18 ::= { mefsoampmlmobjects 4 mefsoamlmcurrentstatsentry OBJECT-TYPE SYNTAX MefSoamLmCurrentStatsEntry MAX-ACCESS not-accessible The conceptual row of mefsoamlmcurrentstatstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamlmcfgindex ::= { mefsoamlmcurrentstatstable 1 MefSoamLmCurrentStatsEntry ::= SEQUENCE { mefsoamlmcurrentstatsindex Unsigned32, mefsoamlmcurrentstatsstarttime DateAndTime, mefsoamlmcurrentstatselapsedtime TimeInterval, mefsoamlmcurrentstatssuspect TruthValue, mefsoamlmcurrentstatsforwardtransmittedframes Gauge32, mefsoamlmcurrentstatsforwardreceivedframes Gauge32, mefsoamlmcurrentstatsforwardminflr Unsigned32, mefsoamlmcurrentstatsforwardmaxflr Unsigned32, mefsoamlmcurrentstatsforwardavgflr Unsigned32, mefsoamlmcurrentstatsbackwardtransmittedframes Gauge32, mefsoamlmcurrentstatsbackwardreceivedframes Gauge32, mefsoamlmcurrentstatsbackwardminflr Unsigned32, mefsoamlmcurrentstatsbackwardmaxflr Unsigned32, mefsoamlmcurrentstatsbackwardavgflr Unsigned32, mefsoamlmcurrentstatssoampdussent Gauge32, mefsoamlmcurrentstatssoampdusreceived Gauge32 mefsoamlmcurrentstatsindex OBJECT-TYPE The index for the current Measurement Interval for this PM session. This value will become the value for contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 60

2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 mefsoamlmhistorystatsindex once the Measurement Interval is completed. Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1. ::= { mefsoamlmcurrentstatsentry 1 mefsoamlmcurrentstatsstarttime OBJECT-TYPE SYNTAX DateAndTime The time that the current Measurement Interval started. [MEF SOAM-PM] R22, R87, R112 ::= { mefsoamlmcurrentstatsentry 2 mefsoamlmcurrentstatselapsedtime OBJECT-TYPE SYNTAX TimeInterval The time that the current Measurement Interval has been running, in 0.01 seconds. [MEF SOAM-PM] R24, R87, R112 ::= { mefsoamlmcurrentstatsentry 3 mefsoamlmcurrentstatssuspect OBJECT-TYPE SYNTAX TruthValue Whether the Measurement Interval has been marked as suspect. The object is set to false at the start of a measurement interval. It is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following: 1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service [MEF SOAM-PM] R39, R40, R41 ::= { mefsoamlmcurrentstatsentry 4 mefsoamlmcurrentstatsforwardtransmittedframes OBJECT-TYPE SYNTAX Gauge32 This object contains the number of frames transmitted in the forward direction by this MEP. For a PM Session of types lmlmm and lmccm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 61

2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 For a PM Session of type lmslm this includes the count of SOAM ETH-SLM frames only. [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmcurrentstatsentry 5 mefsoamlmcurrentstatsforwardreceivedframes OBJECT-TYPE SYNTAX Gauge32 This object contains the number of frames received in the forward direction by this MEP. For a PM Session of types lmlmm and lmccm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only. For a PM Session of types lmslm this includes the count of SOAM ETH-SLM frames only. [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmcurrentstatsentry 6 mefsoamlmcurrentstatsforwardminflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the minimum one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentstatsentry 7 mefsoamlmcurrentstatsforwardmaxflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the maximum one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentstatsentry 8 mefsoamlmcurrentstatsforwardavgflr OBJECT-TYPE (0..100000) UNITS milli-percent contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 62

2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 This object contains the average one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentstatsentry 9 mefsoamlmcurrentstatsbackwardtransmittedframes OBJECT-TYPE SYNTAX Gauge32 This object contains the number of frames transmitted in the backward direction by this MEP. For a PM Session of type lmlmm and lmccm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only. For a PM Session of type lmslm this includes the count of SOAM ETH-SLM frames only. [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmcurrentstatsentry 10 mefsoamlmcurrentstatsbackwardreceivedframes OBJECT-TYPE SYNTAX Gauge32 This object contains the number of frames received in the backward direction by this MEP. For a PM Session of type lmlmm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only. For a PM Session of type lmslm this includes the count of SOAM ETH-SLM frames only. [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmcurrentstatsentry 11 mefsoamlmcurrentstatsbackwardminflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the minimum one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentstatsentry 12 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 63

3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 mefsoamlmcurrentstatsbackwardmaxflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the maximum one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentstatsentry 13 mefsoamlmcurrentstatsbackwardavgflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the average one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmcurrentstatsentry 14 mefsoamlmcurrentstatssoampdussent OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of SOAM PDUs sent during this Measurement Interval. This object applies when mefsoamlmcfgtype is lmlmm, lmslm, or lmccm. It indicates the number of LMM, CCM, or SLM SOAM frames transmitted. [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmcurrentstatsentry 15 mefsoamlmcurrentstatssoampdusreceived OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of SOAM PDUs PDUs received in this Measurement Interval. This object applies when mefsoamlmcfgtype is lmlmm, lmslm, or lmccm. This object indicates the number of LMR, CCM, or SLR SOAM frames received. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 64

3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmcurrentstatsentry 16 -- ***************************************************************************** -- Ethernet Loss Measurement Availability History Statistic Table -- ***************************************************************************** mefsoamlmhistoryavailstatstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamLmHistoryAvailStatsEntry MAX-ACCESS not-accessible This table contains the results for availability history Measurement Intervals in a SOAM Loss Measurement session. Rows of this table object are created automatically by the SNMP Agent when the Loss Measurement session is running and a Measurement Interval is completed. Each row in the table represents the history statistics for a Loss Measurement session availability Measurement Interval for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. The fifth index index the specific Measurement Interval. At least 32 completed Measurement Intervals are to be supported. 96 completed Measurement Intervals are recommended to be supported. If there are at least 32 rows in the table and a new Measurement Interval completes and a new row is to be added to the table, the oldest completed Measurement Interval can be deleted (row deletion). If the availability Measurement Interval is other than 15 minutes then a minimum of 8 hours of completed Measurement Intervals are to be supported and 24 hours are recommended to be supported. Except for mefsoamlmhistoryavailstatsindex, mefsoamlmhistoryavailstatsendtime, mefsoamlmhistoryavailstatselapsedtime and mefsoamlmhistoryavailstatssuspect, each object in this table applies only if the corresponding bit is set in mefsoamlmcfgmeasurementenable. The rows and objects in this table are to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R7, R15, R21, D8, R25 ::= { mefsoampmlmobjects 5 mefsoamlmhistoryavailstatsentry OBJECT-TYPE SYNTAX MefSoamLmHistoryAvailStatsEntry MAX-ACCESS not-accessible The conceptual row of mefsoamlmhistoryavailstatstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamlmcfgindex, mefsoamlmhistoryavailstatsindex ::= { mefsoamlmhistoryavailstatstable 1 MefSoamLmHistoryAvailStatsEntry ::= SEQUENCE { mefsoamlmhistoryavailstatsindex Unsigned32, contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 65

3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 mefsoamlmhistoryavailstatsendtime DateAndTime, mefsoamlmhistoryavailstatselapsedtime TimeInterval, mefsoamlmhistoryavailstatssuspect TruthValue, mefsoamlmhistoryavailstatsforwardhighloss Unsigned32, mefsoamlmhistoryavailstatsbackwardhighloss Unsigned32, mefsoamlmhistoryavailstatsforwardconsecutivehighloss Unsigned32, mefsoamlmhistoryavailstatsbackwardconsecutivehighloss Unsigned32, mefsoamlmhistoryavailstatsforwardavailable mefsoamlmhistoryavailstatsbackwardavailable mefsoamlmhistoryavailstatsforwardunavailable mefsoamlmhistoryavailstatsbackwardunavailable mefsoamlmhistoryavailstatsforwardminflr mefsoamlmhistoryavailstatsforwardmaxflr mefsoamlmhistoryavailstatsforwardavgflr mefsoamlmhistoryavailstatsbackwardminflr mefsoamlmhistoryavailstatsbackwardmaxflr mefsoamlmhistoryavailstatsbackwardavgflr Gauge32, Gauge32, Gauge32, Gauge32, Unsigned32, Unsigned32, Unsigned32, Unsigned32, Unsigned32, Unsigned32 mefsoamlmhistoryavailstatsindex OBJECT-TYPE MAX-ACCESS not-accessible The index for the availability Measurement Interval within this PM session. Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1. Measurement Intervals for availability (stored in this table) are based on mefsoamlmcfgavailabilitymeasurementinterval and are indexed independently of Measurement Intervals for FLR (stored in mefsoamlmhistorystatstable). Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused while this session is active until it wraps to zero. The index value keeps increasing up to that time. ::= { mefsoamlmhistoryavailstatsentry 1 mefsoamlmhistoryavailstatsendtime OBJECT-TYPE SYNTAX DateAndTime The time that the Measurement Interval ended. [MEF SOAM-PM] R23, R87, R112 ::= { mefsoamlmhistoryavailstatsentry 2 mefsoamlmhistoryavailstatselapsedtime OBJECT-TYPE SYNTAX TimeInterval The length of time that the Measurement Interval ran for, in 0.01 seconds. [MEF SOAM-PM] R24, R87, R112 ::= { mefsoamlmhistoryavailstatsentry 3 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 66

3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 mefsoamlmhistoryavailstatssuspect OBJECT-TYPE SYNTAX TruthValue Whether the Measurement Interval has been marked as suspect. The object is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following: 1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service [MEF SOAM-PM] R39, R40, R41, R42 ::= { mefsoamlmhistoryavailstatsentry 4 mefsoamlmhistoryavailstatsforwardhighloss OBJECT-TYPE This object is the number of high loss intervals (HLI) over time in the forward direction. The value starts at 0 and increments for every HLI that occurs. This parameter is equivalent to 'L Sub T' found in MEF 10.2.1. [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87 ::= { mefsoamlmhistoryavailstatsentry 5 mefsoamlmhistoryavailstatsbackwardhighloss OBJECT-TYPE This object is the number of high loss intervals (HLI) over time in the backward direction. The value starts at 0 and increments for every HLI that occurs. This parameter is equivalent to 'L Sub T' found in MEF 10.2.1. [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87 ::= { mefsoamlmhistoryavailstatsentry 6 mefsoamlmhistoryavailstatsforwardconsecutivehighloss OBJECT-TYPE This object is the number of consecutive high loss intervals (CHLI) over time in the forward direction. The value starts at 0 and increments for every HLI that occurs that is determined to fall within a CHLI. This parameter is equivalent to 'B Sub T' found in MEF 10.2.1. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 67

3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87 ::= { mefsoamlmhistoryavailstatsentry 7 mefsoamlmhistoryavailstatsbackwardconsecutivehighloss OBJECT-TYPE This object is the number of consecutive high loss intervals (CHLI) over time in the forward direction. The value starts at 0 and increments for every HLI that occurs that is determined to fall within a CHLI. This parameter is equivalent to 'B Sub T' found in MEF 10.2.1. [MEF 10.2.1] 6.9.9; [MEF SOAM-PM] R87 ::= { mefsoamlmhistoryavailstatsentry 8 mefsoamlmhistoryavailstatsforwardavailable OBJECT-TYPE SYNTAX Gauge32 This object contains the number of availability indicators evaluated as available in the forward direction by this MEP during this Measurement Interval. [MEF SOAM-PM] R87; [MEF 10.2.1] ::= { mefsoamlmhistoryavailstatsentry 9 mefsoamlmhistoryavailstatsbackwardavailable OBJECT-TYPE SYNTAX Gauge32 This object contains the number of availability indicators evaluated as available in the backward direction by this MEP during this Measurement Interval. [MEF SOAM-PM] R87 ::= { mefsoamlmhistoryavailstatsentry 10 mefsoamlmhistoryavailstatsforwardunavailable OBJECT-TYPE SYNTAX Gauge32 This object contains the number of availability indicators evaluated as unavailable in the forward direction by this MEP during this Measurement Interval. [MEF SOAM-PM] R87 ::= { mefsoamlmhistoryavailstatsentry 11 mefsoamlmhistoryavailstatsbackwardunavailable OBJECT-TYPE SYNTAX Gauge32 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 68

3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 This object contains the number of availability indicators evaluated as unavailable in the backward direction by this MEP during this Measurement Interval. [MEF SOAM-PM] R87 ::= { mefsoamlmhistoryavailstatsentry 12 mefsoamlmhistoryavailstatsforwardminflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the minimum one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistoryavailstatsentry 13 mefsoamlmhistoryavailstatsforwardmaxflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the maximum one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistoryavailstatsentry 14 mefsoamlmhistoryavailstatsforwardavgflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the average one-way availability flr in the forward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 69

3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistoryavailstatsentry 15 mefsoamlmhistoryavailstatsbackwardminflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the minimum one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistoryavailstatsentry 16 mefsoamlmhistoryavailstatsbackwardmaxflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the maximum one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistoryavailstatsentry 17 mefsoamlmhistoryavailstatsbackwardavgflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the average one-way availability flr in the backward direction, from among the set of availability flr values calculated by the MEP in this Measurement Interval. There is one availability flr value for each delta_t time period within the Measurement Interval, as specified in MEF 10.2.1. The flr value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 70

3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistoryavailstatsentry 18 -- ***************************************************************************** -- Ethernet Loss Measurement Loss History Statistic Table -- ***************************************************************************** mefsoamlmhistorystatstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamLmHistoryStatsEntry MAX-ACCESS not-accessible This table contains the results for history Measurement Intervals in a SOAM Loss Measurement session. Rows of this table object are created automatically by the SNMP Agent when the Loss Measurement session is running and a Measurement Interval is completed. Each row in the table represents the history statistics for a Loss Measurement session Measurement Interval for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. The fifth index index the specific Measurement Interval. At least 32 completed Measurement Intervals are to be supported. 96 completed Measurement Intervals are recommended to be supported. If there are at least 32 rows in the table and a new Measurement Interval completes and a new row is to be added to the table, the oldest completed Measurement Interval may be deleted (row deletion). If the measurement interval is other than 15 minutes then a minimum of 8 hours of completed Measurement Intervals are to be supported and 24 hours are recommended to be supported. Except for mefsoamlmhistorystatsindex, mefsoamlmhistorystatsendtime, mefsoamlmhistorystatselapsedtime and mefsoamlmhistorystatssuspect, each object in this table applies only if the corresponding bit is set in mefsoamlmcfgmeasurementenable. The rows and objects in this table are to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R7, R15, R21, D8, R25 ::= { mefsoampmlmobjects 6 mefsoamlmhistorystatsentry OBJECT-TYPE SYNTAX MefSoamLmHistoryStatsEntry MAX-ACCESS not-accessible The conceptual row of mefsoamlmhistorystatstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamlmcfgindex, mefsoamlmhistorystatsindex contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 71

3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 ::= { mefsoamlmhistorystatstable 1 MefSoamLmHistoryStatsEntry ::= SEQUENCE { mefsoamlmhistorystatsindex Unsigned32, mefsoamlmhistorystatsendtime DateAndTime, mefsoamlmhistorystatselapsedtime TimeInterval, mefsoamlmhistorystatssuspect TruthValue, mefsoamlmhistorystatsforwardtransmittedframes Gauge32, mefsoamlmhistorystatsforwardreceivedframes Gauge32, mefsoamlmhistorystatsforwardminflr Unsigned32, mefsoamlmhistorystatsforwardmaxflr Unsigned32, mefsoamlmhistorystatsforwardavgflr Unsigned32, mefsoamlmhistorystatsbackwardtransmittedframes Gauge32, mefsoamlmhistorystatsbackwardreceivedframes Gauge32, mefsoamlmhistorystatsbackwardminflr Unsigned32, mefsoamlmhistorystatsbackwardmaxflr Unsigned32, mefsoamlmhistorystatsbackwardavgflr Unsigned32, mefsoamlmhistorystatssoampdussent Gauge32, mefsoamlmhistorystatssoampdusreceived Gauge32 mefsoamlmhistorystatsindex OBJECT-TYPE MAX-ACCESS not-accessible The index for the Measurement Interval within this PM session. Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1. Measurement Intervals for FLR (stored in this table) are based on mefsoamlmcfgmeasurementinterval and are indexed independently of Measurement Intervals for availability (stored in mefsoamlmhistoryavailstatstable). Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused while this session is active until it wraps to zero. The index value keeps increasing up to that time. ::= { mefsoamlmhistorystatsentry 1 mefsoamlmhistorystatsendtime OBJECT-TYPE SYNTAX DateAndTime The time that the Measurement Interval ended. [MEF SOAM-PM] R23, R87, R112 ::= { mefsoamlmhistorystatsentry 2 mefsoamlmhistorystatselapsedtime OBJECT-TYPE SYNTAX TimeInterval The length of time that the Measurement Interval ran for, in 0.01 seconds. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 72

3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 [MEF SOAM-PM] R24, R87, R112 ::= { mefsoamlmhistorystatsentry 3 mefsoamlmhistorystatssuspect OBJECT-TYPE SYNTAX TruthValue Whether the Measurement Interval has been marked as suspect. The object is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following: 1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service [MEF SOAM-PM] R39, R40, R41, R42 ::= { mefsoamlmhistorystatsentry 4 mefsoamlmhistorystatsforwardtransmittedframes OBJECT-TYPE SYNTAX Gauge32 This object contains the number of frames transmitted in the forward direction by this MEP. For a PM Session of types lmlmm and lmccm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only. For a PM Session of type lmslm this includes the count of OAM ETH-SLM frames only. [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmhistorystatsentry 5 mefsoamlmhistorystatsforwardreceivedframes OBJECT-TYPE SYNTAX Gauge32 This object contains the number of frames received in the forward direction by this MEP. For a PM Session of types lmlmm and lmccm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only. For a PM Session of type lmslm this includes the count of OAM ETH-SLM frames only. [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmhistorystatsentry 6 mefsoamlmhistorystatsforwardminflr OBJECT-TYPE (0..100000) UNITS milli-percent contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 73

3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 This object contains the minimum one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistorystatsentry 7 mefsoamlmhistorystatsforwardmaxflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the maximum one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistorystatsentry 8 mefsoamlmhistorystatsforwardavgflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the average one-way frame loss ratio in the forward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistorystatsentry 9 mefsoamlmhistorystatsbackwardtransmittedframes OBJECT-TYPE SYNTAX Gauge32 This object contains the number of frames transmitted in the backward direction by this MEP. For a PM Session of type lmlmm and lmccm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only. For a PM Session of types lmslm this includes the count of SOAM ETH-SLM frames only. [MEF SOAM-PM] D37 ::= { mefsoamlmhistorystatsentry 10 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 74

3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 mefsoamlmhistorystatsbackwardreceivedframes OBJECT-TYPE SYNTAX Gauge32 This object contains the number of frames received in the backward direction by this MEP. For a PM Session of type lmlmm and lmccm this includes Ethernet Service Frames and SOAM PDUs that are in a higher MEG level only. For a PM Session of types lmslm this includes the count of SOAM ETH-SLM frames only. [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmhistorystatsentry 11 mefsoamlmhistorystatsbackwardminflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the minimum one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] R69, R87, R112 ::= { mefsoamlmhistorystatsentry 12 mefsoamlmhistorystatsbackwardmaxflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the maximum one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. [MEF SOAM-PM] D37 ::= { mefsoamlmhistorystatsentry 13 mefsoamlmhistorystatsbackwardavgflr OBJECT-TYPE (0..100000) UNITS milli-percent This object contains the average one-way frame loss ratio in the backward direction calculated by this MEP for this Measurement Interval. The FLR value is a ratio that is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00). Units are in milli-percent, where 1 indicates 0.001 percent. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 75

3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 [MEF SOAM-PM] D37 ::= { mefsoamlmhistorystatsentry 14 mefsoamlmhistorystatssoampdussent OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of SOAM PDUs sent during this Measurement Interval. This object applies when mefsoamlmcfgtype is lmlmm, lmslm, or lmccm. It indicates the number of LMM, CCM, or SLM SOAM frames transmitted. [MEF SOAM-PM] R69, R87 ::= { mefsoamlmhistorystatsentry 15 mefsoamlmhistorystatssoampdusreceived OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of SOAM PDUs received in this Measurement Interval. This object applies when mefsoamlmcfgtype is lmlmm, lmslm, or lmccm. This object indicates the number of LMR, CCM, or SLR SOAM frames received. [MEF SOAM-PM] R69, R87 ::= { mefsoamlmhistorystatsentry 16 -- ***************************************************************************** -- Ethernet Delay Measurement Configuration Table -- ***************************************************************************** mefsoamdmcfgtable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamDmCfgEntry MAX-ACCESS not-accessible This table includes configuration objects and operations for the Delay Measurement function. Each row in the table represents a Delay Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. A Delay Measurement session is created on an existing MEP by first accessing the mefsoamdmopernextindex object and using this value as the mefsoamdmcfgindex in the row creation. Some writable objects in this table are only applicable in certain cases (as described under each object), and attempts to write values for them in other cases will be ignored. The writable objects in this table need to be persistent upon reboot or restart of a device. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 76

3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 [MEF SOAM-PM] R50; [Y.1731] ::= { mefsoampmdmobjects 1 mefsoamdmcfgentry OBJECT-TYPE SYNTAX MefSoamDmCfgEntry MAX-ACCESS not-accessible The conceptual row of mefsoamdmcfgtable. INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamdmcfgindex ::= { mefsoamdmcfgtable 1 MefSoamDmCfgEntry ::= SEQUENCE { mefsoamdmcfgindex mefsoamdmcfgtype mefsoamdmcfgversion mefsoamdmcfgenabled mefsoamdmcfgmeasurementenable mefsoamdmcfgmessageperiod mefsoamdmcfgpriority mefsoamdmcfgframesize mefsoamdmcfgdatapattern mefsoamdmcfgtesttlvincluded mefsoamdmcfgtesttlvpattern mefsoamdmcfgmeasurementinterval mefsoamdmcfgnumintervalsstored mefsoamdmcfgdestmacaddress mefsoamdmcfgdestmepid mefsoamdmcfgdestismepid mefsoamdmcfgsourcemacaddress mefsoamdmcfgstarttimetype mefsoamdmcfgfixedstartdateandtime mefsoamdmcfgrelativestarttime mefsoamdmcfgstoptimetype mefsoamdmcfgfixedstopdateandtime mefsoamdmcfgrelativestoptime mefsoamdmcfgrepetitiontime Unsigned32, INTEGER, Unsigned32, TruthValue, BITS, MefSoamTcMeasurementPeriodType, IEEE8021PriorityValue, Unsigned32, MefSoamTcDataPatternType, TruthValue, MefSoamTcTestPatternType, Unsigned32, Unsigned32, MacAddress, Dot1agCfmMepIdOrZero, TruthValue, MacAddress, mefsoamdmcfgalignmeasurementintervals TruthValue, mefsoamdmcfgalignmeasurementoffset Unsigned32, mefsoamdmcfgnummeasbinsperframedelayinterval Unsigned32, mefsoamdmcfgnummeasbinsperinterframedelayvariationinterval Unsigned32, mefsoamdmcfginterframedelayvariationselectionoffset Unsigned32, mefsoamdmcfgnummeasbinsperframedelayrangeinterval Unsigned32, mefsoamdmcfgsessiontype mefsoamdmcfgsessionstatus mefsoamdmcfghistoryclear mefsoamdmcfgrowstatus mefsoamdmcfgindex MefSoamTcOperationTimeType, DateAndTime, TimeInterval, MefSoamTcOperationTimeType, DateAndTime, TimeInterval, Unsigned32, MefSoamTcSessionType, MefSoamTcStatusType, TruthValue, RowStatus contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 77

3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 OBJECT-TYPE (1..4294967295) MAX-ACCESS not-accessible An index to the Delay Measurement Configuration table which indicates the specific measurement session for the MEP. mefsoampmmepopernextindex needs to be inspected to find an available index for row-creation. Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused for other PM sessions on the same MEP while this session is active. The index value keeps increasing until it wraps to zero. This is to facilitate access control based on a fixed index for an EMS, since the index is not reused. ::= { mefsoamdmcfgentry 1 mefsoamdmcfgtype OBJECT-TYPE SYNTAX INTEGER { dmdmm (1), dm1dmtx (2), dm1dmrx (3) This object indicates what type of Delay Measurement is to be performed. dmdmm(1) dm1dmtx(2) dm1dmrx(3) DMM SOAM PDU generated, DMR responses received (one-way or two-way measurements) 1DM SOAM PDU generated (one-way measurements are made by the receiver) 1DM SOAM PDU received and tracked (one-way measurements) The exact PDUs to use are specified by this object in combination with mefsoamdmcfgversion. The value dmdmm is required. The values dm1dmtx and dm1dmrx are optional. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R52, R53, R54, O5, R88 ::= { mefsoamdmcfgentry 2 mefsoamdmcfgversion OBJECT-TYPE This object indicates the version of the PDUs used to perform Delay Measurement. Version 0 indicates the PDU formats defined in Y.1731-2008. Version 1 indicates the PDU formats defined in Y.1731-2011. The exact PDUs to use are specified by this object in combination with mefsoamdmcfgtype. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 78

3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 This object can only be written at row creation time and cannot be modified once it has been created. [Y.1731] DEFVAL { 0 ::= { mefsoamdmcfgentry 3 mefsoamdmcfgenabled OBJECT-TYPE SYNTAX TruthValue This object specifies whether the Delay Measurement session is enabled. The value 'true' indicates the Delay Measurement session is enabled AND SOAM PDUs are sent and/or measurements are collected when the session is running according to the scheduling objects (start time, stop time, etc.). The value 'false' indicates the Delay Measurement session is disabled AND SOAM PDUs are not sent and/or measurements collected. For a Delay Measurement session to be removed the row is deleted in order to release internal resources. This object can written/modified after row creation time. If the DM session is enabled it resumes after shutdown/restart. If the DM session is disabled the current Measurement Interval is stopped, if it in process at the time, and all the in process calculations for the partially completed Measurement Interval are finalized. This object does not affect whether the single-ended Responder is enabled or not, which is enabled or disabled by the mefsoampmmepdmsingleendedresponder object. [MEF SOAM-PM] R4, R5, R6, O1, R12, R14 DEFVAL { true ::= { mefsoamdmcfgentry 4 mefsoamdmcfgmeasurementenable OBJECT-TYPE SYNTAX BITS { bsoampdussent(0), bsoampdusreceived(1), bframedelaytwowaybins(2), bframedelaytwowaymin(3), bframedelaytwowaymax(4), bframedelaytwowayavg(5), bframedelayforwardbins(6), bframedelayforwardmin(7), bframedelayforwardmax(8), bframedelayforwardavg(9), bframedelaybackwardbins(10), bframedelaybackwardmin(11), bframedelaybackwardmax(12), bframedelaybackwardavg(13), bifdvforwardbins(14), bifdvforwardmin(15), bifdvforwardmax(16), bifdvforwardavg(17), contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 79

4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 bifdvbackwardbins(18), bifdvbackwardmin(19), bifdvbackwardmax(20), bifdvbackwardavg(21), bifdvtwowaybins(22), bifdvtwowaymin(23), bifdvtwowaymax(24), bifdvtwowayavg(25), bframedelayrangeforwardbins(26), bframedelayrangeforwardmax(27), bframedelayrangeforwardavg(28), bframedelayrangebackwardbins(29), bframedelayrangebackwardmax(30), bframedelayrangebackwardavg(31), bframedelayrangetwowaybins(32), bframedelayrangetwowaymax(33), bframedelayrangetwowayavg(34), bmeasuredstatsframedelaytwoway(35), bmeasuredstatsframedelayforward(36), bmeasuredstatsframedelaybackward(37), bmeasuredstatsifdvtwoway(38), bmeasuredstatsifdvforward(39), bmeasuredstatsifdvbackward(40) A vector of bits that indicates the type of SOAM DM counters that are enabled. A bit set to '1' enables the specific SOAM DM counter. A bit set to '0' disables the SOAM DM counter. If a particular SOAM DM counter is not supported the BIT value is set to '0'. Not all SOAM DM counters are supported for all SOAM DM types. This object can only be written at row creation time and cannot be modified once it has been created. bsoampdussent(0) Enables/disables the mefsoamdmcurrentstatssoampdussent and mefsoamdmhistorystatssoampdussent counters. bsoampdusreceived(1) Enables/disables the mefsoamdmcurrentstatssoampdusreceived and mefsoamdmhistorystatssoampdusreceived counters. bframedelaytwowaybins(2) Enables/disables the mefsoamdmcurrentstatsbinsentry counter and the mefsoamdmhistorystatsbinsentry counter when the mefsoamdmcfgmeasbintype is 'twowayframedelay'. bframedelaytwowaymin(3) Enables/disables the mefsoamdmcurrentstatsframedelaytwowaymin and mefsoamdmhistorystatsframedelaytwowaymin counters. bframedelaytwowaymax(4) Enables/disables the mefsoamdmcurrentstatsframedelaytwowaymax and mefsoamdmhistorystatsframedelaytwowaymax counters. bframedelaytwowayavg(5) Enables/disables the mefsoamdmcurrentstatsframedelaytwowayavg and mefsoamdmhistorystatsframedelaytwowayavg counters. bframedelayforwardbins(6) Enables/disables the mefsoamdmcurrentstatsbinsentry counter and the mefsoamdmhistorystatsbinsentry counter contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 80

4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 when the mefsoamdmcfgmeasbintype is 'forwardframedelay'. bframedelayforwardmin(7) Enables/disables the mefsoamdmcurrentstatsframedelayforwardmin and mefsoamdmhistorystatsframedelayforwardmin counters. bframedelayforwardmax(8) Enables/disables the mefsoamdmcurrentstatsframedelayforwardmax and mefsoamdmhistorystatsframedelayforwardmax counters. bframedelayforwardavg(9) Enables/disables the mefsoamdmcurrentstatsframedelayforwardavg and mefsoamdmhistorystatsframedelayforwardavg counters. bframedelaybackwardbins(10) Enables/disables the mefsoamdmcurrentstatsbinsentry counter and the mefsoamdmhistorystatsbinsentry counter when the mefsoamdmcfgmeasbintype is 'backwardframedelay'. bframedelaybackwardmin(11) Enables/disables the mefsoamdmcurrentstatsframedelaybackwardmin and mefsoamdmhistorystatsframedelaybackwardmin counters. bframedelaybackwardmax(12) Enables/disables the mefsoamdmcurrentstatsframedelaybackwardmax and mefsoamdmhistorystatsframedelaybackwardmax counters. bframedelaybackwardavg(13) Enables/disables the mefsoamdmcurrentstatsframedelaybackwardavg and mefsoamdmhistorystatsframedelaybackwardavg counters. bifdvforwardbins(14) Enables/disables the mefsoamdmcurrentstatsbinsentry counter and the mefsoamdmhistorystatsbinsentry counter when the mefsoamdmcfgmeasbintype is 'forwardifdv'. bifdvforwardmin(15) Enables/disables the mefsoamdmcurrentstatsifdvforwardmin and mefsoamdmhistorystatsifdvforwardmin counters. bifdvforwardmax(16) Enables/disables the mefsoamdmcurrentstatsifdvforwardmax and mefsoamdmhistorystatsifdvforwardmax counters. bifdvforwardavg(17) Enables/disables the mefsoamdmcurrentstatsifdvforwardavg and mefsoamdmhistorystatsifdvforwardavg counters. bifdvbackwardbins(18) Enables/disables the mefsoamdmcurrentstatsbinsentry counter and the mefsoamdmhistorystatsbinsentry counter when the mefsoamdmcfgmeasbintype is 'backwardifdv'. bifdvbackwardmin(19) Enables/disables the mefsoamdmcurrentstatsifdvbackwardmin and mefsoamdmhistorystatsifdvbackwardmin counters. bifdvbackwardmax(20) Enables/disables the mefsoamdmcurrentstatsifdvbackwardmax and mefsoamdmhistorystatsifdvbackwardmax counters. bifdvbackwardavg(21) Enables/disables the mefsoamdmcurrentstatsifdvbackwardavg and mefsoamdmhistorystatsifdvbackwardavg counters. bifdvtwowaybins(22) Enables/disables the mefsoamdmcurrentstatsbinsentry counter and the mefsoamdmhistorystatsbinsentry counter when the mefsoamdmcfgmeasbintype is 'twowayifdv'. bifdvtwowaymin(23) Enables/disables the mefsoamdmcurrentstatsifdvtwowaymin and mefsoamdmhistorystatsifdvtwowaymin counters. bifdvtwowaymax(24) Enables/disables the mefsoamdmcurrentstatsifdvtwowaymax and mefsoamdmhistorystatsifdvtwowaymax counters. bifdvtwowayavg(25) Enables/disables the mefsoamdmcurrentstatsifdvtwowayavg and mefsoamdmhistorystatsifdvtwowayavg counters. bframedelayrangeforwardbins(26) Enables/disables the mefsoamdmcurrentstatsbinsentry counter contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 81

4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 and the mefsoamdmhistorystatsbinsentry counter when the mefsoamdmcfgmeasbintype is 'forwardframedelayrange'. bframedelayrangeforwardmax(27) Enables/disables the mefsoamdmcurrentstatsframedelayrangeforwardmax and mefsoamdmhistorystatsframedelayrangeforwardmax counters. bframedelayrangeforwardavg(28) Enables/disables the mefsoamdmcurrentstatsframedelayrangeforwardavg and mefsoamdmhistorystatsframedelayrangeforwardavg counters. bframedelayrangebackwardbins(29) Enables/disables the mefsoamdmcurrentstatsbinsentry counter and the mefsoamdmhistorystatsbinsentry counter when the mefsoamdmcfgmeasbintype is 'backwardframedelayrange'. bframedelayrangebackwardmax(30) Enables/disables the mefsoamdmcurrentstatsframedelayrangebackwardmax and mefsoamdmhistorystatsframedelayrangebackwardmax counters. bframedelayrangebackwardavg(31) Enables/disables the mefsoamdmcurrentstatsframedelayrangebackwardavg and mefsoamdmhistorystatsframedelayrangebackwardavg counters. bframedelayrangetwowaybins(32) Enables/disables the mefsoamdmcurrentstatsbinsentry counter and the mefsoamdmhistorystatsbinsentry counter when the mefsoamdmcfgmeasbintype is 'twowayframedelayrange'. bframedelayrangetwowaymax(33) Enables/disables the mefsoamdmcurrentstatsframedelayrangetwowaymax and mefsoamdmhistorystatsframedelayrangetwowaymax counters. bframedelayrangetwowayavg(34) Enables/disables the mefsoamdmcurrentstatsframedelayrangetwowayavg and mefsoamdmhistorystatsframedelayrangetwowayavg counters. bmeasuredstatsframedelaytwoway(35) Enables/disables the mefsoamdmmeasuredstatsframedelaytwoway counter. bmeasuredstatsframedelayforward(36) Enables/disables the mefsoamdmmeasuredstatsframedelayforward counter. bmeasuredstatsframedelaybackward(37) Enables/disables the mefsoamdmmeasuredstatsframedelaybackward counter. bmeasuredstatsifdvtwoway(38) Enables/disables the mefsoamdmmeasuredstatsifdvtwoway counter. bmeasuredstatsifdvforward(39) Enables/disables the mefsoamdmmeasuredstatsifdvforward counter. bmeasuredstatsifdvbackward(40) Enables/disables the mefsoamdmmeasuredstatsifdvbackward counter. [MEF SOAM-PM] DEFVAL { { ::= { mefsoamdmcfgentry 5 mefsoamdmcfgmessageperiod OBJECT-TYPE SYNTAX MefSoamTcMeasurementPeriodType UNITS ms This object specifies the interval between Delay Measurement OAM message transmission. For Delay Measurement monitoring applications, the default value is 100ms. This object can only be written at row creation time and cannot be modified once it has been created. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 82

4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 [MEF SOAM-PM] R61, R62, D22, R95, R96, D39 DEFVAL { 100 ::= { mefsoamdmcfgentry 6 mefsoamdmcfgpriority OBJECT-TYPE SYNTAX IEEE8021PriorityValue This object specifies the priority of frames with Delay Measurement OAM message information. The default value is to be the value which yields the lowest frame loss. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R1, R2, R56, D21, R57, R58, R90-R94, D28; [MEF 10.2.1] Section 6.8 ::= { mefsoamdmcfgentry 7 mefsoamdmcfgframesize OBJECT-TYPE This object specifies the Delay Measurement frame size between 64 bytes and the maximum transmission unit of the EVC. The range of frame sizes from 64 through 2000 octets need to be supported, and the range of frame sizes from 2001 through 9600 octets is suggested to be supported. The adjustment to the frame size of the standard frame size is accomplished by the addition of a Data or Test TLV. A Data or Test TLV is only added to the frame if the frame size is greater than 64 bytes. This object is only valid for the entity transmitting the Delay Measurement frames (dmdmm, dm1dmtx) and is ignored by the entity receiving frames. In addition, this object is not valid when mefsoamdmcfgversion is 0. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R63, R64, D23, D24, R97, R98, D40, D41 DEFVAL { 64 ::= { mefsoamdmcfgentry 8 mefsoamdmcfgdatapattern OBJECT-TYPE SYNTAX MefSoamTcDataPatternType This object specifies the DM data pattern included in a Data TLV when the size of the DM frame is determined by the mefsoamdmframesize object and mefsoamdmtesttlvincluded is 'false'. If the frame size object does not define the DM frame size or contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 83

4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 mefsoamdmtesttlvincluded is 'true' the value of this object is ignored. This object can only be written at row creation time and cannot be modified once it has been created. DEFVAL { zeropattern ::= { mefsoamdmcfgentry 9 mefsoamdmcfgtesttlvincluded OBJECT-TYPE SYNTAX TruthValue Indicates whether a Test TLV or Data TLV is included when the size of the DM frame is determined by the mefsoamdmframesize object. A value of 'true' indicates that the Test TLV is to be included. A value of 'false' indicates that the Data TLV is to be included. If the frame size object does not define the DM frame size the value of this object is ignored. This object can only be written at row creation time and cannot be modified once it has been created. [Y.1731] 9.3 DEFVAL { false ::= { mefsoamdmcfgentry 10 mefsoamdmcfgtesttlvpattern OBJECT-TYPE SYNTAX MefSoamTcTestPatternType This object specifies the type of test pattern to be sent in the DM frame Test TLV when the size of DM PDU is determined by the mefsoamdmframesize object and mefsoamdmtesttlvincluded is 'true'. If the frame size object does not define the DM frame size or mefsoamdmtesttlvincluded is 'false' the value of this object is ignored. This object can only be written at row creation time and cannot be modified once it has been created. DEFVAL { null ::= { mefsoamdmcfgentry 11 mefsoamdmcfgmeasurementinterval OBJECT-TYPE (1..1440) UNITS minutes This object specifies a Measurement Interval in minutes. A Measurement Interval 15 minutes needs to be supported, other intervals may be supported. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R16, R17 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 84

4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 DEFVAL { 15 ::= { mefsoamdmcfgentry 12 mefsoamdmcfgnumintervalsstored OBJECT-TYPE (2..1000) This object specifies the number of completed Measurement Intervals to store in the history statistic table. At least 32 completed Measurement Intervals are to be stored. 96 Measurement Intervals are recommended to be stored. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R21, D8, D9 DEFVAL { 32 ::= { mefsoamdmcfgentry 13 mefsoamdmcfgdestmacaddress OBJECT-TYPE SYNTAX MacAddress The Target or Destination MAC Address Field to be transmitted. If mefsoamdmcfgtype is 'dmdmm', the destination address is to be the unicast address of the destination MEP. An error is returned if this object is set to a multicast address. If mefsoamdmcfgtype is 'dm1dmtx', the destination address is normally the unicast address of the destination MEP, but can be a multicast address indicating the level of the MEG: 01-80-c2-00-00-3y, where y is the level of the MEG. An error is returned if this object is set to any other multicast address. If mefsoamdmcfgtype is 'dm1dmrx', this object is ignored. This address will be used if the value of the object mefsoamdmdestismepid is 'false'. This object is only valid for the entity transmitting the SOAM DM frames and is ignored by the entity receiving SOAM DM frames. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R55, R89 ::= { mefsoamdmcfgentry 14 mefsoamdmcfgdestmepid OBJECT-TYPE SYNTAX Dot1agCfmMepIdOrZero The Maintenance Association End Point Identifier of another MEP in the same Maintenance Association to which the SOAM DM frame is to be sent. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 85

4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 This address will be used if the value of the column mefsoamdmdestismepid is 'true'. A value of zero means that the destination MEP ID has not been configured. This object is only valid for the entity transmitting the Delay Measurement frames, types 'dmdmm' and 'dm1dmtx'. It is not applicable for the 'dm1dmrx' type. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R55, R89 DEFVAL { 0 ::= { mefsoamdmcfgentry 15 mefsoamdmcfgdestismepid OBJECT-TYPE SYNTAX TruthValue A value of 'true' indicates that MEPID of the target MEP is used for SOAM DM frame transmission. A value of 'false' indicates that the destination MAC address of the target MEP is used for SOAM DM frame transmission. This object is only valid for the entity transmitting the Delay Measurement frames, types 'dmdmm' and 'dm1dmtx'. It is not applicable for the 'dm1dmrx type. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R55, R89 DEFVAL { true ::= { mefsoamdmcfgentry 16 mefsoamdmcfgsourcemacaddress OBJECT-TYPE SYNTAX MacAddress The Source MAC Address Field of the received SOAM DM session PDUs. If mefsoamdmcfgtype is dm1dmrx this object indicates the source address of the dm1dmtx DM session. This object is only valid for mefsoamdmcfgtype set to dm1dmrx. It is ignored for mefsoamdmcfgtype set to dmdmm or dm1dmtx. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R55, R89 ::= { mefsoamdmcfgentry 17 mefsoamdmcfgstarttimetype OBJECT-TYPE SYNTAX MefSoamTcOperationTimeType contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 86

4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 This object specifies the type of start time of the SOAM DM session. The start time can be disabled (none), immediate, relative, or fixed. The value of 'none' is illegal and a write error will be returned if this value is used. The value of 'immediate' starts the SOAM DM session when the mefsoamdmcfgenabled is true. The value of 'fixed' starts the SOAM DM session when the mefsoamdmfixedstartdateandtime is less than or equal to the current system date and time and mefsoamdmcfgenabled is true. This value is used to implement an On-Demand fixed time PM session. The value of 'relative' starts the SOAM DM session when the current system date and time minus the mefsoamdmrelativestarttime is greater than or equal to the system date and time when the mefsoamdmstarttimetype object was written and mefsoamdmcfgenabled is true. This value is used to implement an On-Demand relative time PM session. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R3, R7, R8, D1 DEFVAL { immediate ::= { mefsoamdmcfgentry 18 mefsoamdmcfgfixedstartdateandtime OBJECT-TYPE SYNTAX DateAndTime This object specifies the fixed start date/time for the SOAM Delay Measurement session. This object is used only used if mefsoamdmstarttimetype is 'fixed' and is ignored otherwise. The default value is year 0000, month 01, day 01, time 00:00:00.00. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R9 DEFVAL { '0000010100000000'H ::= { mefsoamdmcfgentry 19 mefsoamdmcfgrelativestarttime OBJECT-TYPE SYNTAX TimeInterval This object specifies the relative start time, from the current system time, for the SOAM DM session. This object is used only if mefsoamdmstarttimetype is 'relative' and is ignored otherwise. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R9 DEFVAL { 0 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 87

4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 ::= { mefsoamdmcfgentry 20 mefsoamdmcfgstoptimetype OBJECT-TYPE SYNTAX MefSoamTcOperationTimeType This object specifies the type of stop time to terminate the SOAM DM session. The stop time can be forever (none), relative, or fixed. The value of 'none' indicates that the SOAM DM session never ends once it has started unless the session is disabled. The value of 'immediate' is illegal and a write error will be returned if this value is used. The value of 'fixed' stops the SOAM DM session when the mefsoamdmfixedstopdateandtime is less than or equal to the current system date. This value is used to implement an On-Demand fixed time PM session. The value of 'relative' stops the SOAM DM session when the time indicated by mefsoamdmrelativestoptime has passed since the session start time as determined by the mefsoamdmcfgstarttimetype, mefsoamdmcfgfixedstartdateandtime and mefsoamdmcfgrelativestarttime objects. This value is used to implement an On-Demand relative time PM session. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R3, R10, D2 DEFVAL { none ::= { mefsoamdmcfgentry 21 mefsoamdmcfgfixedstopdateandtime OBJECT-TYPE SYNTAX DateAndTime This object specifies the fixed stop date/time for the SOAM Delay Measurement session. This object is used only used if mefsoamdmstoptimetype is 'fixed' and is ignored otherwise. The default value is year 0000, month 01, day 01, time 00:00:00.00. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R10, R13 DEFVAL { '0000010100000000'H ::= { mefsoamdmcfgentry 22 mefsoamdmcfgrelativestoptime OBJECT-TYPE SYNTAX TimeInterval This object specifies the relative stop time, from the session start time, to stop the SOAM DM session. This object is used only if mefsoamdmstoptimetype is 'relative' and is contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 88

4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 ignored otherwise. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R11 DEFVAL { 0 ::= { mefsoamdmcfgentry 23 mefsoamdmcfgrepetitiontime OBJECT-TYPE (0..31536000) UNITS seconds This object specifies a configurable repetition time between Measurement Intervals in a Delay Measurement session in seconds. If the value is 0 (none), there is no time gap between the end of one Measurement Interval and the start of a new Measurement Interval. This is the normal usage case. If the value is greater than one Measurement Interval there is time gap between the end of one Measurement Interval and the start of the next Measurement Interval. The repetition time specifies the time between the start of consecutive Measurement Intervals; hence the gap between the end of one Measurement Interval and the start of the next is equal to the difference between the repetition time and the measurement interval. During this gap, no SOAM PDUs are sent for this session and no measurements are made. If the value is greater 0 but less than or equal to the measurement interval, an error is returned. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R18, D3, R19, R20 DEFVAL { 0 ::= { mefsoamdmcfgentry 24 mefsoamdmcfgalignmeasurementintervals OBJECT-TYPE SYNTAX TruthValue This object specifies whether the Measurement Intervals for the Delay Measurement session are aligned with a zero offset to real time. The value 'true' indicates that each Measurement Interval starts at a time which is aligned to NE time source hour, if the repetition time (or the Measurement Interval, if the repetition time is 0) is a factor of an hour, i.e. 60min/15min = 4. For instance, a Measurement Interval/Repetition Time of 15 minutes would stop/start the Measurement Interval at 0, 15, 30, and 45 minutes of an hour. A Measurement Interval/Repetition Time of 7 minutes would not align to the hour since 7 minutes is NOT a factor of an hour, i.e. 60min/7min = 8.6. In this case the behavior is the same as if the object is set to 'false'. The value 'false' indicates that the first Measurement Interval starts contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 89

4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 at an arbitrary time and each subsequent Measurement Interval starts at a time which is determined by mefsoamlmcfgrepetitiontime. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] D4, D5, D6 DEFVAL { true ::= { mefsoamdmcfgentry 25 mefsoamdmcfgalignmeasurementoffset OBJECT-TYPE (0..525600) UNITS minutes This object specifies the offset in minutes from the time of day value if mefsoamdmcfgalignmeasurementintervals is 'true' and the repetition time is a factor of 60 minutes. If not, the value of this object is ignored. If the Measurement Interval is 15 minutes and mefsoamdmcfgalignmeasurementintervals is true and if this object was set to 5 minutes, the Measurement Intervals would start at 5, 20, 35, 50 minutes past each hour. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] D7 DEFVAL { 0 ::= { mefsoamdmcfgentry 26 mefsoamdmcfgnummeasbinsperframedelayinterval OBJECT-TYPE (2..100) This object specifies the number of measurement bins per Measurement Interval for Frame Delay measurements. At least 3 bins are to be supported; at least 10 bins are recommended to be supported. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R27, D11, R28, D12 DEFVAL { 3 ::= { mefsoamdmcfgentry 27 mefsoamdmcfgnummeasbinsperinterframedelayvariationinterval OBJECT-TYPE (2..100) This object specifies the number of measurement bins per Measurement Interval for Inter-Frame Delay Variation measurements. The minimum number of measurement bins to be supported is 2. The contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 90

4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786 4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 desired number of measurements bins to be supported is 10. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R29, D13, R30, D14 DEFVAL { 2 ::= { mefsoamdmcfgentry 28 mefsoamdmcfginterframedelayvariationselectionoffset OBJECT-TYPE (1..100) This object specifies the selection offset for Inter-Frame Delay Variation measurements. If this value is set to n, then the IFDV is calculated by taking the difference in frame delay between frame F and frame (F+n). This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] O4, D25, O6, D42 DEFVAL { 1 ::= { mefsoamdmcfgentry 29 mefsoamdmcfgnummeasbinsperframedelayrangeinterval OBJECT-TYPE (2..100) This object specifies the number of measurement bins per Measurement Interval for Frame Delay Range measurements. At least 2 bins are to be supported; at least 10 bins are recommended to be supported. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R31, D15, R32, D16 DEFVAL { 2 ::= { mefsoamdmcfgentry 30 mefsoamdmcfgsessiontype OBJECT-TYPE SYNTAX MefSoamTcSessionType This object indicates whether the current session is defined to be 'Proactive' or 'On-Demand'. A value of 'proactive' indicates the current session is 'Proactive'. A value of 'ondemand' indicates the current session is 'On-Demand'. This object can only be written at row creation time and cannot be modified once it has been created. [MEF SOAM-PM] R3 DEFVAL { proactive ::= { mefsoamdmcfgentry 31 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 91

4802 4803 4804 4805 4806 4807 4808 4809 4810 4811 4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864 4865 mefsoamdmcfgsessionstatus OBJECT-TYPE SYNTAX MefSoamTcStatusType This object indicates the current status of the DM session. A value of 'active' indicates the current DM session is active, i.e. the current time lies between the start time and the stop time, and mefsoamdmcfgenabled is true. A value of 'notactive' indicates the current DM session is not active, i.e. it has not started yet, has stopped upon reaching the stop time, or is disabled. ::= { mefsoamdmcfgentry 32 mefsoamdmcfghistoryclear OBJECT-TYPE SYNTAX TruthValue This object when written clears the Delay Measurement history tables (mefsoamdmhistorystatstable and mefsoamdmhistorystatsbinstable) - all rows are deleted. When read the value always returns 'false'. Writing this value does not change the current stat table, nor any of the items in the configuration table. Writing this object at row creation has no effect. DEFVAL { false ::= { mefsoamdmcfgentry 33 mefsoamdmcfgrowstatus OBJECT-TYPE SYNTAX RowStatus The status of the row. The writable columns in a row cannot be changed if the row is active, except for mefsoamdmcfgenabled and mefsoamdmcfghistoryclear objects. All columns are to have a valid value before a row can be activated. ::= { mefsoamdmcfgentry 34 -- ***************************************************************************** -- Ethernet Delay Measurement Bin Configuration Table -- ***************************************************************************** mefsoamdmcfgmeasbintable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamDmCfgMeasBinEntry MAX-ACCESS not-accessible This table includes configuration objects for the Delay Measurement bins to collect stats. Each row in the table is automatically created when the Delay Measurement session is defined for the selected MEP. The number of rows created is based upon three items: the DM type, the number of bins defined for each type, and whether bins are enabled for each type. The first four indices are the same as used to create the DM session: contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 92

4866 4867 4868 4869 4870 4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 Maintenance Domain, MaNet, MEP identification, and mefsoamdmcfgindex. The fifth index is the type of bin, and the sixth index is the bin number. For a dmdmm session all nine types of bins can be created. For a dm1dmmtx session no bins are created. For a dm1dmmrx session only types forwardframedelay, forwardifdv, and forwardframedelayrange can be created. The number of bins created for a bin type is based upon: the mefsoamdmcfgnummeasbinsperframedelayinterval object, the mefsoamdmcfgnummeasbinsperinterframedelayvariationinterval object, the mefsoamdmcfgnummeasbinsperframedelayrangeinterval object, and the mefsoamdmcfgmeasurementenable object. For instance, if a dmdmm session with Bins per Frame Delay Interval set to 5, Bins per Frame Delay Variation Interval set to 3, and Frame Delay Range set to 2 (default), all of the appropriate bits set in mefsoamdmmeasurementcfgenable, the following number of rows would be created: For bin types TwoWayFrameDelay(1), forwardframedelay(2), and backwardframedelay(3) = 5 bins * 3 types = 15 rows For bin types TwoWayIfdv(4), forwardifdv(5), backwardifdv(6) = 3 bins * 3 types = 9 rows. For bins types twowayframedelayrange(7), forwardframedelayrange(8), backwardframedelayrange(9) = 2 bins * 3 types = 6 rows. This gives a total of 30 rows created for the DMM session example. Each value in the bin defaults to 5000us greater than the previous bin, with the first bin default value set to 0. For the delay example above (5 bins), the following default values would be written to the bins: bin 1: 0 (range is 0us <= measurement < 5,000us) bin 2: 5000 (range is 5,000us <= measurement < 10,000us) bin 3: 10000 (range is 10,000us <= measurement < 15,000us) bin 4: 15000 (range is 15,000us <= measurement < 20,000us) bin 5: 20000 (range is 20,000us <= measurement < infinity) For the delay variation example above (3 bins), the following default values would be written to the bins: bin 1: 0 (range is 0us <= measurement < 5,000us) bin 2: 5000 (range is 5,000us <= measurement < 10,000us) bin 3: 10000 (range is 10,000us <= measurement < infinity) For the frame delay range example above (2 bins), the following default values would be written to the bins: bin 1: 0 (range is 0us <= measurement < 5,000us) bin 2: 5000 (range is 5,000us <= measurement < infinity) The writable objects in this table need to be persistent upon reboot or restart of a device. Rows are only created if the corresponding measurement type has been enabled via the mefsoamdmcfgmeasurementenable object. [MEF SOAM-PM] R34, R36, R37, D17, R38, R65, D26, D27, R99, D43, D44 ::= { mefsoampmdmobjects 2 mefsoamdmcfgmeasbinentry OBJECT-TYPE contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 93

4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941 4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 4960 4961 4962 4963 4964 4965 4966 4967 4968 4969 4970 4971 4972 4973 4974 4975 4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 SYNTAX MefSoamDmCfgMeasBinEntry MAX-ACCESS not-accessible The conceptual row of mefsoamdmcfgmeasbintable. INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamdmcfgindex, mefsoamdmcfgmeasbintype, mefsoamdmcfgmeasbinnumber ::= { mefsoamdmcfgmeasbintable 1 MefSoamDmCfgMeasBinEntry ::= SEQUENCE { mefsoamdmcfgmeasbintype mefsoamdmcfgmeasbinnumber mefsoamdmcfgmeasbinlowerbound mefsoamdmcfgmeasbintype OBJECT-TYPE SYNTAX MefSoamTcDelayMeasurementBinType MAX-ACCESS not-accessible This object specifies whether the bin number is for Frame Delay or Inter-Frame Delay Variation. ::= { mefsoamdmcfgmeasbinentry 1 mefsoamdmcfgmeasbinnumber OBJECT-TYPE MAX-ACCESS not-accessible This object specifies the bin number for the configured boundary. The first bin has bin number 1. ::= { mefsoamdmcfgmeasbinentry 2 MefSoamTcDelayMeasurementBinType, Unsigned32, Unsigned32 mefsoamdmcfgmeasbinlowerbound OBJECT-TYPE UNITS microseconds (us) MAX-ACCESS read-write This object specifies the lower boundary for a measurement bin. The upper boundary is defined by the next bin value or infinite for the last bin defined. The measurement boundary for each measurement bin is to be larger than the measurement boundary of the preceding measurement bin. By default, the next bin is set to 5000us larger than the lower bin boundary. The values in a bin boundary object represents the time range used to segregate delay data into the appropriate statistical data bin. For five bins with default values, each bin has the following time range: bin 1 = 0, range is 0us <= measurement < 5,000us bin 2 = 5000, range is 5,000us <= measurement < 10,000us bin 3 = 10000, range is 10,000us <= measurement < 15,000us bin 4 = 15000, range is 15,000us <= measurement < 20,000us contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 94

4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 bin 5 = 20000, range is 20,000us <= measurement < infinity The first bin boundary (mefsoamdmcfgbinnumber set to 1) always contains the value of 0. Attempting to write a non-zero value to this bin will result in an error. [MEF SOAM-PM] R33, R35, D17 ::= { mefsoamdmcfgmeasbinentry 3 -- ***************************************************************************** -- Ethernet Delay Measurement Measured Statistic Table -- ***************************************************************************** mefsoamdmmeasuredstatstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamDmMeasuredStatsEntry MAX-ACCESS not-accessible This object contains the last measured results for a SOAM Delay Measurement session. Each row in the table represents a Delay Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. Instances of this managed object are created automatically by the SNMP Agent when the Delay Measurement session is running. Each object in this table applies only if the corresponding bit is set in mefsoamdmcfgmeasurementenable. The objects in this table do not need to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R7, R15, D18 ::= { mefsoampmdmobjects 3 mefsoamdmmeasuredstatsentry OBJECT-TYPE SYNTAX MefSoamDmMeasuredStatsEntry MAX-ACCESS not-accessible The conceptual row of mefsoamdmmeasuredstatstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamdmcfgindex ::= { mefsoamdmmeasuredstatstable 1 MefSoamDmMeasuredStatsEntry ::= SEQUENCE { mefsoamdmmeasuredstatsframedelaytwoway Unsigned32, mefsoamdmmeasuredstatsframedelayforward Unsigned32, mefsoamdmmeasuredstatsframedelaybackward Unsigned32, mefsoamdmmeasuredstatsifdvtwoway Unsigned32, mefsoamdmmeasuredstatsifdvforward Unsigned32, mefsoamdmmeasuredstatsifdvbackward Unsigned32 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 95

5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120 5121 mefsoamdmmeasuredstatsframedelaytwoway OBJECT-TYPE UNITS microseconds This object contains the two-way frame delay calculated by this MEP from the last received SOAM PDU. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmmeasuredstatsentry 1 mefsoamdmmeasuredstatsframedelayforward OBJECT-TYPE UNITS microseconds This object contains the frame delay in the forward direction calculated by this MEP from the last received SOAM PDU. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66 ::= { mefsoamdmmeasuredstatsentry 2 mefsoamdmmeasuredstatsframedelaybackward OBJECT-TYPE UNITS microseconds This object contains the frame delay in the backward direction calculated by this MEP from the last received SOAM PDU. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmmeasuredstatsentry 3 mefsoamdmmeasuredstatsifdvtwoway OBJECT-TYPE UNITS microseconds This object contains the last two-way inter-frame delay interval calculated by this MEP. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmmeasuredstatsentry 4 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 96

5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 mefsoamdmmeasuredstatsifdvforward OBJECT-TYPE UNITS microseconds This object contains the last one-way inter-frame delay interval in the forward direction calculated by this MEP. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66 ::= { mefsoamdmmeasuredstatsentry 5 mefsoamdmmeasuredstatsifdvbackward OBJECT-TYPE UNITS microseconds This object contains the last one-way inter-frame delay interval in the backward direction calculated by this MEP. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmmeasuredstatsentry 6 -- ***************************************************************************** -- Ethernet Delay Measurement Current Statistic Table -- ***************************************************************************** mefsoamdmcurrentstatstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamDmCurrentStatsEntry MAX-ACCESS not-accessible This table contains the results for the current Measurement Interval in a SOAM Delay Measurement session gathered during the interval indicated by mefsoamlmcfgmeasurementinterval. A row in this table is created automatically by the SNMP Agent when the Delay Measurement session is configured. Each row in the table represents the current statistics for a Delay Measurement session for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. There can be more than one DM session per MEP. The objects in this table apply regardless of the value of mefsoamdmcfgtype unless otherwise specified in the object description. Backward and two-way statistic objects are undefined if mefsoamdmcfgtype is dm1dmrx. Except for mefsoamdmcurrentstatsindex, mefsoamdmcurrentstatsstarttime mefsoamdmcurrentstatselapsedtime and mefsoamdmcurrentstatssuspect, each object in this table applies only if the corresponding bit is set in contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 97

5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 mefsoamdmcfgmeasurementenable. The objects in this table do not need to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R7, R15, D9, D18 ::= { mefsoampmdmobjects 4 mefsoamdmcurrentstatsentry OBJECT-TYPE SYNTAX MefSoamDmCurrentStatsEntry MAX-ACCESS not-accessible The conceptual row of mefsoamdmcurrentstatstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamdmcfgindex ::= { mefsoamdmcurrentstatstable 1 MefSoamDmCurrentStatsEntry ::= SEQUENCE { mefsoamdmcurrentstatsindex Unsigned32, mefsoamdmcurrentstatsstarttime DateAndTime, mefsoamdmcurrentstatselapsedtime TimeInterval, mefsoamdmcurrentstatssuspect TruthValue, mefsoamdmcurrentstatsframedelaytwowaymin Unsigned32, mefsoamdmcurrentstatsframedelaytwowaymax Unsigned32, mefsoamdmcurrentstatsframedelaytwowayavg Unsigned32, mefsoamdmcurrentstatsframedelayforwardmin Unsigned32, mefsoamdmcurrentstatsframedelayforwardmax Unsigned32, mefsoamdmcurrentstatsframedelayforwardavg Unsigned32, mefsoamdmcurrentstatsframedelaybackwardmin Unsigned32, mefsoamdmcurrentstatsframedelaybackwardmax Unsigned32, mefsoamdmcurrentstatsframedelaybackwardavg Unsigned32, mefsoamdmcurrentstatsifdvforwardmin Unsigned32, mefsoamdmcurrentstatsifdvforwardmax Unsigned32, mefsoamdmcurrentstatsifdvforwardavg Unsigned32, mefsoamdmcurrentstatsifdvbackwardmin Unsigned32, mefsoamdmcurrentstatsifdvbackwardmax Unsigned32, mefsoamdmcurrentstatsifdvbackwardavg Unsigned32, mefsoamdmcurrentstatsifdvtwowaymin Unsigned32, mefsoamdmcurrentstatsifdvtwowaymax Unsigned32, mefsoamdmcurrentstatsifdvtwowayavg Unsigned32, mefsoamdmcurrentstatsframedelayrangeforwardmax Unsigned32, mefsoamdmcurrentstatsframedelayrangeforwardavg Unsigned32, mefsoamdmcurrentstatsframedelayrangebackwardmax Unsigned32, mefsoamdmcurrentstatsframedelayrangebackwardavg Unsigned32, mefsoamdmcurrentstatsframedelayrangetwowaymax Unsigned32, mefsoamdmcurrentstatsframedelayrangetwowayavg Unsigned32, mefsoamdmcurrentstatssoampdussent Gauge32, mefsoamdmcurrentstatssoampdusreceived Gauge32 mefsoamdmcurrentstatsindex OBJECT-TYPE The index for the current Measurement Interval for this PM session. This value will become the value for mefsoamdmhistorystatsindex once the Measurement Interval contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 98

5250 5251 5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 is completed. Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1. ::= { mefsoamdmcurrentstatsentry 1 mefsoamdmcurrentstatsstarttime OBJECT-TYPE SYNTAX DateAndTime The time that the current Measurement Interval started. [MEF SOAM-PM] R22, R66, R100 ::= { mefsoamdmcurrentstatsentry 2 mefsoamdmcurrentstatselapsedtime OBJECT-TYPE SYNTAX TimeInterval The time that the current Measurement Interval has been running, in 0.01 seconds. [MEF SOAM-PM] R24, R66, R100 ::= { mefsoamdmcurrentstatsentry 3 mefsoamdmcurrentstatssuspect OBJECT-TYPE SYNTAX TruthValue Whether the Measurement Interval has been marked as suspect. The object is to be set to false at the start of a measurement interval. It is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following: 1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service [MEF SOAM-PM] R39, R40, R41 ::= { mefsoamdmcurrentstatsentry 4 mefsoamdmcurrentstatsframedelaytwowaymin OBJECT-TYPE UNITS microseconds This object contains the minimum two-way frame delay calculated by this MEP for this Measurement Interval. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 99

5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 [MEF SOAM-PM] R66 ::= { mefsoamdmcurrentstatsentry 5 mefsoamdmcurrentstatsframedelaytwowaymax OBJECT-TYPE UNITS microseconds This object contains the maximum two-way frame delay calculated by this MEP for this Measurement Interval. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmcurrentstatsentry 6 mefsoamdmcurrentstatsframedelaytwowayavg OBJECT-TYPE UNITS microseconds This object contains the average two-way frame delay calculated by this MEP for this Measurement Interval. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmcurrentstatsentry 7 mefsoamdmcurrentstatsframedelayforwardmin OBJECT-TYPE UNITS microseconds This object contains the minimum one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R67, R101 ::= { mefsoamdmcurrentstatsentry 8 mefsoamdmcurrentstatsframedelayforwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 100

5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 [MEF SOAM-PM] R67, R101 ::= { mefsoamdmcurrentstatsentry 9 mefsoamdmcurrentstatsframedelayforwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R67, R101 ::= { mefsoamdmcurrentstatsentry 10 mefsoamdmcurrentstatsframedelaybackwardmin OBJECT-TYPE UNITS microseconds This object contains the minimum one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R67 ::= { mefsoamdmcurrentstatsentry 11 mefsoamdmcurrentstatsframedelaybackwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R67 ::= { mefsoamdmcurrentstatsentry 12 mefsoamdmcurrentstatsframedelaybackwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 101

5442 5443 5444 5445 5446 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 5459 5460 5461 5462 5463 5464 5465 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5500 5501 5502 5503 5504 5505 This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R67 ::= { mefsoamdmcurrentstatsentry 13 mefsoamdmcurrentstatsifdvforwardmin OBJECT-TYPE UNITS microseconds This object contains the minimum one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmcurrentstatsentry 14 mefsoamdmcurrentstatsifdvforwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmcurrentstatsentry 15 mefsoamdmcurrentstatsifdvforwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmcurrentstatsentry 16 mefsoamdmcurrentstatsifdvbackwardmin OBJECT-TYPE UNITS microseconds contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 102

5506 5507 5508 5509 5510 5511 5512 5513 5514 5515 5516 5517 5518 5519 5520 5521 5522 5523 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539 5540 5541 5542 5543 5544 5545 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557 5558 5559 5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 This object contains the minimum one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmcurrentstatsentry 17 mefsoamdmcurrentstatsifdvbackwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmcurrentstatsentry 18 mefsoamdmcurrentstatsifdvbackwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmcurrentstatsentry 19 mefsoamdmcurrentstatsifdvtwowaymin OBJECT-TYPE UNITS microseconds This object contains the minimum two-way inter-frame delay interval calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmcurrentstatsentry 20 mefsoamdmcurrentstatsifdvtwowaymax OBJECT-TYPE UNITS microseconds contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 103

5570 5571 5572 5573 5574 5575 5576 5577 5578 5579 5580 5581 5582 5583 5584 5585 5586 5587 5588 5589 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5610 5611 5612 5613 5614 5615 5616 5617 5618 5619 5620 5621 5622 5623 5624 5625 5626 5627 5628 5629 5630 5631 5632 5633 This object contains the maximum two-way inter-frame delay interval calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmcurrentstatsentry 21 mefsoamdmcurrentstatsifdvtwowayavg OBJECT-TYPE UNITS microseconds This object contains the average two-way inter-frame delay interval calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmcurrentstatsentry 22 mefsoamdmcurrentstatsframedelayrangeforwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way frame delay range in the forward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmcurrentstatsentry 23 mefsoamdmcurrentstatsframedelayrangeforwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way frame delay range in the forward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmcurrentstatsentry 24 mefsoamdmcurrentstatsframedelayrangebackwardmax OBJECT-TYPE UNITS microseconds contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 104

5634 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658 5659 5660 5661 5662 5663 5664 5665 5666 5667 5668 5669 5670 5671 5672 5673 5674 5675 5676 5677 5678 5679 5680 5681 5682 5683 5684 5685 5686 5687 5688 5689 5690 5691 5692 5693 5694 5695 5696 5697 This object contains the maximum one-way frame delay range in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmcurrentstatsentry 25 mefsoamdmcurrentstatsframedelayrangebackwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way frame delay range in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmcurrentstatsentry 26 mefsoamdmcurrentstatsframedelayrangetwowaymax OBJECT-TYPE UNITS microseconds This object contains the maximum two-way frame delay range calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmcurrentstatsentry 27 mefsoamdmcurrentstatsframedelayrangetwowayavg OBJECT-TYPE UNITS microseconds This object contains the average two-way frame delay range calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmcurrentstatsentry 28 mefsoamdmcurrentstatssoampdussent OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of SOAM PDUs sent contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 105

5698 5699 5700 5701 5702 5703 5704 5705 5706 5707 5708 5709 5710 5711 5712 5713 5714 5715 5716 5717 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5730 5731 5732 5733 5734 5735 5736 5737 5738 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5753 5754 5755 5756 5757 5758 5759 5760 5761 during this Measurement Interval. This object applies when mefsoamdmcfgtype is dmdmm or dm1dmtx and is undefined if mefsoamdmcfgtype is dm1dmrx. It indicates the number of DMM or 1DM SOAM frames transmitted. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmcurrentstatsentry 29 mefsoamdmcurrentstatssoampdusreceived OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of SOAM PDUs received in this Measurement Interval. This object indicates the number of DMR and 1DM SOAM frames received. This object applies when mefsoamdmcfgtype is dmdmm or dm1dmrx and is undefined if mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmcurrentstatsentry 30 -- ***************************************************************************** -- Ethernet Delay Measurement Current Bin Statistic Table -- ***************************************************************************** mefsoamdmcurrentstatsbinstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamDmCurrentStatsBinsEntry MAX-ACCESS not-accessible This table contains the result bins for the current Measurement Interval in a SOAM Delay Measurement session. Each row in the table represents the current bin statistics for a Delay Measurement session for the defined MEP. This table uses six indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. The fifth index indicates bin type and the sixth indicates the specific bin number. A row in this table is created automatically by the SNMP Agent when the Delay Measurement session is configured and the bin counter value is set to 0. The objects in this table are ignored if mefsoamdmcfgtype is 1DmTx. This table applies only if the corresponding bit is set in mefsoamdmcfgmeasurementenable. The objects in this table do not need to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R7, R15, D9 ::= { mefsoampmdmobjects 5 mefsoamdmcurrentstatsbinsentry OBJECT-TYPE SYNTAX MefSoamDmCurrentStatsBinsEntry MAX-ACCESS not-accessible contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 106

5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 5784 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 The conceptual row of mefsoamdmcurrentstatsbinstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamdmcfgindex, mefsoamdmcfgmeasbintype, mefsoamdmcfgmeasbinnumber ::= { mefsoamdmcurrentstatsbinstable 1 MefSoamDmCurrentStatsBinsEntry ::= SEQUENCE { mefsoamdmcurrentstatsbinscounter Gauge32 mefsoamdmcurrentstatsbinscounter OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of completed measurements initiated in this Measurement Interval whose value falls within the range specified for this bin (that is, greater than or equal to the measurement boundary for the bin, and (unless the bin is the last bin) less than the measurement boundary for the following bin. [MEF SOAM-PM] R66, R67, R100, R101 ::= { mefsoamdmcurrentstatsbinsentry 1 -- ***************************************************************************** -- Ethernet Delay Measurement History Statistic Table -- ***************************************************************************** mefsoamdmhistorystatstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamDmHistoryStatsEntry MAX-ACCESS not-accessible This table contains the results for history Measurement Intervals in a SOAM Delay Measurement session. Rows of this table are created automatically by the SNMP Agent when the Delay Measurement session is running and a Measurement Interval is completed. Each row in the table represents the Measurement Interval history statistics for a Delay Measurement session for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. The fifth index is the Measurement Interval. At least 32 completed Measurement Intervals are to be supported. 96 completed Measurement Intervals are recommended to be supported. If there are at least 32 rows in the table and a new Measurement Interval completes and a new row is to be added to the table, the oldest completed Measurement Interval can be deleted (row deletion). If the measurement interval is other than 15 minutes then a minimum of 8 hours of completed Measurement Intervals are to be supported and 24 hours are contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 107

5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 5864 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 5880 5881 5882 5883 5884 5885 5886 5887 5888 5889 recommended to be supported. The objects in this table apply regardless of the value of mefsoamdmcfgtype unless otherwise specified in the object description. Backward and two-way statistic objects are undefined if mefsoamdmcfgtype is dm1dmrx. Except for mefsoamdmhistorystatsindex, mefsoamdmhistorystatsendtime, mefsoamdmhistorystatselapsedtime and mefsoamdmhistorystatssuspect, each object in this table applies only if the corresponding bit is set in mefsoamdmcfgmeasurementenable. The rows and objects in this table are to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R7, R15, R21, D8, R25 ::= { mefsoampmdmobjects 6 mefsoamdmhistorystatsentry OBJECT-TYPE SYNTAX MefSoamDmHistoryStatsEntry MAX-ACCESS not-accessible The conceptual row of mefsoamdmhistorystatstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamdmcfgindex, mefsoamdmhistorystatsindex ::= { mefsoamdmhistorystatstable 1 MefSoamDmHistoryStatsEntry ::= SEQUENCE { mefsoamdmhistorystatsindex Unsigned32, mefsoamdmhistorystatsendtime DateAndTime, mefsoamdmhistorystatselapsedtime TimeInterval, mefsoamdmhistorystatssuspect TruthValue, mefsoamdmhistorystatsframedelaytwowaymin Unsigned32, mefsoamdmhistorystatsframedelaytwowaymax Unsigned32, mefsoamdmhistorystatsframedelaytwowayavg Unsigned32, mefsoamdmhistorystatsframedelayforwardmin Unsigned32, mefsoamdmhistorystatsframedelayforwardmax Unsigned32, mefsoamdmhistorystatsframedelayforwardavg Unsigned32, mefsoamdmhistorystatsframedelaybackwardmin Unsigned32, mefsoamdmhistorystatsframedelaybackwardmax Unsigned32, mefsoamdmhistorystatsframedelaybackwardavg Unsigned32, mefsoamdmhistorystatsifdvforwardmin Unsigned32, mefsoamdmhistorystatsifdvforwardmax Unsigned32, mefsoamdmhistorystatsifdvforwardavg Unsigned32, mefsoamdmhistorystatsifdvbackwardmin Unsigned32, mefsoamdmhistorystatsifdvbackwardmax Unsigned32, mefsoamdmhistorystatsifdvbackwardavg Unsigned32, mefsoamdmhistorystatsifdvtwowaymin Unsigned32, mefsoamdmhistorystatsifdvtwowaymax Unsigned32, mefsoamdmhistorystatsifdvtwowayavg Unsigned32, mefsoamdmhistorystatsframedelayrangeforwardmax Unsigned32, mefsoamdmhistorystatsframedelayrangeforwardavg Unsigned32, mefsoamdmhistorystatsframedelayrangebackwardmax Unsigned32, mefsoamdmhistorystatsframedelayrangebackwardavg Unsigned32, mefsoamdmhistorystatsframedelayrangetwowaymax Unsigned32, mefsoamdmhistorystatsframedelayrangetwowayavg Unsigned32, mefsoamdmhistorystatssoampdussent Gauge32, contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 108

5890 5891 5892 5893 5894 5895 5896 5897 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908 5909 5910 5911 5912 5913 5914 5915 5916 5917 5918 5919 5920 5921 5922 5923 5924 5925 5926 5927 5928 5929 5930 5931 5932 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942 5943 5944 5945 5946 5947 5948 5949 5950 5951 5952 5953 mefsoamdmhistorystatssoampdusreceived Gauge32 mefsoamdmhistorystatsindex OBJECT-TYPE MAX-ACCESS not-accessible The index for the Measurement Interval within this PM session. Measurement Interval indexes are assigned sequentially by the SNMP Agent. The first Measurement Interval that occurs after the session is started is assigned index 1. Referential integrity is necessary, i.e., the index needs to be persistent upon a reboot or restart of a device. The index is never reused while this session is active until it wraps to zero. The index value keeps increasing up to that time. ::= { mefsoamdmhistorystatsentry 1 mefsoamdmhistorystatsendtime OBJECT-TYPE SYNTAX DateAndTime The time that the Measurement Interval ended. [MEF SOAM-PM] R23, R66, R100 ::= { mefsoamdmhistorystatsentry 2 mefsoamdmhistorystatselapsedtime OBJECT-TYPE SYNTAX TimeInterval The length of time that the Measurement Interval ran for, in 0.01 seconds. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 3 mefsoamdmhistorystatssuspect OBJECT-TYPE SYNTAX TruthValue Whether the Measurement Interval has been marked as suspect. The object is set to true when there is a discontinuity in the performance measurements during the Measurement Interval. Conditions for a discontinuity include, but are not limited to the following: 1 - The local time-of-day clock is adjusted by at least 10 seconds 2 - The conducting of a performance measurement is halted before the current Measurement Interval is completed 3 - A local test, failure, or reconfiguration that disrupts service [MEF SOAM-PM] R39, R40, R41, R42 ::= { mefsoamdmhistorystatsentry 4 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 109

5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 5968 5969 5970 5971 5972 5973 5974 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988 5989 5990 5991 5992 5993 5994 5995 5996 5997 5998 5999 6000 6001 6002 6003 6004 6005 6006 6007 6008 6009 6010 6011 6012 6013 6014 6015 6016 6017 mefsoamdmhistorystatsframedelaytwowaymin OBJECT-TYPE UNITS microseconds This object contains the minimum two-way frame delay calculated by this MEP for this Measurement Interval. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 5 mefsoamdmhistorystatsframedelaytwowaymax OBJECT-TYPE UNITS microseconds This object contains the maximum two-way frame delay calculated by this MEP for this Measurement Interval. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 6 mefsoamdmhistorystatsframedelaytwowayavg OBJECT-TYPE UNITS microseconds This object contains the average two-way frame delay calculated by this MEP for this Measurement Interval. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 7 mefsoamdmhistorystatsframedelayforwardmin OBJECT-TYPE UNITS microseconds This object contains the minimum one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 8 mefsoamdmhistorystatsframedelayforwardmax OBJECT-TYPE contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 110

6018 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031 6032 6033 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6044 6045 6046 6047 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060 6061 6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079 6080 6081 UNITS microseconds This object contains the maximum one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 9 mefsoamdmhistorystatsframedelayforwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way frame delay in the forward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 10 mefsoamdmhistorystatsframedelaybackwardmin OBJECT-TYPE UNITS microseconds This object contains the minimum one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 11 mefsoamdmhistorystatsframedelaybackwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 111

6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096 6097 6098 6099 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 6112 6113 6114 6115 6116 6117 6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133 6134 6135 6136 6137 6138 6139 6140 6141 6142 6143 6144 6145 [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 12 mefsoamdmhistorystatsframedelaybackwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way frame delay in the backward direction calculated by this MEP for this Measurement Interval. The value of this object may not be accurate in the absence of sufficiently precise clock synchronization. This object is undefined is mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 13 mefsoamdmhistorystatsifdvforwardmin OBJECT-TYPE UNITS microseconds This object contains the minimum one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 14 mefsoamdmhistorystatsifdvforwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 15 mefsoamdmhistorystatsifdvforwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way inter-frame delay interval in the forward direction calculated by this MEP for this Measurement Interval. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 112

6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 6163 6164 6165 6166 6167 6168 6169 6170 6171 6172 6173 6174 6175 6176 6177 6178 6179 6180 6181 6182 6183 6184 6185 6186 6187 6188 6189 6190 6191 6192 6193 6194 6195 6196 6197 6198 6199 6200 6201 6202 6203 6204 6205 6206 6207 6208 6209 The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 16 mefsoamdmhistorystatsifdvbackwardmin OBJECT-TYPE UNITS microseconds This object contains the minimum one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 17 mefsoamdmhistorystatsifdvbackwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 18 mefsoamdmhistorystatsifdvbackwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way inter-frame delay interval in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 19 mefsoamdmhistorystatsifdvtwowaymin OBJECT-TYPE UNITS microseconds contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 113

6210 6211 6212 6213 6214 6215 6216 6217 6218 6219 6220 6221 6222 6223 6224 6225 6226 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237 6238 6239 6240 6241 6242 6243 6244 6245 6246 6247 6248 6249 6250 6251 6252 6253 6254 6255 6256 6257 6258 6259 6260 6261 6262 6263 6264 6265 6266 6267 6268 6269 6270 6271 6272 6273 This object contains the minimum two-way inter-frame delay interval calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmhistorystatsentry 20 mefsoamdmhistorystatsifdvtwowaymax OBJECT-TYPE UNITS microseconds This object contains the maximum two-way inter-frame delay interval calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmhistorystatsentry 21 mefsoamdmhistorystatsifdvtwowayavg OBJECT-TYPE UNITS microseconds This object contains the average two-way inter-frame delay interval calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmhistorystatsentry 22 mefsoamdmhistorystatsframedelayrangeforwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way Frame Delay Range in the forward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 23 mefsoamdmhistorystatsframedelayrangeforwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way Frame Delay Range in the forward direction calculated by this MEP for this contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 114

6274 6275 6276 6277 6278 6279 6280 6281 6282 6283 6284 6285 6286 6287 6288 6289 6290 6291 6292 6293 6294 6295 6296 6297 6298 6299 6300 6301 6302 6303 6304 6305 6306 6307 6308 6309 6310 6311 6312 6313 6314 6315 6316 6317 6318 6319 6320 6321 6322 6323 6324 6325 6326 6327 6328 6329 6330 6331 6332 6333 6334 6335 6336 6337 Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 24 mefsoamdmhistorystatsframedelayrangebackwardmax OBJECT-TYPE UNITS microseconds This object contains the maximum one-way Frame Delay Range in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 25 mefsoamdmhistorystatsframedelayrangebackwardavg OBJECT-TYPE UNITS microseconds This object contains the average one-way Frame Delay Range in the backward direction calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. [MEF SOAM-PM] R66 ::= { mefsoamdmhistorystatsentry 26 mefsoamdmhistorystatsframedelayrangetwowaymax OBJECT-TYPE UNITS microseconds This object contains the maximum two-way Frame Delay Range calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmhistorystatsentry 27 mefsoamdmhistorystatsframedelayrangetwowayavg OBJECT-TYPE UNITS microseconds This object contains the average two-way Frame Delay Range contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 115

6338 6339 6340 6341 6342 6343 6344 6345 6346 6347 6348 6349 6350 6351 6352 6353 6354 6355 6356 6357 6358 6359 6360 6361 6362 6363 6364 6365 6366 6367 6368 6369 6370 6371 6372 6373 6374 6375 6376 6377 6378 6379 6380 6381 6382 6383 6384 6385 6386 6387 6388 6389 6390 6391 6392 6393 6394 6395 6396 6397 6398 6399 6400 6401 calculated by this MEP for this Measurement Interval. The value of this object is undefined when mefsoamdmcfgtype is dm1dmtx or dm1dmrx. ::= { mefsoamdmhistorystatsentry 28 mefsoamdmhistorystatssoampdussent OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of SOAM PDUs sent during this Measurement Interval. This object applies when mefsoamdmcfgtype is dmdmm or dm1dmtx and is undefined if mefsoamdmcfgtype is dm1dmrx. It indicates the number of DMM or 1DM SOAM frames transmitted. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 29 mefsoamdmhistorystatssoampdusreceived OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of SOAM PDUs received in this Measurement Interval. This object indicates the number of DMR and 1DM SOAM frames received. This object applies when mefsoamdmcfgtype is dmdmm or dm1dmrx and is undefined if mefsoamdmcfgtype is dm1dmtx. [MEF SOAM-PM] R66, R100 ::= { mefsoamdmhistorystatsentry 30 -- ***************************************************************************** -- Ethernet Delay Measurement Bin History Statistic Table -- ***************************************************************************** mefsoamdmhistorystatsbinstable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamDmHistoryStatsBinsEntry MAX-ACCESS not-accessible This table contains the result bins for the history Measurement Intervals in a SOAM Delay Measurement session. Rows of this table are created automatically by the SNMP Agent when the Delay Measurement session is running and a Measurement Interval is completed. Each row in the table represents the Measurement Interval history statistics for a specific bin in a Delay Measurement session for the defined MEP. This table uses seven indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. The fifth index is the Measurement Interval. The sixth index is the specific bin type. The seventh index is the specific bin number. Rows in this table pertaining to a given Measurement Interval are contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 116

6402 6403 6404 6405 6406 6407 6408 6409 6410 6411 6412 6413 6414 6415 6416 6417 6418 6419 6420 6421 6422 6423 6424 6425 6426 6427 6428 6429 6430 6431 6432 6433 6434 6435 6436 6437 6438 6439 6440 6441 6442 6443 6444 6445 6446 6447 6448 6449 6450 6451 6452 6453 6454 6455 6456 6457 6458 6459 6460 6461 6462 6463 6464 6465 deleted when (and only when) the corresponding row in the mefsoamdmhistorystatstable is deleted. The objects in this table are ignored if mefsoamdmcfgtype is 1DmTx. This table applies only if the corresponding bit is set in mefsoamdmcfgmeasurementenable. The objects in this table need to be persistent upon reboot or restart of a device. [MEF SOAM-PM] R7, R15, R21, D8, R66, R67 ::= { mefsoampmdmobjects 7 mefsoamdmhistorystatsbinsentry OBJECT-TYPE SYNTAX MefSoamDmHistoryStatsBinsEntry MAX-ACCESS not-accessible The conceptual row of mefsoamdmhistorystatsbinstable INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamdmcfgindex, mefsoamdmhistorystatsindex, mefsoamdmcfgmeasbintype, mefsoamdmcfgmeasbinnumber ::= { mefsoamdmhistorystatsbinstable 1 MefSoamDmHistoryStatsBinsEntry ::= SEQUENCE { mefsoamdmhistorystatsbinscounter Gauge32 mefsoamdmhistorystatsbinscounter OBJECT-TYPE SYNTAX Gauge32 This object contains the count of the number of completed measurements initiated in this Measurement Interval whose value falls within the range specified for this bin (that is, greater than or equal to the measurement boundary for the bin, and (unless the bin is the last bin) less than the measurement boundary for the following bin. [MEF SOAM-PM] R66, R67, R100, R101 ::= { mefsoamdmhistorystatsbinsentry 1 -- ***************************************************************************** -- Performance Measurement Loss Threshold Configuration Table -- ***************************************************************************** mefsoamlmthresholdcfgtable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamLmThresholdCfgEntry MAX-ACCESS not-accessible This table contains the list of Loss Measurement configuration threshold values for LM Performance Monitoring. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 117

6466 6467 6468 6469 6470 6471 6472 6473 6474 6475 6476 6477 6478 6479 6480 6481 6482 6483 6484 6485 6486 6487 6488 6489 6490 6491 6492 6493 6494 6495 6496 6497 6498 6499 6500 6501 6502 6503 6504 6505 6506 6507 6508 6509 6510 6511 6512 6513 6514 6515 6516 6517 6518 6519 6520 6521 6522 6523 6524 6525 6526 6527 6528 6529 The main purpose of the threshold configuration table is to configure threshold alarm notifications indicating that a specific performance metric is not being met. Each row in the table represents a Loss Measurement session threshold set for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific LM session on the selected MEP. The fifth index is the specific threshold set number. Rows in this table are not created automatically. A row is created in this table to set up a threshold set on a configured MEP that has a configured LM session. If two managers try to 'create' the same row at the same time, the first creation would succeed, the second creation attempt would result in an error. The second creation attempt would then need to select a new index value to successfully create a new row. An NE needs to support at least one threshold set for NE SOAM PM compliance. A second threshold set on the NE is desirable. More than two threshold sets can be configured on the NE if supported on the NE. All the objects in the row have a default value that disables the particular threshold measurement. In order to enable a threshold measurement the particular bit in the mefsoamlmthresholdcfgenable object is to be set to '1' and the selected threshold measurement is to have a threshold value configured. Non-configured threshold measurements are disabled by default. The writable objects in this table need to be persistent upon reboot or restart of a device. ::= { mefsoampmlmobjects 7 mefsoamlmthresholdcfgentry OBJECT-TYPE SYNTAX MefSoamLmThresholdCfgEntry MAX-ACCESS not-accessible The conceptual row of mefsoamlmthresholdcfgtable. INDEX { dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamlmcfgindex, mefsoamlmthresholdcfgindex ::= {mefsoamlmthresholdcfgtable 1 MefSoamLmThresholdCfgEntry ::= SEQUENCE { mefsoamlmthresholdcfgindex Unsigned32, mefsoamlmthresholdcfgenable BITS, mefsoamlmthresholdcfgmeasuredflrforwardthreshold Unsigned32, mefsoamlmthresholdcfgmaxflrforwardthreshold Unsigned32, mefsoamlmthresholdcfgavgflrforwardthreshold Unsigned32, mefsoamlmthresholdcfgmeasuredflrbackwardthreshold Unsigned32, mefsoamlmthresholdcfgmaxflrbackwardthreshold Unsigned32, mefsoamlmthresholdcfgavgflrbackwardthreshold Unsigned32, mefsoamlmthresholdcfgforwardhighlossthreshold Unsigned32, mefsoamlmthresholdcfgforwardconsecutivehighlossthreshold Unsigned32, mefsoamlmthresholdcfgbackwardhighlossthreshold Unsigned32, mefsoamlmthresholdcfgbackwardconsecutivehighlossthreshold Unsigned32, mefsoamlmthresholdcfgforwardunavailcountthreshold Unsigned32, contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 118

6530 6531 6532 6533 6534 6535 6536 6537 6538 6539 6540 6541 6542 6543 6544 6545 6546 6547 6548 6549 6550 6551 6552 6553 6554 6555 6556 6557 6558 6559 6560 6561 6562 6563 6564 6565 6566 6567 6568 6569 6570 6571 6572 6573 6574 6575 6576 6577 6578 6579 6580 6581 6582 6583 6584 6585 6586 6587 6588 6589 6590 6591 6592 6593 mefsoamlmthresholdcfgforwardavailratiothreshold Unsigned32, mefsoamlmthresholdcfgbackwardunavailcountthreshold Unsigned32, mefsoamlmthresholdcfgbackwardavailratiothreshold Unsigned32, mefsoamlmthresholdcfgrowstatus RowStatus mefsoamlmthresholdcfgindex OBJECT-TYPE (1..4294967295) MAX-ACCESS not-accessible The index of the threshold number for the specific LM threshold entry. An index value of '1' needs to be supported. Other index values can also be supported. ::= { mefsoamlmthresholdcfgentry 1 mefsoamlmthresholdcfgenable OBJECT-TYPE SYNTAX BITS { bmefsoamlmmeasuredflrforwardthreshold(0), bmefsoamlmmaxflrforwardthreshold(1), bmefsoamlmavgflrforwardthreshold(2), bmefsoamlmmeasuredflrbackwardthreshold(3), bmefsoamlmmaxflrbackwardthreshold(4), bmefsoamlmavgflrbackwardthreshold(5), bmefsoamlmforwardhighlossthreshold(6), bmefsoamlmforwardconsecutivehighlossthreshold(7), bmefsoamlmbackwardhighlossthreshold(8), bmefsoamlmbackwardconsecutivehighlossthreshold(9), bmefsoamlmunavailforwardthreshold(10), bmefsoamlmavailratioforwardthreshold(11), bmefsoamlmunavailbackwardthreshold(12), bmefsoamlmavailratiobackwardthreshold(13) A vector of bits that indicates the type of SOAM LM thresholds notifications that are enabled. A bit set to '1' enables the specific SOAM LM threshold notification and when the specific counter is enabled and the threshold is crossed a notification is generated. A bit set to '0' disables the specific SOAM LM threshold notification. If a particular SOAM LM threshold is not supported the BIT value is set to '0'. bmefsoamlmmeasuredflrforwardthreshold(0) Enables/disables measured frame loss forward ratio threshold notification. The notification is sent immediately when the mefsoamlmmeasuredstatsforwardflr value is greater than or equal to the threshold value. bmefsoamlmmaxflrforwardthreshold(1) Enables/disables maximum frame loss forward ratio threshold notification. The notification is sent immediately when the mefsoamlmcurrentstatsforwardmaxflr value is greater than or equal to threshold value in a Measurement Interval. bmefsoamlmavgflrforwardthreshold(2) Enables/disables average frame loss forward ratio threshold notification. The notification is sent when at the end of a contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 119

6594 6595 6596 6597 6598 6599 6600 6601 6602 6603 6604 6605 6606 6607 6608 6609 6610 6611 6612 6613 6614 6615 6616 6617 6618 6619 6620 6621 6622 6623 6624 6625 6626 6627 6628 6629 6630 6631 6632 6633 6634 6635 6636 6637 6638 6639 6640 6641 6642 6643 6644 6645 6646 6647 6648 6649 6650 6651 6652 6653 6654 6655 6656 6657 Measurement Interval if the mefsoamlmcurrentstatsforwardavgflr value is greater than or equal to the threshold value. bmefsoamlmmeasuredflrbackwardthreshold(3) Enables/disables measured frame loss backward ratio threshold notification. The notification is sent immediately when the mefsoamlmmeasuredstatsbackwardflr value is greater than or equal to the threshold value. bmefsoamlmmaxflrbackwardthreshold(4) Enables/disables maximum frame loss backward ratio threshold notification. The notification is sent immediately when the mefsoamlmcurrentstatsbackwardmaxflr value is greater than or equal to threshold value in a Measurement Interval. bmefsoamlmavgflrbackwardthreshold(5) Enables/disables average frame loss backward ratio threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamlmcurrentstatsbackwardavgflr value is greater than or equal to the threshold value. bmefsoamlmforwardhighlossthreshold(6) Enables/disables forward high loss threshold notification. The notification is sent immediately when the mefsoamlmcurrentavailstatsforwardhighloss value is greater than or equal to the threshold value in a measurement interval. bmefsoamlmforwardconsecutivehighlossthreshold(7) Enables/disables forward consecutive high loss threshold notification. The notification is sent immediately when the mefsoamlmcurrentavailstatsforwardconsecutivehighloss value is greater than or equal to the threshold value in a measurement interval. bmefsoamlmbackwardhighlossthreshold(8) Enables/disables backward high loss threshold notification. The notification is sent immediately when the mefsoamlmcurrentavailstatsbackwardhighloss value is greater than or equal to the threshold value in a measurement interval. bmefsoamlmbackwardconsecutivehighlossthreshold(9) Enables/disables backward consecutive high loss threshold notification. The notification is sent immediately when the mefsoamlmcurrentavailstatsbackwardconsecutivehighloss value is greater than or equal to the threshold value in a measurement interval. bmefsoamlmunavailforwardthreshold(10) Enables/disables unavailable forward threshold notification. The notification is sent immediately when the mefsoamlmcurrentavailstatsforwardunavailable value is greater than or equal to threshold value in a Measurement Interval. bmefsoamlmavailratioforwardthreshold(11) Enables/disables availability ratio forward threshold notification. The notification is sent immediately when the availability ratio is greater than or equal to threshold value in a Measurement Interval. The availability ratio can be calculated from the values of mefsoamlmcurrentavailstatsforwardavailable and mefsoamlmcurrentavailstatsforwardunavailable. bmefsoamlmunavailbackwardthreshold(12) Enables/disables unavailable backward threshold notification. The notification is sent immediately when the mefsoamlmcurrentavailstatsbackwardunavailable value is greater than or equal to threshold value in a Measurement Interval. bmefsoamlmavailratiobackwardthreshold(13) Enables/disables availability ratio backward threshold notification. The notification is sent immediately when the availability ratio is greater than or equal to threshold value contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 120

6658 6659 6660 6661 6662 6663 6664 6665 6666 6667 6668 6669 6670 6671 6672 6673 6674 6675 6676 6677 6678 6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 6689 6690 6691 6692 6693 6694 6695 6696 6697 6698 6699 6700 6701 6702 6703 6704 6705 6706 6707 6708 6709 6710 6711 6712 6713 6714 6715 6716 6717 6718 6719 6720 6721 in a Measurement Interval. The availability ratio can be calculated from the values of mefsoamlmcurrentavailstatsbackwardavailable and mefsoamlmcurrentavailstatsbackwardunavailable. DEFVAL { { ::= { mefsoamlmthresholdcfgentry 2 mefsoamlmthresholdcfgmeasuredflrforwardthreshold OBJECT-TYPE (0..100000) UNITS milli-percent This object is used to set the measured forward frame loss ratio threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 100000 ::= { mefsoamlmthresholdcfgentry 3 mefsoamlmthresholdcfgmaxflrforwardthreshold OBJECT-TYPE (0..100000) UNITS milli-percent This object is used to set the maximum forward frame loss ratio threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 100000 ::= { mefsoamlmthresholdcfgentry 4 mefsoamlmthresholdcfgavgflrforwardthreshold OBJECT-TYPE (0..100000) UNITS milli-percent This object is used to set the average forward frame loss ratio threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 100000 ::= { mefsoamlmthresholdcfgentry 5 mefsoamlmthresholdcfgmeasuredflrbackwardthreshold OBJECT-TYPE (0..100000) UNITS milli-percent This object is used to set the measured backward frame loss ratio threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 100000 ::= { mefsoamlmthresholdcfgentry 6 mefsoamlmthresholdcfgmaxflrbackwardthreshold OBJECT-TYPE (0..100000) UNITS milli-percent contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 121

6722 6723 6724 6725 6726 6727 6728 6729 6730 6731 6732 6733 6734 6735 6736 6737 6738 6739 6740 6741 6742 6743 6744 6745 6746 6747 6748 6749 6750 6751 6752 6753 6754 6755 6756 6757 6758 6759 6760 6761 6762 6763 6764 6765 6766 6767 6768 6769 6770 6771 6772 6773 6774 6775 6776 6777 6778 6779 6780 6781 6782 6783 6784 6785 This object is used to set the maximum backward frame loss ratio threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 100000 ::= { mefsoamlmthresholdcfgentry 7 mefsoamlmthresholdcfgavgflrbackwardthreshold OBJECT-TYPE (0..100000) UNITS milli-percent This object is used to set the average backward frame loss ratio threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 100000 ::= { mefsoamlmthresholdcfgentry 8 mefsoamlmthresholdcfgforwardhighlossthreshold OBJECT-TYPE This object is used to set the forward high loss threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamlmthresholdcfgentry 9 mefsoamlmthresholdcfgforwardconsecutivehighlossthreshold OBJECT-TYPE This object is used to set the consecutive forward high loss threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamlmthresholdcfgentry 10 mefsoamlmthresholdcfgbackwardhighlossthreshold OBJECT-TYPE This object is used to set the backward high loss threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamlmthresholdcfgentry 11 mefsoamlmthresholdcfgbackwardconsecutivehighlossthreshold OBJECT-TYPE This object is used to set the consecutive backward high loss threshold value that will be used to determine if a threshold notification is generated. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 122

6786 6787 6788 6789 6790 6791 6792 6793 6794 6795 6796 6797 6798 6799 6800 6801 6802 6803 6804 6805 6806 6807 6808 6809 6810 6811 6812 6813 6814 6815 6816 6817 6818 6819 6820 6821 6822 6823 6824 6825 6826 6827 6828 6829 6830 6831 6832 6833 6834 6835 6836 6837 6838 6839 6840 6841 6842 6843 6844 6845 6846 6847 6848 6849 DEFVAL { 4294967295 ::= { mefsoamlmthresholdcfgentry 12 mefsoamlmthresholdcfgforwardunavailcountthreshold OBJECT-TYPE This object is used to set the forward unavailability threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamlmthresholdcfgentry 13 mefsoamlmthresholdcfgforwardavailratiothreshold OBJECT-TYPE (0..100000) UNITS milli-percent This object is used to set the forward availability/total time ratio threshold value that will be used to determine if a threshold notification is generated if the ratio drops below the configured value. The ratio value is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00) Units are in milli-percent, where 1 indicates 0.001 percent. DEFVAL { 0 ::= { mefsoamlmthresholdcfgentry 14 mefsoamlmthresholdcfgbackwardunavailcountthreshold OBJECT-TYPE This object is used to set the backward unavailability threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamlmthresholdcfgentry 15 mefsoamlmthresholdcfgbackwardavailratiothreshold OBJECT-TYPE (0..100000) UNITS milli-percent This object is used to set the backward availability/total time ratio threshold value that will be used to determine if a threshold notification is generated if the ratio drops below the configured value. The ratio value is expressed as a percent with a value of 0 (ratio 0.00) through 100000 (ratio 1.00) Units are in milli-percent, where 1 indicates 0.001 percent. DEFVAL { 0 ::= { mefsoamlmthresholdcfgentry 16 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 123

6850 6851 6852 6853 6854 6855 6856 6857 6858 6859 6860 6861 6862 6863 6864 6865 6866 6867 6868 6869 6870 6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 mefsoamlmthresholdcfgrowstatus OBJECT-TYPE SYNTAX RowStatus The status of the row. The writable columns in a row cannot be changed if the row is active. All columns are to have a valid value before a row can be activated. ::= { mefsoamlmthresholdcfgentry 17 -- ***************************************************************************** -- Performance Measurement Delay Threshold Configuration Table -- ***************************************************************************** mefsoamdmthresholdcfgtable OBJECT-TYPE SYNTAX SEQUENCE OF MefSoamDmThresholdCfgEntry MAX-ACCESS not-accessible This table contains the list of Delay Measurement threshold configuration values for DM Performance Monitoring. The main purpose of the threshold configuration table is to configure threshold alarm notifications indicating that a specific performance metric is not being met. Each row in the table represents a Delay Measurement session threshold set for the defined MEP. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MaNet, and MEP tables. The fourth index is the specific DM session on the selected MEP. The fifth index is the specific threshold set number. Rows in this table are not created automatically. A row is created in this table to set up a threshold set on a configured MEP that has a configured DM session. An NE needs to support at least one threshold set for NE SOAM PM compliance. A second threshold set on the NE is desirable. More than two threshold sets on the NE can be configured if supported on the NE. All the objects in the row have a default value that disables the particular threshold measurement. In order to enable a threshold measurement the particular bit in the mefsoamdmthresholdcfgenable object is to be set to '1' and the selected threshold measurement is to have a threshold value configured. Non-configured threshold measurements are disabled by default. The writable objects in this table need to be persistent upon reboot or restart of a device. ::= { mefsoampmdmobjects 8 mefsoamdmthresholdcfgentry OBJECT-TYPE SYNTAX MefSoamDmThresholdCfgEntry MAX-ACCESS not-accessible The conceptual row of mefsoamdmthresholdcfgtable. INDEX { contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 124

6914 6915 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925 6926 6927 6928 6929 6930 6931 6932 6933 6934 6935 6936 6937 6938 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, mefsoamdmcfgindex, mefsoamdmthresholdcfgindex ::= {mefsoamdmthresholdcfgtable 1 MefSoamDmThresholdCfgEntry ::= SEQUENCE { mefsoamdmthresholdcfgindex Unsigned32, mefsoamdmthresholdcfgenable BITS, mefsoamdmthresholdcfgmeasuredframedelaytwowaythreshold Unsigned32, mefsoamdmthresholdcfgmaxframedelaytwowaythreshold Unsigned32, mefsoamdmthresholdcfgavgframedelaytwowaythreshold Unsigned32, mefsoamdmthresholdcfgmeasuredifdvtwowaythreshold Unsigned32, mefsoamdmthresholdcfgmaxifdvtwowaythreshold Unsigned32, mefsoamdmthresholdcfgavgifdvtwowaythreshold Unsigned32, mefsoamdmthresholdcfgmaxframedelayrangetwowaythreshold Unsigned32, mefsoamdmthresholdcfgavgframedelayrangetwowaythreshold Unsigned32, mefsoamdmthresholdcfgmeasuredframedelayforwardthreshold Unsigned32, mefsoamdmthresholdcfgmaxframedelayforwardthreshold Unsigned32, mefsoamdmthresholdcfgavgframedelayforwardthreshold Unsigned32, mefsoamdmthresholdcfgmeasuredifdvforwardthreshold Unsigned32, mefsoamdmthresholdcfgmaxifdvforwardthreshold Unsigned32, mefsoamdmthresholdcfgavgifdvforwardthreshold Unsigned32, mefsoamdmthresholdcfgmaxframedelayrangeforwardthreshold Unsigned32, mefsoamdmthresholdcfgavgframedelayrangeforwardthreshold Unsigned32, mefsoamdmthresholdcfgmeasuredframedelaybackwardthreshold Unsigned32, mefsoamdmthresholdcfgmaxframedelaybackwardthreshold Unsigned32, mefsoamdmthresholdcfgavgframedelaybackwardthreshold Unsigned32, mefsoamdmthresholdcfgmeasuredifdvbackwardthreshold Unsigned32, mefsoamdmthresholdcfgmaxifdvbackwardthreshold Unsigned32, mefsoamdmthresholdcfgavgifdvbackwardthreshold Unsigned32, mefsoamdmthresholdcfgmaxframedelayrangebackwardthreshold Unsigned32, mefsoamdmthresholdcfgavgframedelayrangebackwardthreshold Unsigned32, mefsoamdmthresholdcfgrowstatus mefsoamdmthresholdcfgindex OBJECT-TYPE (1..4294967295) MAX-ACCESS not-accessible The index of the threshold number for the specific DM threshold entry. RowStatus An index value of '1' is to be supported. Other index values can be supported. ::= { mefsoamdmthresholdcfgentry 1 mefsoamdmthresholdcfgenable OBJECT-TYPE SYNTAX BITS { bmefsoamdmmeasuredframedelaytwowaythreshold(0), bmefsoamdmmaxframedelaytwowaythreshold(1), bmefsoamdmavgframedelaytwowaythreshold(2), bmefsoamdmmeasuredifdvtwowaythreshold(3), bmefsoamdmmaxifdvtwowaythreshold(4), bmefsoamdmavgifdvtwowaythreshold(5), bmefsoamdmmaxframedelayrangetwowaythreshold(6), bmefsoamdmavgframedelayrangetwowaythreshold(7), bmefsoamdmmeasuredframedelayforwardthreshold(8), bmefsoamdmmaxframedelayforwardthreshold(9), contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 125

6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6993 6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 bmefsoamdmavgframedelayforwardthreshold(10), bmefsoamdmmeasuredifdvforwardthreshold(11), bmefsoamdmmaxifdvforwardthreshold(12), bmefsoamdmavgifdvforwardthreshold(13), bmefsoamdmmaxframedelayrangeforwardthreshold(14), bmefsoamdmavgframedelayrangeforwardthreshold(15), bmefsoamdmmeasuredframedelaybackwardthreshold(16), bmefsoamdmmaxframedelaybackwardthreshold(17), bmefsoamdmavgframedelaybackwardthreshold(18), bmefsoamdmmeasuredifdvbackwardthreshold(19), bmefsoamdmmaxifdvbackwardthreshold(20), bmefsoamdmavgifdvbackwardthreshold(21), bmefsoamdmmaxframedelayrangebackwardthreshold(22), bmefsoamdmavgframedelayrangebackwardthreshold(23) A vector of bits that indicates the type of SOAM DM threshold notifications that are enabled. A bit set to '1' enables the specific SOAM DM threshold notification and when the specific counter is enabled and the threshold is crossed a notification is generated. A bit set to '0' disables the specific SOAM DM threshold notification. If a particular SOAM DM threshold is not supported the BIT value is set to '0'. bmefsoamdmmeasuredframedelaytwowaythreshold(0) Enables/disables measured frame two-way delay threshold notification. The notification is sent immediately when the mefsoamdmmeasuredstatsframedelaytwoway value is greater than or equal to threshold value. bmefsoamdmmaxframedelaytwowaythreshold(1) Enables/disables maximum frame two-way delay threshold notification. The notification is sent immediately when the mefsoamdmcurrentstatsframedelaytwowaymax value is greater than or equal to threshold value in a Measurement Interval. bmefsoamdmavgframedelaytwowaythreshold(2) Enables/disables average frame two-way delay threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamdmcurrentstatsframedelaytwowayavg value is greater than or equal to the threshold value. bmefsoamdmmeasuredifdvtwowaythreshold(3) Enables/disables measured frame IFDV two-way threshold notification. The notification is sent immediately when the mefsoamdmmeasuredstatsifdvtwoway value is greater than or equal to threshold value. bmefsoamdmmaxifdvtwowaythreshold(4) Enables/disables maximum frame IFDV two-way threshold notification. The notification is sent immediately when the mefsoamdmcurrentstatsifdvtwowaymax value is greater than or equal to threshold value in a Measurement Interval. bmefsoamdmavgifdvtwowaythreshold(5) Enables/disables average frame IFDV two-way threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamdmcurrentstatsifdvtwowayavg value is greater than or equal to the threshold value. bmefsoamdmmaxframedelayrangetwowaythreshold(6) Enables/disables maximum Frame Delay Range two-way threshold contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 126

7042 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7081 7082 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 notification. The notification is sent immediately when the mefsoamdmcurrentstatsframedelayrangetwowaymax value is greater than or equal to threshold value in a Measurement Interval. bmefsoamdmavgframedelayrangetwowaythreshold(7) Enables/disables average Frame Delay Range two-way threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamdmcurrentstatsframedelayrangetwowayavg value is greater than or equal to the threshold value. bmefsoamdmmeasuredframedelayforwardthreshold(8) Enables/disables measured forward frame delay threshold notification. The notification is sent immediately when the mefsoamdmmeasuredstatsframedelayforward value is greater than or equal to threshold value. bmefsoamdmmaxframedelayforwardthreshold(9) Enables/disables maximum forward frame delay threshold notification. The notification is sent immediately when the mefsoamdmcurrentstatsframedelayforwardmax value is greater than or equal to threshold value in a Measurement Interval. bmefsoamdmavgframedelayforwardthreshold(10) Enables/disables average forward frame delay threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamdmcurrentstatsframedelayforwardavg value is greater than or equal to the threshold value. bmefsoamdmmeasuredifdvforwardthreshold(11) Enables/disables measured frame IFDV forward threshold notification. The notification is sent immediately when the mefsoamdmmeasuredstatsifdvforward value is greater than or equal to threshold value. bmefsoamdmmaxifdvforwardthreshold(12) Enables/disables maximum frame IFDV forward threshold notification. The notification is sent immediately when the mefsoamdmcurrentstatsifdvforwardmax value is greater than or equal to threshold value in a Measurement Interval. bmefsoamdmavgifdvforwardthreshold(13) Enables/disables average frame IFDV forward threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamdmcurrentstatsifdvforwardavg value is greater than or equal to the threshold value. bmefsoamdmmaxframedelayrangeforwardthreshold(14) Enables/disables maximum Frame Delay Range forward threshold notification. The notification is sent immediately when the mefsoamdmcurrentstatsframedelayrangeforwardmax value is greater than or equal to threshold value in a Measurement Interval. bmefsoamdmavgframedelayrangeforwardthreshold(15) Enables/disables average Frame Delay Range forward threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamdmcurrentstatsframedelayrangeforwardavg value is greater than or equal to the threshold value. bmefsoamdmmeasuredframedelaybackwardthreshold(16) Enables/disables measured backward frame delay threshold notification. The notification is sent immediately when the mefsoamdmmeasuredstatsframedelaybackward value is greater than or equal to threshold value. bmefsoamdmmaxframedelaybackwardthreshold(17) Enables/disables maximum backward frame delay threshold notification. The notification is sent immediately when the mefsoamdmcurrentstatsframedelaybackwardmax value is greater than or equal to threshold value in a Measurement Interval. bmefsoamdmavgframedelaybackwardthreshold(18) contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 127

7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 Enables/disables average backward frame delay threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamdmcurrentstatsframedelaybackwardavg value is greater than or equal to the threshold value. bmefsoamdmmeasuredifdvbackwardthreshold(19) Enables/disables measured frame IFDV backward threshold notification. The notification is sent immediately when the mefsoamdmmeasuredstatsifdvbackward value is greater than or equal to threshold value. bmefsoamdmmaxifdvbackwardthreshold(20) Enables/disables maximum frame IFDV backward threshold notification. The notification is sent immediately when the mefsoamdmcurrentstatsifdvbackwardmax value is greater than or equal to threshold value in a Measurement Interval. bmefsoamdmavgifdvbackwardthreshold(21) Enables/disables average frame IFDV backward threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamdmcurrentstatsifdvbackwardavg value is greater than or equal to the threshold value. bmefsoamdmmaxframedelayrangebackwardthreshold(22) Enables/disables maximum Frame Delay Range backward threshold notification. The notification is sent immediately when the mefsoamdmcurrentstatsframedelayrangebackwardmax value is greater than or equal to threshold value in a Measurement Interval. bmefsoamdmavgframedelayrangebackwardthreshold(23) Enables/disables average Frame Delay Range backward threshold notification. The notification is sent when at the end of a Measurement Interval if the mefsoamdmcurrentstatsframedelayrangebackwardavg value is greater than or equal to the threshold value. DEFVAL { { ::= { mefsoamdmthresholdcfgentry 2 mefsoamdmthresholdcfgmeasuredframedelaytwowaythreshold OBJECT-TYPE UNITS microseconds This object is used to set the measurement two-way delay threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 3 mefsoamdmthresholdcfgmaxframedelaytwowaythreshold OBJECT-TYPE UNITS microseconds This object is used to set the maximum two-way delay threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 4 mefsoamdmthresholdcfgavgframedelaytwowaythreshold OBJECT-TYPE contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 128

7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 UNITS microseconds This object is used to set the average two-way delay threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 5 mefsoamdmthresholdcfgmeasuredifdvtwowaythreshold OBJECT-TYPE UNITS microseconds This object is used to set the measurement two-way IFDV threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 6 mefsoamdmthresholdcfgmaxifdvtwowaythreshold OBJECT-TYPE UNITS microseconds This object is used to set the maximum two-way IFDV threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 7 mefsoamdmthresholdcfgavgifdvtwowaythreshold OBJECT-TYPE UNITS microseconds This object is used to set the average two-way IFDV threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 8 mefsoamdmthresholdcfgmaxframedelayrangetwowaythreshold OBJECT-TYPE UNITS microseconds This object is used to set the maximum two-way Frame Delay Range threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 9 mefsoamdmthresholdcfgavgframedelayrangetwowaythreshold OBJECT-TYPE contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 129

7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 UNITS microseconds This object is used to set the average two-way Frame Delay Range threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 10 mefsoamdmthresholdcfgmeasuredframedelayforwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the measurement forward delay threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 11 mefsoamdmthresholdcfgmaxframedelayforwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the maximum forward delay threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 12 mefsoamdmthresholdcfgavgframedelayforwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the average forward delay threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 13 mefsoamdmthresholdcfgmeasuredifdvforwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the measurement IFDV threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 14 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 130

7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 mefsoamdmthresholdcfgmaxifdvforwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the maximum IFDV threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 15 mefsoamdmthresholdcfgavgifdvforwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the average IFDV threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 16 mefsoamdmthresholdcfgmaxframedelayrangeforwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the maximum Frame Delay Range threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 17 mefsoamdmthresholdcfgavgframedelayrangeforwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the average Frame Delay Range threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 18 mefsoamdmthresholdcfgmeasuredframedelaybackwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the measurement backward delay threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 19 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 131

7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 mefsoamdmthresholdcfgmaxframedelaybackwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the maximum backward delay threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 20 mefsoamdmthresholdcfgavgframedelaybackwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the average backward delay threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 21 mefsoamdmthresholdcfgmeasuredifdvbackwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the measurement backward IFDV threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 22 mefsoamdmthresholdcfgmaxifdvbackwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the maximum backward IFDV threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 23 mefsoamdmthresholdcfgavgifdvbackwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the average backward IFDV threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 132

7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 ::= { mefsoamdmthresholdcfgentry 24 mefsoamdmthresholdcfgmaxframedelayrangebackwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the maximum backward Frame Delay Range threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 25 mefsoamdmthresholdcfgavgframedelayrangebackwardthreshold OBJECT-TYPE UNITS microseconds This object is used to set the average backward Frame Delay Range threshold value that will be used to determine if a threshold notification is generated. DEFVAL { 4294967295 ::= { mefsoamdmthresholdcfgentry 26 mefsoamdmthresholdcfgrowstatus OBJECT-TYPE SYNTAX RowStatus The status of the row. The writable columns in a row cannot be changed if the row is active. All columns are to have a valid value before a row can be activated. ::= { mefsoamdmthresholdcfgentry 27 -- ***************************************************************************** -- Notification Configuration Objects -- ***************************************************************************** mefsoampmnotificationcfgalarminterval OBJECT-TYPE (0..60) UNITS Seconds MAX-ACCESS read-write A value indicating the shortest time interval in seconds between the generation of the same notification type per PM session to the list of notification destinations. An agent generates the first notification of given type for a given PM session immediately. An agent is not to generate a second specific notification of the same type for the same MEP for the same session until the time interval has expired. A value of zero indicates that all notifications are sent immediately upon detection of the condition. DEFVAL {5 ::= { mefsoampmnotificationcfg 1 mefsoampmnotificationcfgalarmenable OBJECT-TYPE contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 133

7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 SYNTAX BITS { bavailabilitychangealarm(0), blmsessionstartstopalarm(1), bdmsessionstartstopalarm(2), bpmthresholdabovealarm(3), bpmthresholdsetclearalarm(4) MAX-ACCESS read-write A vector of bits that indicates whether a specific notification is enabled. A bit set to '1' enables the specific notification generation. A bit set to '0' disables the specific notification. If a particular alarm is not supported the BIT value of the enable/disable is set to '0'. bavailabilitychangealarm(0) enables/disables mefsoamavailabilitychangealarm blmsessionstartstopalarm(1) enables/disables mefsoamlmsessionstartstopalarm bdmsessionstartstopalarm(2) enables/disables mefsoamdmsessionstartstopalarm bpmthresholdabovealarm(3) enables/disables mefsoampmthresholdabovealarm bpmthresholdsetclearalarm(4) enables/disables mefsoampmthresholdsetclearalarm DEFVAL { { ::= { mefsoampmnotificationcfg 2 -- ***************************************************************************** -- Notification Data Objects -- ***************************************************************************** mefsoampmnotificationobjdateandtime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS accessible-for-notify This object contains the time and date at the time that the notification event is detected, not the time of the notification generation. This object is used only for notifications. The mechanism to set and keep current the date and time is not specified. ::= { mefsoampmnotificationobj 1 mefsoampmnotificationobjthresholdid OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS accessible-for-notify The Object Identifier of the object that caused the generation of the notification from the mefsoamlmthresholdentry or mefsoamdmthresholdentry. This object is only used for the notification. ::= { mefsoampmnotificationobj 2 mefsoampmnotificationobjthresholdconfig OBJECT-TYPE MAX-ACCESS accessible-for-notify contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 134

7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 The configured threshold value of the object that caused the generation of the notification. This object is only used for the notification. ::= { mefsoampmnotificationobj 3 mefsoampmnotificationobjthresholdvalue OBJECT-TYPE MAX-ACCESS accessible-for-notify The measured value of the object at the time of the generation of the Notification, from the mefsoamlmmeasuredstatstable, mefsoamlmcurrentstatstable, mefsoamlmcurrentavailstatstable, mefsoamdmmeasuredstatstable or mefsoamdmcurrentstatstable. This object is only used for the notification. ::= { mefsoampmnotificationobj 4 mefsoampmnotificationobjsuspect OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS accessible-for-notify The suspect flag for the current Measurement Interval in which the notification was generated from the mefsoamlmcurrentstatstable, mefsoamlmcurrentavailstatstable, or mefsoamdmcurrentstatstable. This object is only used for the notification. ::= { mefsoampmnotificationobj 5 mefsoampmnotificationobjcrossingtype OBJECT-TYPE SYNTAX INTEGER { abovealarm (1), setalarm (2), clearalarm (3) MAX-ACCESS accessible-for-notify The Notification Crossing Type of the object that caused the generation of the notification from the mefsoamlmthresholdentry or mefsoamdmthresholdentry. abovealarm(1) indicates that the crossing type alarm was an above threshold setalarm(2) indicates that the crossing type alarm was a set threshold clearalarm(3) indicates that the crossing type alarm was a clear threshold This object is only used for the notification. ::= { mefsoampmnotificationobj 6 mefsoampmnotificationobjdestinationmep OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS accessible-for-notify contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 135

7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 The MAC address of the Destination MEP associated the notification found in either the mefsoamdmcfgtable or mefsoamlmcfgtable. This object is only used for the notification. ::= { mefsoampmnotificationobj 7 mefsoampmnotificationobjpriority OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS accessible-for-notify The CoS priority of the associated notification found in either the mefsoamdmcfgtable or mefsoamlmcfgtable. This object is only used for the notification. ::= { mefsoampmnotificationobj 8 -- ***************************************************************************** -- NOTIFICATIONS (TRAPS) -- ***************************************************************************** mefsoamavailabilitychangealarm NOTIFICATION-TYPE OBJECTS { mefsoampmnotificationobjdateandtime, mefsoamlmmeasuredstatsavailforwardstatus, mefsoamlmmeasuredstatsavailbackwardstatus, mefsoamlmmeasuredstatsavailforwardlasttransitiontime, mefsoamlmmeasuredstatsavailbackwardlasttransitiontime, mefsoamlmcurrentavailstatsforwardavailable, mefsoamlmcurrentavailstatsforwardunavailable, mefsoamlmcurrentavailstatsbackwardavailable, mefsoamlmcurrentavailstatsbackwardunavailable, mefsoampmnotificationobjdestinationmep, mefsoampmnotificationobjpriority An mefsoamavailabilitychangealarm notification is sent when the state of mefsoamlmmeasuredstatsavailforwardstatus or mefsoamlmmeasuredstatsavailbackwardstatus changes. The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the PM session reporting the change by the indices in the OID mefsoamlmmeasuredstatsavailforwardlasttransitiontime, including dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, and mefsoamlmcfgindex. An agent is not to generate more than one mefsoamavailabilitychangealarm 'notification-event' in a given time interval per PM session as specified by the mefsoampmnotificationcfgalarminterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations. If additional availability state changes occur within the mefsoampmnotificationcfgalarminterval period, then notification generation for these changes are suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any availability contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 136

7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 state changes occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away. [MEF SOAM-PM] R83, R84 ::= { mefsoampmnotifications 1 mefsoamlmsessionstartstopalarm NOTIFICATION-TYPE OBJECTS { mefsoamlmcfgsessionstatus, mefsoampmnotificationobjdateandtime, mefsoampmnotificationobjdestinationmep An mefsoamlmsessionstartstopalarm notification is sent when the state of mefsoamlmcfgsessionstatus changes. The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the individual PM session reporting the start/stop by the indices in the OID mefsoamlmcfgsessionstatus, including dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, and mefsoamlmcfgindex. An agent is not to generate more than one mefsoamlmsessionstartstopalarm 'notification-event' in a given time interval per LM session as specified by the mefsoampmnotificationcfgalarminterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations. If additional operational state changes occur within the mefsoampmnotificationcfgalarminterval period, then notification generation for these changes are be suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any operational state changes occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away. ::= { mefsoampmnotifications 2 mefsoamdmsessionstartstopalarm NOTIFICATION-TYPE OBJECTS { mefsoamdmcfgsessionstatus, mefsoampmnotificationobjdateandtime, mefsoampmnotificationobjdestinationmep An mefsoamdmsessionstartstopalarm notification is sent when the state of mefsoamdmcfgsessionstatus changes. The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the individual PM session reporting the start/stop by the indices in the OID mefsoamdmcfgsessionstatus, including dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, and mefsoamdmcfgindex. An agent is not to generate more than one mefsoamdmsessionstartstopalarm 'notification-event' in a given time interval per DM session as specified by mefsoampmnotificationcfgalarminterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 137

7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 If additional operational state changes occur within the mefsoampmnotificationcfgalarminterval period, then notification generation for these changes are suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any operational state changes occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away. ::= { mefsoampmnotifications 3 mefsoampmthresholdcrossingalarm NOTIFICATION-TYPE OBJECTS { mefsoampmnotificationobjcrossingtype, mefsoampmnotificationobjthresholdid, mefsoampmnotificationobjthresholdconfig, mefsoampmnotificationobjthresholdvalue, mefsoampmnotificationobjsuspect, mefsoampmnotificationobjdateandtime, mefsoampmnotificationobjdestinationmep An mefsoampmthresholdcrossingalarm notification is sent if the following conditions are met for a particular type. For an abovealarm five conditions need to be met: a) measurement of the parameter is enabled via mefsoamlmcfgmeasurementenable for a LM crossing or mefsoamdmcfgmeasurementenable for a DM crossing; and b) the parameter threshold is configured in the mefsoamlmthresholdcfgtable or mefsoamdmthresholdcfgtable; and c) the threshold crossing type of bpmthresholdabovealarm is enabled; and d) the measured value of the parameter exceeds the value configured in the mefsoamlmthresholdcfgtable for a LM crossing entry or mefsoamdmthresholdcfgtable for a DM crossing entry for a type of bpmthresholdabovealarm; and e) no previous mefsoampmthresholdcrossingalarm notifications with type abovealarm have been sent relating to the same threshold in the mefsoamlmthresholdcfgtable or mefsoamdmthresholdcfgtable and the same parameter, during this Measurement Interval. For a setalarm five conditions need to be met: a) measurement of the parameter is enabled via mefsoamlmcfgmeasurementenable for a LM crossing or mefsoamdmcfgmeasurementenable for a DM crossing; and b) the parameter threshold is configured in the mefsoamlmthresholdcfgtable or mefsoamdmthresholdcfgtable; and c) the threshold crossing type of bpmthresholdsetclearalarm is enabled; and d) the measured value of the parameter exceeds the value configured in the mefsoamlmthresholdcfgtable for a LM crossing entry or mefsoamdmthresholdcfgtable for a DM crossing entry for a type of bpmthresholdsetclearalarm for the Measurement Interval; and contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 138

7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 e) the previous measured value did not exceed the value configured in the mefsoamlmthresholdcfgtable for a LM crossing entry or mefsoamdmthresholdcfgtable for a DM crossing entry for a type of bpmthresholdsetclearalarm. For a clearalarm five conditions need to be met: a) measurement of the parameter is enabled via mefsoamlmcfgmeasurementenable for a LM crossing or mefsoamdmcfgmeasurementenable for a DM crossing; and b) the parameter threshold is configured in the mefsoamlmthresholdcfgtable or mefsoamdmthresholdcfgtable; and c) the threshold crossing type of bpmthresholdsetclearalarm is enabled; and d) the measured value of the parameter did not exceed the value configured in the mefsoamlmthresholdcfgtable for a LM crossing entry or mefsoamdmthresholdcfgtable for a DM crossing entry for a type of bpmthresholdsetclearalarm for the Measurement Interval; and e) the previous measured value did exceed the value configured in the mefsoamlmthresholdcfgtable for a LM crossing entry or mefsoamdmthresholdcfgtable for a DM crossing entry for a type of bpmthresholdsetclearalarm. In the case of thresholds applied to a maximum or average measurement counter, the previous measured value is the value of the counter at the end of the preceding Measurement Interval. In the case of thresholds applied to the last measured value, it is the previous measured value. The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the LM or DM session reporting the threshold crossing by the indices in the mefsoampmnotificationcfgthresholdid object, including dot1agcfmmdindex, dot1agcfmmaindex, dot1agcfmmepidentifier, and the mefsoamlmcfgindex or mefsoamdmcfgindex. An agent is not to generate more than one mefsoamlmthresholdcrossingalarm 'notification-event' of a given type per LM or DM session as specified by mefsoampmnotificationcfgalarminterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations. If additional threshold crossing events occur within the mefsoampmnotificationcfgalarminterval period, then notification generation for these changes are suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any threshold crossing events occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away. ::= { mefsoampmnotifications 4 -- ***************************************************************************** -- SOAM-PM MIB Module - Conformance Information -- ***************************************************************************** mefsoampmmibcompliances OBJECT IDENTIFIER ::= { mefsoampmmibconformance 1 mefsoampmmibgroups OBJECT IDENTIFIER ::= { mefsoampmmibconformance 2 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 139

7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 -- ****************************************************************** -- SOAM-PM MIB Units of conformance -- ****************************************************************** mefsoampmmepmandatorygroup OBJECT-GROUP OBJECTS { mefsoampmmepopernextindex, mefsoampmmepslmsingleendedresponder, mefsoampmmepdmsingleendedresponder Mandatory objects for the Service OAM PM MEP group. ::= { mefsoampmmibgroups 1 mefsoampmmepoptionalgroup OBJECT-GROUP OBJECTS { mefsoampmmeplmsingleendedresponder Optional objects for the Service OAM PM MEP group. ::= { mefsoampmmibgroups 2 mefsoamlmcfgmandatorygroup OBJECT-GROUP OBJECTS { mefsoamlmcfgtype, mefsoamlmcfgenabled, mefsoamlmcfgmeasurementenable, mefsoamlmcfgmessageperiod, mefsoamlmcfgpriority, mefsoamlmcfgframesize, mefsoamlmcfgdatapattern, mefsoamlmcfgmeasurementinterval, mefsoamlmcfgnumintervalsstored, mefsoamlmcfgdestmacaddress, mefsoamlmcfgdestmepid, mefsoamlmcfgdestismepid, mefsoamlmcfgstarttimetype, mefsoamlmcfgfixedstartdateandtime, mefsoamlmcfgrelativestarttime, mefsoamlmcfgstoptimetype, mefsoamlmcfgfixedstopdateandtime, mefsoamlmcfgrelativestoptime, mefsoamlmcfgrepetitiontime, mefsoamlmcfgavailabilitymeasurementinterval, mefsoamlmcfgavailabilitynumconsecutivemeaspdus, mefsoamlmcfgavailabilityflrthreshold, mefsoamlmcfgavailabilitynumconsecutiveintervals, mefsoamlmcfgsessiontype, mefsoamlmcfgsessionstatus, mefsoamlmcfghistoryclear, mefsoamlmcfgrowstatus Mandatory objects for the Service OAM LM Configuration group. ::= { mefsoampmmibgroups 3 mefsoamlmcfgoptionalgroup OBJECT-GROUP OBJECTS { contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 140

7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 mefsoamlmcfgversion, mefsoamlmcfgtesttlvincluded, mefsoamlmcfgtesttlvpattern, mefsoamlmcfgalignmeasurementintervals, mefsoamlmcfgavailabilitynumconsecutivehighflr, mefsoamlmcfgalignmeasurementoffset Optional objects for the Service OAM LM Configuration group. ::= { mefsoampmmibgroups 4 mefsoamlmmeasuredstatsmandatorygroup OBJECT-GROUP OBJECTS { mefsoamlmmeasuredstatsavailforwardlasttransitiontime, mefsoamlmmeasuredstatsavailbackwardlasttransitiontime Mandatory objects for the Service OAM LM Measured Stats group. ::= { mefsoampmmibgroups 5 mefsoamlmmeasuredstatsoptionalgroup OBJECT-GROUP OBJECTS { mefsoamlmmeasuredstatsforwardflr, mefsoamlmmeasuredstatsbackwardflr, mefsoamlmmeasuredstatsavailforwardstatus, mefsoamlmmeasuredstatsavailbackwardstatus Optional objects for the Service OAM LM Measured Stats group. ::= { mefsoampmmibgroups 6 mefsoamlmcurrentavailstatsmandatorygroup OBJECT-GROUP OBJECTS { mefsoamlmcurrentavailstatsindex, mefsoamlmcurrentavailstatsstarttime, mefsoamlmcurrentavailstatselapsedtime, mefsoamlmcurrentavailstatssuspect, mefsoamlmcurrentavailstatsforwardavailable, mefsoamlmcurrentavailstatsbackwardavailable, mefsoamlmcurrentavailstatsforwardunavailable, mefsoamlmcurrentavailstatsbackwardunavailable Mandatory objects for the Service OAM LM Current Availability group. ::= { mefsoampmmibgroups 7 mefsoamlmcurrentavailstatsoptionalgroup OBJECT-GROUP OBJECTS { mefsoamlmcurrentavailstatsforwardhighloss, mefsoamlmcurrentavailstatsbackwardhighloss, mefsoamlmcurrentavailstatsforwardconsecutivehighloss, mefsoamlmcurrentavailstatsbackwardconsecutivehighloss, mefsoamlmcurrentavailstatsforwardminflr, mefsoamlmcurrentavailstatsforwardmaxflr, mefsoamlmcurrentavailstatsforwardavgflr, mefsoamlmcurrentavailstatsbackwardminflr, mefsoamlmcurrentavailstatsbackwardmaxflr, mefsoamlmcurrentavailstatsbackwardavgflr contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 141

8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 Optional objects for the Service OAM LM Current Availabilty Stats group. ::= { mefsoampmmibgroups 8 mefsoamlmcurrentstatsmandatorygroup OBJECT-GROUP OBJECTS { mefsoamlmcurrentstatsindex, mefsoamlmcurrentstatsstarttime, mefsoamlmcurrentstatselapsedtime, mefsoamlmcurrentstatssuspect, mefsoamlmcurrentstatssoampdussent, mefsoamlmcurrentstatssoampdusreceived Mandatory objects for the Service OAM LM current statistics group. ::= { mefsoampmmibgroups 9 mefsoamlmcurrentstatsoptionalgroup OBJECT-GROUP OBJECTS { mefsoamlmcurrentstatsforwardtransmittedframes, mefsoamlmcurrentstatsforwardreceivedframes, mefsoamlmcurrentstatsbackwardtransmittedframes, mefsoamlmcurrentstatsbackwardreceivedframes, mefsoamlmcurrentstatsforwardminflr, mefsoamlmcurrentstatsforwardmaxflr, mefsoamlmcurrentstatsforwardavgflr, mefsoamlmcurrentstatsbackwardminflr, mefsoamlmcurrentstatsbackwardmaxflr, mefsoamlmcurrentstatsbackwardavgflr Optional objects for the Service OAM LM Current Stats group. ::= { mefsoampmmibgroups 10 mefsoamlmhistoryavailstatsmandatorygroup OBJECT-GROUP OBJECTS { mefsoamlmhistoryavailstatsendtime, mefsoamlmhistoryavailstatselapsedtime, mefsoamlmhistoryavailstatssuspect, mefsoamlmhistoryavailstatsforwardavailable, mefsoamlmhistoryavailstatsbackwardavailable, mefsoamlmhistoryavailstatsforwardunavailable, mefsoamlmhistoryavailstatsbackwardunavailable Mandatory objects for the Service OAM Availability LM history statistics group. ::= { mefsoampmmibgroups 11 mefsoamlmhistoryavailstatsoptionalgroup OBJECT-GROUP OBJECTS { mefsoamlmhistoryavailstatsforwardhighloss, mefsoamlmhistoryavailstatsbackwardhighloss, mefsoamlmhistoryavailstatsforwardconsecutivehighloss, mefsoamlmhistoryavailstatsbackwardconsecutivehighloss, mefsoamlmhistoryavailstatsforwardminflr, mefsoamlmhistoryavailstatsforwardmaxflr, mefsoamlmhistoryavailstatsforwardavgflr, mefsoamlmhistoryavailstatsbackwardminflr, mefsoamlmhistoryavailstatsbackwardmaxflr, contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 142

8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 mefsoamlmhistoryavailstatsbackwardavgflr Optional objects for the Service OAM Availability LM history statistics group. ::= { mefsoampmmibgroups 12 mefsoamlmhistorystatsmandatorygroup OBJECT-GROUP OBJECTS { mefsoamlmhistorystatsendtime, mefsoamlmhistorystatselapsedtime, mefsoamlmhistorystatssuspect, mefsoamlmhistorystatssoampdussent, mefsoamlmhistorystatssoampdusreceived Mandatory objects for the Service OAM LM history statistics group. ::= { mefsoampmmibgroups 13 mefsoamlmhistorystatsoptionalgroup OBJECT-GROUP OBJECTS { mefsoamlmhistorystatsforwardtransmittedframes, mefsoamlmhistorystatsforwardreceivedframes, mefsoamlmhistorystatsbackwardtransmittedframes, mefsoamlmhistorystatsbackwardreceivedframes, mefsoamlmhistorystatsforwardminflr, mefsoamlmhistorystatsforwardmaxflr, mefsoamlmhistorystatsforwardavgflr, mefsoamlmhistorystatsbackwardminflr, mefsoamlmhistorystatsbackwardmaxflr, mefsoamlmhistorystatsbackwardavgflr Optional objects for the Service OAM LM History Stats group. ::= { mefsoampmmibgroups 14 mefsoamdmcfgmandatorygroup OBJECT-GROUP OBJECTS { mefsoamdmcfgtype, mefsoamdmcfgenabled, mefsoamdmcfgmeasurementenable, mefsoamdmcfgmessageperiod, mefsoamdmcfgpriority, mefsoamdmcfgframesize, mefsoamdmcfgdatapattern, mefsoamdmcfgmeasurementinterval, mefsoamdmcfgnumintervalsstored, mefsoamdmcfgdestmacaddress, mefsoamdmcfgdestmepid, mefsoamdmcfgdestismepid, mefsoamdmcfgstarttimetype, mefsoamdmcfgfixedstartdateandtime, mefsoamdmcfgrelativestarttime, mefsoamdmcfgstoptimetype, mefsoamdmcfgfixedstopdateandtime, mefsoamdmcfgrelativestoptime, mefsoamdmcfgrepetitiontime, contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 143

8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 mefsoamdmcfgalignmeasurementintervals, mefsoamdmcfgnummeasbinsperframedelayinterval, mefsoamdmcfgnummeasbinsperinterframedelayvariationinterval, mefsoamdmcfgnummeasbinsperframedelayrangeinterval, mefsoamdmcfgsessiontype, mefsoamdmcfgsessionstatus, mefsoamdmcfghistoryclear, mefsoamdmcfgrowstatus Mandatory objects for the Service OAM DM configuration group. ::= { mefsoampmmibgroups 15 mefsoamdmcfgoptionalgroup OBJECT-GROUP OBJECTS { mefsoamdmcfgversion, mefsoamdmcfgtesttlvincluded, mefsoamdmcfgtesttlvpattern, mefsoamdmcfgsourcemacaddress, mefsoamdmcfgalignmeasurementoffset, mefsoamdmcfginterframedelayvariationselectionoffset Optional objects for the Service OAM DM Configuration group. ::= { mefsoampmmibgroups 16 mefsoamdmcfgmeasbinmandatorygroup OBJECT-GROUP OBJECTS { mefsoamdmcfgmeasbinlowerbound Mandatory objects for the Service OAM DM measurement bin configuration group. ::= { mefsoampmmibgroups 17 mefsoamdmmeasuredstatsoptionalgroup OBJECT-GROUP OBJECTS { mefsoamdmmeasuredstatsframedelaytwoway, mefsoamdmmeasuredstatsframedelayforward, mefsoamdmmeasuredstatsframedelaybackward, mefsoamdmmeasuredstatsifdvtwoway, mefsoamdmmeasuredstatsifdvforward, mefsoamdmmeasuredstatsifdvbackward Optional objects for the Service OAM DM Measured Stats group. ::= { mefsoampmmibgroups 18 mefsoamdmcurrentstatsmandatorygroup OBJECT-GROUP OBJECTS { mefsoamdmcurrentstatsindex, mefsoamdmcurrentstatsstarttime, mefsoamdmcurrentstatselapsedtime, mefsoamdmcurrentstatssuspect, mefsoamdmcurrentstatsframedelaytwowaymin, mefsoamdmcurrentstatsframedelaytwowaymax, mefsoamdmcurrentstatsframedelaytwowayavg, mefsoamdmcurrentstatsframedelayforwardmin, mefsoamdmcurrentstatsframedelayforwardmax, contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 144

8194 8195 8196 8197 8198 8199 8200 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 mefsoamdmcurrentstatsframedelayforwardavg, mefsoamdmcurrentstatsframedelaybackwardmin, mefsoamdmcurrentstatsframedelaybackwardmax, mefsoamdmcurrentstatsframedelaybackwardavg, mefsoamdmcurrentstatsifdvforwardmin, mefsoamdmcurrentstatsifdvforwardmax, mefsoamdmcurrentstatsifdvforwardavg, mefsoamdmcurrentstatsifdvbackwardmin, mefsoamdmcurrentstatsifdvbackwardmax, mefsoamdmcurrentstatsifdvbackwardavg, mefsoamdmcurrentstatsframedelayrangeforwardmax, mefsoamdmcurrentstatsframedelayrangeforwardavg, mefsoamdmcurrentstatsframedelayrangebackwardmax, mefsoamdmcurrentstatsframedelayrangebackwardavg, mefsoamdmcurrentstatssoampdussent, mefsoamdmcurrentstatssoampdusreceived Mandatory objects for the Service OAM DM current statistics group. ::= { mefsoampmmibgroups 19 mefsoamdmcurrentstatsoptionalgroup OBJECT-GROUP OBJECTS { mefsoamdmcurrentstatsifdvtwowaymin, mefsoamdmcurrentstatsifdvtwowaymax, mefsoamdmcurrentstatsifdvtwowayavg, mefsoamdmcurrentstatsframedelayrangetwowaymax, mefsoamdmcurrentstatsframedelayrangetwowayavg Optional objects for the Service OAM DM current statistics group. ::= { mefsoampmmibgroups 20 mefsoamdmcurrentstatsbinsmandatorygroup OBJECT-GROUP OBJECTS { mefsoamdmcurrentstatsbinscounter Mandatory objects for the Service OAM DM current statistics bin group. ::= { mefsoampmmibgroups 21 mefsoamdmhistorystatsmandatorygroup OBJECT-GROUP OBJECTS { mefsoamdmhistorystatsendtime, mefsoamdmhistorystatselapsedtime, mefsoamdmhistorystatssuspect, mefsoamdmhistorystatsframedelaytwowaymin, mefsoamdmhistorystatsframedelaytwowaymax, mefsoamdmhistorystatsframedelaytwowayavg, mefsoamdmhistorystatsframedelayforwardmin, mefsoamdmhistorystatsframedelayforwardmax, mefsoamdmhistorystatsframedelayforwardavg, mefsoamdmhistorystatsframedelaybackwardmin, mefsoamdmhistorystatsframedelaybackwardmax, mefsoamdmhistorystatsframedelaybackwardavg, mefsoamdmhistorystatsifdvforwardmin, mefsoamdmhistorystatsifdvforwardmax, mefsoamdmhistorystatsifdvforwardavg, mefsoamdmhistorystatsifdvbackwardmin, mefsoamdmhistorystatsifdvbackwardmax, contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 145

8258 8259 8260 8261 8262 8263 8264 8265 8266 8267 8268 8269 8270 8271 8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 mefsoamdmhistorystatsifdvbackwardavg, mefsoamdmhistorystatsframedelayrangeforwardmax, mefsoamdmhistorystatsframedelayrangeforwardavg, mefsoamdmhistorystatsframedelayrangebackwardmax, mefsoamdmhistorystatsframedelayrangebackwardavg, mefsoamdmhistorystatssoampdussent, mefsoamdmhistorystatssoampdusreceived Mandatory objects for the Service OAM DM history statistics group. ::= { mefsoampmmibgroups 22 mefsoamdmhistorystatsoptionalgroup OBJECT-GROUP OBJECTS { mefsoamdmhistorystatsifdvtwowaymin, mefsoamdmhistorystatsifdvtwowaymax, mefsoamdmhistorystatsifdvtwowayavg, mefsoamdmhistorystatsframedelayrangetwowaymax, mefsoamdmhistorystatsframedelayrangetwowayavg Optional objects for the Service OAM DM history statistics group. ::= { mefsoampmmibgroups 23 mefsoamdmhistorystatsbinsmandatorygroup OBJECT-GROUP OBJECTS { mefsoamdmhistorystatsbinscounter Mandatory objects for the Service OAM DM history statistics bin group. ::= { mefsoampmmibgroups 24 mefsoamlmthresholdmandatorygroup OBJECT-GROUP OBJECTS { mefsoamlmthresholdcfgenable, mefsoamlmthresholdcfgmaxflrforwardthreshold, mefsoamlmthresholdcfgavgflrforwardthreshold, mefsoamlmthresholdcfgmaxflrbackwardthreshold, mefsoamlmthresholdcfgavgflrbackwardthreshold, mefsoamlmthresholdcfgforwardunavailcountthreshold, mefsoamlmthresholdcfgforwardavailratiothreshold, mefsoamlmthresholdcfgbackwardunavailcountthreshold, mefsoamlmthresholdcfgbackwardavailratiothreshold, mefsoamlmthresholdcfgrowstatus Mandatory objects for the Service OAM LM threshold group. ::= { mefsoampmmibgroups 25 mefsoamlmthresholdoptionalgroup OBJECT-GROUP OBJECTS { mefsoamlmthresholdcfgforwardhighlossthreshold, mefsoamlmthresholdcfgforwardconsecutivehighlossthreshold, mefsoamlmthresholdcfgbackwardhighlossthreshold, mefsoamlmthresholdcfgbackwardconsecutivehighlossthreshold, mefsoamlmthresholdcfgmeasuredflrforwardthreshold, mefsoamlmthresholdcfgmeasuredflrbackwardthreshold contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 146

8322 8323 8324 8325 8326 8327 8328 8329 8330 8331 8332 8333 8334 8335 8336 8337 8338 8339 8340 8341 8342 8343 8344 8345 8346 8347 8348 8349 8350 8351 8352 8353 8354 8355 8356 8357 8358 8359 8360 8361 8362 8363 8364 8365 8366 8367 8368 8369 8370 8371 8372 8373 8374 8375 8376 8377 8378 8379 8380 8381 8382 8383 8384 8385 Optional objects for the Service OAM LM Threshold group. ::= { mefsoampmmibgroups 26 mefsoamdmthresholdmandatorygroup OBJECT-GROUP OBJECTS { mefsoamdmthresholdcfgenable, mefsoamdmthresholdcfgmaxframedelaytwowaythreshold, mefsoamdmthresholdcfgavgframedelaytwowaythreshold, mefsoamdmthresholdcfgmaxframedelayforwardthreshold, mefsoamdmthresholdcfgavgframedelayforwardthreshold, mefsoamdmthresholdcfgmaxifdvforwardthreshold, mefsoamdmthresholdcfgavgifdvforwardthreshold, mefsoamdmthresholdcfgmaxframedelayrangeforwardthreshold, mefsoamdmthresholdcfgavgframedelayrangeforwardthreshold, mefsoamdmthresholdcfgmaxframedelaybackwardthreshold, mefsoamdmthresholdcfgavgframedelaybackwardthreshold, mefsoamdmthresholdcfgmaxifdvbackwardthreshold, mefsoamdmthresholdcfgavgifdvbackwardthreshold, mefsoamdmthresholdcfgmaxframedelayrangebackwardthreshold, mefsoamdmthresholdcfgavgframedelayrangebackwardthreshold, mefsoamdmthresholdcfgrowstatus Mandatory objects for the Service OAM DM threshold group. ::= { mefsoampmmibgroups 27 mefsoamdmthresholdoptionalgroup OBJECT-GROUP OBJECTS { mefsoamdmthresholdcfgmeasuredifdvtwowaythreshold, mefsoamdmthresholdcfgmeasuredframedelaytwowaythreshold, mefsoamdmthresholdcfgmeasuredframedelayforwardthreshold, mefsoamdmthresholdcfgmeasuredifdvforwardthreshold, mefsoamdmthresholdcfgmeasuredframedelaybackwardthreshold, mefsoamdmthresholdcfgmeasuredifdvbackwardthreshold, mefsoamdmthresholdcfgmaxifdvtwowaythreshold, mefsoamdmthresholdcfgavgifdvtwowaythreshold, mefsoamdmthresholdcfgmaxframedelayrangetwowaythreshold, mefsoamdmthresholdcfgavgframedelayrangetwowaythreshold Optional objects for the Service OAM DM threshold group. ::= { mefsoampmmibgroups 28 mefsoampmnotificationsmandatorygroup NOTIFICATION-GROUP NOTIFICATIONS { mefsoamavailabilitychangealarm, mefsoamlmsessionstartstopalarm, mefsoamdmsessionstartstopalarm Mandatory notifications for the SOAM PM Notifications group. ::= { mefsoampmmibgroups 29 mefsoampmnotificationsoptionalgroup NOTIFICATION-GROUP NOTIFICATIONS { mefsoampmthresholdcrossingalarm contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 147

8386 8387 8388 8389 8390 8391 8392 8393 8394 8395 8396 8397 8398 8399 8400 8401 8402 8403 8404 8405 8406 8407 8408 8409 8410 8411 8412 8413 8414 8415 8416 8417 8418 8419 8420 8421 8422 8423 8424 8425 8426 8427 8428 8429 8430 8431 8432 8433 8434 8435 8436 8437 8438 8439 8440 8441 8442 8443 8444 8445 8446 8447 8448 8449 Optional objects for the Service OAM PM Notifications group. ::= { mefsoampmmibgroups 30 mefsoampmnotificationcfgmandatorygroup OBJECT-GROUP OBJECTS { mefsoampmnotificationcfgalarminterval, mefsoampmnotificationcfgalarmenable Mandatory objects for the SOAM PM Notification Configuration group. ::= { mefsoampmmibgroups 31 mefsoampmnotificationobjmandatorygroup OBJECT-GROUP OBJECTS { mefsoampmnotificationobjdateandtime, mefsoampmnotificationobjsuspect, mefsoampmnotificationobjdestinationmep, mefsoampmnotificationobjpriority Mandatory objects for the SOAM PM Notification Object group. ::= { mefsoampmmibgroups 32 mefsoampmnotificationobjoptionalgroup OBJECT-GROUP OBJECTS { mefsoampmnotificationobjthresholdconfig, mefsoampmnotificationobjthresholdid, mefsoampmnotificationobjthresholdvalue, mefsoampmnotificationobjcrossingtype Optional objects for the Service OAM PM Notifications group. ::= { mefsoampmmibgroups 33 -- ****************************************************************** -- SOAM-PM MIB Module Compliance statements -- ****************************************************************** mefsoampmmibcompliance MODULE-COMPLIANCE The compliance statement for the Ethernet Service OAM PM MIB. MODULE MANDATORY-GROUPS { mefsoampmmepmandatorygroup, mefsoamlmcfgmandatorygroup, mefsoamlmmeasuredstatsmandatorygroup, mefsoamlmcurrentavailstatsmandatorygroup, mefsoamlmcurrentstatsmandatorygroup, mefsoamlmhistoryavailstatsmandatorygroup, mefsoamlmhistorystatsmandatorygroup, mefsoamdmcfgmandatorygroup, mefsoamdmcfgmeasbinmandatorygroup, mefsoamdmcurrentstatsmandatorygroup, mefsoamdmcurrentstatsbinsmandatorygroup, mefsoamdmhistorystatsmandatorygroup, mefsoamdmhistorystatsbinsmandatorygroup, mefsoamlmthresholdmandatorygroup, mefsoamdmthresholdmandatorygroup, mefsoampmnotificationsmandatorygroup, contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 148

8450 8451 8452 8453 8454 8455 8456 8457 8458 8459 8460 8461 8462 8463 8464 8465 8466 8467 8468 8469 8470 8471 8472 8473 8474 8475 8476 8477 8478 8479 8480 8481 8482 8483 8484 8485 8486 8487 8488 8489 8490 8491 8492 8493 8494 8495 8496 8497 8498 8499 8500 8501 8502 8503 8504 8505 END mefsoampmnotificationcfgmandatorygroup, mefsoampmnotificationobjmandatorygroup GROUP mefsoampmmepoptionalgroup The mefsoampmmepoptionalgroup is an optional requirement. GROUP mefsoamlmcfgoptionalgroup The mefsoamlmcfgoptionalgroup is an optional requirement. GROUP mefsoamlmmeasuredstatsoptionalgroup The mefsoamlmmeasuredstatsoptionalgroup is an optional requirement. GROUP mefsoamlmcurrentavailstatsoptionalgroup The mefsoamlmcurrentavailstatsoptionalgroup is an optional requirement. GROUP mefsoamlmcurrentstatsoptionalgroup The mefsoamlmcurrentstatsoptionalgroup is an optional requirement. GROUP mefsoamlmhistoryavailstatsoptionalgroup The mefsoamlmcurrentstatsoptionalgroup is an optional requirement. GROUP mefsoamlmhistorystatsoptionalgroup The mefsoamlmhistorystatsoptionalgroup is an optional requirement. GROUP mefsoamdmcfgoptionalgroup The mefsoamdmcfgoptionalgroup is an optional requirement. GROUP mefsoamdmmeasuredstatsoptionalgroup The mefsoamdmmeasuredstatsoptionalgroup is an optional requirement. GROUP mefsoamdmcurrentstatsoptionalgroup The mefsoamdmcurrentstatsoptionalgroup is an optional requirement. GROUP mefsoamdmhistorystatsoptionalgroup The mefsoamdmhistorystatsoptionalgroup is an optional requirement. GROUP mefsoamlmthresholdoptionalgroup The mefsoamlmthresholdoptionalgroup is an optional requirement. GROUP mefsoamdmthresholdoptionalgroup The mefsoamdmthresholdoptionalgroup is an optional requirement. GROUP mefsoampmnotificationsoptionalgroup The mefsoampmnotificationsoptionalgroup is an optional requirement. GROUP mefsoampmnotificationobjoptionalgroup The mefsoampmnotificationobjoptionalgroup is an optional requirement. ::= { mefsoampmmibcompliances 1 contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 149

8506 8507 8508 8509 8510 8511 8512 8513 8514 8515 8516 8517 8518 8519 8520 8521 8522 8523 8524 8525 8526 8527 8528 8529 8530 8531 8532 8533 8534 8535 8536 8537 8538 8539 8540 8541 9. References [1] Bradner, S., Key words for use in RFCs to Indicate Requirement Levels, RFC 2119, March 1997. (Normative) [2] McCloghrie, K., et al., Structure of Management Information Version 2 (SMIv2), RFC 2578, April 1999. [3] Harrington, D, et al, An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks, RFC 3411, December 2002. [4] Heard, C., Guidelines for Authors and Reviewers of MIB Documents, RFC 4181, September, 2005. [5] Metro Ethernet Forum, MEF 4, Metro Ethernet Network Architecture Framework - Part 1: Generic Framework, May 2004. [6] Metro Ethernet Forum, MEF 7.1, Phase 2 EMS-NMS Information Model, October 2009. [7] Metro Ethernet Forum, MEF 10.2.1, Ethernet Services Attributes Phase 2, January 2011. [8] Metro Ethernet Forum, MEF 10.2, Ethernet Services Attributes Phase 2, October 2009. [9] Metro Ethernet Forum, MEF 15, Requirements for Management of Metro Ethernet Phase 1 Network Elements, November 2005. [10] Metro Ethernet Forum, MEF 17, Service OAM Requirements & Framework Phase 1, April 2007. [11] Metro Ethernet Forum, MEF 26, External Network Network Interface (ENNI) - Phase 1, January 2010 [12] Metro Ethernet Forum, MEF 30, Service OAM Fault Management Implementation Agreement, Janaury 2011 [13] Metro Ethernet Forum, MEF 35, Service OAM Performance Monitoring Implementation Agreement, January 2012 [14] Metro Ethernet Forum, MEF 31, Service OAM Fault Management Definition of Managed Objects, Janaury 2011 [15] Metro Ethernet Forum, MEF 31.0.1, Service OAM Fault Management Definition of Managed Objects, Janaury 2012 [16] International Telecommunication Union, Recommendation G.8011/Y.1307, Ethernet over Transport Ethernet services framework, August 2004. [17] International Telecommunication Union, Recommendation G.8021/Y.1341, Characteristics of Ethernet transport network equipment functional blocks, December 2007. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 150

8542 8543 8544 8545 8546 8547 8548 8549 8550 8551 8552 8553 8554 8555 8556 8557 8558 8559 8560 8561 8562 8563 8564 8565 8566 8567 8568 8569 8570 [18] International Telecommunication Union, Recommendation G.8051/Y.1345, Management aspects of the Ethernet-over-Transport (EoT) capable network element, October 2007. [19] International Telecommunication Union, Recommendation Q.840.1, Requirements and Analysis for NMS-EMS Management Interface of Ethernet over Transport and Metro Ethernet Network, March 2007 [20] International Telecommunication Union, Recommendation Y.1731, OAM functions and mechanisms for Ethernet based Networks, February 2011. [21] IEEE Std 802.1Q-2005, IEEE Standard for Local and metropolitan area networks Virtual Bridged Local Area Networks, 19 May 2006 [22] IEEE Std 802.1ad-2005, IEEE Standard for Local and metropolitan area networks Virtual Bridged Local Area Networks Amendment 4: Provider Bridges, May 2006. [23] IEEE Std 802.1ag-2007, IEEE Standard for Local and metropolitan area networks Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault Management, December 2007. [24] IEEE Std 802.3-2008, IEEE Standard for Information technology Telecommunications and information exchange between systems Local and metropolitan area networks Specific requirements Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications, 26 December 2008. [25] IEEE Std 802.1ap-2008, IEEE Standard for Local and metropolitan area networks - Virtual Bridged Local Area Networks Amendment 8: Management Information Base (MIB) Definitions for VLAN Bridges, March 2009 [26] International Organization for Standardization, International Standard 8824 Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), December, 1987. [27] Lam, K., et al., Network Management Requirements for MPLS-based Transport Networks, RFC 5951, September 2010. contain the following statement: Reproduced with permission of the Metro Ethernet Forum. No user of Page 151