ETSI EN 300 820-2-1998 Telecommunications Management Network (TMN) Management Information Model for the X-Type Interface between Operation Systems (OSs) of a Virtual Path (VP) Virt.pdf

1、 STDDETSI EN 300 820-2-ENGL L998 m 3400855 03L53bL Ob4 m EN 300 820-2 1.2.3 (1998-07) European Standard (Telecommunications series) Telecommunications Management Network (TMN); Management information model for the X-type interface between Operation Systems (OSs) of a Virtual Path (VP)Nirtual Channel

2、 (VC) cross connected network; Part 2: Asynchronous Transfer Mode (ATM) VP alarm management 2 EN 300 820-2 V1.2.3 (1 998-07) Reference DENRMN-00032 (71ciOiqO.PDF) Keywords B-ISDN, broadband, ISDN, management ETSI Postal address F-O6921 Sophia Antipolis Cedex - FRANCE Office address 650 Route des Luc

3、ioles - Sophia Antipolis Valbonne - FRANCE Siret Na 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre ia Cous-Prfecture de Grasse (06) No 780W88 Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Internet secretariat etsi.fr http:/www.etsi.f r http:/www.etsi.org Copyright Notificatio

4、n No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. Q European Telecommunications Standards Institute 1998. All rights reserved. ETSI 3 EN 300 820-2 Vl.2.3 (199847) Contents Intellectual Property Rig

5、hts 4 Foreword 4 1 2 3 3.1 3.2 4 5 5.1 5.2 6 6.1 6.2 6.3 6.4 7 7.1 7.2 7.3 8 9 9.1 Scope 5 Normative references . 5 Definitions and abbreviations 6 Definitions . 6 Abbreviations . 8 Requirements . 8 Resources for ATM VP alarm management 9 The basis for the exchange of management information 9 The ma

6、naged resources 10 The VP alarm reporting management function sets . VP alarm reporting MS . Overview . 10 Alarm notification MFS . 11 Alarm processing MFS 12 Alarm event logging MFS 12 Management functions . 13 Alarm notification management functions . 13 Alarm processing management function 18 Ala

7、rm event logging management function . 18 Scenarios 19 Management information . 20 Relationships 20 10 9.1.1 Managed objects 21 9.1.2 inheritance tree . 22 9.1.3 Naming tree 22 X-interface GDMO description . 23 X-interface ATM VP alarm management ASN.1 module 23 Security aspects 24 History 25 9.2 9.

8、3 Annex A (informative): ETSI 4 EN 300 820-2 VI .2.3 (1 998-07) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-memb

9、ers , and can be found in ETR 314: “Intellectual Property Rights (IPRs); Essential, orpotentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/www.etsi.frlipr or

10、 http:/www .etsi.org/ipr). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been camed out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essenti

11、al to the present document. Fo re wo rd This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Telecommunications Management Network (TMN). The present document is part 2 of a multi-part EN covering the management information model for the X-type interface b

12、etween Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected network, as identified below: Part 1: “Configuration management aspects“; Part 2: Part 3: “Performance management aspects“. “Asynchronous Transfer Mode (ATM) VP alarm management“; National transposition dates

13、Date of adoption of this EN: 3 July 1998 1 Date of latest announcement of this EN (doa): 31 October 1999 Date of latest publication of new National Standard or endorsement of this EN (dop/e): 30 April 1999 1 Date of withdrawal of any conflicting National Standard (dow): 30 April 1999 STD.ETSI EN 300

14、 820-2-ENGL 1778 3400855 0315365 70T 5 EN 300 820-2 V1.2.3 (1 99807) 1 Scope The present document addresses the requirements of network and service providers of Asynchronous Transfer Mode (ATM) cross connected networks for managing the fault alarms associated with the Virtual Path (VP) connections,

15、which span several administrative ATM domains. These requirements are satisfied by the use of a standardized interface (the “X-interface“) between Operation Systems (0%) belonging to different Public Network Operators (PNOs). The present document describes the X-interface VP alarm management area co

16、vering the following aspects: - the Management Services (MS) and Management Functions (MF) needed that provide the necessary alarm messages for faults detected within ATM Connections which span several administrative domains; the management information crossing the X-interface. This management infor

17、mation specification uses the Guidelines for the Defmition of Managed Objects (GDMO) formalism, described in ITU-T Recommendation X.722 121. - The present document has been named as “ATM VP alarm management“ because it is expected to be part of a comprehensive fault management standard for ATM VP an

18、d Virtual Channels (VCs) in due course. As such it is self-sufficient for the defined scope of reporting faults on, and recovery procedures for, VPs across the X-interface. 2 Normative refe re nces References may be made to: specific versions of publications (identified by date of publication, editi

19、on number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or all versions up to and including the identified version (identified by “up to and including“ before the version identity); or all versions subsequent to and including the identified vers

20、ion (identified by “onwards“ following the version identity); or publications without mention of a specific version, in which case the latest version appiies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. 111 EN 300 820-1:

21、“Network Aspects (NA); Management information model for the X-type interface between Operation Systems (OSs) of a Virtual Path (VP)/Virtual Channel (VC) cross connected network; Part 1 : Configuration management aspects“. ITU-T Recommendation X.722: “Information Technology - Open Systems Interconnec

22、tion - Stnicture of management information: Guidelines for the definition of managed objects“. ITU-T Recommendation G.805: “Generic functional architecture of transport networks“. ITU-T Recommendation M.30 10: “Principles for a Telecommunications Management Network“. ITU-T Recommendation X.721: “Def

23、inition of Management Information“. ITU-T Recommendation X.733: “Information Technology - Open Systems Interconnection - Systems management: Alarm reporting function“. ITU-T Recommendation M.3400: “TMN management functions“. ITU-T Recommendation X.734: “Event report management function“. ITU-T Recom

24、mendation X.208: “Specification of Abstract Syntax Notation One“. 121 131 141 I51 161 171 181 191 ETSI _ STD-ETSI EN 300 820-2-ENGL 1998 D 3V00855 03153bb 646 D 6 EN 300 820-2 V1.2.3 (1 998-07) 1101 Network Management Forum NMF025: “The Ensembles Concepts and Format“, Issue 1.0, August 1992. TU-T Re

25、commendation X.7 11 : “Common management information protocol specification for CCITT Applications“. L11J 3 3.1 Definit ions and abbreviations Definitions For the purposes of the present document, the foilowing definitions apply: (Some definitions depend on the future acceptance of the “cascadedlmix

26、ed mode“ as described in EN 300 820-1 i. This dependence is already taken into account in these definitions). access point: It is defined in ITU-T Recommendation G.805 131. A Public Network Operator (A PNO): The A PNO is the PNO whose subnet is connected to the A user, the user where the overall VP-

27、connection starts. The A PNO can be the initiating one, but this is not always the case. If it is the initiating PNO it is the root of the X-interface tree. If not, it is the most left leaf (as indicated in figure 1). if, in fuhire the “cascaded“ mode should be accepted as defined in EN 300 820-1 l,

28、 and if the A PNO also acts as initiating PNO, then the A PNO is the consumer of the other PNOs parts of the VP connection. cascade organization: It is described in EN 300 820-1 i. The impact of this organization on the model is for further study. connection: A “transport entity“ which is capable of

29、 transferring information transparently between “connection points“. A “connection“ defiies the association between the “connection points“ and the “connection points“ delimit the “connection“. consumer and provider roles of a PNO: With respect to a particular VP, a PNO acts as a consumer if it has

30、delegated the management of a VP subnetwork connection plus the outgoing link connection (both shall be part of the connection) to another PNO (that acts as a provider). If, in future, the “cascaded/mixed“ mode should be accepted (EN 300 820-1 i), a PNO can have both roles at once, if it is providin

31、g part of the VP (acting as a provider), and at the same time asks another PNO to provide a part of the connection (acting as a consumer). destination PNO: Z PNO (mis term was used in older versions of the specification). initiating Network Operator (PNO): The initiating PNO is the PNO requesting a

32、particular ATM connection starting in the A subnetwork and ending in the Z subnetwork; it controls the overall VP connection. Inter PNO Physical Link (IPPL): It represents a physical link that offers bi-directional transmission capabilities and connects two pnoVpSubnetworks. Each InterPNOPhysicaiLin

33、k is terminated by two pnoNWAtmAccessPoints which are in charge of emitting failures related to the link or to the access point itself. An IPPL can be realized by any transmission capability (SDH, PDH etc.). There is no explicit managed object defined in the X-interface that represents this resource

34、. Information about IPPLs is included in the interPNOTopologicalSubnetworkPair object, EN 300 820-1 i. Link connection: A “transport entity“ provided by the “client/server“ association. It is formed by a near-end “adaptation“ function, a server “trail“ and a far-end “adaptation“ function between “co

35、nnection points“. It can be configured as part of the “trail management process“ in the associated server layer. Link: A “topological component“ which describes the fixed relationship between a “sub-network“ and another “sub-network“ or “access group“. mixture organization: It is described in EN 300

36、 820-1 i. The impact of this organization on the X-interface model is for further study. network connection: A “transport entity“ formed by the series of “connections“ between “termination connection points“. ETSI STD-ETSI EN 300 820-2-ENGL 1998 m 3400855 03153b7 582 7 EN 300 820-2 V1.2.3 (199807) o

37、riginating PNO: An A PNO when it is also the initiating PNO. (This term was used in older versions of the specification). Public Network Operator (PNO): An operator that manages an administrative ATM domain. The term PNO is used in the present document to be in alignment with EN 300 820-1 i. pnoVpSu

38、bnetwork: A subnetwork (according to 1TU-T Recommendation G.805 131) is a topological component used for carrying ATM cells. PnoVpSubnetworks are delineated by termination points, modelled by VpCTps contained in NWATMAccesspoints, and they are used for setting up pnoVpSubnetworkConnections. NOTE: In

39、 principle (cf. to 1-ETS 300 653) one subnetwork can consist of several subcomponents: subnetworks and connections between subnetworks (generally called link connections). But this capability is not supported in Xcoop. Usually one pnoVpSubnetwork represents an ATM network belonging to the domain one

40、 network operator. protection switching: Automatic switching to pre-assigned spare capacity in network resources, consequent on reaction to receipt of an alarm signal by a network management system. (In the context of the present document, this is internal to a PNO). recovery: Recovery is a procedur

41、e performed by a PNO which makes use of spare capacity in the subnetwork or inter-pno physical links belonging to this PNO. It follows after an alarm signai from a fault in the PNOs network resources. star organization: It is described in EN 300 820-1 i J. It is the organizational form that is used

42、in this specification. sub-network connection: A “transport entity“ formed by a “connection“ across a “sub-network between “connection points“. It can be configured as part of the “trail management process“ as defined in IT-T Recommendation G.805 131. subnetwork: A “topological component“ used to ef

43、fect routing and management. It describes the potential for “sub-network connections“ across the “sub-network“. It can be partitioned into interconnected “sub-networks“ and “links“. Each “ sub-network“ in turn can be partitioned into smaller “sub-networks “ and “links“ and so on. A “sub-network may

44、be contained within one physical node. termination connection point: It is defined in IT-T Recommendation G.805 131. trail: It is defined in IT-T Recommendation G.805 131. transit PNO: A transit PNO is a PNO using its own subnetwork to perform its required transit part of VP connection. It has a pro

45、vider role and corresponds to a leaf in the X-interface tree, not being the Z side. In the “cascadedmixed approach“ case (EN 300 820-1 111). it can be both a provider (where it acts as a msit) and a consumer (where it effectively acts as an Initiating PNO). user: An end customer which is associated

46、with the reservation of a VP connection. VP subnetwork connection: A “transport entity“ which is capable of transferring information transparently between “connection points“ across a subnetwork or from a subnetwork access point to a user. X-interface tree: With respect to a particular VP, an X-inte

47、rface relationship exists between each provider PNO and its consumer PNO. Because each provider has exactly one consumer, the X-interface relations between all PNOs involved in the management of a particular VP form a tree, the X-interface relation tree. Note, that for a particular VP there can be s

48、everal possible X-interface relation trees; the actual tree is formed at VP Set-up. The root of the tree is the Initiating PNO; it uses (and via an X-interface controls) the PNOs (often transit PNOs), to which it is connected in the tree via its branches. The most right leaf of the tree is the Z PNO

49、. Figure 1 shows an example of an X-interface tree. X-interface: The management interface between two PNOs. In the “Responsibility Model“, which is described in ITU-T Recommendation M.3010 141, two Operations Systems Functions (= Managers ) that are located in different TMNs (= different PNOs), communicate over an X Reference Point. Z PNO: A Z PNO is a PNO whose subnet is connected to a user, where the overall VP connection ends. 8 Initiating PNO EN 300 820-2 V1.2.3 (1 998-07) Transit Transit PNO PNO Figure 1: Example of an X-interface tree