Information technology — Open Systems Interconnection — Systems management: Event Report Management Function

Defines a systems management function which may be used by an application process in a centralized or decentralized management environment to interact for the purpose of systems management. Establishes user requirements for the event report management function, establishes models that relate the services provided by this function to user requirements, defines the services provided by the function, specifies the protocol that is necessary in order to provide the services, defines the relationship between the services and SMI operation and notifications, defines relationships with other systems management functions, specifies conformance requirements.

Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Gestion-systèmes: Fonction de gestion de rapport événementiel

General Information

Status
Published
Publication Date
26-May-1993
Current Stage
9093 - International Standard confirmed
Completion Date
29-Jul-2008
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 10164-5:1993 - Information technology -- Open Systems Interconnection -- Systems management: Event Report Management Function
English language
18 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL
ISOJIEC
STANDARD 10164-5
First edition
1993-06- 15
Information technology - Open Systems
Interconnection - Systems Management:
Event Report Management Function
- In terconnexion de systkmes ouverts
Technologies de I’informa tion
- Gestion-systemes: Fonction de gestion de rapport benementiel
(OW
Reference number
ISO/IEC 10164-5:1993(E)

---------------------- Page: 1 ----------------------
Page
Contents
1
1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
Normative references .
2
............ 1
2.1 Identical Recommendations I International Standards
2.2 Paired Recommendations I International Standards equivalent
2
in technical content .
2
.................................
2.3 Additional references
........................................... 2
3 Definitions
.........................
3.1 Basic reference model definitions 3
3
3.2 Service convention deftitions .
3
3.3 Management framework defmitions .
3.4 Systems management overview deftitions . 3
.......... 3
3.5 Common management information service definitions
....................... 3
3.6 OS1 conformance testing definitions
3
3.7 AdditionaI definitions .
4
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
................
Model for the event report management function 5
7.1General. 5
.........................
7.2 Event report management model 5
6
......................................
Generic definitions
6
....................................
8.1 Managed objects
11
...........................
8.2 Imported generic defnitions
11
Servicedefinitions .
11
9.1 Introduction .
...................... 11
9.2 Initiation of event report forwarding
....................
9.3 Termirration of event report forwarding 12
9.4 Event forwarding discriminator modification, suspension and
12
resumption .
12
..........
9.5 Retrieval of event fonvarding discriminator attributes
8 ISO/1 EC 1993
All rights reserved. No part of this publication may be reproduced or utilized in any form or
by any means, electronie or mechanical, including photocopying and microfilm, without per-
mission in writing from the publisher.
lSO/IEC Copyright Office l Case Postale 56 l CH-l 211 Geneve 20 l Switzerland
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
10 Functional uni& . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
11 Protocol . 13
13
11.1 Elements of procedure .
11.2 Abstract Syntax . 13
113 . Negotiationoffunctionalunits •.~~.~~~~.~~~~~~~.~ l 14
12 Relationship with other fimctions . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
14
13 Conformance .
15
13 1 General conformance class requirements .
13.2 Dependent conformance ciass requirements . 15
13’3 . Confannance to support managed Object definitions . 15
16
Annex A Example vahe notation for the discriminator construct . . . . . .
17
Annex B Event forwarding using local mechanism . . . . . . . . . . . . . . .
Annex C Considerations for System implementation conformance
18
Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . .
111

---------------------- Page: 3 ----------------------
Foreword
ISO (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized System for worldwide standardiz-
ation. 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 10164-5 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, in collaboration with the CCI‘IT. The identical
text is published as CCITT Recommendation X.734.
lSO/IEC 10164 consists of the following Parts, under the general title Information
technology - Open Systems Interconnection - Systems Management:
- Part 1 : Object Management Function
- Part 2 : State Management Function
- Part 3 : Attributes for representing relationships
- Part 4 : Alarm reporting function
- Part 5 : Event report managementfunction
- Part 6: Log control function
- Part 7: Security alarm reporting function
- Part 8: Security audit trail function
- Part 9: Objects and attributes for access control
- Part 10: Accounting meterfunction
- Part 11: Workload monitoring function
- Part 12: Test management function
- Part 13: Summarization function
- Part 14: Confidence and diagnostic test categories

---------------------- Page: 4 ----------------------
Introduction
ISOAEC 10164 is a multipart Standard developed according to ISO 7498 and
ISO/IEC 7498-4. ISO/IEC 10164 is related to the following International Standards:
Open Systems Interconnection -
ISO/IEC 9595: 1990, Information technology -
Common management information Service definition;
ISO/IEC 9596: 1990, Information technology - Open Systems Interconnection -
Common management information protocol;
technology - Open Systems Interconnection -
ISO/IEC 10040: 1992, Information
Systems management overview;
ISO/IEC 10165: 1992, Information technology - Open Systems Interconnection -
Structure of management information.

---------------------- Page: 5 ----------------------
This page intentionally left blank

---------------------- Page: 6 ----------------------
ISO/DEC 10164-5 : 1993 (E)
INTERNATIONAL STANDARD
CCITI’ RECOMMENDATION
INFORlWATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION -
SYSTEMS MANAGEMENT: EVENT REPORT IMANAGEMENT FUNCTION
1
Scope
This Recommendation I International Standard defines a Systems Management Function which may be used by an
application process in a centralized or decentralized management environment to interact for the purpose of Systems
management, as defined by CCITT Rec. X.700 I ISO/IEC 74984. This Recommendation I International Standard
defines the Event report management function and consists of Services and two functional units. This function is
positioned in the application layer of CCITI’ Rec. X.200 I ISO 7498 and is defined according to the model provided by
ISO/IEC 9545. The role of Systems management functions is described in CCITI’ Rec. X.701 I ISO/IEC 10040.
This Recommendation I International Standard
-
establishes user requirements for the event report management function;
-
establishes models that relate the Services provided by the function to User requirements;
-
defines the Services provided by the function;
-
specifies the protocol that is necessary in Order to provide the Services;
-
defmes the relationship between the Services and SM1 operations and notifkations;
-
defines relationships with other Systems management functions;
-
specifies conformance requirements.
This Recommendation I International Standard does not
-
define the nature of any implementation intended to provide the event report management function;
-
specify the manner in which management is accomplished by the user of the event report management
function;
-
defme the nature of any interactions which result in the use of the event report management function;
-
specify the Services necessary for the establishment, normal and abnormal release of a management
association;
-
specify the authorization requirements for the use of the event report management function or for any
associated activity;
- define the managed objects related to the management of particular protocol machines.
2 Normative references
The following CCI’IT Recommendations and International Standards contain provisions which, through reference in
this text, constitute provisions of this Recommendation I International Standard. At the time of publication, the editions
indicated were valid. All Recommendations and Standards are subject to revision, and Parties to agreements based on
this Recommendation I 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. ‘Ihe CCITI’ Secretariat maintains a list of the currently valid CCITT Recommendations.
21 0 Identical Recommendations I International Standards
-
CCITT Recommendation X.701 (1992) l ISO/IEC 10040:1992, Infomzation technology - Open Systems
Interconnection - Systems management overview.
CCITT Rec. X.734 (1992 E) 1

---------------------- Page: 7 ----------------------
ISO/lEC 10164-5 : 1993 (E)
-
CCITT Recommendation X.721 (1992) I ISOLIEC 10165-2:1992, Information technology - Open
Structure of management information - Part 2: Definition of manugement
Systems Interconnection -
Information.
-
CCITT Recommendation X.730 (1992) I ISO/IEC 10164-1:1993, Information technology - Open
Systems Interconnection - Systems Management - Part 1: Object management finction.
- CCI’IT Recommendation X.731 (1992) I ISO/IEC 10164-2:1993, Information technology - Open
Systems Interconnection - Systems Management - Part 2: State managementfunction.
22 l Paired.Recommendations I International Standards equivalent in technical content
- CCI’IT Recommendation X.200 (1988), Reference Model of Open Systems Interconnection for CCITT
Applications.
Open Systems Interconnection - Basic Reference
ISO 7498:1984, Information processing systems -
Model.
- CCITT Recommendation X.210 (1988), Open Systems Interconnection Layer Service Definition
Conventions.
ISO/TR 8509: 1987, Information processing systems - Open Systems Interconnection - Service
conventions.
(1988), Management Framework Definition for Open Systems
- CCITT Recommendation X.700
Interconnection (OSI) for CCITTApplications.
ISO/IEC 7498-4: 1989, Information processing systems - Open Systems Interconnection - Basic
Reference Model - Part 4: Managementframework.
- CCITT Recommendation X.208 (1988), Specification of Abstract Syntax Notation One (ASN. 1). X.208,
ITU, Geneva 1989.
ISO/IEC 8824: 1990, Information technology - Open Systems Interconnection - Specification of Abstract
Syntax Notation One (ASNJ).
-
CCITT Recommendation X.209 (1988), Specification of Basic Encoding Rules for Abstract Syntax
Notation One(ASN.I).
ISO/IEC 8825: 1990, Information technology - Open Systems Interconnection - Specification of Basic
Encoding Rules for Abstract Syntax Notation One (ASN.1).
- CCITI’ Recommendation X.710 (1992), Common Management Information Service Definition for
CCITTApplications.
ISO/IJZC 9595: 199 1, Information technology - Open Systems Interconnection - Common management
information service definition.
-
CCITT Recommendation X.290 (1992), OSI Conformance Testing Methodology and Framework for
protocol Recommendations for CCITT applications - General Concepts.
ISO/IFC 9646-1: 199 1, Information technology - Open Systems Interconnection - Conformance testing
methodology andfiamework - Part 1: General concepts.
Additional references
23 l
-
ISOIIEC 9545: 1989, Information technology -
Open Systems Interconnection - Application Layer
structure.
3 Definitions
For the purposes of this Recommendation I International Standard, the following definitions apply.
2
CCITT Rec. X.734 (1992 E)

---------------------- Page: 8 ----------------------
Iso/IEc 10164-5 : 1993 (E)
31 l Basic reference model definitions
This Recommendation I International Standard makes use of the following terms defined in CCITT Rec. X.200 I
ISO 7498.
open System;
a)
b) Systems management.
32 l Service convention definitions
This Recommendation I International Standard makes use of the following tem defined in CCITI’ Rec. X.210 I
ISO/TR 8509.
primitive
33 l Management framework definitions
This Recommendation I International Standard makes use of the following terms as defined in CCITI’ Rec. X.700 I
ISO/IEC 7498-4:
a) Management information;
b) Managed Object;
Systems-management-application-entity.
C)
34 0 Systems management overview definitions
This Recommendation I International Standard makes use of the following terms defined in CCITT Rec. X.701 I
ISOAEC 10040:
agent role;
a)
b) dependent conformance;
c) general conformance;
d) management support Object;
manager role;
d
notifkation;
f)
g) Systems management functional unit;
h) Systems management Operation.
35 l Common management information Service definitions
This Recommendation I International Standard makes use of the following terms defmed in CCITT Rec. X. 710 1
ISOAEC 9595:
attribute;
a)
b) common management information Services;
common management Information Service element.
C)
36 . OS1 conformance testing definitions
This Recommendation I International Standard makes use of the following term defmed in CCITI’ Rec. X.290 I
ISO/IEC 9646- 1.
System conformance Statement
. Additional definitions
37
The following terms are defined in this Recommendation I International Standard.
3.7.1 discriminator: A management support Object that alIows a System to select management operations and
event reports relating to other managed objects.
CCITI’ Rec. X.734 (1992 E) 3

---------------------- Page: 9 ----------------------
ISO/IEC 10164-5 : 1993 (E)
3.7.2 discriminator input Object: A conceptual Object whose attributes are Parameters of either an Operation or a
notification.
Discriminator input objects are defined for the purpose of discrimination and instances of discriminator input objects
exist only for the duration of discrimination. Discriminator input Object attributes tan be used for discrimination, if and
only if they have an Object identifier. Attributes that have no matthing rules defmed for them tan only be checked for
presence.
3.7.3 event forwarding discriminator: A discriminator that acts on potential event reports.
event report management function: A function, including the definition of a management support Object
3.7.4
class, that allows, a manager to control the transmission of event reports from managed objects independent of the
definition of the managed objects.
3.7.5 potential event report: A type of discriminator input Object that is defined for the purpose of event
forwarding discrimination.
A potential event report consists of all the information required to be forwarded in the event report. The information is
derived from the information contained in the notification and information derived from IocaI processing of the
notification, if any.
4 Abbreviations
ASN.l Abstract Syntax Notation One
CMIS Common management information Service
CMISE Common management information Service element
EFD Event forwarding discriminator
ERF Event reporting function
Id Identifier
MAPDU Management application protocol data unit
PDU Protocol data unit
SMAE Systems management application entity
SMFU Systems management functional unit
SM1 Structure of management information
5
Conventions
This Recommendation I International Standard defines Services for the event report management function following
the descriptive conventions defined in CCI’IT Rec. X.210 l ISO/TR 8509.
6 Requirements
The requirements to be satisfied are
a) the definition of a flexible event report control Service which will allow Systems to select which event
reports are to be sent to particular managing Systems;
b) the specification of the destinations (e.g. the identities of managing Systems) to which event reports are
to be sent;
c) the specification of a mechanism to control the forwarding of event reports, for example, by suspending
and resuming their forwarding;
d) the ability for an extemal managing System to modify the conditions used in the reporting of events;
the ability to designate a backup location to which event reports tan be sent if the primary location is
e)
not available.
CCITT Rec. X.734 (1992 E)
4

---------------------- Page: 10 ----------------------
ISOAEC 10164-5 : 1993 (E)
7 Model for the event report management function
71 0 General
The functional requirements noted above, relating to the behaviour of Systems, tan be reduced to a basic requirement
on the behaviour of a System. This is the ability to specify conditions to be satisfied by a potential event report emitted
by a particular managed Object in Order to be sent to specified destinations.
72 Event report management model
l
The event report management model describes the conceptual components that provide for remote event reporting and
local processing of potential event reports. The model also describes the control messages, event reporting messages
and retrieval messages.
The conceptual event pre-processing function receives local notifkations and forms the potential event reports.
Conceptually, these potential event reports are distributed to all event forwarding discriminators that are contained
within the local open System. A potential event report is perceived as a discriminator input Object for the purposes of
discrimination by the event forwarding discriminators only and is not visible from outside the 104 System.
The event forwarding discriminator is used to determine which event reports are to be forwarded to a particular
destination during specified time periods. It may also be used to specify the mode (confinned or non-confirmed) for
forwarding events. Esch event forwarding discriminator may contain a scheduling capability determining the intervals
during which event reports will be selected for forwarding. Esch event forwarding discriminator contains a
discriminator construct which specifies the characteristics a potential event report must satisfy in Order to be
forwarded. Event reports that have been selected arc forwarded to the destination as soon as possible.
The event forwarding discriminator is itself a managed Object and tan therefore emit notifications. These notifications
are processed as potential event reports by all event forwarding discriminators including the one that generated the
notification.
Figure is a schematic representation of the components involved in generating, processing and reporting events.
b
Event reports
TIS00260-9;
Responses + I Control
Figure 1 - Event report management model
CCI’IT Rec. X.734 (1992 E) 5

---------------------- Page: 11 ----------------------
ISOAEC 10164-5 : 1993 (E)
7.2.1 Event reporting management function
Event reporting management allows an open System to establish and control the discrimination and the forwarding of
event reports to other open Systems. Event reports are generated as a result of the notification that an event has
occurred, e.g. a threshold Violation or a Change in configuration Status. The event forwarding management function
provides the capability of identifying the destinations to which selected event reports are to be sent. Event reporting
management provides the means by which discrimination and forwarding tan be initiated, terminated, suspended, or
resumed and through which the attributes of the event forwarding discriminator tan be read and modified.
The event reporting management function provides the capability for setting up a long term event reporting
relationship between two open Systems. WhiIe the event forwarding discriminator is in the unlocked state, the
reporting open System forwards event reports to the specified destination given that the operational state is enabled and
any schedule is not “Off-duty”.
Event reporting management comprises the following:
-
initiation of event forwarding;
-
termination of event forwarding;
-
Suspension of event forwarding;
resumption of event forwarding;
modification of event forwarding conditions;
retrieval of event forwarding conditions.
8 Generic defhitions
81 .
Managed objects
This Recommendation I International Standard provides generic definitions of managed objects, attributes and
packages associated with the discriminator and the event forwarding discriminator.
The discriminator
S.l.1
The basic superclass is the discriminator Object class. The discriminator may be specialized into subclasses to specify
management support Object classes that allow the control of various System management functions. The discriminator
provides for specification of conditions that shall be satisfied Prior to ahowing the management Operation or
notification associated with the discriminator input Object to proceed. Some of the conditions arc common to all
subclasses of the discriminator; others are unique to the specific discriminator subclass.
The conditions specified by the discriminator are
-
identification of a scheduling packages that determine when discriminator processing will occur;
-
the criteria for discrimination;
the administrative and operational state of the discriminator;
-
those specific to a particular discriminator Object subclass.
8.1.1.1 Management of discriminators
The discriminator is a managed Object that allows a managing System to exercise control over the management
operations that may be accepted and the event reports that may be forwarded, by a managed System. Discriminators
tan, therefore, be created, deleted, read and modified. In addition, the activity of discriminators tan be suspended and
resumed by means of manipulating their administrative states.
When a discriminator is created, the discriminator
shall generate an Object creation notification. This notification shall
be processed by the newly created discriminator.
Esch discriminator has an operational state and an administrative state. The operational states defined for the
discriminator are those.defined in CCITT Rec. X.73 1 I ISO/IEC 10164-2. The administrative state attribute defined for
the discriminator is a subset of those defined in CCITT Rec. X.731 I ISO/IEC 10164-2. A Change in the operational
state shall be reported using the state Change notification. This notification shall be processed by the affected
discriminator before it enters the disabled state or after it enters the enabled state, as appropriate.
6 CCITT Rec. X.734 (1992 E)

---------------------- Page: 12 ----------------------
ISO/IIEC 10164-5 : 1993 (E)
The operational states defined for the discriminator are enabled and disabled. For the discriminator, the enabled state
is the state in which the discriminator tan process discriminator input objects (unless administratively prohibited from
doing so or if any schedule is “Off-duty”); in the disabled state the discriminator does not process any discriminator
input objects.
The administrative states defined for the discriminator are locked and unlocke& State changes in the administrative
state of the discriminator are the result of intervention by a managing System or local administrative activity. The
precise semantics of these states are defined as part of the class defmition of subclasses of discriminator.
The managing System may leck or unleck the discriminator. Whenever the administrative state of the discriminator
changes, the discriminator shalI generate a notification. When the state is changed fiom unlocked to locked and the
discriminator is in the enabled state, the discriminator shall not Change state until a state Change notification indicating
the state Change has been processed by the discriminator. When the discriminator state is changed from locked to
unlocked, the discriminator shall generate a notification indicating the state Change immediately after having entered
the unlocked state. The state Change from unlocked to locked is assumed to occur instantaneously and without
disrupting the processing of a current potential event report.
When the discriminator is deleted, the discriminator shall generate an Object deletion notification and process that
notification Prior to deletion. If the discriminator is in the unlocked and enabled states it shall process the discriminator
input Object indicating the Object deletion Prior to its deletion.
In addition to manipulating the state of a discriminator, a manager tan Change the time during which a discriminator
will be available and Change the conditions under which tests on a discriminator input Object tan evaluate to TRUE.
These changes are defined to occur in such a way so as not to impact a discriminator input Object that is currently
being processed. The availability Status shall be present when a manager tan Change the time during which the
discriminator is available. The availability Status attribute value for the discriminator is a subset of those defmed in
CCITT Rec. X.73 1 I ISO/IEC 10164-1. If discrimination is available and the scheduling attributes are changed so that
the current time is not within tbe “available” time range, the availability Status becomes “Off-duty”. This notification
shall be processed by the affected event forwarding discriminator before it enters the off-duty Status. No state Change
notifications are generated for this attribute.
Changes to values of attributes other than administrative state, operational state and, if present, availability status, shall
be reported using the attribute value Change notification.
Open Systems may be configured with a mechanism for forwarding events when no manageable event forwarding
discriminator is available (see Annex B). This mechanism is outside the scope of this specification.
8.1.1.2 Normai Operation of discriminators
A discriminator contains a discriminator construct that is a filtering mechanism which acts on attributes of
discriminator input objects. A discriminator construct is a set of one or more assertions about the presence or values of
attributes. If the discriminator construct involves more than one assertion, the assertions are grouped together using
logical Operators.
The discriminator construct tan specify tests for equality and inequality conditions of attributes, test for the presence
of attributes and the negation of any of these conditions. Multiple conditions may be combined by means of “AND” or
“OR” Operators. When an attribute for which an attribute value assertion is present in the discriminator construct, is
absent in a discriminator input Object to be tested, the result of the test On that attribute value assertion shall be
evaluated as FALSE.
An empty discriminator construct will evaluate to TRUE for any set of discriminator input Object attributes. For the
discriminator, if the discriminator construct evaluates to TRUE, the discriminator is in the unlocked and enabled
states, and the availability Status, if present, is not “Off-duty”,
then the discriminator input Object Passes the
discriminator and will be processed further (the processing to be performed depends on the precise semantics of the
discriminator subclass).
If the discriminator is in the locked or disabled states or has the “Off-duty” availability status (if present), then
discriminator input objects will not be processed by that discrirninator. If the discriminator is created such that a
manager tan not Change the time when it is available, then the discriminator is assumed to be always available.
8.1.1.3 Discriminator attributes
The following mandatory attributes are defined for the discriminator Object class.
CCI’IT Rec. X.734 (1992 E) 7

---------------------- Page: 13 ----------------------
ISO/IEC 10164-5 : 1993 (E)
8.L1.3.1 Discriminator Id
This attribute is used to uniquely identify the instance of a discriminator.
8.1.1.3.2 Discriminator construct
This attribute specifies tests on the information that is to be processed by the discriminator.
8.1.1.3.3 Administrative state
This attribute represents the administrative state of the discriminator. The following administrative states are defmed:
unlocked - processing of the information by the discriminator is permitted by a managing System;
a)
locked - processing of the information by the discriminator is prohibited by a managing System.
b)
8.1.1.3.4 Operational state
This attribute represents the operational capability of the discriminator to Perform its function. The following
operational states are defined:
enabled - the discriminator is operational;
a)
b) disabled - the discriminator is inoperable.
8.1.1.4 Discriminator notifications
The following mandatory notifications arc defined for the discriminator Object class:
state Change;
a)
b) attribute value Change;
Object creation;
C)
d) Object deletion.
8.1.1.5 Scheduling packages
To accommodate various levels of complexity in scheduling event reporting act
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.