ITU-T X 723-1993 Information Technology - Open Systems Interconnection - Structure of Management Information Generic Management Information - Data Networks and Open System Communic.pdf

《ITU-T X 723-1993 Information Technology - Open Systems Interconnection - Structure of Management Information Generic Management Information - Data Networks and Open System Communic.pdf》由会员分享，可在线阅读，更多相关《ITU-T X 723-1993 Information Technology - Open Systems Interconnection - Structure of Management Information Generic Management Information - Data Networks and Open System Communic.pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、ITU-T RECMN*X*723 93 4862571 0586805 T7b INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OS1 MANAGEMENT X.723 (1 1/93) INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - STRUCTURE OF MANAGEMENT INFORMATION:

2、 GENERIC MANAGEMENT INFORMATION ITU-T Recommendation X.723 (Previously “CCITT Recommendation”) ITU-T RECMN*X-723 93 m 4862593 0.586806 902 W Foreword ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Sta

3、ndardization Sector (ITU-T) is a permanent organ of the ITU. Some 179 member countries, 84 telecom operating entities, 145 scientific and industrial organizations and 38 international organizations participate in ITU-T which is the body which sets world telecommunications standards (Recommendations)

4、. The approval of Recommendations by the members of IT-T is covered by the procedure laid down in WTSC Resolution No, 1 (Helsinki, 1993). In addition, the World Telecommunication Standardization Conference (WTSC), which meets every four years, approves Recommendations submitted to it and establishes

5、 the study programme for the following period. In some areas of information technology, which fall within ITU-T?s purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. The text of ITU-T Recommendation X.723 was approved on 16th November 1993. The identical text is

6、also published as ISOAEC International Standard 10165-5. NOTE In this Recommendation, the expression ?Administration? is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O ITU 1994 All rights reserved. No part of this publication may be repr

7、oduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the IW. ITU-T RECMN*X.23 93 m 4862593 O586807 849 1 2 3 4 5 6 7 8 9 10 11 12 13 CONTENTS Page scope 1 Normative references . 1 Definitions 2 Abbreviation

8、s . 3 Conventions 3 Overview 3 Generic managed object class definitions 4 Name bindings . 9 A#nbu tes 10 Attribute Groups . 15 Actions . 16 Notifications . 17 ASN.l definitions . 18 ITU-T RW . X.723 (1993 E) i ITU-T RECMN*X-723 93 4862573 0586808 785 = Summary This Recommendation documents managemen

9、t information that is applicable to more than one open system resource by documenting those common structures as generic definitions. These generic definitions may be used in the specification of managed objects for technology specific use such as OS1 layers. In general, use of OS1 layer specific us

10、e will require. ii ITU-T RW. X.723 (1993 E) ITU-T RECMN*X-723 93 4862591 O586809 611 = ISO/IEC 10165-5 : 1994 (E) INTERNATIONAL STANDARD ITU-T RECOMMENDATION INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - STRUCTURE OF MANAGEMENT INFORMATION: GENERIC MANAGEMENT INFORMATION 1 scope This Recom

11、mendation I International Standard provides developers of OS1 Recommendations I International Standards that contain managed object definitions with generic definitions of managed object classes that will provide common superclass definitions from which layer- or resource specific object class defin

12、itions may be derived; assist with the development of common elements of object class definitions across multiple layers or components of layers; reduce duplication of effort in other working groups by identifying commonly usehil definitions. - - - To this end, this Recommendation I International St

13、andard defines managed object classes which may be used as superclasses, using the template notation defined in CCITT Rec. X.722 I ISOAEC 10165-4, including the definition of any packages, attributes, attribute groups, behaviour, actions, notifications and parameters that may be associated with the

14、superclasses. It also defines functional units required by layer- or resource-specific management standards which are not defined in the CCITT Rec. X.73X I ISOAEC 10164 series of systems management function standards. This Recommendation I Intemational Standard is applicable to the development of an

15、y OS1 Recommen- dationlhternational Standard which defines managed object classes that may be refined from the managed object classes defined in this Recommendation I International Standard. This Recommendation I International Standard does not specify or imply any constraints on the development of

16、managed object definitions in terms of their inheritance relationships. Developers of managed object class definitions are encouraged to use the definitions contained in this Recommendation I International Standard to promote consistency between similar managed object classes; however, use of these

17、definitions is not mandated. 2 Normative references The following Recommendations and International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation I International Standard. At the time of publication, the editions indicated were valid

18、. All Recommendations and International Standards are subject to revision, and parties to agreements based on this Recommendation I International Standard are encouraged to investigate the possibility of applying the most recent edition of the Recommendations and International Standards listed below

19、. Members of EC and IS0 maintain registers of currently valid Intemational Standards. The ITU-T maintains a list of the currently valid Recommendations. 2.1 Identical Recommendations I International Standards - CCIT Recommendation X.701 (1992) I ISO/IEC 10040:1992, Information technology - Open Syst

20、ems Interconnection - Systems Management Overview. CC Recommendation X.720 (1992) I ISO/IEC 10165-1:1992, Information technology - Open Systems Interconnection - Structure of Management Information: Management Information Model. CC Recommendation X.721 (1992) I ISO/IEC 10165-2:1992, Information tech

21、nology - Open Systems Interconnection - Structure of Management Information: Definition of Management Information. - - ITU-T Rec. X.723 (1993 E) 1 ISO/IEC 10165-5 : 1994 (E) - CC Recommendation X.722 (1992) I ISO/IEC 10165-4:1992, Information technology - Open Systems Interconnection - Structure of

22、Management Information: Guidelines for the Definition of Managed Objects. CC Recommendation X.731 (1992) I ISO/IEC 10164-2: 1992, Information technology - Open Systems Interconnection - Systems Management: State Managernent Function. - Paired Recommendations I Intemational Standards equivalent in te

23、chnical content - CCITT Recommendation X.200 (1989), Reference Model of Open Systems Interconnection for CCITT Applications. IS0 7498: 1984, Information processing systems - Open Systems Interconnection - Basic Reference Model. CCITT Recommendation X.208 (1989), Specification of abstract syntax nota

24、tion one (ASN. I). ISOAEC 8824: 1990, Information technology - Open Systems Interconnection - Spec$cation of Abstract Syntax Notation One (ASN. I). - CCITT Recommendation X.700 (1992), Management Framework Definition for Open Systems Interconnection (OSI) for CCIP Applications. IS0 7498-4: 1989, Inf

25、ormation processing systems - Open Systems Interconnection - Basic Reference Model - Part 4: Management Framework. CCIT Recommendation X.7 10 (199 l), Common Management Information Service Definition for CCIP Applications. ISOAEC 9595: 1991, Information technology - Open Systems Interconnection - Co

26、mmon management information service definition. - - 3 Definitions For the purposes of this Recommendation I International Standard, the following definitions apply. 3.1 Basic reference model definitions This Recommendation I International Standard uses the following terms defined in CCIT Rec. X.200

27、I IS0 7498: a) (N)-SAP; b) open system; c) systems management; d) application process. 3.2 Management framework definitions This Recommendation I International Standard uses the following terms defined in CCI“ Rec. X.700 I ISO/IEC 7498-4: managed object. 3.3 Systems management overview definitions T

28、his Recommendation I International Standard uses the following terms defined in CC Rec. X.701 I ISOAEC 10040: a) generic definitions; b) managed object class; c) management information; d) notification. 3.4 Management information model definitions This Recommendation I International Standard uses th

29、e following terms defined in CCITT Rec. X.720 I ISO/IEC 10165- 1 a) allomorphism; b) attribute type; c) behaviour; d) containment; 2 ITU-T RW. X.723 (1993 E) ITU-T RECMNxX.723 93 = 48b259L 0586811 27T ISO/IEC 10165-5 1994 (E) e) name binding; g) specialization; h) subordinate object; i) superclass;

30、j) superior object. f) package; 3.5 CMIS definitions This Recommendation I International Standard uses the following terms defined in CCITT Rec. X.710 I ISO/IEC 9595: amibute. 3.6 ASNA definitions This Recommendation I International Standard uses the following terms defined in CCITT Rec. X.208 I ISO

31、/IEC 8824: a) object identifier; b) sequence-of type; c) sequencetype; d) set-oftype; e) settype; f) type- 3.7 GDMO definitions This Recommendation I International Standard uses the following terms defined in CCT Rec. X.722 I ISO/IEC 10165-4: a) managed object class definition; b) template. 4 Abbrev

32、iations ASN. 1 CL Connectionless CMIS Common Management Information Service CO Connection Oriented GDMO Guidelines for the Definition of Managed Objects GMI Generic Management Information OS1 Open Systems Interconnection PDU Protocol Data Unit SAP Service Access Point SM Structure of Management Info

33、mation Abstract Syntax Notation One 5 Conventions This Recommendation I International Standard uses the template notation defined in CCiT Rec. X.722 I ISO/IEC 10165-4 as the notation for defining managed object classes and the abstract syntax notation defined in CC Rec. X.208 I ISO/IEC 8824 as the m

34、eans of defining ASN. 1 data types associated with the use of the template notation. Text based on these notational conventions is printed in a distinctive typeface. 6 Overview The purpose of this Recommendation I International Standard is to document structures for managed object classes and manage

35、ment information types that are common to more than one open system resource, by defining those common structures as generic definitions of management information. Other work items, such as those concerned with the ITU-T RW. X.723 (1993 E) 3 ITU-T RECMN*X.23 93 = 48b259L 0586822 Lob ISO/IEC 10165-5

36、: 1994 (E) management of individual OS1 layers, may specialize these generic definitions in ways that are appropriate for the requirements of the layer or resource concerned. In the process of specialization, the generic managed object classes defined in this Recommendation I International Standard

37、may be defined as superclasses of allomorphic classes where appropriate. The use of generic managed object classes in this way will help to ensure the consistency and completeness of managed object class definitions for such resources as layer entities, SAPS. connections, etc., and also take account

38、 of relationships between them. Similar advantages may be gained by defining managed object classes corresponding to components of OS1 layers, such as subnetworks. Definers of management information are also encouraged to use the definitions contained in CCIT Rec. X.721 I ISO/IEC 10165-2 where they

39、are applicable to the managed object classes or other information types being defined. 7 Generic managed object class definitions This clause contains managed object class definitions for generic managed object classes, along with their mandatory and conditional packages and behaviour definitions. T

40、he definitions have been documented “in-line“ with the exception of the attribute definitions which are to be found in clause 9. 7.1 Application process The applicationProcess managed object class is used to represent an element within a system which performs the information processing for a particu

41、lar application. The SupportEntityNames attribute contains a set of distinguished names of supporting entities which provide communication services to the application process. The semantics and syntax of the operationalstate attribute are defined in CCIT Rec. X.731 I ISO/IEC 10164-2 and CCIT Rec. X.

42、721 I ISO/IEC 10165-2. applicationProcess MANAGED OBJECT CLASS DERIVED FROM “CCITT Rec. X.721 (1992) I ISO/IEC 10165-2 1992“:tOp CHARACTERIZED BY applicationProcessP1 PACKAGE BEHAVIOUR applicationProcessB1 BEHAVIOUR DEFINED AS !An application process supports the disabled and enabled values of the o

43、perationalState attribute as described in CCITT Rec. X.731 (1 992) I ISO/IEC 1 O1 64-2:1992 as follows: - an application process is disabled if it is inoperable or a resource on which it depends is inoperable, - an application process is enabled if it is operable.! , ATTRIBUTES applicationProcessld

44、GET, applicationProcessTitle GET, suppottEntityNames GET, “CCITT Rec. X.721 (1 992) I ISOAEC 1 O1 65-2:1992“:operationalState GET , REGISTERED AS (joint-iso-ccitt ms(9) smi(3) part5(5) managedObjectClass(3) applicationProcess(8) ; 7.2 Communications entity The communications entity managed object cl

45、ass is used to represent an active functional element which performs communication processing functions within a system, e.g. Network Entity, Transport Entity, etc. The localSapNames attribute contains a set of distinguished names of layer (N-1) SAPS or ports at which services are provided to the en

46、tity. NOTE 1 - Although the localSapNames attribute is for generality defined as a set valued attribute and may therefore contain zero or more SAP names, the set membership is, in most cases, limited to a single SAP name. 4 ITU-T RW. X.723 (1993 E) ITU-T RECMN*X.23 93 W 486259L 0586833 042 ISO/IEC 1

47、0165-5 : 1994 (E) The semantics and syntax of the operationaiState attribute are defined in CC Rec. X.731 (1992) I ISO/IEC NOTE 2 - In circumstances where both connection oriented and connectionless services are available at a particular layer, the further refinement of the conununications entity ma

48、naged object class to distinguish between connection oriented and connectionless entities is discouraged, as it becomes unclear under some circumstances (particularly under error conditions) as to what belongs to the CO entity and what belongs to the CL entity (e.g. If a corrupted PDU is received, i

49、s it the CO counter of corrupted PDUs that is incremented, or is it the CL counter. or both?). 10164-2:1992 and CCITT RK. X.721(1992) I ISO/IEC 10165-21992. communicationsEntity MANAGED OBJECT CLASS DERIVED FROM “CCITT Rec. X.721 (1992) I ISOAEC 10165-2:1992“:top ; CHARACTERIZED BY communicationsEntityP1 PACKAGE BEHAVIOUR communicationsEntityB1 BEHAVIOUR DEFINED AS !A communications entity supports the disabled and enabled values of the operationalstate attribute as described in CCIlT Rec. X.731 (1 992) I ISO/IEC 10164-2:1992 as follows: - an entity is dis