Network Working Group S. Chisholm
Request for Comments: 3877 Nortel Networks
Category: Standards Track D. Romascanu
Avaya
September 2004
Network Working Group S. Chisholm
Request for Comments: 3877 Nortel Networks
Category: Standards Track D. Romascanu
Avaya
September 2004
Alarm Management Information Base (MIB)
报警管理信息库（MIB）
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes management objects used for modelling and storing alarms.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于建模和存储报警的管理对象。
Table of Contents
目录
1. The Internet-Standard Management Framework . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Alarm Management Framework . . . . . . . . . . . . . . . . . . 4
3.1. Terminology. . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Alarm Management Architecture. . . . . . . . . . . . . . 5
3.3. Features of this Architecture. . . . . . . . . . . . . . 5
3.4. Security . . . . . . . . . . . . . . . . . . . . . . . . 8
3.5. Relationship between Alarm and Notifications . . . . . . 9
3.6. Notification Varbind Storage and Reference . . . . . . . 9
3.7. Relation to Notification Log MIB . . . . . . . . . . . . 10
3.8. Relation to Event MIB. . . . . . . . . . . . . . . . . . 10
4. Generic Alarm MIB. . . . . . . . . . . . . . . . . . . . . . . 10
4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2. Definitions. . . . . . . . . . . . . . . . . . . . . . . 15
5. ITU Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 38
5.2. IANA Considerations. . . . . . . . . . . . . . . . . . . 39
5.3. Textual Conventions. . . . . . . . . . . . . . . . . . . 47
5.4. Definitions. . . . . . . . . . . . . . . . . . . . . . . 49
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.1. Alarms Based on linkUp/linkDown Notifications. . . . . . 59
6.2. Temperature Alarm using generic Notifications. . . . . . 62
6.3. Temperature Alarm without Notifications. . . . . . . . . 63
6.4. Printer MIB Alarm Example. . . . . . . . . . . . . . . . 65
6.5. Rmon Alarm Example . . . . . . . . . . . . . . . . . . . 66
6.6. The Lifetime of an Alarm . . . . . . . . . . . . . . . . 67
7. Security Considerations. . . . . . . . . . . . . . . . . . . . 70
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 72
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
9.1. Normative References . . . . . . . . . . . . . . . . . . 72
9.2. Informative References . . . . . . . . . . . . . . . . . 73
10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 74
11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 75
1. The Internet-Standard Management Framework . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Alarm Management Framework . . . . . . . . . . . . . . . . . . 4
3.1. Terminology. . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Alarm Management Architecture. . . . . . . . . . . . . . 5
3.3. Features of this Architecture. . . . . . . . . . . . . . 5
3.4. Security . . . . . . . . . . . . . . . . . . . . . . . . 8
3.5. Relationship between Alarm and Notifications . . . . . . 9
3.6. Notification Varbind Storage and Reference . . . . . . . 9
3.7. Relation to Notification Log MIB . . . . . . . . . . . . 10
3.8. Relation to Event MIB. . . . . . . . . . . . . . . . . . 10
4. Generic Alarm MIB. . . . . . . . . . . . . . . . . . . . . . . 10
4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2. Definitions. . . . . . . . . . . . . . . . . . . . . . . 15
5. ITU Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 38
5.2. IANA Considerations. . . . . . . . . . . . . . . . . . . 39
5.3. Textual Conventions. . . . . . . . . . . . . . . . . . . 47
5.4. Definitions. . . . . . . . . . . . . . . . . . . . . . . 49
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.1. Alarms Based on linkUp/linkDown Notifications. . . . . . 59
6.2. Temperature Alarm using generic Notifications. . . . . . 62
6.3. Temperature Alarm without Notifications. . . . . . . . . 63
6.4. Printer MIB Alarm Example. . . . . . . . . . . . . . . . 65
6.5. Rmon Alarm Example . . . . . . . . . . . . . . . . . . . 66
6.6. The Lifetime of an Alarm . . . . . . . . . . . . . . . . 67
7. Security Considerations. . . . . . . . . . . . . . . . . . . . 70
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 72
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
9.1. Normative References . . . . . . . . . . . . . . . . . . 72
9.2. Informative References . . . . . . . . . . . . . . . . . 73
10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 74
11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 75
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
In traditional SNMP management, problems are detected on an entity either through polling interesting MIB variables, waiting for the entity to send a Notification for a problem, or some combination of the two. This method is somewhat successful, but experience has shown some problems with this approach. Managers monitoring large numbers of entities cannot afford to be polling large numbers of objects on each device. Managers trying to ensure high reliability are unable to accurately determine whether any problems had occurred when they were not monitoring an entity. Finally, it can be time consuming for managers to try to understand the relationships between the various objects they poll, the Notifications they receive and the problems occurring on the entity. Even after detailed analysis they may still be left with an incomplete picture of what problems are occurring. But, it is important for an operator to be able to determine current problems on a system, so they can be fixed.
在传统的SNMP管理中，通过轮询感兴趣的MIB变量、等待实体发送问题通知，或通过两者的某种组合，在实体上检测问题。这种方法有些成功，但经验表明这种方法存在一些问题。监控大量实体的管理者无法在每个设备上轮询大量对象。试图确保高可靠性的管理者无法准确确定在他们不监控实体时是否发生了任何问题。最后，管理者试图了解他们轮询的各种对象、他们收到的通知以及实体上发生的问题之间的关系可能会非常耗时。即使经过详细的分析，他们仍然可能对正在发生的问题有一个不完整的了解。但是，对于操作员来说，能够确定系统上当前的问题是很重要的，这样它们就可以被修复。
This memo describes a method of using alarm management in SNMP to address these problems. It also provides the necessary MIB objects to support this method.
本备忘录描述了在SNMP中使用报警管理解决这些问题的方法。它还提供了必要的MIB对象来支持此方法。
Alarms and other terms related to alarm management are defined in the following sections.
报警和其他与报警管理相关的术语在以下章节中定义。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[RFC2119]中的说明进行解释。
Error A deviation of a system from normal operation.
系统偏离正常运行的偏差。
Fault Lasting error or warning condition.
持续错误或警告状态的故障。
Event Something that happens which may be of interest. A fault, a change in status, crossing a threshold, or an external input to the system, for example.
事件发生的可能引起兴趣的事情。例如，故障、状态变化、超过阈值或系统的外部输入。
Notification Unsolicited transmission of management information.
通知管理信息的非请求传输。
Alarm Persistent indication of a fault.
报警持续指示故障。
Alarm State A condition or stage in the existence of an alarm. As a minimum, alarms states are raise and clear. They could also include severity information such as defined by perceived severity in the International Telecommunications Union (ITU) model [M.3100] - cleared, indeterminate, critical, major, minor and warning.
报警状态存在报警的条件或阶段。作为最低要求，警报状态为raise（升起）和clear（清除）。它们还可以包括严重性信息，如国际电信联盟（ITU）模型[M.3100]中的感知严重性定义——清除、不确定、严重、严重、轻微和警告。
Alarm Raise The initial detection of the fault indicated by an alarm or any number of alarm states later entered, except clear.
Alarm Rise（警报提升）通过警报或随后输入的任何数量的警报状态（清除除外）指示的故障的初始检测。
Alarm Clear The detection that the fault indicated by an alarm no longer exists.
报警清除检测到报警指示的故障不再存在。
Active Alarm An alarm which has an alarm state that has been raised, but not cleared.
激活报警具有已发出但未清除的报警状态的报警。
Alarm Detection Point The entity that detected the alarm.
报警检测点检测报警的实体。
Perceived Severity The severity of the alarm as determined by the alarm detection point using the information it has available.
感知严重性——由报警检测点使用其可用信息确定的报警严重性。
+------------------------------------------------+
| |
| +------------------------------------+ |
| | Notification Management | |
| +------------------------------------+ |
| | |
+------------------------------------------------+
|
|
|
|<----------------------------------------------+
| |
+------------------V-------------+ |
| +---------------V-----------+ | |
| | RFC 3413 | | |
| | SNMP-NOTIFICATION-MIB | | |
| +--------+--------------+-+-+ | |
| | | | | |
| | | +------------------+ |
| | | | | |
| | | | +----------V--------------+ |
| | | | | +--------V---------+ | |
| +---------V------------+ | | | | Alarm Modelling | | |
| | RFC 3014 | | | | | (descriptions) | | |
| | NOTIFICATION-LOG-MIB | | | | +--------+---------+ | |
| +----------------------+ | | | | | |
| | | | +--------V------------+ | |
| +------------------------V-+ | | | Generic: Model- | | |
| | RFC 3413 | | | | Active : Specific | | |
| | SNMP-TARGET-MIB | | | | Alarms : Extensions | | |
| +----------+---------------+ | | +--------+------------+ | |
| | | | | | |
+------------|-------------------+ +----------|--------------+ |
| | |
| +------------------+
V
Informs & Traps
+------------------------------------------------+
| |
| +------------------------------------+ |
| | Notification Management | |
| +------------------------------------+ |
| | |
+------------------------------------------------+
|
|
|
|<----------------------------------------------+
| |
+------------------V-------------+ |
| +---------------V-----------+ | |
| | RFC 3413 | | |
| | SNMP-NOTIFICATION-MIB | | |
| +--------+--------------+-+-+ | |
| | | | | |
| | | +------------------+ |
| | | | | |
| | | | +----------V--------------+ |
| | | | | +--------V---------+ | |
| +---------V------------+ | | | | Alarm Modelling | | |
| | RFC 3014 | | | | | (descriptions) | | |
| | NOTIFICATION-LOG-MIB | | | | +--------+---------+ | |
| +----------------------+ | | | | | |
| | | | +--------V------------+ | |
| +------------------------V-+ | | | Generic: Model- | | |
| | RFC 3413 | | | | Active : Specific | | |
| | SNMP-TARGET-MIB | | | | Alarms : Extensions | | |
| +----------+---------------+ | | +--------+------------+ | |
| | | | | | |
+------------|-------------------+ +----------|--------------+ |
| | |
| +------------------+
V
Informs & Traps
The subject of alarm management can potentially cover a large number of topics including real-time alarms, historical alarms, alarm correlation, and alarm suppression, to name a few. Within each of these topics, there are a number of established models that could be
报警管理主题可能涵盖大量主题，包括实时报警、历史报警、报警相关性和报警抑制等。在这些主题中，有许多已建立的模型可以
supported. This memo focuses on a subset of this problem space, but describes a modular SNMP alarm management framework. Alarms SHOULD be modelled so Notifications are sent on alarm Clear.
支持。本备忘录侧重于此问题空间的一个子集，但描述了模块化SNMP报警管理框架。警报应建模，以便在警报清除时发送通知。
The framework defines a generic Alarm MIB that can be supported on its own, or with additional alarm modelling information such as the provided ITU Alarm MIB. In addition, the active alarm tables could also be extended to support additional information about active alarm instances. This framework can also be expanded in the future to support such features as alarm correlation and alarm suppression. This modular architecture means that the cost of supporting alarm management features is proportional to the number of features an implementation supports.
该框架定义了一个通用报警MIB，该MIB可以单独支持，也可以使用其他报警建模信息，如提供的ITU报警MIB。此外，还可以扩展活动报警表，以支持有关活动报警实例的其他信息。该框架还可以在将来扩展，以支持报警关联和报警抑制等功能。这种模块化架构意味着支持报警管理功能的成本与实现支持的功能数量成正比。
Alarm models document an understanding between a manager and an agent as to what problems will be reported on a system, how these problems will be reported, and what might possibly happen over the lifetime of this problem.
报警模型记录了管理者和代理之间关于系统上报告哪些问题、如何报告这些问题以及在该问题的生命周期内可能发生的情况的理解。
The alarm modelling method provided in this memo provides flexibility to support implementations with different modelling requirements. All alarms are modelled as a series of states that are related together using an alarm ID. Alarm states can be modelled using traditional Notifications, generic alarm Notifications, or without the use of Notifications.
本备忘录中提供的报警建模方法提供了灵活性，以支持具有不同建模要求的实施。所有报警都建模为一系列状态，这些状态使用报警ID关联在一起。可以使用传统通知、通用报警通知或不使用通知来建模报警状态。
Alarm states modelled using traditional Notifications would specify a Notification Object Identifier, and optionally an (offset, value) pair of one of the Notification varbinds to identify the state. This alarm state would be entered when the entity generated a Notification that matched this information and the alarm would be added to the active alarm table. This Notification would also get sent on the wire to any destinations, as indicated in the SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB [RFC3413].
使用传统通知建模的报警状态将指定一个通知对象标识符，并可选地指定一个通知变量绑定的（偏移量、值）对来标识状态。当实体生成与此信息匹配的通知时，将进入此报警状态，并且报警将添加到活动报警表中。如SNMP-TARGET-MIB和SNMP-Notification-MIB[RFC3413]中所示，此通知还将通过线路发送到任何目的地。
Alarm states modelled using generic Notifications use the alarmActiveState or alarmClearState Notifications defined in this memo. These alarm states would be entered after being triggered by a stimulus outside the scope of this memo, the alarm would be added to the active alarm table and these generic Notifications would then be sent on the wire to any destinations, as indicated in the SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB [RFC3413].
使用通用通知建模的报警状态使用此备忘录中定义的alarmActiveState或alarmClearState通知。这些报警状态将在被本备忘录范围外的刺激触发后输入，报警将被添加到活动报警表中，然后这些通用通知将通过线路发送到任何目的地，如SNMP-TARGET-MIB和SNMP-NOTIFICATION-MIB[RFC3413]所示。
Alarm states modelled without any Notifications would be triggered by some stimulus outside the scope of this memo, the alarm would be added to the active alarm table, but no Notifications would be sent to interested managers.
在没有任何通知的情况下建模的报警状态将由本备忘录范围之外的刺激触发，报警将添加到活动报警表中，但不会向感兴趣的经理发送通知。
The Alarm MIB provides a means to determine whether a given notification is of interest to managers for purposes of alarm management by permitting inspection of the alarm models. If no entries in the alarmModelTable could match a particular notification, then that notification is not relevant to the alarm models defined. In addition, information in the alarm model, such as the Notification ID and the description tell exactly what error or warning condition this alarm is indicating. If the ITU-ALARM-MIB is also supported, additional information is provided via the probable cause.
报警MIB提供了一种方法，通过允许检查报警模型，确定管理人员是否对给定通知感兴趣，以便进行报警管理。如果alarmModelTable中没有条目可以匹配特定通知，则该通知与定义的报警模型无关。此外，报警模型中的信息（如通知ID和描述）准确地说明了此报警指示的错误或警告条件。如果还支持ITU-ALARM-MIB，则通过可能原因提供附加信息。
An important goal of alarm management is to ensure that any detected problems get fixed, so it is necessary to know exactly where this problem is occurring. In addition, it is necessary to be able to tell when alarm instances are raised against the same component, as well as to be able to tell what instance of an alarm is cleared by an instance of an alarm clear.
报警管理的一个重要目标是确保任何检测到的问题都得到修复，因此有必要确切地知道该问题发生的位置。此外，还必须能够告知何时针对同一组件引发报警实例，以及能够告知哪个报警实例被报警清除实例清除。
The Alarm MIB provides a generic method for identifying the resource by extracting and building a resource ID from the Notification varbinds. It records the relevant information needed to locate the source of the alarm.
Alarm MIB提供了一种通用方法，通过从通知变量绑定中提取并构建资源ID来识别资源。它记录了定位报警源所需的相关信息。
Alarm Information, as defined in ITU alarm models [M.3100], is optionally available to implementations through the optional support of the ITU-ALARM-MIB.
如ITU警报模型[M.3100]中所定义的警报信息，可通过ITU-Alarm-MIB的可选支持选择性地用于实施。
An alarm model can be added and removed during runtime. It can be modified assuming it is not being referenced by any active alarm instance.
可以在运行时添加和删除报警模型。可以对其进行修改，前提是它未被任何活动报警实例引用。
A list of currently active alarms and supporting statistics on the SNMP entity can be obtained.
可以获得SNMP实体上当前活动警报和支持统计信息的列表。
This allows the network management station to find out about any problems that may have occurred before it started managing a particular network element, or while it was out of contact with it.
这使网络管理站能够了解在开始管理特定网元之前或与之失去联系时可能发生的任何问题。
All aspects of the Alarm MIB can be supported both on the device experiencing the alarms and on any mid-level managers that might be monitoring such devices.
警报MIB的所有方面都可以在经历警报的设备上以及任何可能监视此类设备的中级管理器上得到支持。
Some systems may have a requirement that information on alarms that are no longer active is available. This memo provides a clear table to support this requirement.
某些系统可能要求不再激活的报警信息可用。本备忘录提供了一个明确的表格来支持这一要求。
This can also be achieved through the support of the Notification Log MIB [RFC3014] to store alarm state transitions.
这也可以通过支持通知日志MIB[RFC3014]来实现，以存储报警状态转换。
Given the nature of VACM, security for alarms is awkward since access control for the objects in the underlying Notifications can be checked only where the Notification is created. Thus such checking is possible only for locally generated Notifications, and even then only when security credentials are available.
鉴于VACM的性质，警报的安全性很难保证，因为只有在创建通知的地方才能检查底层通知中对象的访问控制。因此，这种检查只能用于本地生成的通知，甚至只有在安全凭据可用时才可能进行。
For the purpose of this discussion, "security credentials" means the input values for the abstract service interface function isAccessAllowed [RFC3411] and using those credentials means conceptually using that function to see that those credentials allow access to the MIB objects in question, operating as for a Notification Originator in [RFC3413].
在本讨论中，“安全凭据”是指允许访问抽象服务接口函数的输入值[RFC3411]，使用这些凭据意味着从概念上使用该函数以查看这些凭据允许访问有问题的MIB对象，操作方式与[RFC3413]中的通知发起人相同.
The Alarm MIB has the notion of a named alarm list. By using alarm list names and view-based access control [RFC3415] a network administrator can provide different access for different users. When an application creates an alarm model (indexed in part by the alarm list name) the security credentials of the creator remain associated with that alarm model and constrain what information is allowed to be placed in the active alarm table, the active alarm variable table, the cleared alarm table, and the ITU alarm table.
报警MIB具有命名报警列表的概念。通过使用报警列表名称和基于视图的访问控制[RFC3415]，网络管理员可以为不同的用户提供不同的访问。当应用程序创建报警模型（部分由报警列表名称索引）时，创建者的安全凭据仍与该报警模型关联，并限制允许在活动报警表、活动报警变量表、清除的报警表和ITU报警表中放置的信息。
When processing locally-generated Notifications, the managed system MUST use the security credentials associated with each alarm model respectively, and MUST apply the same access control rules as described for a Notification Originator in [RFC3413].
在处理本地生成的通知时，受管系统必须分别使用与每个报警模型关联的安全凭据，并且必须应用与[RFC3413]中针对通知发起人所述相同的访问控制规则。
The managed system SHOULD NOT apply access control when processing remotely-generated Notifications using the alarm models. In those cases the security of the information in the alarm tables SHOULD be left to the normal, overall access control for those tables.
当使用报警模型处理远程生成的通知时，受管系统不应应用访问控制。在这些情况下，应将报警表中信息的安全性留给这些表的正常总体访问控制。
It is important to understand the relationship between alarms and Notifications, as both are traditional fault management methods. This relationship is modelled using the alarmModelTable to define the alarmModelNotificationId for each alarm state.
了解报警和通知之间的关系很重要，因为两者都是传统的故障管理方法。此关系使用alarmModelTable建模，以定义每个报警状态的alarmModelNotificationId。
Not all Notifications signal an alarm state transition. Some Notifications are simply informational in nature, such as those that indicate that a configuration operation has been performed on an entity. These sorts of Notifications would not be represented in the Alarm MIB.
并非所有通知都表示警报状态转换。有些通知本质上只是信息性的，例如那些指示已对实体执行了配置操作的通知。这些类型的通知不会在报警MIB中表示。
The Alarm MIB allows the use of the Notification space as defined in [RFC2578] in order to identify the Notifications that are related with the specific alarm state transitions. However there is no assumption that the respective Notifications must be sent for all or any of the alarm state transitions. It is also possible to model alarms using no Notifications at all. This architecture allows for both the efficient exploitation of the body of defined Notification and for the use of non-Notification based systems.
报警MIB允许使用[RFC2578]中定义的通知空间，以识别与特定报警状态转换相关的通知。但是，不存在必须为所有或任何报警状态转换发送相应通知的假设。也可以完全不使用通知来模拟报警。此体系结构既允许有效利用已定义通知的主体，也允许使用非基于通知的系统。
In SNMPv1 [RFC1157], the varbinds in the Trap-PDU sent over the wire map one to one into those varbinds listed in the SMI of the trap in the MIB in which it was defined [RFC1215]. In the case of linkDown trap, the first varbind can unambiguously be identified as ifIndex. With the introduction of the InformRequest-PDU and SNMPv2-Trap-PDU types, which send sysUptime and snmpTrapOID as the first two varbinds, while the SMI in the MIB where the Notification is defined only lists additional varbinds, the meaning of "first varbind" becomes less clear. In the case of the linkDown Notification, referring to the first varbind could potentially be interpreted as either the sysUptime or ifIndex.
在SNMPv1[RFC1157]中，陷阱PDU中通过线路发送的变量绑定一一映射到定义它的MIB中陷阱SMI中列出的变量绑定[RFC1215]。在linkDown陷阱的情况下，第一个变量绑定可以明确地标识为ifIndex。随着InformRequest PDU和SNMPv2 Trap PDU类型的引入，它们将sysUptime和snmpTrapOID作为前两个varbind发送，而定义通知的MIB中的SMI只列出了其他varbind，“first varbind”的含义变得不那么清楚。在linkDown通知的情况下，引用第一个varbind可能被解释为sysUptime或ifIndex。
The varbind storage approach taken in the Alarm MIB is that sysUptime and snmpTrapOID SHALL always be stored in the active alarm variable table as entry 1 and 2 respectively, regardless of whether the transport was the Trap-PDU, the InformRequest-PDU or the SNMPv2- Trap-PDU. If the incoming Notification is an SNMPv1 Trap-PDU then an appropriate value for sysUpTime.0 or snmpTrapOID.0 shall be determined by using the rules in section 3.1 of [RFC3584].
报警MIB中采用的varbind存储方法是，sysUptime和snmpTrapOID应始终分别作为条目1和条目2存储在活动报警变量表中，无论传输是陷阱PDU、InformRequest PDU还是SNMPv2-陷阱PDU。如果传入通知是SNMPv1陷阱PDU，则应使用[RFC3584]第3.1节中的规则确定sysUpTime.0或snmpTrapOID.0的适当值。
The varbind reference approach taken in the Alarm MIB is that, for variables such as the alarmModelVarbindIndex, the first two obligatory varbinds of the InformRequest-PDU and SNMPv2-Trap-PDU need to be considered so the index values of the Trap-PDU and the SMI need be adjusted by two. In the case of linkDown, the third varbind would always be ifIndex.
报警MIB中采用的varbind参考方法是，对于alarmModelVarbindIndex等变量，需要考虑InformRequest PDU和SNMPv2陷阱PDU的前两个强制varbind，因此陷阱PDU和SMI的索引值需要调整两个。在linkDown的情况下，第三个varbind始终是ifIndex。
The Alarm MIB is intended to complement the Notification Log MIB [RFC3014], but can be used independently. The alarmActiveTable is defined in manner similar to that of the nlmLogTable. This format allows for the storage of any Trap or Notification type that can be defined using the SMI, or can be carried by SNMP. Using the same format as the Notification Log MIB also simplifies operations for systems choosing to implement both MIBs.
报警MIB旨在补充通知日志MIB[RFC3014]，但可以单独使用。alarmActiveTable的定义方式与nlmLogTable类似。此格式允许存储任何陷阱或通知类型，这些陷阱或通知类型可以使用SMI定义，也可以由SNMP携带。使用与通知日志MIB相同的格式还可以简化选择实现这两个MIB的系统的操作。
The object alarmActiveLogPointer points, for each entry in the alarmActiveLogTable, to the log index in the Notification Log MIB, if used.
对象alarmActiveLogPointer为alarmActiveLogTable中的每个条目指向通知日志MIB中的日志索引（如果使用）。
If the Notification Log MIB is supported, it can be monitored by a management system as a hedge against lost alarms. The Notification Log can also be used to support historical alarm management.
如果支持通知日志MIB，则管理系统可以对其进行监控，以防止报警丢失。通知日志还可用于支持历史报警管理。
During the work and discussions in the Working Group, the issue of the relationship between the MIB modules and the Event MIB [RFC2981] was raised. There is no direct relation or dependency between the Alarm MIB and the Event MIB. Some common terms (like 'event') are being used in both MIB modules, and the user is directed to the sections that define terminology in the two documents for clarification.
在工作组的工作和讨论期间，提出了MIB模块与事件MIB[RFC2981]之间的关系问题。报警MIB和事件MIB之间没有直接关系或依赖关系。两个MIB模块中都使用了一些常用术语（如“事件”），用户将被引导到两个文档中定义术语的部分进行澄清。
The ALARM-MIB consists of alarm models and lists of active and cleared alarms.
ALARM-MIB由报警模型以及激活和清除的报警列表组成。
The alarmModelTable contains information that is applicable to all instances of an alarm. It can be populated at start-up with all alarms that could happen on a system or later configured by a management application. It contains all the alarms for a given system. If a Notification is not represented in the alarmModelTable, it is not an alarm state transition. The alarmModelTable provides a
alarmModelTable包含适用于所有报警实例的信息。它可以在启动时填充可能发生在系统上的所有报警，或稍后由管理应用程序配置的所有报警。它包含给定系统的所有警报。如果alarmModelTable中未表示通知，则它不是报警状态转换。alarmModelTable提供了一个
means of defining the raise/clear and other state transition relationships between alarm states. The alarmModelIndex acts as a unique identifier for an alarm. An alarm model consists of definitions of the possible states an alarm can assume as well as the Object Identifier (OID) of the Notification associated with this alarm state. The object alarmModelState defines the states of an alarm.
定义报警状态之间的提升/清除和其他状态转换关系的方法。alarmModelIndex充当报警的唯一标识符。报警模型包括报警可能呈现的状态的定义以及与此报警状态关联的通知的对象标识符（OID）。对象alarmModelState定义报警的状态。
The alarmActiveTable contains a list of alarms that are currently occurring on a system. It is intended that this table be queried upon device discovery and rediscovery to determine which alarms are currently active on the device.
alarmActiveTable包含系统上当前发生的报警列表。在设备发现和重新发现时查询此表，以确定设备上当前激活的报警。
The alarmActiveVariableTable contains the Notification variable bindings associated with the alarms in the alarmActiveTable.
alarmActiveVariableTable包含与alarmActiveTable中的报警关联的通知变量绑定。
The alarmActiveStatsTable contains current and total raised alarm counts as well as the time of the last alarm raise and alarm clears per named alarm list.
alarmActiveStatsTable包含当前和总发出的报警计数，以及根据命名报警列表上次发出报警和清除报警的时间。
The alarmClearTable contains recently cleared alarms. It contains up to alarmClearMaximum cleared alarms.
alarmClearTable包含最近清除的报警。它最多包含alarmClearMaximum cleared报警。
The MIB also defines generic alarm Notifications that can be used when there is not an existing applicable Notification to signal the alarm state transition - alarmActiveState and alarmClearState.
MIB还定义了通用报警通知，当没有可用的通知向报警状态转换（alarmActiveState和alarmClearState）发出信号时，可以使用这些通知。
The relationship between the Alarm MIB and the other alarm model MIB modules is expressed by the following: The alarmModelTable has a corresponding table in the specific MIB. For each row in the specific MIB alarm model table there is one row in the alarmModelTable. The alarmActiveTable has a corresponding table in the specific MIBs. For each row in the specific MIB active alarm table, there is one row in the alarmActiveTable. The alarmModelSpecificPointer object in the alarmModelTable points to the specific model entry in an extended alarm model table corresponding to this particular alarm. The alarmActiveSpecificPointer object in the alarmActiveTable points to the specific active alarm entry in an extended active alarm table corresponding to this particular alarm instance.
Alarm MIB与其他报警模型MIB模块之间的关系表示为：alarmModelTable在特定MIB中具有相应的表。对于特定MIB报警模型表中的每一行，alarmModelTable中有一行。alarmActiveTable在特定MIB中具有相应的表。对于特定MIB活动报警表中的每一行，alarmActiveTable中有一行。alarmModelTable中的alarmModelSpecificPointer对象指向与此特定报警对应的扩展报警模型表中的特定模型条目。alarmActiveTable中的alarmActiveSpecificPointer对象指向与此特定报警实例对应的扩展活动报警表中的特定活动报警条目。
Additional extensions can be defined by defining an AUGMENTATION of either the Alarm or ITU Alarm tables. As the alarm model table only provides a mechanism to point at one specific alarm model, additional specific models SHOULD define another mechanism to map from the generic alarm model to the additional model.
可以通过定义报警表或ITU报警表的扩充来定义其他扩展。由于报警模型表仅提供指向一个特定报警模型的机制，其他特定模型应定义另一种机制，以从通用报警模型映射到其他模型。
The problem that each alarm indicates is identified through the Object Identifier of the NotificationId of the state transition, and, optionally, the ITU parameters. alarmModelDescription provides a description of the alarm state suitable for displaying to an operator.
每个报警指示的问题通过状态转换NotificationId的对象标识符以及ITU参数（可选）进行识别。alarmModelDescription提供适合向操作员显示的报警状态说明。
The SNMP-TARGET-MIB [RFC3413] provides the ability to specify which managers, if any, receive Notifications of problems. Solutions can therefore use the features of this MIB to change the Notification behaviour of their implementations. Specifying target hosts in this MIB along with specifying notifications in the alarmModelNotificationId would allow Notifications to be logged and sent out to management stations in an architecture as described in section 3.2. Specifying no target hosts in this MIB along with specifying notifications in the alarmModelNotificationId would allow Notifications to be logged but not sent out to management stations in an architecture as described in section 3.2. Regardless of what is defined in the SNMP-TARGET-MIB, specifying { 0 0 } in the alarmModelNotificationId would result in no notifications being logged or sent to management stations as a consequence of this particular alarm state transition.
SNMP-TARGET-MIB[RFC3413]提供了指定哪些管理器（如果有）接收问题通知的功能。因此，解决方案可以使用此MIB的功能来更改其实现的通知行为。在此MIB中指定目标主机以及在alarmModelNotificationId中指定通知将允许记录通知并将其发送到第3.2节所述体系结构中的管理站。在此MIB中不指定目标主机，同时在alarmModelNotificationId中指定通知，将允许记录通知，但不会发送到第3.2节所述体系结构中的管理站。无论SNMP-TARGET-MIB中定义了什么，在alarmModelNotificationId中指定{0}都不会导致由于此特定报警状态转换而记录或发送到管理站的通知。
Alarms are modelled by defining all possible states in the alarmModelTable, as well as defining alarmModelNotificationId, alarmModelVarbindIndex, and alarmModelVarbindValue for each of the possible alarm states. Optionally, ituAlarmPerceivedSeverity models the states in terms of ITU perceived severity.
通过在alarmModelTable中定义所有可能的状态，以及为每个可能的报警状态定义alarmModelNotificationId、alarmModelVarbindIndex和alarmModelVarbindValue，可以对报警进行建模。或者，iTuarmPerceivedSeverity根据ITU感知的严重性对状态进行建模。
Resources under alarm can be identified using the alarmActiveResourceId. This OBJECT IDENTIFIER points to an appropriate object to identify the given resource, depending on the type of the resource.
可以使用alarmActiveResourceId识别报警下的资源。此对象标识符指向一个适当的对象来标识给定资源，具体取决于资源的类型。
The consumer of the alarmActiveResourceId does not necessarily need to know the type of the resource in the resource ID, but if they want to know this, examining the content of the resource ID can derive it - 1.3.6.1.2.1.2.2.1.1.something is an interface, for example. It is therefore good practice to use resource IDs that can be consistently used across technologies, such as ifIndex, entPhysicalIndex or sysApplRunIndex, to minimize the number of resource prefixes a manager interested in a resource type needs to learn.
alarmActiveResourceId的使用者不一定需要知道资源ID中的资源类型，但如果他们想知道这一点，检查资源ID的内容可以得到它-1.3.6.1.2.1.2.2.1.1。例如，某个东西就是一个接口。因此，最好使用可以跨技术（如ifIndex、entPhysicalIndex或sysApplRunIndex）一致使用的资源ID，以尽量减少对资源类型感兴趣的管理者需要学习的资源前缀数量。
Resource ID can be calculated using the alarmModelResourcePrefix, alarmModelVarbindSubtree and the Notification varbinds. This allows for both the managed element to be able to compute and populate the alarmActiveResourceId object and for the manager to be able to determine when two separate alarm instances are referring to the same resource.
可以使用alarmModelResourcePrefix、alarmModelVarbindSubtree和通知varbinds计算资源ID。这使得托管元素能够计算和填充alarmActiveResourceId对象，并且管理器能够确定两个单独的报警实例何时引用同一资源。
If alarmModelResourcePrefix has a value of 0.0, then alarmActiveResourceId is simply the variable identifier of the first Notification varbind that matches the prefix defined in alarmModelVarbindSubtree. Otherwise, alarmActiveResourceId is calculated by appending the instance information from the first Notification varbind that matches alarmModelVarbindSubtree to the prefix defined in alarmModelResourcePrefix. The instance information is the portion of the variable identifier following the part that matched alarmModelVarbindSubtree. If no match is found, then alarmActiveResourceId is simply the value of alarmModelResourcePrefix.
如果alarmModelResourcePrefix的值为0.0，则alarmActiveResourceId只是与alarmModelVarbindSubtree中定义的前缀匹配的第一个通知varbind的变量标识符。否则，通过将与alarmModelVarbindSubtree匹配的第一个通知varbind中的实例信息附加到alarmModelResourcePrefix中定义的前缀来计算alarmActiveResourceId。实例信息是与alarmModelVarbindSubtree匹配的部分后面的变量标识符部分。如果未找到匹配项，则alarmActiveResourceId只是alarmModelResourcePrefix的值。
In addition to this, the variable bindings from the Notifications that signal the alarm state transitions are stored in the active alarm variable table. This allows for implementations familiar with the particular Notifications to implement other forms of resource identification.
除此之外，通知报警状态转换的变量绑定存储在活动报警变量表中。这允许熟悉特定通知的实现实现其他形式的资源标识。
For Example:
例如：
A) Consider an alarm modelled using the authenticationFailure [RFC3418] Notification.
a）考虑使用认证失败[FRC318]通知建模的警报。
authenticationFailure NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An authenticationFailure trap signifies that the SNMPv2
entity, acting in an agent role, has received a protocol
message that is not properly authenticated. While all
implementations of the SNMPv2 must be capable of generating
this trap, the snmpEnableAuthenTraps object indicates
whether this trap will be generated."
::= { snmpTraps 5 }
authenticationFailure NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An authenticationFailure trap signifies that the SNMPv2
entity, acting in an agent role, has received a protocol
message that is not properly authenticated. While all
implementations of the SNMPv2 must be capable of generating
this trap, the snmpEnableAuthenTraps object indicates
whether this trap will be generated."
::= { snmpTraps 5 }
To set the resource ID to be usmStats, 1.3.6.1.6.3.15.1.1, configure as follows: alarmModelVarbindSubtree = 0.0 alarmModelResourcePrefix = usmStats (1.3.6.1.6.3.15.1.1)
要将资源ID设置为usmStats，请按如下方式配置：alarmModelVarbindSubtree=0.0 alarmModelResourcePrefix=usmStats（1.3.6.1.6.3.15.1.1）
B) Consider an alarm modelled using linkDown [RFC2863]
B）考虑使用Link向下建模的警报[RCFC663]
linkDown NOTIFICATION-TYPE
OBJECTS { ifIndex, ifAdminStatus, ifOperStatus }
STATUS current
DESCRIPTION
""
::= { snmpTraps 3 }
linkDown NOTIFICATION-TYPE
OBJECTS { ifIndex, ifAdminStatus, ifOperStatus }
STATUS current
DESCRIPTION
""
::= { snmpTraps 3 }
To set the resource Id to be the ifIndex, configure as follows: alarmModelVarbindSubtree = ifIndex (1.3.6.1.2.1.2.2.1.1) alarmModelResourcePrefix = 0.0
要将资源Id设置为ifIndex，请按如下方式配置：alarmModelVarbindSubtree=ifIndex（1.3.6.1.2.1.2.1.1）alarmModelResourcePrefix=0.0
Alternatively, since ifIndex is the first varbind, the following would also work, but might be less meaningful to a human reader of the MIB table: alarmModelVarbindSubtree = 0.0 alarmModelResourcePrefix = 0.0
或者，由于ifIndex是第一个varbind，以下命令也可以使用，但对MIB表的人工读取器来说可能意义不大：alarmModelVarbindSubtree=0.0 alarmModelResourcePrefix=0.0
C) Consider an alarm modelled using the bgpBackwardTransition [RFC1657] Notification.
c）考虑使用BGPBudWordDebug [RCF1657 ]通知建模的警报。
bgpBackwardTransition NOTIFICATION-TYPE
OBJECTS { bgpPeerLastError,
bgpPeerState }
STATUS current
DESCRIPTION
"The BGPBackwardTransition Event is generated
when the BGP FSM moves from a higher numbered
state to a lower numbered state."
::= { bgpTraps 2 }
bgpBackwardTransition NOTIFICATION-TYPE
OBJECTS { bgpPeerLastError,
bgpPeerState }
STATUS current
DESCRIPTION
"The BGPBackwardTransition Event is generated
when the BGP FSM moves from a higher numbered
state to a lower numbered state."
::= { bgpTraps 2 }
To set the resource Id to be the bgpPeerRemoteAddr, the index to the bgpTable, where bgpPeerState resides, configure as follows: alarmModelVarbindSubtree = bgpPeerState (1.3.6.1.2.1.15.3.1.2) alarmModelResourcePrefix = bgpPeerRemoteAddr (1.3.6.1.2.1.15.3.1.7)
要将资源Id设置为bgpeerremoteaddr，即bgpeerState所在的bgpTable的索引，请按如下方式配置：alarmModelVarbindSubtree=bgpeerState（1.3.6.1.2.1.15.3.1.2）alarmModelResourcePrefix=bgpeerremoteddr（1.3.6.1.2.1.15.3.1.7）
The alarm model table SHOULD be initially populated by the system. The objects in alarmModelTable and ituAlarmTable have a MAX-ACCESS of read-create, which allows managers to modify the alarm models to suit their requirements.
报警模型表最初应由系统填充。alarmModelTable和iTuarmTable中的对象具有读取-创建的最大访问权限，允许管理员修改报警模型以满足其要求。
Lists of alarms currently active on an SNMP entity are stored in the alarmActiveTable and, optionally, a model specific alarmTable, e.g., the ituAlarmActiveTable.
SNMP实体上当前处于活动状态的报警列表存储在alarmActiveTable中，还可以选择存储在特定于型号的alarmTable中，例如iTuarmActiveTable。
Distributed alarm management can be achieved by support of the Alarm MIB on both the alarm detection point and on the mid-level manager. This is facilitated by the ability to be able to store different named alarm lists. A mid-level manager could create an alarmListName for each of the devices it manages and therefore store separate lists for each device. In addition, the context and IP addresses of the alarm detection point are stored in the alarmActiveTable.
通过在报警检测点和中层管理器上支持报警MIB，可以实现分布式报警管理。能够存储不同的命名报警列表有助于实现这一点。中级管理器可以为其管理的每个设备创建alarmListName，从而为每个设备存储单独的列表。此外，报警检测点的上下文和IP地址存储在alarmActiveTable中。
ALARM-MIB DEFINITIONS ::= BEGIN
ALARM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Integer32, Unsigned32, Gauge32,
TimeTicks, Counter32, Counter64,
IpAddress, Opaque, mib-2,
zeroDotZero
FROM SNMPv2-SMI -- [RFC2578]
DateAndTime,
RowStatus, RowPointer,
TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579]
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB -- [RFC3291]
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ZeroBasedCounter32
FROM RMON2-MIB; -- [RFC2021]
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Integer32, Unsigned32, Gauge32,
TimeTicks, Counter32, Counter64,
IpAddress, Opaque, mib-2,
zeroDotZero
FROM SNMPv2-SMI -- [RFC2578]
DateAndTime,
RowStatus, RowPointer,
TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579]
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB -- [RFC3291]
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ZeroBasedCounter32
FROM RMON2-MIB; -- [RFC2021]
alarmMIB MODULE-IDENTITY
LAST-UPDATED "200409090000Z" -- September 09, 2004
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
"WG EMail: disman@ietf.org
Subscribe: disman-request@ietf.org
http://www.ietf.org/html.charters/disman-charter.html
alarmMIB MODULE-IDENTITY
LAST-UPDATED "200409090000Z" -- September 09, 2004
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
"WG EMail: disman@ietf.org
Subscribe: disman-request@ietf.org
http://www.ietf.org/html.charters/disman-charter.html
Chair: Randy Presuhn randy_presuhn@mindspring.com
主席：兰迪·普雷森·兰迪_presuhn@mindspring.com
Editors: Sharon Chisholm Nortel Networks PO Box 3511 Station C Ottawa, Ont. K1Y 4H7 Canada schishol@nortelnetworks.com
编者：安大略省渥太华市C站3511信箱，莎伦·奇肖姆北电网络公司。K1Y 4H7加拿大schishol@nortelnetworks.com
Dan Romascanu Avaya Atidim Technology Park, Bldg. #3 Tel Aviv, 61131 Israel Tel: +972-3-645-8414 Email: dromasca@avaya.com" DESCRIPTION "The MIB module describes a generic solution to model alarms and to store the current list of active alarms.
Dan Romascanu Avaya Atidim科技园，特拉维夫3号楼，61131以色列电话：+972-3-645-8414电子邮件：dromasca@avaya.com“说明”MIB模块描述了一种通用解决方案，用于模拟报警和存储当前活动报警列表。
Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3877. For full legal notices see the RFC
itself. Supplementary information may be available on:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "200409090000Z" -- September 09, 2004
DESCRIPTION
"Initial version, published as RFC 3877."
::= { mib-2 118 }
Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3877. For full legal notices see the RFC
itself. Supplementary information may be available on:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "200409090000Z" -- September 09, 2004
DESCRIPTION
"Initial version, published as RFC 3877."
::= { mib-2 118 }
alarmObjects OBJECT IDENTIFIER ::= { alarmMIB 1 }
alarmObjects OBJECT IDENTIFIER ::= { alarmMIB 1 }
alarmNotifications OBJECT IDENTIFIER ::= { alarmMIB 0 }
alarmNotifications OBJECT IDENTIFIER ::= { alarmMIB 0 }
alarmModel OBJECT IDENTIFIER ::= { alarmObjects 1 }
alarmModel OBJECT IDENTIFIER ::= { alarmObjects 1 }
alarmActive OBJECT IDENTIFIER ::= { alarmObjects 2 }
alarmActive OBJECT IDENTIFIER ::= { alarmObjects 2 }
alarmClear OBJECT IDENTIFIER ::= { alarmObjects 3 }
alarmClear OBJECT IDENTIFIER ::= { alarmObjects 3 }
-- Textual Conventions
--文本约定
-- ResourceId is intended to be a general textual convention
-- that can be used outside of the set of MIBs related to
-- Alarm Management.
-- ResourceId is intended to be a general textual convention
-- that can be used outside of the set of MIBs related to
-- Alarm Management.
ResourceId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier for this resource.
ResourceId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier for this resource.
The type of the resource can be determined by looking at the OID that describes the resource.
可以通过查看描述资源的OID来确定资源的类型。
Resources must be identified in a consistent manner. For example, if this resource is an interface, this object MUST point to an ifIndex and if this resource is a physical entity [RFC2737], then this MUST point to an entPhysicalDescr, given that entPhysicalIndex is not accessible. In general, the value is the name of the instance of the first accessible columnar object in the conceptual row of a table that is meaningful for this resource type, which SHOULD be defined in an IETF standard MIB." SYNTAX OBJECT IDENTIFIER
必须以一致的方式确定资源。例如，如果此资源是接口，则此对象必须指向ifIndex，如果此资源是物理实体[RFC2737]，则必须指向entPhysicalDescr，因为entPhysicalIndex不可访问。通常，该值是表概念行中第一个可访问列对象的实例的名称，该列对象对此资源类型有意义，应在IETF标准MIB中定义。“语法对象标识符”
-- LocalSnmpEngineOrZeroLenStr is intended to be a general
-- textual convention that can be used outside of the set of
-- MIBs related to Alarm Management.
-- LocalSnmpEngineOrZeroLenStr is intended to be a general
-- textual convention that can be used outside of the set of
-- MIBs related to Alarm Management.
LocalSnmpEngineOrZeroLenStr ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An SNMP Engine ID or a zero-length string. The
instantiation of this textual convention will provide
guidance on when this will be an SNMP Engine ID and
when it will be a zero lengths string"
SYNTAX OCTET STRING (SIZE(0 | 5..32))
LocalSnmpEngineOrZeroLenStr ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An SNMP Engine ID or a zero-length string. The
instantiation of this textual convention will provide
guidance on when this will be an SNMP Engine ID and
when it will be a zero lengths string"
SYNTAX OCTET STRING (SIZE(0 | 5..32))
-- Alarm Model
--报警模型
alarmModelLastChanged OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time of the last creation, deletion or modification of an entry in the alarmModelTable.
alarmModelLastChanged对象类型语法TimeTicks MAX-ACCESS只读状态current DESCRIPTION“上次创建、删除或修改alarmModelTable中的条目时sysUpTime的值。
If the number and content of entries has been unchanged since the last re-initialization of the local network management subsystem, then the value of this object MUST be zero."
如果自上次重新初始化本地网络管理子系统以来，条目的数量和内容保持不变，则此对象的值必须为零。”
::= { alarmModel 1 }
::= { alarmModel 1 }
alarmModelTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmModelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of information about possible alarms on the system,
and how they have been modelled."
::= { alarmModel 2 }
alarmModelTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmModelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of information about possible alarms on the system,
and how they have been modelled."
::= { alarmModel 2 }
alarmModelEntry OBJECT-TYPE
SYNTAX AlarmModelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entries appear in this table for each possible alarm state.
This table MUST be persistent across system reboots."
INDEX { alarmListName, alarmModelIndex, alarmModelState }
::= { alarmModelTable 1 }
alarmModelEntry OBJECT-TYPE
SYNTAX AlarmModelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entries appear in this table for each possible alarm state.
This table MUST be persistent across system reboots."
INDEX { alarmListName, alarmModelIndex, alarmModelState }
::= { alarmModelTable 1 }
AlarmModelEntry ::= SEQUENCE {
alarmModelIndex Unsigned32,
alarmModelState Unsigned32,
alarmModelNotificationId OBJECT IDENTIFIER,
alarmModelVarbindIndex Unsigned32,
alarmModelVarbindValue Integer32,
alarmModelDescription SnmpAdminString,
alarmModelSpecificPointer RowPointer,
alarmModelVarbindSubtree OBJECT IDENTIFIER,
alarmModelResourcePrefix OBJECT IDENTIFIER,
alarmModelRowStatus RowStatus
}
AlarmModelEntry ::= SEQUENCE {
alarmModelIndex Unsigned32,
alarmModelState Unsigned32,
alarmModelNotificationId OBJECT IDENTIFIER,
alarmModelVarbindIndex Unsigned32,
alarmModelVarbindValue Integer32,
alarmModelDescription SnmpAdminString,
alarmModelSpecificPointer RowPointer,
alarmModelVarbindSubtree OBJECT IDENTIFIER,
alarmModelResourcePrefix OBJECT IDENTIFIER,
alarmModelRowStatus RowStatus
}
alarmModelIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An integer that acts as an alarm Id
to uniquely identify each alarm
within the named alarm list. "
::= { alarmModelEntry 1 }
alarmModelIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An integer that acts as an alarm Id
to uniquely identify each alarm
within the named alarm list. "
::= { alarmModelEntry 1 }
alarmModelState OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS not-accessible STATUS current
alarmModelState对象类型语法Unsigned32（1..4294967295）MAX-ACCESS不可访问状态当前
DESCRIPTION
"A value of 1 MUST indicate a clear alarm state.
The value of this object MUST be less than the
alarmModelState of more severe alarm states for
this alarm. The value of this object MUST be more
than the alarmModelState of less severe alarm states
for this alarm."
::= { alarmModelEntry 2 }
DESCRIPTION
"A value of 1 MUST indicate a clear alarm state.
The value of this object MUST be less than the
alarmModelState of more severe alarm states for
this alarm. The value of this object MUST be more
than the alarmModelState of less severe alarm states
for this alarm."
::= { alarmModelEntry 2 }
alarmModelNotificationId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The NOTIFICATION-TYPE object identifier of this alarm
state transition. If there is no notification associated
with this alarm state, the value of this object MUST be
'0.0'"
DEFVAL { zeroDotZero }
::= { alarmModelEntry 3 }
alarmModelNotificationId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The NOTIFICATION-TYPE object identifier of this alarm
state transition. If there is no notification associated
with this alarm state, the value of this object MUST be
'0.0'"
DEFVAL { zeroDotZero }
::= { alarmModelEntry 3 }
alarmModelVarbindIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "The index into the varbind listing of the notification indicated by alarmModelNotificationId which helps signal that the given alarm has changed state. If there is no applicable varbind, the value of this object MUST be zero.
alarmModelVarbindIndex对象类型语法Unsigned32 MAX-ACCESS read create STATUS current DESCRIPTION“将索引放入alarmModelNotificationId指示的通知的varbind列表中，这有助于发出给定报警已更改状态的信号。如果没有适用的varbind，则此对象的值必须为零。
Note that the value of alarmModelVarbindIndex acknowledges the existence of the first two obligatory varbinds in the InformRequest-PDU and SNMPv2-Trap-PDU (sysUpTime.0 and snmpTrapOID.0). That is, a value of 2 refers to the snmpTrapOID.0.
请注意，alarmModelVarbindIndex的值确认InformRequest PDU和SNMPv2陷阱PDU（sysUpTime.0和snmpTrapOID.0）中存在前两个强制变量绑定。也就是说，值2表示snmpTrapOID.0。
If the incoming notification is instead an SNMPv1 Trap-PDU,
then an appropriate value for sysUpTime.0 or snmpTrapOID.0
shall be determined by using the rules in section 3.1 of
[RFC3584]"
DEFVAL { 0 }
::= { alarmModelEntry 4 }
If the incoming notification is instead an SNMPv1 Trap-PDU,
then an appropriate value for sysUpTime.0 or snmpTrapOID.0
shall be determined by using the rules in section 3.1 of
[RFC3584]"
DEFVAL { 0 }
::= { alarmModelEntry 4 }
alarmModelVarbindValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create
alarmModelVarbindValue对象类型语法整数32 MAX-ACCESS读取创建
STATUS current DESCRIPTION "The value that the varbind indicated by alarmModelVarbindIndex takes to indicate that the alarm has entered this state.
STATUS current DESCRIPTION“alarmModelVarbindIndex指示的varbind值，用于指示报警已进入此状态。
If alarmModelVarbindIndex has a value of 0, so
MUST alarmModelVarbindValue.
"
DEFVAL { 0 }
::= { alarmModelEntry 5 }
If alarmModelVarbindIndex has a value of 0, so
MUST alarmModelVarbindValue.
"
DEFVAL { 0 }
::= { alarmModelEntry 5 }
alarmModelDescription OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A brief description of this alarm and state suitable
to display to operators."
DEFVAL { "" }
::= { alarmModelEntry 6 }
alarmModelDescription OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A brief description of this alarm and state suitable
to display to operators."
DEFVAL { "" }
::= { alarmModelEntry 6 }
alarmModelSpecificPointer OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "If no additional, model-specific Alarm MIB is supported by the system the value of this object is `0.0'and attempts to set it to any other value MUST be rejected appropriately.
alarmModelSpecificPointer对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“如果系统不支持其他特定于模型的报警MIB，则此对象的值为“0.0”，并且必须适当拒绝将其设置为任何其他值的尝试。
When a model-specific Alarm MIB is supported, this object
MUST refer to the first accessible object in a corresponding
row of the model definition in one of these model-specific
MIB and attempts to set this object to { 0 0 } or any other
value MUST be rejected appropriately."
DEFVAL { zeroDotZero }
::= { alarmModelEntry 7 }
When a model-specific Alarm MIB is supported, this object
MUST refer to the first accessible object in a corresponding
row of the model definition in one of these model-specific
MIB and attempts to set this object to { 0 0 } or any other
value MUST be rejected appropriately."
DEFVAL { zeroDotZero }
::= { alarmModelEntry 7 }
alarmModelVarbindSubtree OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The name portion of each VarBind in the notification, in order, is compared to the value of this object. If the name is equal to or a subtree of the value of this object, for purposes of computing the value
alarmModelVarbindSubtree对象类型语法对象标识符MAX-ACCESS read create STATUS current DESCRIPTION“通知中每个VarBind的名称部分按顺序与此对象的值进行比较。如果名称等于或是此对象的值的子树，则用于计算值
of AlarmActiveResourceID the 'prefix' will be the
matching portion, and the 'indexes' will be any
remainder. The examination of varbinds ends with
the first match. If the value of this object is 0.0,
then the first varbind, or in the case of v2, the
first varbind after the timestamp and the trap
OID, will always be matched.
"
DEFVAL { zeroDotZero }
::= { alarmModelEntry 8 }
of AlarmActiveResourceID the 'prefix' will be the
matching portion, and the 'indexes' will be any
remainder. The examination of varbinds ends with
the first match. If the value of this object is 0.0,
then the first varbind, or in the case of v2, the
first varbind after the timestamp and the trap
OID, will always be matched.
"
DEFVAL { zeroDotZero }
::= { alarmModelEntry 8 }
alarmModelResourcePrefix OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of AlarmActiveResourceId is computed
by appending any indexes extracted in accordance
with the description of alarmModelVarbindSubtree
onto the value of this object. If this object's
value is 0.0, then the 'prefix' extracted is used
instead.
"
DEFVAL { zeroDotZero }
::= { alarmModelEntry 9 }
alarmModelResourcePrefix OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of AlarmActiveResourceId is computed
by appending any indexes extracted in accordance
with the description of alarmModelVarbindSubtree
onto the value of this object. If this object's
value is 0.0, then the 'prefix' extracted is used
instead.
"
DEFVAL { zeroDotZero }
::= { alarmModelEntry 9 }
alarmModelRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Control for creating and deleting entries. Entries may be modified while active. Alarms whose alarmModelRowStatus is not active will not appear in either the alarmActiveTable or the alarmClearTable. Setting this object to notInService cannot be used as an alarm suppression mechanism. Entries that are notInService will disappear as described in RFC2579.
alarmModelRowStatus对象类型语法RowStatus MAX-ACCESS读取创建状态当前描述“用于创建和删除条目的控件。在激活时可以修改条目。alarmModelRowStatus未激活的报警将不会出现在alarmActiveTable或alarmClearTable中。将此对象设置为notInService不能用作报警抑制机制。如RFC2579所述，不在服务中的条目将消失。
This row can not be modified while it is being referenced by a value of alarmActiveModelPointer. In these cases, an error of `inconsistentValue' will be returned to the manager.
当该行被alarmActiveModelPointer值引用时，无法修改该行。在这些情况下，将向经理返回一个“值不一致”的错误。
This entry may be deleted while it is being referenced by a value of alarmActiveModelPointer. This results in the deletion of this entry and entries in the active alarms referencing this entry via an alarmActiveModelPointer.
当alarmActiveModelPointer值引用此条目时，可能会将其删除。这将导致删除此条目以及通过alarmActiveModelPointer引用此条目的活动报警中的条目。
As all read-create objects in this table have a DEFVAL clause,
there is no requirement that any object be explicitly set
before this row can become active. Note that a row consisting
only of default values is not very meaningful."
::= { alarmModelEntry 10 }
As all read-create objects in this table have a DEFVAL clause,
there is no requirement that any object be explicitly set
before this row can become active. Note that a row consisting
only of default values is not very meaningful."
::= { alarmModelEntry 10 }
-- Active Alarm Table --
--主动报警表--
alarmActiveLastChanged OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the last
creation or deletion of an entry in the alarmActiveTable.
If the number of entries has been unchanged since the
last re-initialization of the local network management
subsystem, then this object contains a zero value."
::= { alarmActive 1 }
alarmActiveLastChanged OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the last
creation or deletion of an entry in the alarmActiveTable.
If the number of entries has been unchanged since the
last re-initialization of the local network management
subsystem, then this object contains a zero value."
::= { alarmActive 1 }
alarmActiveOverflow OBJECT-TYPE
SYNTAX Counter32
UNITS "active alarms"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of active alarms that have not been put into
the alarmActiveTable since system restart as a result
of extreme resource constraints."
::= { alarmActive 5 }
alarmActiveOverflow OBJECT-TYPE
SYNTAX Counter32
UNITS "active alarms"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of active alarms that have not been put into
the alarmActiveTable since system restart as a result
of extreme resource constraints."
::= { alarmActive 5 }
alarmActiveTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmActiveEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of Active Alarms entries."
::= { alarmActive 2 }
alarmActiveTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmActiveEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of Active Alarms entries."
::= { alarmActive 2 }
alarmActiveEntry OBJECT-TYPE SYNTAX AlarmActiveEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entries appear in this table when alarms are raised. They are removed when the alarm is cleared.
alarmActiveEntry对象类型语法alarmActiveEntry MAX-ACCESS不可访问状态当前描述”条目在引发报警时显示在此表中。清除报警时，这些条目将被删除。
If under extreme resource constraint the system is unable to
如果在极端资源限制下，系统无法
add any more entries into this table, then the
alarmActiveOverflow statistic will be increased by one."
INDEX { alarmListName, alarmActiveDateAndTime,
alarmActiveIndex }
::= { alarmActiveTable 1 }
add any more entries into this table, then the
alarmActiveOverflow statistic will be increased by one."
INDEX { alarmListName, alarmActiveDateAndTime,
alarmActiveIndex }
::= { alarmActiveTable 1 }
AlarmActiveEntry ::= SEQUENCE {
alarmListName SnmpAdminString,
alarmActiveDateAndTime DateAndTime,
alarmActiveIndex Unsigned32,
alarmActiveEngineID LocalSnmpEngineOrZeroLenStr,
alarmActiveEngineAddressType InetAddressType,
alarmActiveEngineAddress InetAddress,
alarmActiveContextName SnmpAdminString,
alarmActiveVariables Unsigned32,
alarmActiveNotificationID OBJECT IDENTIFIER,
alarmActiveResourceId ResourceId,
alarmActiveDescription SnmpAdminString,
alarmActiveLogPointer RowPointer,
alarmActiveModelPointer RowPointer,
alarmActiveSpecificPointer RowPointer }
AlarmActiveEntry ::= SEQUENCE {
alarmListName SnmpAdminString,
alarmActiveDateAndTime DateAndTime,
alarmActiveIndex Unsigned32,
alarmActiveEngineID LocalSnmpEngineOrZeroLenStr,
alarmActiveEngineAddressType InetAddressType,
alarmActiveEngineAddress InetAddress,
alarmActiveContextName SnmpAdminString,
alarmActiveVariables Unsigned32,
alarmActiveNotificationID OBJECT IDENTIFIER,
alarmActiveResourceId ResourceId,
alarmActiveDescription SnmpAdminString,
alarmActiveLogPointer RowPointer,
alarmActiveModelPointer RowPointer,
alarmActiveSpecificPointer RowPointer }
alarmListName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The name of the list of alarms. This SHOULD be the same as nlmLogName if the Notification Log MIB [RFC3014] is supported. This SHOULD be the same as, or contain as a prefix, the applicable snmpNotifyFilterProfileName if the SNMP-NOTIFICATION-MIB DEFINITIONS [RFC3413] is supported.
alarmListName对象类型语法SnmpAdminString（大小（0..32））MAX-ACCESS not accessible STATUS current DESCRIPTION“报警列表的名称。如果通知日志MIB[RFC3014]支持。如果支持SNMP-NOTIFICATION-MIB定义[RFC3413]，则该名称应与适用的snmpNotifyFilterProfileName相同，或作为前缀包含。
An implementation may allow multiple named alarm lists, up to
some implementation-specific limit (which may be none). A
zero-length list name is reserved for creation and deletion
by the managed system, and MUST be used as the default log
name by systems that do not support named alarm lists."
::= { alarmActiveEntry 1 }
An implementation may allow multiple named alarm lists, up to
some implementation-specific limit (which may be none). A
zero-length list name is reserved for creation and deletion
by the managed system, and MUST be used as the default log
name by systems that do not support named alarm lists."
::= { alarmActiveEntry 1 }
alarmActiveDateAndTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS not-accessible STATUS current DESCRIPTION "The local date and time when the error occurred.
alarmActiveDateAndTime对象类型语法DateAndTime MAX-ACCESS不可访问状态当前描述“发生错误的本地日期和时间。
This object facilitates retrieving all instances of
此对象有助于检索的所有实例
alarms that have been raised or have changed state since a given point in time.
自给定时间点以来已引发或已改变状态的报警。
Implementations MUST include the offset from UTC,
if available. Implementation in environments in which
the UTC offset is not available is NOT RECOMMENDED."
::= { alarmActiveEntry 2 }
Implementations MUST include the offset from UTC,
if available. Implementation in environments in which
the UTC offset is not available is NOT RECOMMENDED."
::= { alarmActiveEntry 2 }
alarmActiveIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A strictly monotonically increasing integer which
acts as the index of entries within the named alarm
list. It wraps back to 1 after it reaches its
maximum value."
::= { alarmActiveEntry 3 }
alarmActiveIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A strictly monotonically increasing integer which
acts as the index of entries within the named alarm
list. It wraps back to 1 after it reaches its
maximum value."
::= { alarmActiveEntry 3 }
alarmActiveEngineID OBJECT-TYPE
SYNTAX LocalSnmpEngineOrZeroLenStr
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identification of the SNMP engine at which the alarm
originated. If the alarm is from an SNMPv1 system this
object is a zero length string."
::= { alarmActiveEntry 4 }
alarmActiveEngineID OBJECT-TYPE
SYNTAX LocalSnmpEngineOrZeroLenStr
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identification of the SNMP engine at which the alarm
originated. If the alarm is from an SNMPv1 system this
object is a zero length string."
::= { alarmActiveEntry 4 }
alarmActiveEngineAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates what type of address is stored in
the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc."
::= { alarmActiveEntry 5 }
alarmActiveEngineAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates what type of address is stored in
the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc."
::= { alarmActiveEntry 5 }
alarmActiveEngineAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The address of the SNMP engine on which the alarm is occurring.
alarmActiveEngineAddress对象类型语法InetAddress MAX-ACCESS只读状态current DESCRIPTION“发生报警的SNMP引擎的地址。
This object MUST always be instantiated, even if the list can contain alarms from only one engine."
必须始终实例化此对象，即使列表只能包含来自一个引擎的报警。”
::= { alarmActiveEntry 6 }
::= { alarmActiveEntry 6 }
alarmActiveContextName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the SNMP MIB context from which the alarm came. For SNMPv1 alarms this is the community string from the Trap. Note that care MUST be taken when selecting community strings to ensure that these can be represented as a well-formed SnmpAdminString. Community or Context names that are not well-formed SnmpAdminStrings will be mapped to zero length strings.
alarmActiveContextName对象类型语法SnmpAdminString（大小（0..32））最大访问只读状态当前说明“报警来自的SNMP MIB上下文的名称。对于SNMPv1报警，这是陷阱中的社区字符串。请注意，在选择社区字符串时必须小心，以确保这些字符串可以表示为格式良好的snmpadmin字符串。格式不正确的snmpadmin字符串的社区或上下文名称将映射到零长度字符串。
If the alarm's source SNMP engine is known not to support
multiple contexts, this object is a zero length string."
::= { alarmActiveEntry 7 }
If the alarm's source SNMP engine is known not to support
multiple contexts, this object is a zero length string."
::= { alarmActiveEntry 7 }
alarmActiveVariables OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of variables in alarmActiveVariableTable for this
alarm."
::= { alarmActiveEntry 8 }
alarmActiveVariables OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of variables in alarmActiveVariableTable for this
alarm."
::= { alarmActiveEntry 8 }
alarmActiveNotificationID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NOTIFICATION-TYPE object identifier of the alarm
state transition that is occurring."
::= { alarmActiveEntry 9 }
alarmActiveNotificationID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NOTIFICATION-TYPE object identifier of the alarm
state transition that is occurring."
::= { alarmActiveEntry 9 }
alarmActiveResourceId OBJECT-TYPE SYNTAX ResourceId MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the resource under alarm.
alarmActiveResourceId对象类型语法ResourceId MAX-ACCESS只读状态当前描述“此对象标识报警下的资源。
If there is no corresponding resource, then
the value of this object MUST be 0.0."
::= { alarmActiveEntry 10 }
If there is no corresponding resource, then
the value of this object MUST be 0.0."
::= { alarmActiveEntry 10 }
alarmActiveDescription OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object provides a textual description of the
active alarm. This text is generated dynamically by the
notification generator to provide useful information
to the human operator. This information SHOULD
provide information allowing the operator to locate
the resource for which this alarm is being generated.
This information is not intended for consumption by
automated tools."
::= { alarmActiveEntry 11 }
alarmActiveDescription OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object provides a textual description of the
active alarm. This text is generated dynamically by the
notification generator to provide useful information
to the human operator. This information SHOULD
provide information allowing the operator to locate
the resource for which this alarm is being generated.
This information is not intended for consumption by
automated tools."
::= { alarmActiveEntry 11 }
alarmActiveLogPointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A pointer to the corresponding row in a
notification logging MIB where the state change
notification for this active alarm is logged.
If no log entry applies to this active alarm,
then this object MUST have the value of 0.0"
::= { alarmActiveEntry 12 }
alarmActiveLogPointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A pointer to the corresponding row in a
notification logging MIB where the state change
notification for this active alarm is logged.
If no log entry applies to this active alarm,
then this object MUST have the value of 0.0"
::= { alarmActiveEntry 12 }
alarmActiveModelPointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A pointer to the corresponding row in the
alarmModelTable for this active alarm. This
points not only to the alarm model being
instantiated, but also to the specific alarm
state that is active."
::= { alarmActiveEntry 13 }
alarmActiveModelPointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A pointer to the corresponding row in the
alarmModelTable for this active alarm. This
points not only to the alarm model being
instantiated, but also to the specific alarm
state that is active."
::= { alarmActiveEntry 13 }
alarmActiveSpecificPointer OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "If no additional, model-specific, Alarm MIB is supported by the system this object is `0.0'. When a model-specific Alarm MIB is supported, this object is the instance pointer to the specific model-specific active alarm list."
alarmActiveSpecificPointer对象类型语法RowPointer MAX-ACCESS只读状态当前描述“如果系统不支持其他特定于模型的报警MIB，则此对象为“0.0”。当支持特定于模型的报警MIB时，此对象为指向特定于模型的活动报警列表的实例指针。”
::= { alarmActiveEntry 14 }
::= { alarmActiveEntry 14 }
-- Active Alarm Variable Table --
--主动报警变量表--
alarmActiveVariableTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmActiveVariableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of variables to go with active alarm entries."
::= { alarmActive 3 }
alarmActiveVariableTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmActiveVariableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of variables to go with active alarm entries."
::= { alarmActive 3 }
alarmActiveVariableEntry OBJECT-TYPE SYNTAX AlarmActiveVariableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entries appear in this table when there are variables in the varbind list of a corresponding alarm in alarmActiveTable.
alarmActiveVariableEntry对象类型语法alarmActiveVariableEntry MAX-ACCESS不可访问状态当前描述“当alarmActiveTable中相应报警的varbind列表中存在变量时，此表中会出现条目。
Entries appear in this table as though the trap/notification had been transported using a SNMPv2-Trap-PDU, as defined in [RFC3416] - i.e., the alarmActiveVariableIndex 1 will always be sysUpTime and alarmActiveVariableIndex 2 will always be snmpTrapOID.
此表中的条目显示为陷阱/通知是使用[RFC3416]中定义的SNMPv2陷阱PDU传输的，即alarmActiveVariableIndex 1始终为sysUpTime，alarmActiveVariableIndex 2始终为snmpTrapOID。
If the incoming notification is instead an SNMPv1 Trap-PDU and
the value of alarmModelVarbindIndex is 1 or 2, an appropriate
value for sysUpTime.0 or snmpTrapOID.0 shall be determined
by using the rules in section 3.1 of [RFC3584]."
INDEX { alarmListName, alarmActiveIndex,
alarmActiveVariableIndex }
::= { alarmActiveVariableTable 1 }
If the incoming notification is instead an SNMPv1 Trap-PDU and
the value of alarmModelVarbindIndex is 1 or 2, an appropriate
value for sysUpTime.0 or snmpTrapOID.0 shall be determined
by using the rules in section 3.1 of [RFC3584]."
INDEX { alarmListName, alarmActiveIndex,
alarmActiveVariableIndex }
::= { alarmActiveVariableTable 1 }
AlarmActiveVariableEntry ::= SEQUENCE {
alarmActiveVariableIndex Unsigned32,
alarmActiveVariableID OBJECT IDENTIFIER,
alarmActiveVariableValueType INTEGER,
alarmActiveVariableCounter32Val Counter32,
alarmActiveVariableUnsigned32Val Unsigned32,
alarmActiveVariableTimeTicksVal TimeTicks,
alarmActiveVariableInteger32Val Integer32,
alarmActiveVariableOctetStringVal OCTET STRING,
alarmActiveVariableIpAddressVal IpAddress,
alarmActiveVariableOidVal OBJECT IDENTIFIER,
alarmActiveVariableCounter64Val Counter64,
AlarmActiveVariableEntry ::= SEQUENCE {
alarmActiveVariableIndex Unsigned32,
alarmActiveVariableID OBJECT IDENTIFIER,
alarmActiveVariableValueType INTEGER,
alarmActiveVariableCounter32Val Counter32,
alarmActiveVariableUnsigned32Val Unsigned32,
alarmActiveVariableTimeTicksVal TimeTicks,
alarmActiveVariableInteger32Val Integer32,
alarmActiveVariableOctetStringVal OCTET STRING,
alarmActiveVariableIpAddressVal IpAddress,
alarmActiveVariableOidVal OBJECT IDENTIFIER,
alarmActiveVariableCounter64Val Counter64,
alarmActiveVariableOpaqueVal Opaque }
alarmActiveVariableOpaqueVal不透明}
alarmActiveVariableIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A strictly monotonically increasing integer, starting at
1 for a given alarmActiveIndex, for indexing variables
within the active alarm variable list. "
::= { alarmActiveVariableEntry 1 }
alarmActiveVariableIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A strictly monotonically increasing integer, starting at
1 for a given alarmActiveIndex, for indexing variables
within the active alarm variable list. "
::= { alarmActiveVariableEntry 1 }
alarmActiveVariableID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The alarm variable's object identifier."
::= { alarmActiveVariableEntry 2 }
alarmActiveVariableID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The alarm variable's object identifier."
::= { alarmActiveVariableEntry 2 }
alarmActiveVariableValueType OBJECT-TYPE
SYNTAX INTEGER {
counter32(1),
unsigned32(2),
timeTicks(3),
integer32(4),
ipAddress(5),
octetString(6),
objectId(7),
counter64(8),
opaque(9)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the value. One and only one of the value
objects that follow is used for a given row in this table,
based on this type."
::= { alarmActiveVariableEntry 3 }
alarmActiveVariableValueType OBJECT-TYPE
SYNTAX INTEGER {
counter32(1),
unsigned32(2),
timeTicks(3),
integer32(4),
ipAddress(5),
octetString(6),
objectId(7),
counter64(8),
opaque(9)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the value. One and only one of the value
objects that follow is used for a given row in this table,
based on this type."
::= { alarmActiveVariableEntry 3 }
alarmActiveVariableCounter32Val OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'counter32'."
::= { alarmActiveVariableEntry 4 }
alarmActiveVariableCounter32Val OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'counter32'."
::= { alarmActiveVariableEntry 4 }
alarmActiveVariableUnsigned32Val OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'unsigned32'."
::= { alarmActiveVariableEntry 5 }
alarmActiveVariableUnsigned32Val OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'unsigned32'."
::= { alarmActiveVariableEntry 5 }
alarmActiveVariableTimeTicksVal OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'timeTicks'."
::= { alarmActiveVariableEntry 6 }
alarmActiveVariableTimeTicksVal OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'timeTicks'."
::= { alarmActiveVariableEntry 6 }
alarmActiveVariableInteger32Val OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'integer32'."
::= { alarmActiveVariableEntry 7 }
alarmActiveVariableInteger32Val OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'integer32'."
::= { alarmActiveVariableEntry 7 }
alarmActiveVariableOctetStringVal OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..65535))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'octetString'."
::= { alarmActiveVariableEntry 8 }
alarmActiveVariableOctetStringVal OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..65535))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'octetString'."
::= { alarmActiveVariableEntry 8 }
alarmActiveVariableIpAddressVal OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'ipAddress'."
::= { alarmActiveVariableEntry 9 }
alarmActiveVariableIpAddressVal OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'ipAddress'."
::= { alarmActiveVariableEntry 9 }
alarmActiveVariableOidVal OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'objectId'."
::= { alarmActiveVariableEntry 10 }
alarmActiveVariableOidVal OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'objectId'."
::= { alarmActiveVariableEntry 10 }
alarmActiveVariableCounter64Val OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'counter64'."
::= { alarmActiveVariableEntry 11 }
alarmActiveVariableCounter64Val OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when alarmActiveVariableType is 'counter64'."
::= { alarmActiveVariableEntry 11 }
alarmActiveVariableOpaqueVal OBJECT-TYPE SYNTAX Opaque (SIZE(0..65535)) MAX-ACCESS read-only STATUS current DESCRIPTION "The value when alarmActiveVariableType is 'opaque'.
alarmActiveVariableOpaqueVal对象类型语法不透明（大小（0..65535））MAX-ACCESS只读状态当前描述“alarmActiveVariableType为“不透明”时的值”。
Note that although RFC2578 [RFC2578] forbids the use
of Opaque in 'standard' MIB modules, this particular
usage is driven by the need to be able to accurately
represent any well-formed notification, and justified
by the need for backward compatibility."
::= { alarmActiveVariableEntry 12 }
Note that although RFC2578 [RFC2578] forbids the use
of Opaque in 'standard' MIB modules, this particular
usage is driven by the need to be able to accurately
represent any well-formed notification, and justified
by the need for backward compatibility."
::= { alarmActiveVariableEntry 12 }
-- Statistics --
--统计数字--
alarmActiveStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmActiveStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents the alarm statistics
information."
::= { alarmActive 4 }
alarmActiveStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmActiveStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents the alarm statistics
information."
::= { alarmActive 4 }
alarmActiveStatsEntry OBJECT-TYPE SYNTAX AlarmActiveStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Statistics on the current active alarms." INDEX { alarmListName }
AlarmActiveStatEntry对象类型语法AlarmActiveStatEntry MAX-ACCESS不可访问状态当前描述“当前活动报警的统计信息”。索引{alarmListName}
::= { alarmActiveStatsTable 1 }
::= { alarmActiveStatsTable 1 }
AlarmActiveStatsEntry ::=
SEQUENCE {
alarmActiveStatsActiveCurrent Gauge32,
alarmActiveStatsActives ZeroBasedCounter32,
alarmActiveStatsLastRaise TimeTicks,
AlarmActiveStatsEntry ::=
SEQUENCE {
alarmActiveStatsActiveCurrent Gauge32,
alarmActiveStatsActives ZeroBasedCounter32,
alarmActiveStatsLastRaise TimeTicks,
alarmActiveStatsLastClear TimeTicks }
alarmActiveStatsLastClear时间标记}
alarmActiveStatsActiveCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of currently active alarms on the system."
::= { alarmActiveStatsEntry 1 }
alarmActiveStatsActiveCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of currently active alarms on the system."
::= { alarmActiveStatsEntry 1 }
alarmActiveStatsActives OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of active alarms since system restarted."
::= { alarmActiveStatsEntry 2 }
alarmActiveStatsActives OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of active alarms since system restarted."
::= { alarmActiveStatsEntry 2 }
alarmActiveStatsLastRaise OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the last
alarm raise for this alarm list.
If no alarm raises have occurred since the
last re-initialization of the local network management
subsystem, then this object contains a zero value."
::= { alarmActiveStatsEntry 3 }
alarmActiveStatsLastRaise OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the last
alarm raise for this alarm list.
If no alarm raises have occurred since the
last re-initialization of the local network management
subsystem, then this object contains a zero value."
::= { alarmActiveStatsEntry 3 }
alarmActiveStatsLastClear OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the last
alarm clear for this alarm list.
If no alarm clears have occurred since the
last re-initialization of the local network management
subsystem, then this object contains a zero value."
::= { alarmActiveStatsEntry 4 }
alarmActiveStatsLastClear OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the last
alarm clear for this alarm list.
If no alarm clears have occurred since the
last re-initialization of the local network management
subsystem, then this object contains a zero value."
::= { alarmActiveStatsEntry 4 }
-- Alarm Clear
--警报解除
alarmClearMaximum OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write
alarmClearMaximum对象类型语法无符号32 MAX-ACCESS读写
STATUS current
DESCRIPTION
"This object specifies the maximum number of cleared
alarms to store in the alarmClearTable. When this
number is reached, the cleared alarms with the
earliest clear time will be removed from the table."
::= { alarmClear 1 }
STATUS current
DESCRIPTION
"This object specifies the maximum number of cleared
alarms to store in the alarmClearTable. When this
number is reached, the cleared alarms with the
earliest clear time will be removed from the table."
::= { alarmClear 1 }
alarmClearTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmClearEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information on
cleared alarms."
::= { alarmClear 2 }
alarmClearTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmClearEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information on
cleared alarms."
::= { alarmClear 2 }
alarmClearEntry OBJECT-TYPE SYNTAX AlarmClearEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information on a cleared alarm." INDEX { alarmListName, alarmClearDateAndTime, alarmClearIndex }
alarmClearEntry对象类型语法alarmClearEntry MAX-ACCESS不可访问状态当前描述“已清除报警的信息”。索引{alarmListName，alarmClearDateAndTime，alarmClearIndex}
::= { alarmClearTable 1 }
::= { alarmClearTable 1 }
AlarmClearEntry ::=
SEQUENCE {
alarmClearIndex Unsigned32,
alarmClearDateAndTime DateAndTime,
alarmClearEngineID LocalSnmpEngineOrZeroLenStr,
alarmClearEngineAddressType InetAddressType,
alarmClearEngineAddress InetAddress,
alarmClearContextName SnmpAdminString,
alarmClearNotificationID OBJECT IDENTIFIER,
alarmClearResourceId ResourceId,
alarmClearLogIndex Unsigned32,
alarmClearModelPointer RowPointer
}
AlarmClearEntry ::=
SEQUENCE {
alarmClearIndex Unsigned32,
alarmClearDateAndTime DateAndTime,
alarmClearEngineID LocalSnmpEngineOrZeroLenStr,
alarmClearEngineAddressType InetAddressType,
alarmClearEngineAddress InetAddress,
alarmClearContextName SnmpAdminString,
alarmClearNotificationID OBJECT IDENTIFIER,
alarmClearResourceId ResourceId,
alarmClearLogIndex Unsigned32,
alarmClearModelPointer RowPointer
}
alarmClearIndex OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An integer which acts as the index of entries within
alarmClearIndex对象类型语法Unsigned32（1..4294967295）MAX-ACCESS不可访问状态当前描述“一个整数，用作
the named alarm list. It wraps back to 1 after it reaches its maximum value.
已命名的报警列表。在达到最大值后，它会返回到1。
This object has the same value as the alarmActiveIndex that
this alarm instance had when it was active."
::= { alarmClearEntry 1 }
This object has the same value as the alarmActiveIndex that
this alarm instance had when it was active."
::= { alarmClearEntry 1 }
alarmClearDateAndTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS not-accessible STATUS current DESCRIPTION "The local date and time when the alarm cleared.
alarmClearDateAndTime对象类型语法DateAndTime MAX-ACCESS不可访问状态当前描述“报警清除时的本地日期和时间。
This object facilitates retrieving all instances of alarms that have been cleared since a given point in time.
此对象有助于检索自给定时间点以来已清除的所有报警实例。
Implementations MUST include the offset from UTC,
if available. Implementation in environments in which
the UTC offset is not available is NOT RECOMMENDED."
::= { alarmClearEntry 2 }
Implementations MUST include the offset from UTC,
if available. Implementation in environments in which
the UTC offset is not available is NOT RECOMMENDED."
::= { alarmClearEntry 2 }
alarmClearEngineID OBJECT-TYPE
SYNTAX LocalSnmpEngineOrZeroLenStr
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identification of the SNMP engine at which the alarm
originated. If the alarm is from an SNMPv1 system this
object is a zero length string."
::= { alarmClearEntry 3 }
alarmClearEngineID OBJECT-TYPE
SYNTAX LocalSnmpEngineOrZeroLenStr
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identification of the SNMP engine at which the alarm
originated. If the alarm is from an SNMPv1 system this
object is a zero length string."
::= { alarmClearEntry 3 }
alarmClearEngineAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates what type of address is stored in
the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc."
::= { alarmClearEntry 4 }
alarmClearEngineAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates what type of address is stored in
the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc."
::= { alarmClearEntry 4 }
alarmClearEngineAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The Address of the SNMP engine on which the alarm was occurring. This is used to identify the source of an SNMPv1
alarmClearEngineAddress对象类型语法InetAddress MAX-ACCESS只读状态当前描述“发生报警的SNMP引擎的地址。此地址用于标识SNMPv1的源
trap, since an alarmActiveEngineId cannot be extracted from the SNMPv1 trap PDU.
陷阱，因为无法从SNMPv1陷阱PDU提取alarmActiveEngineId。
This object MUST always be instantiated, even if the list
can contain alarms from only one engine."
::= { alarmClearEntry 5 }
This object MUST always be instantiated, even if the list
can contain alarms from only one engine."
::= { alarmClearEntry 5 }
alarmClearContextName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the SNMP MIB context from which the alarm came. For SNMPv1 traps this is the community string from the Trap. Note that care needs to be taken when selecting community strings to ensure that these can be represented as a well-formed SnmpAdminString. Community or Context names that are not well-formed SnmpAdminStrings will be mapped to zero length strings.
alarmClearContextName对象类型语法SnmpAdminString（大小（0..32））最大访问只读状态当前说明“报警来自的SNMP MIB上下文的名称。对于SNMPv1陷阱，这是陷阱中的社区字符串。请注意，在选择社区字符串时需要小心，以确保这些字符串可以表示为格式良好的snmpadmin字符串。格式不正确的snmpadmin字符串的社区或上下文名称将映射到零长度字符串。
If the alarm's source SNMP engine is known not to support
multiple contexts, this object is a zero length string."
::= { alarmClearEntry 6 }
If the alarm's source SNMP engine is known not to support
multiple contexts, this object is a zero length string."
::= { alarmClearEntry 6 }
alarmClearNotificationID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NOTIFICATION-TYPE object identifier of the alarm
clear."
::= { alarmClearEntry 7 }
alarmClearNotificationID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NOTIFICATION-TYPE object identifier of the alarm
clear."
::= { alarmClearEntry 7 }
alarmClearResourceId OBJECT-TYPE SYNTAX ResourceId MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the resource that was under alarm.
alarmClearResourceId对象类型语法ResourceId MAX-ACCESS只读状态当前描述“此对象标识处于报警状态的资源。
If there is no corresponding resource, then
the value of this object MUST be 0.0."
::= { alarmClearEntry 8 }
If there is no corresponding resource, then
the value of this object MUST be 0.0."
::= { alarmClearEntry 8 }
alarmClearLogIndex OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS read-only STATUS current
AlarmClearLoginEx对象类型语法Unsigned32（0..4294967295）最大访问只读状态当前
DESCRIPTION
"This number MUST be the same as the log index of the
applicable row in the notification log MIB, if it exists.
If no log index applies to the trap, then this object
MUST have the value of 0."
::= { alarmClearEntry 9 }
DESCRIPTION
"This number MUST be the same as the log index of the
applicable row in the notification log MIB, if it exists.
If no log index applies to the trap, then this object
MUST have the value of 0."
::= { alarmClearEntry 9 }
alarmClearModelPointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A pointer to the corresponding row in the
alarmModelTable for this cleared alarm."
::= { alarmClearEntry 10 }
alarmClearModelPointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A pointer to the corresponding row in the
alarmModelTable for this cleared alarm."
::= { alarmClearEntry 10 }
-- Notifications
--通知
alarmActiveState NOTIFICATION-TYPE OBJECTS { alarmActiveModelPointer, alarmActiveResourceId } STATUS current DESCRIPTION "An instance of the alarm indicated by alarmActiveModelPointer has been raised against the entity indicated by alarmActiveResourceId.
alarmActiveState通知类型对象{alarmActiveModelPointer，alarmActiveResourceId}状态当前描述“已针对alarmActiveResourceId指示的实体引发了alarmActiveModelPointer指示的报警实例。
The agent must throttle the generation of consecutive alarmActiveState traps so that there is at least a two-second gap between traps of this type against the same alarmActiveModelPointer and alarmActiveResourceId. When traps are throttled, they are dropped, not queued for sending at a future time.
代理必须限制连续alarmActiveState陷阱的生成，以便针对同一alarmActiveModelPointer和alarmActiveResourceId的此类陷阱之间至少有两秒钟的间隔。当陷阱被限制时，它们将被丢弃，而不是排队等待将来发送。
A management application should periodically check
the value of alarmActiveLastChanged to detect any
missed alarmActiveState notification-events, e.g.,
due to throttling or transmission loss."
::= { alarmNotifications 2 }
A management application should periodically check
the value of alarmActiveLastChanged to detect any
missed alarmActiveState notification-events, e.g.,
due to throttling or transmission loss."
::= { alarmNotifications 2 }
alarmClearState NOTIFICATION-TYPE OBJECTS { alarmActiveModelPointer, alarmActiveResourceId } STATUS current DESCRIPTION "An instance of the alarm indicated by alarmActiveModelPointer has been cleared against
alarmClearState通知类型对象{alarmActiveModelPointer，alarmActiveResourceId}状态当前描述“已清除alarmActiveModelPointer指示的报警实例
the entity indicated by alarmActiveResourceId.
alarmActiveResourceId指示的实体。
The agent must throttle the generation of consecutive alarmActiveClear traps so that there is at least a two-second gap between traps of this type against the same alarmActiveModelPointer and alarmActiveResourceId. When traps are throttled, they are dropped, not queued for sending at a future time.
代理必须限制连续alarmActiveClear陷阱的生成，以便针对同一alarmActiveModelPointer和alarmActiveResourceId的此类型陷阱之间至少有两秒钟的间隔。当陷阱被限制时，它们将被丢弃，而不是排队等待将来发送。
A management application should periodically check
the value of alarmActiveLastChanged to detect any
missed alarmClearState notification-events, e.g.,
due to throttling or transmission loss."
::= { alarmNotifications 3 }
A management application should periodically check
the value of alarmActiveLastChanged to detect any
missed alarmClearState notification-events, e.g.,
due to throttling or transmission loss."
::= { alarmNotifications 3 }
-- Conformance
--一致性
alarmConformance OBJECT IDENTIFIER ::= { alarmMIB 2 }
alarmConformance OBJECT IDENTIFIER ::= { alarmMIB 2 }
alarmCompliances OBJECT IDENTIFIER ::= { alarmConformance 1 }
alarmCompliances OBJECT IDENTIFIER ::= { alarmConformance 1 }
alarmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems supporting
the Alarm MIB."
MODULE -- this module
MANDATORY-GROUPS {
alarmActiveGroup,
alarmModelGroup
}
GROUP alarmActiveStatsGroup
DESCRIPTION
"This group is optional."
GROUP alarmClearGroup
DESCRIPTION
"This group is optional."
GROUP alarmNotificationsGroup
DESCRIPTION
"This group is optional."
::= { alarmCompliances 1 }
alarmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems supporting
the Alarm MIB."
MODULE -- this module
MANDATORY-GROUPS {
alarmActiveGroup,
alarmModelGroup
}
GROUP alarmActiveStatsGroup
DESCRIPTION
"This group is optional."
GROUP alarmClearGroup
DESCRIPTION
"This group is optional."
GROUP alarmNotificationsGroup
DESCRIPTION
"This group is optional."
::= { alarmCompliances 1 }
alarmGroups OBJECT IDENTIFIER ::= { alarmConformance 2 }
alarmGroups OBJECT IDENTIFIER ::= { alarmConformance 2 }
alarmModelGroup OBJECT-GROUP OBJECTS { alarmModelLastChanged, alarmModelNotificationId,
alarmModelGroup对象组对象{alarmModelLastChanged，alarmModelNotificationId，
alarmModelVarbindIndex,
alarmModelVarbindValue,
alarmModelDescription,
alarmModelSpecificPointer,
alarmModelVarbindSubtree,
alarmModelResourcePrefix,
alarmModelRowStatus
}
STATUS current
DESCRIPTION
"Alarm model group."
::= { alarmGroups 1}
alarmModelVarbindIndex,
alarmModelVarbindValue,
alarmModelDescription,
alarmModelSpecificPointer,
alarmModelVarbindSubtree,
alarmModelResourcePrefix,
alarmModelRowStatus
}
STATUS current
DESCRIPTION
"Alarm model group."
::= { alarmGroups 1}
alarmActiveGroup OBJECT-GROUP
OBJECTS {
alarmActiveLastChanged,
alarmActiveOverflow,
alarmActiveEngineID,
alarmActiveEngineAddressType,
alarmActiveEngineAddress,
alarmActiveContextName,
alarmActiveVariables,
alarmActiveNotificationID,
alarmActiveResourceId,
alarmActiveDescription,
alarmActiveLogPointer,
alarmActiveModelPointer,
alarmActiveSpecificPointer,
alarmActiveVariableID,
alarmActiveVariableValueType,
alarmActiveVariableCounter32Val,
alarmActiveVariableUnsigned32Val,
alarmActiveVariableTimeTicksVal,
alarmActiveVariableInteger32Val,
alarmActiveVariableOctetStringVal,
alarmActiveVariableIpAddressVal,
alarmActiveVariableOidVal,
alarmActiveVariableCounter64Val,
alarmActiveVariableOpaqueVal
}
STATUS current
DESCRIPTION
"Active Alarm list group."
::= { alarmGroups 2}
alarmActiveGroup OBJECT-GROUP
OBJECTS {
alarmActiveLastChanged,
alarmActiveOverflow,
alarmActiveEngineID,
alarmActiveEngineAddressType,
alarmActiveEngineAddress,
alarmActiveContextName,
alarmActiveVariables,
alarmActiveNotificationID,
alarmActiveResourceId,
alarmActiveDescription,
alarmActiveLogPointer,
alarmActiveModelPointer,
alarmActiveSpecificPointer,
alarmActiveVariableID,
alarmActiveVariableValueType,
alarmActiveVariableCounter32Val,
alarmActiveVariableUnsigned32Val,
alarmActiveVariableTimeTicksVal,
alarmActiveVariableInteger32Val,
alarmActiveVariableOctetStringVal,
alarmActiveVariableIpAddressVal,
alarmActiveVariableOidVal,
alarmActiveVariableCounter64Val,
alarmActiveVariableOpaqueVal
}
STATUS current
DESCRIPTION
"Active Alarm list group."
::= { alarmGroups 2}
alarmActiveStatsGroup OBJECT-GROUP OBJECTS { alarmActiveStatsActives,
alarmActiveStatsGroup对象组对象{alarmActiveStatsActives，
alarmActiveStatsActiveCurrent,
alarmActiveStatsLastRaise,
alarmActiveStatsLastClear
}
STATUS current
DESCRIPTION
"Active alarm summary group."
::= { alarmGroups 3}
alarmActiveStatsActiveCurrent,
alarmActiveStatsLastRaise,
alarmActiveStatsLastClear
}
STATUS current
DESCRIPTION
"Active alarm summary group."
::= { alarmGroups 3}
alarmClearGroup OBJECT-GROUP
OBJECTS {
alarmClearMaximum,
alarmClearEngineID,
alarmClearEngineAddressType,
alarmClearEngineAddress,
alarmClearContextName,
alarmClearNotificationID,
alarmClearResourceId,
alarmClearLogIndex,
alarmClearModelPointer
}
STATUS current
DESCRIPTION
"Cleared alarm group."
::= { alarmGroups 4}
alarmClearGroup OBJECT-GROUP
OBJECTS {
alarmClearMaximum,
alarmClearEngineID,
alarmClearEngineAddressType,
alarmClearEngineAddress,
alarmClearContextName,
alarmClearNotificationID,
alarmClearResourceId,
alarmClearLogIndex,
alarmClearModelPointer
}
STATUS current
DESCRIPTION
"Cleared alarm group."
::= { alarmGroups 4}
alarmNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { alarmActiveState, alarmClearState }
STATUS current
DESCRIPTION
"The collection of notifications that can be used to
model alarms for faults lacking pre-existing
notification definitions."
::= { alarmGroups 6 }
alarmNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { alarmActiveState, alarmClearState }
STATUS current
DESCRIPTION
"The collection of notifications that can be used to
model alarms for faults lacking pre-existing
notification definitions."
::= { alarmGroups 6 }
END
终止
This MIB module defines alarm information specific to the alarm model defined in ITU M.3100 [M.3100], X.733 [X.733], and X.736 [X.736]. This MIB module follows the modular architecture defined by the Alarm MIB, in which the generic Alarm MIB can be augmented by other alarm information defined according to more specific models that define additional behaviour and characteristics.
该MIB模块定义了特定于ITU M.3100[M.3100]、X.733[X.733]和X.736[X.736]中定义的报警模型的报警信息。该MIB模块遵循报警MIB定义的模块化体系结构，在该体系结构中，通用报警MIB可通过根据定义其他行为和特征的更具体模型定义的其他报警信息进行扩充。
The ituAlarmTable contains information from the ITU Alarm Model about possible alarms in the system.
iTuarmTable包含来自ITU警报模型的关于系统中可能警报的信息。
The ituAlarmActiveTable contains information from the ITU Alarm Model about alarms modelled using the ituAlarmTable that are currently occurring on the system.
iTuarmActiveTable包含来自ITU报警模型的关于使用iTuarmTable建模的系统上当前发生的报警的信息。
The ituAlarmActiveStatsTable provides statistics on current and total alarms.
iTuarmActiveStatsTable提供当前和总报警的统计信息。
Over time, there will be a need to add new IANAITUEventType and IANAItuProbableCause enumerated values. The Internet Assigned Number Authority (IANA) is responsible for the assignment of the enumerations in these TCs.
随着时间的推移，将需要添加新的IAAItueVentType和IAAItupUpbableCause枚举值。互联网分配号码管理局（IANA）负责分配这些TC中的枚举。
IANAItuProbableCause value of 0 is reserved for special purposes and MUST NOT be assigned. Values of IANAItuProbableCause in the range 1 to 1023 are reserved for causes that correspond to ITU-T probable cause. All other requests for new causes will be handled on a first-come basis, with 1025.
IANAITUPBABLECAUSE值0是为特殊目的而保留的，不得分配。1至1023范围内的IANAITUPBABLECAUSE值保留用于对应于ITU-T可能原因的原因。所有其他新原因的请求将以先到的方式处理，共1025个。
Request should come in the form of well-formed SMI [RFC2578] for enumeration names that are unique and sufficiently descriptive.
请求应以格式良好的SMI[RFC2578]的形式提出，以获得唯一且具有足够描述性的枚举名称。
While some effort will be taken to ensure that new enumerations do not conceptually duplicate existing enumerations it is acknowledged that the existence of conceptual duplicates in the starting probable cause list is an known industry reality.
虽然将采取一些措施确保新的枚举不会在概念上重复现有的枚举，但必须承认，在起始可能原因列表中存在概念上的重复是已知的行业现实。
To aid IANA in the administration of probable cause names and values, the OPS Area Director will appoint one or more experts to help review requests.
为了帮助IANA管理可能原因名称和值，OPS区域总监将任命一名或多名专家帮助审查请求。
See http://www.iana.org
See http://www.iana.org
The following shall be used as the initial values, but the latest values for these textual conventions should be obtained from IANA:
以下应作为初始值，但这些文本约定的最新值应从IANA获得：
IANA-ITU-ALARM-TC-MIB DEFINITIONS ::= BEGIN
IANA-ITU-ALARM-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- [RFC2578] TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579]
从SNMPv2 SMI导入模块标识mib-2--[RFC2578]从SNMPv2 TC导入文本约定；--[RFC2579]
ianaItuAlarmNumbers MODULE-IDENTITY LAST-UPDATED "200409090000Z" -- September 09, 2004 ORGANIZATION "IANA" CONTACT-INFO "Postal: Internet Assigned Numbers Authority Internet Corporation for Assigned Names and Numbers 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292-6601 USA
ianaItuAlarmNumbers MODULE-IDENTITY最后更新的“200409090000Z”--2004年9月9日组织“IANA”联系信息邮寄：互联网指定号码管理局指定姓名和号码互联网公司4676金钟路330号，美国加利福尼亚州马里纳德雷，邮编90292-6601
Tel: +1 310-823-9358 E-Mail: iana@iana.org" DESCRIPTION "The MIB module defines the ITU Alarm textual convention for objects expected to require regular extension.
电话：+1310-823-9358电子邮件：iana@iana.org“说明”MIB模块为预期需要定期扩展的对象定义ITU警报文本约定。
Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3877. For full legal notices see the RFC
itself. Supplementary information may be available on:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "200409090000Z" -- September 09, 2004
DESCRIPTION
"Initial version, published as RFC 3877."
::= { mib-2 119 }
Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3877. For full legal notices see the RFC
itself. Supplementary information may be available on:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "200409090000Z" -- September 09, 2004
DESCRIPTION
"Initial version, published as RFC 3877."
::= { mib-2 119 }
IANAItuProbableCause ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ITU-T probable cause values. Duplicate values defined in
X.733 are appended with X733 to ensure syntactic uniqueness.
Probable cause value 0 is reserved for special purposes.
IANAItuProbableCause ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ITU-T probable cause values. Duplicate values defined in
X.733 are appended with X733 to ensure syntactic uniqueness.
Probable cause value 0 is reserved for special purposes.
The Internet Assigned Number Authority (IANA) is responsible for the assignment of the enumerations in this TC. IANAItuProbableCause value of 0 is reserved for special purposes and MUST NOT be assigned.
Internet分配号码管理局（IANA）负责分配此TC中的枚举。IANAITUPBABLECAUSE值0是为特殊目的而保留的，不得分配。
Values of IANAItuProbableCause in the range 1 to 1023 are reserved for causes that correspond to ITU-T probable cause.
1至1023范围内的IANAITUPBABLECAUSE值保留用于对应于ITU-T可能原因的原因。
All other requests for new causes will be handled on a first-come, first served basis and will be assigned enumeration values starting with 1025.
所有其他新原因的请求将以先到先得的方式处理，并将从1025开始分配枚举值。
Request should come in the form of well-formed
请求应以格式良好的
SMI [RFC2578] for enumeration names that are unique and sufficiently descriptive.
SMI[RFC2578]用于唯一且具有足够描述性的枚举名称。
While some effort will be taken to ensure that new probable causes do not conceptually duplicate existing probable causes it is acknowledged that the existence of conceptual duplicates in the starting probable cause list is an known industry reality.
虽然将采取一些措施确保新的可能原因不会在概念上与现有的可能原因重复，但我们承认，在开始的可能原因列表中存在概念上的重复是已知的行业现实。
To aid IANA in the administration of probable cause names and values, the OPS Area Director will appoint one or more experts to help review requests.
为了帮助IANA管理可能原因名称和值，OPS区域总监将任命一名或多名专家帮助审查请求。
See http://www.iana.org" REFERENCE "ITU Recommendation M.3100, 'Generic Network Information Model', 1995 ITU Recommendation X.733, 'Information Technology - Open Systems Interconnection - System Management: Alarm Reporting Function', 1992 ITU Recommendation X.736, 'Information Technology - Open Systems Interconnection - System Management: Security Alarm Reporting Function', 1992"
看见http://www.iana.org“参考”ITU建议M.3100，“通用网络信息模型”，1995年ITU建议X.733，“信息技术-开放系统互连-系统管理：报警报告功能”，1992年ITU建议X.736，“信息技术.开放系统互连.系统管理：安全报警报告功能”，1992年
SYNTAX INTEGER { -- The following probable causes were defined in M.3100 aIS (1), callSetUpFailure (2), degradedSignal (3), farEndReceiverFailure (4), framingError (5), lossOfFrame (6), lossOfPointer (7), lossOfSignal (8), payloadTypeMismatch (9), transmissionError (10), remoteAlarmInterface (11), excessiveBER (12), pathTraceMismatch (13), unavailable (14), signalLabelMismatch (15), lossOfMultiFrame (16), receiveFailure (17), transmitFailure (18), modulationFailure (19), demodulationFailure (20), broadcastChannelFailure (21),
语法整数{--在M.3100 aIS（1）、callSetUpFailure（2）、degradedSignal（3）、farEndReceiverFailure（4）、framingError（5）、lossOfFrame（6）、lossOfPointer（7）、lossOfSignal（8）、payloadTypeMismatch（9）、transmissionError（10）、remoteAlarmInterface（11）、excessiveBER（12）、PathTraceMissionMatch（13）中定义了以下可能的原因，不可用（14），信号标签不匹配（15），多帧丢失（16），接收失败（17），传输失败（18），调制失败（19），解调失败（20），广播信道失败（21），
connectionEstablishmentError (22), invalidMessageReceived (23), localNodeTransmissionError (24), remoteNodeTransmissionError (25), routingFailure (26),
connectionEstablishmentError（22）、invalidMessageReceived（23）、localNodeTransmissionError（24）、remoteNodeTransmissionError（25）、routingFailure（26），
--Values 27-50 are reserved for communications alarm related --probable causes -- The following are used with equipment alarm.
--值27-50保留用于通信报警相关——可能原因——以下用于设备报警。
backplaneFailure (51),
dataSetProblem (52),
equipmentIdentifierDuplication (53),
externalIFDeviceProblem (54),
lineCardProblem (55),
multiplexerProblem (56),
nEIdentifierDuplication (57),
powerProblem (58),
processorProblem (59),
protectionPathFailure (60),
receiverFailure (61),
replaceableUnitMissing (62),
replaceableUnitTypeMismatch (63),
synchronizationSourceMismatch (64),
terminalProblem (65),
timingProblem (66),
transmitterFailure (67),
trunkCardProblem (68),
replaceableUnitProblem (69),
realTimeClockFailure (70),
--An equipment alarm to be issued if the system detects that the
--real time clock has failed
antennaFailure (71),
batteryChargingFailure (72),
diskFailure (73),
frequencyHoppingFailure (74),
iODeviceError (75),
lossOfSynchronisation (76),
lossOfRedundancy (77),
powerSupplyFailure (78),
signalQualityEvaluationFailure (79),
tranceiverFailure (80),
protectionMechanismFailure (81),
protectingResourceFailure (82),
-- Values 83-100 are reserved for equipment alarm related probable
-- causes
-- The following are used with environmental alarm.
airCompressorFailure (101),
backplaneFailure (51),
dataSetProblem (52),
equipmentIdentifierDuplication (53),
externalIFDeviceProblem (54),
lineCardProblem (55),
multiplexerProblem (56),
nEIdentifierDuplication (57),
powerProblem (58),
processorProblem (59),
protectionPathFailure (60),
receiverFailure (61),
replaceableUnitMissing (62),
replaceableUnitTypeMismatch (63),
synchronizationSourceMismatch (64),
terminalProblem (65),
timingProblem (66),
transmitterFailure (67),
trunkCardProblem (68),
replaceableUnitProblem (69),
realTimeClockFailure (70),
--An equipment alarm to be issued if the system detects that the
--real time clock has failed
antennaFailure (71),
batteryChargingFailure (72),
diskFailure (73),
frequencyHoppingFailure (74),
iODeviceError (75),
lossOfSynchronisation (76),
lossOfRedundancy (77),
powerSupplyFailure (78),
signalQualityEvaluationFailure (79),
tranceiverFailure (80),
protectionMechanismFailure (81),
protectingResourceFailure (82),
-- Values 83-100 are reserved for equipment alarm related probable
-- causes
-- The following are used with environmental alarm.
airCompressorFailure (101),
airConditioningFailure (102),
airDryerFailure (103),
batteryDischarging (104),
batteryFailure (105),
commercialPowerFailure (106),
coolingFanFailure (107),
engineFailure (108),
fireDetectorFailure (109),
fuseFailure (110),
generatorFailure (111),
lowBatteryThreshold (112),
pumpFailure (113),
rectifierFailure (114),
rectifierHighVoltage (115),
rectifierLowFVoltage (116),
ventilationsSystemFailure (117),
enclosureDoorOpen (118),
explosiveGas (119),
fire (120),
flood (121),
highHumidity (122),
highTemperature (123),
highWind (124),
iceBuildUp (125),
intrusionDetection (126),
lowFuel (127),
lowHumidity (128),
lowCablePressure (129),
lowTemperatue (130),
lowWater (131),
smoke (132),
toxicGas (133),
coolingSystemFailure (134),
externalEquipmentFailure (135),
externalPointFailure (136),
-- Values 137-150 are reserved for environmental alarm related
-- probable causes
-- The following are used with Processing error alarm.
storageCapacityProblem (151),
memoryMismatch (152),
corruptData (153),
outOfCPUCycles (154),
sfwrEnvironmentProblem (155),
sfwrDownloadFailure (156),
lossOfRealTimel (157),
--A processing error alarm to be issued after the system has
--reinitialised. This will indicate
--to the management systems that the view they have of the managed
airConditioningFailure (102),
airDryerFailure (103),
batteryDischarging (104),
batteryFailure (105),
commercialPowerFailure (106),
coolingFanFailure (107),
engineFailure (108),
fireDetectorFailure (109),
fuseFailure (110),
generatorFailure (111),
lowBatteryThreshold (112),
pumpFailure (113),
rectifierFailure (114),
rectifierHighVoltage (115),
rectifierLowFVoltage (116),
ventilationsSystemFailure (117),
enclosureDoorOpen (118),
explosiveGas (119),
fire (120),
flood (121),
highHumidity (122),
highTemperature (123),
highWind (124),
iceBuildUp (125),
intrusionDetection (126),
lowFuel (127),
lowHumidity (128),
lowCablePressure (129),
lowTemperatue (130),
lowWater (131),
smoke (132),
toxicGas (133),
coolingSystemFailure (134),
externalEquipmentFailure (135),
externalPointFailure (136),
-- Values 137-150 are reserved for environmental alarm related
-- probable causes
-- The following are used with Processing error alarm.
storageCapacityProblem (151),
memoryMismatch (152),
corruptData (153),
outOfCPUCycles (154),
sfwrEnvironmentProblem (155),
sfwrDownloadFailure (156),
lossOfRealTimel (157),
--A processing error alarm to be issued after the system has
--reinitialised. This will indicate
--to the management systems that the view they have of the managed
--system may no longer
--be valid. Usage example: The managed
--system issues this alarm after a reinitialization with severity
--warning to inform the
--management system about the event. No clearing notification will
--be sent.
applicationSubsystemFailure (158),
configurationOrCustomisationError (159),
databaseInconsistency (160),
fileError (161),
outOfMemory (162),
softwareError (163),
timeoutExpired (164),
underlayingResourceUnavailable (165),
versionMismatch (166),
--Values 168-200 are reserved for processing error alarm related
-- probable causes.
bandwidthReduced (201),
congestion (202),
excessiveErrorRate (203),
excessiveResponseTime (204),
excessiveRetransmissionRate (205),
reducedLoggingCapability (206),
systemResourcesOverload (207 ),
-- The following were defined X.733
adapterError (500),
applicationSubsystemFailture (501),
bandwidthReducedX733 (502),
callEstablishmentError (503),
communicationsProtocolError (504),
communicationsSubsystemFailure (505),
configurationOrCustomizationError (506),
congestionX733 (507),
coruptData (508),
cpuCyclesLimitExceeded (509),
dataSetOrModemError (510),
degradedSignalX733 (511),
dteDceInterfaceError (512),
enclosureDoorOpenX733 (513),
equipmentMalfunction (514),
excessiveVibration (515),
fileErrorX733 (516),
fireDetected (517),
framingErrorX733 (518),
heatingVentCoolingSystemProblem (519),
humidityUnacceptable (520),
inputOutputDeviceError (521),
inputDeviceError (522),
--system may no longer
--be valid. Usage example: The managed
--system issues this alarm after a reinitialization with severity
--warning to inform the
--management system about the event. No clearing notification will
--be sent.
applicationSubsystemFailure (158),
configurationOrCustomisationError (159),
databaseInconsistency (160),
fileError (161),
outOfMemory (162),
softwareError (163),
timeoutExpired (164),
underlayingResourceUnavailable (165),
versionMismatch (166),
--Values 168-200 are reserved for processing error alarm related
-- probable causes.
bandwidthReduced (201),
congestion (202),
excessiveErrorRate (203),
excessiveResponseTime (204),
excessiveRetransmissionRate (205),
reducedLoggingCapability (206),
systemResourcesOverload (207 ),
-- The following were defined X.733
adapterError (500),
applicationSubsystemFailture (501),
bandwidthReducedX733 (502),
callEstablishmentError (503),
communicationsProtocolError (504),
communicationsSubsystemFailure (505),
configurationOrCustomizationError (506),
congestionX733 (507),
coruptData (508),
cpuCyclesLimitExceeded (509),
dataSetOrModemError (510),
degradedSignalX733 (511),
dteDceInterfaceError (512),
enclosureDoorOpenX733 (513),
equipmentMalfunction (514),
excessiveVibration (515),
fileErrorX733 (516),
fireDetected (517),
framingErrorX733 (518),
heatingVentCoolingSystemProblem (519),
humidityUnacceptable (520),
inputOutputDeviceError (521),
inputDeviceError (522),
lanError (523), leakDetected (524), localNodeTransmissionErrorX733 (525), lossOfFrameX733 (526), lossOfSignalX733 (527), materialSupplyExhausted (528), multiplexerProblemX733 (529), outOfMemoryX733 (530), ouputDeviceError (531), performanceDegraded (532), powerProblems (533), pressureUnacceptable (534), processorProblems (535), pumpFailureX733 (536), queueSizeExceeded (537), receiveFailureX733 (538), receiverFailureX733 (539), remoteNodeTransmissionErrorX733 (540), resourceAtOrNearingCapacity (541), responseTimeExecessive (542), retransmissionRateExcessive (543), softwareErrorX733 (544), softwareProgramAbnormallyTerminated (545), softwareProgramError (546), storageCapacityProblemX733 (547), temperatureUnacceptable (548), thresholdCrossed (549), timingProblemX733 (550), toxicLeakDetected (551), transmitFailureX733 (552), transmiterFailure (553), underlyingResourceUnavailable (554), versionMismatchX733 (555), -- The following are defined in X.736 authenticationFailure (600), breachOfConfidentiality (601), cableTamper (602), delayedInformation (603), denialOfService (604), duplicateInformation (605), informationMissing (606), informationModificationDetected (607), informationOutOfSequence (608), keyExpired (609), nonRepudiationFailure (610), outOfHoursActivity (611), outOfService (612), proceduralError (613),
lanError（523）、leakDetected（524）、localNodeTransmissionErrorX733（525）、FrameX733（526）、SignalX733（527）丢失、材料供应耗尽（528）、多路复用器问题X733（529）、outOfMemoryX733（530）、输出设备错误（531）、性能降级（532）、电源问题（533）、压力不可接受（534）、处理器问题（535）、泵故障X733（536）、QueueSizeExceed（537）、receiveFailureX733（538）、receiveFailureX733（539）、remoteNodeTransmissionErrorX733（540）、resourceAtOrNearingCapacity（541）、responseTimeExecessive（542）、RetransmissionRate Oversed（543）、softwareErrorX733（544）、SoftwareProgram异常终止（545）、softwareProgramError（546）、StorageCapacity问题X733（547）、温度不可接受（548）、阈值交叉（549）、计时问题X733（550）、检测到的有毒物质（551）、传输失败X733（552）、传输失败（553）、底层资源不可用（554）、版本匹配X733（555）——以下内容在X.736身份验证失败（600）、违反身份验证（601）、电缆篡改（602）中定义、延迟信息（603）、拒绝服务（604）、重复信息（605）、信息丢失（606）、检测到的信息修改（607）、信息失效（608）、密钥失效（609）、非否认故障（610）、资源失效（611）、服务失效（612）、程序错误（613），
unauthorizedAccessAttempt (614), unexpectedInformation (615),
未经授权的访问企图（614）、意外信息（615），
other (1024) }
其他（1024）}
IANAItuEventType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The ITU event Type values.
IANAItuEventType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The ITU event Type values.
The Internet Assigned Number Authority (IANA) is responsible for the assignment of the enumerations in this TC.
Internet分配号码管理局（IANA）负责分配此TC中的枚举。
Request should come in the form of well-formed SMI [RFC2578] for enumeration names that are unique and sufficiently descriptive.
请求应以格式良好的SMI[RFC2578]的形式提出，以获得唯一且具有足够描述性的枚举名称。
See http://www.iana.org "
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
SYNTAX INTEGER
{
other (1),
communicationsAlarm (2),
qualityOfServiceAlarm (3),
processingErrorAlarm (4),
equipmentAlarm (5),
environmentalAlarm (6),
integrityViolation (7),
operationalViolation (8),
physicalViolation (9),
securityServiceOrMechanismViolation (10),
timeDomainViolation (11)
}
See http://www.iana.org "
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
SYNTAX INTEGER
{
other (1),
communicationsAlarm (2),
qualityOfServiceAlarm (3),
processingErrorAlarm (4),
equipmentAlarm (5),
environmentalAlarm (6),
integrityViolation (7),
operationalViolation (8),
physicalViolation (9),
securityServiceOrMechanismViolation (10),
timeDomainViolation (11)
}
END
终止
ITU-ALARM-TC-MIB DEFINITIONS ::= BEGIN
ITU-ALARM-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- [RFC2578] TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579]
从SNMPv2 SMI导入模块标识mib-2--[RFC2578]从SNMPv2 TC导入文本约定；--[RFC2579]
ituAlarmTc MODULE-IDENTITY
LAST-UPDATED "200409090000Z" -- September 09, 2004
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
" WG EMail: disman@ietf.org
Subscribe: disman-request@ietf.org
http://www.ietf.org/html.charters/disman-charter.html
ituAlarmTc MODULE-IDENTITY
LAST-UPDATED "200409090000Z" -- September 09, 2004
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
" WG EMail: disman@ietf.org
Subscribe: disman-request@ietf.org
http://www.ietf.org/html.charters/disman-charter.html
Chair: Randy Presuhn randy_presuhn@mindspring.com
主席：兰迪·普雷森·兰迪_presuhn@mindspring.com
Editors: Sharon Chisholm Nortel Networks PO Box 3511 Station C Ottawa, Ont. K1Y 4H7 Canada schishol@nortelnetworks.com
编者：安大略省渥太华市C站3511信箱，莎伦·奇肖姆北电网络公司。K1Y 4H7加拿大schishol@nortelnetworks.com
Dan Romascanu Avaya Atidim Technology Park, Bldg. #3 Tel Aviv, 61131 Israel Tel: +972-3-645-8414 Email: dromasca@avaya.com" DESCRIPTION "This MIB module defines the ITU Alarm textual convention for objects not expected to require regular extension.
Dan Romascanu Avaya Atidim科技园，特拉维夫3号楼，61131以色列电话：+972-3-645-8414电子邮件：dromasca@avaya.com“说明”此MIB模块为不需要定期扩展的对象定义了ITU警报文本约定。
Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3877. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html" REVISION "200409090000Z" -- September 09, 2004 DESCRIPTION "Initial version, published as RFC 3877."
版权所有（C）互联网协会（2004年）。该MIB模块的初始版本发布在RFC 3877中。有关完整的法律通知，请参见RFC本身。补充资料可从以下网址获得：http://www.ietf.org/copyrights/ianamib.html修订版“200409090000Z”-2004年9月9日描述“初始版本，作为RFC 3877出版。”
::= { mib-2 120 }
::= { mib-2 120 }
ItuPerceivedSeverity ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ITU perceived severity values"
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
SYNTAX INTEGER
{
cleared (1),
indeterminate (2),
critical (3),
major (4),
minor (5),
warning (6)
}
ItuPerceivedSeverity ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ITU perceived severity values"
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
SYNTAX INTEGER
{
cleared (1),
indeterminate (2),
critical (3),
major (4),
minor (5),
warning (6)
}
ItuTrendIndication ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ITU trend indication values for alarms."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
SYNTAX INTEGER
{
moreSevere (1),
noChange (2),
lessSevere (3)
}
ItuTrendIndication ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ITU trend indication values for alarms."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
SYNTAX INTEGER
{
moreSevere (1),
noChange (2),
lessSevere (3)
}
END
终止
ITU-ALARM-MIB DEFINITIONS ::= BEGIN
ITU-ALARM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
Gauge32, mib-2
FROM SNMPv2-SMI -- [RFC2578]
AutonomousType, RowPointer
FROM SNMPv2-TC -- [RFC2579]
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
alarmListName, alarmModelIndex,
alarmActiveDateAndTime, alarmActiveIndex
FROM ALARM-MIB -- [RFC3877]
ItuPerceivedSeverity,
ItuTrendIndication
FROM ITU-ALARM-TC-MIB -- [RFC3877]
IANAItuProbableCause,
IANAItuEventType
FROM IANA-ITU-ALARM-TC-MIB -- [RFC3877]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ZeroBasedCounter32
FROM RMON2-MIB; -- [RFC2021]
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
Gauge32, mib-2
FROM SNMPv2-SMI -- [RFC2578]
AutonomousType, RowPointer
FROM SNMPv2-TC -- [RFC2579]
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
alarmListName, alarmModelIndex,
alarmActiveDateAndTime, alarmActiveIndex
FROM ALARM-MIB -- [RFC3877]
ItuPerceivedSeverity,
ItuTrendIndication
FROM ITU-ALARM-TC-MIB -- [RFC3877]
IANAItuProbableCause,
IANAItuEventType
FROM IANA-ITU-ALARM-TC-MIB -- [RFC3877]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ZeroBasedCounter32
FROM RMON2-MIB; -- [RFC2021]
ituAlarmMIB MODULE-IDENTITY
LAST-UPDATED "200409090000Z" -- September 09, 2004
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
"WG EMail: disman@ietf.org
Subscribe: disman-request@ietf.org
http://www.ietf.org/html.charters/disman-charter.html
ituAlarmMIB MODULE-IDENTITY
LAST-UPDATED "200409090000Z" -- September 09, 2004
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
"WG EMail: disman@ietf.org
Subscribe: disman-request@ietf.org
http://www.ietf.org/html.charters/disman-charter.html
Chair: Randy Presuhn randy_presuhn@mindspring.com
主席：兰迪·普雷森·兰迪_presuhn@mindspring.com
Editors: Sharon Chisholm Nortel Networks PO Box 3511 Station C Ottawa, Ont. K1Y 4H7 Canada schishol@nortelnetworks.com
编者：安大略省渥太华市C站3511信箱，莎伦·奇肖姆北电网络公司。K1Y 4H7加拿大schishol@nortelnetworks.com
Dan Romascanu Avaya Atidim Technology Park, Bldg. #3 Tel Aviv, 61131
Dan Romascanu Avaya Atidim科技园，特拉维夫3号楼，61131
Israel Tel: +972-3-645-8414 Email: dromasca@avaya.com" DESCRIPTION "The MIB module describes ITU Alarm information as defined in ITU Recommendation M.3100 [M.3100], X.733 [X.733] and X.736 [X.736].
以色列电话：+972-3-645-8414电子邮件：dromasca@avaya.com“说明”MIB模块描述了ITU建议M.3100[M.3100]、X.733[X.733]和X.736[X.736]中定义的ITU报警信息。
Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3877. For full legal notices see the RFC
itself. Supplementary information may be available on:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "200409090000Z" -- September 09, 2004
DESCRIPTION
"Initial version, published as RFC 3877."
::= { mib-2 121 }
Copyright (C) The Internet Society (2004). The
initial version of this MIB module was published
in RFC 3877. For full legal notices see the RFC
itself. Supplementary information may be available on:
http://www.ietf.org/copyrights/ianamib.html"
REVISION "200409090000Z" -- September 09, 2004
DESCRIPTION
"Initial version, published as RFC 3877."
::= { mib-2 121 }
ituAlarmObjects OBJECT IDENTIFIER ::= { ituAlarmMIB 1 }
ituAlarmObjects OBJECT IDENTIFIER ::= { ituAlarmMIB 1 }
ituAlarmModel OBJECT IDENTIFIER ::= { ituAlarmObjects 1 }
ituAlarmModel OBJECT IDENTIFIER ::= { ituAlarmObjects 1 }
ituAlarmActive OBJECT IDENTIFIER ::= { ituAlarmObjects 2 }
ituAlarmActive OBJECT IDENTIFIER ::= { ituAlarmObjects 2 }
ituAlarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF ItuAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of ITU Alarm information for possible alarms
on the system."
::= { ituAlarmModel 1 }
ituAlarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF ItuAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of ITU Alarm information for possible alarms
on the system."
::= { ituAlarmModel 1 }
ituAlarmEntry OBJECT-TYPE SYNTAX ItuAlarmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entries appear in this table whenever an entry is created in the alarmModelTable with a value of alarmModelState in the range from 1 to 6. Entries disappear from this table whenever the corresponding entries are deleted from the alarmModelTable, including in cases where those entries have been deleted due to local system action. The value of alarmModelSpecificPointer has no effect on the creation or deletion of entries in this table. Values of alarmModelState map to values of ituAlarmPerceivedSeverity as follows:
iTuarmEntry对象类型语法iTuarmEntry MAX-ACCESS不可访问状态当前描述“每当在alarmModelTable中创建alarmModelState值在1到6范围内的条目时，该表中就会出现条目。每当从alarmModelTable中删除相应的条目时，该表中的条目就会消失，包括由于本地系统操作而删除这些条目的情况。alarmModelSpecificPointer的值对创建或删除此表中的条目没有影响。alarmModelState的值映射到iTuarmPercevedSeverity的值，如下所示：
alarmModelState -> ituAlarmPerceivedSeverity
1 -> clear (1)
2 -> indeterminate (2)
3 -> warning (6)
4 -> minor (5)
5 -> major (4)
6 -> critical (3)
alarmModelState -> ituAlarmPerceivedSeverity
1 -> clear (1)
2 -> indeterminate (2)
3 -> warning (6)
4 -> minor (5)
5 -> major (4)
6 -> critical (3)
All other values of alarmModelState MUST NOT appear in this table.
alarmModelState的所有其他值不得出现在此表中。
This table MUST be persistent across system reboots."
INDEX { alarmListName, alarmModelIndex,
ituAlarmPerceivedSeverity }
::= { ituAlarmTable 1 }
This table MUST be persistent across system reboots."
INDEX { alarmListName, alarmModelIndex,
ituAlarmPerceivedSeverity }
::= { ituAlarmTable 1 }
ItuAlarmEntry ::= SEQUENCE {
ituAlarmPerceivedSeverity ItuPerceivedSeverity,
ituAlarmEventType IANAItuEventType,
ituAlarmProbableCause IANAItuProbableCause,
ituAlarmAdditionalText SnmpAdminString,
ituAlarmGenericModel RowPointer }
ItuAlarmEntry ::= SEQUENCE {
ituAlarmPerceivedSeverity ItuPerceivedSeverity,
ituAlarmEventType IANAItuEventType,
ituAlarmProbableCause IANAItuProbableCause,
ituAlarmAdditionalText SnmpAdminString,
ituAlarmGenericModel RowPointer }
ituAlarmPerceivedSeverity OBJECT-TYPE
SYNTAX ItuPerceivedSeverity
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"ITU perceived severity values."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
::= { ituAlarmEntry 1 }
ituAlarmPerceivedSeverity OBJECT-TYPE
SYNTAX ItuPerceivedSeverity
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"ITU perceived severity values."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
::= { ituAlarmEntry 1 }
ituAlarmEventType OBJECT-TYPE SYNTAX IANAItuEventType MAX-ACCESS read-write STATUS current DESCRIPTION "Represents the event type values for the alarms" REFERENCE "ITU Recommendation M.3100, 'Generic Network Information Model', 1995 ITU Recommendation X.733, 'Information Technology - Open Systems Interconnection - System Management: Alarm
iTuarmEventType对象类型语法IANAItuEventType MAX-ACCESS读写状态当前描述”表示警报的事件类型值“参考”ITU建议M.3100，“通用网络信息模型”，1995 ITU建议X.733，“信息技术-开放系统互连-系统管理：警报”
Reporting Function', 1992
ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmEntry 2 }
Reporting Function', 1992
ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmEntry 2 }
ituAlarmProbableCause OBJECT-TYPE
SYNTAX IANAItuProbableCause
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"ITU probable cause values."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992
ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmEntry 3 }
ituAlarmProbableCause OBJECT-TYPE
SYNTAX IANAItuProbableCause
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"ITU probable cause values."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992
ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmEntry 3 }
ituAlarmAdditionalText OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the additional text field for the alarm."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
::= { ituAlarmEntry 4}
ituAlarmAdditionalText OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the additional text field for the alarm."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
::= { ituAlarmEntry 4}
ituAlarmGenericModel OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-write STATUS current DESCRIPTION "This object points to the corresponding row in the alarmModelTable for this alarm severity.
iTuarmGenericModel对象类型语法RowPointer MAX-ACCESS读写状态current DESCRIPTION“此对象指向alarmModelTable中此报警严重性对应的行。
This corresponding entry to alarmModelTable could also be derived by performing the reverse of the mapping from alarmModelState to ituAlarmPerceivedSeverity defined
通过执行从alarmModelState到定义的AlarmPerceivedSeverity的反向映射，也可以导出alarmModelTable的相应条目
in the description of ituAlarmEntry to determine the
appropriate { alarmListName, alarmModelIndex, alarmModelState }
for this { alarmListName, alarmModelIndex,
ituAlarmPerceivedSeverity }."
::= { ituAlarmEntry 5 }
in the description of ituAlarmEntry to determine the
appropriate { alarmListName, alarmModelIndex, alarmModelState }
for this { alarmListName, alarmModelIndex,
ituAlarmPerceivedSeverity }."
::= { ituAlarmEntry 5 }
-- ITU Active Alarm Table --
--ITU主动报警表--
ituAlarmActiveTable OBJECT-TYPE
SYNTAX SEQUENCE OF ItuAlarmActiveEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of ITU information for active alarms entries."
::= { ituAlarmActive 1 }
ituAlarmActiveTable OBJECT-TYPE
SYNTAX SEQUENCE OF ItuAlarmActiveEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of ITU information for active alarms entries."
::= { ituAlarmActive 1 }
ituAlarmActiveEntry OBJECT-TYPE
SYNTAX ItuAlarmActiveEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entries appear in this table when alarms are active. They
are removed when the alarm is no longer occurring."
INDEX { alarmListName, alarmActiveDateAndTime,
alarmActiveIndex }
::= { ituAlarmActiveTable 1 }
ituAlarmActiveEntry OBJECT-TYPE
SYNTAX ItuAlarmActiveEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entries appear in this table when alarms are active. They
are removed when the alarm is no longer occurring."
INDEX { alarmListName, alarmActiveDateAndTime,
alarmActiveIndex }
::= { ituAlarmActiveTable 1 }
ItuAlarmActiveEntry ::= SEQUENCE {
ituAlarmActiveTrendIndication ItuTrendIndication,
ituAlarmActiveDetector AutonomousType,
ituAlarmActiveServiceProvider AutonomousType,
ituAlarmActiveServiceUser AutonomousType
}
ItuAlarmActiveEntry ::= SEQUENCE {
ituAlarmActiveTrendIndication ItuTrendIndication,
ituAlarmActiveDetector AutonomousType,
ituAlarmActiveServiceProvider AutonomousType,
ituAlarmActiveServiceUser AutonomousType
}
ituAlarmActiveTrendIndication OBJECT-TYPE
SYNTAX ItuTrendIndication
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the trend indication values for the alarms."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
::= { ituAlarmActiveEntry 1 }
ituAlarmActiveTrendIndication OBJECT-TYPE
SYNTAX ItuTrendIndication
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the trend indication values for the alarms."
REFERENCE
"ITU Recommendation M.3100, 'Generic Network Information
Model', 1995
ITU Recommendation X.733, 'Information Technology - Open
Systems Interconnection - System Management: Alarm
Reporting Function', 1992"
::= { ituAlarmActiveEntry 1 }
ituAlarmActiveDetector OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the SecurityAlarmDetector object."
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmActiveEntry 2 }
ituAlarmActiveDetector OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the SecurityAlarmDetector object."
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmActiveEntry 2 }
ituAlarmActiveServiceProvider OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the ServiceProvider object."
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmActiveEntry 3 }
ituAlarmActiveServiceProvider OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the ServiceProvider object."
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmActiveEntry 3 }
ituAlarmActiveServiceUser OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the ServiceUser object."
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmActiveEntry 4 }
ituAlarmActiveServiceUser OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the ServiceUser object."
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmActiveEntry 4 }
-- Statistics and Counters
--统计数字及计数器
ituAlarmActiveStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF ItuAlarmActiveStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents the ITU alarm statistics
information."
::= { ituAlarmActive 2 }
ituAlarmActiveStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF ItuAlarmActiveStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents the ITU alarm statistics
information."
::= { ituAlarmActive 2 }
ituAlarmActiveStatsEntry OBJECT-TYPE SYNTAX ItuAlarmActiveStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Statistics on the current active ITU alarms." INDEX { alarmListName }
iTuarmActiveStatEntry对象类型语法iTuarmActiveStatEntry MAX-ACCESS不可访问状态当前描述“当前活动ITU报警的统计信息”。索引{alarmListName}
::= { ituAlarmActiveStatsTable 1 }
::= { ituAlarmActiveStatsTable 1 }
ItuAlarmActiveStatsEntry ::=
SEQUENCE {
ituAlarmActiveStatsIndeterminateCurrent Gauge32,
ituAlarmActiveStatsCriticalCurrent Gauge32,
ituAlarmActiveStatsMajorCurrent Gauge32,
ituAlarmActiveStatsMinorCurrent Gauge32,
ituAlarmActiveStatsWarningCurrent Gauge32,
ituAlarmActiveStatsIndeterminates ZeroBasedCounter32,
ituAlarmActiveStatsCriticals ZeroBasedCounter32,
ituAlarmActiveStatsMajors ZeroBasedCounter32,
ituAlarmActiveStatsMinors ZeroBasedCounter32,
ituAlarmActiveStatsWarnings ZeroBasedCounter32
}
ItuAlarmActiveStatsEntry ::=
SEQUENCE {
ituAlarmActiveStatsIndeterminateCurrent Gauge32,
ituAlarmActiveStatsCriticalCurrent Gauge32,
ituAlarmActiveStatsMajorCurrent Gauge32,
ituAlarmActiveStatsMinorCurrent Gauge32,
ituAlarmActiveStatsWarningCurrent Gauge32,
ituAlarmActiveStatsIndeterminates ZeroBasedCounter32,
ituAlarmActiveStatsCriticals ZeroBasedCounter32,
ituAlarmActiveStatsMajors ZeroBasedCounter32,
ituAlarmActiveStatsMinors ZeroBasedCounter32,
ituAlarmActiveStatsWarnings ZeroBasedCounter32
}
ituAlarmActiveStatsIndeterminateCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the current number of active alarms with a
ituAlarmPerceivedSeverity of indeterminate."
::= { ituAlarmActiveStatsEntry 1 }
ituAlarmActiveStatsIndeterminateCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the current number of active alarms with a
ituAlarmPerceivedSeverity of indeterminate."
::= { ituAlarmActiveStatsEntry 1 }
ituAlarmActiveStatsCriticalCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the current number of active alarms with a
ituAlarmPerceivedSeverity of critical."
::= { ituAlarmActiveStatsEntry 2 }
ituAlarmActiveStatsCriticalCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the current number of active alarms with a
ituAlarmPerceivedSeverity of critical."
::= { ituAlarmActiveStatsEntry 2 }
ituAlarmActiveStatsMajorCurrent OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the current number of active alarms with a
iTuarmActiveStatsMajorCurrent对象类型语法量表32 MAX-ACCESS只读状态当前描述“当前激活报警数量的计数，带有
ituAlarmPerceivedSeverity of major."
::= { ituAlarmActiveStatsEntry 3 }
ituAlarmPerceivedSeverity of major."
::= { ituAlarmActiveStatsEntry 3 }
ituAlarmActiveStatsMinorCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the current number of active alarms with a
ituAlarmPerceivedSeverity of minor."
::= { ituAlarmActiveStatsEntry 4 }
ituAlarmActiveStatsMinorCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the current number of active alarms with a
ituAlarmPerceivedSeverity of minor."
::= { ituAlarmActiveStatsEntry 4 }
ituAlarmActiveStatsWarningCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the current number of active alarms with a
ituAlarmPerceivedSeverity of warning."
::= { ituAlarmActiveStatsEntry 5 }
ituAlarmActiveStatsWarningCurrent OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the current number of active alarms with a
ituAlarmPerceivedSeverity of warning."
::= { ituAlarmActiveStatsEntry 5 }
ituAlarmActiveStatsIndeterminates OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of indeterminate since system
restart."
::= { ituAlarmActiveStatsEntry 6 }
ituAlarmActiveStatsIndeterminates OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of indeterminate since system
restart."
::= { ituAlarmActiveStatsEntry 6 }
ituAlarmActiveStatsCriticals OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of critical since system restart."
::= { ituAlarmActiveStatsEntry 7 }
ituAlarmActiveStatsCriticals OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of critical since system restart."
::= { ituAlarmActiveStatsEntry 7 }
ituAlarmActiveStatsMajors OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of major since system restart."
::= { ituAlarmActiveStatsEntry 8 }
ituAlarmActiveStatsMajors OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of major since system restart."
::= { ituAlarmActiveStatsEntry 8 }
ituAlarmActiveStatsMinors OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of minor since system restart."
::= { ituAlarmActiveStatsEntry 9 }
ituAlarmActiveStatsMinors OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of minor since system restart."
::= { ituAlarmActiveStatsEntry 9 }
ituAlarmActiveStatsWarnings OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of warning since system restart."
::= { ituAlarmActiveStatsEntry 10 }
ituAlarmActiveStatsWarnings OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the total number of active alarms with a
ituAlarmPerceivedSeverity of warning since system restart."
::= { ituAlarmActiveStatsEntry 10 }
-- Conformance
--一致性
ituAlarmConformance OBJECT IDENTIFIER ::= { ituAlarmMIB 2 }
ituAlarmCompliances OBJECT IDENTIFIER ::= { ituAlarmConformance 1 }
ituAlarmConformance OBJECT IDENTIFIER ::= { ituAlarmMIB 2 }
ituAlarmCompliances OBJECT IDENTIFIER ::= { ituAlarmConformance 1 }
ituAlarmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems supporting
the ITU Alarm MIB."
MODULE -- this module
MANDATORY-GROUPS {
ituAlarmGroup
}
GROUP ituAlarmServiceUserGroup
DESCRIPTION
"This group is optional."
GROUP ituAlarmSecurityGroup
DESCRIPTION
"This group is optional."
GROUP ituAlarmStatisticsGroup
DESCRIPTION
"This group is optional."
::= { ituAlarmCompliances 1 }
ituAlarmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems supporting
the ITU Alarm MIB."
MODULE -- this module
MANDATORY-GROUPS {
ituAlarmGroup
}
GROUP ituAlarmServiceUserGroup
DESCRIPTION
"This group is optional."
GROUP ituAlarmSecurityGroup
DESCRIPTION
"This group is optional."
GROUP ituAlarmStatisticsGroup
DESCRIPTION
"This group is optional."
::= { ituAlarmCompliances 1 }
ituAlarmGroups OBJECT IDENTIFIER ::= { ituAlarmConformance 2 }
ituAlarmGroups OBJECT IDENTIFIER ::= { ituAlarmConformance 2 }
ituAlarmGroup OBJECT-GROUP OBJECTS { ituAlarmEventType,
iTuarmGroup对象组对象{iTuarmEventType，
ituAlarmProbableCause,
ituAlarmGenericModel
}
STATUS current
DESCRIPTION
"ITU alarm details list group."
::= { ituAlarmGroups 1}
ituAlarmProbableCause,
ituAlarmGenericModel
}
STATUS current
DESCRIPTION
"ITU alarm details list group."
::= { ituAlarmGroups 1}
ituAlarmServiceUserGroup OBJECT-GROUP
OBJECTS {
ituAlarmAdditionalText,
ituAlarmActiveTrendIndication
}
STATUS current
DESCRIPTION
"The use of these parameters is a service-user option."
::= { ituAlarmGroups 2 }
ituAlarmServiceUserGroup OBJECT-GROUP
OBJECTS {
ituAlarmAdditionalText,
ituAlarmActiveTrendIndication
}
STATUS current
DESCRIPTION
"The use of these parameters is a service-user option."
::= { ituAlarmGroups 2 }
ituAlarmSecurityGroup OBJECT-GROUP
OBJECTS {
ituAlarmActiveDetector,
ituAlarmActiveServiceProvider,
ituAlarmActiveServiceUser
}
STATUS current
DESCRIPTION
"Security Alarm Reporting Function"
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmGroups 3 }
ituAlarmSecurityGroup OBJECT-GROUP
OBJECTS {
ituAlarmActiveDetector,
ituAlarmActiveServiceProvider,
ituAlarmActiveServiceUser
}
STATUS current
DESCRIPTION
"Security Alarm Reporting Function"
REFERENCE
"ITU Recommendation X.736, 'Information Technology - Open
Systems Interconnection - System Management: Security
Alarm Reporting Function', 1992"
::= { ituAlarmGroups 3 }
ituAlarmStatisticsGroup OBJECT-GROUP
OBJECTS {
ituAlarmActiveStatsIndeterminateCurrent,
ituAlarmActiveStatsCriticalCurrent,
ituAlarmActiveStatsMajorCurrent,
ituAlarmActiveStatsMinorCurrent,
ituAlarmActiveStatsWarningCurrent,
ituAlarmActiveStatsIndeterminates,
ituAlarmActiveStatsCriticals,
ituAlarmActiveStatsMajors,
ituAlarmActiveStatsMinors,
ituAlarmActiveStatsWarnings
}
STATUS current
DESCRIPTION
ituAlarmStatisticsGroup OBJECT-GROUP
OBJECTS {
ituAlarmActiveStatsIndeterminateCurrent,
ituAlarmActiveStatsCriticalCurrent,
ituAlarmActiveStatsMajorCurrent,
ituAlarmActiveStatsMinorCurrent,
ituAlarmActiveStatsWarningCurrent,
ituAlarmActiveStatsIndeterminates,
ituAlarmActiveStatsCriticals,
ituAlarmActiveStatsMajors,
ituAlarmActiveStatsMinors,
ituAlarmActiveStatsWarnings
}
STATUS current
DESCRIPTION
"ITU Active Alarm Statistics."
::= { ituAlarmGroups 4 }
"ITU Active Alarm Statistics."
::= { ituAlarmGroups 4 }
END
终止
This example demonstrates an interface-based alarm that goes into a state of "warning" when a linkDown Notification [RFC2863] occurs but the ifAdminStatus indicates the interface was taken down administratively. If IfAdminStatus is "up" when the linkDown Notification occurs, then there is a problem, so the state of the alarm is critical. A linkUp alarm clears the alarm.
此示例演示了一个基于接口的警报，当发生链接关闭通知[RFC2863]但ifAdminStatus指示该接口已被管理性关闭时，该警报将进入“警告”状态。如果在发生链接断开通知时IfAdminStatus为“up”，则存在问题，因此报警状态为关键状态。连接警报清除警报。
linkDown NOTIFICATION-TYPE
OBJECTS { ifIndex, ifAdminStatus, ifOperStatus }
STATUS current
DESCRIPTION
""
::= { snmpTraps 3 }
linkDown NOTIFICATION-TYPE
OBJECTS { ifIndex, ifAdminStatus, ifOperStatus }
STATUS current
DESCRIPTION
""
::= { snmpTraps 3 }
linkUp NOTIFICATION-TYPE
OBJECTS { ifIndex, ifAdminStatus, ifOperStatus }
STATUS current
DESCRIPTION
""
::= { snmpTraps 4 }
linkUp NOTIFICATION-TYPE
OBJECTS { ifIndex, ifAdminStatus, ifOperStatus }
STATUS current
DESCRIPTION
""
::= { snmpTraps 4 }
alarmModelIndex 3 alarmModelState 1 alarmModelNotificationId linkUp alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription "linkUp" alarmModelSpecificPointer ituAlarmEntry.3.1 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType communicationsAlarm (2) ituAlarmPerceivedSeverity cleared (1) ituAlarmGenericModel alarmModelEntry.3.1
alarmModelIndex 3 alarmModelState 1 alarmModelNotificationId linkUp alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription“linkUp”alarmModelSpecificPointer iTuarmEntry.3.1 alarmModelVarbindSubtree ifIndex（1.3.6.1.2.2.1.1）alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）iTuarmEventType Communications警报（2）iTuarmPerceivedSeverity已清除（1）iTuarmGenericModel alarmModelEntry.3.1
alarmModelIndex 3 alarmModelState 2 alarmModelNotificationId linkDown alarmModelVarbindIndex 2
alarmModelIndex 3 alarmModelState 2 alarmModelNotificationId链接下alarmModelVarbindIndex 2
alarmModelVarbindValue down (2) alarmModelDescription "linkDown administratively" alarmModelSpecificPointer ituAlarmEntry.3.6 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType communicationsAlarm (2) ituAlarmPerceivedSeverity warning (6) ituAlarmGenericModel alarmModelEntry.3.2
alarmModelVarbindValue down（2）alarmModelDescription“linkDown Administrative”AlarmModelSpecificationPointer iTuarmEntry.3.6 alarmModelVarbindSubtree ifIndex（1.3.6.1.2.2.1.1）alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）iTuarmEventType communicationsAlarm（2）iTuarmPerceived严重性警告（6）iTuarmGenericModel alarmModelEntry.3.2
alarmModelIndex 3 alarmModelState 3 alarmModelNotificationId linkDown alarmModelVarbindIndex 2 alarmModelVarbindValue up (1) alarmModelDescription "linkDown - confirmed problem" alarmModelSpecificPointer ituAlarmEntry.3.3 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType communicationsAlarm (2) ituAlarmPerceivedSeverity critical (3) ituAlarmGenericModel alarmModelEntry.3.3
alarmModelIndex 3 alarmModelState 3 alarmModelNotificationId linkDown alarmModelVarbindIndex 2 alarmModelVarbindValue up（1）alarmModelDescription“linkDown-confirmed problem”AlarmModelSpecification ituAlarmEntry.3.3 alarmModelVarbindSubtree ifIndex（1.3.6.1.2.2.1.1）alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）iTuarmEventType通信警报（2）iTuarmPercevedSeverity critical（3）iTuarmGenericModel alarmModelEntry.3.3
alarmActiveIndex 1 alarmActiveDateAndTime 2342464573 alarmActiveDateAndTime DateAndTime, alarmActiveEngineID SnmpEngineID, alarmActiveEngineAddressType ipV4 alarmActiveEngineAddress 10.10.10.10 alarmActiveContextName SnmpAdminString, alarmActiveVariables 3 alarmActiveNotificationID 1.3.6.1.6.3.1.1.5.3 alarmActiveResourceId 1.3.6.1.2.1.2.2.1.1.346 alarmActiveLogPointer 0.0 alarmActiveModelPointer alarmModelEntry.3.3 alarmActiveSpecificPointer ituAlarmActiveEntry.1.3 ituAlarmActiveTrendIndication moreSevere (1) ituAlarmDetector 0.0 ituAlarmServiceProvider 0.0 ituAlarmServiceUser 0.0
alarmActiveIndex 1 AlarmActiveDate and Time 2342464573 AlarmActiveDate and Time Date and Time，alarmActiveEngineID SnmpEngineID，alarmActiveEngineAddressType ipV4 alarmActiveEngineAddress 10.10.10 alarmActiveContextName snmpAdministring，alarmActiveVariables 3 alarmActiveNotificationID 1.3.6.1.6.3.1.1.5.3 alarmActiveResourceId 1.3.6.1.2.2.1.1.346 alarmActiveLogPointer 0.0 alarmActiveModelPointer alarmModelEntry.3 AlarmActiveSpecification Pointer iTAlarmActiveEntry.1.3 iTAlarmActiveTrend指示更严重（1）ituAlarmDetector 0.0 ituAlarmServiceProvider 0.0 ituAlarmServiceUser 0.0
alarmActiveVariableIndex 1 alarmActiveVariableID sysUpTime.0 alarmActiveVariableValueType timeTicks(3) alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 46754
alarmActiveVariableIndex 1 alarmActiveVariableID系统正常运行时间。0 alarmActiveVariableValueType时间刻度（3）alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 46754
alarmActiveVariableInteger32Val 0 alarmActiveVariableOctetStringVal "" alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 0.0 alarmActiveVariableCounter64Val 0 alarmActiveVariableIndex 2 alarmActiveVariableID snmpTrapOID.0 alarmActiveVariableValueType objectId(7) alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 0 alarmActiveVariableInteger32Val 0 alarmActiveVariableOctetStringVal "" alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 1.3.6.1.6.3.1.1.5.3 alarmActiveVariableCounter64Val 0 alarmActiveVariableIndex 3 alarmActiveVariableID ifIndex alarmActiveVariableValueType integer32(4) alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 0 alarmActiveVariableInteger32Val 346 alarmActiveVariableOctetStringVal "" alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 0.0 alarmActiveVariableCounter64Val 0 alarmActiveVariableIndex 4 alarmActiveVariableID ifAdminStatus alarmActiveVariableValueType integer32(4) alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 0 alarmActiveVariableInteger32Val up (1) alarmActiveVariableOctetStringVal "" alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 0.0 alarmActiveVariableCounter64Val 0 alarmActiveVariableIndex 5 alarmActiveVariableID ifOperStatus alarmActiveVariableValueType integer32(4) alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 0 alarmActiveVariableInteger32Val down(2) alarmActiveVariableOctetStringVal "" alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 0.0
alarmActiveVariableInteger32Val 0 alarmActiveVariableOctetStringVal“”alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 0.0 alarmActiveVariableCounter64Val 0 alarmActiveVariableIndex 2 alarmActiveVariableID snmpTrapOID.0 alarmActiveVariableValueType objectId（7）alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 0 alarmActiveVariableInteger32Val 0 alarmActiveVariableOctetStringVal“”alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 1.3.6.6.3.1.1.5.3 alarmActiveVariableCounter64Val 0 alarmActiveVariableIndex 3 alarmActiveVariableID ifIndex alarmActiveVariableValueType整数32（4）alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 0 alarmActiveVariableInteger32Val 346 alarmActiveVariableOctetStringVal“”alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 0.0 alarmActiveVariableCounter64Val 0 alarmActiveVariableIndex 4 alarmActiveVariableID ifAdminStatus alarmActiveVariableValueType integer32（4）alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 0 alarmActiveVariableInteger32Val up（1）alarmActiveVariableOctetStringVal“”alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 0.0 alarmActiveVariableCounter64Val 0 alarmActiveVariableIndex 5 alarmActiveVariableID IfOperatStatus alarmActiveVariableValueType整数32（4）alarmActiveVariableCounter32Val 0 alarmActiveVariableUnsigned32Val 0 alarmActiveVariableTimeTicksVal 0 alarmActiveVariableInteger32Val向下（2）alarmActiveVariableOctetStringVal“”alarmActiveVariableIpAddressVal 0 alarmActiveVariableOidVal 0.0
alarmActiveVariableCounter64Val 0 alarmActiveVariableOpaqueVal
alarmActiveVariableCounter64Val 0 alarmActiveVariableOpaqueVal
Consider a system able to detect four different temperature states for a widget - normal, minor, major, critical. The system does not have any Notification definitions for these alarm states. A temperature alarm can be modelled using the generic alarm Notifications of alarmClearState and alarmActive.
考虑一个系统能够检测四个不同的温度状态的小部件-正常的，次要的，主要的，关键的。系统没有这些报警状态的任何通知定义。可以使用alarmClearState和alarmActive的通用报警通知对温度报警进行建模。
alarmModelIndex 5 alarmModelState 1 alarmModelNotificationId alarmClearState alarmModelVarbindIndex 2 alarmModelVarbindValue cleared (1) alarmModelDescription "Acme Widget Temperature Normal" alarmModelSpecificPointer ituAlarmEntry.5.1 alarmModelVarbindSubtree alarmActiveResourceId alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType environmentalAlarm (6) ituPerceivedSeverity cleared (1) ituAlarmGenericModel alarmModelEntry.5.1
alarmModelIndex 5 alarmModelState 1 alarmModelNotificationId alarmClearState alarmModelVarbindIndex 2 alarmModelVarbindValue cleared（1）alarmModelDescription“Acme Widget Temperature Normal”alarmModelSpecificPointer iTuarmEntry.5.1 alarmModelVarbindSubtree alarmActiveResourceId alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）ituAlarmEventType环境警报（6）iTuPercevedSeverity cleared（1）ituAlarmGenericModel alarmModelEntry.5.1
alarmModelIndex 5 alarmModelState 2 alarmModelNotificationId alarmActiveState alarmModelVarbindIndex 2 alarmModelVarbindValue minor (5) alarmModelDescription "Acme Widget Temperature Minor" alarmModelSpecificPointer ituAlarmEntry.5.5 alarmModelVarbindSubtree alarmActiveResourceId alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventState environmentalAlarm (6) ituPerceivedSeverity minor (5) ituAlarmGenericModel alarmModelEntry.5.2
alarmModelIndex 5 alarmModelState 2 alarmModelNotificationId alarmActiveState alarmModelVarbindIndex 2 alarmModelVarbindValue次要（5）alarmModelDescription“Acme Widget Temperature次要”alarmModelSpecificPointer iTuarmEntry.5 alarmModelVarbindSubtree alarmActiveResourceId alarmModelResourcePrefix 0.0 alarmModelRowStatus活动（1）ituAlarmEventState环境警报（6）iTuPercevedSeverity次要（5）ituAlarmGenericModel alarmModelEntry.5.2
alarmModelIndex 5 alarmModelState 3 alarmModelNotificationId alarmActiveState alarmModelVarbindIndex 2 alarmModelVarbindValue major (4) alarmModelDescription "Acme Widget Temperature Major" alarmModelSpecificPointer ituAlarmEntry.5.4 alarmModelVarbindSubtree alarmActiveResourceId alarmModelResourcePrefix 0.0
alarmModelIndex 5 alarmModelState 3 alarmModelNotificationId alarmActiveState alarmModelVarbindIndex 2 alarmModelVarbindValue major（4）alarmModelDescription“Acme Widget Temperature major”alarmModelSpecificPointer iTuarmEntry.5.4 alarmModelVarbindSubtree alarmActiveResourceId alarmModelResourcePrefix 0.0
alarmModelRowStatus active (1) ituAlarmEventType environmentalAlarm (6) ituPerceivedSeverity major (4) ituAlarmGenericModel alarmModelEntry.5.3 alarmModelIndex 5 alarmModelState 4 alarmModelNotificationId alarmActiveState alarmModelVarbindIndex 2 alarmModelVarbindValue critical (3) alarmModelDescription "Acme Widget Temperature Critical" alarmModelSpecificPointer ituAlarmEntry.5.3 alarmModelVarbindSubtree alarmActiveResourceId alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType environmentalAlarm (6) ituPerceivedSeverity critical (3) ituAlarmGenericModel alarmModelEntry.5.4
alarmModelRowStatus active（1）iTuarmEventType Environment Alarm（6）iTunesPercevedSeverity major（4）iTuarmGenericModel alarmModelEntry.5.3 alarmModelIndex 5 alarmModelState 4 alarmModelNotificationId alarmActiveState alarmModelVarbindIndex 2 alarmModelVarbindValue critical（3）alarmModelDescription“Acme Widget Temperature critical”alarmModelSpecificPointer iTuarmEntry.5.3 alarmModelVarbindSubtree alarmActiveResourceId alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）iTuarmEventType Environment警报（6）iTuarmPercevedSeverity critical（3）iTuarmGenericModel alarmModelEntry.5.4
Consider a system able to detect four different temperature states for a widget - normal, minor, major, critical. The system does not have any Notification definitions for these alarm states. A temperature alarm can be modelled without specifying any Notifications in the alarm model. When a temperature state other than normal is detected, an instance of this alarm would be added to the active alarm table, but no Notifications would be sent out.
考虑一个系统能够检测四个不同的温度状态的小部件-正常的，次要的，主要的，关键的。系统没有这些报警状态的任何通知定义。可以对温度警报进行建模，而无需在警报模型中指定任何通知。当检测到非正常的温度状态时，此报警的实例将添加到活动报警表中，但不会发送任何通知。
This could alternatively be accomplished using the models from example 6.2 and by not specifying any target managers in the SNMP-TARGET-MIB, which would allow the alarm state Notifications to be logged in the Notification Log while still preventing Notifications from being transmitted on the wire.
或者，也可以使用示例6.2中的模型，通过在SNMP-target-MIB中不指定任何目标管理器来实现，这将允许在通知日志中记录报警状态通知，同时仍然防止在线路上传输通知。
alarmModelIndex 6 alarmModelState 1 alarmModelNotificationId 0.0 alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription "Widget Temperature" alarmModelSpecificPointer ituAlarmEntry.6.1 alarmModelVarbindSubtree 0.0 alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType environmentalAlarm (6) ituPerceivedSeverity cleared (1) ituAlarmGenericModel alarmModelEntry.6.1
alarmModelIndex 6 alarmModelState 1 alarmModelNotificationId 0.0 alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription“Widget Temperature”alarmModelSpecificPointer iTAlarmEntry.6.1 alarmModelVarbindSubtree 0.0 alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）iTAlarmEventType EnvironmentAlarm（6）iTunesPerceivedSeverity已清除（1）iTuarmGenericModel alarmModelEntry.6.1
alarmModelIndex 6 alarmModelState 2 alarmModelNotificationId 0.0 alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription "Widget Temperature" alarmModelSpecificPointer ituAlarmEntry.6.5 alarmModelVarbindSubtree 0.0 alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventState environmentalAlarm (6) ituAlarmPerceivedSeverity minor (5) ituAlarmGenericModel alarmModelEntry.6.2
alarmModelIndex 6 alarmModelState 2 alarmModelNotificationId 0.0 alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription“Widget Temperature”alarmModelSpecificPointer iTAlarmEntry.6.5 alarmModelVarbindSubtree 0.0 alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）iTAlarmEventState环境警报（6）iTuarmPerceivedSeverity minor（5）iTuarmGenericModel alarmModelEntry.6.2
alarmModelIndex 6 alarmModelState 3 alarmModelNotificationId 0.0 alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription "Widget Temperature" alarmModelSpecificPointer ituAlarmEntry.6.4 alarmModelVarbindSubtree 0.0 alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType environmentalAlarm (6) ituPerceivedSeverity major (4) ituAlarmGenericModel alarmModelEntry.6.3
alarmModelIndex 6 alarmModelState 3 alarmModelNotificationId 0.0 alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription“Widget Temperature”alarmModelSpecificPointer iTAlarmEntry.6.4 alarmModelVarbindSubtree 0.0 alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）iTAlarmEventType Environment警报（6）iTunesPerceivedSeverity主要（4）iTuarmGenericModel alarmModelEntry.6.3
alarmModelIndex 6 alarmModelState 4 alarmModelNotificationId 0.0 alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription "Widget Temperature Severe" alarmModelSpecificPointer ituAlarmEntry.6.3 alarmModelVarbindSubtree 0.0 alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1) ituAlarmEventType environmentalAlarm (6) ituPerceivedSeverity critical (3) ituAlarmGenericModel alarmModelEntry.6.4
alarmModelIndex 6 alarmModelState 4 alarmModelNotificationId 0.0 alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription“小部件温度严重”alarmModelSpecificPointer iTAlarmEntry.6.3 alarmModelVarbindSubtree 0.0 alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）iTAlarmEventType Environment Alarm（6）iTunesPerceivedSeverity critical（3）iTuarmGenericModel alarmModelEntry.6.4
Consider the following Notifications defined in the printer MIB [RFC3805]:
考虑打印机MIB中定义的以下通知[RCF3805]：
prtAlertSeverityLevel OBJECT-TYPE
-- This value is a type 1 enumeration
SYNTAX INTEGER {
other(1),
critical(3),
warning(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The level of severity of this alert table entry. The printer
determines the severity level assigned to each entry into the
table."
::= { prtAlertEntry 2 }
prtAlertSeverityLevel OBJECT-TYPE
-- This value is a type 1 enumeration
SYNTAX INTEGER {
other(1),
critical(3),
warning(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The level of severity of this alert table entry. The printer
determines the severity level assigned to each entry into the
table."
::= { prtAlertEntry 2 }
printerV2Alert NOTIFICATION-TYPE
OBJECTS { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup,
prtAlertGroupIndex, prtAlertLocation, prtAlertCode }
STATUS current
DESCRIPTION
"This trap is sent whenever a critical event is added to the
prtAlertTable."
::= { printerV2AlertPrefix 1 }
printerV2Alert NOTIFICATION-TYPE
OBJECTS { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup,
prtAlertGroupIndex, prtAlertLocation, prtAlertCode }
STATUS current
DESCRIPTION
"This trap is sent whenever a critical event is added to the
prtAlertTable."
::= { printerV2AlertPrefix 1 }
These Notifications can be used to model a printer alarm as follows:
这些通知可用于模拟打印机警报，如下所示：
alarmModelIndex 9 alarmModelState 1 alarmModelNotificationId alarmClearState alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription "Printer Alarm" alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree prtAlertGroup alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1)
alarmModelIndex 9 alarmModelState 1 alarmModelNotificationId alarmClearState alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription“打印机报警”alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree prtAlertGroup alarmModelResourcePrefix 0.0 alarmModelRowStatus活动（1）
alarmModelIndex 9 alarmModelState 2 alarmModelNotificationId printerV2Alert alarmModelVarbindIndex 2 alarmModelVarbindValue warning (4) alarmModelDescription "Printer Alarm" alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree prtAlertGroup alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1)
alarmModelIndex 9 alarmModelState 2 alarmModelNotificationId printerV2Alert alarmModelVarbindIndex 2 alarmModelVarbindValue警告（4）alarmModelDescription“打印机报警”alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree prtAlertGroup alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）
alarmModelIndex 9 alarmModelState 3
alarmModelIndex 9 alarmModelState 3
alarmModelNotificationId printerV2Alert alarmModelVarbindIndex 2 alarmModelVarbindValue other (1) alarmModelDescription "Printer Alarm - unknown severity" alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree prtAlertGroup alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1)
alarmModelNotificationId printerV2Alert alarmModelVarbindIndex 2 alarmModelVarbindValue其他（1）alarmModelDescription“打印机报警-未知严重性”alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree prtAlertGroup alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）
alarmModelIndex 9 alarmModelState 4 alarmModelNotificationId printerV2Alert alarmModelVarbindIndex 2 alarmModelVarbindValue critical (3) alarmModelDescription "Printer Alarm" alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree prtAlertGroup alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1)
alarmModelIndex 9 alarmModelState 4 alarmModelNotificationId printerV2Alert alarmModelVarbindIndex 2 alarmModelVarbindValue critical（3）alarmModelDescription“打印机报警”alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree prtAlertGroup alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）
The RMON MIB [RFC2819] defines a mechanism for generating threshold alarms. When the thresholds are crossed, RisingAlarm and FallingAlarm Notifications are generated as appropriate. These Notifications can be used to model an upper threshold alarm as follows:
RMON MIB[RFC2819]定义了生成阈值报警的机制。当超过阈值时，将酌情生成RisingAlarm和FallingAlarm通知。这些通知可用于对上限报警建模，如下所示：
alarmModelIndex 6 alarmModelState 1 alarmModelNotificationId FallingAlarm alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription "RMON Rising Clear Alarm" alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree alarmIndex alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1)
alarmModelIndex 6 alarmModelState 1 alarmModelNotificationId FallingAlarmModelVarBindIndex 0 alarmModelVarbindValue 0 alarmModelDescription“RMON上升清除报警”alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）
alarmModelIndex 6 alarmModelState 2 alarmModelNotificationId RisingAlarm alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription "RMON Rising Alarm" alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree alarmIndex alarmModelResourcePrefix 0.0 alarmModelRowStatus active (1)
alarmModelIndex 6 alarmModelState 2 alarmModelNotificationId RisingAlarm alarmModelVarbindIndex 0 alarmModelVarbindValue 0 alarmModelDescription“RMON上升警报”alarmModelSpecificPointer 0.0 alarmModelVarbindSubtree AlarmModel警报索引alarmModelResourcePrefix 0.0 alarmModelRowStatus active（1）
The following example demonstrates the relationship between the active alarm table, the clear alarm table and the Notification Log MIB.
以下示例演示了活动报警表、清除报警表和通知日志MIB之间的关系。
Consider a system with alarms modelled as in example 1 and which also supports the informational Notification dsx3LineStatusChange.
考虑具有如实例1中所述的警报的系统，该系统还支持信息通知DSX3LIN StestUschange。
dsx3LineStatusChange NOTIFICATION-TYPE
OBJECTS { dsx3LineStatus,
dsx3LineStatusLastChange }
STATUS current
DESCRIPTION
"A dsx3LineStatusChange trap is sent when the
value of an instance of dsx3LineStatus changes. It
can be utilized by an NMS to trigger polls. When
the line status change results in a lower level
line status change (i.e., ds1), then no traps for
the lower level are sent."
::= { ds3Traps 0 1 }
dsx3LineStatusChange NOTIFICATION-TYPE
OBJECTS { dsx3LineStatus,
dsx3LineStatusLastChange }
STATUS current
DESCRIPTION
"A dsx3LineStatusChange trap is sent when the
value of an instance of dsx3LineStatus changes. It
can be utilized by an NMS to trigger polls. When
the line status change results in a lower level
line status change (i.e., ds1), then no traps for
the lower level are sent."
::= { ds3Traps 0 1 }
0. At system start, the active alarm table, alarm clear table and the Notification Log are all empty. ___________________________ _______________________ | alarmActiveTable | | nlmLogTable | |---------------------------| |-----------------------| | alarmActiveIndex | alarm | | nlmLogPointer | notif.| |---------------------------| |-----------------------| |___________________________| |_______________________|
0. 系统启动时，活动报警表、报警清除表和通知日志均为空alarmActiveTable | | nlmLogTable | | | | | | | | nlmLogTable | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ||_______________________|
__________________________________________________
| alarmClearTable |
|--------------------------------------------------|
| alarmClear Index | alarm |
|--------------------------------------------------|
| | |
|__________________________________________________|
__________________________________________________
| alarmClearTable |
|--------------------------------------------------|
| alarmClear Index | alarm |
|--------------------------------------------------|
| | |
|__________________________________________________|
1. Some time later, a link goes down generating a linkDown Notification, which is sent out and logged in the Notification Log. As this Notification is modelled as an alarm state, an entry is added to the active alarm table. __________________________________________________ | alarmActiveTable | |--------------------------------------------------| | alarmActiveIndex | alarm | |--------------------------------------------------| | 1 | link down - problem confirmed | |__________________________________________________|
1. 一段时间后，一个链接关闭，生成一个linkDown通知，该通知被发送并记录在通知日志中。由于此通知被建模为报警状态，将向活动报警表中添加一个条目alarmActiveTable | |---------------------------------------alarmActiveIndex | alarm | |----------------------------------------------------------------链接-问题已确认|__________________________________________________|
_______________________________________________
| nlmLogTable |
|-----------------------------------------------|
| nlmLogPointer | Notification |
|-----------------------------------------------|
| 1 | linkdown |
|_______________________________________________|
_______________________________________________
| nlmLogTable |
|-----------------------------------------------|
| nlmLogPointer | Notification |
|-----------------------------------------------|
| 1 | linkdown |
|_______________________________________________|
__________________________________________________
| alarmClearTable |
|--------------------------------------------------|
| alarmClear Index | alarm |
|--------------------------------------------------|
| | |
|__________________________________________________|
__________________________________________________
| alarmClearTable |
|--------------------------------------------------|
| alarmClear Index | alarm |
|--------------------------------------------------|
| | |
|__________________________________________________|
2. Some time later, the value of an instance of dsx3LineStatus changes. This Notification is sent out and logged. As this is not modelled into an alarm state, the active alarm table remains unchanged. __________________________________________________ | alarmActiveTable | |--------------------------------------------------| | alarmActiveIndex | alarm | |--------------------------------------------------| | 1 | linkDown - problem confirmed | |__________________________________________________|
2. 一段时间后，dsx3LineStatus实例的值会更改。此通知将被发送并记录。由于未将其建模为报警状态，活动报警表保持不变alarmActiveTable | |---------------------------------------alarmActiveIndex | alarm | |----------------------------------------------------------------1 |链接-问题已确认|__________________________________________________|
_____________________________________________
| nlmLogTable |
|---------------------------------------------|
| nlmLogPointer | Notification |
|---------------------------------------------|
| 1 | linkDown |
| 2 | dsx3LineStatusChange |
|_____________________________________________|
_____________________________________________
| nlmLogTable |
|---------------------------------------------|
| nlmLogPointer | Notification |
|---------------------------------------------|
| 1 | linkDown |
| 2 | dsx3LineStatusChange |
|_____________________________________________|
__________________________________________________
| alarmClearTable |
|--------------------------------------------------|
| alarmClear Index | alarm |
|--------------------------------------------------|
| | |
|__________________________________________________|
__________________________________________________
| alarmClearTable |
|--------------------------------------------------|
| alarmClear Index | alarm |
|--------------------------------------------------|
| | |
|__________________________________________________|
3. Some time later, the link goes back up. A linkUp Notification is sent out and logged. As this Notification models the clear alarm for this alarm, the alarm entry is remove from the active alarm table. An entry is added to the clear alarm table. __________________________________________________ | alarmActiveTable | |--------------------------------------------------| | alarmActiveIndex | alarm | |--------------------------------------------------| |__________________________________________________|
3. 一段时间后，链接又恢复了。将发送并记录链接通知。由于此通知为该报警的清除报警建模，因此将从活动报警表中删除报警条目。一个条目被添加到清除报警表中。uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu|alarmActiveTable | |----------------------------------------------------------------| | alarmActiveIndex | alarm |----------------------------------------------------------------||__________________________________________________|
_____________________________________________
| nlmLogTable |
|---------------------------------------------|
| nlmLogPointer | Notification |
|---------------------------------------------|
| 1 | linkDown |
| 2 | dsx3LineStatusChange |
| 3 | linkUp |
|_____________________________________________|
_____________________________________________
| nlmLogTable |
|---------------------------------------------|
| nlmLogPointer | Notification |
|---------------------------------------------|
| 1 | linkDown |
| 2 | dsx3LineStatusChange |
| 3 | linkUp |
|_____________________________________________|
__________________________________________________
| alarmClearTable |
|--------------------------------------------------|
| alarmClear Index | alarm |
|--------------------------------------------------|
| 1 | linkDown - confirmed problem |
|__________________________________________________|
__________________________________________________
| alarmClearTable |
|--------------------------------------------------|
| alarmClear Index | alarm |
|--------------------------------------------------|
| 1 | linkDown - confirmed problem |
|__________________________________________________|
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。
The following objects are defined with a MAX-ACCESS clause of read-write or read-create: alarmModelNotificationId, alarmModelVarbindIndex, alarmModelVarbindValue, alarmModelDescription, alarmModelSpecificPointer, alarmModelVarbindSubtree, alarmModelResourcePrefix, alarmModelRowStatus, alarmClearMaximum, ituAlarmEventType, ituAlarmProbableCause, ituAlarmAdditionalText, and ituAlarmGenericModel.
以下对象是使用读写或读创建的MAX-ACCESS子句定义的：alarmModelNotificationId、alarmModelVarbindIndex、alarmModelVarbindValue、alarmModelDescription、alarmModelSpecificPointer、alarmModelVarbindSubtree、alarmModelResourcePrefix、alarmModelRowStatus、alarmClearMaximum、iTAlarmEventType、iTAlarmProbableCause、，iTuarmAdditionalText和iTuarmGenericModel。
Note that setting the value of alarmClearMaximum too low may result in security related alarms history being prematurely lost.
请注意，将alarmClearMaximum的值设置得过低可能会导致与安全相关的报警历史过早丢失。
Changing values of alarmModelRowStatus as part of creating and deleting rows in the alarmModelTable result in adding new alarm models to the system or taking them out respectively. These operations need to be carefully planned. Adding a new model should be made in a consistent manner to avoid the system overflow with alarms. Taking out a model should result in the deletion of all this model's related alarms in the system.
在alarmModelTable中创建和删除行时更改alarmModelRowStatus的值会导致向系统中添加新的报警模型或分别将其取出。这些行动需要仔细规划。应以一致的方式添加新模型，以避免系统溢出警报。取出模型应导致删除系统中所有该模型的相关报警。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
Note that the alarm throttling mechanism associated with the alarmActiveState and alarmActiveClear notifications only applies to a given alarm. Defining multiple alarms from the same internal stimulus may then still result in a flood of alarms into the network.
请注意，与alarmActiveState和alarmActiveClear通知关联的报警节流机制仅适用于给定的报警。从同一个内部刺激定义多个警报可能仍然会导致大量警报涌入网络。
Although the use of community strings in SNMPv1 is not considered an effective means of providing security, security administrators SHOULD consider whether the fact that alarmActiveContextName can reveal community string values would make this object sensitive in their environment.
虽然SNMPv1中的社区字符串的使用不被认为是提供安全的有效手段，但安全管理员应该考虑ALARMcActudieTrimeNoNT是否可以显示社区字符串值这一事实会使该对象在其环境中敏感。
This MIB module can provide access to information that may also be accessed through manipulation of the SNMP-NOTIFICATION-MIB and the NOTIFICATION-LOG-MIB. This is expressed in part through the common indexing structure of nlmLogName [RFC3014], snmpNotifyFilterProfileName [RFC3413], and alarmListName. Consequently, it is RECOMMENDED that security administrators take care to configure a coherent VACM security policy. The objects
此MIB模块可以提供对信息的访问，这些信息也可以通过操纵SNMP-NOTITITIONG-MIB和NOTINOTIONG-LOG-MIB来访问。这部分是通过nlmLogName[RFC3014]、snmpNotifyFilterProfileName[RFC3413]和alarmListName的公共索引结构表示的。因此，建议安全管理员注意配置一致的VACM安全策略。物体
alarmActiveLogPointer, alarmActiveModelPointer, alarmActiveSpecificPointer, and alarmClearModelPointer are object identifiers that reference information to which a particular user might not be given direct access. The structure of these object identifiers does not permit the extraction of any sensitive information. Two other objects, alarmClearResourceId, and alarmActiveResourceId, are also syntactically object identifiers, but their structure could provide a user with potentially useful information to which he or she might not otherwise be granted access, such as the existence of a particular resource.
alarmActiveLogPointer、alarmActiveModelPointer、alarmActiveSpecificPointer和alarmClearModelPointer是对象标识符，它们引用特定用户可能无法直接访问的信息。这些对象标识符的结构不允许提取任何敏感信息。另外两个对象alarmClearResourceId和alarmActiveResourceId在语法上也是对象标识符，但它们的结构可以为用户提供潜在有用的信息，否则用户可能无法访问这些信息，例如特定资源的存在。
For further discussion of security, see section 3.4.
有关安全性的进一步讨论，请参见第3.4节。
This document is a product of the DISMAN Working Group.
本文件是DEMAN工作组的成果。
[M.3100] ITU Recommendation M.3100, "Generic Network Information Model", 1995
[M.3100]国际电联建议M.3100，“通用网络信息模型”，1995年
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol (SNMP)", STD 15, RFC 1157, May 1990.
[RFC1157]Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议（SNMP）”，STD 15，RFC 1157，1990年5月。
[RFC1215] Rose, M., "A Convention for defining traps for use with the SNMP", RFC 1215, March 1991.
[RFC1215]Rose，M.，“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[RFC2021] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2 using SMIv2", January 1997.
[RFC2021]Waldbusser，S.，“使用SMIv2的远程网络监控管理信息库版本2”，1997年1月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC3291] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 3291, May 2002.
[RFC3291]Daniele，M.，Haberman，B.，Routhier，S.和J.Schoenwaeld，“互联网网络地址的文本约定”，RFC 3291，2002年5月。
[RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002.
[RFC3411]Harrington，D.，Presohn，R.和B.Wijnen，“描述简单网络管理协议（SNMP）管理框架的体系结构”，STD 62，RFC 3411，2002年12月。
[RFC3413] Levi, D., Meyer, P. and B. Stewart, "Simple Network Management Protocol (SNMP) Applications", STD 62, RFC 3414, December 2002.
[RFC3413]Levi，D.，Meyer，P.和B.Stewart，“简单网络管理协议（SNMP）应用”，STD 62，RFC 3414，2002年12月。
[RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3415, December 2002.
[RFC3415]Wijnen，B.，Presohn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，STD 62，RFC 3415，2002年12月。
[RFC3416] Presuhn, R., Ed., "Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3416, December 2002.
[RFC3416]Presohn，R.，Ed.“简单网络管理协议（SNMP）的协议操作第2版”，STD 62，RFC 3416，2002年12月。
[RFC3584] Frye, R., Levi, D., Routhier, S. and B. Wijnen, "Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework", BCP 74, RFC 3584, August 2003.
[RFC3584]Frye，R.，Levi，D.，Routhier，S.和B.Wijnen，“互联网标准网络管理框架版本1，版本2和版本3之间的共存”，BCP 74，RFC 3584，2003年8月。
[X.733] ITU Recommendation X.733, "Information Technology - Open Systems Interconnection - System Management: Alarm Reporting Function", 1992.
[X.733]国际电联建议X.733，“信息技术-开放系统互连-系统管理：报警报告功能”，1992年。
[X.736] ITU Recommendation X.736, "Information Technology - Open Systems Interconnection - System Management: Security Alarm Reporting Function", 1992.
[X.736]国际电联建议X.736，“信息技术-开放系统互连-系统管理：安全警报报告功能”，1992年。
[RFC1657] Willis, S., Burruss, J. and J. Chu, Ed., "Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2", RFC 1657, July 1994.
[RFC1657]Willis，S.，Burruss，J.和J.Chu，Ed.，“使用SMIv2的第四版边界网关协议（BGP-4）的托管对象定义”，RFC 1657，1994年7月。
[RFC2737] McCloghrie, K. and A. Bierman, "Entity MIB (version 2)", RFC 2737, December 1999.
[RFC2737]McCloghrie，K.和A.Bierman，“实体MIB（版本2）”，RFC 27371999年12月。
[RFC2819] Waldbusser, S. "Remote Network Monitoring Management Information Base", STD 59, RFC 2819, May 2000.
[RFC2819]Waldbusser，S.“远程网络监控管理信息库”，STD 59，RFC 2819，2000年5月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“使用SMIv2的接口组MIB”，RFC 28632000年6月。
[RFC2981] Kavasseri, R., Ed., "Event MIB", RFC 2981, October 2000.
[RFC2981]卡瓦塞里，R.，编辑，“事件MIB”，RFC 29812000年10月。
[RFC3014] Kavasseri, R., "Notification Log MIB", RFC 3014, November 2000.
[RFC3014]Kavasseri，R.，“通知日志MIB”，RFC30142000年11月。
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC3418] Presuhn, R., Ed., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002.
[RFC3418]Presohn，R.，Ed.“简单网络管理协议（SNMP）的管理信息库（MIB）”，STD 62，RFC 3418，2002年12月。
[RFC3805] Bergman, R., Lewis, H. and I. McDonald, "Printer MIB v2", RFC 3805, June 2004.
[RFC3805]伯格曼，R.，刘易斯，H.和I.麦克唐纳，“打印机MIB v2”，RFC 3805，2004年6月。
Sharon Chisholm Nortel Networks PO Box 3511, Station C Ottawa, Ontario, K1Y 4H7 Canada
Sharon Chisholm Nortel Networks加拿大安大略省渥太华C站3511信箱，K1Y 4H7
EMail: schishol@nortelnetworks.com
EMail: schishol@nortelnetworks.com
Dan Romascanu Avaya Atidim Technology Park, Bldg. #3 Tel Aviv, 61131 Israel
以色列特拉维夫3号楼Dan Romascanu Avaya Atidim技术园，61131
Phone: +972-3-645-8414
EMail: dromasca@avaya.com
Phone: +972-3-645-8414
EMail: dromasca@avaya.com
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
版权所有（C）互联网协会（2004年）。本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。