ETSI EN 300 820-2 V1.3.1 (2000-11)

Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for the X- interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 2: Alarm management

REN/TMN-GOM003-2

Telekomunikacijsko upravljavno omrežje (TMN) - Informacijski model upravljanja asinhronega prenosnega načina (ATM) za vmesnik X med obratovalnimi sistemi (OS) omrežja s prevezovanjem navidezne poti (VP)/navideznega kanala (VC) - 2. del: Upravljanje alarma

General Information

• Status: Published
• Publication Date: 26-Nov-2000
• Technical Committee: TMN GOM - Generic Objects Modelling
• Current Stage: 12 - Completion
• Due Date: 01-Dec-2000
• Completion Date: 27-Nov-2000
• Ref Project: SIST EN 300 820-2 V1.3.1:2003 - Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for the X- interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 2: Alarm management

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Telecommunications Management Network (TMN); Asynchronous Transfer Mode (ATM) management information model for the X- interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected networks; Part 2: Alarm management33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 300 820-2 Version 1.3.1SIST EN 300 820-2 V1.3.1:2003en01-november-2003SIST EN 300 820-2 V1.3.1:2003SLOVENSKI
STANDARD



SIST EN 300 820-2 V1.3.1:2003



ETSIEN300820-2V1.3.1(2000-11)EuropeanStandard(Telecommunicationsseries)TelecommunicationsManagementNetwork(TMN);AsynchronousTransferMode(ATM)managementinformationmodelfortheX-interfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetworks;Part2:AlarmmanagementSIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)2ReferenceREN/TMN-GOM003-2KeywordsATM,alarm,B-ISDN,broadband,interface,management,switching,TMNETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°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:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)3ContentsIntellectualPropertyRights.4Foreword.41Scope.52References.53Definitionsandabbreviations.63.1Definitions.63.2Abbreviations.94Requirements.105ResourcesforATMVP/VCalarmmanagement.105.1Thebasisfortheexchangeofmanagementinformation.105.2Themanagedresources.116TheVP/VCalarmreportingmanagementfunctionsets.126.1VP/VCalarmreportingMS-Overview.126.2AlarmnotificationMFS.126.3AlarmprocessingMFS.136.4AlarmeventloggingMFS.147Managementfunctions.157.1Alarmnotificationmanagementfunctions.157.2Alarmprocessingmanagementfunction.197.3Alarmeventloggingmanagementfunction.198Scenarios.209Managementinformation.229.1Relationships.229.1.1Managedobjects.229.1.2Inheritancetree.239.1.3Namingtree.239.2X-interfaceGDMOdescription.259.3X-interfaceATMVP/VCalarmmanagementASN.1module.25AnnexA(informative):Securityaspects.26History.27SIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)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).Thepresentdocumentispart2ofamulti-partdeliverablecoveringthemanagementinformationmodelfortheX-typeinterfacebetweenOperationsSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetwork,asidentifiedbelow:Part1:"Configurationmanagement";Part2:"Alarmmanagement";Part3:"VPPerformancemanagement".(VCPerformanceManagementaspectsareforfurtherstudy).NationaltranspositiondatesDateofadoptionofthisEN:24November2000DateoflatestannouncementofthisEN(doa):28February2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31August2001DateofwithdrawalofanyconflictingNationalStandard(dow):31August2001SIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)51ScopeThepresentdocumentaddressestherequirementsofnetworkandserviceprovidersofAsynchronousTransferMode(ATM)crossconnectednetworksformanagingthefaultalarmsassociatedwiththeVirtualPath(VP)connectionsandVirtualChannel(VC)connections(generallydenotedas'VP/VCconnections'inthepresentdocument),whichspanseveraladministrativeATMdomains.Theserequirementsaresatisfiedbytheuseofastandardizedinterface(the"X-interface")betweenOperationSystems(OSs)belongingtodifferentNetworkOperators(PNOs).Readersofthepresentdocumentshouldbemadeawarethattheabbreviation'PNO'istakentomeanProvidingNetworkOperator.Inthepreviousversionofthepresentdocument(andrelateddocuments),PNOwasdefinedasPublicNetworkOperator.Thechangeindefinitionhasbeenprovidedtoreflectthechangeinmarketconditionsforprovisionofinterconnectedtelecommunicationsservices.However,itisconsiderednecessarytoretaintheabbreviation'PNO'becauseitisfoundinmanyofthemanagedobjectdefinitionsusedtospecifytheX-interface.Itwouldbedisadvantageoustointroducemajorchangesinthesemanagedobjectdefinitions,whichservepurelytechnicalpurposesformanagementofinterconnectionsonly.ThepresentdocumentshouldbeusedinconjunctionwithEN300820-1[1]andEN300820-3[14].ThepresentdocumentdescribestheX-interfaceVP/VCalarmmanagementareacoveringthefollowingaspects:-theManagementServices(MS)andfunctionsneededthatprovidethenecessaryalarmmessagesforfaultsdetectedandrelatedrecoveryprocedureswithinATMVPorVCConnectionswhichspanseveraladministrativedomains;-themanagementinformationcrossingtheX-interface.ThismanagementinformationspecificationusestheGuidelinesfortheDefinitionofManagedObjects(GDMO)formalism,describedinITU-TRecommendationX.722[2].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300820-1:"TelecommunicationsManagementNetwork(TMN);AsynchronousTransferMode(ATM)ManagementinformationmodelforXinterfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetworks;Part1:Configurationmanagement".[2]ITU-TRecommendationX.722:"InformationTechnology-OpenSystemsInterconnection-Structureofmanagementinformation:Guidelinesforthedefinitionofmanagedobjects".[3]ITU-TRecommendationG.805:"GenericFunctionalArchitectureofTransportNetworks".[4]ETSIES200653:"TelecommunicationsManagementNetwork(TMN);Networklevelgenericclasslibrary".[5]ITU-TRecommendationM.3010:"PrinciplesforaTelecommunicationsManagementNetwork".[6]NetworkManagementForumNMF025:"The'Ensembles'ConceptsandFormat",Issue1.0,August1992.SIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)6[7]ITU-TRecommendationX.733:"InformationTechnology-OpenSystemsInterconnection-SystemsManagement:Alarmreportingfunction".[8]ITU-TRecommendationX.711:"CommonmanagementinformationprotocolspecificationforITU-TApplications".[9]ITU-TRecommendationX.721:"DefinitionofManagementInformation".[10]ITURecommendationM.3400:"TMNmanagementfunctions".[11]ITU-TRecommendationX.734:"EventreportmanagementFunction".[12]ITU-TRecommendationX.208:"SpecificationofAbstractSyntaxNotationOne".[13]ETSITS101674-1:"TechnicalFrameworkfortheprovisionofinteroperableATMservices;Part1:NNI-InterfaceUserandControlplanespecification(includingnetworkfunctionsandserviceaspects)Phase1".[14]ETSIEN300820-3:"TelecommunicationsManagementNetwork(TMN);AsynchronousTransferMode(ATM)managementinformationmodelfortheXinterfacebetweenOperationSystems(OSs)ofaVirtualPath(VP)/VirtualChannel(VC)crossconnectednetworks;Part3:VPPerformancemanagement".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:(Somedefinitionsdependonthefutureacceptanceofthe"cascaded/mixedmode"asdescribedinEN300820-1[1].Thisdependenceisalreadytakenintoaccountinthesedefinitions.PNOisprovidedasthefirstdefinitioninordertohelpclarifyseveraldifferentPNOrolessubsequentlyprovidedinthelistbelow).ProvidingNetworkOperator(PNO):operatorabletoprovidenetworkresourcestocustomers(includingotherPNOs).ForthepurposesofthepresentdocumenttheseresourcesareATMVPorVCsubnetworkresourceswhichmaybeinterconnectedtocompatibleresourcesprovidedbyanotheroperatororcustomeraccesspoint:definedinITU-TRecommendationG.805[3]APNO:PNOwheretheInitiator(IPNO)startsreservingtheEnd-to-endVPorVCconnection.IftheterminationpointoftheconnectionisataUseraccesspoint,thisisconsideredtobetheAUserAccesspoint.TheAPNOcanbetheInitiatingPNO,butthisisnotalwaysthecase.ItistheConsumerofotherPNO'spartsoftheVP/VCconnectionNOTE1:If,infuturethe"cascaded"modeshouldbeacceptedasdefinedinEN300820-1[1],andiftheAPNOalsoactsasinitiatingPNO,thentheAPNOistheconsumeroftheotherPNO'spartsoftheVP/VCconnection.ATMInterconnectionGateway:representsanATMaccesspointinonesubnetwork,whichisassociatedwithanATMaccesspointinanothersubnetworkforthepurposeoftopologicalinterconnectionconnection:"transportentity"whichiscapableoftransferringinformationtransparentlybetween"connectionpoints(CP)".A"connection"definestheassociationbetweenthe"connectionpoints"andthe"connectionpoints"delimitthe"connection"consumerandproviderrolesofaPNO:withrespecttoaparticularEnd-to-endconnection,aPNOactsasaconsumerifithasdelegatedthemanagementofaVP/VCsubnetworkconnectionplustheoutgoinglinkconnectiontoanotherPNO(beingaProviderPNO).If,infuture,the"cascaded/mixed"modeshouldbeaccepted(EN300820-1[1]),aPNOcanhavebothrolesatonce,ifitisprovidingpartoftheEnd-to-endconnection(beingaProvider),andatthesametimeasksanotherPNOtoprovideapartoftheEnd-to-endconnection(beingaConsumer)destinationPNO:ZPNO(Thistermwasusedinolderversionsofthespecification)SIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)7end-to-endconnection:overallConnectionwhichcanbeoneofthefollowingtypes:-User-to-userVPC/VCC;-Network-to-userVPC;-User-to-networkVPCorNetwork-to-networkVPC.Thesetypesaredefinedin[1].Foragivenend-to-endconnection,anyPNOmayactinanyoftheI,A,TorZPNOrolesaccordingtotheinterconnectionrequirementstoprovidetheserviceinitiatingNetworkOperator(IPNO):initiatingPNOisthePNOrequestingaparticularATMEnd-to-endconnection.ItstartsrequestinginthesubnetworkoftheAPNOandendsinthesubnetworkoftheZPNO;ItcontrolstheoverallEnd-to-endconnectionInterPNOPhysicalLink(IPPL):itrepresentsaphysicallinkthatoffersbi-directionaltransmissioncapabilitiesandconnectstwopnoVpSubnetworks.EachInterPNOPhysicalLinkisterminatedbytwopnoNWAtmAccessPointswhichareinchargeofemittingfailuresrelatedtothelinkortotheaccesspointitself.AnIPPLcanberealizedbyanytransmissioncapability(SDH,PDHetc.).ThereisnoexplicitmanagedobjectdefinedintheX-interfacethatrepresentsthisresource.InformationaboutIPPLsisincludedintheinterPnoTopologicalSubnetworkPairobjectEN300820-1[1]link:"topologicalcomponent"whichdescribesthefixedrelationshipbetweena"sub-network"andanother"sub-network"or"accessgroup".Itisdefinedbyanaccesspointononesub-network,whichisassociatedwithanaccesspointonanothersubnetworknetwork-to-networkVPC:VP"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingatanATMInterconnectionGatewayandendingatanATMInterconnectionGateway.ThisinvolvestheATMresourcesofmorethanonePNO.TheNetwork-to-networkconnectionsthatarerelevanttotheXInterfaceareoftheVPtypenetwork-to-userVPC:VP"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingatanATMInterconnectionGatewayandendingattheZUserAccesspointinthenetworkoftheZPNO.ThisinvolvestheATMresourcesofmorethanonePNO.TheNetwork-to-userconnectionsthatarerelevanttotheXInterfaceareoftheVPtypeProvidingNetworkOperator(PNO):operatorabletoprovidenetworkresourcestocustomers(includingotherPNOs)pnoVcSubnetwork:topologicalcomponentusedtoeffectroutingandmanagementofATMcells.Itdescribesthepotentialforsettingup"ATM-VCconnections"acrossthesubnetwork.ThepnoVcSubnetworksaredelineatedbyATMAccessPointsandinterconnectedby"inter-PNOPhysicallinks".ApnoVcSubnetworkcanbepartitionedintointerconnected"sub-networks"and"links",butthispartitioningisnotshownoverXInterface.Inthecontextofthepresentdocument,onepnoVcSubnetworkrepresentsanATMnetworkbelongingtoonePNOpnoVpSubnetwork:topologicalcomponentusedtoeffectroutingandmanagementofATMcells.Itdescribesthepotentialforsettingup"ATM-VPconnections"acrossthesubnetwork.ThepnoVpSubnetworksaredelineatedbyATMAccessPointsandinterconnectedby"inter-PNOPhysicallinks".ApnoVpSubnetworkcanbepartitionedintointerconnected"sub-networks"and"links",butthispartitioningisnotshownovertheX-interface.InthecontextofthepresentdocumentonepnoVpSubnetworkrepresentsanATMVpnetworkbelongingtoonePNONOTE2:Inprinciple(cf.toES200653[4])onesubnetworkcanconsistofseveralsubcomponents:subnetworksandconnectionsbetweensubnetworks.However,thiscapabilityisnotsupportedinthisspecificationfortheX-interface.UsuallyonepnoVpSubnetworkorpnoVcSubnetworkrepresentsanATMnetworkbelongingtothedomainonenetworkoperator.protectionswitching:automaticswitchingtopre-assignedsparecapacityinnetworkresources,consequentonreactiontoreceiptofanalarmsignalbyanetworkmanagementsystem.(Inthecontextofthepresentdocument,thisisinternaltoaPNO)recovery:recoveryisaprocedureperformedbyaPNOwhichmakesuseofsparecapacityinthesubnetworkorinter-pnophysicallinksbelongingtothisPNO.ItfollowsafteranalarmsignalfromafaultinthePNO'snetworkresourcesstarorganization:itisdescribedinEN300820-1[1].ItistheorganizationalformthatisusedinthisspecificationSIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)8subnetwork:"topologicalcomponent"usedtoeffectroutingandmanagement.Itdescribesthepotentialfor"subnetworkconnections"acrossthe"sub-network".Itcanbepartitionedintointerconnected"sub-networks"and"links".Each"sub-network"inturncanbepartitionedintosmaller"sub-networks"and"links"andsoon.A"sub-network"maybecontainedwithinonephysicalnode.Inthepresentdocumentthispartitionisnotusedsubnetworkconnection:"transportentity"formedbya"connection"acrossa"sub-network"between"connectionpoints".Itcanbeconfiguredaspartofthe"trailmanagementprocess"asdefinedinITU-TRecommendationG.805[3]transitPNO(TPNO):transitPNOisaPNOusingitsownsubnetworktoperformitsrequiredtransitpartofVP/VCconnection.IthasaproviderroleandcorrespondstoaleafintheX-interfacetree,notbeingtheZside.Inthe"cascaded/mixedapproach"case(EN300820-1[1]),itcanbebothaprovider(whereitactsasaTransitoperator)andaConsumer(whereitvirtuallyactsasanInitiatingPNO)user:consumeroftheATMinterconnection,providedbytheEnd-to-endconnectionUser-to-networkVPC:"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingattheAUserAccesspointinthenetworkoftheAPNOandendingatanATMInterconnectionGateway.ThisinvolvestheATMresourcesofmorethanonePNO.TheUser-to-networkconnectionsthatarerelevanttotheXInterfaceareoftheVPtypeuser-to-userVPC/VCC:"transportentity"formedbytheseriesof"connections"between"terminationCPs",startingattheAUserAccesspointinthenetworkoftheAPNOandendingattheZUserAccesspointinthenetworkoftheZPNO.ThisinvolvestheATMresourcesofmorethanonePNO.TheUser-to-userconnectionsthatarerelevanttotheXInterfacecanbeoftheVPtypeortheVCtypeVCsubnetworkconnection:"transportentity"whichiscapableoftransferringinformationtransparentlybetween"connectionpoints"acrossaVCsubnetworkorfromaVCsubnetworkaccesspointtoauserVPsubnetworkconnection:"transportentity"whichiscapableoftransferringinformationtransparentlybetween"connectionpoints"acrossaVPsubnetworkorfromaVPsubnetworkaccesspointtoauserX-interface:managementinterfacebetweentwoPNOs.Inthe"ResponsibilityModel",whichisdescribedinITU-TRecommendationM.3010[5],twoOperationsSystemsFunctions(=Managers)thatarelocatedindifferentTMNs(=differentPNOs),communicateoveranXReferencePointX-interfacetree:withrespecttoaparticularVPC/VCC,anX-interfacerelationshipexistsbetweeneachproviderPNOanditsconsumerPNO.Becauseeachproviderhasexactlyoneconsumer,theX-interfacerelationsbetweenallPNOsinvolvedinthemanagementofaparticularVPC/VCCformatree,theX-interfacerelationtree.Note,thatforaparticularVP/VCtherecanbeseveralpossibleX-interfacerelationtrees;theactualtreeisformedatVP/VCset-up.TherootofthetreeistheInitiatingPNO;ituses(usingX-interfacemanagementprocesses)thePNOs(oftentransitPNOs),towhichitisconnectedinthetreeviaitsbranches.ThemostrightleafofthetreeistheZPNO.Figure1showsanexampleofanX-interfacetreeZPNO:PNOwheretheInitiator(IPNO)endsreservingtheEnd-to-endVPorVCconnection.IftheterminationpointoftheconnectionisataUseraccesspoint,thisisconsideredtobetheZUserAccesspoint.Inthiscase,theIPNOviewstheZPNOasaPNOwhosesubnetisconnectedtotheZUserSIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)9IPNOAPNOTPNOZPNOTPNOLegend:PNOProvidingNetworkOperatorIPNOInitiatingPNOAPNOAccessPNOTPNOTransitPNOZPNOTerminatingPNOFigure1:ExampleofanX-interfacetreewiththeInitiatingPNOnotbeingtheAPNO3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:APNOAccessPNO.ReferalsotoDefinitionsASN.1AbstractSyntaxNotation.1ATMAsynchronousTransferModeCMISECommonManagementInformationServiceElementCPConnectionPointeFDEventForwardingDiscriminatorENEuropeanNormETSEuropeanTechnicalStandardGDMOGuidelinesfortheDefinitionofManagedObjectsIPNOInitiatingPNO.ReferalsotoDefinitionsINMSInter-operatorNetworkManagementSystemIPPLInter-PNOPhysicalLinkITU-TInternationalTelecommunicationsUnion,TelecommunicationsStandardizationSectorMFSManagementFunctionSetMSManagementServiceNMSNetworkManagementSystemONMSOperator'sNetworkManagementSystemOSOperationsSystemPDHPlesiochronousDigitalHierarchyPNOProvidingNetworkOperatorPSProtectionSwitchingQALogQualifiedAlarmLogRALogReceivedAlarmLogSALogSentAlarmLogSDHSynchronousDigitalHierarchyTPNOTransitPNO.ReferalsotoDefinitionsTMNTelecommunicationsManagementNetworkVCVirtualChannelVCCVirtualChannelConnectionVCSCVirtualChannelSubnetworkConnectionVPVirtualPathVPCVirtualPathConnectionVPSCVirtualPathSubnetworkConnectionX-typeNetworkManagementinterfacebetweentelecommunicationsoperatorsSIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)104Requirements1)Incaseoffaults,itshouldbepossibletolocalizefaultsonaPNOsub-networkand/orIPPLlevel.2)AllpartieswhichareaffectedbyafaultyPNOsub-networkaretobeinformedofthefailure.3)AllalarminformationpassedacrosstheX-interfaceshouldbetime-stamped.4)EliminationofredundantmultiplealarmsrelatingtoasingleunderlyingcausebeforethealarminformationistransmittedacrosstheX-interface.5)Protectionswitchingandtheresultoftheprotectionshouldbenotified.6)Under_recoveryactionsandtheresultsofunder_recoveryactionsshouldbenotified.7)Itshouldbepossibletoenable/disablealarmreportingonagivenconnectionorgroupofconnections.5ResourcesforATMVP/VCalarmmanagement5.1ThebasisfortheexchangeofmanagementinformationThearchitecturalframeworkcharacterizingtheexchangeofmanagementinformationacrosstheX-interfaceisrepresentedinfigure2.X-interfaceRemoteINMSPNOVP/VCSubnetworkQinterfaceONMSAlarmNotificationMSLegend:PNOProvidingNetworkOperatorONMSOperatorNetworkManagementSystemINMSInter-operatorNetworkManagementSystemMSManagementServiceVP/VCVirtualPathorVirtualChannelPNOVP/VCSubnetworkQinterfaceONMSINMSAlarmNotificationMSOtherX-interfaceMS’s[1],[2]OtherX-interfaceMS’s[1],[2]Figure2:ArchitecturalframeworkfortheX-interfaceInfigure2,theterm"ONMS"isdefinedasanOperatorNetworkManagementSystem.ForthepurposeofthepresentdocumenttheONMSistakentobethemanagementsystemwhichcontrolsanoperator'sVP/VCsubnetworkwhichisinterconnectedtoanotheroperator'scompatibleVP/VCsubnetwork.(InterconnectionattheVP/VCsubneworklevelisnotshowninfigure2butmayinaccordancewiththespecificationdefinedinTS101674-1[13]).Thetermdenotedas'INMS'isdefinedasanInter-operatorNetworkManagementSystem."INMS"canbeconsideredasanoperator'smanagementsystemforanX-interfaceinterconnectionwithanotheroperator,whetherwithinnationalboundariesoracrossthem.ThedistinctionbetweenONMSandINMShasbeenmadebecausethesetwosystemsactondifferentInformationModelsandbecausethereisthenecessityofexchangeofinformationbetweenthem.Thelogicalpositioningofthe"Q"interface,whichbasicallycontrolsnetworkswitchesinthePNOVP/VCSubnetwork,isalsoindicatedbutanymattersrelatingtothisinterfaceareoutsidethescopeofthepresentdocument.SIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)11TheINMSbelongingtoanyoperatorhastosupportthefollowingoperationsasfarastheAlarmNotificationMSisconcerned:-receptionofnotificationscomingfromaremoteINMS.Thesenotificationsaredescribedindetailinsubclause7.1;-receptionofalarmscomingfromtheONMSandrelevanttotheX-interface.ThesealarmsareassociatedwithfaultyVP/VCconnectionsusedforend-to-endconnections(theymaybePhysicalLayeralarmsorVP/VCLayeralarmsorfaultsaffectingtheATMCrossConnectwhichactsastheinter-networkgateway);-elaborationofalarmscomingfromtheONMS(qualificationandadaptationtointer-networkalarmformat);-sendingofalarmstotheappropriatePNOs(InitiatingPNOinthecaseofaVPSCorVCSCfaultorallPNOsinthecaseofInter-PNOPhysicalLink(IPPL)fault);-loggingalarmsandretrievingalarmreports.5.2ThemanagedresourcesAsimplifiedviewofthenetworklevelresourcesbeingmanagedisprovidedinfigure3.Thisviewisprovidedintheformofanexampleofthemanagementviewafterauser-to-userVPorVCconnectionhasbeensetup.Furtherdetailsandrelatedexamplesareprovidedin[1].Figure3showstheX-interfacesbetweentheIPNOandotherPNOswhichmaybeusedtosupporttheVP/VCalarmmanagementfunctionsdefinedinthepresentdocument.TheNMS'sassociatedwiththeA,TandZPNOsmayormaynothaveINMSfunctionalityimplementedasdefinedinsubclause5.1.X-interfaceX-interfaceQ-interface11111145545511APNONMSTPNONMSZPNONMS3Legend:1’pnoNWAtmAccessPointforuseraccess(noassociationwith(2))1:pnoNWAtmAccessPoint4:pnoVpSubnetworkConnectionorpnoVcSubnetworkConnection2:interPnoTopologicalSubnetworkPair5:pnoVPCTPorpnoVCCTP(VP/VCConnectionTerminationPoint)3:pnoVpSubnetworkorpnoVcSubnetworkNMS:NetworkManagementSystem(maycontainONMSandINMS)IPNOAPNOX-interfaceTPNOZPNOViewonX.InterfaceattheTPNONMSViewonXInterfaceattheAPNONMSViewonXInterfaceattheZPNONMSQ-interfaceQ-interface22221’User-access-point4551’User-access-point33IPNOINMSFigure3:X-interfacemanagednetworkresourcesandconnectionsSIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)126TheVP/VCalarmreportingmanagementfunctionsets6.1VP/VCalarmreportingMS-OverviewIndefiningtheVP/VCAlarmReportingManagementService(MS)fortheX-interfaceandfollowingtheEnsemblesconcept,definedbytheNetworkManagementForumNMF025[6],someManagementFunctionSets(MFS)havebeenidentified.EachMFShasbeendecomposedinMF.ThefollowingMFSshavebeenidentifiedtomanagethenotificationsdescribedinclause7:-AlarmnotificationMFS;-AlarmeventloggingMFS;-AlarmprocessingMFS.TheidentifiedVP/VCsAlarmReportingMFSsareorganizedasdepictedinfigure4anddescribedinmoredetailinsubclauses6.2,6.3and6.4.(NotethatdetailsofimplementationoftheINMSfunctions,MSsanddatabasesareaninternalmatterforanyPNOwishingtoprovideanX-interfaceinaccordancewiththespecificationinthepresentdocumentandthereforeimplementationguidanceorspecificationsareoutsidethescopeofthepresentdocument).XInterfaceONMSINMSAlarmEventLogMFSAlarmNotificationMFSAlarmProcessingMFSAlarmMgtDataBaseVP/VCAlarmManagementMSOtherX-interfaceMS’s[1],[2]Figure4:MFSsandotherX-interfaceMSsrelativetotheVP/VCalarmmanagementMS6.2AlarmnotificationMFSThisMFSperformsthefollowingtasks:transmissionoffaultyVP/VCalarmnotificationsacrosstheX-interface;thesenotificationscontainthefollowingparameters:-subnetworkId,resourceid(vpConnectionIdorvcConnectionIdoratmAccessPointId),timeofevent,probablecause,perceivedseverity,specificproblems(thelastthreeofwhicharedescribedinmoredetailbelowandarederivedfromtheeventinformationsectionofITU-TRecommendationX.733[7]andarereproducedhereinordertoclarifythebasisonwhichtheMFSmessagesaregeneratedbythesystem).forwardingofsentalarmstotheAlarmEventLoggingMFStoberecordedintheSALog:-thefourtypesofAlarmNotificationsaresummarizedinfigure5.InthecaseofanIPPLfailurethesamenotificationsaresentbuttoallPNOsinsteadofonlytheOriginPNO.SIST EN 300 820-2 V1.3.1:2003



ETSIETSIEN300820-2V1.3.1(2000-11)13probableCause:thisparameterdefinesfurtherqualification(afterEventTypeandinformation)astotheprobablecauseofthealarm.Probablecausevaluesfornotificationsshallbeindicatedinthebehaviourclauseoftheobjectclassdefinition.ThesyntaxofstandardprobableCausesshallbetheASN.1typeobjectidentifier.ThemanagedobjectclassdesignershouldchoosethemostspecificprobableCauseapplicable.ThesetofprobableCauseswillnotbefurtherelaboratedhereandreferenceshouldbemadetoITU-TRecommendationX.733[7].specificProblems:ThisparameteridentifiesthestatusofthealarmintheVP/VCAlarmmanagementservice.Inthecontextofthesespecifications,thespecificProblemsvalueshavebeenrestrictedto:-protection-switched;-under-recovery;-cleared;-unrecoverable.perceivedSeverity:thisparameterdefinessixseveritylevels,whichprovideanindicationofhowitisperceivedthatthecapabilityofthemanagedobjecthasbeenaffected.Briefly,theseare:cleared:indicatestheclearingofoneormorepreviouslyreportedalarms.indeterminate:indicatesthattheseveritylevelcannotbedetermined.critical:indicatesthataserviceaffectingconditionhasoccurredandanimmediatecorrectiveactionisrequired.major:indicatesthataserviceaffectingconditionhashappenedandanurgentcorrectiveactionisrequired.minor:indicatestheexistenceofanon-serviceaffectingfaultconditionandthatcorrectiveactionshouldbetakeninordertopreventamoreseriousfault.warning:indicatesthedetectionofapotentialorimpendingserviceaffectingfault,beforeanysignificanteffectshavebeenfelt.Again,referenceshouldbemadetoITURecommendationX.733[7]forfulldescriptions.6.3AlarmprocessingMFSFortheAlarmProcessingMFSthefollowingtasksareidentified:-WithregardtotheONMSQ-interface,asdepictedinfigure2(NotapartoftheX-interfacespecification):-receptionofalarmsconcerningthepartofthePNO'sONMS-basedsub-networksuppo
...