ISO/IEC 10040:1998

Information technology — Open Systems Interconnection — Systems management overview

This Recommendation | International Standard: provides an overview to the family of systems management standards; establishes the basis for partitioning the systems management standards into separate groups, specifying the scope of each group and identifying the principal components within each group; gives guidance on the development of systems management standards and identifies the way they relate to each other; defines terms for use by other systems management standards; is applicable to the definition of all systems management standards and to all aspects of systems management of whatever scale; is applicable to situations in which the responsibility for systems management is centralized and those where it is decentralized; establishes a model for systems management, identifies several aspects of systems management (i.e. information, functional, communications, and organizational), and further refines the model to clarify these aspects; identifies the principles governing conformance requirements and conformance claims to systems management standards. There are no conformance requirements on the main body of this Recommendation | International Standard, however it does specify requirements on standards claiming compliance to systems management. Annex A defines an application context for systems management and specifies the rules for negotiating systems management functional units. There are conformance requirements associated with these rules.

Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Aperçu général de la gestion-systèmes

La presente Recommandation | Norme intemationale offre un apercu general de la famille des normes de gestion-systemes; etablit les bases permettant de subdiviser les normes de gestion-systemes en groupes distincts, precise le domaine d'application de chaque groupe et definit les principales composantes a l'interieur de chaque groupe; foumit des directives pour l'elaboration de normes de gestion-systemes et identifie les liens entre ces normes; définit les termes utilises dans d'autres normes de gestion-systemes; s'applique a la definition de toutes les normes de gestion-systemes et a tous les aspects de la gestionsystemes, quelle que soit leur importance; s'applique aux cas ou la responsabilite de la gestion-systemes est centralisee ou distribuee; definit un modele de gestion-systemes, precise plusieurs aspects (informationnel, fonctionnel, de communication et d'organisation) de la gestion-systemes et affine ledit mod&e pour preciser ces differents aspects; recense les principes regissant les imperatifs de conformite et les declarations de conformite par rapport aux normes de gestion-systemes. Il n'existe aucun imperatif de conformite aux dispositions du corps principal de la presente Recommandation 1 Norme intemationale; cette demiere precise toutefois les exigences auxquelles doivent repondre les normes qui se veulent conformes a la gestion-systemes. L'Annexe A definit un contexte d'application pour la gestion-systemes et specific les regles fonctionnelles de gestion-systemes. Des exigences de c onformite sont associees a ces regles.

General Information

• Status: Published
• Publication Date: 14-Oct-1998
• ICS: 35.100.70 - Application layer
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9093 - International Standard confirmed
• Start Date: 31-Mar-2009
• Completion Date: 12-Feb-2026

Relations

• Revises: ISO/IEC 10040:1992/Cor 2:1996 - Information technology — Open Systems Interconnection — Systems management overview — Technical Corrigendum 2
• Effective Date: 15-Apr-2008
• Revises: ISO/IEC 10040:1992/Cor 1:1994 - Information technology — Open Systems Interconnection — Systems management overview — Technical Corrigendum 1
• Effective Date: 15-Apr-2008
• Revises: ISO/IEC 10040:1992/Amd 1:1995 - Information technology — Open Systems Interconnection — Systems management overview — Amendment 1: Management knowledge management
• Effective Date: 15-Apr-2008
• Revises: ISO/IEC 10040:1992 - Information technology — Open Systems Interconnection — Systems management overview
• Effective Date: 15-Apr-2008

Overview

ISO/IEC 10040:1998 - Information technology - Open Systems Interconnection - Systems management overview (ITU‑T X.701) provides a high‑level framework and vocabulary for the OSI family of systems management standards. It summarizes the scope and organization of systems management standards, establishes a partitioning into logical groups, defines key terms, and presents a model that clarifies the major aspects of systems management: information, functional, communications, and organizational. The standard guides the development and interrelation of other systems management standards and sets the principles for conformance claims.

Key Topics

• Systems management model - conceptual model separating information, functional, communications and organizational aspects to guide standard development and interoperability.
• Partitioning of standards - basis for grouping standards and identifying principal components within each group.
• Definitions and terminology - common terms for use across the systems management family to ensure consistency.
• Structure and architecture - guidance on architecture, structure of management information, and communication of management information.
• Systems management functions - identification of typical management functions (e.g., object/state management, alarm reporting, event reporting, logging, diagnostics, security audit and access control).
• Conformance and compliance principles - rules governing how other standards may claim compliance; the main body imposes no direct conformance requirements but specifies requirements for standards that claim compliance. Annex A defines an application context and rules for negotiating management functional units and contains associated conformance requirements.
• Normative relationships - references to related OSI standards and protocols (for example ASN.1, CMIS/CMIP, SMI, and conformance testing frameworks).

Applications

ISO/IEC 10040:1998 is relevant to:

• Standard developers creating or updating systems management specifications within the OSI family.
• Vendors designing network and systems management products (management agents, consoles, CMIP implementations).
• Systems integrators and architects defining management architectures for large, distributed or mixed centralized/decentralized environments.
• Test and conformance laboratories assessing claims of compliance to OSI systems management standards.
• IT managers and procurement teams evaluating interoperability and management capabilities across multi‑vendor systems.

Adopting ISO/IEC 10040 helps ensure consistent terminology, modular structuring of management standards, and clearer interoperability and conformance claims across OSI systems management implementations.

Related standards

Notable related documents referenced in ISO/IEC 10040:1998 include ITU‑T X.200 / ISO/IEC 7498‑1 (OSI Basic Reference Model), ASN.1 specifications (ISO/IEC 8824 series), CMIS/CMIP (ISO/IEC 9595 / 9596), SMI/SMI modules (ISO/IEC 10165 series), and conformance testing frameworks (ISO/IEC 9646). These define the technical building blocks that implement the overview provided by ISO/IEC 10040.

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 10040
Second edition
1998-10-15
Information technology — Open Systems
Interconnection — Systems management
overview
Technologies de l'information — Interconnexion de systèmes ouverts
(OSI) — Aperçu général de la gestion-système
Reference number
B C
Contents
Page
1 Scope . 1
2 Normative references. 1
2.1 Identical ITU-T Recommendations | International Standards. 1
2.2 Paired Recommendations | International Standards equivalent in technical content . 3
2.3 Additional references. 4
3 Definitions . 4
3.1 Basic reference model definitions . 4
3.2 Management framework definitions . 4
3.3 CMISE definitions. 4
3.4 Management information model definitions. 4
3.5 OSI conformance testing methodology and framework definitions. 5
3.6 Systems management overview definitions . 5
4 Abbreviations. 6
5 Systems management. 7
6 Systems management model . 8
6.1 Introduction . 8
6.2 Information aspects . 9
6.3 Functional aspects . 11
6.4 OSI communications aspects. 11
6.5 Organizational aspects. 15
7 Systems management standards . 16
7.1 Architecture and structure . 17
7.2 Communication of management information. 17
7.3 Structure of management information . 17
7.4 Systems management functions . 18
8 Conformance and compliance. 19
8.1 Compliance to this Recommendation | International Standard . 19
8.2 Conformance to this Recommendation | International Standard. 21
Annex A – Application context for systems management. 22
A.1 Background . 22
A.2 Systems management application context . 22
A.3 Rules for establishing associations . 23
A.4 Conformance . 25
Annex B – Scope statement for systems management functions. 26
B.1 The rules. 26
B.2 The boilerplate. 26
©  ISO/IEC 1998
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or
utilized in any form or by any means, electronic or mechanical, including photocopying and micro-
film, without permission in writing from the publisher.
ISO/IEC Copyright Office • Case postale 56 • CH-1211 Genève 20 • Switzerland
Printed in Switzerland
ii
©
ISO/IEC ISO/IEC 10040:1998(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the
specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the
development of International Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work.
In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. Draft
International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the national bodies casting a vote.
International Standard ISO/IEC 10040 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 33, Distributed application services, in collaboration with ITU-T. The identical text is published as ITU-T
Recommendation X.701.
This second edition cancels and replaces the first edition (ISO/IEC 10040:1992), which has been technically revised. It also
incorporates Amendment 1:1995, Technical Corrigendum 1:1994 and Technical Corrigendum 2:1996.
Annex A forms an integral part of this International Standard. Annex B is for information only.
iii
ISO/IEC 10040 : 1998 (E)
INTERNATIONAL STANDARD
ISO/IEC 10040 : 1998 (E)
ITU-T Rec. X.701 (1997 E)
ITU-T RECOMMENDATION
INFORMATION TECHNOLOGY – OPEN SYSTEMS INTERCONNECTION –
SYSTEMS MANAGEMENT OVERVIEW
1 Scope
This Recommendation | International Standard:
– provides an overview to the family of systems management standards;
– establishes the basis for partitioning the systems management standards into separate groups, specifying
the scope of each group and identifying the principal components within each group;
– gives guidance on the development of systems management standards and identifies the way they relate to
each other;
– defines terms for use by other systems management standards;
– is applicable to the definition of all systems management standards and to all aspects of systems
management of whatever scale;
– is applicable to situations in which the responsibility for systems management is centralized and those
where it is decentralized;
– establishes a model for systems management, identifies several aspects of systems management
(i.e. information, functional, communications, and organizational), and further refines the model to clarify
these aspects;
– identifies the principles governing conformance requirements and conformance claims to systems
management standards.
There are no conformance requirements on the main body of this Recommendation | International Standard, however it
does specify requirements on standards claiming compliance to systems management.
Annex A defines an application context for systems management and specifies the rules for negotiating systems
management functional units. There are conformance requirements associated with these rules.
2 Normative references
The following Recommendations and International Standards contain provisions which, through reference in this text,
constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated
were valid. All Recommendations and Standards are subject to revision, and parties to agreement based on this
Recommendation | International Standard are encouraged to investigate the possibility of applying the most recent edition
of the Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently valid
International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently valid
ITU-T Recommendations.
2.1 Identical ITU-T Recommendations | International Standards
– ITU-T Recommendation X.200 (1994) | ISO/IEC 7498-1:1994, Information technology – Open Systems
Interconnection – Basic Reference Model: The Basic Model.
– ITU-T Recommendation X.207 (1993) | ISO/IEC 9545:1994, Information technology – Open Systems
Interconnection – Application layer structure.
– ITU-T Recommendation X.217 (1995) | ISO/IEC 8649:1996, Information technology – Open Systems
Interconnection – Service definition for the association control service element.
– ITU-T Recommendation X.227 (1995) | ISO/IEC 8650-1:1996, Information technology – Open Systems
Interconnection – Connection-oriented protocol for the association control service element: Protocol
specification.
ITU-T Rec. X.701 (1997 E) 1
ISO/IEC 10040 : 1998 (E)
– ITU-T Recommendation X.680 (1994) | ISO/IEC 8824-1:1995, Information technology – Abstract Syntax
Notation One (ASN.1): Specification of basic notation.
– ITU-T Recommendation X.681 (1994) | ISO/IEC 8824-2:1995, Information technology – Abstract Syntax
Notation One (ASN.1): Information object specification.
– ITU-T Recommendation X.682 (1994) | ISO/IEC 8824-3:1995, Information technology – Abstract Syntax
Notation One (ASN.1): Constraint specification.
– ITU-T Recommendation X.683 (1994) | ISO/IEC 8824-4:1995, Information technology – Abstract Syntax
Notation One (ASN.1): Parameterization of ASN.1 specifications.
– ITU-T Recommendation X.690 (1994) | ISO/IEC 8825-1:1995, Information technology – ASN.1 encoding
rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished
Encoding Rules (DER).
– ITU-T Recommendation X.691 (1995) | ISO/IEC 8825-2:1995, Information technology – ASN.1 encoding
rules: Specification of Packed Encoding Rules (PER).
– ITU-T Recommendation X.702 (1995) | ISO/IEC 11587:1996, Information technology – Open Systems
Interconnection – Application context for systems management with transaction processing.
– CCITT Recommendation X.712 (1992) | ISO/IEC 9596-2:1993, Information technology – Open Systems
Interconnection – Common management information protocol: Protocol Implementation Conformance
Statement (PICS) proforma plus Technical Corrigenda 1 and 2 (1996).
– CCITT Recommendation X.720 (1992) | ISO/IEC 10165-1:1993, Information technology – Open Systems
Interconnection – Structure of management information: Management information model.
– CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, Information technology – Open Systems
Interconnection – Structure of management information: Definition of management information.
– CCITT Recommendation X.722 (1992) | ISO/IEC 10165-4:1992, Information technology – Open Systems
Interconnection – Structure of management information: Guidelines for the definition of managed objects.
– ITU-T Recommendation X.723 (1993) | ISO/IEC 10165-5:1994, Information technology – Open Systems
Interconnection – Structure of management information: Generic management information.
– ITU-T Recommendation X.724 (1993) | ISO/IEC 10165-6:1994, Information technology – Open Systems
Interconnection – Structure of management information: Requirements and guidelines for implementation
conformance statement proformas associated with OSI management.
– ITU-T Recommendation X.725 (1995) | ISO/IEC 10165-7:1996, Information technology – Open Systems
Interconnection – Structure of management information: General relationship model.
– CCITT Recommendation X.730 (1992) | ISO/IEC 10164-1:1993, Information technology – Open Systems
Interconnection – Systems Management: Object management function.
– CCITT Recommendation X.731 (1992) | ISO/IEC 10164-2:1992, Information technology – Open Systems
Interconnection – Systems Management: State management function.
– CCITT Recommendation X.732 (1992) | ISO/IEC 10164-3:1993, Information technology – Open Systems
Interconnection – Systems Management: Attributes for representing relationships.
– CCITT Recommendation X.733 (1992) | ISO/IEC 10164-4:1992, Information technology – Open Systems
Interconnection – Systems Management: Alarm reporting function.
– CCITT Recommendation X.734 (1992) | ISO/IEC 10164-5:1993, Information technology – Open Systems
Interconnection – Systems Management: Event report management function.
– CCITT Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, Information technology – Open Systems
Interconnection – Systems Management: Log control function.
– CCITT Recommendation X.736 (1992) | ISO/IEC 10164-7:1992, Information technology – Open Systems
Interconnection – Systems Management: Security alarm reporting function.
– ITU-T Recommendation X.737 (1995) | ISO/IEC 10164-14:1996, Information technology – Open Systems
Interconnection – Systems Management: Confidence and diagnostic test categories.
– ITU-T Recommendation X.738 (1993) | ISO/IEC 10164-13:1995, Information technology – Open Systems
Interconnection – Systems Management: Summarization function.
– ITU-T Recommendation X.739 (1993) | ISO/IEC 10164-11:1994, Information technology – Open Systems
Interconnection – Systems Management: Metric objects and attributes.
2 ITU-T Rec. X.701 (1997 E)
ISO/IEC 10040 : 1998 (E)
– CCITT Recommendation X.740 (1992) | ISO/IEC 10164-8:1993, Information technology – Open Systems
Interconnection – Systems Management: Security audit trail functions.
– ITU-T Recommendation X.741 (1995) | ISO/IEC 10164-9:1995, Information technology – Open Systems
Interconnection – Systems Management: Objects and attributes for access control.
– ITU-T Recommendation X.742 (1995) | ISO/IEC 10164-10:1995, Information technology – Open Systems
Interconnection – Systems Management: Usage metering function for accounting purposes.
– ITU-T Recommendation X.745 (1993) | ISO/IEC 10164-12:1994, Information technology – Open Systems
Interconnection – Systems Management: Test management function.
– ITU-T Recommendation X.746 (1995) | ISO/IEC 10164-15:1995, Information technology – Open Systems
Interconnection – Systems Management: Scheduling function.
– ITU-T Recommendation X.751 (1995) | ISO/IEC 10164-17:1996, Information technology – Open Systems
Interconnection – Systems Management: Change over function.
2.2 Paired Recommendations | International Standards equivalent in technical content
– CCITT Recommendation X.208 (1988), Specification of Abstract Syntax Notation 1 (ASN.1).
ISO/IEC 8824:1990, Information technology – Open Systems Interconnection – Specification of Abstract
Syntax Notation One (ASN.1).
– CCITT Recommendation X.209 (1988), Specification of basic encoding rules for Abstract Syntax
Notation One (ASN.1).
ISO/IEC 8825:1990, Information technology – Open Systems Interconnection – Specification of Basic
Encoding Rules for Abstract Syntax Notation One (ASN.1).
– CCITT Recommendation X.219 (1988), Remote operations: Model, notation and service definition.
ISO/IEC 9072-1:1989, Information processing systems – Text communication – Remote Operations –
Part 1: Model, notation and service definition.
– CCITT Recommendation X.229 (1988), Remote operations: Protocol specification.
ISO/IEC 9072-2:1989 Information processing systems – Text communication – Remote Operations –
Part 2: Protocol specification.
– ITU-T Recommendation X.290 (1995), OSI conformance testing methodology and framework for
protocol Recommendations for ITU-T applications – General concepts.
ISO/IEC 9646-1:1994, Information technology – Open Systems Interconnection – Conformance testing
methodology and framework – Part 1: General concepts.
– ITU-T Recommendation X.296 (1995), OSI conformance testing methodology and framework for
protocol Recommendations for ITU-T applications – Implementation conformance statements.
ISO/IEC 9646-7:1995, Information technology – Open Systems Interconnection – Conformance testing
methodology and framework – Part 7: Implementation Conformance Statements.
– CCITT Recommendation X.700 (1992), Management framework for Open Systems Interconnection (OSI)
for CCITT applications.
ISO/IEC 7498-4:1989, Information processing systems – Open Systems Interconnection – Basic
Reference Model – Part 4: Management framework.
– CCITT Recommendation X.710 (1991), Common management information service definition for CCITT
applications.
ISO/IEC 9595:1991, Information technology – Open Systems Interconnection – Common management
information service definition.
– CCITT Recommendation X.711 (1991), Common management information protocol specification for
CCITT applications.
ISO/IEC 9596-1:1991, Information technology – Open Systems Interconnection – Common management
information protocol – Part 1: Specification.
– CCITT Recommendation X.860 (1992), Open Systems Interconnection – Distributed transaction
processing – Model.
ISO/IEC 10026-1:1992, Information technology – Open Systems Interconnection – Distributed
Transaction Processing – Part 1: OSI TP Model.
ITU-T Rec. X.701 (1997 E) 3
ISO/IEC 10040 : 1998 (E)
– CCITT Recommendation X.861 (1992), Open Systems Interconnection – Distributed transaction
processing: Service definition.
ISO/IEC 10026-2:1992, Information technology – Open Systems Interconnection – Distributed
Transaction Processing – Part 2: OSI TP Service.
– CCITT Recommendation X.862 (1993), Open Systems Interconnection – Distributed transaction
processing: Protocol specification.
ISO/IEC 10026-3:1992, Information technology – Open Systems Interconnection – Distributed
Transaction Processing – Part 3: Protocol specification.
2.3 Additional references
– ISO 8571:1988, Information processing systems – Open Systems Interconnection – File Transfer, Access
and Management.
– ISO/IEC 9545:1994, Information technology – Open Systems Interconnection – Application Layer
structure.
3 Definitions
3.1 Basic reference model definitions
This Recommendation | International Standard is based on the concepts in the Basic Reference Model for Open Systems
Interconnection and makes use of the following terms defined in ITU-T Rec. X.200 | ISO/IEC 7498-1:
a) application service element;
b) systems management.
3.2 Management framework definitions
This Recommendation | International Standard makes use of the following terms defined in CCITT Rec. X.700 | ISO/IEC
7498-4:
a) managed object;
b) management information base;
c) systems management application entity.
3.3 CMISE definitions
This Recommendation | International Standard makes use of the following terms defined in CCITT Rec. X.710 | ISO/IEC
9595:
a) attribute (of managed object);
b) common management information service element;
c) common management information services.
3.4 Management information model definitions
This Recommendation | International Standard makes use of the following terms defined in CCITT Rec. X.720 | ISO/IEC
10165-1:
a) attribute type;
b) naming tree;
c) managed object boundary.
This Recommendation | International Standard makes use of the following term defined in ITU-T Rec X.725 |
ISO/IEC 10165-7:
d) managed relationship.
4 ITU-T Rec. X.701 (1997 E)
ISO/IEC 10040 : 1998 (E)
3.5 OSI conformance testing methodology and framework definitions
This Recommendation | International Standard makes use of the following terms defined in ITU-T Rec. X.290 |
ISO/IEC 9646-1 and ITU-T Rec. X.296 | ISO/IEC 9646-7:
a) Protocol Implementation Conformance Statement (PICS);
a) PICS proforma;
b) system conformance statement;
c) implementation conformance statement (ICS);
d) ICS proforma.
3.6 Systems management overview definitions
For the purposes of this Recommendation | International Standard, the following definitions apply.
3.6.1 agent: An MIS-User, which for a particular systems management interaction, has taken an agent role.
3.6.2 agent role: A role taken by an MIS-User in which it is capable of performing management operations on
managed objects and of emitting notifications on behalf of managed objects.
3.6.3 generic definitions: Definitions of managed object classes, attribute types, notification types or management
operation types, made available for general use.
3.6.4 (management) interaction: A single management operation or a single notification or an identified set of
logically related management operations and notifications during which the manager and agent role do not change.
3.6.5 managed object class: A named set of managed objects sharing the same (named) sets of attributes,
notifications, management operations (packages), and which share the same conditions for presence of those packages.
NOTE – The following two definitions are aligned with the corresponding definitions in OSI Conformance Testing Methodology
and Framework ITU-T Rec. X.290 | ISO/IEC 9646-1 for PICS and PICS proforma.
3.6.6 managed object conformance statement (MOCS): A statement made by a supplier of a managed object
implementation, stating the capabilities and options which have been implemented, and any features which have been
omitted.
3.6.7 management information conformance statement (MICS): A statement from a supplier about an
implementation's manager role capabilities and options relating to management information which have been
implemented and any features which have been omitted.
3.6.8 MICS proforma: A document, in the form of a questionnaire, which when completed by the supplier of an
implementation having manager role capability becomes a MICS.
3.6.9 MOCS proforma: A document, in the form of a questionnaire, designed by the managed object definer or
conformance test suite specifier, which when completed for a managed object implementation becomes the MOCS.
3.6.10 managed (open) system: A real open system containing an MIS-User which can take the agent role.
3.6.11 management domain: A specification of a collection of managed objects of interest.
3.6.12 management information: The information within an open system which may be transferred by OSI
management protocols.
3.6.13 management jurisdiction: A representation of the relationship between a management policy and a
management domain.
3.6.14 management policy: An identifiable specification that can be evaluated with respect to managed objects.
3.6.15 management policy violation: The condition existing when managed objects fail to comply with the semantics
of a policy.
3.6.16 management support object: A systems managed object defined specifically to support a systems
management function (e.g. log, discriminator).
3.6.17 manager: An MIS-User, which for a particular systems management interaction, has taken a manager role.
3.6.18 manager role: A role taken by an MIS-User in which it is capable of issuing management operations and of
receiving notifications.
3.6.19 managing (open) system: A real open system containing an MIS-User which can take the manager role.
ITU-T Rec. X.701 (1997 E) 5
ISO/IEC 10040 : 1998 (E)
3.6.20 MIS-User: An application making use of systems management services.
3.6.21 notification: Information emitted by a managed object relating to an event that has occurred within the
managed object.
3.6.22 notification type: A named data-type defining a specific kind of notification.
3.6.23 (N)-layer managed object: A managed object specific to the (N)-layer.
3.6.24 (N)-layer management protocol: An (N)-layer protocol for the exchange of (N)-layer management
information supported solely by protocols of the layers (N-1) and below.
NOTE – This Recommendation | International Standard neither specifies nor requires the use of (N)-layer management protocols.
The definition is included here for the sake of completeness.
3.6.25 (systems management) operation: An operation on a managed object to effect systems management.
3.6.26 systems managed object: A managed object relevant to more than one layer, to the system as a whole, or to
specific management functions.
3.6.27 systems management application process: An application process participating in systems management.
3.6.28 systems management application service element: An application service element providing systems
management services.
3.6.29 systems management function: A part of systems management activities which satisfy a set of logically related
user requirements.
3.6.30 systems management functional area: A category of systems management user requirements.
3.6.31 systems management functional unit: A named non-empty set of systems management services defined for
the purpose of identifying specific sets of functionality where there is a requirement to establish or negotiate the use of
such functionality between end systems or for reference purposes in other standards.
3.6.32 systems management functional unit package: A named non-empty set of systems management functional
units, defined for the purposes of negotiation of functional units on an association.
3.6.33 systems management (application) protocol: An application layer protocol supporting systems management
services.
3.6.34 systems management service: A named set of service primitives that provide a service for use in systems
management.
4 Abbreviations
For the purposes of this Recommendation | International Standard, the following abbreviations apply:
ACSE Association Control Service Element
ASE Application Service Element
ASN.1 Abstract Syntax Notation One
B-ISDN Broadband Integrated Services Digital Network
CMIP Common Management Information Protocol
CMIPDU Common Management Information Protocol Data Unit
CMIS Common Management Information Service
CMISE Common Management Information Service Element
CSPDN Circuit Switched Public Data Network
DMI Definitions of Management Information
FTAM File Transfer, Access and Management
GDMO Guidelines for the Definition of Managed Objects
GMI Generic Management Information
GMOCS Guidelines for Managed Object Conformance Statements
GRM General Relationship Model
ICS Implementation Conformance Statement
Id Identifier
6 ITU-T Rec. X.701 (1997 E)
ISO/IEC 10040 : 1998 (E)
ISDN Integrated Services Digital Network
LAN Local Area Network
MAPDU Management Application Protocol Data Unit
MCS Management Conformance Summary
MHS Message Handling System
MIB Management Information Base
MICS Management Information Conformance Statement
MIDS Management Information Definition Statement
MIS Management Information Service
MOCS Managed Object Conformance Statement
MOTIS Message Oriented Text Interchange System
MRCS Managed Relationship Conformance Statement
OSI Open Systems Interconnection
PICS Protocol Implementation Conformance Statement
PSPDN Packet Switched Public Data Network
ROSE Remote Operations Service Element
SACF Single Association Control Function
SMAE Systems Management Application Entity
SMAPM Systems Management Application Protocol Machine
SMASE Systems Management Application Service Element
SMF Systems Management Function
SMFA Systems Management Functional Area
SMFU Systems Management Functional Unit
SMI Structure of Management Information
TMN Telecommunications Management Network
TP Transaction Processing
VT Virtual Terminal
WAN Wide Area Network
5 Systems management
Systems management provides mechanisms for the monitoring, control and coordination of resources and OSI protocol
standards for communicating information pertinent to those resources. In order to describe management operations on
resources, the resources are viewed as managed objects with defined properties. Information required for systems
management purposes in any open system may be provided through local input, may result from input from other open
systems through systems management (application layer) communication or may be a result of lower layer protocol
exchanges.
In particular, systems management applies to but is not limited to (e.g. use of ITU-T M.3000-Series, TMN, is also
considered a valid application of systems management):
– OSI Layer 1 (Dedicated lines/leased lines, satellite connections);
– OSI Layer 2 (LAN, WAN, etc.);
– OSI Layer 3 (CSPDN, PSPDN, ISDN, B-ISDN, ITU-T Rec. X.300 subnetwork, etc.);
– OSI Layer 4 (Transport Layer Entities);
– OSI Layer 5 (Session Layer Entities);
– OSI Layer 6 (Presentation Layer Entities);
– OSI Layer 7 (MHS | MOTIS, FTAM, VT, TP, Directory).
NOTE – While the principal impetus for the development of these standards has been the need to manage OSI resources, they also
have broader applicability. Furthermore, it is possible that in the future, standards development may be undertaken to specifically
address additional areas.
ITU-T Rec. X.701 (1997 E) 7
ISO/IEC 10040 : 1998 (E)
Systems management is applicable to a wide range of distributed processing and communications environments. These
environments range from local area networks interconnecting small systems, to interconnected corporate and national
networks on a global scale. Small scale environments may be managed by appropriate small scale management systems,
consisting of a single manager capable of controlling and coordinating the open communication environment through a
number of agents. The standards and concepts are also applicable to large scale environments supporting multiple
managers.
There are three main groupings within the set of systems management standards. They are:
a) a set of standards specifying systems management functions;
b) a set of standards relating to the specification of managed objects;
c) a set of application layer service and protocol standards for communicating information relating to
management functions.
The requirements to be satisfied by systems management activities can conveniently be grouped into five areas, each of
which gives rise to one or more standards covering one or more functions. These areas as defined by the OSI
Management Framework (see CCITT Rec. X.700 | ISO/IEC 7498-4) are:
– fault management;
– configuration management;
– accounting management;
– performance management;
– security management.
However, many items of information, their associated management operations and the communication protocols are
known to be common to more than one area. And, in performing management activities, sets of management functions
may be combined to effect a particular management policy.
For these reasons, systems management standards form a closely interrelated set of standards.
6 Systems management model
6.1 Introduction
This clause identifies a number of concepts of systems management and provides a model to clarify these concepts and
their relationships.
The following subclauses describe the various aspects of the systems management model:
– information aspects;
– functional aspects;
– OSI communications aspects;
– organizational aspects.
Management of a communications environment is an information processing application. Because the environment being
managed is distributed, the individual components of the management activities are themselves distributed. Management
applications perform the management activities in a distributed manner, by establishing associations between systems
management application entities.
As shown in Figure 1 the interactions which take place between systems management application entities are abstracted in
terms of management operations and notifications issued by one entity to the other; these are communicated using
systems management services and protocols.
8 ITU-T Rec. X.701 (1997 E)
ISO/IEC 10040 : 1998 (E)
Managed open system
Performing
Communicating management
operations
Management operations
MIS-User MIS-User
Notifications
(manager role) (agent role)
Notifications
emitted
Managed
objects
TISO0010-92/d01
Figure 1 – Systems management interactions
FIGURE 1/X.701.[D01] =
Management activities are effected through the manipulation of managed objects. For the purposes of systems
management, management applications are categorized as MIS-Users. Each interaction takes place between two MIS-
Users, one taking the manager role, the other the agent role.
An MIS-User taking the role of an agent is that part of a distributed application that manages the managed objects within
its local system environment. An agent performs management operations on managed objects as a consequence of
management operations communicated from a manager. An agent may also forward notifications emitted by managed
objects to a manager.
An MIS-User taking the role of a manager is that part of a distributed application which has responsibility for one or
more management activities, by issuing management operations and receiving notifications.
The concept of a manager is not limited to applications participating solely in systems management; other applications
needing access to management information may use management information services.
Roles are not permanently assigned to MIS-Users. Some MIS-Users can be restricted to only taking an agent role, some
to only taking a manager role while other MIS-Users are allowed to take an agent role in one interaction and to take a
manager role in a separate interaction.
NOTE 1 – When a management interaction between open systems pertains to more than one managed object, the specification of
how the agent distributes the management operation amongst its managed objects is not subject to standardization.
NOTE 2 – A managed object can itself represent a resource outside of the managed system. The relationship between the managed
system and the outside resource may also be one of manager/agent. If the communication between these systems follows OSI
Management standards, then management operations on a managed object in the original managed system might result in further
manager/agent exchanges, operating on a “remote” managed object. No limits are imposed upon the number of such cascaded
management operations that are permitted.
It is important to recognize that this Recommendation | International Standard only establishes a conceptual model that
describes the structure and contents of the information actually communicated by the use of standardized management
information services. Whenever management information is communicated, it is done in terms of this model.
Whether, where and how systems represent and store the real data from which the management information is derived is a
local matter, and therefore not subject to standardization.
NOTE 3 – Figure 2 represents a particular way of viewing certain aspects of the system management model and is given for
information only. The figure has been of value during the development of this Specification. In particular, it differentiates the
mapping to standardized communication (following the rules introduced in 6.2) from local mapping, which illustrates that a
method of viewing the real management information in terms of the model must exist within the systems management application
process. Furthermore, the method exists in the local environment and is therefore an implementation matter not subject to
standardization.
Figure 2 does not show the complete model, nor does it show all the details in full. In particular it does not imply that there is
necessarily only one subtree of the naming tree related to a specific layer, nor does it imply that the term “systems management
information model space” is a defined term.
6.2 Information aspects
This subclause introduces the information aspects of the systems management model. The definitive specification of the
information model is given in CCITT Rec. X.720 | ISO/IEC 10165-1. It refines the concept of Managed Objects defined
in CCITT Rec. X.700 | ISO/IEC 7498-4. It deals with their attributes, the management operations that may be performed
upon them, and the notifications that they may emit. The set of managed objects in a system, together with their attributes,
constitutes that system's Management Information Base (MIB).
ITU-T Rec. X.701 (1997 E) 9
ISO/IEC 10040 : 1998 (E)
Standardized managed objects are expected to be specified by the standardization organizations responsible for
standardizing the resources represented by the managed objects (e.g. the group responsible for standardizing an (N)-layer
protocol entity is also responsible for standardizing the managed object that represents the management view of that
protocol entity). Guidelines and tools to support the definition of managed objects are provided, as are a collection of
definitions of management information to support the definitions of managed objects and the definition of systems
management functions.
6.2.1 Managed objects
A managed object is the OSI Management view of a resource that is subject to management, such as a layer entity, a
connection, a Directory Service Agent, or an item of physical communications equipment. Thus, a managed object is the
abstraction of such a resource that represents its properties as seen by (and for the purpose of) management. An essential
part of the definition of a managed object is the relationship between these properties and the operational behaviour of
the resource. This relationship is not modelled in a general way.
Managed objects can be specific to an individual layer, in which case they are known as (N)-layer managed objects.
Those managed objects that are relevant to more than one layer, to a specific systems management function (management
support object) or to the system as a whole are known as systems managed objects.
Systems management application process
Mapping to standardized communication
Application
Presentation
Session
Local
Transport
mapping
Network
Data-link
Physical
Systems managed objects
(N)-layer managed objects
OSI environment Local environment
TISO0020-92/do2
Managed object
Containment hierarchy of managed objects
Systems management information model space
Use standardized OSI management communication
Figure 2 – Relationship between information and communication aspects
of the systems management model
FIGURE 2/X.701.[D02] =
6.2.2 Attributes
Attributes are properties of managed objects. An attribute has an associated value, which may have a simple or a complex
structure.
6.2.3 Management operations and notifications
Part of the definition of a managed object is the specification of the set of management operations that can be performed
upon it and the effect that these management operations have upon the managed object and its attributes. The definition
may also specify the effect, if any, on related managed objects. The execution of a management operation may also be
conditional upon the state of the managed object or its attributes. An essential part of the definition of a management
operation is the set of possible ways in which it can fail.
10 ITU-T Rec. X.701 (1997 E)
ISO/IEC 10040 : 1998 (E)
Managed objects may also emit notifications, which contain information concerning the occurrence of an event associated
with the managed object.
Whereas the mechanisms for communicating management operations and notifications are subject to OSI management
standardization, the mechanisms for performing management operations and notifications are not. No corresponding
internal systems interface is subject to standardization. The relationship between management operations at the managed
object boundary and what is communicated in protocol between open systems is described in 6.4.
6.3 Functional aspects
This subclause describes functional aspects of the systems management model.
A systems management function may satisfy more than one requirement and to satisfy some requirements, more than one
function may be applicable. Therefore, a many-to-many relationship between functions and requirements exists.
The specification of a systems management function defines the management activities and information that are necessary
to meet the requirements.
Management functions may be combined to accomplish a specific management activity.
Since not all services are always required on a given association, a systems management function's services may be
subgrouped into one or more functional units, which are basic units of negotiation between MIS-Users. In addition,
functional units spanning services from more than one function may be defined.
Functional units that cross function boundaries are provided to support the following sets of capabilities:
a) notifications only;
b) management operations only;
c) notifications and management operations.
NOTE – Other functional units are defined that allow negotiation of subsets of these capabilities (e.g. monitor, control).
The agent cannot in general determine the purpose of the management operations it receives or the notifications it emits.
For example, an open system cannot in general determine whether its responses to requests to read error counters will be
used for the purpose of fault management or performance management. The agent responds to requests from a manager
individually, without needing any wider context within which to carry out the request.
6.4 OSI communications aspects
The interactions between MIS-Users acting in the role of manager and agent respectively are realized through the
exchange of management information. This communication is accomplished using OSI protocols.
The general OSI communication service for systems management is CMIS. Subclause 6.4.1 describes how CMIS is used
to support communications concerning the management operations and notifications applicable to managed objects in a
managed system. Subclauses 6.4.2 through 6.4.5 explain how communications support fits into the application layer
structure.
MIS-Users may make use of other OSI services (such as TP or FTAM) which may or may not support the manager/agent
role distinction, however the MIS-Users shall 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
There are two aspects to communications support for management operations and notifications:
a) support for the transfer of requests for management operations and notifications between MIS-Users;
b) support for the control of access to managed objects and the external dissemination of notification
information.
ITU-T Rec. X.701 (1997 E) 11
ISO/IEC 10040 : 1998 (E)
The major components are shown in Figure 3.
Managed open system
Performing
Communicating management
Access
control
operations
Management operations
MIS-User
Notifications
(manager role)
Notifications
Notification
dissemination em
...

ISO/CEI
NORME
INTERNATIONALE
Deuxihme bdition
1998-10-15
Technologies de I’information -
lnterconnexion de systgmes ouverts
(OSI) - Apergu g&&al de la
gestion-systgmes
Open Systems Interconnection - Systems
Information technology -
management overview
Num&o de &f&ence
ISO/CEI 10040:1998(F)
ISOKEI 10040:1998(F)
PDF - Exonhration de responsabilit6
Le pr&ent fichier PDF peut contenir des polices de caracteres integrees. Conformement aux conditions de licence d’Adobe, ce fichier peut
etre imprim ou visualise, mais ne doit pas etre modifie a moins que I’ordinateur employ6 a cet effet ne beneficie d’une licence autorisant
I’utilisation de ces polices et que celles-ci y soient installees. Lors du telechargement de ce fichier, les parties concernees acceptent de fait
la responsabitite de ne pas &rein&e les conditions de licence d’Adobe. Le Secretariat central de I’ISO decline toute responsabilite en la
matiere.
Adobe est une marque deposee d’Adobe Systems Incorporated.
I I
Les details relatifs aux pro&& logiciels utilises pour la creation du present fichier PDF sont disponibles dans la rubrique General Info du
fichier; les parametres de creation PDF ont et6 optimises pour I’impression. Toutes les mesures ont ete prises pour garantir I’exploitation de
ce fichier par les comites membres de I’ISO. Dans le cas peu probable ou surviendrait un probleme d’utilisation, veuillez en informer le
Secretariat central a I’adresse donnee ci-dessous.
0 ISOKEI 1998
Droits de reproduction reserves. Sauf prescription differente, aucune par-tie de cette publication ne peut etre reproduite ni utilisee sous quelque
forme que ce soit et par aucun pro&de, electronique ou mecanique, y compris la photocopie et les microfilms, sans I’accord ecrit de I’ISO a
l’adresse ci-apres ou du comite membre de I’ISO dans le pays du demandeur.
I SO copyright off ice
Case postale 56 l CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax. [phone]
E-mail copyright @ iso.ch
Web www.iso.ch
Version francaise tiree en 2000
lmprime en Suisse
0 ISO/CEI 1998 - Tous droits reserves

ISO/CEI10040:l998(F)
Sommaire
Page
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.
1 Domaine d’application
...................................................................................................................................
2 References normatives
....................................................
2.1 Recommandations de WIT-T / Normes intemationales identiques
.......
2.2 Paires de Recommandations 1 Normes intemationales equivalentes par leur contenu technique
................................................................................................................................
2.3 Autres references
......................................................................................................................................................
3 Definitions
.......................................................................................
Definitions du modele de reference de base
3.1
..............................................................................................
3.2 Definitions du cadre general de gestion
........................................................................................................................
3.3 Definitions du CMISE
.................................................................................
Definitions du modele d’information de gestion
3.4
...............................
3.5 Definitions du cadre general et de la methodologie des tests de conformite OS1
.......................................................................
3.6 Definitions de l’apercu general de la gestion-systemes
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Abreviations
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 Gestion-systemes
...........................................................................................................................
Modele de gestion-systemes
.........................................................................................................................................
6.1 Introduction
......................................................................................................................
6.2 Aspects informationnels
...........................................................................................................................
6.3 Aspects fonctionnels
..........................................................................................................
6.4 Aspects de communication OS1
.....................................................................................................................
6.5 Aspects organisationnels
..........................................................................................................................
Normes de gestion-systemes
......................................................................................................................
7.1 Architecture et structure
......................................................................................
7.2 Communication des informations de gestion
.................................................................................................
7.3 Structure des informations de gestion
............................................................................................................
7.4 Fonctions de gestion-systemes
.....................................................................................................................................................
8 Conformite
....................................................
Conformite a la presente Recommandation 1 Norme intemationale
8.1
....................................................
8.2 Conformite a la presente Recommandation 1 Norme intemationale
...................................................................................
Annexe A - Contexte d’application pour la gestion-systemes
A. 1 Historique .
........................................................................................
A.2 Contexte d’application de gestion-systemes
................................................................................
A.3 Regles concernant l’etablissement d’associations
A.4 Conformite .
..................................... 28
Annexe B - Declaration de domaine d’application pour les fonctions de gestion-systemes
B.l Regles .
B.2 Gabarit .
. . .
@ ISOKEI
ISO/CEIl0040:l998(F)
Avant-propos
L’ISO (Organisation internationale de normalisation) et la CEI (Commission
electrotechnique internationale) forment ensemble un systeme consacre a la
normalisation internationale consideree comme un tout. Les organismes nationaux
membres de 1’ISO ou de la CEI participent au developpement de Normes internationales
par l’intermediaire des comites techniques trees par l’organisation concernee afin de
s’occuper des differents domaines particuliers de l’activite technique. Les comites
techniques de 1’ISO et de la CEI collaborent dans des domaines d’interet commun.
D’autres organisations internationales, gouvernementales et non gouvernementales, en
liaison avec I’ISO et la CEI participent egalement aux travaux.
Dans le domaine des technologies de l’information, I’ISO et la CEI ont tree un comite
technique mixte, l’ISO/CEI JTC 1. Les projets de Normes internationales adopt& par le
comite technique mixte sont soumis aux organismes nationaux pour approbation, avant
leur acceptation comme Normes internationales. Les Normes internationales sont
approuvees conformement aux procedures qui requierent l’approbation de 75 % au
moins des organismes nationaux votants.
La Norme internationale ISOKEI 10040 a ete elaboree par le comite technique mixte
ISOKEI JTC 1, Technologies de Z’information, sous-comite SC 33, Services
d’applications distribue’es, en collaboration avec WIT-T. Le texte identique est publie
en tant que Recommandation UIT-T X.701.
Cette deuxieme edition annule et remplace la premiere edition (ISOKEI 10040: 1992), qui a
fait l’objet d’une revision technique.
Elle incorpore aussi Mmendement 1: 1995,
le Rectificatif technique 1: 1994 et le Rectificatif technique 2: 1996.
L’annexe A fait partie integrante de la presente Norme internationale. L’annexe B est
donnee uniquement a titre d’information.
iv
ISOKEI 10040 : 1998 (F)
NORME INTERNATIONALE
RECOMMANDATION UIT-T
TECHNOLOGIES DE L’INFORMATION -
INTERCONNEXION DE SYSThMES OUVERTS (OSI) -
APERCU G~NhAL DE LA GESTION-SYSTkMES
1 Domaine d’application
La presente Recommandation 1 Norme intemationale
-
offre un apercu general de la famille des normes de gestion-systemes;
-
etablit les bases permettant de subdiviser les normes de gestion-systemes en groupes distincts, precise le
domaine d’application de chaque groupe et definit les principales composantes a l’interieur de chaque
groupe;
-
foumit des directives pour l’elaboration de normes de gestion-systemes et identifie les liens entre ces
normes;
-
d&nit les termes utilises dans d’autres normes de gestion-systemes;
-
s’applique a la definition de toutes les normes de gestion-systemes et a tous les aspects de la gestion-
systemes, quelle que soit leur importance;
-
s’applique aux cas ou la responsabilite de la gestion-systemes est centralisee ou distribuee;
-
definit un modele de gestion-systemes, precise plusieurs aspects (informationnel, fonctionnel, de
communication et d’organisation) de la gestion-systemes et affine ledit mod&e pour preciser ces differents
aspects;
-
recense les principes regissant les imperatifs de conformite et les declarations de conformite par rapport
aux normes de gestion-systemes.
11 n’existe aucun imperatif de conformite aux dispositions du corps principal de la presente Recommandation 1 Norme
intemationale; cette demiere precise toutefois les exigences auxquelles doivent repondre les normes qui se veulent
conformes a la gestion-systemes.
gestion-systemes et specific les regles de negotiation des unites
L’Annexe A definit un contexte d’application pour la
fonctionnelles de gestion-systemes. Des exigences de c onformite sont associees a ces regles.
2 Rhfbrences normatives
Les Recommandations et Normes intemationales suivantes contiennent des dispositions qui, par suite de la reference qui
y est faite, constituent des dispositions valables pour la presente Recommandation 1 Norme intemationale. Au moment de
la publication, les editions indiquees etaient en vigueur. Toutes Recommandations et Normes sont sujettes a revision et
les parties prenantes aux accords fond& sur la presente Recommandation 1 Norme intemationale sont invitees a
rechercher la possibilite d’appliquer les editions les plus recentes des Recommandations et Normes indiquees ci-apres.
Les membres de la CEI et de 1’ISO possedent le registre des Normes intemationales en vigueur. Le Bureau de la
normalisation des telecommunications de I’UIT tient a jour une liste des Recommandations UIT-T en vigueur.
Recommandations de IWIT-T 1 Normes internationales identiques
21 .
-
Recommandation UIT-T X.200 (1994) I ISO/CEI 7498-l : 1994, Technologies de Z’informatkz -
Modkle de rkfkrence de base: le mod2Ze de rkfkrence de base.
Interconnexion des syskmes ouverts -
-
Recommandation UIT-T X.207 (1993) I ISO/CEI 9545: 1994, Technologies de Z’information -
Interconnexion des systGmes ouverts - Structure de la couche application.
-
Recommandation UIT-T X.217 (1995) I ISO/CEI 8649: 1996, Technologies de Pinformation -
Interconnexion des syst2mes ouverts - Dkfinition de service applicable ti Z’klkment de service de contrGZe
d’association.
Rec. UIT-T X.701 (1997 F)
ISOKEI 10040 : 1998 (F)
Recommandation UIT-T X.227 (1995) I ISO/CEI 8650-l : 1996, Technologies de Z’infirmation -
Znterconnexion des systGmes ouverts - ProtocoZe en mode connexion applicable a Z’eZement de service de
controZe d’association: spe’czjkation du protocole.
Recommandation UIT-T X.680 (1994) ( ISO/CEI 8824- 1: 1995, Technologies de Z’information - Notation
de syntaxe abstraite numero un: specification de Za notation de base.
Recommandation UIT-T X.68 1 (1994) I ISO/CEI 8824-2: 1995, Technologies de Z’information - Notation
de syntaxe abstraite numero un: spectftcation des objets informationnels.
Recommandation UIT-T X.682 (1994) I ISOKEI 8824-3: I. 995, Technologies de Z’information - Notation
de syntaxe abstraite numkro un: spkzjication des contraintes.
Recommandation UIT-T X.683 (1994) I ISOKEI 8824-4: 1995, Technologies de Z’information - Notation
de syntaxe abstraite numkro un: paramktrage des sp&t;Jications de la notation de syntaxe abstraite
num&o un.
-
Recommandation UIT-T X.690 (1994) I ISOKEI 8825- 1: 1995, Technologies de Z’information - RkgZes de
codage de la notation de syntaxe abstraite numkro un: sp&iJication des rsgles de codage de base, des
r;gZes de codage canoniques et des rGgZes de codage distinctives.
Recommandation UIT-T X.691 (1995) I ISOKEI 8825-2: 1995, Technologies de Z’information - RGgZes de
codage ASN. 1: spkcification des rkgles de codage compact.
Recommandation UIT-T X.702 (1995) I ISOKEI 11587: 1996, Technologies de Z’information -
Interconnexion des systemes ouverts - Contexte d’application pour la gestion-systemes avec traitement
transactionnel.
-
Recommandation X.712 du CCITT (1992) 1 ISO/CEI 9596-2: 1993, Technologies de Z’information -
Interconnexion des systemes ouverts - Protocole commun de transfert d’informations de gestion:
formulaire de declaration de conformite d’une instance de protocole, plus Corrigendum technique 1
(1996) et Corrigendum technique 2 (1996).
-
Recommandation X.720 du CCITT (1992) I ISO/CEI 10165-l : 1993, Technologies de Z’information -
Interconnexion des systkmes ouverts - Structure des informations de gestion: modGZe d’information de
gestion.
-
Recommandation X.721 du CCITT (1992) I ISOKEI 10165-2: 1992, Technologies de Z’information -
Interconnexion des systemes ouverts - Structure des informations de gestion: dkfinition des informations
de gestion.
-
Recommandation X.722 du CCITT (1992) j ISOKEI 10165-4: 1992, TechnoZogies de Z’information -
Interconnexion des systGmes ouverts -
Structure des informations de gestion: directives pour la definition
des objets g&&s.
-
Recommandation UIT-T X.723 (1993) I ISOKEI 10 165-5: 1994, Technologies de Z’information -
Interconnexion des systkmes ouverts
- Structure des informations de gestion: informations generiques de
gestion.
-
Recommandation UIT-T X.724 (1993) I ISO/CEI 10165-6: 1994, Technologies de Z’information -
Interconnexion des systsmes ouverts - Structure de Z’information de gestion: Spkczjkations et directives
pour Z’ktablissement des formulaires de dklaration de conformitk d’instances assock% ir la gestion OSI.
-
Recommandation UIT-T X.725 (1995) 1 ISOKEI 10165-7: 1996, Technologies de Z’information -
Interconnexion des syst$mes ouverts - Structure de Z’information de gestion: modsle g&&al de relation.
-
Recommandation X.730 du CCITT (1992) I ISO/CEI 10164- 1: 1993, Technologies de Z’information -
Interconnexion des systkmes ouverts
- Gestion-systsmes: fonction de gestion des objets.
Recommandation X.73 1 du CCITT (1992) I ISO/CEI 10164-2: 1992, Technologies de Z’information -
Interconnexion des systsmes ouverts
- Gestion-systemes: fonction de gestion d’itats.
Recommandation X.732 du CCITT (1992) I ISO/CEI 10 164-3: 1993, Technologies de Z’information -
Interconnexion des systemes ouverts - Gestion-systemes: attributs relationnels.
Recommandation X.733 du CCITT (1992) I ISO/CEI 10164-4: 1992, Technologies de Z’information -
Interconnexion des systemes ouverts
- Gestion-systemes: fonction de signalisation des aZarmes.
Recommandation X.734 du CCITT (1992) I ISO/CEI 10164-5: 1993, Technologies de Z’information -
Interconnexion des systGmes ouverts - Gestion-systsmes: fonction de gestion des rapports d’&!nement.
Rec. UIT-T X.701 (1997 F)
ISOKEI 10040:1998(F)
-
Recommandation X.735 du CCITT (1992) ) ISO/CEI 10164-6: 1993, Technologies de Z’information -
Gestion-systemes: fonction de commande des registres de
Interconnexion des systGmes ouverts -
consignation.
-
Recommandation X.736 du CCITT (1992) I ISOKEI 10164-7: 1992, TechnoZogies de Z’information -
- Gestion-systemes: fonction de signalisation des alarmes de
Interconnexion des systemes ouverts
securite.
-
Recommandation UIT-T X.737 (1995) I ISO/CEI 10164-14:1996, Technologies de Z’information -
Interconnexion des systemes ouverts - Gestion-systemes: categories de tests de confiance et de
diagnostic.
-
Recommandation UIT-T X.738 (1993) ( ISO/CEI 10164-13: 1995, Technologies de Z’information -
- Gestion-systemes: fonction de recapitulation.
Interconnexion des systemes ouverts
-
Recommandation UIT-T X.739 (1993) I ISO/CEI 10164-l 1: 1994, Technologies de Z’information -
Interconnexion des systemes ouverts - Gestion-systemes: objets et attributs metriques.
-
Recommandation X.740 du CCITT (1992) / ISO/CEI 10164-8: 1993, Technologies de Z’information -
Interconnexion des systemes ouverts - Gestion-systemes: fonction de piste de verification de securite.
-
Recommandation UIT-T X.741 (1995) I ISO/CEI 10164-9: 1995, Technologies de Z’information -
- Gestion-systemes: objets et attributs de controle d’acces.
Interconnexion des systemes ouverts
-
Recommandation UIT-T X.742 (1995) I ISOKEI 10164-10: 1995, TechnoZogies de Z’information -
Interconnexion des systemes ouverts - Gestion-systemes: fonction de comptage d’utilisation aux fins de
comptabilite.
-
Recommandation UIT-T X.745 (1993) I ISO/CEI 10164-12: 1994, Technologies de Z’information -
Gestion-systemes: fonction de gestion des tests.
Interconnexion des systemes ouverts -
-
Recommandation UIT-T X.746 (1995) I ISO/CEI 10164-l 5: 1995, Technologies de Z’information -
Interconnexion des systemes ouverts - Gestion-systemes: fonction de programmation.
-
Recommandation UIT-T X.75 1 (1995) I ISO/CEI 10164-17: 1996, TechnoZogies de Z’information -
Interconnexion des systemes ouverts - Gestion-systemes: fonction de basculement.
Paires de Recommandations 1 Normes internationales kquivalentes par leur contenu technique
22 .
-
Recommandation X.208 du CCITT (1988), Speczfkation de la syntaxe abstraite numero un (ASN. I).
ISO/CEI 8824: 1990, Technologies de Z’information - Interconnexion de systemes ouverts - SpeciJication
de la notation de syntaxe abstraite numero I (ASN. I).
-
Recommandation X.209 du CCITT (1988), Speczfication des regles de codage de base pour la notation
de syntaxe abstraite numero un (ASN. I).
ISO/CEI 8825: 1990, Technologies de Z’information - Interconnexion de systemes ouverts - Specification
de regles de base pour coder la notation de syntaxe abstraite numero UNE (ASN. 1).
-
modele, notation et definition du
Recommandation X.2 19 du CCITT (1988), Operations distantes:
service.
- Communication de texte - Operations a
ISO/CEI 9072- 1: 1989, Systemes de traitement de Z’information
distance - Partie I: Modele, notation et definition du service.
-
Recommandation X.229 du CCITT (1988), Operations distantes: specification du protocole.
ISOKEI 9072-2: 1989, Systemes de traitement de Z’information - Communication de texte - Operations a
distance - Partie 2: SpeciJication du protocole.
-
Recommandation UIT-T X.290 (1995), Cadre general et methodologie des tests de conformite
d’interconnexion des systemes ouverts pour Zes Recommandations sur Zes protocoles pour Zes applications
de Z’UIT-T - Concepts generaux.
ISOKEI 9646-l : 1994, Technologies de Z’information - Interconnexion de systemes ouverts - Cadre
general et methodologie des tests de conformite OSI - Partie 1: Concepts generaux.
-
Recommandation UIT-T X.296 (1995), Cadre general et methodologie des tests de conformite OSI pour
Zes Recommandations sur Zes protocoles pour Zes applications de Z’UIT-T - Declarations de conformite
d’instance.
Rec. UIT-T X.701 (1997 F) 3
ISOKEI 10040 : 1998 (F)
ISO/CEI 9646-7: 1995, Technologies de l’information -
Interconnexion de syst2me.s ouverts (OSI) -
- Mkthodologie g&n&ale et proce’dures - Partie 7: Dklarations de conformit& des
Essais de conformitk
mises en Euvre.
-
Recommandation X.700 du CCITT (1992), Cadre de gestion pour l’interconnexion de systkmes ouverts
pour les applications du CCITT.
ISOICEI 7498-4: 1989, Systt?mes de traitement de Z’information - Interconnexion de systkmes ouverts -
Partie 4: Cadre g&n&al de gestion.
ModGle de rifkrence de base -
-
Recommandation X.710 du CCITT (1991), Dkfinition du service commun de transfert d’informations de
gestion pour les applications du CCITT.
ISO/CEI 9595: 199 1, Technologies de /‘information - Interconnexion de systGmes ouverts - Dkfinition du
service commun d’informations de gestion.
-
Recommandation X.71 1 du CCITT (1991), SpkciJication du protocoZe commun de transfert
d’informations de gestion pour les applications du CCITT.
HOLE1 9596- 1: 199 1, Technologies de Z’information - Interconnexion de systGmes ouverts - Protocole
commun d’information de gestion - Partie I: Spkification.
-
Recommandation X.860 du CCITT (1992), Interconnexion des systsmes ouverts - Traitement de
transactions rkparties: mod;le.
ISO/CEI 10026- 1: 1992, Technologies de Z’information - Interconnexion de systGmes ouverts (OSI) -
Traitement transactionnel rkparti - Partie I: Modgle OSI TP.
-
Recommandation X.861 du CCITT (1992), Interconnexion des systkmes ouverts - Sp+cation du
service de traitement des transactions rkparties.
ISOICEI 10026-2: 1992, Technologies de l’information - Interconnexion de systsmes ouverts (OSI) -
Traitement transactionnel rkparti - Partie 2: Service OSI TP.
-
Recommandation X.862 du CCITT (1993), Interconnexion des syskmes ouverts - Traitement
transactionnel rkparti: sp&%ation du protocole.
ISOICEI 10026-3: 1992, Technologies de l’information - Interconnexion de systGmes ouverts (OSI) -
Traitement transactionnel rkparti - Partie 3: Spkzfication du protocole.
.
23 Autres rhfhences
-
IS0 8571:1988, Systsmes de traitement de l’information - Interconnexion de systsmes ouverts -
Transfert, acc&s et gestion defichiers.
-
ISOKEI 9545:1994, Technologies de l’information - Interconnexion de systGmes ouverts (OSI) -
Structure de la couche application.
3 Dkfinitions
31 . DkTinitions du modcle de r6f6rence de base
La prkente Recommandation 1 Norrne internationale est baske sur les concepts dkfinis dans le modtile de la rkfkrence de
base pour l’interconnexion des systkmes ouverts et utilise les terrnes suivants dkfinis dans la Rec. UIT-T X.200 1
ISO/CEI 7498- 1:
klkment de service d’application;
a)
b) gestion-systtimes.
32 . Dbfinitions du cadre g&k-al de gestion
La prksente Recommandation 1 Norme intemationale utilise les termes suivants, dkfinis dans la Rec. X.700 du
CCITT 1 ISOKEI 7498-4:
objet g&-k;
a)
b)
base d’information de gestion;
entite d’application de gestion-systkmes.
C>
4 Rec. UT-T X.701 (1997 F)
ISOKEI 10040 : 1998 (F)
33 . Dbfinitions du CMISE
La prksente Recommandation I Norme intemationale utilise les termes suivants dkfinis dans la Rec. X.710 du
CCITT I ISO/CEI 9595:
attribut (d’un objet g&k);
a)
klement du service commun d’information de gestion;
W
services communs d’information de gestion.
C>
34 . Dbfmitions du moditle d’information de gestion
les termes suivants, dkfinis dans la Rec. X.720 du
La prksente Recommandation I Norme intemationale utilise
CCITT I ISOKEI 10165-l:
type d’attribut;
a>
b) arbre de d&omination;
c) limite d’un objet g&k.
La prksente Recommandation I Norme intemationale utilise le terme suivant, dkfini dans la Rec. UIT-T X.725 I
ISOKEI 10165-7:
relation g&e.
35 . Dbfinitions du cadre g&&al et de la mkthodologie des tests de conformitG OS1
La prksente Recommandation I Norme intemationale utilise les termes suivants, dkfinis dans la Rec. UIT-T X.290 I
ISO/CEI 9646-l et la Rec. UIT-T X.296 I ISO/CEI 9646-7:
a) dkclaration de conformitk d’implkmentation de protocole (PICS);
b) formulaire PICS;
c) declaration de conformitk de systkme;
d) dklaration de confonnitk d’implementation (ICS);
e) formulaire ICS.
36 . Dkfmitions de l’aperqu g&k-al de la gestion-systi!mes
Pour les besoins de la prksente Recommandation I Norme intemationale, les dkfinitions suivantes s’appliquent.
3.6.1 agent: utilisateur-MIS qui, pour une interaction don&e de gestion-systkmes, a pris un rGle d’agent.
3.6.2 rGle d’agent: rhle pris par un utilisateur-MIS et dans lequel il est capable d’effectuer des opkrations de gestion
sur des objets g&-6s et d’kmettre des notifications pour le compte d’objets g&s.
3.6.3 dkfinitions g&h-iques: definitions de classes d’objets g&s, de types d’attribut, de types de notification ou de
types d’opkration de gestion destinkes A une utilisation g&-kale.
interaction (de gestion): opkration de gestion unique ou notification unique ou ensemble identifik d’opkrations
3.6.4
de gestion et de notifications logiquement liees pendant laquelle/lequel le rble de gestionnaire et celui d’agent ne
changent pas.
classe d’objets g&h: ensemble nommk d’objets g&s partageant les memes ensembles (nommk) d’attributs,
3.6.5
de notifications, d’opkrations de gestion (lots) et repondant aux mzmes conditions en ce qui conceme la presence de ces
lots.
NOTE - Les deux dkfinitions suivantes sont alignees sur les dkfinitions correspondantes figurant dans le cadre g&&al et la
m&hodologie des tests de conformitk OSI, Rec. UIT-T X.290 1 ISO/CEI 9646-l pour le PICS et le formulaire PICS.
declaration de conformitk d’objet g&C (MOCS, managed object conformance statement): declaration faite
3.6.6
par le foumisseur d’une application d’objet g&k, prkisant les capacitk et les options qui ont &k rkaliskes et toute
caractkristique qui a ktk omise.
Rec. UIT-T X.701 (1997 F) 5
ISO/CEI 10040 : 1998 (F)
3.6.7 declaration de conformite d’information de gestion (MICS, management information conformance
statement): declaration d’un foumisseur etablissant les capacites de role de gestionnaire d’une instance, les options
d’information de gestion qui sont assurees et toute caracteristiques qui a ete omise.
3.6.8 formulaire MICS: document se presentant sous la for-me d’un questionnaire, et qui, une fois compl& par le
devient une declaration de conformite
foumisseur d’une instance ayant des capacites de role de gestionnaire,
d’information de gestion.
3.6.9 formulaire MOCS: document, sous forme de questionnaire, etabli par le definisseur de l’objet g&k ou par le
concepteur de la suite de tests de conformite qui, lorsqu’il est rempli pour l’instance d’un objet g&e, devient le MOCS.
3.6.10 systeme (ouvert) g&C: systeme ouvert reel contenant un utilisateur-MIS qui peut prendre le role d’agent.
3.6.11 domaine de gestion: specification d’une collection d’objets g&es don&s.
3.6.12 information de gestion: information a l’interieur d’un systeme ouvert qui peut etre transferee moyennant
l’utilisation des protocoles de gestion OSI.
3.6.13 juridiction de gestion: representation de la relation entre une politique de gestion et un domaine de gestion.
politique de gestion: specification identifiable qui peut etre evaluee compte tenu des objets g&es.
3.6.14
3.6.15 violation de la politique de gestion: situation observee lorsque des objets g&es ne peuvent se conformer a la
semantique d’une politique.
objet g&e des systemes, defini specifiquement pour assurer une fonction de gestion-
3.6.16 objet support de gestion:
systemes xemple cons&nation, discriminateur).
(par e
3.6.17 gestionnaire: utilisateur-MIS, qui, pour une interaction donnee de gestion-systemes, a pris un role
de gestionnaire.
3.6.18 role de gestionnaire: role joue par un utilisateur-MIS en vertu duquel il est capable de declencher des
operations de gestion et de recevoir des notifications.
3.6.19 systeme (ouvert) de gestion: systeme ouvert reel contenant un utilisateur-MIS qui peut jouer le role
de gestionnaire.
3.6.20 utilisateur-MIS: application utilisant les services de gestion-systemes.
notification: information envoyee par un objet g&e concernant un evenement survenu a l’interieur de
3.6.21
l’obj et g&e.
3.6.22 type de notification: type de don&es nomme definissant une sorte particuliere de notification.
3.6.23 objet gdre de couche (IV): objet gere propre a la couche (N).
3.6.24 protocole de gestion de couche (N): protocole de couche (N) utilise pour l’echange d’informations de gestion
de couche (N) acceptees uniquement par les protocoles des couches (N-l) et inferieures.
NOTE - La prksente Recommandation 1 Norme intemationale ne spkifie ni n’exige l’utilisation de protocoles de gestion de
couche (N). La dkfinition est incluse ici dans un souci d’exhaustivitk.
operation (de gestion-systemes): operation effect&e sur un objet gere pour realiser la gestion-systemes.
3.6.25
3.6.26 objet g&C des systemes: objet gere significatif pour plus d’une couche, pour le systeme dans son ensemble ou
pour des fonctions precises de gestion.
3.6.27 processus d’application de gestion-systemes: processus d’application participant a la gestion-systemes.
3.6.28 Mment de service d’application de gestion-systemes: element de service d’application assurant des services
de gestion-systemes.
3.6.29 fonction de gestion-systemes: par-tie des activites de g&on-systemes qui repondent a un ensemble de besoins
d’utilisateurs lies logiquement.
zone fonctionnelle de gestion-systemes: categoric de besoins d’utilisateur relevant de la gestion-systemes.
3.6.30
unit6 fonctionnelle de gestion-systemes: ensemble nomme non vide de services de gestion-systemes defini
3.6.31
pour identifier des ensembles specifiques de fonctionnalites lorsqu’il est necessaire de definir ou de negocier l’utilisation
desdites fonctionnalites entre des systemes d’extremite ou pour servir de reference a d’autres normes.
Rec. UIT-T X.701 (1997 F)
ISOKEI 10040 : 1998 (F)
3.6.32 paquet d’unitks fonctionnelles de gestion-systCmes: ensemble nomme non vide d’unites fonctionnelles de
gestion-systemes, defini pour les besoins de la negotiation des unites fonctionnelles sur une association.
3.6.33 protocole d’application de gestion=systGmes: protocole de la couche Application admettant des services de
gestion-systemes.
3.6.34 service de gestion-systcmes: ensemble nomme de primitives de service qui foumissent un service destine a
etre utilise dans la gestion-systemes.
4 Abrhiations
Pour les besoins de la presente Recommandation 1 Norme intemationale, les abreviations suivantes soni utilisees.
ACSE element de service de controle d’association (association control service element)
ASE element de service d’application (application service element)
ASN. 1 notation de syntaxe abstraite numero un (abstract syntax notation one)
CMIP protocole commun d’information de gestion (common management information protocol)
CMIPDU unite de don&es du protocole commun d’information de gestion (common management
information protocol data unit)
CMIS service commun d’information de gestion (common management information service)
element du service commun d’information de gestion (common management information service
CMISE
element)
DMI definitions des informations de gestion (definitions of management information)
FTAM transfert, acces et gestion de fichiers (file transfer, access and management)
GDMO directives pour la definition des objets g&es (guidelines for the definition of managed objects)
informations generiques de gestion (generic management information)
GM1
directives pour l’etablissement de declarations de conformite d’objets g&es (guidelines for
GMOCS
managed object conformance statements)
modele relationnel general (genera2 relationship model)
GRM
ICS declaration de conformite d’implementation (implementation conformance statement)
Id identificateur
LAN reseau local (local area network)
MAPDU unite de don&es du protocole d’application de gestion (management application protocol
data unit)
MCS recapitulatif de conformite de gestion (management conformance summary)
MHS systeme de messagerie (message handling system)
base d’information de gestion (management information base)
MIB
MICS declaration de conformite d’information de gestion (management information conformance
statement)
MIDS declaration de definition d’information de gestion (management information definition
statement)
service d’information de gestion (management information service)
MIS
MOCS declaration de conformite d’objet gere (managed object conformance statement)
MOTIS systeme d’echanges de textes orient& messages (message oriented text interchange system)
MRCS declaration de conformite de relation geree (managed relationship conformance statement)
interconnexion des systemes ouverts (open systems interconnection)
OS1
declaration de conformite d’implementation de protocole (protocol implementation conformance
PIGS
statement)
RNIS reseau numerique a integration de services
Rec. UIT-T X.701 (1997 F) 7
ISO/CEI 10040 : 1998 (F)
reseau numerique a integration de services a large bande
RNIS-LB
ROSE element de service d’operations distantes (remote operations service element)
reseau public de don&es a commutation de circuits
RPDCC
RPDCP reseau public de don&es a commutation par paquets
SACF fonction de controle d’association unique (single association control function)
entite d’application de gestion-systemes (systems management application entity)
SMAE
SMAPM machine protocole d’application de gestion-systemes (systems management application protocol
machine)
element de service d’application de gestion-systemes (systems management application service
SMASE
element)
SMF fonction de gestion-systemes (systems management function)
SMFA zone fonctionnelle de gestion-systemes (systems management functional area)
SMFU unite fonctionnelle de gestion-systemes (systems management functional unit)
SMI structure de l’information de gestion (structure of management information)
RGT reseau de gestion des telecommunications
TP traitement transactionnel (transaction processing)
VT terminal virtue1 (virtual terminal)
WAN reseau regional (wide area network)
5 Gestion-systcmes
La gestion-systemes foumit des mecanismes permettant de surveiller, de controler et de coordonner les ressources ainsi
que les normes de protocole OS1 permettant de communiquer des informations concernant ces ressources. Pour decrire
les operations de gestion effectuees sur les ressources, les ressources sont considerees comme des objets g&-es ayant des
proprietes definies. Les informations necessaires pour les besoins de la gestion-systemes dans tout systeme ouvert
peuvent etre fournies par entree locale, peuvent resulter de don&es provenant d’autres systemes ouverts par le biais
d’une communication (couche Application) de gestion-systemes ou d’echanges entre protocoles des couches inferieures.
En particulier, la gestion-systemes s’applique notamment mais pas exclusivement aux couches suivantes (par exemple,
l’utilisation des Recommandations UIT-T de la serie M.3000 relatives au reseau de gestion des telecommunications est
egalement consideree comme &ant une application valable de la gestion-systemes):
-
couche 1 de 1’OSI (lignes specialisees/lignes louees, liaisons par satellite);
-
couche 2 de 1’OSI (LAN, WAN, etc.);
-
couche 3 de 1’OSI (RPDCC, RPDCP, RNIS, RNIS-LB, sows-reseau conforme aux specifications de la
Rec. UIT-T X.300);
-
couche 4 de 1’OSI (entites de la couche Transport);
-
couche 5 de 1’OSI (entites de la couche Session);
-
couche 6 de 1’OSI (entites de la couche Presentation);
-
couche 7 de 1’OSI (MHS I MOT& FTAM, VT, TP, annuaire).
NOTE - Si ces normes ont ete klaborkes essentiellement eu kgard h la necessitk de g&-er les ressources OSI, elles ont aussi une
applicabilitk plus large. De plus, il est possible qu’8 l’avenir, l’elaboration des normes Porte sur des domaines supplementaires bien
spkcifiques.
La gestion-systemes s’applique a une large gamme d’environnements de traitement et de communication distribues. Ces
environnements vont des reseaux locaux reliant de petits systemes a des reseaux prives ou nationaux interconnect& a
l’echelle mondiale. Dans le cas des environnements peu “etendus” la gestion peut etre assuree par les systemes de gestion
appropries correspondants, composes d’un seul gestionnaire capable de controler et de coordonner l’environnement
ouvert de communications grace a un certain nombre d’agents. Les normes et les concepts s’appliquent aussi a des
environnements plus etendus qui admettent plusieurs gestionnaires.
8 Rec. UIT-T X.701 (1997 F)
ISO/CEI 10040 : 1998 (F)
L’ensemble des normes de gestion-systemes se subdivise en trois groupes principaux:
un ensemble de normes specifiant les fonctions de gestion-systemes;
a>
un ensemble de normes relatives a la specification des objets g&es;
b)
un ensemble de normes de protocoles et de services de la couche Application permettant de communiquer
C>
les informations concernant les fonctions de gestion.
Les exigences auxquelles doivent se conformer les activites de gestion-systemes peuvent, par commodite, etre classees
en cinq domaines dont chacun donne lieu a une ou plusieurs normes couvrant une ou plusieurs fonctions. Ces domaines,
definis dans le cadre general de gestion OS1 (voir la Rec. X.700 du CCITT 1 ISOKEI 7498-4) sont les suivants:
gestion des fautes;
-
gestion des configurations;
-
gestion de la comptabilite;
-
gestion des performances;
-
securite.
gestion de la
Toutefois, de nombreux elements d’information, les operations de gestion et les protocoles de communication qui leur
sont associes sont communs a plusieurs domaines. Lorsqu’on execute les activites de gestion, il est possible de combiner
des ensembles de fonctions de gestion pour realiser une politique de gestion particuliere.
Pour ces raisons, les normes de gestion-systemes forment un ensemble de normes etroitement liees.
6 Mod&e de gestion-syst&mes
61 . Introduction
Le present article d&nit un certain nombre de concepts propres a la gestion-systemes et foumit un modele permettant de
preciser ces concepts ainsi que leurs relations.
Les paragraphes ci-apres decrivent les divers aspects du modele de gestion-systemes:
-
aspects informationnels;
-
aspects fonctionnels;
aspects de communication OSI;
-
aspects organisationnels.
La gestion d’un environnement de communication est une application de traitement de l’information. L’environnement
g&-e &ant distribue, les differentes composantes des activites de gestion sont elles-memes distribuees. Les applications
de gestion executent les activites de gestion de facon distribuee, moyennant l’etablissement d’associations entre les
entites d’application de gestion-systemes.
Comme le montre la Figure 1, les interactions intervenant entre les differentes entites d’application de gestion-systemes
sont resumees sous forme d’operations de gestion et de notifications envoyees par une entite a une autre; elles sont
transmises A l’aide de services et de protocoles de gestion-systkmes.
Les activites de gestion se realisent par manipulation d’objets g&es. Pour les besoins de la gestion-systkmes, les
applications de gestion sont assimilees a des categories d’utilisateurs-MIS. Chaque interaction fait intervenir deux
utilisateurs-MIS, l’un jouant le role de gestionnaire et l’autre le role d’agent.
Un utilisateur-MIS qui joue le role d’agent est la partie d’une application distribuee qui gere les objets g&es dans
l’environnement de son systeme local. Un agent effectue des operations de gestion sur des objets g&es a la suite
d’operations de gestion emanant d’un gestionnaire. Un agent peut aussi retransmettre des notifications envoyees par des
objets g&es a un gestionnaire.
gestionnaire est la partie d’une application distribuee qui est responsable d’une ou
Un utilisateur-MIS qui joue le role de
pour ce faire, initialise des operations de gestion et recoit des notifications.
de plusieurs activites de gestion et qui,
.cations intervenant uniquement dans la gestion-systemes; d’autres
Le concept de gestionnaire n’est pas limite aux appli
de gestion peuvent utiliser les services d’information de gestion.
applications qui doivent avoir acces aux informations
Rec. UIT-T X.701 (1997 F) 9
ISO/CEI 10040 : 1998 (F)
Systkme g&k ouvert
Exkcution
op&-ations
--- b
de gestion
Utilisateur-MIS
Utilisateur-MIS
(r6le d’agent)
(r6le de gestionnaire:
Objets :
g&h
TlSOOOlO-92/dOl
Figure 1 - Interactions de gestion-systtimes
Les roles ne sont pas affect& de facon definitive aux utilisateurs-MIS. Certains utilisateurs-MIS peuvent etre limit& a
un role d’agent, d’autres a un role de gestionnaire alors que d’autres utilisateurs-MIS sont autorises a jouer le role d’agent
dans une interaction et celui de gestionnaire dans une autre interaction.
gestion entre systemes ouverts concerne plus d’un objet g&e, la specification de la facon dont
NOTE 1 - Lorsqu’une interaction de
l’agent repartit l’operation de gestion entre ses objets g&-es ne fait pas l’objet d’une normalisation.
NOTE 2 - Un objet g&e peut lui-meme rep&enter une ressource exterieure au systeme g&e. La relation entre le systeme gere et
la ressource exterieure peut aussi etre une relation du type gestionnaire/agent. Si la communication entre ces systemes respecte les
normes de gestion OSI, les operations de gestion sur un objet g&-e appartenant au systeme g&e d’origine risquent d’aboutir a de
nouveaux echanges gestionnaire/agent, agissant sur un objet gere “distant”. Le nombre d’operations de gestion en cascade de ce
type qui sont auto&es n’est pas limit&
11 importe de reconnaitre que la presente Recommandation 1 Nor-me intemationale ne fait que definir un modele
conceptuel qui d&-it la structure et le contenu des informations qui sont effectivement communiquees par le biais des
services normalises d’information de gestion. Chaque fois qu’une information de gestion est communiquee, elle l’est
conformement a ce modele.
Quant a la question de savoir si, ou et comment les systemes representent et mettent en memoire les don&es reelles a
partir desquelles l’information de gestion est obtenue, elle doit etre resolue au niveau local et ne fait done pas l’objet
d’une normalisation.
NOTE 3 - La Figure 2 represente une facon particuliere de visualiser certains aspects du modele de gestion-systemes et est
don&e a titre d’inforrnation seulement. Cette figure presentait de l’interet lors de l’elaboration de la presente Specification. Elle
etablit notamment une distinction entre le mappage avec les communications normalisees (conformement aux regles enoncees
en 6.2) et le mappage local, ce qui tend a prouver qu’une methode permettant de visualise
...