ITU-T X 780 AMD 1-2002 TMN Guidelines for Defining CORBA Managed Objects Amendment 1 System Objects and User Guide for Bulk Attribute Retrieval - Series X Data Networks and Open Synt.pdf

《ITU-T X 780 AMD 1-2002 TMN Guidelines for Defining CORBA Managed Objects Amendment 1 System Objects and User Guide for Bulk Attribute Retrieval - Series X Data Networks and Open Synt.pdf》由会员分享，可在线阅读，更多相关《ITU-T X 780 AMD 1-2002 TMN Guidelines for Defining CORBA Managed Objects Amendment 1 System Objects and User Guide for Bulk Attribute Retrieval - Series X Data Networks and Open Synt.pdf（12页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.780 Amendment I (05/2002) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OS1 management - Management functions and ODMA functions TMN guidelines for defining CORBA managed objects Amendment I : Syst

2、em objects and user guide for bulk attribute retrieval ITU-T Recommendation X.780 (2001) - Amendment 1 ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS PUBLIC DATA NETWORKS Services and facilities Interfaces Transmission, signalling and switching Network aspects Maintenanc

3、e Administrative arrangements Model and notation Service definitions Connection-mode protocol specifications Connectionless-mode protocol specifications PICS proformas Protocol Identification Security Protocols Layer Managed Objects Conformance testing General Satellite data transmission systems IP-

4、based networks MESSAGE HANDLING SYSTEMS DIRECTORY OS1 NETWORKING AND SYSTEM ASPECTS Networking Efficiency Quaity of service Naming, Addressing and Registration Abstract Syntax Notation One (ASN. 1) Systems Management framework and architecture Management Communication Service and Protocol OPEN SYSTE

5、MS INTERCONNECTION INTERWORKING BETWEEN NETWORKS OS1 MANAGEMENT X. 1-X.19 X.20-X.49 X.50-X.89 X.90-X. 149 X.150-X.179 X. 180-X. 199 X.200-X.209 X.210-X.219 X.220-X.229 X.230-X.239 X.240-X.259 X.260-X.269 X.270-X.279 X.280-X.289 X.290-X.299 X.300-X.349 X.350-X.369 x.370-x.399 X.400-X.499 X.500-X.599

6、X.600-X.629 X. 63 0-X. 63 9 X.640-X.649 X.650-X.679 X.680-X.699 X.700-X.709 X.710-X.719 structure of Management Information X.720-X.729 SECURJTY X.800-X.849 OS1 APPLICATIONS Commitment, Concurrency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED PROCESSING X.850-X.859 X.860-X.

7、879 X.880-X.899 X.900-X.999 For further details, please refer to the lst of ITU-T Recommendations. ITU-T Recommendation X.780 TMN guidelines for defining CORBA managed objects Amendment 1 System objects and user guide for bulk attribute retrieval Summary This amendment to ITU-T Rec. X.780 (2001) add

8、s the definition of the System and Subsystem managed objects, and a non-normative appendix containing a user guide. Source Amendment 1 to IT-T Recommendation X.780 (2001) was prepared by ITU-T Study Group4 (200 1-2004) and approved under the WTSA Resolution 1 procedure on 29 May 2002. ITU-T RW. X.78

9、0 (2001)/Amd.l(05/2002) 1 FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating

10、 and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produc

11、e Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this

12、Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL, PROPERTY RIGHTS IT draws attention to the possibility that the practice or implementation of this Recommendation may involve th

13、e use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommenda

14、tion, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. o ITU

15、2002 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of IT. ii ITU-T Rec. X.780 (2001)/Amd.l(05/2002) CONTENTS Page 1) Clause 2.1 . 2) New clauses 5.8 and 5.9 . 5.8 System Managed Object . 5.8.1 5.9 Subsystem Managed O

16、bject . Notifications On The System Managed Object 3) Annex A 4) New Appendix II 1 1 2 2 6 . ITU-T RW. X.780 (2001)/Amd.l(05/2002) 111 ITU-T Recommendation X.780 Object Creation Object Deletion State Change TMN guidelines for defining CORBA managed objects “itut-x7 80: :createDeleteNotificationsPack

17、age“ “itutx780:createDeleteNotificationsPackage“ “itut-x780: : stateChangeNotXicationPackage“ , Amendment 1 System Objects and user guide for bulk attribute retrieval 1) Clause 2.1 Add the following new reference to clause 2.1: SI ITU-T Recommendation X.720 (1992) I ISOhEC 1 O 165: 1993, Information

18、 technology - Open Systems Interconnection - Structure of management information: Management infor- mation model. 2) Add the following new clauses aJter clause 5.7: New clauses 5.8 and 5.9 5.8 System managed object In addition to the top-most ManagedObject class, the IDL also contains a couple of ma

19、naged object definitions that specialize ManagedObject. The System managed object class is used to represent a set of hardware and software that forms an autonomous whole capable of performing information processing andor information transfer. The entire specification of the sequence of name binding

20、s to be used in constructing the distinguished name for a System managed object is outside the scope of this Recommendation. Examples of names for systems are specified in ITU-T Rec. X.720 8. An instance of this managed object class may be used as the superior in naming managed objects representing

21、either information processing and or information transfer resources contained within this instance. Note that the managed object defined here does not have the ITU-T Rec. X.721 6 Supported Features attribute since the CORBA interface does not define negotiable Functional Units. 5.8.1 The System mana

22、ged object has the following notifications: Notifications on the system managed object Table dX.780 - System notifications I Notification I Conditional Package (if Conditional) I Changes in the following states (when defined) will cause State Change notifications (when supported) to be emitted: - Ad

23、ministrative State. - Operational State. - Usage State. ITU-T Rw. X.780 (2001)/Amd.l(05/2002) 1 5.9 Subsystem managed Object The Subsystem managed object is a subclass of the System managed object class (see 5.8) and is contained by a System or another Subsystem managed object class instance. The Su

24、bsystem managed object class may be used as a common containment point for managed objects in a system that relate to the operation of a given layer. The choice of structuring within a system is dependent on what structure the system designer wishes to present externally for management purposes. Thi

25、s managed object class represents a portion of a system where components are named independently of the components of other subsystems. 3) Annex A Add the following to the IDL in Annex A. After the last exception in the “EXCEPTIONS“ portion of the IDL, which is shown in this line: exception Invalids

26、tring ; Add these lines: const string administrativestatepackage = “itut 744dl:administrativeStatePackagel; const string createDeleteNotificationsPackage = 11itutx744dl:createDeleteNotificationsPackage11; const string stateChangeNotificationPackage = 11itut-x744dl:stateChangeNotificationPackage11; e

27、xception NOadministrativeStatePackage ; After the MANAGED OBJECT FACTORY INTERFACE dejkition, which ends with this line: ; / end of ManagedObjectFactory interface Add the following lines: / SYSTEM INTERFACE /* This valuetype is used to retrieve multiple attributes. */ valuetype SystemValueType : tru

28、ncatable ManagedObjectValueType public OperationalStateType operationalstate; public UsageStateType usagestate; public AdministrativeStateType administrativestate; / GET / GET / GET-REPLACE / administrativestatepackage ; / valuetype SystemValueType /* The System managed object class is used to repre

29、sent a set of and software that forms an autonomous whole capable of performing information processing and/or information transfer. hardware The entire specification of the sequence of name bindings to be used in constructing the distinguished name for a System managed object is outside the scope of

30、 this Recommendation. Name bindings to the Recommendation M.3120 Managed Element managed object class is supplied. Examples of names for systems are specified in Recommendation X.720. NOTE - This definition does not correspond to real open system but corresponds to real systems in Recommendation X.2

31、00. 2 ITU-T RM. X.780 (2001)/Amd.l(05/2002) An instance of this managed object class may be used as the superior in naming managed objects representing either information processing and or information transfer resources contained within this instance. Note that this does not have the Supported Featu

32、res attribute defined in Recommendation X.721, since the CORBA interface does not define negotiable Functional Units. */ interface System : Managedobject I /* Operational State, Usage State and Administrative State are described in Recommendation X.731 */ OperationalStateType OperationalStateGet ()

33、raises (ApplicationError) ; UsageStateType usageStateGet (1 raises (ApplicationError) ; /* */ PRESENT IF an instance supports it. AdministrativeStateType administrativeStateGet () raises (ApplicationError, NOadministrativeStatePackage) ; void administrativestateset in AdministrativeStateType adminis

34、trativestate) raises (ApplicationError, NOadministrativeStatePackage); CONDITIONALNOTIFICATION( Notifications, objectcreation, createDeleteNotificationsPackage) CONDITIONALNOTIFICATION ( Notifications, objectDeletion, createDeleteNotificationsPackage) CONDITIONALNOTIFICATION( Notifications, statecha

35、nge, StateChanqeNotificationPackage) ; / interface System / SYSTEM FACTORY INTERFACE /* */ Factory for System interface SystemFactory : Managec ManagedObject create 3bj ect actory (in NameBindingType nameBinding, in MONameType superior, in string reqID, / auto naming if empty string out MONameType n

36、ame, in AdministrativeStateType administrativestate / GET-REPLACE ITU-T RC. X.780 (2001)/Amd.l (092002) 3 / administrativeStatePackage ) raises (ApplicationError , CreateError) ; ; / interface SystemFactory / SUBSYSTEM INTERFACE /* This valuetype is used to retrieve multiple attributes. */ valuetype

37、 SubsystemValueType : truncatable SystemValueType ; / valuetype SubsystemValueType /* The Subsystem managed object class may be used as a common containment point for managed objects in a system that relate to the operation of a given layer. The choice of structuring within a system is dependent on

38、what structure the system designer wishes to present externally for management purposes. This managed object class represents a portion of a system where components are named independently of the components of other subsystems. */ interface Subsystem : System ; / interface Subsystem / SUBSYSTEM FACT

39、ORY INTERFACE /* */ Factory for Subsystem interface SubsystemFactory : ManagedObjectFactory ManagedObject create (in NameBindingType nameBinding, in MONameType superior, in string reqID, / auto naming if empty string out MONameType name, in AdministrativeStateType administrativestate / GET-REPLACE /

40、 administrativestatepackage ) raises (ApplicationError, CreateError) ; ; / interface SubsystemFactory AJter the defmition of the NOTIFICATIONS INTERFACE, which ends with this line: ; / end of Notifications interface 4 ITU-T Rec. X.780 (2001)/Amd.l(05/2002) Add the following lines: / NAME BINDINGS /*

41、 This name binding is used to name the System object relative to the local root. That is, enable it to be the top-most managed object on a system. */ module System const string superiorclass = II1 ; const boolean superiorSubclassesAllowed = FALSE; const string SubordinateClass = 1ritut-x780:Systern1

42、1; const boolean subordinateSubclassesAllowed = TRUE; const boolean managerCreatesAllowed = FALSE; const DeletePolicyType deletepolicy = const string kind = llSystemll; itut-x780:deleteOnlyIfNoContainedObjects; ; / module System /* This name binding is used to name the Subsystem object relative to a

43、 Subsystem object. */ module Subsystem-Subsystem const string superiorClass = 11itut-x780:Subsystem11; const boolean superiorSubclassesAllowed = TRUE; const string subordinateClass = r1itut-x780:Subsystemf1; const boolean SubordinateSubclassesAllowed = TRUE; const boolean managerCreatesAllowed = TRU

44、E; const DeletePolicyType deletepolicy = const string kind = “Subsystem“; itut-x780:deleteOnlyIfNoContainedObjects; ; / module Subsystem-System /* This name binding is used to name the Subsystem object relative to a System object. */ module Subsystem-System const string superiorClass = f1itut-x780:S

45、ystemf1; const boolean superiorSubclassesAllowed = TRUE; const string subordinateClass = 11itut-x780:Subsystem11; const boolean subordinateSubclassesAllowed = TRUE; const boolean managerCreatesAllowed = TRUE; const DeletePolicyType deletepolicy = const string kind = 18Subsystemf1 ; itut-x780:deleteO

46、nlyIfNoContainedObjects; ; / module Subsystem-System ITU-T RC. X.780 (2001)/Amd.l(05/2002) 5 4) New Appendix II Add the following new non-normative appendix: Appendix II User guide for bulk attribute retrieval This appendix provides additional information about the TMN CODA framework intended to hel

47、p those implementing systems that conform to the framework Recommendations. Bulk retrieval of attributes The top-most managed object interface, ManagedObject, defines an operation that enables a managing system to retrieve multiple attributes from a managed object in one operation. The signature of

48、this operation, AttributesGet, is shown below: ManagedObjectValueType attributesGet ( in NameType name, inout StringSetType attributeNames) raises (ApplicationError); Note that the names of the attributes requested by the managing system are submitted in the UttributeNames parameter, and the names o

49、f the attributes actually returned by the managed object are also returned in the uttributeNames parameter. Because the list of attributes returned by the managed object may differ from the requested list, the inlout parameter attributeNames may be changed by the managed object. Managing system implementations that wish to repeatedly use the same list of attributes will not want that list modified by the managed object. One solution to this problem is made possible by the way in which