GB/T 17143.4-1997 Information technology Open Systems Interconnection System management Part 4: Alarm reporting function
Some standard content:
GB/T 17143.4—1997
This standard is equivalent to ISO/IEC10164-4:1992 "Information Technology Open Systems Interconnection System Management: Alarm Reporting Function" and ISO/IEC10164-4:1992/Cor.1:1994 "Information Technology Open Systems Interconnection System Management: Alarm Reporting Function Technical Modification 1".
According to ISO/IEC10164-4:1992/Cor.1:1994, this standard deletes the restrictions on notes in 8.1.2.12. GB/T17143, under the general title of "Information Technology Open Systems Interconnection System Management", currently includes the following 8 parts: Part 1 (i.e. GB/T17143.1): Object management function Part 2 (i.e. GB/T17143.2): State management function Part 3 (i.e. GB/T17143.3): Attributes representing relationships Part 4 (i.e. GB/T17143.4): Alarm reporting function Part 5 (i.e. GB/T17143.5): Event report management function Part 6 (i.e. GB/T17143.6): Log control function Part 7 (i.e. GB/T17143.7): Security alarm reporting function Part 8 (i.e. GB/T17143.8): Security audit tracking function Appendix A of this standard is a prompt appendix.
This standard was proposed by the Ministry of Electronics Industry of the People's Republic of China. This standard is under the jurisdiction of the Standardization Institute of the Ministry of Electronics Industry. Drafting unit of this standard: Standardization Institute of the Ministry of Electronics Industry. The main drafters of this standard are Zheng Hongren, Zhou Xiaohua and Cao Dongqi. 516
GB/T17143.4—1997
ISO/IEC Foreword
ISO (International Organization for Standardization) and IEC (International Electrotechnical Commission) are worldwide specialized standardization organizations. National member bodies (all of which are members of ISO or IEC) participate in the formulation of international standards for specific technical scopes through various technical committees established by international organizations. The technical committees of ISO and IEC cooperate in areas of common interest. Other official and non-official international organizations in contact with ISO and IEC can also participate in the formulation of international standards. For information technology, ISO and IEC have established a joint technical committee, namely ISO/IECJTC1. The draft international standard proposed by the joint technical committee needs to be circulated to national member bodies for voting. To publish an international standard, at least 75% of the national member bodies participating in the vote need to vote in favor.
ISO/IEC10164-4 was developed by the ISO/IECJTC1\Information Technology" Joint Technical Committee in cooperation with CCITT. The equivalent text is CCITT X.733.
ISO/IEC10164 is under the general title of "Information Technology Open Systems Interconnection System Management" and currently includes the following 14 parts: Part 1: Object management function
Part 2: State management function
Part 3: Attributes representing relationships
-Part 4: Alarm reporting function
Part 5: Incident report management function
Part 6: Log control function
-Part 7: Security alarm reporting function
-Part 8: Security audit trail function
Part 9: Objects and attributes of access control Part 10: Accounting and metering functions Part 11: Workload monitoring functions Part 12: Test management functions Part 13: Summarization functions Part 14: Reliability and diagnostic test classification 517 GB/T17143.4—1997 GB/T17143 is a standard consisting of multiple parts formulated in accordance with GB9387 and GB/T9387.4. GB/T17143 is related to the following standards: GB/T 16644
GB/T 17142
GB/T 17175
GB/T16645
Information technology
Information technology
Information technology
Information technology
Open systems interconnection
Open systems interconnection
Open systems interconnection
Open systems interconnection
Public management information service definition
Systems management overview
Management information structure
Public management information protocol
1 Scope
National Standard of the People's Republic of China
Information technology-Open Systems Interconnection
Systems management
Part 4: Alarm reporting functionGB/T17143.4—1997
idtISO/IEC 10164-4:1992
This standard defines a system management function for application processes to interact in a centralized or decentralized management environment for system management as defined in GB/T9387.4. This standard defines a function, which consists of class definitions, services and functional units. This function belongs to the application layer of the OSI reference model (GB9387) and is defined according to the model provided by GB/T17176. The role of the system management function is described by GB/T17142. The alarm notifications defined by this function provide information about system operating conditions and service quality, and managers may need to act accordingly.
This standard
Establishes user requirements for the alarm reporting function, establishes a model that links the services and generic definitions provided by this function with user requirements, and defines the services provided by this function;
Defines generic notification types and parameters compiled according to GB/T17175.4, - specifies the protocol necessary to provide the service; - specifies the abstract syntax necessary to identify and negotiate functional units in the protocol; - defines the relationship between this service and SMI notifications; - specifies the requirements that other standards that use these generic definitions should comply with; - defines the relationship with other system management functions; - specifies consistency requirements.
This standard
Does not define the characteristics of any implementation intended to provide the alarm reporting function; - does not specify the way management is completed by the user of the alarm reporting function; - does not define any characteristics of the interaction that leads to the use of the alarm reporting function; - does not specify the services necessary to establish, normal release and abnormal release management connections, does not exclude the definition of further notification types, and does not define managed objects.
2 Referenced standards
The provisions contained in the following standards constitute the provisions of this standard through reference in this standard. When this standard is published, the versions shown are valid. All standards will be revised. Parties using this standard should explore the possibility of using the latest versions of the following standards. GB9387-88 Information Processing System Open System Interconnection Basic Reference Model (idtISO7498:1984,eqvCCITTX.200:1988)
Approved by the State Administration of Technical Supervision on December 15, 1997 and implemented on August 1, 1998
GB/T 17143. 4- 1997
GB/T9387.4-1996 Information Processing Systems Open Systems Interconnection Basic Reference Model Part 4: Management Framework (idtISO/IEC7498-4:1989,eqvCCITTX.700:1992)GB/T15129-94
Information Processing Systems Open Systems Interconnection Service Agreement (idtISO/TR8509:1987,eqvCCITTX.210:1988)
GB/T16262-1996 Information Technology Open Systems Interconnection Abstract Syntax Notation One (ASN.1) Specification (idtISO/IEC8824:1990,eqvCCITTT X.208:1988)GB/T16263--1996 Information technology Open Systems Interconnection Abstract Syntax Notation (ASN.1) Basic Encoding Rules Specification (idtISO/IEC8825:1990,eqvCCITTX.209:1988)GB/T16644-1996 Information technology Open Systems Interconnection Common Management Information Service Definition (idtISO/IEC9595:1991,eqvCCITT X.710:1991)
GB/T17142-1997 Information technology Open Systems Interconnection System Management Overview (idtISO/IEC10040:1992)GB/T 17143.2—1997
Information technology Open Systems Interconnection System management Part 2: State management functions (idtISO/IEC 10164-2:1993)
GB/T 17143.3-1997
Information technology Open Systems InterconnectionbzxZ.net
System management Part 3: Attributes representing relationships (idtISO/IEC 10164-3:1993)
GB/T 17143.5—1997
Information technology Open Systems Interconnection
System management Part 5: Event reporting management functions (idtISO/IEC 10164-5:1993)
GB/T 17175.1—1997
Information technology Open Systems Interconnection
ISO/IEC 10165-1:1993)
GB/T 17175.2—1997
Information technology Open Systems Interconnection
ISO/IEC 10165-2:1992)
Part 1: Management information model (idt
Management information structure
Management information structure
Part 2 Management information definitions (idt
Information technology Open Systems Interconnection Management information structure Part 4: Definitions of managed objects GB/T 17175. 4—1997↑
South (idt ISO/IEC10165-4:1992)
GB/T17176-1997 Information technology Open systems interconnection Application layer architecture (idtISO/IEC9545:1994) GB/T17178.1-1997 Information technology Open systems interconnection - Conformance test methods and framework Part 1: Basic concepts (idt ISO/IEC 9646-1:1994)
3 Definitions
This standard adopts the following definitions.
3.1 Basic reference model definition
This standard adopts the following terms defined in GB9387: a) open system;
b) system management.
3.2 Management framework definition
This standard adopts the following terms defined in GB/T9387.4: managed object.
3.3 CMIS Definition
This standard adopts the following terms defined in GB/T16644: attribute.
3.4 System Management Overview Definition
This standard adopts the following terms defined in GB/T17142: a) agent;
b) agent role;
c) subordinate consistency;
d) general consistency;
e) generic definition;
f) manager;
g) manager role;
h) notification,
i) system management application protocol;
j) system management functional unit.
3.5 Event Report Management Function Definition
GB/T17143.4—1997
This standard adopts the following terms defined in GB/T17143.5: event forwarding discriminator.
3.6 OSI Conformance Test Definitions
This standard adopts the following terms defined in GB/T17178.1: System Conformance Statement.
3.7 Supplementary Definitions
This standard adopts the following definitions.
3.7.1 Error
Deviation of the system from normal operation.
3.7.2 Fault
Incorrect operation due to physical or algorithmic reasons. Faults manifest as errors. 3.7.3 Alarm
Notification of a specific event, in the form defined by this function. An alarm may or may not represent an error. 3.7.4 Alarm Report
A specific type of event report used to transmit alarm information. 4 Abbreviations
5 Conventions
Abstract Syntax Notation -
Common Management Information Service
Management Application Protocol Data Unit
System Management Application Protocol Unit
This standard defines services following the descriptive conventions defined in GB/T15129. In Chapter 9, the definition of each service includes a table listing its primitive parameters. For a given primitive, the presence of each parameter is described by one of the following values: M The parameter is mandatory;
(i) The parameter value is equal to the value of the parameter in the left column; U The use of this parameter is an option for the service user; This parameter does not exist in the interaction described by this primitive; The parameter is conditional, and the condition is defined by the text describing the parameter. C
GB/T 17143. 4—1997
P The parameter is subject to the mandatory constraints of GB/T16644. Note: The parameters marked with "P\" in this standard service table are directly mapped to the corresponding parameters of the CMIS service primitives without changing the semantics or syntax of the parameters. The remaining parameters are used to construct MAPDU. 6 Requirements
The requirement met by this function is a standard form of alarm reporting, errors and related information. 7 Model
Early detection of failures before users feel significant consequences is a desirable requirement for communication systems. By monitoring the error rate, degradation of service quality can be detected. Threshold mechanisms on counters and meters detect this trend and warn managers when the error rate becomes high.
An important criterion for reporting communication resource failures is to what level the failure reduces the service quality from the original user demand (or promised to the user). The severity of the failure can be determined from the warning (this Faults can be classified as critical, major, minor or warning, depending on the level of degradation in service quality caused by the fault. An alarm is a specific type of notification related to the detection of a fault or abnormal situation. It is best to include the managed object definer in the alarm information, which will help to clarify the cause of the potential abnormal situation, as well as other information related to side effects. An example of such diagnostic information is the current and past values of the configuration management state of an object. A single event may cause several notifications to be generated, and it is important to be able to indicate in one notification the correlation with other notifications. However, the mechanism for determining the relationship between the various notifications caused by a single event is beyond the scope of this function. In some cases, it is considered necessary to send a notification in a standardized manner. It is important to provide alarm reporting, i.e. using a common set of notification types, with standardized parameters and parameter definitions, independent of the specific managed object. The notification types specified in this function will be universally applicable and can be introduced into any managed object definition.
Control of notifications, such as whether a notification results in an event report, can be accomplished using the event reporting management function defined in GB/T 17143.5.
8 Generic Definitions
8.1 Generic Notifications
The set of generic notifications, parameters and semantics defined by this standard details the following general parameters of the M-EVENT-RE-PORT service defined by GB/T 16644:
—Event Type,
—Event Information,
—Event Response.
|All notifications are potential items in the system management log, and this standard defines a managed object class for this purpose. GB/T17175.2 defines a generic event log record object class from which all items are derived, additional information specified by the event information, and event response parameters. 8.1.1 Event type
This parameter classifies alarms and specifies five basic alarm categories. They are: - Communication alarm type: This type of alarm is in principle related to the procedures and (or) processes required to transport information from one point to another; - Quality of service alarm type: This type of alarm is in principle related to reduced service quality; - Processing error alarm type: This type of alarm is in principle related to software or processing failures; - Equipment alarm type: This type of alarm is in principle related to equipment failures; - Environmental alarm type: This type of alarm is in principle related to the environmental conditions in which the equipment is located. 8.1.2 Event information
The following parameters constitute notification specific information.
8.1.2.1 Possible Causes
GB/T17143.4-—1997
This parameter defines further limitations for the possible causes of an alarm. The possible cause values for the notification shall be specified in the behavior clause of the object class definition. For use in the context of system management applications defined in GB, T17142, this standard defines standard possible causes that have broad applicability to managed object classes. These values are registered in GB/T17175.2. The syntax of the standard possible causes shall be ASN.1 Type object identifier. For use within the context of system management applications defined in ISO 17142, additional standard possible causes may be added to this standard and registered using the registration procedures defined in ISO 16262 for ASN.1 object identifier values. For use within the context of system management applications defined in ISO 17142, other possible causes may be defined outside of this standard and registered using the registration procedures defined in ISO 16262 for ASN.1 object identifier values. For use outside of the context of system management applications, some possible causes may also be defined, the syntax of such possible causes being either ASN.1 object identifiers or ASN.1 type integers. Managed object class definers should select the most specific possible cause available. This standard defines the following possible causes:
Adapter error:
Application subsystem failure: A failure occurred in the application subsystem (an application subsystem may include software supporting the session layer, presentation layer, and application layer);
Bandwidth reduction: The available transmission bandwidth has been reduced; Call establishment error: An error occurred while trying to establish a connection; Communication protocol error: The communication protocol was violated; Communication subsystem failure: A failure in the subsystem that supports communication on a remote communication link (which can be achieved by an X.25 network, a token ring local area network, or other network through a leased telephone line); Configuration or setting Control error: the generation or customization parameters of a system or device are incorrectly specified or are inconsistent with the actual configuration. Congestion: a system or network element has reached or is approaching its capacity. Corrupted data: an error has caused the data to become incorrect and therefore unreliable. Exceeded CPU cycle limit: the number of instructions issued by the central processing unit to complete a task is unacceptable. Data transmitter or modem error: an internal error has occurred in the data transmitter or modem. Degraded signaling: the quality or reliability of the data sent has been reduced. -DTE-DCE interface error: there is a problem in the DTE-DCE interface. The interface includes the interface between DTE and DCE, the communication protocol between DTE and DCE, and the information about the circuit provided by DCE; the closed door opens;
equipment failure: an internal machine error has occurred for which no more specific possible cause has been identified; excessive vibration: the vibration or earthquake limit has been exceeded, file error: the format of the file (or file collection) is incorrect and cannot be used reliably in processing: fire is detected,
flood is detected,
a frame synchronization error: in the continuous ratio Error in delimitation information for bit groups in the special stream; Problem with the heating/ventilation/cooling system;
Unacceptable humidity: Humidity is not within acceptable limits; -1/0 device error: An error occurred on the 1/0 device, -Input device error: An error occurred on the input device: -LAN error: An error was detected on the local area network: Leak detected: A (non-toxic) liquid or gas leak was detected: -Local node transmission error: An error occurred on the communication channel between the local node and the adjacent node, 523
GB/T 17143.4— 1997
Frame loss: the inability to locate information that delimits groups of bits in a continuous bit stream; signal loss: an error condition in which no data exists on a communications circuit or channel; a supply exhausted: a required supply has been exhausted; a multiplexer problem: an error occurs when multiplexing communications signals; a memory full: no addressable memory is available; an output device error: an error occurs on an output device; performance degradation: the service agreement or service limit exceeds acceptable limits; a power problem: a power problem exists for one or more resources; a voltage drop: a voltage drop is too high; a power problem occurs when a communication signal is multiplexed; a power failure: a power failure ... Unacceptable force: Fluid or gas pressure is not within acceptable limits, - Processor problem: An internal machine error occurred in the central processing unit, - Pump failure: A failure occurred in the mechanism that transfers fluids based on pressure differences within the fluids, - Queue size exceeded: The number of items to be processed (configurable or non-configurable) exceeds the maximum allowed number, - Receive failure;
Receiver failure;
- Remote node transmission error: An error occurred on the communication channel beyond the adjacent node, - Resource at or near capacity: The use of a resource is at or near the maximum allowed capacity, - Response time Exceeded: the time taken between the end of an inquiry and the start of answering this inquiry exceeds acceptable limits; Retransmission rate exceeded: the number of repeated transmissions exceeds acceptable limits; - Software error: a software error occurred for which no more specific possible cause was identified, - Abnormal termination of a software program: the software program terminated abnormally due to some unrecoverable error condition, - Software program error: an error occurred in the software program, resulting in incorrect results, - Storage capacity problem: the storage device has little or no available space to store additional data, - Unacceptable temperature: the temperature is not within acceptable limits; - A threshold limit (configurable or non-configurable) has been exceeded; - Timing problem: a process that requires timed execution or coordination cannot be completed, or has been completed but cannot be considered reliable; - Toxic leak detected: a toxic fluid or gas leak has been detected; - Transmission failure;
Transmitter failure;
- A resource located below is unavailable: the entity on which the reporting object depends has become unavailable, - Version mismatch: the versions of two or more communicating entities conflict in functionality, which may affect any processing involving these entities.
8.1.2.2 Specific Problem
When this parameter is present, it specifies more precise details for the possible cause of the alarm. This parameter qualifies the possible causes selected and can be used by a managed object class definer to specify a set of identifiers to be used in the managed object class. This parameter can be either a set of integers or a set of object identifiers. However, only object identifiers can be used in the system management context defined by ISO/IEC 16262. These object identifiers can be registered outside of this standard using the registration procedures defined in ISO/IEC 16262 for ASN.1 object identifier values.
8.1.2.3 Perceived Severity
This parameter defines six severity levels that provide the degree to which the capabilities of the managed object are perceived to be affected. These severity levels represent service-impacting conditions in the order from most severe to least severe: critical, major, minor, and warning. The levels defined with this mandatory parameter are: - Cleared: The "cleared" severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this managed object with the same alarm type, probable cause and specific problem (if given). Multiple related notifications may be cleared using the associated notification parameters (defined below).
GB/T17143.4—1997
This standard does not require re-reporting of cleared alarms. Therefore, a management system cannot assume that the absence of alarms with a severity level of "cleared" means that the conditions that caused the previous alarm to be generated still exist. The managed object definer should specify whether and under what conditions the severity level of "cleared" is used. - Uncertain: The severity level of "uncertain" indicates that the severity cannot be determined. - Critical: The severity level of "critical" indicates that a condition affecting service has occurred and that immediate corrective action is required. This severity level may be reported, for example, when a managed object has become completely out of service and its capabilities must be restored. - Major: The severity level of "major" indicates that a condition affecting service has developed and that urgent corrective action is required. This severity level may be reported, for example, when the capabilities of a managed object are severely degraded and full capabilities must be restored. - Minor: A minor severity level indicates that a non-service-affecting fault condition exists and that corrective action should be taken to prevent a more severe fault (i.e., service-affecting). This severity level may be reported, for example, when a detected alarm condition does not currently degrade the capabilities of a managed object.
- Warning: A warning severity level indicates that a potential or imminent service-affecting fault has been detected before any significant impact is felt. To prevent it from becoming a more severe service-affecting fault, action should be taken to further diagnose (if necessary) and correct the problem. 8.1.2.4 Backed-up Status
When this parameter is present, it specifies whether the object sending the alarm has been backed up and thus whether the service provided to the user has been interrupted. Use this field in conjunction with the severity field to provide a separate form of information to qualify the severity of the alarm and the ability of the system as a whole to continue to provide service. If this parameter value is true, it indicates that the object sending the alarm has a backup, if false, the object is not backed up. 8.1.2.5 Backup Object
This parameter is present when the Backup Status parameter is present and its value is true. This parameter specifies the managed object instance that provides backup services for the managed object associated with the notification. This parameter is useful, for example, when the backup object is from a group of objects, any one of which can be dynamically assigned to replace a failed object.
The Backup Object parameter is related to the Backup Object Relationship attribute defined in ISO 17143.3. When an alarm is sent, the value of this parameter shall be the same as the Backup Object attribute value.
8.1.2.6 Trend Indication
When this parameter is present, it specifies the current severity trend of the managed object. If present, it indicates that there are one or more alarms that have not been cleared ("pending alarms") and that such alarms ("current alarms") and they all belong to the same managed object. The Trend Indication parameter has the following three possible values:
- More severe: The perceived severity in the current alarm is higher (more severe) than that reported in any pending alarm;
- No change: The perceived severity reported in the current alarm is the same as the highest (most severe) pending alarm;
- Less severe: At least one pending alarm is of higher (more severe) severity than the current alarm. For Trend Indication to be meaningful, the Perceived Severity parameter for each alarm that may be sent by a managed object must be defined consistently for all alarm types defined for that managed object. Trend Indication information is particularly useful to management systems that receive alarm reports from event forwarding discriminators that are configured to pass alarms of the perceived severity level mentioned above. Severity trends may also be determined by a management system that monitors the Perceived Severity parameter in received alarm reports. If there are no pending alarms, the Trend Indication parameter is not present. Without the trend indication parameter, it cannot be used to indicate the presence or absence of pending alarms. 8.1.2.7 Reading Information
This parameter shall be present when the alarm is the result of a threshold crossing. It consists of four sub-parameters: - Triggering Threshold; Value Attribute Identifier that caused the notification. - Threshold Level: For a meter, the reading level specifies a pair of thresholds; the first of which is the value of the threshold that was crossed and the second is its corresponding hysteresis. For a counter, the threshold level specifies only the value of the threshold. - Observed Value: The meter or counter value that crossed the threshold. It may be different from the threshold value, for example, if the meter can only take on discrete 525
values.
GB/T 17143.4—1997
- Arming Time: For a meter reading, this is the time when the reading was last re-armed, i.e. the time after the last threshold crossing has exceeded the threshold hysteresis value, thus allowing notification to be generated again when the threshold is crossed. For counter thresholds, this is the later of the time when the threshold offset was last used or the time when the counter was last initialized (for resettable counters). 8.1.2.8 Notification Identifier
When this parameter is present, it provides an identifier for the notification, which may be carried in the Correlation Notification parameter (see below) of future notifications. Notification identifiers shall be chosen to be unique for all notifications of a particular managed object over the entire time that correlation is meaningful. A notification identifier may be reused if there is no requirement that a previous notification using that notification identifier be correlated with a future notification. In general, notification identifiers should be chosen to ensure uniqueness to the managed system over a potentially long period of time. 8.1.2.9 Related Notifications
When this parameter is present, it contains a set of notification identifiers and, if necessary, the object instance names to which they are related. The set is defined as the set of all notifications that are related to this notification. If the Correlation Event Report originates from a managed object instance and the Correlation Notification parameter is not present, the source object instance shall be present. The algorithm to perform correlation is outside the scope of this standard. 8.1.2.10 State Change Definition
When this parameter is present, it is used to indicate the state transitions associated with the alarm as defined in ISO 17143.2. In this case, if the managed object class definition includes state change notifications, it shall also send a state change notification as defined in ISO 17143.2.
8.1.2.11 Monitoring Attributes
When the Monitoring Attributes parameter is present, it defines one or more attributes of the managed object and their corresponding values in the event of an alarm. The managed object definer may define a set of attributes if there is a set of attributes of interest. For example, to allow timely reporting of changing conditions in the event of an alarm. 8.1.2.12 Planned Repair Action
When this parameter is present, it is used if the cause is known and the system being managed can propose one or more solutions (such as switching to alternate equipment, retrying, changing media, etc.). This parameter is a set of possibilities defined by the object class definer. This parameter can be either a set of integers or a set of object identifiers. However, only object identifiers may be used in the context of system management as defined in ISO/IEC 17142. Such identifiers may be registered using the registration procedure defined in ISO/IEC 16262 for ASN.1 object identifier values. NOTE: In this standard, two values with the following semantics have been assigned to this parameter: No Repair Action Required: This value is used to indicate that no repair action is required to be initiated by the administrator, as it is not the administrator's responsibility; and - Repair Action Required: This value is used to indicate that repair action is required to be initiated by the administrator to correct the problem reported in the alarm report. This value also indicates that no specific repair action has been scheduled by the agent's system. These values may be used if the cause is known and the system being managed can propose one or more planned actions for the alarm report recipient to take. 8.1.2.13 Supplementary Text
When this parameter is present, a free-form textual narrative is allowed to be reported. Interpretation Notification does not require understanding of the semantics of this field. This standard does not specify the format or meaning of the data contained in the Supplementary Text parameter. These contents are not subject to any OSI management conformance testing.
8.1.2.14 Supplementary Information
When this parameter is present, a set of supplementary information is allowed to be included in the event report. It is a series of data structures, each of which contains three items of information: an identifier, a valid position indicator, and a problem message. The identifier subparameter carries a registered object identifier, which defines the data type of the information subparameter. The management system must understand this data type in order to perform syntax analysis on the contents of the information subparameter. Supplementary identifiers can be registered using the procedures defined in GB/T 16262 for ASN.1 object identifier values. The valid position subparameter is a Boolean value. This Boolean value is set to true if the receiving system must be able to parse the contents of the information subparameter in order to fully understand the event report. Even if the supplementary information parameter is not fully understood, an event report indication should be given to the user. The indication that the supplementary information parameter is not fully understood is a local matter. The information subparameter should carry information about the event. If the identifier is known, the information can be parsed. 8.1.3 Event Response
This standard does not specify the management information used in the event response parameters. 8.2 Managed Objects
The alarm record is a managed object class that is derived from the event log record object class defined in GB/T 17175.2. The alarm record object class represents the information stored in the log as a result of receiving an event report, where the event type is one of the alarm types defined in this standard. 8.3 Conformance
The managed object class definition supports the functions defined in this standard by referencing the notification samples defined in GB/T 17175.2, in conjunction with the appropriate notification specifications. The reference mechanism is defined by GB/T 17175.4. For each use of an alarm, it is required to import one or more managed object class definitions for the alarms defined in this standard so that the alarm type and possible cause can be selected to be closest to the real event in the managed object. If a managed object class specifies more than one event for a particular combination of alarm type and probable cause, the Specific Problem parameter may be used to uniquely identify the event. The Supplementary Text parameter may be used to identify and transmit supplementary or more specific alarm information. However, a better approach is to register and use supplementary values for parameters such as "Probable Cause", "Specific Problem", and "Supplementary Information". The Supplementary Information parameter may include diagnostic information and other information about the alarm. However, information that can be mapped to other parameters provided by this standard (except supplementary text) should not be reported using the Supplementary Information parameter. 9 Service Definition
9.1 Introduction
This standard defines a service, which is identified as follows, along with appropriate parameters. The Alarm Report service allows one user to notify another user of an alarm detected in a managed object. The original user must specify whether a response is required. Further parameters convey the identification of the managed object, the type and time of the alarm, and other relevant management information. 9.2 Alarm Report Service
The alarm report service uses the parameters defined in Chapter 8 of this standard, as well as the general M-EVENT-REPORT service parameters defined in GB/T 16644.
Table 1 lists the parameters of the alarm report service.
Table 1 Alarm Report Parameters
Number Name
Call Identifier
Managed Object Class
Managed Object Example
Event Type
Event Time
Event Information
Possible Causes
Explicit Problem
Perceived Severity
Backup Status
Backup Object
Req/Ind
Rsp/Conf
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.