ISO/IEC 10164-4:1992
(Main)Information technology — Open Systems Interconnection — Systems Management: Alarm reporting function — Part 4:
Information technology — Open Systems Interconnection — Systems Management: Alarm reporting function — Part 4:
Establishes user requirements for the alarm reporting function and a model that relates the service and generic definitions provided by this function to user requirements, defines the service provided by the function and generic notification types and parameters, specifies the protocol and the abstract syntax, defines the relationship between this service and SMI notifications, specifies compliance requirements placed on other standards that make use of these generic definitions, 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 signalisation des alarmes — Partie 4:
General Information
Relations
Standards Content (Sample)
INTERNATIONAL
ISO/IEC
STANDARD 10164-4
First edition
1992-12-15
Information technology - Open Systems
Interconnection - Systems Management: Alarm
reporting function
Technologies de I’information - Interconnexion de systemes ouverts -
Gestion-Systeme: Fonction de campte rendu d’alarme
~ -~
-
=
=
=
=
=
5
:
I
Z
=
=
=
=
EL
Reference number
Es -
c
!Tlizfl
__
p ISO/IEC 10164-4:1992 (E)
---------------------- Page: 1 ----------------------
ISO/IEC 10164-4 : 1992 (E)
Contents
1
1 Scope .
2
2 Normative rcl‘crcnces .
........... 2
2.1 Identical CCITT Recommendations I International Standards.
2.2 Paired CCITT Recommendations I International Standards
2
cyuivalent in technical content .
3
2.3 Additional refcrences .
3
3 Dcfinitions .
3
.......................................................
3.1 Basic reterencc model definitions
3
...................................................
3.2 Management framework detinitions
3
................................................................................
3.3 CMIS dcfïnitions
3
.........................................
3.4 Systems managcment overview def’initions
3
....................................
3.5 Evcnr report management function detinitions
4
....................................................
3.6 OS1 contormancc testing dcfinitions
4
.........................................................................
3.7 Additional definitions
4
4 Abhrcviations .
4
5 Convcntioni .
4
6 Rcquircments .
5
.........................................................................................................
7 Model
0 ISWEC 1992
All rights rescrved. No pt of this publication rnay bc rcproduced or utilized in my l’orrn or by any
IIIC;~IS, dcctronic or mcchmical, including photocopying and rnicrotiltn, without pcmission in writing
from thc publishur.
lSO/lEC Copyright Ol’l‘i~ . Gase postalt 56 l CH- 13 I 1 Gcnkvc 20 l Switzcr-lmd
Pr-intd in Switzer-lmd
ii
---------------------- Page: 2 ----------------------
ISO/IJX 10164-4 : 1992 (E)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8 Generic definitions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1 Generic notifications
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.2 Managed objects
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~. 11
8.3 Compliance
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9 Service definition
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1 Introduction
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 11
9.2 Alarm reporting Service
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
10 Functional units
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
11 Protocol
..................................................................... 12
1 1.1 Elements ot' procedure
................................................................................ 13
11.2 Abstract Syntax
16
1 1.3 Negotiation of the alarm reporting functional unit .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
12 Relationships with other functions
13 Conformance . 16
16
13.1 General conformance elass requirements .
..................................... 17
13.2 Depcndent conformance class requirements
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
ANNEX A Example Probable cause usage
. . .
Ill
---------------------- Page: 3 ----------------------
ISO/IEC10164-4:1992(E)
Foreword
ISO (the International Organization for Standardization) and IEC (thc International
Elcctrotechnical Commission) form the specializcd System for worldwide
standardization. National bedies that arc members of ISO or IEC participate in the
dcvelopment of International Standards through technical committees established by the
rcspectivc organization to deal with particular fiel& 01‘ technical activity. ISO and IEC
technical comnnittces collaboratc in fiel& of mutual interest. Other international
organizations, governmental and non-governInenta1, in liaison with ISO and IEC, also
takc part in the work.
In the field of information technology, ISO and IEC have established a joint technical
committee, ISO/lEC JTC 1. Draft International Standards adopted by thc joint tcchnical
committcc arc circulated to national bedies for voting Publication as an International
Standard rcquires approval by at least 75 % of the national bedies casting a vote.
International Standard ISO 10164-4 was prepared by Joint Technical Committee ISO/IEC
JTC 1, h/bwc~tion techology, in collaboration with the CCITT. The identical tcxt is
publishcd as CCITT Iieconnmendation X.733.
ISO/IEC 1 01 64 consists of the following Parts, under the general title Ir~fi,rwrcrtim
-
teclrnolog)~ Open Systems Interconnection - Systems Manngenien t:
- Pm-t 1: Ol?ject nlnrznger?ler2t.~4rzctioii
- Part 2: Stcltc ~zlarzcr~erlient.fCrnction
- Pm-t 3: AttributesjOr represedng rehtiomhips
- Pcrrt 4: Ah-m r-el’o,-ti,tg.lirllc:tio,z
-
Pm-t 5: Evcnt report rncrllcrge,llc~ll:.liuzctio,l
- h-t 6: Log <:olitr-oI.~ir,zctiori
- Pcrrt 7: Secw-ity crlcrrrlr reporting ji4rictioii
- Pm-t 8: Secnrity m4dit tt-~ril.ficllctioli
-- Pm-t 9: Ohjrcls nnci crttriLxrtesfi,r c~ccess corztrol
- Pcrrt IO: Accounting I)lete,-.firllctia,r2
- Pm-t 11: Werkload monitoring jimcth
- Part 12: Test mmmgeme~~ t jicmhn
- Pm-t 13: Sr4rllrrlcrr-i~nti012 ji4rictiori
- Pm-t 14: Con/idence nnd cliagwstic test cntegories
---------------------- Page: 4 ----------------------
ISO/IEC 10164-4 : 1992(E)
Introduction
ISO/IEC 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:
1990, Information technology - Open Systems
- ISO/IEC 9595 :
Interconnection - Common management informution Service definition;
- ISO/IEC 9596 : 1990, Information technology - Open Systems
Interconnection - Commun munagement information protocol;
- ISO/IEC 10040 : 1992, Information technology - Open Systems
Interconnection - Systems management overview;
- ISO/IEC 10165 : 1992, Information technology - Open Systems
Interconnection - Structure of management information.
V
---------------------- Page: 5 ----------------------
This page intentionally left blank
---------------------- Page: 6 ----------------------
ISO/IEC 10164-4 : 1992 (E)
INTERNATIONAL STANDARD
CCITT RECOMYMENDATION
INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION -
SYSTEMS MANAGEMENT: ALARM REPORTING FUNCTION
1 Scope
This Recommendation I International Standard defines a Systems Management Function that 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 7498-4. This Recommendation I International Standard
defines a function which consists of generic definitions, Services and functional units. This function is positioned in
the application layer of the OS1 reference model (CCITT 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 by CCITT Rec. X.701 I
ISO/lEC 10040. The alarm notifications defined by this function provides information that a manager may need to act
upon pertaining to a system’s operational condition and quality of Service.
This Recommendation i International Standard
establishes user requirements for the alarm reporting function;
-
establishes a model that relates the Service and generic definitions provided by this function to user
requirements;
defines the Service provided by the function;
-
defines generic notification types and Parameters documented in accordance with CCITT Rec. X.722 1
ISO/IEC 10165-4;
specifies the protocol that is necessary in Order to provide the Service;
-
specifies the abstract syntax necessary to identify and negotiate the functional unit in protocol;
-
defines the relationship between this Service and SM1 notifications;
specifies compliance requirements placed on other Standards that make use of these generic definitions;
-
defines relationships with other Systems management functions;
-
conformance requirements.
specifies
This Recommendation I International Standard does not
-
define the nature of any implementation intended to provide the Alarm Reporting function;
-
specify the manner in which management is accomplished by the user of the Alarm Reporting function;
-
define the nature of any interactions which result in the use of the Alarm Reporting function;
-
specify the Services necessary for the establishment, normal and abnormal release of a management
association;
-
preclude the defmition of further notifkation types;
define managed objects.
1
CCITT Rec. X.733 (1992 E)
---------------------- Page: 7 ----------------------
ISO/IEC 10164-4 : 1992 (E)
2 Normative references
The following CCITT 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 arc subject to revision, and Parties to agreements based on
this Recommendation I International Standard arc encouraged to investigate the possibihty of applying the most recent
editions of the Recommendations and Standards indicated below. Members of IEC and ISO maintain registers of
currently valid International Standards. The CCITT Secretariat maintains a list of the currently valid CCITT
Recommendations.
21 . Identical CCITT Recommendations I International Standards
-
CCITT Recommendation X.701 (1992) I ISO/IEC 10040 : 1992, Information technology - Open Systems
Interconnection - Systems management overview.
-
CCITT Recommendation X.731 (1992) I ISOIIEC 10164-2 : 1992, Information technology - Open
Systems Interconnection - Systems Management - State managementfiinction .
-
CCITT Recommendation X.732 (1992) I ISO/IEC 10164-3 : 1992, Information technology - Open
Systems Interconnection - Systems Management - Attributes for representing relationships.
-
CCITT Recommendation X.734l) I ISOLEC 10164-5 : 1992, Information technology - Open Systems
Interconnection - Systems Management - Event report managementfunction.
-
CCITT Recommendation X.720 (1992) I ISOIIEC 10165-1 : 1992, Information technology - Open
Systems Interconnection - Structure of management information - Management information model.
- CCITT Recommendation X.721 (1992) I ISOIIEC 10165-2 : 1992, Information technology - Open
- Structure of management information - Definition of management
Systems Interconnection
information.
-
CCITT Recommendation X.722 (1992) l ISO/IEC 10165-4 : 1992, Information technology - Open
- Structure of Management Information - Guidelines for the definition of
Systems Interconnection
managed objects.
22 l Paired CCITT Recommendations 1 International Standards equivalent in technical content
-
CCITT Recommendation X.7001) , Managementframework for Open systems Interconnection (OSI) for
CCI?T applications.
ISO/IEC 7498-4 : 1989, Information processing systems - Open Systems Interconnection - Basic
Reference Model - Part 4 : Management ji-amework.
-
CCITT Recommendation X.200 (1988), Reference Mode2 of Open Systems Interconnection for CCIlT
Applications.
ISO 7498 : 1984, Information processing systems - Open Systems Interconnection - Basic Reference
Model.
-
CCITT Recommendation X.208 (1988), Specification of abstract syntax notation one (ASN.1).
ISOIIEC 8824 : 1990, Information technology - Open Systems Interconnection - Specification of
Abstract Syntax Notation One (ASN.1).
-
CCITT Recommendation X.210 (1988), Reference Model of Open Systems Interconnection (0%) Layer
Service Definition Conventions for CCITT Applications.
ISO/TR 8509 : 1987, Information processing systems
- Open Systems Interconnection - Service
conventions.
-
CCITT Recommendation X.710 (1991), Common Management Information Service Definition for
CCITT Applications.
ISO/lEC 9595 : 1991, Information technology - Open Systems Interconnection - Common management
information Service definition.
‘) Presently at state of draft Recommendation.
2 CCITT- Rec. X.733 (1992 E)
---------------------- Page: 8 ----------------------
ISOAEC 10164-4 : 1992 (E)
-
CCITT Recommendation X.290 (1992), OSI Conformance Testing Methodology and Framework for
Protocol Recommendations for CCITT Applications - General Concepts.
ISOAEC 9646-1 : 199 1, Information technology - Open Systems Interconnection confo?mance testing
methodology andframework - Part 1: General concepts.
23 . Addi tional references
-
ISO/IEC 9545 : 1989, Information processing Systems - Open Systems Interconnection - Application
Layer structure.
3 Definitions
For the purposes of this Recommendation I International Standard, the following definitions apply.
31 . 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>
Systems management.
b)
Management framework definitions
32 .
Chis Recommendation I International Standard makes use of the following terms defined in CCITT Rec. X.700 I
ISOIIEC 7498-4.
managed Object
33 . CMIS definitions
This Recommendation I International Standard makes use of the following terms ‘defmed in CCITT Rec. X.710 I
ISO/IEC 9595.
attribute
34 . Systems management overview definitions
This Recommendation I International Standard makes use of the following terms defined in CCITT Rec. X.701 I
ISO/IEC 10040.
agent;
a>
agent role;
b)
dependent conformance;
C>
d) general conformance;
e) generic defiiitions;
manager;
0
g) manager role;
h) notification;
Systems managemen t application protocol;
.
Systems management functional unit.
J)
35 . Event report management function definitions
This Recommendation I International Standard makes use of the following terms defined in CCITT Rec. X.734 I
ISO/IEC 10164-5.
event forwarding discriminator
CCITT Rec. X.733 (1992 E) 3
---------------------- Page: 9 ----------------------
ISO/IEC 10164-4 : 1992 (E)
36 . OS1 conformance testing defipitions
This Recommendation I International Standard makes use of the following terms defined in CCITT Rec. X.290 I
ISOIIEC 9646- 1.
System conformance Statement
37 l Additional definitions
For the purposes of this Recommendation I International Standard, the following definitions apply.
3.7.1 error: A deviation of a System from normal Operation.
3.7.2 fault: The physical or algorithmic Cause of a malfunction. Faults manifest themselves as errors.
3.7.3 alarm: A notification, of the form defined by this function, of a specific event.
An alarm may or may not
represent an error.
3.7.4 alarm report: A specific type of event report used to convey alarm information.
4 Abbreviations
ASN. 1 Abstract Syntax Notation One
CMIS Common Management Information Service
Conf Confinn
Ind Indication
MAPDU Management Application Protocol Data Unit
Request
Req
Response
RsP
SMAPM Systems Management Application Protocol Machine
5 Conventions
This Recommendation I International Standard defines Services following the descriptive conventions defined in
CCITT Rec. X.210 I ISO/TR 8509. In clause 9, the definition of each Service includes a table that lists the Parameters
of its primitives. For a given primitive, the presence of each Parameter is described by one of the following values
M the Parameter is mandatory
-
the value of the Parameter is equal to the value of the Parameter in the column to the left
t-9
U
the use of the Parameter is a service-user Option.
-
the Parameter is not present in the interaction described by the primitive concemed.
C the Parameter is conditional. The condition(s) arc defined by the text which describes the
Parameter.
P subject to the constraints imposed on the Parameter by CCITT Rec. X.710 I ISO/IEC 9595.
NOTE - The Parameters which are marked ‘2”’ in Service tables of this Recommendation I International Standard are
mapped directly onto the corresponding Parameters of the CMIS Service primitive, without changing the semantics or Syntax of the
Parameters. The remaining Parameters are used to construct an MAPDU.
6 Requirements
The requirements satisfied by this function are the reporting of alarms, errors and related information, in a Standard
fashion.
CCITT Rec. X.733 (1992 E)
4
---------------------- Page: 10 ----------------------
ISO/IEC 10164-4 : 1992 (E)
7 Model
Early detection of faults before significant effects have been felt by the user is a desirable requirement
of communicating Systems. Degradation of Service may be detected by monitoring of error rates. Threshold
mechanisms on counters and gauges are a method of detecting such trends and providing a waming to managers when
the rate becomes high.
An importam criterion by which failures of communications resources are to be reported is the level to which the fault
degrades the quality of the Service that was originally requested by (or promised to) the Service User. Malfunctions
will range in severity from Waming, where there is no impact upon the quality of Service offered to the User, to
Critical, where it is no longer possible to provide the Service requested by (or promised to) the Service User. The level
of severity tan be described generically and ctiteria specified based upon the level of degradation that the fault causes
to the Service: Critical, Major, Minor or Warning.
Alarms are specific types of notifications conceming detected faults or abnormal conditions. Managed Object defmers
are encouraged to include in alarms information that will help with understanding the Cause of the potentially
abnormal Situation, and other information related to side effects. An example of such diagnostic information is the
current and past values of the configuration management state of the Object.
A Single incident may Cause the generation of several notifications; it is important to be able to specify in a
notification some correlation with other notifkations. However, the mechanism, if any, for determining the
relationship between notifications resulting from a Single incident is outside the scope of this function.
It is considered important in some circumstances to provide alarm reports with a standardized style, using a common
set of notification types, with standardized Parameters and Parameter definitions, independent of particular managed
objects. The notification types specified in this function are intended to be generally applicable and tan be imported
into the definition of any managed Object.
Control of notifications, e.g. whether a notification results in an event report, may be accomplished by use of the Event
Report management function defined in CCITT Rec. X.734 I ISO/IEC 10164-5.
8 Generic definitions
. Generic notifications
81
The set of generic notifications, Parameters and semantics defined by this Recommendation I International Standard
provide the detail for the following general Parameters of the M-EVENT-REPORT Service as defined by CCITT
Rec. X.710 I ISO/IEC 9595
-
event type;
-
event in formation;
-
event reply.
All notifications are potential entries in a Systems management log and this Recommendation I International Standard
defines a managed Object class for this purpose. CCITT Rec. X.721 l ISO/IEC 10165-2 defines a generic event log
record Object class from which all entries are derived, the additional information being specified by the event
information and event reply Parameters.
8.1.1 Event type
This Parameter categories the alarm. Five basic categories of alarm are specified. These are
-
communications alarm type: An alarm of this is principally associated with the procedures and/or
tYPe
processes required to convey information from one Point to another;
-
quality of Service alarm type: An alarm of this type is principally associated with a degradation in tbe
quality of a Service;
-
processing error alarrn type: An alarm of this type is principally associated with a softwar-e or processing
fault;
-
equipment alarm type: An alarm of this type is principally associated with an equipment fault;
-
environmental alarm type: An alarm of this type is principally associated with a condition relating to an
enclosure in which the equipment resides.
5
CCITT Rec. X.733 (1992 E)
---------------------- Page: 11 ----------------------
ISO/IEC 10164-4 : 1992 @)
8.1.2 Event information
The following Parameters constitute the notification specific information.
8.1.2.1 Probable Cause
This Parameter defines further qualification as to the probable Cause of the alarm. Probable Cause values for
notifications shall be indicated in the behaviour clause of the Object class defmition. This Recommendation 1
International Standard defines, for use within the Systems management application context defined in CCITT X.701 I
ISO/IEC 10040, Standard Probable Causes that have wide applicability across managed Object classes. These values
are registered in CCITT X.721 I ISO/IEC 10165-2. The syntax of Standard Probable Causes shall be the ASN.l type
Object identifier. Additional Standard Probable Causes, for use within the Systems management application context
defined in CCITT X.701 l ISO/IEC 10040, may be added to this Recommendation l International Standard and
registered using the registration procedures defined for ASN.1 Object identifier values in CCITT Rec. X.208 I
ISOIIEC 8824.
Other Probable Causes, for use within the Systems management application context defined in CCITT X.701 I
ISO/IEC 10040, may be defined outside of this Recommendation I International Standard and registered using the
procedures defined for ASN.l Object identifier values in CCITT Rec. X.208 I ISO/IEC 8824.
Probable Causes may be defined for use outside of the Systems management application context; the Syntax of such
Probable Causes shall be either an ASN. 1 Object identifier or ASN. 1 type integer.
The managed Object class definer should choose the most specific Probable Cause applicable.
This Recommendation I International Standard defines the following Probable Causes
-
adapter error;
-
application Subsystem failure: A failure in an application Subsystem has occurred (an application
Subsystem may include Software to support the Session, Presentation or Application layers);
-
bandwidth reduced: The available transmission bandwidth has decreased;
-
cal1 establishment error: An error occurred while attempting to establish a connection;
-
communications protocol error: A communication protocol has been violated;
-
communications Subsystem failure: A failure in a Subsystem that supports communications over
telecommunications links, these may be implemented via leased telephone lines, by X.25 networks,
token-ring LAN, or otherwise;
-
configuration or customization error: A System or device generation or customization Parameter has
been specified incorrectly, or is inconsistent with the actual configuration;
-
congestion: A System or network component has reached its capacity or is approaching it;
-
corrupt data: An error has caused data to be incorrect and thus unreliable;
-
CPU cycles limit exceeded: A Central Processing Unit has issued an unacceptable number of
instructions to accomplish a task;
-
dataset or modern error: An intemal error has occurred on a dataset or modern;
-
degraded Signal: The quality or reliability of transmitted data has decreased;
- DTE-DCE interface error: A Problem in a DTE-DCE interface, which includes the interface between the
DTE and DCE, any protocol used to communicate between the DTE and DCE and information provided
by the DCE about the circuit;
enclosure door open;
-
equipmen t malfunction: An in temal machine error has occurred for which no
more specific Probable
Cause has been identified;
-
excessive Vibration: Vibratory or seismic limits have been exceeded;
-
file error: The formst of a file (or set of files) is incorrect and thus cannot be used reliably in processing;
-
fire detected;
-
flood detected;
framing error: An error in the information that delimits the bit groups within a continuous stream of bits;
-
heating/ventilation/cooling System Problem;
CCITT Rec. X.733 (1992 E)
---------------------- Page: 12 ----------------------
ISOiKEC 10164-4 : 1992 (E)
humidity unacceptable: The humidity is not within acceptable limits; .
I/O device error: An error has occurred on the VO device;
input device error: An error has occurred on the input device;
LAN error: An error has been detected on a local area network;
leak detected: A leakage of (non-toxic) fluid or gas has been detected;
local node transmission error: An error occurred on a cornm unications channel between the local node
and an adjacent node;
-
10~s of frame: An inability to locate the information that delimits the bit grouping within a continuous
stream of bits;
loss of Signal: An error condition in which no data is present on a communications circuit or channel;
material supply exhausted: A supply of needed material has been exhausted;
multiplexer Problem: An error has occurred while multiplexing communications Signals;
out of memory: There is no program-addressable storage available;
output device error: An error has occurred on the output device;
performante degraded: Service agreements or Service limits are outside of acceptable limits;
power Problem: There is a Problem with the power supply for one or more resources;
pressure unacceptable: A fluid or gas pressure is not within acceptable limits;
processor Problem: An intemal machine error has occurred on a Central Processing Unit;
-
pump failure: Failure of mechanism that transports a fluid by inducing pressure different& within the
fluid;
-
queue size exceeded: The number of items to be processed (configurable or not) has exceeded the
maximum allowable;
-
receive failure;
-
receiver failure;
-
remote node transmission error: An error occurred on a communication channel beyond the adjacent
node;
-
resource at or nearing capacity: The usage of a resource is at or nearing the maximum allowable
capacity;
-
response time excessive:
The elapsed time between the end of an inquiry and beginning of the answer to
that inquiry is acceptable limits;
outside of
retransmission rate excessive: The number of repeat transmissions is outside of acceptable limits;
Software error: A Software error has occurred for which no more specific Probable Cause tan be
identified;
-
Software program abnormally terminated: A Software program has abnormally terminated due to some
unrecoverable error condition;
-
Software program error: An error has occurred within a Software program that has caused incorrect
results;
storage capacity Problem: A storage device has very iittle or no space available to store additional data;
temperature unacceptable: A temperature is not within acceptable limits;
threshold crossed: A limit (configurable or not) has been exceeded;
timing Problem: A process that requires timed execution and/or Coordination cannot complete, or hciS
completed but cannot be considered reliable;
-
toxic leak detected: A leakage of toxic fluid or gas has been detected;
-
transmit failure;
-
transmitter failure;
CCITT Rec. X.733 (1992 E) 7
---------------------- Page: 13 ----------------------
ISO/IEC 10164-4 : 1992 (E)
-
underlying resource unavailable: An entity upon which the reporting Object depends has become
unavailable;
-
communicating
version mismatch: There is a conflict in the functionality of Versions of two or more
entities which may affe
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.