SIST EN 301 384 V1.1.2:2003
(Main)Telecommunications Management Network (TMN); Performance monitoring for Plesiochronous Digital Hierarchy (PDH) interfaces; Information model for the Network Element (NE) view
- Abstract
Filling the missing registration identifiers.
- Status
- Published
- Publication Date
- 31-Oct-2003
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Nov-2003
- Due Date
- 01-Nov-2003
- Completion Date
- 01-Nov-2003
SIST EN 301 384 V1.1.2:2003 is the Slovenian standard identical to ETSI EN 301 384 Version 1.1.2. It specifies a Telecommunications Management Network (TMN) information model for performance monitoring of Plesiochronous Digital Hierarchy (PDH) interfaces from the Network Element (NE) view, so that an element manager can read counters, alarms and history data in a consistent way.
What does SIST EN 301 384 V1.1.2:2003 specify?
SIST EN 301 384 V1.1.2:2003 specifies the managed-object model for PDH performance monitoring in the NE view. The model is aimed at the information exchanged across TMN interfaces, especially the element-manager to element interface, and it is organized as clauses on the model, object classes, packages, attributes, actions, notifications, name bindings and ASN.1 definitions.
The scope is narrow and practical. SIST EN 301 384 V1.1.2:2003 defines the information model for PDH performance monitoring, but leaves out the protocol stack, network-level management processes, application contexts, conformance requirements, and information models for other systems or equipment.
Clause 4 gives the performance monitoring management model. Clause 5 defines the managed object classes. Clause 6 defines the special packages, and clauses 7 to 11 cover attributes, actions, notifications, name bindings and the ASN.1 module.
What are the key requirements of SIST EN 301 384 V1.1.2:2003?
SIST EN 301 384 V1.1.2:2003 builds its PDH model on the TMN and Q.822 performance-management framework, and it reuses the SDH/PDH management patterns from the referenced recommendations. In practice, this means the PDH counters and alarms are modeled as TMN managed objects rather than as ad hoc vendor-specific data.
- Clause 5 defines current-data classes for unidirectional, near-end, far-end and bidirectional monitoring. These classes hold the live counts for a monitored point, so a manager can read the current state of a termination point or trail.
- The monitored events include BBE, ES, SES, FEES, FESES and, where supported, UAS, CSES, FEBBE and FECSES. This tells implementers which performance counters must be exposed for each monitoring case.
- Near-end and far-end monitoring are kept separate. That matters because availability and error counts are derived from conditions on the correct end of the PDH path, not from a combined view.
- Threshold crossing generates a QOS alarm. The model says the alarm is raised when a threshold is reached or crossed, and it clears at the end of the granularity period unless another crossing occurs. Operators use this to spot repeated degradation, not just single spikes.
- Unavailable time has explicit entry and exit rules. An unavailable period starts after 10 consecutive SES and ends after 10 consecutive non-SES, and performance-event counts other than UAS are inhibited during unavailable time. This prevents unavailable periods from distorting ordinary error totals.
- Threshold-reset variants are defined for 15-minute granularity. They use fixed-window reset behavior and support high/low threshold handling through the threshold-data list, so a management system can treat short-term alarms differently from ordinary accumulation.
- Clause 10 defines name bindings for current and history objects. History objects are created at the end of each granularity period and are linked by scannerId or historyDataId, which is how a manager finds the right stored observation.
What terms does SIST EN 301 384 V1.1.2:2003 define?
- Telecommunications Management Network (TMN) - the management architecture used to exchange the performance-monitoring information.
- Network Element (NE) - the equipment domain visible at the element-manager to element interface.
- Plesiochronous Digital Hierarchy (PDH) - the transport hierarchy whose interfaces and trails are monitored.
- Background Block Error (BBE) - a block-error performance event used in the current-data model.
- Severely Errored Second (SES) - a one-second interval with severe errors that drives unavailable-time logic.
- Unavailable Seconds (UAS) - one-second intervals that belong to an unavailable period.
- Threshold Reset (TR) - the class variant that uses threshold-reset behavior with 15-minute granularity.
Who uses SIST EN 301 384 V1.1.2:2003?
SIST EN 301 384 V1.1.2:2003 is used by telecom equipment vendors, TMN and element-manager developers, and operators who monitor PDH transmission equipment. It is also relevant to quality and conformance teams that need to model counters, alarms, history retention and name bindings in a management system.
What changed in SIST EN 301 384 V1.1.2:2003 from the previous edition?
SIST EN 301 384 V1.1.2:2003 is identified as Version 1.1.2, and the history also records Version 1.1.1 as the earlier publication. The history shows a one-step approval procedure before the February 2001 publication of Version 1.1.2.
Which standards are used with SIST EN 301 384 V1.1.2:2003?
- ITU-T G.784 and ETSI EN 301 167 - provide the SDH management and performance-monitoring framework that this PDH model follows.
- ITU-T M.3010 - gives the TMN architecture for the interfaces used to exchange the information.
- ETSI EN 300 371 - provides the PDH NE information model used for related name bindings and sink objects.
- ITU-T M.2120 and ITU-T Q.822 - supply the maintenance and Q3 performance-management foundations for the object model.
- ETSI EN 300 417-1-1 and ETSI EN 300 417-5-1 - define the performance primitives and PDH path-layer functions behind the counters.
- ITU-T G.826 - defines the error-performance events and unavailable-time entry and exit criteria used by the model.
- ITU-T X.739 and ITU-T M.3100 - provide generic management attributes such as granularityPeriod and currentProblemList.
What does the SIST EN 301 384 V1.1.2:2003 document contain?
Clause 5 contains the managed object class definitions for current data and history data, including near-end, far-end, bidirectional and threshold-reset variants. Clause 6 defines imported and PDH-specific packages, while clause 10 defines the name bindings that create contained history objects under current-data objects. Clause 11 provides the ASN.1 module PDHPMASN1, and Figures 1 to 3 show the inheritance of the current-data classes, the history-data classes and the naming tree.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 301 384 V1.1.2:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Telecommunications Management Network (TMN); Performance monitoring for Plesiochronous Digital Hierarchy (PDH) interfaces; Information model for the Network Element (NE) view". This standard covers: Filling the missing registration identifiers.
Filling the missing registration identifiers.
SIST EN 301 384 V1.1.2:2003 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 384 V1.1.2:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Telekomunikacijsko upravljavno omrežje (TMN) - Nadzorovanje zmogljivosti vmesnikov pleziohrone digitalne hierarhije (PDH) - Informacijski model, gledano s strani omrežnega elementa (NE)Telecommunications Management Network (TMN); Performance monitoring for Plesiochronous Digital Hierarchy (PDH) interfaces; Information model for the Network Element (NE) view33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 384 Version 1.1.2SIST EN 301 384 V1.1.2:2003en01-november-2003SIST EN 301 384 V1.1.2:2003SLOVENSKI
STANDARD
ETSIEN301384V1.1.2(2001-02)EuropeanStandard(Telecommunicationsseries)TelecommunicationsManagementNetwork(TMN);PerformancemonitoringforPlesiochronousDigitalHierarchy(PDH)interfaces;InformationmodelfortheNetworkElement(NE)viewSIST EN 301 384 V1.1.2:2003
ETSIETSIEN301384V1.1.2(2001-02)2ReferenceREN/TMN-00050KeywordsNE,PDH,performance,Q3interface,transmissionETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 301 384 V1.1.2:2003
ETSIETSIEN301384V1.1.2(2001-02)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.63Abbreviations.74PerformanceMonitoringManagementModel.75Managedobjectclassdefinitions.76Packages.137Attributes.138Actions.139Notifications.1310Namebindings.1311ASN.1definitions.15History.17SIST EN 301 384 V1.1.2:2003
ETSIETSIEN301384V1.1.2(2001-02)4IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeTelecommunicationsManagementNetwork(TMN).NationaltranspositiondatesDateofadoptionofthisEN:23February2001DateoflatestannouncementofthisEN(doa):31May2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30November2001DateofwithdrawalofanyconflictingNationalStandard(dow):30November2001SIST EN 301 384 V1.1.2:2003
ETSIETSIEN301384V1.1.2(2001-02)51ScopeThepresentdocumentprovidesaninformationmodelfortheperformancemonitoringofSynchronousDigitalHierarchy(SDH)network.Thismodeldescribesthemanagedobjectclassesandtheirpropertiesfortheperformancemonitoringfunction,asdefinedinITU-TRecommendationG.784[1]andEN301167[2]andasrelatedtoSDHNetworkElements(NEs).TheseobjectsareusefultodescribeinformationexchangedacrossinterfacesdefinedinITU-TRecommendationM.3010[3]TelecommunicationsManagementNetwork(TMN)architectureforthemanagementoftheperformancemonitoringfunction.PDHperformancemonitoringfunctionsareusedtomonitorspecifiedperformanceeventsofspecifiedterminationpointsmanagedobjectsasdefinedinEN300371[4]andtoreporttheseperformancedata,aswellasqualityofservicealarmstoitsmanagingsystemaccordingtoagivenschedule.ITU-TRecommendationM.2120[5]definesmaintenanceoftransportnetwork,ITU-TRecommendationG.784[1]definesthemanagementofSDHbasedNE.ThepresentdocumentdefinestheobjectmodelbasedonITU-TRecommendationQ.822[6]accordingtotherequirementsdescribedinITU-TRecommendationG.784[1],EN301167[2]andITU-TRecommendationM.2120[5].ThismodelusesgenericmechanismdefinedinITU-TRecommendationQ.822[6].Thepresentdocumentdefines:-aninformationmodel,asrelatedtotheperformancemonitoringfunctionforthePlesiochronousDigitalHierarchy(PDH).Thepresentdocumentdoesnotdefine:-theprotocolstacktobeusedformessagecommunication;-thenetworklevelmanagementprocesses;-theapplicationcontexts;-theconformancerequirementstobemetbyanimplementationofthisinformationmodel;-informationmodelsforothersystemsorequipment.Theinformationmodeldefinedhere(andthecorrespondingmessageset)isconcernedwiththemanagementofNEs,theequipmentbywhichtheyareimplementedandthefunctionscontainedwithinthem.Moreprecisely,itappliestoanequipmentdomainvisibleattheelementmanagertoelementinterfaceandisonlyconcernedwithinformationavailablewithinthatdomain.Informationpropertothedomainofanetworklevelmanagementprocessisnotincludedwithinthismodel.SIST EN 301 384 V1.1.2:2003
ETSIETSIEN301384V1.1.2(2001-02)62ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,subsequentrevisionsdoapply.[1]ITU-TRecommendationG.784(1994):"SynchronousDigitalHierarchy(SDH)management".[2]ETSIEN301167:"TransmissionandMultiplexing(TM);ManagementofSynchronousDigitalHierarchy(SDH)transmissionequipment;Faultmanagementandperformancemonitoring;Functionaldescription".[3]ITU-TRecommendationM.3010(1996):"Principlesforatelecommunicationsmanagementnetwork".[4]ETSIEN300371:"TelecommunicationsManagementNetwork(TMN);PlesiochronousDigitalHierarchy(PDH)informationmodelfortheNetworkElement(NE)view".[5]ITU-TRecommendationM.2120(1997):"PDHpath,sectionandtransmissionsystemandSDHpathandmultiplexsectionfaultdetectionandlocalizationprocedures".[6]ITU-TRecommendationQ.822(1994):"Stage1,stage2andstage3descriptionfortheQ3interface-Performancemanagement".[7]ITU-TRecommendationG.774-01(1996):"SynchronousDigitalHierarchy(SDH)bidirectionalperformancemonitoringforthenetworkelementview".[8]ITU-TRecommendationG.774-06(1997):"SynchronousDigitalHierarchy(SDH)unidirectionalperformancemonitoringforthenetworkelementview".[9]ETSIEN300417-1-1:"TransmissionandMultiplexing(TM);Genericrequirementsoftransportfunctionalityofequipment;Part1-1:Genericprocessesandperformance".[10]ETSIEN300417-5-1:"TransmissionandMultiplexing(TM);Genericrequirementsoftransportfunctionalityofequipment;Part5-1:PlesiochronousDigitalHierarchy(PDH)pathlayerfunctions".[11]ITU-TRecommendationG.826(1996):"Errorperformanceparametersandobjectivesforinternational,constantbitratedigitalpathsatorabovetheprimaryrate".[12]ITU-TRecommendationX.739(1993):"Informationtechnology-OpenSystemsInterconnection-Systemsmanagement:Metricobjectsandattributes".[13]ITU-TRecommendationM.3100(1995):"Genericnetworkinformationmodel".SIST EN 301 384 V1.1.2:2003
ETSIETSIEN301384V1.1.2(2001-02)73AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:BBEBackgroundBlockErrorCSESConsecutiveSeverelyErroredSecondsCTPConnectionTerminationPointESErroredSecondFEBBEFarEndBackgroundBlockErrorFEESFarEndErroredSecondFESESFarEndSeverelyErroredSecondsNENetworkElementPDHPlesiochronousDigitalHierarchySDHSynchronousDigitalHierarchySEMFSynchronousEquipmentManagementFunctionSESSeverelyErroredSecondTMNTelecommunicationsManagementNetworkTRThresholdResetTTPTrailTerminationPointUASUnavailableSeconds4PerformanceMonitoringManagementModelTheperformancemonitoringrequirementstobemetbytheSDHEquipmentManagementFunction(SEMF)aredescribedinITU-TRecommendationG.784[1],clause5.3andinEN301167[2],clauses5.1to5.2.ThefunctionalmodelgivenintheSEMFforperformancemonitoringofSDHsignalsisbasicallyapplicableforPDHsignalsaswell.5ManagedobjectclassdefinitionsInthecontextofthepresentdocument,theIMPORTSclausespecifiestheobjectclasseswhichcanbeinstantiatedintheScopeofthepresentdocument.TheIMPORTSclausedoesnotincludeuninstantiatedsuperclasses.BEGINIMPORTScurrentData,historyDataFROMQ822-PM-ASN1Module{itu(0)recommendation(0)q(17)q822(822)informationModel(0)managedObjectClass(3)};ENDPDHCurrentDataUnidirectionalpdhCurrentDataUnidirectionalMANAGEDOBJECTCLASSDERIVEDFROM"RecommendationQ.822[6]:1993":currentData;CHARACTERIZEDBY"RecommendationQ.822[6]:1993":zeroSuppressionPkg,"RecommendationQ.822[6]:1993":thresholdPkg,pdhCurrentDataUnidirectionalPackagePACKAGEBEHAVIOURpdhCurrentDataUnidirectionalBehaviour;ATTRIBUTES"RecommendationM.3100[13]:1995":currentProblemListGET,"RecommendationX.739[12]:1993":granularityPeriodPERMITTEDVALUESPDHPMASN1.UniDGranularityPeriod;;;CONDITIONALPACKAGES"RecommendationG.774-01[7]:1994":historyPackagePRESENTIF"aninstancedoesnotsupportflexibleassignmentofthehistorylength","RecommendationG.774-01[7]:1994":unavailableTimeAlarmPackagePRESENTIF"startingandendingofunavailableperiodhastobereportedandthegranularityperiodis24hours";REGISTEREDAS{en1384ObjectClass1};SIST EN 301 384 V1.1.2:2003
ETSIETSIEN301384V1.1.2(2001-02)8pdhCurrentDataUnidirectionalBehaviourBEHAVIOURDEFINEDAS"ThepdhCurrentDataUnidirectionalclassisusedtodefinegenericcharacteristicforunidirectionalPDHperformancemonitoringfromwhichsubclassesaredefinedinordertoholdperformanceeventcountsforaspecificmonitoringpoint.SubclassesofthisclassareusedinordertosupportperformancemonitoringofPDHtrailsatvariouslayersasdescribedinEN300417-5-1[10].TheperformancemonitoringeventsES,SESandBBEwhicharemonitoredbysomeofthesubclassesofthissubclassaredefinedinannexB/G.826[11]andarebasedontheperformanceeventprimitivesspecifiedinEN300417-1-1[9]andEN300417-5-1[10].ThegranularityPeriodattributecanonlybeassignedavalueatcreationtime.ThisclasscanonlycontainonereferencetoaninstanceofthethresholdDataobjectclassinthethresholdDataInstanceattribute.IfathresholdisreachedorcrossedthenthecurrentProblemListattributeshallindicateitwiththeprobablecausethresholdCrossed.Subclassofthisclassisusedtomonitorthenear-endorfar-endperformancedataofthetrail.Aperiodofunavailabletimebeginsattheonsetof10consecutiveSESevents.Thesetensecondsareconsideredtobepartofunavailabletime.Anewperiodofavailabletimebeginsattheonsetoftenconsecutivenon-SESevents.Thesetensecondsareconsideredtobepartofavailabletime.Theunavailabilityconditionsarekeptseparatefornearendandfarendmonitoring.Thismeansthatnearendunavailabilityisdeducedfromnearendconditionsonly(e.g.10consecutiveSESatthenearend)andfarendunavailabilityisdeducedfromfarendconditionsonly(e.g.10consecutiveSESatthefarend).Forthresholdresetsubclassesofthisobjectclassthefollowingrulesapply:NomorethanoneQOSalarmshallbegenerateduntiltherehasbeena15minutesrectangularfixedwindowwithlesserrorcountthanthelowerrorcountthresholdandnounavailableperiodexists.Toprovisionthehighandlowthresholdvalue,thecounterThresholdAttributListattributeoftheITU-TRecommendationQ.822[6]thresholdDataInstanceisused.Inthisattributeallthethresholds(highandlow)foreachnecessarycounterarestoredinalist.Thismeansforexample,thatthehighthresholdforESandthelowthresholdforESareindividuallystoredinthesamelist.Itisuptothenetworkelementtorecognizewhichisthehighandwhichisthelowone.IftheunavailableTimeAlarmPackageispresentandifanunavailableperiodstartsthenacommunicationalarmshallbesentwithaprobablecauseofUnavailableandthepresenceofthisunavailableconditionisindicatedbythecurrentProblemListattribute.IfanunavailableperiodisendingthenacommunicationalarmshallbesentwithaprobablecauseofUnavailableandaseverityofCleared.Anavailableconditionisindicatedbytheabsenceoftheunavailableconditioninthecurrentproblemlist.TheunavailableconditionhasnoeffectontheoperationalState.Eachsubclassofthisclassshalldefinetheperformanceattributesrequiredtoholdthemandatoryoroptionalperformanceevents.Theseperformanceeventcounts(exceptUAS)areinhibitedduringunavailabletimeofitsowndirection(atthenearendoratthefarend).AttributeswhicharedefinedinasubclassofthisclassshallbeincludedinhistoryinformationusingthehistoryData,oroneofitssubclass,unlessitisexplicitlyspecifiedinthesubclassofthisclassthataparticularattributebenotincluded.Eachsubclassofthisclassshallindicatewhichsubclassofthehistorydataisusedforhistoryretention.Thefollowingconditionalpackagesarenotusedinthisclass:filterSuppressionPkg,observedManagedObjectPkg.Concerningthesubclassesofthisclassthefollowingruleapplies:Ifasubclassofthisclasshasagranularityperiodof15minutes,itshouldbeeitheraninstancewiththethresholdresetfunctionalityoraninstancewithoutthisfunctionalityinstantiated(perterminationpoint),butnotboth.";PDHCurrentDataNearEndpdhCurrentDataNearEndMANAGEDOBJECTCLASSDERIVEDFROMpdhCurrentDataUnidirectional;CHARACTERIZEDBYpdhCurrentDataNearEndPackagePACKAGEBEHAVIOURpdhCurrentDataNearEndBehaviour;ATTRIBUTES"RecommendationG.774-01[7]:1994":bBEREPLACE-WITH-DEFAULTGET,"RecommendationG.774-01[7]:1994":eSREPLACE-WITH-DEFAULTGET,"RecommendationG.774-01[7]:1994":sESREPLACE-WITH-DEFAULTGET;;;CONDITIONALPACKAGES"RecommendationG.774-06[8]:1997":nearEndUASCurrentDataPackagePRESENTIF"aninstancesupportsit","RecommendationG.774-01[7]:1994":cSESCurrentDataPackagePRESENTIF"thegranularityperiodis15minutesandaninstancesupportsit";REGISTEREDAS{en1384ObjectClass2};pdhCurrentDataNearEndBehaviourBEHAVIOURDEFINEDAS"InstancesofthepdhCurrentDataNearEndmanagedobjectclassareusedtoholdthecurrentnearendregistercountsforaPDHpathduringacollectionperiod.Thefollowingperformanceprimitivesareobserved:DefectSeconds(pN_DS)andErroredBlocks(nN_B).SIST EN 301 384 V1.1.2:2003
ETSIETSIEN301384V1.1.2(2001-02)9TheseprimitivesareprovidedbymonitoringfunctionsrepresentedinsuperiorPDHterminationpointsandaredefinedinPDHpathlayersaccordingEN300417-5-1[10].Fortheseperformanceprimitivesthefollowingperformanceeventsaredefined:BBEBackgroundBlockError.ESErroredSecond.SESSeverelyErroredSecond.UASUnavailableSecond:Thiscounterisusedtostoreonesecondintervalspertainingtoanunavailabletimeperiodatthenearend.Inaddition,theoptionalperformanceeventCSES(ConsecutiveSES)isdefined.ThismanagedobjectclassusesthepdhPathHistoryDataNearEndmanagedobjectclassforhistoryretention.AQOSalarmshallbesentassoonasathresholdisreachedorcrossed.AttheendofthegranularityperiodtheQOSalarmisimplicitlyclearedand,providingtherearenootheroutstandingthresholdcrossingQOSalarms,thresholdCrossingisremovedfromthecurrentProblemList(i.e.nonotificationissent).AnewQOSalarmshallbesentifthethresholdisreachedorcrossedagainduringthenextgranularityperiod.Onlyonethresholdvalueperperformancecounterwillbesupported.";PDHCurrentDataNearEndThresholdResetpdhCurrentDataNearEndTRMANAGEDOBJECTCLASSDERIVEDFROMpdhCurrentDataNearEnd;CHARACTERIZEDBY"RecommendationG.774-01[7]:1994":thresholdResetPackage,pdhCurrentDataNearEndTRPackagePACKAGEATTRIBUTES"RecommendationX.739[12]:1993":granularityPeriodPERMITTEDVALUESPDHPMASN1.TRGranularityPeriod;;;REGISTEREDAS{en1384ObjectClass3};PDHCurrentDataFarEndpdhCurrentDataFarEndMANAGEDOBJECTCLASSDERIVEDFROMpdhCurrentDataUnidirectional;CHARACTERIZEDBYpdhFarEndCurrentDataPkg,pdhCurrentDataFarEndPac
...