1、INTERNATIONAL TELECOMMUNICATION UNION#)44 8 THE INTERNATIONAL (01/92)TELEGRAPH AND TELEPHONECONSULTATIVE COMMITTEE$!4! #/-5.)#!4)/. .%47/2+3). establishes a model that relates the services and generic definitions provided by this function to userrequirements; defines the services provided by the fun
2、ction; defines generic notification types and parameters documented in accordance with CCITT Rec. X.722 |ISO/IEC 10165-4; specifies the protocol that is necessary in order to provide the services; defines the relationship between these services and management operations and notifications; specifies
3、compliance requirements placed on other Standards that make use of these generic definitions; defines relationships with other systems management functions; specifies conformance requirements.This Recommendation | International Standard does not define the nature of any implementation intended to pr
4、ovide the object management function; specify the manner in which management is accomplished by the user of the object managementfunction; define the nature of any interactions which result in the use of the object management function; specify the services necessary for the establishment, normal and
5、 abnormal release of a managementassociation; preclude the definition of further notification types; define managed objects.2 Normative referencesThe following CCITT Recommendations and International Standards contain provisions which, through reference inthis text, constitute provisions of this Rec
6、ommendation | International Standard. At the time of publication, the editionsindicated were valid. All Recommendations and Standards are subject to revision, and parties to agreements based onthis Recommendation | International Standard are encouraged to investigate the possibility of applying the
7、most recenteditions of the Recommendations and Standards indicated below. Members of IEC and ISO maintain registers ofcurrently valid International Standards. The CCITT Secretariat maintains a list of the currently valid CCITTRecommendations.ISO/IEC 10164-1 : 1993 (E)2 CCITT Rec. X.730 (1992 E)2.1 I
8、dentical Recommendations | International Standards CCITT Recommendation X.701 (1992) | ISO/IEC 10040:1992, Information technology Open SystemsInterconnection Systems managemet overview. CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1:1993, Information technology Open SystemsInterconnection Struc
9、ture of management information: Management information model. CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, Information technology Open SystemsInterconnection - Structure of management information: Definition of management information. CCITT Recommendation X.722 (1992) | ISO/IEC 10165-4:
10、1992, Information technology OpenSystems Interconnection Structure of management information: Guidelines for the definition ofmanaged objects. CCITT Recommendation X.733 (1992) | ISO/IEC 10164-4:1992, Information technology OpenSystems Interconnection Systems Management: Alarm reporting function. CC
11、ITT Recommendation X.734 (1992) | ISO/IEC 10164-5:1993, Information technology Open SystemsInterconnection Systems Management: Event report management function. CCITT Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, Information technology Open SystemsInterconnection Systems Management: Log contro
12、l function.2.2 Paired Recommendations | International Standards equivalent in technical content CCITT Recommendation X.200 (1988), Reference Model of Open Systems Interconnection for CCITTApplications.ISO 7498:1984, Information processing systems Open Systems Interconnection Basic ReferenceModel. CC
13、ITT Recommendation X.209 (1988), Specification of basic encoding rules for Abstract SyntaxNotation One (ASN.1).ISO/IEC 8825:1990, Information technology Open Systems Interconnection Specification of BasicEncoding Rules for Abstract Syntax Notation One (ASN.1). CCITT Recommendation X.210 (1988), Open
14、 Systems Interconnection. Layer Service DefinitionConventions.ISO/TR 8509:1987, Information processing systems Open Systems Interconnection Serviceconventions. CCITT Recommendation X.290 (1992), OSI conformance testing methodology and framework forprotocol Recommendations for CCITT applications Gene
15、ral concepts.ISO/IEC 9646-1:1991, Information technology Open Systems Interconnection Conformance testingmethodology and framework Part 1: General concepts. CCITT Recommendation X.700 (1992), Management Framework Definition for Open SystemsInterconnection (OSI) for CCITT Applications.ISO/IEC 7498-4:
16、1989, Information processing systems Open Systems Interconnection BasicReference Model Part 4: Management framework. CCITT Recommendation X.710 (1991), Common Management Information Service Definition for CCITTapplications.ISO/IEC 9595:1991, Information technology Open Systems Interconnection Common
17、 managementinformation service definition.2.3 Additional references ISO/IEC 9545:1989, Information technology Open Systems Interconnection Application layerstructure.ISO/IEC 10164-1 : 1993 (E)CCITT Rec. X.730 (1992 E) 33 DefinitionsFor the purposes of this Recommendation | International Standard, th
18、e following definitions apply.3.1 Basic reference model definitionsThis Recommendation | International Standard makes use of the following term defined in CCITT Rec. X.200 |ISO 7498:a) open system;b) systems management;c) layer management.d) OSI environment;3.2 Management framework definitionsThis R
19、ecommendation | International Standard makes use of the following term defined in CCITT Rec. X.700 | ISO/IEC7498-4:managed object3.3 CMIS definitionsThis Recommendation | International Standard makes use of the following term defined in CCITT Rec. X.710 | ISO/IEC9595:attribute3.4 Systems management
20、overview definitionsThis Recommendation | International Standard makes use of the following terms defined in CCITT Rec. X.701 |ISO/IEC 10040:a) agent;b) agent role;c) dependent conformance;d) general conformance;e) generic definitions;f) managed object class;g) manager;h) manager role;i) notificatio
21、n;j) systems management functional unit;k) systems management function;l) systems management application protocol;m) (systems management) operation.3.5 Management information model definitionsThis Recommendation | International Standard makes use of the following term defined in CCITT Rec. X.720 | I
22、SO/IEC10165-1:managed object boundaryISO/IEC 10164-1 : 1993 (E)4 CCITT Rec. X.730 (1992 E)3.6 Service conventions definitionsThis Recommendation | International Standard makes use of the following terms defined in CCITT Rec. X.210 | ISO/TR8509:a) confirm (primitive);b) confirmed-service;c) indicatio
23、n (primitive);d) non-confirmed-service;e) request (primitive);f) response (primitive);g) service-user;h) service-provider.3.7 OSI conformance testing definitionsThis Recommendation | International Standard makes use of the following term defined in CCITT Rec. X.290 | ISO/IEC9646-1:system conformance
24、 statement4 AbbreviationsASN.1 Abstract Syntax Notation OneCMIS Common Management Information serviceConf ConfirmationInd IndicationMAPDU Management application protocol data unitOSI Open systems interconnectionReq RequestRsp ResponseSMAPM Systems management application protocol machineSMI Structure
25、 of management information5 ConventionsThis Recommendation | International Standard defines services for the object management function following thedescriptive conventions defined in CCITT Rec. X.210 | ISO/TR 8509. In clause 9, the definition of each service includesa table that lists the service p
26、arameters. For a given service primitive, the presence of each parameter is described by oneof the following values.M the parameter is mandatory;(=) the value of the parameter is equal to the value of the parameter in the column to the left;U the use of the parameter is a Service-user option; the pa
27、rameter is not present in the interaction described by the primitive concerned;C the parameter is conditional;P the parameter is subject to the constraints imposed by CCITT Rec. X.710 | ISO/IEC 9595.NOTE The parameters that are marked “P” in service tables of this Recommendation | International Stan
28、dard are mappeddirectly onto the corresponding parameters of the CMIS service primitive, without changing the semantics or syntax of theparameters. The remaining parameters are used to construct an MAPDU.ISO/IEC 10164-1 : 1993 (E)CCITT Rec. X.730 (1992 E) 56 RequirementsThe MIS-User needs the abilit
29、y to create and delete managed objects; examine and modify the value of attributes of managed objects; be made aware of changes in the configuration of managed objects.7 Model7.1 IntroductionEach resource that is subject to systems management is represented by a managed object. These are described i
30、n CCITTRec. X.720 | ISO/IEC 10165-1.Managed objects can be created and deleted, and values of attributes of managed objects can be changed, in one or moreof three distinct ways through configuration processes in the local system environment that are outside the scope of OSI; through the (N)-layer op
31、eration and/or the layer management of an open system, as described in those(N)-layer standards; through the OSI systems management services.Object management describes services for the reporting of creation and deletion of managed objects; the reporting of changes to attribute values of managed obj
32、ects.Object management describes pass-through services for the creation and deletion of managed objects; performing actions upon managed objects; attribute changing; attribute reading; event reporting.7.2 Pass-through servicesWhere different parts of systems management functions define operations or
33、 notifications, then they do so independentlyof their mapping onto an underlying communications service. This enables this Recommendation | InternationalStandard to be used across a range of underlying communications services by other systems management functions ormanaged objects. When a systems ma
34、nagement function defines specific systems management services, then theseservices shall map directly onto the CMIS services.In order to achieve this objective it is necessary for one of the systems management Recommendations | InternationalStandards to detail the mapping between the operations and
35、notifications that apply across a managed object boundaryand the underlying communications services. This Recommendation | International Standard is used to document suchmapping.Currently, only the mapping onto CMIS are defined by this Recommendation | International Standard through the use ofpass-t
36、hrough services.Except where this Recommendation | International Standard describes specific services, the management operations andnotifications that apply across a managed object boundary shall map onto the pass-through services of thisRecommendation | International Standard as shown in Table 1.IS
37、O/IEC 10164-1 : 1993 (E)6 CCITT Rec. X.730 (1992 E)The management operations are described in CCITT Rec. X.720 | ISO/IEC 10165-1.Table 1 Mapping of pass-through services8 Generic definitionsThe set of generic notifications, parameters and semantics defined by this Recommendation | International Stan
38、dardprovide the detail for the following general parameters of the M-EVENT-REPORT service as defined by CCITTRec. X.710 | ISO/IEC 9595: event type; event information; event reply.All notifications are potential entries in a systems management log and this Recommendation | International Standarddefin
39、es three managed object classes for this purpose. CCITT Rec. X.721 | ISO/IEC 10165-2 defines a generic event logrecord object class from which all entries are derived, the additional information being specified by the eventinformation and event reply parameters.8.1 Event typeThis parameter defines t
40、he type of the event. The following three event types are defined in this Recommendation |International Standard: object creation: An indication that a managed object instance has been created. Where a managed objectclass is required to report the creation of a managed object instance, then that man
41、aged object class shallimport the object creation notification type. The creation of a managed object within an open system canbe as a result of a PT-CREATE service, or a local operation within the open system; object deletion: An indication that a managed object instance has been deleted. Where a m
42、anaged objectclass is required to report the deletion of a managed object instance, then that managed object class shallimport the object deletion notification type. The deletion of a managed object within an open system canbe as a result of a PT-DELETE service, or a local operation within the open
43、system; attribute value change: An indication that the attribute value(s) of a managed object has changed. Thisnotification type is used to report one or more of the following:a) the addition of one or more new members to one or more set-valued attributes;b) the removal of one or more members from o
44、ne or more set-valued attributes;SMI Pass-throughCreate PT-CREATEDelete PT-DELETEAction PT-ACTIONReplace PT-SETAdd PT-SETRemove PT-SETReplace-with-Default PT-SETGet PT-GETNotification PT-EVENT-REPORTISO/IEC 10164-1 : 1993 (E)CCITT Rec. X.730 (1992 E) 7c) the replacement of the value of one or more a
45、ttributes;d) the changing of the value of one or more attributes to their default value(s);through either the internal operation of the resource or via management operation. This notification typeshall not be used for conveying attribute value changes which have specific notification types alreadyde
46、fined.It is the role of the managed object class definer to fully detail the requirements that a managed object class has forgenerating one or more of the above notification types. For the attribute value change notification, this includesidentifying which attributes, and which value changes to thos
47、e attributes, are significant enough to warrant thenotification being emitted.8.2 Event informationThe following parameters constitute the notification specific event information.8.2.1 Object creation notification parametersThe following parameters are defined for the object creation notification.8.
48、2.1.1 Source IndicatorThis parameter, when present, indicates the source of the operation that led to the generation of this notification type. Itcan have one of the following values: resource operation: The notification was generated in response to a creation effected through the internaloperation
49、of the resource; management operation: The notification was generated in response to a creation effected through an SMImanagement operation applied across the managed object boundary external to the managed object; unknown: It is not possible to determine the source of the operation.8.2.1.2 Attribute listThis parameter, when present, contains a list of attributes and their values at the time the managed object was created.The managed object class definition may specify which at
