ITU-T M 3101-1995 Managed Object Conformance Statements for the Generic Network Information Model - Maintenance Telecommunications Management Network (Study Group 4 105 pp)《关于通用网络信.pdf

《ITU-T M 3101-1995 Managed Object Conformance Statements for the Generic Network Information Model - Maintenance Telecommunications Management Network (Study Group 4 105 pp)《关于通用网络信.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3101-1995 Managed Object Conformance Statements for the Generic Network Information Model - Maintenance Telecommunications Management Network (Study Group 4 105 pp)《关于通用网络信.pdf（105页珍藏版）》请在麦多课文档分享上搜索。

1、 STD-ITU-T RECMN M*3101-ENGL 1775 48b2571 Ob23510 377 INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU M.31 O1 (07/95) MAINTENANCE TELECOMMUNICATIONS MANAGEMENT NETWORK MANAGED OBJECT CONFORMANCE STATEMENTS FOR THE GENERIC NETWORK INFORMATION MODEL ITU-T Re

2、commendation M.3101 (Previously “CCITT Recommendation”) FOREWORD The -T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommen- dations on

3、 them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study bly the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The appr

4、oval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). ITU-T Recommendation M.3101 was prepared by -T Study Group 4 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 27th of July 199

5、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 1995 All rights reserve.d. No part of this publication may be reproduced or utilized in any form or by any means, elect

6、ronic or mechanical, including photocopying and microfilm, without permission in writing from the IT. STD-ITU-T RECMN M.3LOL-ENGL 1775 W qAb257L Ob23512 141 = CONTENTS 1 Scope 2 References 3 Abbreviations . 4 5 Structure . Management information conformance requirements 6 Additional guidelines . Ann

7、ex A - MCS proforma . A.l Introduction A.2 Identification of the implementation . A.3 Identification of the Recommendation in which the management information is defined . A.4 Management conformance summary 6.1 Use of ASN.1 NameType syntax Annex B - MOCS proforma . B . 1 B.2 B.3 B . 4 B.5 B.6 B.7 B.

8、8 B . 9 B.10 B.ll B.12 B.13 B.14 B.15 B.16 B.17 B.18 B.19 B . 20 B.21 B.22 B.23 B.24 B.25 B.26 B.27 Introduction Instructions for completing the MOCS proforma to produce a MOCS Statement of conformance to the alarmseverity AssignmentProfile object class Statement of conformance to the circuitEndPoin

9、tSubgroup object class . Statement of conformance to the connectionR1 object class Statement of conformance to the connectionTerminationPointBidirectional object class Statement of conformance to the connectionTerminationPointSink object class . Statement of conformance to the connectionTerminationP

10、ointSource object class . Statement of conformance to the crossConnection object class . Statement of conformance to the equipment object class . Statement of conformance to the equipmentR1 object class Statement of conformance to the circuitPack object class Statement of conformance to the equipmen

11、tHolder object class Statement of conformance to the fabric object class Statement of conformance to the fabricR1 object class Statement of conformance to the gtp object class . Statement of conformance to the managedElement object class Statement of conformance to the mpCrossConnection object class

12、 . Statement of conformance to the namedlrossconnection object class Statement of conformance to the namedMpCrossConnection object class Statement of conformance to the network object class . Statement of conformance to the softwareRl object class . Statement of conformance to the tpPool object clas

13、s . Statement of conformance to the managedElementR1 object class Statement of conformance to the software object class Statement of conformance to the trailR1 object class . Statement of conformance to the trailTerminationPointBidirectiona1 object class . Recommendation M.3101 (07/95) Page 1 1 1 1

14、2 2 2 2 2 3 4 5 7 7 7 8 10 14 16 20 23 26 29 30 34 38 42 44 47 48 52 57 58 60 62 63 67 70 71 74 1 STD.ITU-T RECMN M.3101-ENGL 1775 48b2571 Ob23513 088 B.28 B.29 B.30 B.31 Statement of conformance to the trailTerminationPointSink object class Statement of conformance to the networkR1 object class Sta

15、tement of conformance to the managedElementComplex object class Statement of conformance to the trailTerminationPointSource object class Annex C - MRCS proforma . C.l Introduction C.2 C.3 Name binding support . Appendix I - MOCS proforma . 1.1 Introduction 1.2 1.3 Statement of conformance to the con

16、nection object class 1.4 Statement of conformance to the trail object class . Appendix II - MRCS proforma II.1 Introduction II.2 II.3 Mame binding support . Instructions for completing the MRCS proforma to produce a MRCS Instructions for completing the MOCS proforma $0 produce a MOCS Instructions fo

17、r completing the MRCS proforma to produce a MRCS Page 77 80 83 85 87 87 87 88 91 91 91 92 95 99 99 99 100 ii Recommendation M.3101 (07/95) STD-ITU-T RECMN M-31OL-ENGL 1775 W Li8b2571 Ob235LLi TLLi m Recommendation M.3101 MANAGED OBJECT CONFORMANCE STATEMENTS FOR THE GENERIC NETWORK INFORMATION MODEL

18、 (Geneva, 1995) 1 Scope This Recommendation defines management conformance requirements of the Generic Network Information Model (GNIM) defined in Recommendation M.3 100. This Recommendation does not define conformance requirements for management information that is only referred to in Recommendatio

19、n M.3100. 2 References The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to rev

20、ision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. - - ITU-T Recommendation M.310 (19

21、99, Generic network information model. ITU-T Recommendation Q.821 (1993), Stage 2 and stage 3 description for the Q3 interface - Alarm surveillance. - ITU-T Recommendation X.291 (1995), OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications - Abstract t

22、est suite specification. ITU-T Recommendation X.296 (1996), OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications - Implementation conformance statement. CCIT Recommendation X.721 (1992), Information technology - Open Systems Interconnection - Structur

23、e of management information: Definition of management informution. ITU-T Recommendation X.724 (1993), Information technology - Open System Interconnection - Structure of management information: Requirements and guidelines for implementation conformunce statement profomas associated with OSI manageme

24、nt. - - - 3 Abbreviations For the purposes of this Recommendation, the following abbreviations are used: GNIM Generic Network Information Model MCS Management Conformance Summary MOCS Managed Object Conformance Statement MRCS Managed Relationship Conformance Statement 4 Management information confor

25、mance requirements A Management Conformance Summary (MCS) proforma which conforms to this Recommendation shall be textually identical to the MCS proforma specified in Annex A, differing only in pagination and page headers. Managed Object Conformance Statement (MOCS) proforma of managed object classe

26、s defined in Recommen- dation M.3100, which conforms to this Recommendation shall be textually identical to the MOCS proforma specified in Annex B, differing only in pagination and page headers. Recommendation M.3 101 (OW99 1 STD-ITU-T RECMN M*3LOL-ENGL 1995 48b259L Ob23515 750 Managed Relationship

27、Conformance Statement (MRCS) proforma for name bindings defined in Recommenda- tion M.3100, which conforms to this Recommendation shall be textually identical to the MRCS proforma specified in Annex C, differing only in pagination and page headers. A supplier of a system which conforms to this Recom

28、mendation and Recommendation M.3100 shall: - - - - provide the information necessary to uniquely identify both the supplier and the implementation; complete the management conformance summary proforma in Annex A; complete the managed object conformance statement proformas in Annex B; complete the ma

29、naged relationship conformance statement proformas in Annex C. 5 Structure The management conformance summary is contained in Annex,A. The MCS does not include conformance summary of the deprecatedobsolete managed object classes and name binding that are included in Appendix Wv.3100. Annex B defines

30、 MOCS proformas for those managed object classes that are defined in the main part of Recom- mendation M.3 1100, Le. excluding deprecated/obsolete managed object classes defined in Appendix WM.3 100. Annex C defines MRCS proformas for name bindings defined in Recommendation M.3100. Appendix I define

31、s MOCS proformas for deprecatedobsolete managed object classes and name bindings defined in Appendix IL/M.31100. Appendix II defines MRCS proformas for deprecatedobsolete name bindings included in Appendix IIIM.3 100. 6 Additional guidelines 6.1 The NameType syntax is used for naming and is defined

32、as a choice of integer or string syntax. An implementation may use either or both of these alternatives (for different object instances). The use of these syntaxes affect the behaviour of filtered operations. The supplier of a system which conforms to this Recommendation and Recommendation M.3 100 s

33、hall, for each attribute using the Nameype syntax, indicate the expected result in the “Additional information” column. Use of ASNA NameType syntax Annex A MCS proforma) (This annex forms an integral part of this Recommendation) A.1 Introduction A.l.l Purpose and structure The Management Conformance

34、 Summary (MCS) is a statement by a supplier that identifies an implementation and provides information on whether the implementation claims conformance to any of the listed set of standards that specify conformance requirements to OS1 management. Users of this R.ecommendation may freely reproduce th

35、e MCS proforma in this annex so that it can be used for its intended pur- pose, and may further publish the completed MCS. 2 Recommendation M.3101 (07/95) The MCS proforma is a document, in the form of a questionnaire, designed by a proforma specifier, that when completed by the supplier of an imple

36、mentation becomes the MCS. AL2 The supplier of the implementation shall enter an explicit statement in each of the boxes provided. Specific instruction is provided in the text which preceedes each table. A.1.3 Symbols and abbreviations The following abbreviations are used throughout the proformas of

37、 Annexes A, B and C. m3 1 OOInformationModel m3 1000bjectClass Instructions for completing the MCS proforma to produce the MCS2) ( ccitt(0) recommendation(0) m( 13) gnm(3 100) informationModel(0) ( m3 100InformationModel managedObjectClass(3) ) m3 100NameBinding m3 100Attribute m3100Action m3 1 OOIn

38、formationModei nameBinding(6) ) ( m3 100InformationModel attribute(7) m3100InformationModel action(9) q82 1 InformationModel q821Paameter smi2Mobj ectllass smi2NameBinding ccitt(0) recommendation(0) q( 17) q821(821) informationModel(0) ) q82 1InformationModel parameter(9) joint-iso-ccitt(2) ms(9) sm

39、i(3) part2(2) managedObjectClass(3) ) ( joint-iso-ccitt(2) ms(9) smi(3) part2(2) nameBinding(6) smi2AttributeID smi2Notifcation joint-iso-ccitt(2) ms(9) smi(3) parQ(2) attribute(7) ( joint-iso-ccitt(2) ms(9) smi(3) part2(2) notification( 10) A.2 Identification of the implementation A.2.1 Date of sta

40、tement The supplier of the implementation shall enter the date of this statement in the box below. Use the format DD-MM- YYYY. Date of statement A.2.2 Identification of the implementation The supplier of the implementation shall enter information necessary to uniquely identify the implementation and

41、 the system(s) in which it may reside, in the box below. *) Instructions for completing the MCS proforma are specified in Rec. X.724 I ISOAEC 10165-6, clause 5. Recommendation M.3101 (07/95) 3 STD-ITU-T RECMN M-31OL-ENGL 1775 9 48b257L Ob23517 723 A.2.3 Identification of the implementation The suppl

42、ier of the implementation shall enter information necessary to uniquely identify the implementation and the system(s) in which it may reside, in the box below. E A.2.4 Contact The supplier of the implementation shall provide information on whom to contact if there are any queries concerning the cont

43、ent of the MCS, in the box below. A.3 Identification of the Recommendation in which the management information is defined The supplier of the implementation shall enter the title, reference number and date of the publication of the Recommendation I International Standard which specifies the manageme

44、nt information to which conformance is claimed, in the box below. -_ Recommendation to which conformance is claimed I A.3.1 Technical corrigenda implemented The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify the Recommendation to the

45、 identified Recommendation, in the box below. 4 Recommendation M.3101 (07195) A.4 Management conformance summary The supplier of the implementation shall provide information on whether the implementation claims conformance to any of the set of standards globally representing the implementation under

46、 claim. For each standard the supplier of the implementation claims conformance to, the corresponding conformance statement(s) shall be filled in, or referenced by, the MCS. Columns 7 (Support), 8 (Table numbers of PICSMOCSMRCS) and 9 (Additional information) are to be filled in by the supplier of t

47、he implementation. The following common notations, defined in Rec. X.291 I ISOAEC 9646-2 and Rec. X.296 I ISOEC 9646-7 are used for the status value column: m mandatory; O optional; C conditional; X prohibited; - not applicable or out of scope. Note that “c”, “m”, “O and “x” are prefixed by a “c:” w

48、hen nested under a conditional or optional item of the same table. Note that “O” may be suffixed by “.n” (where “n” is a unique number) for mutually exclusive or selectable options among a set of status values. The following common notations, defined in Rec. X.724 I ISO/IEC 10165-6 and Rec. X.296 I

49、ISOEC 9646-7 are used for the support answer column: Y implemented; N not implemented; - no answer required; Ig See Tables A. 1 to A.3. the item is ignored (i.e. processed syntactically but not semantically). I Index TABLE A.lM.3101 Identification of the Table numbers of Description Constraints and Status Support Table Additional document including PICS proforma values numbers of information the PICS proforma PICS Recommendation M.3101 (07/95) 5 - STD-ITU-T RECMN M-3101-ENGL 1775 VBb2571 Ob23517 5Tb TABLE A.2M.3101 MOCS