Information technology — Open Systems Interconnection — Systems Management: Alarm reporting function — Part 4: — Amendment 1: Implementation conformance statement proformas

Contains tables, which document the mandatory and optional management information specific to the Alarm Reporting Function. This amendment will be used by Profile specifiers, for example, those developing International Standardized Profiles (ISPs), to specify an explicit subset of capability, which will afford interoperability between implementations.

Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Gestion-systèmes: Fonction de signalisation des alarmes — Partie 4: — Amendement 1: Formulaires de déclaration de conformité d'instance

General Information

Status
Published
Publication Date
26-Dec-1995
Current Stage
6060 - International Standard published
Completion Date
27-Dec-1995
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 10164-4:1992/Amd 1:1995 - Implementation conformance statement proformas
English language
29 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO/IEC 10164-4:1992/Amd 1:1995 - Formulaires de déclaration de conformité d'instance
French language
29 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO/IEC 10164-4:1992/Amd 1:1995 - Formulaires de déclaration de conformité d'instance
French language
29 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ISO/IEC
INTERNATIONAL
10164-4
STANDARD
First edition
1992-I 2-l 5
AMENDMENT 1
1995-I 2-l 5
Information technology - Open Systems
- Systems Management:
Interconnection
Alarm reporting function
AMENDMENT 1: Implementation
conformance statement proformas
Technologies de I ‘information - In terconnexion de s ys t&mes ouverts
(03) - Gestion-systgmes: Fonction de rapport d’alarme
AMENDEMENT I: Proformes de dklaration de conformit de mise
en w.wre
Reference number
lSO/IEC 10164-4:1992/Amd.l :I 995(E)

---------------------- Page: 1 ----------------------
ISO/IEC 10164-4:1992/Amd.l:1995(E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form
the specialized system for worldwide standardization. National bodies that are members of IS0 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. IS0 and IEC technical committees collaborate in fields of mutual interest.
Other international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the
work.
In the field of information technology, IS0 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.
Amendment 1 to International Standard ISO/IEC 10164-4:1992 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 21, Open systems interconnection, data management and
open distributed processing, in collaboration with ITU-T. The identical text is published as ITU-T Rec. X733/Amd. 1.
0 ISO/IEC 1995
All rights reserved. Unless otherwise specified, no part of this publication may be repro-
duced or utilized in any form or by any means, electronic or mechanical, including photo-
copying and microfilm, without permission in writing from the publisher.
ISO/IEC Copyright Office l Case Postale 56 l CH-1211 Gen&ve 20 l Switzerland
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
@ ISO/IEC ISO/IEC 10164-4: 1992/Amd.l: 1995(E)
Introduction
This amendment includes tables, which document the mandatory and optional management information specific to the
Alarm Reporting Function. This amendment will be used by Profile specifiers, for example those developing
International Standardized Profiles (ISPs), to specify an explicit subset of capability, which will afford interoperability
between implementations. The table also include a column for equipment vendors to state the capability of their products
in terms of the Profiles or base specification. The table structures comply with the Guidelines for Implementation
Conformance Statement Proformas specified in ITU-T Recommendation X.724 I ISO/IEC 101656.
. . .
111

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

---------------------- Page: 4 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l : 1995 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION -
SYSTEMS MANAGEMENT: ALARM REPORTING FUNCTION
AMENDMENT 1
(to ITU-T Rec. X.733 I ISO/IEC 10164-4)
Implementation conformance statement proformas
Add the following footnote to thefirst list item in 2.1:
1)
“0 As amended by ITU-T Rec. X.70Kor.2 I ISO/IEC 10040Kor.2”.
Add the following reference to 2.1:
2)
64
-
ITU-T Recommendation X.724 (1993) I ISO/IEC 101656: 1994, Information technology - Open Systems
Interconnection - Structure of management information: Requirements and guidelines for implementation
conformance statement proformas associated with OSI management.”
Add the following references to 2.2:
3)
66
- CCITT Recommendation X.291 (1992), OSI conformance testing methodology and framework for
protocol Recommendations for CCITT applications - Abstract test suite specification.
ISO/IEC 9646-2: 199 1, Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 2: Abstract test suite specification.
-
ITU-T Recommendation X.2963), OSI conformance testing methodology and framework for protocol
Recommendations for ITU-T applications - Implementation conformance statements.
ISOIIEC 9646-73>, Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation conformance statements.”
And then add the following footnote:
3)
Presently at the stage of draft.
Apply the following changes to 3.4:
4)
Delete items c) and d).
Relabel item e) as c) and insert the following new items:
“e) managed object conformance statement (MOCS);
f) management information conformance statement (MICS);”
Relabel items h) through j) as j) through 1) and insert the following new items:
“h) MICS proforma;
MOCS proforma;”
0
Apply the following change to 3.6:
3
Replace “system conformance statement” with the following:
“a) PICS proforma;
b) protocol implementation conformance statement;
system conformance statement.”
C>
Renumber 3.7 as 3.8 and insert the following new subclause:
6)
ITU-T Rec. X.733 (1992)/Amd.l(1995 E) 1

---------------------- Page: 5 ----------------------
ISO/IE@ 10164-4 : 1992/Amd.l : 1995 (E)
37 . “Implementation conformance statement proforma definitions
This Recommendation I International Standard makes use of the following terms defined in ITU-T Rec. X.724 I
ISO/IEC 10165-6:
Managed Relationship Conformance Statement (MRCS);
a)
Management Conformance Summary (MCS);
b)
c) Management Information Definition Statement (MIDS) proforma;
d) MCS proforma;
e) MRCS proforma.”
Add the following abbreviations to clause 4:
7)
Implementation Conformance Statement
“ICS
MCS Management Conformance Summary
MICS Management Information Conformance Statement
MIDS Management Information Definition Statement
MOCS Managed Object Conformance Statement
MRCS Managed Relationship Conformance Statement
Protocol Implementation Conformance Statement”
PIGS
Replace clause 13 with the following:
8)
66
13 Conformance
Implementations claiming to conform to this Recommendation I International Standard shall comply with the
conformance requirements as defined in the following subclauses.
13.1 Static conformance
The implementation shall conform to the requirements of th is Recommendation I International Standard in the manager
role, the agent role, or both roles. A claim of conformance to at least one role shall be made in Table A. 1.
If a claim of conformance is made for support in the manager role, the implementation shall support at least one of the
notifications or at least one of the management operations specified in this Recommendation I International Standard.
The conformance requirements in the manager role for those management operations and notifications are identified in
Table A.3 and further tables referenced by Annex A.
If a claim of conformance is made for support in the agent role, the implementation shall support at least one of the
notifications specified in this Recommendation I International Standard. The conformance requirements in the agent role
are identified in Table A.4 and further tables referenced by Annex A.
The implementation shall support the transfer syntax derived from the encoding rules specified in CCITT Rec. X.209 I
ISO/IEC 8825 named {joint-iso-ccitt asnl(1) basicEncoding( 1)) for the abstract data types referenced by the definitions
for which support is claimed.
NOTE - Prior to the publication of this amendment, this Recommendation I International Standard identified general and
dependent conformance classes. A claim of conformance similar to general conformance class can be made by stating support in the
manager role, the agent role, or both roles, for the alarm reporting functional unit in Table A.2. A claim of conformance similar to
dependent conformance class can be made by stating support for at least one of the items in Tables A.3 or A.4
13.2 Dynamic conformance
Implementations claiming to conform to this Recommendation I International Standard shall support the elements of
procedure and definitions of semantics corresponding to the definitions for which support is claimed.
13.3 Management implementation conformance statement requirements
Any MCS proforma, MICS proforma, and MOCS proforma which conforms to this Recommendation I International
Standard shall be technically identical to the proformas specified in Annexes A, B and C preserving table numbering and
the index numbers of items, and differing only in pagination and page headers.
2 ITU-T Rec. X.733 (1992)/Amd.l(1995 E)

---------------------- Page: 6 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l : 1995 (E)
The supplier of an implementation which is claimed to conform to this Recommendation I International Standard shall
complete a copy of the Management Conformance Summary (MCS) provided in Annex A as part of the conformance
requirements together with any other ICS proformas referenced as applicable from that MCS. An ICS which conforms to
this Recommendation I International Standard shall:
-
describe an implementation which conforms to this Recommendation I International Standard;
-
have been completed in accordance with the instructions for completion given in ITU-T Rec. X.724 I
ISO/IEC 10165-6;
-
include the information necessary to uniquely identify both the supplier and the implementation.
Claims of conformance to the management information defined in this Recommendation I International Standard in
managed object classes defined elsewhere shall include the requirements of the MIDS proforma in the MOCS for the
managed object class.”
ITU-T Rec. X.733 (1992)/Amd.l(1995 E)
3

---------------------- Page: 7 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l : 1995 (E)
RelabeL Annex A as Annex E and insert the following annexes:
9)
Annex A
MCS proforma4)
(This annex forms an integral part of this Recommendation I International Standard)
A.1 Introduction
A.l.1 Purpose and structure
The Management Conformance Summary (MCS) is a statement by a supplier that identifies an implementation and
provides information on whether the implementation claims conformance to any of the listed set of documents that
specify conformance requirements to OSI management.
The MCS proforma is a document in the form of a questionnaire that completed by the supplier of an
implementation becomes the MCS.
A.l.2 Instructions for completing the MCS proforma to produce a MCS
The supplier of the implementation shall enter an explicit statement in each of the boxes provided. Specific instruction is
provided in the text which precedes each table.
A.l.3 Symbols, abbreviations and terms
For all annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISO/IEC 9646-2 and ITU-T Rec. X.296 I ISO/IEC 9646-7, are used for the Status column:
m Mandatory;
0 Optional;
C Conditional;
X Prohibited;
-
Not applicable or out of scope.
NOTES
‘c’, ‘m’, and ‘0’ are prefixed by “c:” when nested under a conditional or optional item of the same table;
1
2 ‘0’ may be suffixed by “.N” (where N is a unique number) for selectable options among a set of status values. Support
of at least one of the choices (from the items with the same value of N) is required.
For all annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISO/IEC 9646-2 and ITU-T Rec. X.296 I ISO/IEC 9646-7, are used for the Support column:
Y Implemented;
N Not implemented;
-
No answer required;
The item is ignored (i.e. processed syntactically but not semantically).
II3
A.l.4 Table format
Some of the tables in this Recommendation I International Standard have been split because the information is too wide
to fit on the page. Where this occurs, the index number of the first block of columns are the index numbers of the
corresponding rows of the remaining blocks of columns. A complete table reconstructed from the constituent parts
should have the following layout:
Index First block of columns Second block of columns Etc.
4, Users of this Recommendation I International Standard may freely reproduce the MCS proforma in this annex so that it can be
used for its intended purpose, and may further publish the completed MCS. Instructions for the MCS proforma are specified in
ITU-T Rec. X.724 I ISO/IEC 10165-6.
4 IT&T Rec. X.733 (1992)/Amd.l(1995 E)

---------------------- Page: 8 ----------------------
ISOAEC 10164-4 : 1992/Amd.l : 1995 (E)
In this Recommendation I International Standard the constituent parts of the table appear consecutively, starting with the
first block of columns.
When a table with sub-rows is too wide to fit on a page, the continuation table(s) have been constructed with index
numbers identical to the index numbers in the corresponding rows of the first table, and with sub-index numbers
corresponding to the sub-rows within each indexed row. For example, if Table X.1 has 2 rows and the continuation of
Table X.1 has 2 sub-rows for each row, the tables are presented as follows:
Table X.1 - Title
SUPP0I-t I
I
Index A B C D E F G
1 a b -
2 a b -
Table X.1 (continued) - Title
2.2
h i
I 9
A complete table reconstructed from the constituent parts should have the following layout:
Sub-index H I 9 K L
Index A B C D E F G
h i
1 a b - 1.1
ii
I.2 h i
j
2 a b - 2.9 h i
ii
h i
2.2
9
References made to cells within tables shall be interpreted as references within reconstructed tables. In the examples,
above, the reference X.l/ld corresponds to the blank cell in column G for row with Index 1, and X.l/l.2b corresponds to
the blank cell in column L for row with Sub-index 1.2.
A.2 Identification of the implementation
A.2.1
Date of statement
The supplier of the implementation shall enter the date of this statement in the box below. Use the format DD-MM-
YYYY.
Date of statement
I
I
ITU-T Rec. X.733 (1992)/Amd.l(1995 E)
5

---------------------- Page: 9 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l : 1995 (E)
A.2.2 Identification of the implementation
The supplier of the implementation shall enter information necessary to uniquely identify the implementation and the
system(s) in which it may reside, in the box below.
A.2.3 Contact
The supplier of the implementation shall provide information on whom to contact if there are any queries concerning the
content of the MCS or any referenced conformance statement, in the box below.
Identification of the Recommendations I International Standards in which the management
A.3
information is defined
The supplier of the implementation shall enter the title, reference number and date of the publication of the
Recommendations I International Standards which specify the management information to which conformance is
claimed, in the box below.
Recommendations I International Standards to which conformance is claimed
I I
A.3.1 Technical corrigenda implemented
The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify
the identified Recommendations I International Standards, in the box below.
A.3.2 Amendments implemented
The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the
identified Recommendations I International Standards, in the box below.
ITU-T Rec. X.733 (1992)/Amd.l(1995 E)
6

---------------------- Page: 10 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l: 1995 (E)
A.4 Management conformance summary
The supplier of the implementation shall state the capabilities and features supported and provide a summary of
conformance claims to Recommendations I International Standards using the tables in this annex.
The supplier of the implementation shall specify the roles that are supported, in Table A. 1.
Table A.1 - Roles
Index Roles supported 1 Status 1 Support 1 Additional information
I I I
1 1 --IManager role support 0.1
I 1 I 7
2 Agent role support 0.1
I I I I I I
The supplier of the implementation shall specify support for the systems management functional unit, in Table A.2.
Table A.2 - Systems management functional unit
Manager Agent
Index Systems management functional unit name Status Support Status Support Additional information
1 alarm reporting functional unit Cl c2
cl: if Al/la then o else-.
c2: if A. 1/2a then o else -.
The supplier of the implementation shall specify support for management information in the manager role, in Table A.3.
Table A.3 - Manager role minimum conformance requirement
Index Item Status support Additional information
c3
1 Communications alarm notification
2 Environmental alarm notification c3
c3
3 Equipment alarm notification
c3
4 Processing error alarm notification
c3
5 Quality of service alarm notification
C4
‘6 Operations on managed objects
c3: if A.Z/l a then m else (if A. l/l a then 0.2 else -).
c4: if A.Z/l a then o else (if A. l/l a then 0.2 else -).
NOTE - Manager role minimum conformance requires support for at least one of the items identified in this table. Support for
the functional unit identified in Table A.2 mandates support for some of those items. Conditions c3 and c4 express both of these
requirements
ITU-T Rec. X.733 (1992)/Amd.l(1995 E)

---------------------- Page: 11 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l : 1995 (E)
The supplier of the implementation shall specify support for management information in the agent role, in Table A.4.
Table A.4 - Agent role minimum conformance requirement
Status support Table reference Additional information
Index Item
1 Communications alarm notification C5
2 Environmental alarm notification C5
C5
3 Equipment alarm notification
C5
4 Processing error alarm notification
5 Quality of service alarm notification c5
-
6 Alarm record managed object class c6
c5: if A.Z/l b then m else (if A. 1/2a then 0.3 else -).
c6: if A. 1/2a and A.5/1 a then m else --*
NOTES
1 Condition c6 makes it mandatory, if logging is supported, to support the event log records associated with the notifications
supported.
2 The Table reference column in this table is the notification reference of the MOCS supplied by the supplier of the managed
object which claims to import the notification from this Recommendation I International Standard.
Table A.5 - Logging of event records
I I
NOTE 1 - Conformance to this Recommendation I International Standard does not require conformance to CCITI’
Rec. X.735 1 ISO/IEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the Recommendations
I International Standards summarized in Tables A.6 to A.9. For each Recommendation I International Standard that the
supplier of the implementation claims conformance to, the corresponding conformance statement(s) shall be completed,
or referenced by, the MCS. The supplier of the implementation shall complete the Support, Table numbers and
Additional information columns.
In Tables A.6 to A.9, the Status column is used to indicate whether the supplier of the implementation is required to
complete the referenced tables or referenced items. Conformance requirements are as specified in the referenced tables
or referenced items and are not changed by the value of the MCS Status column. Similarly, the Support column is used
by the supplier of the implementation to indicate completion of the referenced tables or referenced items.
Table A.6 - PICS support summary
Table
Table
Identification of the
Description Constraints status support numbers Additional
Index numbers
document that includes of pIcs
information
and values
of PIGS
the PICS proforma
proforma
OBJECT m
1 CCITT Rec. X.730 I Annex E SM application context
all tables IDENTIFIER
ISO/IEC 10164- 1
NOTE 2 - Conformance to the MAPDUs defined in this Recommendation I International Standard can be claimed by
completing the corresponding tables in the MICS and MOCS annexes of the referenced Recommendations I International Standards.
8 ITU-T Rec. X.733 (1992)/Amd.l(1995 E)

---------------------- Page: 12 ----------------------
ISO/IEC 10164-4 : 199WAmd.l: 1995 (E)
Table A.7 - MOCS support summary
Table
Identification of the Table
Additional
Description Constraints
Index numbers
Status SuPPo’ numbers
document that includes of MOCS
information
and values
of MOCS
the MOCS proforma
proforma
alarmRecord
1
I I I - Ic81 I I I
c8: if A.4/6a then m else -.
I
I
Table A.8 - MRCS support summary
Table
Table
Identification of the
Description Constraints Additional
Index numbers
Status SuPPo’ numbers
document that includes of MRCS
information
and values
of MRCS
the MRCS proforma
proforma
logRecord-log name - c9
1 CCI’IT Rec. X.735 I Item D.111
ISO/IEC 10164-6 binding
c9: if A.5/la then o else -.
Table A.9 - MICS support summary
Table
Table
Identification of the
numbers Description Constraints Additional
Index
Status SuPPo’ numbers
document that includes of MICS
and values information
of MICS
the MICS proforma
proforma
-
CCITI’ Rec. X.733 I Table B. 1 notifications cl0
1
ISO/IEC 10164-4
-
2 CCITI’ Rec. X.733 I Tables B.2 management cl1
ISO/IEC 10164-4 , and B.3 operations
I I I I I I I I I
~10: if A.3/1a or A.3/2a or A.3/3a or A.3/4a or A.3/5a then m else -.
cl 1: if A.3/6a then m else -.
ITU-T Rec. X.733 (1992)/Amd.l(1995 E) 9

---------------------- Page: 13 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l : 1995 (E)
Annex B
MICS proforma5)
(This annex forms an integral part of this Recommendation I International Standard)
Bl . Introduction
The purpose of this MICS proforma is to provide a mechanism for a supplier of an implementation which claims
conformance, in the manager role, to management information specified in this Recommendation 1 International
Standard, to provide conformance information in a standard form.
B.2 Instructions for completing the MICS proforma to produce a MICS
The MICS proforma contained in this annex is comprised of information in tabular form, in accordance with ITU-T
Rec. X.724 I ISO/IEC 10165-6. In addition to the general guidance given in ITU-T Rec. X.724 I ISOLIEC 101656, the
Additional information column shall be used to identify the object classes for which the management operations are
supported. The supplier of the implementation shall state which items are supported in the tables below and if necessary,
provide additional information.
B3 . Symbols, abbreviations and terms
The following abbreviations are used throughout the MICS proforma:
dmi-att joint-iso-ccitt ms(9) smi(3) part2(2) attribute(7)
dmi-not joint-iso-ccitt ms(9) smi(3) part2(2) notification( 10)
The notations used for the Status and Support columns are specified in A.l.3.
B4 . Statement of conformance to the management information
B.4.1 Notifications
The snecifier of a manager role imnlementation that claims to support the notifications specified in this Recommendation
I International Standardihall import a copy of Table IL1 and con$ete it.
Table B.l - Notification support
Support
Value of object
Non- Additional
Notification type Constraints
Index identifier for the Status Confirmed
template label and values confirmed information
notification type
-
1 communicationsAlarm (dmi-not 2) cl
-
2 environmentalAlarm ( dmi-not 3 ) c2
-
3 equipmentAlarm (dmi-not 4) c3
-
4 processingErrorAlarm (dmi-not 10) c4
-
5 qualityOfServiceAlarm (dmi-not 11) c5
cl: if A.3/la then m else --*
c2: if A.3/2a then m else -.
c3: if A.3/3a then m else -.
c4: if A.3/4a then m else -*
c5: if A.3/5a then m else -”
(continued)
5, Users of this Recommendation I International Standard may freely reproduce the MICS proforma in this annex so that it can be
used for its intended purpose, and may further publish the completed MICS.
10 ITU-T Rec. X.733 (1992)/Amd.l(1995 E)

---------------------- Page: 14 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l : 1995 (E)
Table B.1 (continued) - Notification support
Value of object
identifier for the
Additional
Index Sub-index Notification field name label attribute type Constraints and values Status support
information
associated with
the field
probablecause (dmi-att 18) m
I
globalvalue OBJECT IDENTIFIER m
I
INTEGER m
localValue
I
specificProblems (dmi-att 27) required for some objects m
I
global OBJECT IDENTIFIER m
I
local INTEGER m I
(dmi-att 17) ENUMERATED 0 to 5 m
perceivedseveri ty
I
backedUpStatus (dmi-att 11) required for some objects m
I
backUpObject (dmi-att 40) for backup relationships m
I
distinguishedName m I
1.5.2 nonSpecificForm m
I
1ocalDistinguishedName 1 - m
I
ENUMERATED 0 to 2 m
1.6 trendIndication (dmi-att 30)
I
thresholdInfo (dmi-att 29) for threshold attributes m
I
- -
1.7.1 triggeredThreshold m
- -
1.7.2 observedValue m
- -
1.7.2.1
integer m
-
1.7.2.2 real required for some objects m
- -
1.7.3 thresholdLevel m
- -
1.7.3.1 m
UP
- -
1.7.3.1.1 high
m
-
1.7.3.1.1.1 integer m
-
1.7.3.1.1.2 real required for some objects m
-
1.7.3.1.2 low for guage thresholds m
- -
1.7.3.1.2.1 integer m
-
1.7.3.1.2.2 real required for some objects m
- -
1.7.3.2 down m
- -
1.7.3.2.1 high m
- -
1.7.3.2.1.1 integer
-
1.7.3.2.1.2 real
required for some objects
- -
1.7.3.2.2 low
- -
1.7.3.2.2.1 integer
-
1.7.3.2.2.2 real required for some objects
- -
1.7.4 armTime
1.8 notificationIdentifier (dmi-att 161 INTEGER
-
1.9 correlatedNotifications (dmi-att 12)
-
-
1.9.1 correlatedNotifications
- -
1.9.2 sourceObjectInst
- -
1.9.2.1 distinguishedName
-
-
1.9.2.2 nonSpecificForm
- -
1.9.2.3 1ocalDistinguishedName
(continued)
ITU-T Rec. X.733 (1992)/Amd.l(1995 E) 11

---------------------- Page: 15 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l : 1995 (E)
Table B.l (continued) - Notification support
Value of object
identifier for the
Additional
Index Sub-index Notification field name label attribute type Constraints and values Status Support
information
associated with
the field
1
1 1.10 StateChangeDefinition (dmi-att 28) required for some objects m
I
- -
1.10.1 attributeId m
-
1.10.1.1 global OBJECT IDENTIFIER m
-
1.10.1.2 local INTEGER m
- -
1.10.2 oldAttributeValue m
-
-
m
1.10.3 newAttributeValue
1.11 monitoredAttributes (dmi-att 15) required for some objects m
proposedRepairActions (dmi-att 19) required for some objects m
1.12
-
1.12.1 global OBJECT IDENTIFIER m
-
1.12.2 local INTEGER m
-
1.13 addi tionalTex t (dmi-att 7) m
1.14 additionalInformation (dmi-att 6) required for some objects m
-
2 2.1 probablecause (dmi-att 18) m
-
2.1.1 globalvalue OBJECT IDENTIFIER m
-
2.1.2 localValue INTEGER m
2.2 specificProblems (dmi-att 27) required for some objects m
- -
2.7.3.1.1 high m
- -
2.7.3.1.1.1 integer m
-
2.7.3.1.1.2 real required for some objects m
-
2.7.3.1.2 low for guage thresholds m
- -
2.7.3.1.2.1 integer m
-
2.7.3.1.2.2 real required for some objects m
- -
2.7.3.2 down m
-
-
2.7.3.2.1 high m
- -
2.7.3.2.1.1 integer m
-
2.7.3.2.1.2 real required for some objects m
- -
2.7.3.2.2 low m
- -
2.7.3.2.2.1 integer m
-
2.7.3.2.2.2 real required for some objects m
(continued)
12 ITU-T Rec. X.733 (1992)/Amd.l(1995 E)

---------------------- Page: 16 ----------------------
ISO/IEC 10164-4 : 1992/Amd.l : 1995 (E)
Table B.l (continued) - Notification support
Value of object
identifier for the
Additional
attribute type Constraints and values Status support
Index Sub-index Notification field name label
information
associated with
the field
-
-
2 2.7.4 armTime m
notificationIdentifier (dmi-att 161 INTEGER m
2.8
-
2.9 correlatedNotifications (dmi-att 12) m
- -
12.9.1 1 correlatedNotifications m
I I
- -
1 2.9.2 I sourceObjectInst m
I I
-
-
m
1 2.9.2.1 I distinguishedName
I I
- -
1 2.9.2.2 1 nonSpecificForm m
I I
- -
2.9.2.3 1ocalDistinguishedName m
I I
2.10 StateChangeDefini tion (dmi-att 28} reauired for some obiects I m I
I
- -
12.10.1 1 attributeId I m I
-
12.10.1.1 1 global OBJECT IDENTIFIER m
-
I2.10.1.2 [ local INTEGER m
-
-
r2.- OldAttributeValue m
- -
1 2.10.3 I newAttributeValue m
I I
1211 1 monitoredAttributes (dmi-att 15 I required for some obiects I
. m I I
12.12 I proposedRepairActions ( dmi-att 19 I required for some objects I m I
I
-
OBJECTIDENTIFIER I m I
12.12.1 I global
I
-
1 2.12.2 1 local INTEGER m
I
I I
m
12.13 I additionalText (dmi-att 7)
I I
12.14 addi tionalInformation (dmi-att 6 1 required for some objet
I
-
I
3 131 . I nrobablecause (dmi-att 18 1
-
13.1.1 1 globalvalue OBJECT IDENTIFIER m
-
13.1.2 I localValue INTEGER m
I I I
. I specificProblems (dmi-att 27 P required for some obiects I m
132 I I
-
1 3.2.1 1 global OBJECT IDENTIFIER m
-
1 3.2.2 1 local [NTEGER m
1 3.3 1 perceivedseverity (dmi-att 17) ENUMERATEDOto5 I m I
I
1 3.4 I backedUpStatus (dmi-att 11) reauired for some objects I
m I I
1 3.5 I backUpObject (dmi-att 40) for backup relationships I m I
-
13.5.1 I d- 1stinguishedName
I m I I
- -
13.5.2 I nonSpecificForm m
I I
- -
m
13.5.3 I 1ocalDistinguishedName I
I
3.6 trendIndication (dmi-att 30) ENUMERATED0 to 2 1 m I
I
3.7 thresholdInfo (dmi-att 29) for threshold attributes I m I
-
m
3.7.1 triggeredThreshold
I I
-
m
3.7.2 observedvalue
I I
-
m
3.7.2.1 integer
I I
~~~
3.7.2.2 real required
...

NORME
ISO/CEI
I NTER NAT1 ONALE
10164-4
Premiere edition
1992-1 2-1 5
AMENDEMENT 1
1995-1 2-1 5
Technologies de l'information -
Interconnexion de systèmes ouverts
(OSI) - Gestion-systèmes: Fonction
de signalisation des alarmes
AMENDEMENT 1 : Formulaires de déclaration
de conformité d'instance
Information technology - Open Systems Interconnection - Systems
Management: Alarm reporting function
AMENDMENT 1: Implementation conformance statement proformas
Numero de reference
ISOlCEl 1 O1 64-4:1992/Amd.l :I 9951F3

---------------------- Page: 1 ----------------------
~~
ISO/CEI 10164-4:1992/Amd.l:1995(F)
Avant-propos
L’ISO (Organisation internationale de normalisation) et la CE1 (Commission
électrotechnique internationale) forment ensemble un système consacré B la nor-
malisation internationale considérée comme un tout. Les organismes nationaux
membres de I’ISO ou de la CE1 participent au développement de Normes inter-
nationales par l’intermédiaire des comités techniques créés par l’organisation
concernée afin de s’occuper des différents domaines particuliers de l’activité tech-
nique. Les comités techniques de I’ISO et de la CE1 collaborent dans des
domaines d’intérêt commun. D’autres organisations internationales, gouverne-
mentales ou non gouvernementales, en liaison avec I’ISO et la CE1 participent
également aux travaux.
Dans le domaine des technologies de l’information, I’ISO et la CE1 ont créé un
comité technique mixte, l’ISO/CEI JTC 1. Les projets de Normes internationales
adoptés par le comité technique mixte sont soumis aux organismes nationaux pour
approbation, avant leur acceptation comme Normes internationales. Les Normes
internationales sont approuvées conformément aux procédures qui requièrent
l’approbation de 75 % au moins des organismes nationaux votants.
L’Amendement 1 B la Norme internationale ISOKEI 10164-4:1992 a été élaboré
par le comité technique mixte ISOKEI JTC 1, Technologies de l’information,
sous-comité SC 2 1, Interconnexion des systèmes ouverts, gestion des donndes et
traitement distribué ouvert, en collaboration avec I’UIT-T. Le texte identique est
publié en tant que Recommandation UIT-T X.733/Amd. 1.
O ISOiCEI 1995
Droits de reproduction réservés. Sauf prescription différente, aucune partie de cette publi-
cation ne peut être reproduite ni utilisée sous quelque forme que ce soit et par aucun pro-
cédé, électronique ou mécanique, y compris la photocopie et les microfilms, sans l’accord
écrit de I’éditeur.
ISOiCEI Copyright Offce Case postale 56 CH-1211 Genkve 20 Suisse
Version française tirée en 1996
Imprimé en Suisse
11

---------------------- Page: 2 ----------------------
4
ISO/CEI 10164-4: 1992/Amd. 1 : 1995(F)
Introduction
Le présent amendement contient les tableaux qui indiquent les informations de gestion obligatoires et facultatives
propres à la fonction de signalisation d'alarmes. I1 sera utilisé par les spécificateurs de profils, par exemple ceux qui
élaborent des profils normalisés internationaux (ISP) (international standardized profiles), quand ils spécifient un sous-
ensemble explicite de capacités afin d'assurer I'interopérabilité des applications. Les tableaux comportent aussi une
colonne dans laquelle les fournisseurs d'équipements indiqueront les capacités de leurs produits en termes de profils ou
de spécifications de base. La structure des tableaux est conforme aux lignes directrices contenues dans la
Rec. UIT-T X.724 I ISO/CEI 10165-6 pour l'établissement des formulaires de déclaration de conformité des instances de
protocole.
...
111

---------------------- Page: 3 ----------------------
ISOKEI 10164-4 : 199YAmd.l : 1995 (F)
NORME INTERNATIONALE
RECOMMANDATION UIT-T
TECHNOLOGIES DE L'INFORMATION - INTERCONNEXION
DE SYSTÈMES OUVERTS (OSI) - GESTION-SYSTÈMES: FONCTION
DE SIGNALISATION DES ALARMES
AMENDEMENT 1
(à la Rec. UIT-T X.733 I ISOKEI 10164-4)
Formulaires de déclaration de conformité d'instance
Au 2. I, ajouter la note de bas de page suivante au premier élément de la liste:
1)
Tel que modifide par la Rec. UIT-T X.70Kor.2 I ISO/CEI 10040/Cor.2.>~
Au 2.1, ajouter la référence suivante:
2)
G- Recommandation UIT-T X.724 (1993) 1 ISOICEI 10165-6: 1994, Technologie de l'information -
Interconnexion des systèmes ouverts - Structure de l'information de gestion: Spécijïcations et directives
pour l'établissement des formulaires de déclaration de conformité d'instances associés à la gestion OSI.*
Au 2.2, ajouter les références suivantes:
3)
<<- Recommandation X.291 du CCITT (1992), Cadre général et méthodologie des tests de conformité
d'interconnexion des systèmes ouverts pour les Recommandations sur les protocoles pour les applications
de 1'UIT-T- Spécification de suites de tests abstraite.
ISOKEI 9646-2: 1991, Technologies de l'infonnation - Interconnexion de systèmes ouverts - Cadre
général et méthodologie des tests de conformité OS1 - Partie 2: Spécijïcation des suites de tests
abstraites.
-
Recommandation UIT-T X.2963), Cadre général et méthodologie des tests de conformité OS1 pour les
Recommandations sur les protocoles pour les applications de 1'UIT-T - Déclarations de conformité
d'instance.
ISOICEI 9646-73), Technologies de l'information - Interconnexion de systèmes ouverts - Méthodologie
générale et procédures - Partie 7: Déclarations de conformité des instances.*
Ajouter la note de bas de page suivante:
<<3) Actuellement 21 1'Ctat de projet.))
Au 3.4, faire les modifications suivantes:
4)
Supprimer les points c) et d).
Renommer les points e) et c) et insérer les nouveaux points suivants:
< f) déclaration de conformit6 d'information de gestion (MICS);))
Les points h) à j) deviennent les déments j) à 1). Insérer les nouveaux points suivants:
< i) formulaire MOCS;>)
Au 3.6, faire les modifications suivantes:
5)
Remplacer < < ddclaration de conformitd d'instance de protocole;
b)
dkclaration de conformit6 du systbme.,)
c)
1
Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 4 ----------------------
ISOICEI 10164-4 : 1992/Amd.l : 1995 (F)
Le paragraphe 3.7 devient 3.8. Insérer le nouveau paragraphe suivant:
6)
3.7 < La prdsente Recommandation 1 Norme internationale utilise les termes suivants définis par la Rec. UIT-T X.724 I
ISO/CEI 10165-6:
declaration de conformite de relation gCr6e (MRCS);
a)
rkcapitulatif de conformite de gestion (MCS);
b)
formulaire de déclaration de définition d'information de gestion (Formulaire MIDS);
c)
d) formulaire MCS;
e) formulaire MRCS.n
A l'article 4, ajouter les abréviations suivantes:
7)
aICS Déclaration de conformité d'instance (implementation conformance statement)
MCS
Recapitulatif de conformitt de gestion (management conformance summary)
MICS
Declaration de conformit6 d'information de gestion (management information conformance
statement)
MIDS Déclaration de définition d'information de gestion (management information definition statement)
MOCS Declaration de conformite d'objet g6rC (managed object conformance statement)
MRCS Declaration de conformitt de relation g6r6e (managed relationship conformance statement)
PICS D6claration de conformite dinstance de protocole (protocol implementation conformance
statement),,
Remplacer l'article 13 par ce qui suit:
8)
((13 Conformité
Les instances qui se veulent conformes B la prdsente Recommandation I Norme internationale doivent satisfaire aux
prescriptions de conformitt? definies aux paragraphes suivants.
13.1 Conformité statique
L'instance doit satisfaire aux prescriptions de conformite de la pr6sente Recommandation I Norme internationale dans
son rôle de gestionnaire, son rôle d'agent, ou dans les deux rôles. Une déclaration de conformit6.B l'un des rôles au moins
sera faite au Tableau A. 1.
Si une déclaration de conformit6 est faite pour la prise en charge du rôle de gestionnaire, l'instance doit prendre en
charge l'une au moins des notifications ou l'une des operations de gestion specifiées dans la presente Recommandation I
Norme internationale. Les prescriptions de conformit6 du rôle de gestionnaire B ces operations et notifications de gestion
sont identifies au Tableau A.3 et dans d'autres tableaux referenc6s dans l'Annexe A.
Si une declaration de conformite est faite pour la prise en charge du rôle d'agent, l'instance doit prendre en charge l'une
au moins des notifications specifides dans la pr6sente Recommandation I Norme internationale. Les prescriptions de
conformité du rôle d'agent sont identifiees au Tableau A.4 et dans d'autres tableaux r6ferencks dans l'Annexe A.
L'instance doit prendre en charge la syntaxe de transfert obtenue B partir des regles de codage specifites dans la
Rec. X.209 du CCITT I ISO/CEI 8825 appelee {joint-iso-ccitt asnl(1) basicEncoding(l)} pour les types abstraits de
données rbf6renc6s par les definitions que l'instance veut prendre en charge.
NOTE - Avant publication du present amendement, la pr6sente Recommandation 1 Norme internationale identifiait des
classes de conformit6 g6ndrale et induite. Une dtclaration de conformit6 semblable ?î celle de la classe de conformit6 g6nérale peut
être faite en d6clarant la prise en charge par le rôle de gestionnaire, le rôle d'agent ou par les deux rôles, de l'unit6 fonctionnelle de
rapport d'alarme du Tableau A.2. Une dtclaration de conformitt semblable celle de la classe de conformit6 induite peut Ctre faite en
déclarant la prise en charge de l'un au moins des Cléments des Tableaux A.3 et A.4.
2 Rec. UIT-T X.733 (1992YAmd.l (1995 F)

---------------------- Page: 5 ----------------------
ISO/CEI 10164-4 : 19921Amd.l: 1995 (F)
13.2 Conformité dynamique
Les instances qui se veulent conformes à la présente Recommandation I Norme internationale doivent prendre en charge
les elements de procédure et les d6finitions semantiques correspondant aux definitions qu'elles veulent prendre en
charge.
13.3 Prescriptions de déclaration de conformité d'information de gestion
Un formulaire MCS, MICS ou MOCS conforme à la presente Recommandation I Norme internationale doit être
identique, dans son texte, aux formulaires correspondants sp6cifies dans les Annexes A, B ou C, doit conserver la
numerotation des tableaux et les numeros d'index des diffkrents elements et ne peut diff6rer de ces formulaires que par la
pagination et les en-têtes de page.
Le fournisseur d'une instance qui se veut conforme il la prksente Recommandation I Norme internationale doit complkter
un formulaire rkcapitulatif de conformit6 de gestion (MCS) fourni dans l'Annexe A, ce qui fait partie des prescriptions
de conformit6, de même que tout autre formulaire ICS r6férenc6 qui est applicable daprc?s le MCS. Un ICS qui se veut
conforme B la prisente Recommandation I Norme internationale:
-
decrit une instance conforme B la presente Recommandation I Norme internationale;
- est rempli conformement aux instructions donnees B cet effet dans la Rec. UIT-T X.724 I
ISOICEI 10165-6;
-
contient les renseignements nkcessaires pour identifier sans ambiguïtk le fournisseur et l'instance.
Les declarations de conformite d'information de gestion ddfinies dans la prksente Recommandation I Norme
internationale pour des classes d'objets gCr& dkfinies par ailleurs comprennent les prescriptions du formulaire MIDS des
formulaires MOCS pour la classe des objets gtr6s.u
3
Rec. UIT-T X.733 (1992)/Amd.1(1995 F)

---------------------- Page: 6 ----------------------
ISO/CEI 10164-4 : 1992/Amd.l: 1995 (F)
L'Annexe A devient l'Annexe E. Insérer les annexes suivantes:
9)
Annexe A
Formulaire MCP
(Cette annexe fait partie integrante de la prksente Recommandation I Norme internationale)
A.1 Introduction
A.l.l Purpose and structure
The Management Conformance Summary (MCS) is a statement by a supplier that identifies an implementation and
provides information on whether the implementation claims conformance to any of the listed set of documents that
specify conformance requirements to OS1 management.
The MCS proforma is a document in the form of a questionnaire that when completed by the supplier of an
implementation becomes the MCS.
A.1.2 Instructions for completing the MCS proforma to produce a MCS
The supplier of the implementation shall enter an explicit statement in each of the boxes provided. Specific instruction is
provided in the text which precedes each table.
A.1.3 Symbols, abbreviations and terms
For all annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISOAEC 9646-2 and ITU-T Rec. X.296 I ISOAEC 9646-7, are used for the Status column:
m Mandatory:
O Optional:
C Conditional;
X Prohibited;
-
Not applicable or out of scope.
NOTES
1 'c', 'm', and 'O' are prefixed by "c:" when nested under a conditional or optional item of the same table;
2 'O' may be suffixed by ".N" (where N is a unique number) for selectable options among a set of status values. Support
of at least one of the choices (from the items with the same value of N) is required.
For all annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISOAEC 9646-2 and ITU-T Rec. X.296 I ISOAEC 9646-7, are used for the Support column:
Y Implemented;
N Not implemented;
- No answer required;
The item is ignored (i.e. processed syntactically but not semantically).
Ig
A.1.4 Table format
Some of the tables in this Recommendation I International Standard have been split because the information is too wide
to fit on the page. Where this occurs, the index number of the first block of columns are the index numbers of the
corresponding rows of the remaining blocks of columns. A complete table reconstructed from the constituent parts
should have the following layout:
~~
Index First block of columns I Second block of columns I Etc.
I
4, Les utilisateurs de la prtsente Recommandation I Norme internationale sont autorisés B reproduire le formulaire MCS de la
prtsente annexe pour utiliser celui-ci conformtment h son objet. Ils sont tgalement autorids B publier le formulaire une fois
celui-ci complétt. Les instructions pour le formulaire MCS sont spécifiées dans la Rec. UIT-T X.724 I ISO/CEI 10165-6.
4 Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 7 ----------------------
ISO/CEI 10164-4 : 199YAmd.l: 1995 (F)
In this Recommendation I International Standard the constituent parts of the table appear consecutively, starting with the
first block of columns.
When a table with sub-rows is too wide to fit on a page, the continuation table(s) have been constructed with index
numbers identical to the index numbers in the corresponding rows of the first table, and with sub-index numbers
corresponding to the sub-rows within each indexed row. For example, if Table X.l has 2 rows and the continuation of
Table X.l has 2 sub-rows for each row, the tables are presented as follows:
Table X.1- Title
1 ab-
2 ab-
Table X.1 (continuqd) - Title
Index Sub-index H I JKL
1
1.1 h 1 j
1.2 h i j
2
2.1 h i j
2.2 h i j
A complete table reconstructed from the constituent parts should have the following layout:
I I I 2.2 I
References made to cells within tables shall be interpreted as references within reconstructed tables. In the examples,
above, the reference X.l/ld corresponds to the blank cell in column G for row with Index 1, and X.1/1.2b corresponds to
the blank cell in column L for row with Sub-index 1.2.
A.2 Identification of the implementation
A.2.1 Date of statement
The supplier of the implementation shall enter the date of this statement in the box below. Use the format DD-MM-
YYYY.
Date of statement
5
Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 8 ----------------------
ISOlCEI 10164-4 : 1992lAmd.l : 1995 (F)
A.2.2 Identification of the implementation
The supplier of the implementation shall enter information necessary to uniquely identify the implementation and the
system(s) in which it may reside, in the box below.
A.2.3 Contact
The supplier of the implementation shall provide information on whom to contact if there are any queries concerning the
content of the MCS or any referenced conformance statement, in the box below.
A.3 Identification of the Recommendations I International Standards in which the management
information is defined
The supplier of the implementation shall enter the title, reference number and date of the publication of the
Recommendations I International Standards which specify the management information to which conformance is
claimed, in the box below.
~ ~~~ ~ ~~
Recommendations I International Standards to which conformance is claimed
A.3.1 Technical corrigenda implemented
The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify
the identified Recommendations I International Standards, in the box below.
A.3.2 Amendments implemented
The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the
identified Recommendations I International Standards, in the box below.
6 Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 9 ----------------------
ISO/CEI 10164-4 : 199WAmd.l : 1995 (F)
A.4 Management conformance summary
The supplier of the implementation shall state the capabilities and features supported and provide a summary of
conformance claims to Recommendations I International Standards using the tables in this annex.
The supplier of the implementation shall specify the roles that are supported, in Table A. 1.
Table A.1- Roles
Index
Roles supported Status Support Additional information
1 Manager role SUD DO^^ o. 1
~
2 I Agent role support
O. 1
The supplier of the implementation shall specify support for the systems management functional unit, in Table A.2.
Table A.2 - Systems management functional unit
Manager Agent
Index Systems management functional unit name
Status Support Status Support Additional information
1 alarm reporting functional unit cl c2
The supplier of the implementation shall specify support for management information in the manager role, in Table A.3.
Table A.3 - Manager role minimum conformance requirement
Index Item Status Support Additional information
1 Communications alarm notification c3
2 Environmental alarm notification c3
3 Equipment alarm notification c3
4 Processing error alarm notification c3
c3
5 Quality of service alarm notification
6 Operations on managed objects c4
Rec. UIT-T X.733 (1992)/Amd.l(1995 F) 7

---------------------- Page: 10 ----------------------
ISO/CEI 10164-4 : 1992/Amd.l: 1995 (F)
The supplier of the implementation shall specify support for management information in the agent role, in Table A.4.
Index
Item Status Support Table reference Additional information
1
Communications alarm notification C5
2 Environmental alarm notification C5
3 Equipment alarm notification c5
4 Processing error alarm notification C5
5
Quality of service alarm notification C5
6
Alarm record managed object class c6 -
Table AS - Logging of event records
Additional
Index
Status support information
1 Does the implementation support logging of event records in agent role? c7
I c7: if A. 1/2a then O else -.
NOTE 1 - Conformance to this Recommendation I International Standard does not require conformance to CCITT
Rec. X.735 I ISO/IEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the Recommendations
I International Standards summarized in Tables A.6 to A.9. For each Recommendation I International Standard that the
supplier of the implementation claims conformance to, the corresponding conformance statement(s) shall be completed,
or referenced by, the MCS. The supplier of the implementation shall complete the Support, Table numbers and
Additional information columns.
In Tables A.6 to A.9, the Status column is used to indicate whether the supplier of the implementation is required to
complete the referenced tables or referenced items. Conformance requirements are as specified in the referenced tables
or referenced items and are not changed by the value of the MCS Status column. Similarly, the Support column is used
by the supplier of the implementation to indicate completion of the referenced tables or referenced items.
Table A.6 - PICS support summary
~~
Table
Identification of the
Index numbers Description Constraints Status Support numbers Additional
document that includes
and values of PICS information
of PICS
the PICS proforma
proforma
- ~~~
Annex E SM application context OBJECT m
1 CCIlT Rec. X.730 I
IDENTIFIER
ISOAEC 10164-1 all tables
NOTE 2 - Conformance to the MAPDUs defined in this Recommendation I Intemational Standard can be claimed by
completing the corresponding tables in the MICS and MOCS annexes of the referenced Recommendations I International Standards.
Rec. UIT-T X.733 (1992)/Amd.l(1995 F)
8

---------------------- Page: 11 ----------------------
Identification of th
...

NORME
lSO/CEI
INTERNATIONALE
10164-4
Première édition
1992-I 2-l 5
AMENDEMENT 1
1995-I 2-l 5
Technologies de l’information -
Interconnexion de systèmes ouverts
(OSI) - Gestion-systèmes: Fonction
de signalisation des alarmes
AMENDEMENT 1: Formulaires de déclaration
de conformité d’instance
Information technolog y - Open S ys tems In terconnec tion - S ys tems
Management: Alarm reporting function
AMENDMENT 1: Implementation conformance statement proformas
Numéro de référence
ISO/CEI 10164-4:1992/Amd.l:1995(F)

---------------------- Page: 1 ----------------------
NO/CE1 1016494:1992/Amd.l:1995(F)
Avant-propos
LIS0 (Organisation internationale de normalisation) et la CE1 (Commission
électrotechnique internationale) forment ensemble un système consacré à la nor-
malisation internationale considérée comme un tout. Les organismes nationaux
membres de 1’ISO ou de la CE1 participent au développement de Normes inter-
nationales par l’intermédiaire des comités techniques créés par l’organisation
concernée afin de s’occuper des différents domaines particuliers de l’activité tech-
nique. Les comités techniques de 1’ISO et de la CE1 collaborent dans des
domaines d’intérêt commun. D’autres organisations internationales, gouverne-
mentales ou non gouvernementales, en liaison avec I’ISO et la CE1 participent
également aux travaux.
Dans le domaine des technologies de l’information, 1’ISO et la CE1 ont créé un
comité technique mixte, 1’ISOKEI JTC 1. Les projets de Normes internationales
adoptés par le comité technique mixte sont soumis aux organismes nationaux pour
approbation, avant leur acceptation comme Normes internationales. Les Normes
internationales sont approuvées conformément aux procédures qui requièrent
l’approbation de 75 % au moins des organismes nationaux votants.
L’Amendement 1 à la Norme internationale ISO/CEI 10164-4: 1992 a été élaboré
par le comité technique mixte ISOKEI JTC 1, Technologies de Z’information,
sous-comité SC 21, Interconnexion des systèmes ouverts, gestion des données et
traitement distribué ouvert, en collaboration avec l’UIT-T. Le texte identique est
publié en tant que Recommandation UIT-T X733/Amd. 1.
0 ISO/CEI 1995
Droits de reproduction réservés. Sauf prescription différente, aucune partie de cette publi-
cation ne peut être reproduite ni utilisée sous quelque forme que ce soit et par aucun pro-
cédé, électronique ou mécanique, y compris la photocopie et les microfilms, sans l’accord
écrit de l’éditeur.
ISOKEI Copyright Office l Case postale 56 l CH-1 211 Genéve 20 l Suisse
Version française tirée en 1996
Imprimé en Suisse
ii

---------------------- Page: 2 ----------------------
ISOKEI 10X4-4: 1992/Amd.l: 1995(F)
0 ISO/CEI
Introduction
Le présent amendement contient les tableaux qui indiquent les informations de gestion obligatoires et facultatives
propres à la fonction de signalisation d’alarmes. Il sera utilisé par les spécificateurs de profils, par exemple ceux qui
élaborent des profils normalisés internationaux (ISP) (international standardized profiles), quand ils spécifient un sous-
ensemble explicite de capacités afin d’assurer l’interopérabilité des applications. Les tableaux comportent aussi une
colonne dans laquelle les fournisseurs d’équipements indiqueront les capacités de leurs produits en termes de profils ou
de spécifications de base. La structure des tableaux est conforme aux lignes directrices contenues dans la
Rec. UIT-T X.724 I ISOKEI 10165-6 pour l’établissement des formulaires de déclaration de conformité des instances de
protocole.
. . .
111

---------------------- Page: 3 ----------------------
Page blanche

---------------------- Page: 4 ----------------------
ISOKEI 10164-4 : 199WAmd.l: 1995 (F)
NORME INTERNATIONALE
RECOMMANDATION UIT-T
TECHNOLOGIES DE L’INFORMATION - INTERCONNEXION
DE SYSTÈMES OUVERTS (OSI) - GESTION-SYSTÈMES: FONCTION
DE SIGNALISATION DES ALARMES
AMENDEMENT 1
(à la Rec. UIT-T X.733 I ISOKEI 10164-4)
Formulaires de déclaration de conformité d’instance
Au 2.1, ajouter la note de bas de page suivante au premier élément de la liste:
1)
«l) Tel que modifiée par la Rec. UIT-T X.701Kor.2 I ISOKEI 10040/Cor.2.»
Au 2.1, ajouter la référence suivante:
2)
«- Recommandation UIT-T X.724 (1993) 1 ISOKEI 10165-6: 1994, Technologie de l’information -
Interconnexion des systèmes ouverts - Structure de l’information de gestion: Spécifications et directives
pour l’établissement des formulaires de déclaration de conformité d’instances associés à la gestion OSI.»
Au 2.2, ajouter les références suivantes:
3)
«- Recommandation X.291 du CCITT (1992), Cadre général et méthodologie des tests de conformité
d’interconnexion des systèmes ouverts pour les Recommandations sur les protocoles pour les applications
de I’UIT-T - Spéciflcation de suites de tests abstraite.
ISOKEI 9646-2: 199 1, Technologies de 1 ‘information - Interconnexion de systèmes ouverts - Cadre
Partie 2: Spécification des suites de tests
général et méthodologie des tests de conformité OSI -
abstraites.
-
Recommandation UIT-T X.2963), Cadre général et méthodologie des tests de conformité OSI pour les
Recommandations sur les protocoles pour les applications de I’UIT-T - Déclarations de conformité
d’instance.
ISOICEI 9646-73), Technologies de 1 ‘information - Interconnexion de systèmes ouverts - Méthodologie
générale et procédures - Partie 7: Déclarations de conformité des instances.»
Ajouter la note de bas de page suivante:
«3) Actuellement à l’état de projet.»
Au 3.4, faire les modiftcations suivantes:
4)
Supprimer les points c) et d).
Renommer les points e) et c) et insérer les nouveaux points suivants:
«e) déclaration de conformité d’objet géré (MOCS);
f) déclaration de conformité d’information de gestion (MICS);»
Les points h) à j) deviennent les éléments j) à 1). Insérer les nouveaux points suivants:
«h) formulaire MICS;
formulaire MOCS;»
0
Au 3.6, faire les modifications suivantes:
5)
Remplacer «déclaration de conformité du système» par:
«a) formulaire PICS;
déclaration de conformité d’instance de protocole;
b)
déclaration de conformité du système.»
C)
Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 5 ----------------------
ISOKEI 10164-4 : 199WAmd.l: 1995 (F)
Le paragraphe 3.7 devient 3.8. Insérer le nouveau paragraphe suivant:
37 . «Définition des formulaires de déclaration de conformité d’instance
La présente Recommandation I Norme internationale utilise les termes suivants définis par la Rec. UIT-T X.724 1
ISOKEI 10165-6:
a) déclaration de conformité de relation gérée (MRCS);
b) récapitulatif de conformité de gestion (MCS);
c) formulaire de déclaration de définition d’information de gestion (Formulaire MIDS);
d) formulaire MCS;
e) formulaire MRCS .»
A l’article 4, ajouter les abréviations suivantes:
«ICS Déclaration de conformité d’instance (implementation conformance statement)
MCS Récapitulatif de conformité de gestion (management conformance summary)
MICS Déclaration de conformité d’information de gestion (management information conformance
statement)
MIDS Déclaration de définition d’information de gestion (management information definition statement)
MOCS Déclaration de conformité d’objet géré (managed abject conformance statement)
MRCS Déclaration de conformité de relation gérée (managed relationship conformance statement)
PICS Déclaration de conformité d’instance de protocole (protocol implementation conformance
statement)»
Remplacer 1 ‘article 13 par ce qui suit:
8)
Conformité
«13
Les instances qui se veulent conformes à la présente Recommandation 1 Norme internationale doivent satisfaire aux
prescriptions de conformité définies aux paragraphes suivants.
13.1 Conformité statique
L’instance doit satisfaire aux prescriptions de conformité de la présente Recommandation 1 Norme internationale dans
son rôle de gestionnaire, son rôle d’agent, ou dans les deux rôles. Une déclaration de conformité à l’un des rôles au moins
sera faite au Tableau A. 1.
Si une déclaration de conformité est faite pour la prise en charge du rôle de gestionnaire, l’instance doit prendre en
charge l’une au moins des notifications ou l’une des opérations de gestion spécifiées dans la présente Recommandation I
Norme internationale. Les prescriptions de conformité du rôle de gestionnaire à ces opérations et notifications de gestion
sont identifiés au Tableau A.3 et dans d’autres tableaux référencés dans YAnnexe A.
Si une déclaration de conformité est faite pour la prise en charge du rôle d’agent, l’instance doit prendre en charge l’une
au moins des notifications spécifiées dans la présente Recommandation I Norme internationale. Les prescriptions de
conformité du rôle d’agent sont identifiées au Tableau A.4 et dans d’autres tableaux référencés dans 1’Annexe A.
L’instance doit prendre en charge la syntaxe de transfert obtenue à partir des règles de codage spécifiées dans la
Rec. X.209 du CCITT I ISOKEI 8825 appelée (joint-iso-ccitt asnl( 1) basicEncoding( 1)) pour les types abstraits de
données référencés par les définitions que l’instance veut prendre en charge.
NOTE - Avant publication du présent amendement, la présente Recommandation I Norme internationale identifiait des
classes de conforrnitk générale et induite. Une déclaration de conformité semblable à celle de la classe de conformité générale peut
être faite en déclarant la prise en charge par le rôle de gestionnaire, le rôle d’agent ou par les deux rôles, de l’unité fonctionnelle de
rapport d’alarme du Tableau A.2. Une declaration de conformité semblable à celle de la classe de conformité induite peut être faite en
déclarant la prise en charge de l’un au moins des cléments des Tableaux A.3 et A.4.
2 Rec. UIT-T X.733 (1992)/Amd.1(1995 F)

---------------------- Page: 6 ----------------------
ISOKEI 10164-4 : 1992/Amd.l: 1995 (F)
13.2 Conformité dynamique
Les instances qui se veulent conformes à la présente Recommandation 1 Norme internationale doivent prendre en charge
les éléments de procédure et les définitions sémantiques correspondant aux définitions qu’elles veulent prendre en
charge.
Prescriptions de déclaration de conformité d’information de gestion
13.3
Un formulaire MCS, MICS ou MOCS conforme à la présente Recommandation 1 Norme internationale doit être
identique, dans son texte, aux formulaires correspondants spécifiés dans les Annexes A, B ou C, doit conserver la
numérotation des tableaux et les numéros d’index des differents éléments et ne peut différer de ces formulaires que par la
pagination et les en-têtes de page.
Le fournisseur d’une instance qui se veut conforme à la présente Recommandation 1 Norme internationale doit compléter
un formulaire récapitulatif de conformite de gestion (MCS) fourni dans YAnnexe A, ce qui fait partie des prescriptions
de conformité, de même que tout autre formulaire ICS reférence qui est applicable d’après le MCS. Un ICS qui se veut
conforme à la présente Recommandation 1 Norme internationale:
-
décrit une instance conforme à la présente Recommandation 1 Norme internationale;
-
est rempli conformément aux instructions données à cet effet dans la Rec. UIT-T X.724 1
ISOKEI 101656;
-
contient les renseignements nécessaires pour identifier sans ambiguïté le fournisseur et l’instance.
Les déclarations de conformité d’information de gestion définies dans la présente Recommandation I Norme
internationale pour des classes d’objets gérés définies par ailleurs comprennent les prescriptions du formulaire MIDS des
formulaires MOCS pour la classe des objets gérés.»
Rec. UIT-T X.733 (1992)/Amd.l(1995 F) 3

---------------------- Page: 7 ----------------------
ISOKEI 10164-4 : 1992/Amd.l: 1995 (F)
L’Annexe A devient 1’Annexe E. Insérer les annexes suivantes:
9)
Annexe A
Formulaire MCW
(Cette annexe fait partie intégrante de la présente Recommandation I Norme internationale)
Al . Introduction
A.1.1 Purpose and structure
The Management Conformance Summary (MCS) is a statement by a supplier that identifies an implementation and
provides information on whether the implementation claims conformance to any of the listed set of documents that
specify conformance requirements to OS1 management.
The MCS proforma is a document in the for-m of a questionnaire that when completed by the supplier of an
implementation becomes the MCS.
A.l.2 Instructions for completing the MCS proforma to produce a MCS
The supplier of the implementation shall enter an explicit statement in each of the boxes provided. Specific instruction is
provided in the text which precedes each table.
A.l.3 Symbols, abbreviations and terms
For a11 annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISO/IEC 9646-2 and [TU-T Rec. X.296 1 ISO/IEC 9646-7, are used for the Status column:
m Mandatory;
0 Optional;
Condi tional ;
C
Prohibited;
X
-
Not applicable or out of scope.
NOTES
1 ‘c’, ‘m’, and ‘0’ are prefixed by “c:” when nested under a conditional or optional item of the same table;
2 ‘0’ may be suffxed by “.N” (where N is a unique number) for selectable options among a set of status values. Support
of at least one of the choices (from the items with the same value of N) is required.
For a11 annexes of this Recommendation I International Standard, the following common notations, defined in CCITT
Rec. X.291 I ISOLIEC 9646-2 and ITU-T Rec. X.296 I ISOLIEC 9646-7, are used for the Support column:
Y Implemented;
N Not implemented;
-
No answer required;
The item is ignored (i.e. processed syntactically but not semantically).
Ig
A.l.4 Table format
Some of the tables in this Recommendation I International Standard have been split because the information is too wide
to fit on the page. Where this occurs, the index number of the first block of columns are the index numbers of the
corresponding rows of the remaining blocks of columns. A complete table reconstructed from the constituent parts
should have the following layout:
Index First block of columns Second block of columns Etc.
4, Les utilisateurs de la présente Recommandation I Norme internationale sont autorisés à reproduire le formulaire MCS de la ,
présente annexe pour utiliser celui-ci conformément à son objet. Ils sont également autorisés à publier le formulaire une fois
celui-ci complété. Les instructions pour le formulaire MCS sont spécifiées dans la Rec. UIT-T X.724 I ISOKEI 10165-6.
4 Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 8 ----------------------
ISOKEI 10164-4 : 199WAmd.l: 1995 (F)
In this Recommendation I International Standard the constituent parts of the table appear consecutively, starting with the
first block of columns.
When a table with sub-rows is too wide to fit on a page, the continuation table(s) have been constructed with index
numbers identical to the index numbers in the corresponding rows of the first table, and with sub-index numbers
corresponding to the sub-rows within each indexed row. For example, if Table X.1 has 2 rows and the continuation of
Table X.1 has 2 sub-rows for each row, the tables are presented as follows:
Table X.1 - Title
support
. l
Index A B C D E F G
1 a b -
2 a b -
l
Table X.1 (continued) - Title
2.2
I I I
A complete table reconstructed from the constituent parts should have the following layout:
Index A B C D E 1 G 1 Sub-index 1 H 1 1 1 J
1.1 h i
j
1.2 h i
j
2.1 h i
j
2.2 h i
J
References made to cells within tables shall be interpreted as references within reconstructed tables. In the examples,
above, the reference X. l/ld corresponds to the blank ce11 in column G for row with Index 1, and X. 1/1.2b corresponds to
the blank ce11 in column L for row with Sub-index 1.2.
A.2 Identification of the implementation
A.2.1 Date of statement
The supplier of the implementation shall enter the date of this statement in the box below. Use the format DD-MM-
YYYY.
Date of statement
I I
Rec. UIT-T X.733 (1992)/Amd.l(1995 F)
5

---------------------- Page: 9 ----------------------
ISOKEI 10164-4 : 1992lAmd.l : 1995 (F)
A.2.2 Identification of the implementation
The supplier of the implementation shah enter information necessary to uniquely identify the implementation and the
system(s) in which it may reside, in the box below.
A.2.3 Contact
The supplier of the implementation shall provide information on whom to contact if there are any queries concerning the
content of the MCS or any referenced conformance statement, in the box below.
A.3 Identification of the Recommendations I International Standards in which the management
information is defined
The supplier of the implementation shall enter the title, reference number and date of the publication of the
Recommendations I International Standards which specify the management information to which conformance is
claimed, in the box below.
Recommendations I International Standards to which conformance is claimed
Technical corrigenda implemented
A.3.1
The supplier of the implementation shall enter the reference numbers of implemented technical corrigenda which modify
the identified Recommendations I International Standards, in the box below,
A.3.2 Amendments implemented
The supplier of the implementation shall state the titles and reference numbers of implemented amendments to the
identified Recommendations I International Standards, in the box below.
6 Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 10 ----------------------
ISOKEI 10164-4 : 199YAmd.l: 1995 (F)
A.4 Management conformance summary
The supplier of the implementation shall state the capabilities and features supported and provide a summary of
conformance claims to Recommendations I International Standards using the tables in this annex.
The supplier of the implementation shall specify the roles that are supported, in Table A. 1.
Table A.1 - Roles
Index Roles supported Status Support Additional information
1 Manager role support 0.1
2 Agent role support 0.1
The supplier of the implementation shall specify support for the systems management functional unit, in Table A.2.
Table A.2 - Systems management functional unit
Manager Agent
Index Systems management functional unit name Status Support Status Support Additional information
alarm reporting functional unit Cl c2
1
cl: if Al/la then o else -.
c2: if A.l/2a then o else -.
I I
The supplier of the implementation shall specify support for management information in the manager role, in Table A.3.
Table A.3 - Manager role minimum conformance requirement
Addi tional information
Index Item Status support
c3
1 Communications alarm notification
c3
2 Environmental alarm notification
c3
Equipment alarm notification
3
c3
4 Processing error alarm notification
c3
5 Quality of service alarm notification
c4
Operations on managed abjects
6
c3: if A.Ula then m else (if A.l/la then 0.2 else -).
c4: if A.Ula then o else (if A.l/la then 0.2 else -).
NOTE - Manager role minimum conformance requires support for at least one of the items identified in this table. Support for
the functional unit identifïed in Table A.2 mandates support for some of those items. Conditions c3 and c4 express both of these
requirements.
Rec. UIT-T X.733 (1992)/Amd.l(1995 F) 7

---------------------- Page: 11 ----------------------
ISO/CEI 10164-4 : 199WAmd.l : 1995 (F)
The supplier of the implementation shah specify support for management information in the agent role, in Table A.4.
Table A.4 - Agent raie minimum conformance requirement
Index Item Status Additional information
support Table reference
1 Communications alarm notification C5
2 Environmental alarm notification C5
Equipment alarm notification C5
3
4 Processing error alarm notification c5
5 Quality of service alarm notification c5
-
6 Alarm record managed abject class c6
c5: if A.Ulb then m else (if A.l/2a then 0.3 else -).
c6: if A.l/2a and A.5/la then m else -.
NOTES
1 Condition c6 makes it mandatory, if logging is supported, to support the event log records associated with the notifications
supported.
2 The Table reference column in this table is the notification reference of the MOCS supplied by the supplier of the managed
abject which claims to import the notification from this Recommendation I International Standard.
Table A.5 - Logging of event records
Addi tional
Index Status Support
information
1 Does the implementation support logging of event records in agent role? c7
c7: if A. 1/2a then o else -.
I I
NOTE 1 - Conformance to this Recommendation l International Standard does not require conformance to CCITT
Rec. X.735 I ISO/IEC 10164-6.
The supplier of the implementation shall provide information on claims of conformance to any of the Recommendations
I International Standards summarized in Tables A.6 to A.9. For each Recommendation I International Standard that the
supplier of the implementation claims conformance to, the corresponding conformance statement(s) shall be completed,
or referenced by, the MCS. The supplier of the implementation shall complete the Support, Table numbers and
Additional information columns.
In Tables A.6 to A.9, the Status column is used to indicate whether the supplier of the implementation is required to
complete the referenced tables or referenced items. Conformance requirements are as specified in the referenced tables
or referenced items and are not changed by the value of the MCS Status column. Similarly, the Support column is used
by the supplier of the implementation to indicate completion of the referenced tables or referenced items.
Table A.6 - PICS support summary
Identifica tion of the Table
Index 1 nTi!zrs 1 Description 1 Constraints 1 Status 1 Support Addi tional
LAC :,,1.Tl,, --
document tiiaL IIIUUUC;~ of pIcs numbers
information
and values
the PICS proforma
of PICS
proforma
I I l I
1 CCITT Rec. X.730 I
ISO/IEC 10164-l
NOTE 2 - Conformance to the MAPDUs defined in this Recommendation I International Standard cari be claimed by
completing the corresponding tables in the MICS and MOCS annexes of the referenced Recommendations I International Standards.
8 Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 12 ----------------------
ISOKEI 10164-4 : 199WAmd.l: 1995 (F)
Table A.7 - MOCS support summary
Table
Table
Identification of the
Additional
Constraints
Index numbers Description
StatUS SUPPO’ numbers
document that includes of MOCS
information
and values
the MOCS proforma of MOCS
proforma
1 CCITT Rec. X.733 I Annex C alarmRecord C8
a11 tables
ISO/IEC 10164-4
c8: if A.4/6a then m else -*
Table A.8 - MRCS support summary
Table
Table
Identification of the
Additional
Index numbers Description Constraints
StatUS SUPPO’ numbers
document that includes of MRCS
and values information
of MRCS
the MRCS proforma
proforma
Item D.l/l logRecord-log name - c9
1 CCITT Rec. X.735 I
binding
ISO/IEC 10164-6
c9: if A.5/la then o else -.
Table A.9 - MICS support summary
Table
Table
Identification of the
Additional
numbers Description Constraints Status Support numbers
Index
document that includes of MICS
and values information
of MICS
the MICS proforma
proforma
Table B. 1 notifications cl0
1 CCITT Rec. X.733 I
ISO/IEC 10164-4
cl1
2 CCITT Rec. X.733 I Tables B.2 management
and B.3 operations
ISO/IEC 10164-4
~10: if A.3/la or A.3/2a or A.3/3a or A.3/4a or A.3/5a then m else -*
cl 1: if A.3/6a then m else -.
9
Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 13 ----------------------
ISOKEI 10164-4 : 1992/Amd.l: 1995 (F)
Annexe B
Formulaire MICW
(Cette annexe fait partie intégrante de la présente Recommandation I Norme internationale)
Introduction
Bl .
The purpose of this MICS proforma is to provide a mechanism for a supplier of an implementation which claims
conformance, in the manager role, to management information specified in this Recommendation I International
Standard, to provide conformance information in a standard form.
B2 0 Instructions for complleting the MICS proforma to produce a MICS
The MICS proforma contained in this annex is comprised of information in tabular form, in accordance with ITU-T
Rec. X.724 I ISO/IEC 101656. In addition to the general guidance given in ITU-T Rec. X.724 I ISO/IEC 101656, the
Additional information column shall be used to identify the abject classes for which the management operations are
supported. The supplier of the implementation shall state which items are supported in the tables below and if necessary,
provide additional information.
Symbols, abbreviations and terms
B3 .
The following abbreviations are used throughout the MICS proforma:
dmi-att joint-iso-ccitt ms(9) smi(3) part2(2) attribute(7)
dmi-not joint-iso-ccitt ms(9) smi(3) part2(2) notification( 10)
The notations used for the Status and Support columns are specified in A. 1.3.
B4 . Statement of conformance to the management information
B.4.1 Notifications
The specifier of a manager role implementation that claims to support the notifications specified in this Recommendation
I International Standard shah import a copy of Table B.l and complete it.
Table B.l - Notification support
support
Value of abject
Non- Addi tional
Notification type Constraints
identifier for the S tatus
Index
and values Confirmed confirmed information
template label
notification type
-
(dmi-not 2) cl
1 communicationsAlarm
-
c2
2 environmentalAlarm ( dmi-not 3 )
-
3 equipmentAlarm (dmi-not 4) c3
-
4 processingErrorAlarm (dmi-not 10) c4
-
qualityOfServiceAla.rm (dmi-not 11) c5
5
cl: if A.3/la then m else -.
c2: if A.3/2a then m else -.
c3: if A.3/3a then m else -.
c4: if A.3/4a then m else -.
c5: if A.3/5a then m else -.
(continued)
5, Les utilisateurs de la présente Recommandation I Norme internationale sont autorisés à reproduire le formulaire MICS de la
présente annexe pour utiliser celui-ci conformement à son objet.
10 Rec. UIT-T X.733 (1992)/Amd.l(1995 F)

---------------------- Page: 14 ----------------------
ISOKEI 10164-4 : 1992/Amd.l: 1995 (F)
Table B.l (continued) - Notification support
Value of abject
identifier for the
Addi tional
Sub-index Notification field name label attribute type Constraints and values Status support
Index
information
associated with
the field
1 1.1 probablecause 1 (dmi-att 18) 1
1.1.1 globalValue 1 OBJECT IDENTIFIER m
I I
1.1.2 localvalue INTEGER m
I I I
specificProblems ( dmi-att 27)
1.2 required for some abjects
1.2.1 global
1.2.2 local INTEGER
I I
1.3 perceivedseverity 1 (dmi-att 17) 1 ENUMERATED 0 to 5
1.4 backedUpStatus 1 (dmi-att 11) 1 required for some abjects
1.5 backUpObject 1 (dmi-att 40) 1 for backUp relationships
1.51 distinguishedName
1.5.2 nonSnecificPorm
1.5.3 1ocalDistineuishedName 1 - I m
I
m
1.6 trendIndication 1 {dmi-att 30) 1 ENUMERATED o to 2
I
1.7 thresholdInfo 1 (dmi-att 29) 1 for threshold attributes m
I I l
1.7.1 triggeredThreshold m-- I I
I I
1.7.2 observedValue
I I
1.7.2.1 integer
I I
-
real 1 required for some abjects
1.7.2.2
1.7.3 thresholdlevel I l
1.7.3.1
UD I I
1.7.3.1.1 hieh I I m
I
1.7.3.1.1.1 integer m
I l I
1.7.3.1.1.2 real I I reauired for some obiects m
I
1.7.3.1.2 low for guage thresholds m
I
I
1.7.3.1.2.1 integer m
r--- I
I I
1.7.3.1.2.2 real 1 required for some abjects m
I
1.7.3.2 down m
I
I I
1.7.3.2.1 high m
I
1.7.3.2.1.1 integer m
I I I
1.7.3.2.1.2 real 1 required for some abjects m
I
1.7.3.2.2 low m
I I I
1.7.3.2.2.1 m
integer
I - I
1.7.3.2.2.2 real I I reauired for some obiects m
1 d
1.7.4 armTime m
1.8 notificationIdentifier 1 (dmi-att 16) 1 INTEGER m
/
~ 1.9 correlatedNotifications m
1 {dmi-att 12) 1
correlatedNotifications m
I I
sourceObjectInst m
I I
distinguishedName m
-
nonSnecificPorm m
1ocalDistineuishedName 1 - I m
(continued)
Rec. UIT-T X.733 (1992)/Amd.l(1995 F) 11

---------------------- Page: 15 ----------------------
ISOKEI 10164-4 : 1992/Amd.l : 1995 (F)
Table B.l (continued) - Notification support
Value of abject
identifier for the
Addi tional
Sub-index Notification field name label attribute type Constraints and values Status support
Index
information
associated wi th
the field
1 1.10 StateChangeDefinition (dmi-att 28) required for some abjects m
-
1.10.1 attributeId m
-
1.10.1.1 global OBJECT IDENTIFIER m
1.10.1.2 local INTEGER m
-
m
1.10.2 1 oldAttributeValue
I I I
1.10.3 1 newAttributeValue I m I I
1.11 monitoredAttributes (dmi-att 15) required for some abjects m
.
1.12 proposedRepairActions ( dmi-att 19 ) required for some abjects m
1.12.1 global OBJECT IDENTIFIER m
1.12.2 1 local INTEGER m
I I
1.13 additionalText (dmi-att 7) m
!
1.14 addi tionalInformation (dmi-att 6) required for some abjects m
-
2 2.1 probablecause (dmi-att 18) m
m
2.1.1 1 globalvalue 1 OBJECTIDENTIFIER 1
I I
1
2.1.2 1 localValue- INTEGER I-ii- 1
1 I I 1
specificProblems (dmi-att 27) required for some abjects m
2.2
2.2.1 global OBJECT IDENTIFIER m
I local INTEGER I m I
-
2.5.3 1ocalDistinguishedName m
I
I
.
m
2.6 trendIndication (dmi-att 30) 1 ENUMERATEDO to2 1
I
\
2.7 thresholdInfo (dmi-att 29) for threshold attributes m
- -
m
2.7.1 triggeredThreshold
2.7.2 observedValue m
I I
2.7.2.1
2.7.2.2
2.7.3
2.7.3.1
2.7.3.1.1
2.7.3.1.1.1 integer
2.7.3.1.1.2 real required for some abjects m
2.7.3.1.2 low for guage thresholds m
2.7.3.1.2.1 integer
2.7.3.1.2.2 real required for some abjects m
2.7.3.2 . down
J
-
2.7.3.2.1 l high m
2.7.3.2.1.1 integer m
1
2.7.3.2.1.2 real
required for some abjects m
-
2.7.3.2.2 low m
2.7.3.2.2.1 integer m
2.7.3.2.2.2 real required for some obiects m
(continued)
12 Rec. UIT-T X.733 (1
...

Questions, Comments and Discussion

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