GB/T 17142-1997 Information technology Open Systems Interconnection System management overview
Some standard content:
GB/T17142-1997
This standard is equivalent to ISO/IEC10040:1992 "Information Technology Open Systems Interconnection System Management Overview", ISO/IEC10040:1992/Cor.1:1994 "Information Technology Open Systems Interconnection System Management Overview Technical Revision 1", ISO/IEC10040:1992/Cor.2:1996 "Information Technology Open Systems Interconnection System Management Overview Technical Revision 2" and ISO/IEC10040:1992/Amd.1:1995 "Information Technology Open Systems Interconnection System Management Overview Supplement 1". Appendix A of this standard is the standard appendix, and Appendix B is the indicative appendix. This standard was proposed by the Ministry of Electronics Industry of the People's Republic of China. This standard is under the jurisdiction of the Standardization Institute of the Ministry of Electronics Industry. The drafting unit of this standard: Standardization Institute of the Ministry of Electronics Industry. The main drafters of this standard are Zheng Hongren, Zhou Xiaohua, Dai Hao, and Zhang Xiaotao. 434
GB/T 17142—1997
ISO/IEC Foreword
ISO (International Organization for Standardization) and IEC (International Electrotechnical Commission) are specialized organizations for standardization worldwide. National member bodies (which are members of ISO or IEC) participate in the development of international standards for specific technical areas through technical committees established by the international organizations. ISO and IEC technical committees cooperate in areas of common interest. Other official and non-official international organizations in contact with ISO and IEC may also participate in the development of international standards. For information technology, ISO and IEC have established a joint technical committee, ISO/IECJTC1. Draft international standards proposed by the joint technical committee are circulated to national member bodies for voting. To publish an international standard, at least 75% of the national member bodies participating in the voting must vote in favor.
ISO/IEC10040 was developed by the ISO/IECJTC1 Joint Technical Committee "Information Technology" in cooperation with CCITT. The equivalent text is CCITT X.701.
Appendix A forms part of this standard.
Appendix B is for information only.
1 Scope
National Standard of the People's Republic of China
Information technology-Open Systems Interconnection
Systems management overview
Information technology-Open Systems Interconnection-Systems management overview
This standard
provides an overview of the systems management standard series; GB/T 17142 - 1997
idt IS0/IEC 10040:1992
Establishes the basis for dividing systems management standards into independent groups, defining the scope of each group and identifying the major components in each group; - provides guidance for the development of systems management standards and identifies how they relate to each other, and defines the terms used by other systems management standards; - can be used for definitions of all systems management standards and various aspects of system management of any size; - can be used in situations where the response to systems management is centralized and decentralized; establishes a model for systems management, identifies several aspects of systems management (for example: information, function, communication and organization), and further refines the model to clarify these aspects; determines the requirements for conformance and the guiding principles for claims of conformance to systems management standards. There are no conformance requirements in the main body of this standard, but it specifies the standards that should be followed to meet the system management requirements. Appendix A of this standard defines an application context for system management and specifies rules for negotiating system management functional units. There are conformance requirements associated with these rules. 2 Referenced standards
The provisions contained in the following standards constitute the provisions of this standard through reference in this standard. The versions shown are valid at the time of publication of this standard. All standards are subject to revision, and parties using this standard should explore the possibility of using the latest versions of the following standards. GB9387--88 Information Processing Systems Open Systems Interconnection Basic Reference Model (idtISO7498:1984,eqvCCITT X.200:1988)
GB/T9387.4-1996 Information Processing Systems Open Systems Interconnection Basic Reference Model Part 4: Management Framework (idtISO/IEC 7498-4:1989,eqvCCITT X.700:1992)GB/T16263-1996
Information Technology Open Systems Interconnection Abstract Syntax Notation One (ASN.1) Basic Encoding Rules Specification (idt ISO/IEC 8825:1990,eqvCCITT X.209:1988) Information Processing Systems Open Systems Interconnection File Transfer, Access and Management (idtISO/IECGB/T 16505—19963
8571:1989)
Information technology open systems interconnection common management information service definition (idtISO/IFC9595: GB/T 16644—1996
1991,eqv CCITT X.710:1991)
GB/T16645.1--1996 Information technology open systems interconnection common management information protocol Part 1: Specification (idtISO/
IEC 9596-1:1991,eqv CCITT X.711:1991)Approved by the State Administration of Technical Supervision on December 15, 1997436
Implemented on August 1, 1998
GB/T 17142—1997
GB/T16687--1996 Information Processing Systems Open Systems Interconnection Link Control Service Element Protocol Specification (idtISO/IEC8650:1988,eqv CCITT X. 227:1988) Information Processing Systems Open Systems Interconnection Link Control Service Element Service Definition (idt1SO8649:GB/T 16688---1996
1988,eqv CCITT X.217:1988)
Information Technology Remote Operation Part 2: OSI Implementation Remote Operation Service Element (ROSE)
GB/T 16975.21997
Service Definition (idtISO/IEC13712-2:1995) Information Technology Remote Operation Part 3: OSI Implementation Remote Operation Service Element (ROSE) GB/T 16975.3—1997
Protocol Specification (idtISO/IEC13712-3:1995)
System Management
GB/T 17143. 1-1997
IEC 10164-1:1993)
System Management
GB/T 17143.2-1997
Information Technology Open Systems Interconnection
IEC10164-2:1993)
GB/T 17143.3—1997
Information Technology Open Systems Interconnection
ISO/IEC 10164-3:1993)
Part 2: State management functions (idtISO/Part 3: Attributes of representation relations (idtSystem management
Information technology Open Systems Interconnection
GB/T 17143.4-19971
System management
IEC 10164-4:1992)
Information technology Open Systems Interconnection
GB/T 17143.5—1997
ISO/IEC 10164-5:1993)
GB/T 17143. 6--1997
Information technology Open Systems Interconnection
IEC10164-6:1993)
GB/T 17143.7—1997
Information technology Open Systems Interconnection
ISO/IEC 10164-7:1992)
System management
System management
System management
Part 4: Alarm reporting function (idtISO/Part 5: Event reporting management function (idtPart 6: Log control function (idtISO/Part 7: Security alarm reporting function (idtInformation technology Open Systems Interconnection Distributed Transaction Processing (idtISO/IEC10026:1992) GB/T 17173-1997
GB/T17175.1-1997 Information technology Open Systems Interconnection Management information structure Part 1: Management information model (idtISO/IEC 10165-1:1993)
GB/T 17175.2-1997
Information technology Open Systems Interconnection
E Management information structure Part 2: Management information definition (idtISO/IEC 10165-2:1992)
Information technology Open Systems Interconnection Management information structure Part 4: Definition of managed objects GB/T 17175. 4-19971
South (idtISO/IEC10165-4:1992)
Information technology Open Systems Interconnection Conformance test methods and framework Part 1: Basic concepts GB/T 17178. 1--1997
(idtISO/IEC9646-1:1991,eqvCCITTX.290:1992)3 Definition
3.1 Basic reference model definition
This standard is based on the concepts in the open systems interconnection basic reference model and uses the following terms defined in GB9387: a) application service element; b) systems management. 3.2 Management framework definition
This standard adopts the following terms defined in GB/T 9387.4: a) managed object;
b) management information base;
systems management application entity.3.3 CMISE definition
GB/T 17142 1997
This standard adopts the following terms defined in GB/T 16644: a) attribute (of managed object);
b) common management information service element;
c) common management information service. 3.4 Management information model definition
This standard adopts the following terms defined in GB/T 17175.1: a) attribute type;
b) naming tree;
c) managed object boundary. 3.5 OSI-Conformance Test Method and Framework Definitions This standard adopts the following terms defined in GB/T 17178.1: a) protocol implementation conformance statement (PICS); b) PICS proforma; c) system conformance statement; d) implementation conformance statement (ICS); e) ICS proforma. 3.6 System Management General Definitions
This standard adopts the following definitions:
3.6.1 Agent
A MIS user that acts as a proxy for a specific system management interaction. 3.6.2 Agent role
A role played by a MIS user that has the ability to perform management operations on managed objects and send notifications on behalf of managed objects. 3.6.3 Generic definitions Definitions of managed object classes, attribute types, notification types, or management operation types so that they can be used for general applications. 3.6.4 (Management) interaction A single management operation or a single notification, or an identified set of logically related management operations and notifications, in which the roles of manager and agent do not change.
3.6.5 managed object class A named collection of managed objects that share the same (named) set of attributes, notifications, and management operations (packages), and share the same conditions under which these packages exist.
NOTE 1: The following two definitions are closely related to the corresponding definitions of PICS and PICS proformas in ISO 17178.1 OSI Conformance Testing Method and Framework.
3.6.6 managed object conformance statement (MOCS) A statement generated by the provider of a managed object implementation: the capabilities and options that have been implemented, and any features that have been ignored. 3.6.7 Management Information - Conformance Statement (MICS) A statement made by the provider regarding the capabilities of the implemented manager role, the options associated with the implemented management information, and certain features that are ignored.
3.6.8 MICS proforma A document in the form of a questionnaire that, when completed by an implementation provider with manager role capabilities, becomes a MICS. 3.6.9 MOCS proforma A document in the form of a questionnaire that, when designed by the definer of a managed object or the designer of a conformance test suite, and completed by a managed object implementation, becomes a MOCS.
3.6.10 Managed (open) system
GB/T 17142—1997
An open real system that contains a MIS user that can act in a proxy role. 3.6.11 management domain a collection of managed objects to which a common system management policy applies. 3.6.12 management information information that can be transmitted by the OSI management protocol in an open system. 3.6.13 management support object a system managed object specifically defined to support system management functions (e.g., logs, identifiers). 3.6.14 manager manager
~ an MIS user who plays the role of a manager for a specific system management interaction. 3.6.15 manager role managerrole
a role played by a MIS user that has the ability to issue management operations and receive notifications. 3.6.16 managing (open) system an open real system that contains a MIS user who can play the role of a manager. 3.6.17 MIS user MIS-User
an application that uses system management services. 3.6.18 notification notification
Information sent by a managed object related to an event occurring within the managed object. 3.6.19 notification type notificationtype named data type that defines a specific kind of notification. 3.6.20 (N)-layer managed object (N)-layer managed object refers to a managed object at the (N) layer.
3.6.21 (N)-layer management protocol (N)-layer management protocol (N)-layer protocol used to exchange (N)-layer management information, supported only by (N-1) and below layers. NOTE 2 This standard neither specifies nor requires the use of the (N)-layer management protocol. Its definition is included here for completeness. 3.6.22 (systems management) operation (systems management) operation on a managed object that affects systems management. 3.6.23 systems managed object systems managed object refers to more than one layer of managed objects, but to the system as a whole or to a specified management function. 3.6.24 Systems management application process systems management application process Application processes involved in systems management.
3.6.25 systems management application service element systems management application service element application service element that provides systems management services. 3.6.26 systems management function systems management function a part of systems management activities that satisfies a set of logically related user requirements. 3.6.27 systems management functional area systems management functional area the scope of systems management user requirements.
3.6.28 systems management functional unit systems management functional unit a non-empty set of named systems management services defined for the purpose of identifying a specific set of such functionalities where the use of such functionalities is established or negotiated between end systems, or for reference in other standards. 3.6.29 systems management functional unit package systems management functional unit package a non-empty set of named systems management functional units defined for the purpose of negotiating functional units over an association. 3.6.30 systems management (application) protocol systems management (application) protocol application layer protocol that supports systems management services. 439
3.6.31 Systems management service
GB/T 17142—1997
systems management service
A named set of service primitives that provide services used in system management. 4 Abbreviations
B-ISDN
CMIPDU
5 System Management
Abstract Syntax Notation 1
Association Control Service Element
Application Service Element
Broadband Integrated Services Digital Network
Public Management Information Protocol
Public Management Information Protocol Data Unit
Public Management Information Service
Public Management Information Service Element
Circuit Switched Public Data Network
File Transfer, Access and Management
Implementation Conformance Statement
Identifier
Integrated Services Digital Network
Local Area Network
Management Application Protocol Data Unit
Message Handling System
Message Oriented Text Exchange System
Management Information Base
Management Information Conformance Statement||t t||Management Information Service
Managed Object Conformance Statement
Open Systems Interconnection
Protocol Implementation Conformance Statement
Packet Switching Public Data Network
Teleoperation Service Element
Single Contact Control Function
System Management Application Entity
System Management Application Protocol Machine
System Management Application Service Element
System Management Functional Scope
System Management Functional Unit
Management Information Structure
Telecommunication Management Network
Transaction Processing
Virtual Terminal
Wide Area Network
System Management provides mechanisms for monitoring, controlling, and coordinating resources in an OSI environment, and for communicating information associated with those resources. 440
GB/T17142—1997
OSI protocol standard. To describe management operations on resources in an OSI environment, these resources are considered as managed objects with specified characteristics. In any open system, the information required for system management can be provided by local input, or generated from input from other open systems through system management (application layer) communication, or can be the result of low-level protocol exchanges. In particular, system management applies to, but is not limited to: OSI layer 1 (dedicated/leased lines, satellite connections); OSI layer 2 (local area network, wide area network, etc.); OSI layer 3 (CSPDN, PSPDN, ISDN, B-ISDN, subnets of CCITT Recommendation X.300, etc.); - OSI layer 4 (transport layer entities),
OSI layer 5 (session layer entities);
- OSI layer 6 (presentation layer entities);
OSI layer 7 (MHSIMOTIS, FIAM, VT, TP, directory). (For example: the use of CCITT Recommendation M.30TMN is also considered a valid application of system management). NOTE: These standards were, of course, developed primarily to meet the need for managed OSI resources, but they also have broad applicability. Furthermore, it is possible that other areas may be specifically addressed in the standards in the future. Systems management can be applied to a wide range of distributed processing and communication environments. These environments range from local area networks interconnecting small systems to global scale interconnected cooperative and national networks. Small scale environments can be managed by appropriate small scale management systems consisting of a single manager that is able to control and coordinate the open communication environment through many agents. The standards and concepts are also applicable to large scale environments supporting multiple managers.
The entire set of systems management standards can be divided into the following three main groups: a) Group -→ is a set of standards that specify system management functions; b) a set of standards that are related to the specification of managed objects; c) a set of application layer service and protocol standards for information communication related to management functions. The needs met by system management activities can be conveniently divided into five groups, each of which gives one or more standards covering one or more functions. These scopes defined by the management framework (GB/T9387.4) are: - fault management;
configuration management;
accounting management,
- performance management;
security management.
However, it is known that many information items and their related management operations and communication protocols are common to multiple scopes. And in performing management activities, groups of management functions can be combined to complete specific management strategies. For this reason, system management standards constitute a closely related set of standards. 6 System Management Model
6.1 Introduction
This chapter identifies a number of system management concepts and provides a model to illustrate these concepts and their interrelationships. The following clauses describe various aspects of the system management model:--Information aspects;
Functional aspects:
OSI communication aspects;
Organizational aspects.
The management of the communication environment is an information processing application. Since the managed environment is distributed, the individual components of the management activities are themselves distributed. Management applications perform management activities in a distributed manner by establishing connections between system management application entities. 441
GB/T 17142-—1997
As shown in Figure 1, the interactions that occur between system management application entities are abstracted as management operations and notifications issued by one entity to another; they communicate using system management services and protocols. Managed open system
MIS user
(Manager role)
Management operation
MIS user
(Agent role)
Figure 1 System management interaction
Execute management operation
Issue notification
Managed object
Management activities are triggered by manipulating managed objects. For system management, management applications are classified according to MIS users. Each interaction occurs between two MIS users, one of whom plays the manager role and the other plays the agent role. The MIS user in the agent role is part of a distributed application that manages managed objects in its local system environment. Based on the management operations communicated by the manager, the agent performs management operations on the managed objects. The agent can also forward notifications issued by the managed objects to the manager.
The MIS user in the manager role is part of a distributed application that is responsible for one or more management activities by issuing management operations and receiving notifications.
The concept of management is not limited to applications that participate solely in system management; other applications that need access to management information may use the management information services.
The roles of MIS users are not permanently assigned. Some MIS users are restricted to acting only in the agent role, some in the manager role, and other MIS users are allowed to act in the agent role in one interaction and in the manager role in another interaction. NOTE
1 When a management interaction between open systems pertains to more than one managed object, the specification of how the agent distributes management operations among its managed objects is not part of the standard.
2 Managed objects may themselves represent resources external to a managed system. The relationship between a managed system and an external resource may also be a manager/agent relationship. If the communication between these systems follows the OSI management standard, management operations on managed objects in the original managed system may result in further manager/agent exchanges to operate on "remote" managed objects. There is no limit to the number of such layered management operations allowed. It is important to recognize that this International Standard establishes only a conceptual model that describes the structure and content of the information that is actually communicated using standardized management information services. Whenever management information is communicated, it is communicated according to this model. Where and how a system represents and stores the actual data that produces the management information is a local issue and is therefore not part of the standard.
NOTE 3: Figure 2 shows a particular way of viewing the system management model and is given for information only. The figure was of importance during the development of this specification. In particular, it distinguishes between local mappings to standardized communications (following the rules introduced in 6.2) and illustrates that there must be a way to view the actual management information according to the model in the system management application process. Furthermore, this method exists in the local environment and therefore implementation issues are not part of the standard.
Figure 2 does not show a complete model nor does it show all the details. In particular, it does not mean that a subtree of the naming tree must be associated with a specific layer, nor does it mean that the term "system management information model space" is a defined term. 442
6.2 Information aspects
GB/T 171421997
System management application process
Mapping to standardized communications
Data link
Managed objects
System managed objects
Local mapping
(N) layer managed objects
OSI environment
The level of human managed objects
System management information model space
Using standardized OST management communications
Local environment
Figure 2 Relationship between the information and communication aspects of the system management model This clause introduces the information aspects of the system management model. The definition of the information model is given in GB/T 17175.1. It refines the concept of managed objects defined in GB/T 9387.4. It involves their attributes, the management operations that may be performed on them, and the notifications that they may issue. The collection of managed objects in a system, together with their attributes, constitutes the Management Information Base (MIB) of that system. Managed objects that meet the standard are to be specified by the standards body responsible for standardizing the resources represented by the managed objects (e.g. the group responsible for standardizing (N) layer protocol entities is also responsible for standardizing managed objects that represent the management view of that protocol entity). Guidelines and tools to support the definition of managed objects are provided as a collection of management information definitions and system management function definitions that support the definition of managed objects.
6.2.1 Managed Objects
A managed object is an OSI management view of a resource (such as a layer entity, a connection, or an item of physical communication equipment) that is subject to management. A managed object is therefore an abstraction of such a resource that is viewed by management (and for management purposes) and represents its properties. An essential part of the definition of a managed object is the relationship between these properties and the operational behavior of the resource. Such relationships cannot be modeled in a general way. Managed objects can be specific to a single layer, in which case they are called (N) layer managed objects. Those managed objects that are related to multiple layers, to specific system management functions (management support objects) or to the entire system are called system managed objects. 6.2.2 Attributes
An attribute is a property of a managed object. An attribute has an associated value, which may have a simple or complex structure. 6.2.3 Management operations and notifications
Part of the definition of a managed object is the set of management operations that can be performed on it and the specification of the effects of these management operations on the managed object and its attributes. If there are related managed objects, the definition may also specify the effects on them. The execution of a management operation may also be conditionally dependent on the state of a managed object or its attributes. The essential part of the definition of a management operation is a set of possible methods in which it may fail.
Managed objects may also send notifications, which contain information about the occurrence of an event that is associated with the managed object. The mechanism for transmitting management operations and notifications belongs to the OSI management standardization content, while the mechanism for executing management operations and notifications does not belong to the 443
GB/T17142-1997
(OSI management standardization content. The corresponding internal system interface does not belong to the standardization content. The relationship between the various management operations on the boundaries of the managed objects and what is transmitted in the protocols between the open systems will be described in 6.4. 6.3 Functional aspects
This clause describes the functional aspects of the system management model. A system management function may meet multiple requirements; or multiple functions may be used to meet some requirements. Therefore, there is a gap between functions and requirements. There is a many-to-many relationship.
The system management function specification defines the necessary management activities and information to meet the requirements. Management functions can be combined to accomplish specific management activities. Since not all services are always required for a given relationship, the services of the system management function may be grouped into one or more functional units, which are the basic units negotiated between MIS users. In addition, functional units that can provide multiple functional services can be defined.
Functional units that cross functional boundaries are provided to support the following set of capabilities: a) notification only;
b) management operations only;
c) notification and management operations.
Note: Negotiation of subsets of these capabilities (e.g., monitoring, control) is allowed to define other functional units. An agent cannot generally determine the purpose of the management operation it receives or the notification it sends. For example, an open system cannot generally determine whether its response to a request to read error counters will be used for fault management purposes or performance management purposes. The agent responds to requests from managers alone without requiring any broader context to execute the request. 6.4 OS1 Communication Aspects
Interaction between MIS users in the manager and agent roles is accomplished by exchanging management information. This communication is accomplished using OSI protocols.
The general OSI communication service for system management is CMIS. 6.4.1 describes how CMIS is used to support communications related to management operations and notifications applicable to managed objects in a managed system. 6.4.2 to 6.4.5 explain how the communication support fits into the application layer architecture.
MIS users may make use of other OSI services (such as TP or FTAM) that may or may not support the manager/agent role distinction; however, MIS users should still support the manager/agent role distinction. NOTE: MIS users may make use of other services. 6.4.1 Support for Management Operations and Notifications
Communication support for management operations and notifications has two aspects: a) support for the transmission of requests for management operations and notifications between MIS users; and b) support for access control to managed objects and external propagation of notification information. The main components are shown in Figure 3.
System management services have primitives for communicating requests for various types of management operations defined in ISO/IEC 17175.1, as well as primitives for transmitting notification information. In this way, system management services reflect the exchanges defined on the boundaries of managed objects. System management services provide additional support for selecting appropriate managed objects with screening and filtering. ISO/IEC 17143.1 defines how system management services are mapped to CMIS services. There is a strict correspondence between the types of exchanges defined on the boundaries of managed objects (in information models) and the communication support in system management services; however, in individual exchanges (or possible exchanges) of information, these mechanisms can participate in controlling the flow of information. Access control mechanisms may deny management operation requests for selected managed objects by specified managers. For external communications of management notifications issued by managed objects, a mechanism is defined to identify the destination of external communications and the matching principles that notification information should meet. Another mechanism can also be defined independently to record information for later retrieval. 144
GB/T17142-1997
(OSI management standardization content. The corresponding internal system interface is not part of the standardization content. The relationship between the management operations on the boundaries of the managed objects and what is transmitted in the protocols between the open systems will be described in 6.4. 6.3 Functional aspects
This clause describes the functional aspects of the system management model. A system management function may meet multiple requirements; or multiple functions may be used to meet certain requirements. Therefore, there is a many-to-many relationship between functions and requirements.
To meet the requirements , the system management function specification defines the required management activities and information. Management functions may be combined to accomplish specific management activities. Since not all services are always required for a given relationship, the services of the system management functions may be grouped into one or more functional units, which are the basic units negotiated between MIS users. In addition, functional units that can provide services of multiple functions may be defined.
Functional units that cross functional boundaries are provided to support the following set of capabilities: a) notification only;
b) management operations only;
c) notification and management operations.
Note: Negotiation of subsets of these capabilities (e.g., monitoring, control) is allowed to define other functional units. An agent cannot generally determine the purpose of the management operations it receives or the notifications it sends. For example, an open system cannot generally determine whether its response to a request to read error counters will be used for fault management purposes or performance management purposes. An agent responds to requests from managers alone without requiring any broader context to execute the request. 6.4 OS1 Communication Aspects
Interaction between MIS users in the manager and agent roles is accomplished by exchanging management information. This communication is accomplished using OSI protocols.
The generic OSI communication service for system management is CMIS. 6.4.1 describes how CMIS is used to support communications related to management operations and notifications applicable to managed objects in a managed system. 6.4.2 to 6.4.5 explain how the communication support fits into the application layer architecture.
MIS users may make use of other OSI services (such as TP or FTAM) that may or may not support the manager/agent role distinction, however, MIS users should still support the manager/agent role distinction. NOTE: MIS users may make use of other services. 6.4.1 Support for Management Operations and Notifications
Communication support for management operations and notifications has two aspects: a) Support for the transmission of requests for management operations and notifications between MIS users; and b) Support for access control to managed objects and external propagation of notification information. The main components are shown in Figure 3.
System management services have primitives for communicating requests for various types of management operations defined in GB/T 17175.1, as well as primitives for transmitting notification information. In this way, system management services reflect the exchanges defined on the boundaries of managed objects. System management services provide additional support for selecting appropriate managed objects with screening and filtering. GB/T 17143.1 defines how system management services are mapped to CMIS services. There is a strict correspondence between the types of exchanges defined on the boundaries of managed objects (in information models) and the communication support in system management services; however, in individual exchanges (or possible exchanges) of information, these mechanisms can participate in controlling the flow of information. Access control mechanisms may deny management operation requests for selected managed objects by specified managers. For external communications of management notifications issued by managed objects, a mechanism is defined to identify the destination of external communications and the matching principles that notification information should meet. Another mechanism can also be defined independently to record information for later retrieval. 1443 Functional Aspects
This clause describes the functional aspects of the system management model. A system management function may satisfy multiple requirements; or multiple functions may be used to satisfy some requirements. Therefore, there is a many-to-many relationship between functions and requirements.
The system management function specification defines the management activities and information required to satisfy the requirements. Management functions may be combined to accomplish specific management activities. Since not all services are always required for a given relationship, the services of the system management function may be grouped into one or more functional units, which are the basic units negotiated between MIS users. In addition, functional units that provide services of multiple functions may be defined.
Functional units that cross functional boundaries are provided to support the following set of capabilities: a) notification only;
b) management operations only; www.bzxz.net
c) notification and management operations.
Note: Negotiation of subsets of these capabilities (e.g., monitoring, control) is allowed to define other functional units. An agent cannot generally determine the purpose of the management operations it receives or the notifications it sends. For example, an open system cannot generally determine whether its response to a request to read error counters will be used for fault management purposes or for performance management purposes. An agent responds to requests from a manager independently without any need for any broader context to execute the request. 6.4 OS1 Communication Aspects
Interaction between MIS users in the manager and agent roles is accomplished by exchanging management information. This communication is accomplished using OSI protocols.
The generic OSI communication service for system management is CMIS. 6.4.1 describes how CMIS is used to support communications related to management operations and notifications applicable to managed objects in a managed system. 6.4.2 to 6.4.5 explain how the communication support fits into the application layer architecture.
MIS users may make use of other OSI services (such as TP or FTAM) that may or may not support the manager/agent role distinction, but the MIS user should still support the manager/agent role distinction. NOTE: MIS users may make use of other services. 6.4.1 Support for Management Operations and Notifications
Communication support for management operations and notifications has two aspects: a) Support for the transmission of requests for management operations and notifications between MIS users; b) Support for access control of managed objects and external dissemination of notification information. The main components are shown in Figure 3.
System management services have primitives for communicating requests for various types of management operations defined in ISO 17175.1, as well as primitives for transmitting notification information. In this way, system management services reflect the exchanges defined on the boundaries of managed objects. System management services provide additional support for selecting appropriate managed objects using screening and filtering. ISO 17143.1 defines how system management services are mapped to CMIS services. There is a strict correspondence between the types of exchanges defined on the boundaries of managed objects (in information models) and the communication support in system management services; however, in individual exchanges (or possible exchanges) of information, these mechanisms can participate in controlling the flow of information. Access control mechanisms may deny management operation requests for selected managed objects by specified managers. For external communications of management notifications from managed objects, a mechanism is defined to identify the destination of external communications and the matching criteria that the notification information should satisfy. Another mechanism may also be defined independently to record the information for later retrieval. 1443 Functional Aspects
This clause describes the functional aspects of the system management model. A system management function may satisfy multiple requirements; or multiple functions may be used to satisfy some requirements. Therefore, there is a many-to-many relationship between functions and requirements.
The system management function specification defines the management activities and information required to satisfy the requirements. Management functions may be combined to accomplish specific management activities. Since not all services are always required for a given relationship, the services of the system management function may be grouped into one or more functional units, which are the basic units negotiated between MIS users. In addition, functional units that provide services of multiple functions may be defined.
Functional units that cross functional boundaries are provided to support the following set of capabilities: a) notification only;
b) management operations only;
c) notification and management operations.
Note: Negotiation of subsets of these capabilities (e.g., monitoring, control) is allowed to define other functional units. An agent cannot generally determine the purpose of the management operations it receives or the notifications it sends. For example, an open system cannot generally determine whether its response to a request to read error counters will be used for fault management purposes or for performance management purposes. An agent responds to requests from a manager independently without any need for any broader context to execute the request. 6.4 OS1 Communication Aspects
Interaction between MIS users in the manager and agent roles is accomplished by exchanging management information. This communication is accomplished using OSI protocols.
The generic OSI communication service for system management is CMIS. 6.4.1 describes how CMIS is used to support communications related to management operations and notifications applicable to managed objects in a managed system. 6.4.2 to 6.4.5 explain how the communication support fits into the application layer architecture.
MIS users may make use of other OSI services (such as TP or FTAM) that may or may not support the manager/agent role distinction, but the MIS user should still support the manager/agent role distinction. NOTE: MIS users may make use of other services. 6.4.1 Support for Management Operations and Notifications
Communication support for management operations and notifications has two aspects: a) Support for the transmission of requests for management operations and notifications between MIS users; b) Support for access control of managed objects and external dissemination of notification information. The main components are shown in Figure 3.
System management services have primitives for communicating requests for various types of management operations defined in ISO 17175.1, as well as primitives for transmitting notification information. In this way, system management services reflect the exchanges defined on the boundaries of managed objects. System management services provide additional support for selecting appropriate managed objects using screening and filtering. ISO 17143.1 defines how system management services are mapped to CMIS services. There is a strict correspondence between the types of exchanges defined on the boundaries of managed objects (in information models) and the communication support in system management services; however, in individual exchanges (or possible exchanges) of information, these mechanisms can participate in controlling the flow of information. Access control mechanisms may deny management operation requests for selected managed objects by specified managers. For external communications of management notifications from managed objects, a mechanism is defined to identify the destination of external communications and the matching criteria that the notification information should satisfy. Another mechanism may also be defined independently to record the information for later retrieval. 144
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.