Network Working Group R. Kavasseri
Request for Comments: 2981 (Editor of this version)
Category: Standards Track B. Stewart
(Author of previous version)
Cisco Systems, Inc.
October 2000
Network Working Group R. Kavasseri
Request for Comments: 2981 (Editor of this version)
Category: Standards Track B. Stewart
(Author of previous version)
Cisco Systems, Inc.
October 2000
Event 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 (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
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 managed objects that can be used to manage and monitor MIB objects and take action through events.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了可用于管理和监视MIB对象以及通过事件执行操作的托管对象。
The Event MIB provides the ability to monitor MIB objects on the local system or on a remote system and take simple action when a trigger condition is met.
事件MIB提供监视本地系统或远程系统上的MIB对象的能力，并在满足触发条件时执行简单操作。
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 RFC 2119.
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119中的说明进行解释。
Table of Contents
目录
1 The SNMP Management Framework ............................... 2
2 Overview .................................................... 3
3 Relationship to Other MIBs .................................. 3
4 MIB Sections ................................................ 4
5 Operation ................................................... 5
6 Security .................................................... 7
7 Definitions ................................................. 7
8 Intellectual Property ....................................... 47
9 Acknowledgements ............................................ 47
1 The SNMP Management Framework ............................... 2
2 Overview .................................................... 3
3 Relationship to Other MIBs .................................. 3
4 MIB Sections ................................................ 4
5 Operation ................................................... 5
6 Security .................................................... 7
7 Definitions ................................................. 7
8 Intellectual Property ....................................... 47
9 Acknowledgements ............................................ 47
10 References ................................................. 47
11 Security Considerations .................................... 49
12 Author's Address ........................................... 49
13 Editor's Address ........................................... 49
14 Full Copyright Statement ................................... 50
10 References ................................................. 47
11 Security Considerations .................................... 49
12 Author's Address ........................................... 49
13 Editor's Address ........................................... 49
14 Full Copyright Statement ................................... 50
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2571 [RFC2571].
o RFC 2571[RFC2571]中描述的总体架构。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[RFC1155]、STD 16、RFC 1212[RFC1212]和RFC 1215[RFC1215]中进行了描述。第二个版本称为SMIv2，在STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]中进行了描述。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15 RFC 1157[RFC1157]中进行了描述。SNMP消息协议的第二个版本不是Internet标准跟踪协议，称为SNMPv2c，在RFC 1901[RFC1901]和RFC 1906[RFC1906]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[RFC1906]、RFC 2572[RFC2572]和RFC 2574[RFC2574]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905].
o 访问管理信息的协议操作。STD 15、RFC 1157[RFC1157]中描述了第一组协议操作和相关PDU格式。RFC 1905[RFC1905]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575].
o RFC 2573[RFC2573]中描述的一组基本应用程序和RFC 2575[RFC2575]中描述的基于视图的访问控制机制。
A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570].
有关当前SNMP管理框架的更详细介绍，请参见RFC 2570[RFC2570]。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI中定义的机制定义的。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. It may not be possible to meaningfully monitor Counter64 objects using an SMIv1 version of the MIB.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。生成的已翻译MIB必须在语义上等效，除非由于无法翻译而省略了对象或事件（使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。使用SMIv1版本的MIB可能无法有意义地监视Counter64对象。
With network sizes well beyond the ability of people to manage them directly, automated, distributed management is vital. An important aspect of such management is the ability of a system to monitor itself or for some other system to monitor it.
由于网络规模远远超出了人们直接管理网络的能力，自动化、分布式管理至关重要。这种管理的一个重要方面是系统监控自身或其他系统监控自身的能力。
The Event MIB provides the ability to monitor MIB objects on the local system or on a remote system and take simple action when a trigger condition is met.
事件MIB提供监视本地系统或远程系统上的MIB对象的能力，并在满足触发条件时执行简单操作。
The MIB is intended to suit either a relatively powerful manager or mid- level manager, as well as a somewhat more limited self-managing system.
MIB旨在适合相对强大的经理或中级经理，以及更有限的自我管理系统。
The Event MIB is based on extensive experience with the RMON MIB [RFC1757] and provides a superset of the capabilities of the RMON alarm and event groups. Conceptually, the key extension is the ability to allow alarms to be generated for MIB objects that are on another network element. The Event MIB calls "triggers" what the RMON MIB called "alarms," but the concepts are the same. Event MIB triggers maintain the RMON handling of thresholds and add the concept of booleans. Event MIB events maintain the RMON concept of sending an SNMP notification in response to a trigger and add the concept of setting a MIB object.
事件MIB基于对RMON MIB[RFC1757]的丰富经验，并提供了RMON报警和事件组功能的超集。从概念上讲，关键扩展是允许为另一个网元上的MIB对象生成警报的能力。事件MIB调用RMON MIB称之为“报警”的“触发器”，但概念是相同的。事件MIB触发器维护阈值的RMON处理，并添加布尔概念。事件MIB事件维护RMON的概念，即发送SNMP通知以响应触发器，并添加设置MIB对象的概念。
The Event MIB is the successor and update to SNMPv2's Manager-to-Manager MIB [RFC1451] which was declared Historic pending this work.
事件MIB是SNMPv2的Manager到Manager MIB[RFC1451]的继承者和更新，该MIB已被宣布为历史性的，待执行此工作。
The Event MIB depends on the services of the SNMPv3 Management Target and Notification MIBs [RFC2573].
事件MIB取决于SNMPv3管理目标和通知MIB的服务[RFC2573]。
The Event MIB is nicely complemented by the Distributed Management Expression MIB [RFC2982], which is the expected source of boolean objects to monitor. Note that there is considerable overlap between
事件MIB由分布式管理表达式MIB[RFC2982]很好地补充，它是要监视的布尔对象的预期来源。请注意，这两种方法之间有相当大的重叠
the wildcard and delta sample capabilities of the Event and Expression MIBs. A carefully-planned implementation might well use common code to provide the overlapping functions.
事件和表达式MIB的通配符和增量示例功能。精心规划的实现可能会使用公共代码来提供重叠的功能。
The MIB has four sections: triggers, objects, events, and notifications. Triggers define the conditions that lead to events. Events may cause notifications.
MIB有四个部分：触发器、对象、事件和通知。触发器定义导致事件的条件。事件可能会导致通知。
The trigger table lists what objects are to be monitored and how and relates each trigger to an event. It has supplementary, companion tables for additional objects that depend on the type of test done for the trigger.
触发器表列出了要监视的对象以及每个触发器与事件的关系。它有附加对象的补充表，这些对象取决于为触发器执行的测试类型。
The objects table lists objects that can be added to notifications based on the trigger, the trigger test type, or the event that resulted in the notification.
对象表列出了可以根据触发器、触发器测试类型或导致通知的事件添加到通知中的对象。
The event table defines what happens when an event is triggered: sending a notification, setting a MIB object or both. It has supplementary, companion tables for additional objects that depend on the action taken.
事件表定义了触发事件时发生的情况：发送通知、设置MIB对象或两者兼而有之。它有附加的、伴随的表，用于根据所采取的操作确定的附加对象。
The notification section defines a set of generic notifications to go with the events and for Event MIB error handling, and it defines a set of objects to put in those notifications.
通知部分定义了一组与事件和事件MIB错误处理相关的通用通知，并定义了一组要放入这些通知中的对象。
The following diagram describes the relationships between the tables in the Event MIB.
下图描述了事件MIB中表之间的关系。
+-----------------------------+
| mteTriggerEntry | subclassed by:
| { mteOwner, |---+
| IMPLIED mteTriggerName } | +-- mteTriggerDeltaEntry
| | |
| | +-- mteTriggerExistenceEntry
| | |
| | +-- mteTriggerBooleanEntry
| | |
| | +-- mteTriggerThresholdEntry
| |
| mteTrigger*Event -------------------------------->+
| | |
| mteTriggerObjects ------------------>+ |
+-----------------------------+ | |
| |
+-----------------------------+ V |
| mteObjectsEntry | | |
| { mteOwner, |<-------------+ |
| mteObjectsName, | |
| mteObjectsIndex } | |
+-----------------------------+ |
V
+---------------------------+ |
| mteEventEntry |<----------------------------+
| { mteOwner, |
| IMPLIED mteEventName } |
| |
| mteEventAction---> + (condition)
+---------------------------+ |
V
+---------------------------+ | +---------------------------+
| mteEventNotificationEntry | | | mteEventSetEntry |
| { mteOwner, |<--+-->| { mteOwner, |
| IMPLIED mteEventName } | | IMPLIED mteEventName } |
+---------------------------+ +---------------------------+
+-----------------------------+
| mteTriggerEntry | subclassed by:
| { mteOwner, |---+
| IMPLIED mteTriggerName } | +-- mteTriggerDeltaEntry
| | |
| | +-- mteTriggerExistenceEntry
| | |
| | +-- mteTriggerBooleanEntry
| | |
| | +-- mteTriggerThresholdEntry
| |
| mteTrigger*Event -------------------------------->+
| | |
| mteTriggerObjects ------------------>+ |
+-----------------------------+ | |
| |
+-----------------------------+ V |
| mteObjectsEntry | | |
| { mteOwner, |<-------------+ |
| mteObjectsName, | |
| mteObjectsIndex } | |
+-----------------------------+ |
V
+---------------------------+ |
| mteEventEntry |<----------------------------+
| { mteOwner, |
| IMPLIED mteEventName } |
| |
| mteEventAction---> + (condition)
+---------------------------+ |
V
+---------------------------+ | +---------------------------+
| mteEventNotificationEntry | | | mteEventSetEntry |
| { mteOwner, |<--+-->| { mteOwner, |
| IMPLIED mteEventName } | | IMPLIED mteEventName } |
+---------------------------+ +---------------------------+
The Event MIB is instrumentation for a distributed management application that monitors MIB objects. In its simplest form this application monitors individual, local MIB objects, just as an RMON probe fulfills the functions implied by RMON's alarm and event operation. Additionally the application can monitor remote objects and wildcarded groups of objects.
事件MIB是监视MIB对象的分布式管理应用程序的工具。该应用程序以其最简单的形式监视单个本地MIB对象，就像RMON探测器完成RMON的报警和事件操作所暗示的功能一样。此外，应用程序还可以监视远程对象和通配符对象组。
Remote monitoring uses the tag service of the Management Target MIB [RFC2573] to select and access remote systems as an ordinary SNMP-based management application. Local monitoring may be via a more intimate, local interface which may, for example, bypass SNMP encoding but otherwise is functionally identical to remote SNMP operation, including the application of access control. A self-management only system MAY not implement remote monitoring.
远程监控使用管理目标MIB[RFC2573]的标记服务作为基于SNMP的普通管理应用程序来选择和访问远程系统。本地监控可以通过更私密的本地接口进行，例如，该接口可以绕过SNMP编码，但在其他方面与远程SNMP操作功能相同，包括访问控制的应用。仅限自我管理的系统可能无法实现远程监控。
Wildcards indicate that the application SHOULD use a GetNext-type operation to find the zero or more instances implied by a truncated object identifier, just like an ordinary SNMP-based management application. Each instance of a wildcard is treated as if it were a separate entry, that is the instances of a wildcarded object are independent of one another. For example, a wild-carded object may trigger an event, and result in the setting of another wildcarded object. The instance that satisfied the trigger function is used to perform the set function. All of this takes place independently of any additional instances that may fill the wildcard.
通配符表示应用程序应该使用GetNext类型操作来查找被截断的对象标识符所隐含的零个或多个实例，就像普通的基于SNMP的管理应用程序一样。通配符的每个实例都被视为一个单独的条目，即通配符对象的实例彼此独立。例如，一个通配符对象可能触发一个事件，并导致另一个通配符对象的设置。满足触发函数的实例用于执行set函数。所有这些都独立于可能填充通配符的任何其他实例。
Error handling is by notification. These error notifications SHOULD be enabled only for the diagnosis of problems indicated by error counters. If minimizing the probability of notification loss is a concern they SHOULD be transmitted as Inform PDUs as described in the [SNMP-TARGET-MIB] or directed to a log as described in the Notification Log MIB [rfcNotificationLogMIB]. Note that this does not mean the Notification Log MIB is REQUIRED, since in fact notifications usually are not lost, but that the Notification Log MIB can be helpful with this as well as other MIBs that include notifications.
错误处理是通过通知进行的。这些错误通知应仅在诊断错误计数器指示的问题时启用。如果将通知丢失的概率降至最低是一个问题，则应按照[SNMP-TARGET-MIB]中的说明将其作为通知PDU传输，或按照通知日志MIB[rfcNotificationLogMIB]中的说明将其定向到日志。请注意，这并不意味着需要通知日志MIB，因为事实上通知通常不会丢失，但通知日志MIB对这一点以及包含通知的其他MIB都有帮助。
Although like most MIBs this one has no explicit controls for the persistence of the values set in configuring events, a robust, polite implementation would certainly not force its managing applications to reconfigure it whenever it resets.
尽管与大多数MIB一样，此MIB没有明确控制配置事件中设置的值的持久性，但一个健壮、礼貌的实现肯定不会强迫其管理应用程序在重置时重新配置它。
Again, as with most MIBs, it is implementation-specific how a system provides and manages such persistence. To speculate, one could imagine, for example, that persistence depended on the context in which the expression was configured, or perhaps system-specific characteristics of the expression's owner. Or perhaps everything in a MIB such as this one, which is clearly aimed at persistent configuration, is automatically part of a system's other persistent configuration.
同样，与大多数MIB一样，系统如何提供和管理这种持久性取决于具体的实现。举例来说，我们可以想象，持久性取决于表达式配置的上下文，或者可能取决于表达式所有者的系统特定特征。或者，像这样的MIB中的所有内容（显然是针对持久性配置的）都会自动成为系统其他持久性配置的一部分。
Security of Event MIB entries depends on SNMPv3 access control for the entire MIB or for subsets based on entry owner names.
事件MIB条目的安全性取决于整个MIB或基于条目所有者名称的子集的SNMPv3访问控制。
Security of monitored objects for remote access depends on the Management Target MIB [RFC2573]. Security for local access can depend on the Management Target MIB or on recording appropriate security credentials of the creator of an entry and using those to access the local objects. These security credentials are the parameters necessary as inputs to isAccessAllowed from the Architecture for Describing SNMP Management Frameworks. When accessing local objects without using a local target tag, the system MUST (conceptually) use isAccessAllowed to ensure that it does not violate security.
远程访问受监控对象的安全性取决于管理目标MIB[RFC2573]。本地访问的安全性可能取决于管理目标MIB，或者取决于记录条目创建者的适当安全凭据并使用这些凭据访问本地对象。这些安全凭据是必要的参数，作为描述SNMP管理框架的体系结构允许的ISACCESS输入。在不使用本地目标标记访问本地对象时，系统必须（概念上）使用isAccessAllowed以确保它不会违反安全性。
To facilitate the provisioning of access control by a security administrator for this MIB itself using the View-Based Access Control Model (VACM) defined in RFC 2275 [RFC2575] for tables in which multiple users may need to independently create or modify entries, the initial index is used as an "owner index". Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy.
为了方便安全管理员使用RFC 2275[RFC2575]中定义的基于视图的访问控制模型（VACM）为该MIB本身提供访问控制，对于多个用户可能需要独立创建或修改条目的表，初始索引用作“所有者索引”。这样的初始索引具有snmpadmin语法，因此可以根据安全策略简单地映射到VACM中定义的securityName或groupName。
If a security administrator were to employ such an approach, all entries in related tables belonging to a particular user will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same sub-identifiers (except for the "column" sub-identifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask "wildcarding" the column sub-identifier. More elaborate configurations are possible.
如果安全管理员采用这种方法，则属于特定用户的相关表中的所有条目都将具有相同的初始索引值。对于特定表中的给定用户条目，这些条目中信息的对象标识符将具有相同的子标识符（除了“列”子标识符），直到编码所有者索引的末尾。要将VACM配置为允许访问表的这一部分，可以创建vacmViewTreeFamilyTable条目，其值为vacmViewTreeFamilySubtree，包括所有者索引部分，以及VACMVIEWTREEFAMILYMAK“通配符”列子标识符。更复杂的配置是可能的。
DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN
DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, NOTIFICATION-TYPE, Counter32, Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, TruthValue FROM SNMPv2-TC
从SNMPv2导入模块标识、对象类型、整数32、无符号32、通知类型、计数器32、仪表32、mib-2、零点零（来自SNMPv2 SMI文本约定）、行状态、TruthValue（来自SNMPv2 TC）
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF sysUpTime FROM SNMPv2-MIB SnmpTagValue FROM SNMP-TARGET-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
SNMPv2 CONF sysUpTime FROM SNMPv2 MIB SnmpTagValue FROM SNMP-TARGET-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB的模块遵从性、对象组、通知组；
dismanEventMIB MODULE-IDENTITY LAST-UPDATED "200010160000Z" -- 16 October 2000 ORGANIZATION "IETF Distributed Management Working Group" CONTACT-INFO "Ramanathan Kavasseri Cisco Systems, Inc. 170 West Tasman Drive, San Jose CA 95134-1706. Phone: +1 408 526 4527 Email: ramk@cisco.com" DESCRIPTION "The MIB module for defining event triggers and actions for network management purposes." -- Revision History
DisamaneventMIB MODULE-IDENTITY上次更新的“200010160000Z”-2000年10月16日组织“IETF分布式管理工作组”联系方式“Ramanathan Kavasseri Cisco Systems，Inc.，地址：加利福尼亚州圣何塞市西塔斯曼大道170号95134-1706。电话：+1408 526 4527电子邮件：ramk@cisco.com“说明“用于定义用于网络管理的事件触发器和操作的MIB模块。”--修订历史记录
REVISION "200010160000Z" -- 16 October 2000
DESCRIPTION "This is the initial version of this MIB.
Published as RFC 2981"
::= { mib-2 88 }
REVISION "200010160000Z" -- 16 October 2000
DESCRIPTION "This is the initial version of this MIB.
Published as RFC 2981"
::= { mib-2 88 }
dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 }
dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 }
-- Management Triggered Event (MTE) objects
--管理触发事件（MTE）对象
mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 }
mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 }
mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 }
mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 }
mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 }
mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 }
mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 }
mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 }
-- -- Textual Conventions --
----文本约定--
FailureReason ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Reasons for failures in an attempt to perform a management
request.
FailureReason ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Reasons for failures in an attempt to perform a management
request.
The first group of errors, numbered less than 0, are related to problems in sending the request. The existence of a particular error code here does not imply that all implementations are capable of sensing that error and
第一组错误（编号小于0）与发送请求时出现的问题有关。此处特定错误代码的存在并不意味着所有实现都能够感知该错误并
returning that code.
返回那个密码。
The second group, numbered greater than 0, are copied directly from SNMP protocol operations and are intended to carry exactly the meanings defined for the protocol as returned in an SNMP response.
第二组（编号大于0）直接从SNMP协议操作中复制，目的是准确地承载SNMP响应中返回的协议定义的含义。
localResourceLack some local resource such as memory lacking or mteResourceSampleInstanceMaximum exceeded badDestination unrecognized domain name or otherwise invalid destination address destinationUnreachable can't get to destination address noResponse no response to SNMP request badType the data syntax of a retrieved object as not as expected sampleOverrun another sample attempt occurred before the previous one completed"
LocalResourceLock某些本地资源，例如内存不足或mteResourceSampleInstanceMaximum已超出badDestination无法识别的域名或其他无效的目标地址DestinationUnrechable无法访问目标地址或响应SNMP请求BAD键入检索到的对象的数据语法与预期不符SampleOverflow在上一次采样尝试完成之前发生了另一次采样尝试“
SYNTAX INTEGER { localResourceLack(-1), badDestination(-2), destinationUnreachable(-3), noResponse(-4), badType(-5), sampleOverrun(-6),
语法整数{localResourceLack（-1）、badDestination（-2）、destinationUnreachable（-3）、NorResponse（-4）、badType（-5）、SampleOverflow（-6），
noError(0),
无错误（0），
tooBig(1), noSuchName(2), badValue(3), readOnly(4), genErr(5), noAccess(6), wrongType(7), wrongLength(8), wrongEncoding(9), wrongValue(10), noCreation(11), inconsistentValue(12), resourceUnavailable(13), commitFailed(14), undoFailed(15), authorizationError(16), notWritable(17), inconsistentName(18) } --
tooBig（1）、noSuchName（2）、badValue（3）、readOnly（4）、genErr（5）、noAccess（6）、ErrorType（7）、ErrorLength（8）、ErrorEncoding（9）、ErrorValue（10）、noCreation（11）、inconsistentValue（12）、resourceUnavailable（13）、commitFailed（14）、undoFailed（15）、authorizationError（16）、notWritable（17）、inconsistentName（18）}）--
-- Resource Control Section --
--资源管制组--
mteResourceSampleMinimum OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The minimum mteTriggerFrequency this system will accept. A system may use the larger values of this minimum to lessen the impact of constant sampling. For larger sampling intervals the system samples less often and suffers less overhead. This object provides a way to enforce such lower overhead for all triggers created after it is set.
mteResourceSampleMinimum对象类型语法整数32（1..2147483647）单位“秒”最大访问读写状态当前说明“此系统可接受的最低MTT频率。系统可以使用该最小值的较大值来减小恒定采样的影响。对于较大的采样间隔，系统采样频率较低，开销较小。此对象提供了一种方法，可以对设置后创建的所有触发器强制执行这种较低的开销。
Unless explicitly resource limited, a system's value for this object SHOULD be 1, allowing as small as a 1 second interval for ongoing trigger sampling.
除非有明确的资源限制，否则此对象的系统值应为1，允许进行触发采样的间隔最短为1秒。
Changing this value will not invalidate an existing setting
of mteTriggerFrequency."
::= { mteResource 1 }
Changing this value will not invalidate an existing setting
of mteTriggerFrequency."
::= { mteResource 1 }
mteResourceSampleInstanceMaximum OBJECT-TYPE SYNTAX Unsigned32 UNITS "instances" MAX-ACCESS read-write STATUS current DESCRIPTION "The maximum number of instance entries this system will support for sampling.
mteResourceSampleInstanceMaximum对象类型语法Unsigned32个单位“实例”MAX-ACCESS读写状态当前描述“此系统支持采样的最大实例条目数。
These are the entries that maintain state, one for each instance of each sampled object as selected by mteTriggerValueID. Note that wildcarded objects result in multiple instances of this state.
这些是维护状态的条目，每个采样对象的每个实例一个，由mteTriggerValueID选择。请注意，通配符对象会导致此状态的多个实例。
A value of 0 indicates no preset limit, that is, the limit is dynamic based on system operation and resources.
值为0表示没有预设限制，即限制是基于系统操作和资源的动态限制。
Unless explicitly resource limited, a system's value for this object SHOULD be 0.
除非明确限制资源，否则此对象的系统值应为0。
Changing this value will not eliminate or inhibit existing sample state but could prevent allocation of additional state information."
更改此值不会消除或禁止现有采样状态，但可能会阻止分配其他状态信息。”
::= { mteResource 2 }
::= { mteResource 2 }
mteResourceSampleInstances OBJECT-TYPE
SYNTAX Gauge32
UNITS "instances"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of currently active instance entries as
defined for mteResourceSampleInstanceMaximum."
::= { mteResource 3 }
mteResourceSampleInstances OBJECT-TYPE
SYNTAX Gauge32
UNITS "instances"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of currently active instance entries as
defined for mteResourceSampleInstanceMaximum."
::= { mteResource 3 }
mteResourceSampleInstancesHigh OBJECT-TYPE
SYNTAX Gauge32
UNITS "instances"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The highest value of mteResourceSampleInstances that has
occurred since initialization of the management system."
::= { mteResource 4 }
mteResourceSampleInstancesHigh OBJECT-TYPE
SYNTAX Gauge32
UNITS "instances"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The highest value of mteResourceSampleInstances that has
occurred since initialization of the management system."
::= { mteResource 4 }
mteResourceSampleInstanceLacks OBJECT-TYPE
SYNTAX Counter32
UNITS "instances"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this system could not take a new sample
because that allocation would have exceeded the limit set by
mteResourceSampleInstanceMaximum."
::= { mteResource 5 }
mteResourceSampleInstanceLacks OBJECT-TYPE
SYNTAX Counter32
UNITS "instances"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this system could not take a new sample
because that allocation would have exceeded the limit set by
mteResourceSampleInstanceMaximum."
::= { mteResource 5 }
-- -- Trigger Section --
----触发段--
-- Counters
--计数器
mteTriggerFailures OBJECT-TYPE SYNTAX Counter32 UNITS "failures" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times an attempt to check for a trigger condition has failed. This counts individually for each attempt in a group of targets or each attempt for a
mteTriggerFailures对象类型语法计数器32个单位“failures”MAX-ACCESS只读状态当前描述“尝试检查触发器条件失败的次数。这对一组目标中的每次尝试或对一个
wildcarded object."
::= { mteTrigger 1 }
wildcarded object."
::= { mteTrigger 1 }
-- -- Trigger Table --
----触发表--
mteTriggerTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information."
::= { mteTrigger 2 }
mteTriggerTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information."
::= { mteTrigger 2 }
mteTriggerEntry OBJECT-TYPE
SYNTAX MteTriggerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single trigger. Applications create and
delete entries using mteTriggerEntryStatus."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerTable 1 }
mteTriggerEntry OBJECT-TYPE
SYNTAX MteTriggerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single trigger. Applications create and
delete entries using mteTriggerEntryStatus."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerTable 1 }
MteTriggerEntry ::= SEQUENCE {
mteOwner SnmpAdminString,
mteTriggerName SnmpAdminString,
mteTriggerComment SnmpAdminString,
mteTriggerTest BITS,
mteTriggerSampleType INTEGER,
mteTriggerValueID OBJECT IDENTIFIER,
mteTriggerValueIDWildcard TruthValue,
mteTriggerTargetTag SnmpTagValue,
mteTriggerContextName SnmpAdminString,
mteTriggerContextNameWildcard TruthValue,
mteTriggerFrequency Unsigned32,
mteTriggerObjectsOwner SnmpAdminString,
mteTriggerObjects SnmpAdminString,
mteTriggerEnabled TruthValue,
mteTriggerEntryStatus RowStatus
}
MteTriggerEntry ::= SEQUENCE {
mteOwner SnmpAdminString,
mteTriggerName SnmpAdminString,
mteTriggerComment SnmpAdminString,
mteTriggerTest BITS,
mteTriggerSampleType INTEGER,
mteTriggerValueID OBJECT IDENTIFIER,
mteTriggerValueIDWildcard TruthValue,
mteTriggerTargetTag SnmpTagValue,
mteTriggerContextName SnmpAdminString,
mteTriggerContextNameWildcard TruthValue,
mteTriggerFrequency Unsigned32,
mteTriggerObjectsOwner SnmpAdminString,
mteTriggerObjects SnmpAdminString,
mteTriggerEnabled TruthValue,
mteTriggerEntryStatus RowStatus
}
mteOwner OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION
mteOwner对象类型语法snmpadmin字符串（大小（0..32））MAX-ACCESS不可访问状态当前说明
"The owner of this entry. The exact semantics of this
string are subject to the security policy defined by the
security administrator."
::= { mteTriggerEntry 1 }
"The owner of this entry. The exact semantics of this
string are subject to the security policy defined by the
security administrator."
::= { mteTriggerEntry 1 }
mteTriggerName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A locally-unique, administratively assigned name for the
trigger within the scope of mteOwner."
::= { mteTriggerEntry 2 }
mteTriggerName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A locally-unique, administratively assigned name for the
trigger within the scope of mteOwner."
::= { mteTriggerEntry 2 }
mteTriggerComment OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A description of the trigger's function and use."
DEFVAL { ''H }
::= { mteTriggerEntry 3 }
mteTriggerComment OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A description of the trigger's function and use."
DEFVAL { ''H }
::= { mteTriggerEntry 3 }
mteTriggerTest OBJECT-TYPE SYNTAX BITS { existence(0), boolean(1), threshold(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The type of trigger test to perform. For 'boolean' and 'threshold' tests, the object at mteTriggerValueID MUST evaluate to an integer, that is, anything that ends up encoded for transmission (that is, in BER, not ASN.1) as an integer.
mteTriggerTest对象类型语法位{existence（0），boolean（1），threshold（2）}MAX-ACCESS read create STATUS current DESCRIPTION“要执行的触发器测试的类型。对于'boolean'和'threshold'测试，mteTriggerValueID处的对象必须计算为整数，即任何最终编码以供传输的对象（即，在BER中，不是ASN.1）作为整数。
For 'existence', the specific test is as selected by mteTriggerExistenceTest. When an object appears, vanishes or changes value, the trigger fires. If the object's appearance caused the trigger firing, the object MUST vanish before the trigger can be fired again for it, and vice versa. If the trigger fired due to a change in the object's value, it will be fired again on every successive value change for that object.
对于“存在”，具体测试由mteTriggerExistenceTest选择。当对象出现、消失或更改值时，触发器将触发。如果该对象的外观导致触发器触发，则该对象必须在再次触发触发器之前消失，反之亦然。如果触发器是由于对象值的更改而触发的，则该对象的每个连续值更改都会再次触发该触发器。
For 'boolean', the specific test is as selected by mteTriggerBooleanTest. If the test result is true the trigger fires. The trigger will not fire again until the value has become false and come back to true.
对于“boolean”，具体测试由mteTriggerBooleanTest选择。如果测试结果为真，则触发。在值变为false并返回true之前，触发器不会再次触发。
For 'threshold' the test works as described below for
对于“阈值”，测试工作如下所述
mteTriggerThresholdStartup, mteTriggerThresholdRising, and mteTriggerThresholdFalling.
mteTriggerThresholdStartup、mteTriggerThresholdRising和mteTriggerThresholdFalling。
Note that combining 'boolean' and 'threshold' tests on the
same object may be somewhat redundant."
DEFVAL { { boolean } }
::= { mteTriggerEntry 4 }
Note that combining 'boolean' and 'threshold' tests on the
same object may be somewhat redundant."
DEFVAL { { boolean } }
::= { mteTriggerEntry 4 }
mteTriggerSampleType OBJECT-TYPE SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The type of sampling to perform.
mteTriggerSampleType对象类型语法整数{absoluteValue（1），deltaValue（2）}MAX-ACCESS读取创建状态当前描述“要执行的采样类型。
An 'absoluteValue' sample requires only a single sample to be meaningful, and is exactly the value of the object at mteTriggerValueID at the sample time.
“absoluteValue”样本只需要一个样本才有意义，并且正好是采样时mteTriggerValueID处对象的值。
A 'deltaValue' requires two samples to be meaningful and is thus not available for testing until the second and subsequent samples after the object at mteTriggerValueID is first found to exist. It is the difference between the two samples. For unsigned values it is always positive, based on unsigned arithmetic. For signed values it can be positive or negative.
“deltaValue”需要两个样本才有意义，因此在mteTriggerValueID处的对象首次发现存在后的第二个和后续样本之前，无法进行测试。这是两个样本之间的差异。基于无符号算术，对于无符号值，它始终为正。对于有符号值，它可以是正值或负值。
For SNMP counters to be meaningful they should be sampled as a 'deltaValue'.
要使SNMP计数器有意义，应将其作为“deltaValue”进行采样。
For 'deltaValue' mteTriggerDeltaTable contains further parameters.
对于“deltaValue”，mteTriggerDeltaTable包含更多参数。
If only 'existence' is set in mteTriggerTest this object has
no meaning."
DEFVAL { absoluteValue }
::= { mteTriggerEntry 5 }
If only 'existence' is set in mteTriggerTest this object has
no meaning."
DEFVAL { absoluteValue }
::= { mteTriggerEntry 5 }
mteTriggerValueID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The object identifier of the MIB object to sample to see if the trigger should fire.
mteTriggerValueID对象类型语法对象标识符MAX-ACCESS read create STATUS current DESCRIPTION“要采样的MIB对象的对象标识符，以查看是否应触发触发器。
This may be wildcarded by truncating all or part of the instance portion, in which case the value is obtained as if with a GetNext function, checking multiple values
这可以通过截断全部或部分实例部分来进行通配符，在这种情况下，该值的获取就像使用GetNext函数一样，检查多个值
if they exist. If such wildcarding is applied, mteTriggerValueIDWildcard must be 'true' and if not it must be 'false'.
如果它们存在的话。如果应用了此类通配符，则mteTriggerValueIDWildcard必须为“true”，否则必须为“false”。
Bad object identifiers or a mismatch between truncating the identifier and the value of mteTriggerValueIDWildcard result in operation as one would expect when providing the wrong identifier to a Get or GetNext operation. The Get will fail or get the wrong object. The GetNext will indeed get whatever is next, proceeding until it runs past the initial part of the identifier and perhaps many unintended objects for confusing results. If the value syntax of those objects is not usable, that results in a 'badType' error that terminates the scan.
错误的对象标识符或截断标识符与mteTriggerValueIDWildcard值之间的不匹配会导致操作，正如向Get或GetNext操作提供错误标识符时所预期的那样。Get将失败或获取错误的对象。GetNext确实会获取下一个，直到它运行过标识符的初始部分，可能还有许多意外的对象，导致结果混乱。如果这些对象的值语法不可用，则会导致“badType”错误，从而终止扫描。
Each instance that fills the wildcard is independent of any
additional instances, that is, wildcarded objects operate
as if there were a separate table entry for each instance
that fills the wildcard without having to actually predict
all possible instances ahead of time."
DEFVAL { zeroDotZero }
::= { mteTriggerEntry 6 }
Each instance that fills the wildcard is independent of any
additional instances, that is, wildcarded objects operate
as if there were a separate table entry for each instance
that fills the wildcard without having to actually predict
all possible instances ahead of time."
DEFVAL { zeroDotZero }
::= { mteTriggerEntry 6 }
mteTriggerValueIDWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control for whether mteTriggerValueID is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard."
DEFVAL { false }
::= { mteTriggerEntry 7 }
mteTriggerValueIDWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control for whether mteTriggerValueID is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard."
DEFVAL { false }
::= { mteTriggerEntry 7 }
mteTriggerTargetTag OBJECT-TYPE SYNTAX SnmpTagValue MAX-ACCESS read-create STATUS current DESCRIPTION "The tag for the target(s) from which to obtain the condition for a trigger check.
mteTriggerTargetTag对象类型语法SnmpTagValue MAX-ACCESS read create STATUS current DESCRIPTION“从中获取触发器检查条件的目标的标记。
A length of 0 indicates the local system. In this case, access to the objects indicated by mteTriggerValueID is under the security credentials of the requester that set mteTriggerEntryStatus to 'active'. Those credentials are the input parameters for isAccessAllowed from the Architecture for Describing SNMP Management Frameworks.
长度为0表示本地系统。在这种情况下，对mteTriggerValueID指示的对象的访问权属于将mteTriggerEntryStatus设置为“活动”的请求者的安全凭据。这些凭据是从用于描述SNMP管理框架的体系结构中允许的ISACCESS的输入参数。
Otherwise access rights are checked according to the security
否则，将根据安全性检查访问权限
parameters resulting from the tag."
DEFVAL { ''H }
::= { mteTriggerEntry 8 }
parameters resulting from the tag."
DEFVAL { ''H }
::= { mteTriggerEntry 8 }
mteTriggerContextName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION "The management context from which to obtain mteTriggerValueID.
mteTriggerContextName对象类型语法SNMPAdministring MAX-ACCESS read create STATUS current DESCRIPTION“从中获取mteTriggerValueID的管理上下文。
This may be wildcarded by leaving characters off the end. For example use 'Repeater' to wildcard to 'Repeater1', 'Repeater2', 'Repeater-999.87b', and so on. To indicate such wildcarding is intended, mteTriggerContextNameWildcard must be 'true'.
这可以通过在末尾保留字符来进行通配符。例如，使用“Repeater”将通配符转换为“Repeater1”、“Repeater2”、“Repeater-999.87b”，等等。若要指示打算使用这种通配符，mteTriggerContextNameWildcard必须为“true”。
Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time.
填充通配符的每个实例都独立于任何其他实例，也就是说，通配符对象的操作就像每个实例都有一个单独的表条目填充通配符一样，而不必提前实际预测所有可能的实例。
Operation of this feature assumes that the local system has a
list of available contexts against which to apply the
wildcard. If the objects are being read from the local
system, this is clearly the system's own list of contexts.
For a remote system a local version of such a list is not
defined by any current standard and may not be available, so
this function MAY not be supported."
DEFVAL { ''H }
::= { mteTriggerEntry 9 }
Operation of this feature assumes that the local system has a
list of available contexts against which to apply the
wildcard. If the objects are being read from the local
system, this is clearly the system's own list of contexts.
For a remote system a local version of such a list is not
defined by any current standard and may not be available, so
this function MAY not be supported."
DEFVAL { ''H }
::= { mteTriggerEntry 9 }
mteTriggerContextNameWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control for whether mteTriggerContextName is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard."
DEFVAL { false }
::= { mteTriggerEntry 10 }
mteTriggerContextNameWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control for whether mteTriggerContextName is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard."
DEFVAL { false }
::= { mteTriggerEntry 10 }
mteTriggerFrequency OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current
mteTriggerFrequency对象类型语法无符号32单位“秒”最大读取创建状态当前
DESCRIPTION "The number of seconds to wait between trigger samples. To encourage consistency in sampling, the interval is measured from the beginning of one check to the beginning of the next and the timer is restarted immediately when it expires, not when the check completes.
DESCRIPTION“触发器采样之间等待的秒数。为鼓励采样的一致性，测量从一次检查开始到下一次检查开始的间隔，计时器在到期时立即重新启动，而不是在检查完成时。
If the next sample begins before the previous one completed the system may either attempt to make the check or treat this as an error condition with the error 'sampleOverrun'.
如果下一个样本在前一个样本完成之前开始，系统可能会尝试进行检查，或者将其视为错误条件，并显示错误“SampleOverflow”。
A frequency of 0 indicates instantaneous recognition of the condition. This is not possible in many cases, but may be supported in cases where it makes sense and the system is able to do so. This feature allows the MIB to be used in implementations where such interrupt-driven behavior is possible and is not likely to be supported for all MIB objects even then since such sampling generally has to be tightly integrated into low-level code.
频率为0表示即时识别该状况。这在许多情况下是不可能的，但在有意义且系统能够做到的情况下可能会得到支持。此功能允许在实现中使用MIB，在这种实现中，中断驱动行为是可能的，并且即使在这种情况下，也不可能支持所有MIB对象，因为这样的采样通常必须紧密集成到低级代码中。
Systems that can support this SHOULD document those cases
where it can be used. In cases where it can not, setting this
object to 0 should be disallowed."
DEFVAL { 600 }
::= { mteTriggerEntry 11 }
Systems that can support this SHOULD document those cases
where it can be used. In cases where it can not, setting this
object to 0 should be disallowed."
DEFVAL { 600 }
::= { mteTriggerEntry 11 }
mteTriggerObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"To go with mteTriggerObjects, the mteOwner of a group of
objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteTriggerEntry 12 }
mteTriggerObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"To go with mteTriggerObjects, the mteOwner of a group of
objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteTriggerEntry 12 }
mteTriggerObjects OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger.
mteTriggerObjects对象类型语法SNMPAdministring（大小（0..32））MAX-ACCESS read create STATUS current DESCRIPTION“mteObjectsTable中一组对象的mteObjectsName。这些对象将添加到触发此触发器产生的任何通知中。
A list of objects may also be added based on the event or on the value of mteTriggerTest.
还可以根据事件或mteTriggerTest的值添加对象列表。
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteTriggerEntry 13 }
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteTriggerEntry 13 }
mteTriggerEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A control to allow a trigger to be configured but not used.
When the value is 'false' the trigger is not sampled."
DEFVAL { false }
::= { mteTriggerEntry 14 }
mteTriggerEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A control to allow a trigger to be configured but not used.
When the value is 'false' the trigger is not sampled."
DEFVAL { false }
::= { mteTriggerEntry 14 }
mteTriggerEntryStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The control that allows creation and deletion of entries.
Once made active an entry may not be modified except to
delete it."
::= { mteTriggerEntry 15 }
mteTriggerEntryStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The control that allows creation and deletion of entries.
Once made active an entry may not be modified except to
delete it."
::= { mteTriggerEntry 15 }
-- -- Trigger Delta Table --
----触发器增量表--
mteTriggerDeltaTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerDeltaEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information for delta
sampling."
::= { mteTrigger 3 }
mteTriggerDeltaTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerDeltaEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information for delta
sampling."
::= { mteTrigger 3 }
mteTriggerDeltaEntry OBJECT-TYPE
SYNTAX MteTriggerDeltaEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single trigger's delta sampling. Entries
automatically exist in this this table for each mteTriggerEntry
that has mteTriggerSampleType set to 'deltaValue'."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerDeltaTable 1 }
mteTriggerDeltaEntry OBJECT-TYPE
SYNTAX MteTriggerDeltaEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single trigger's delta sampling. Entries
automatically exist in this this table for each mteTriggerEntry
that has mteTriggerSampleType set to 'deltaValue'."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerDeltaTable 1 }
MteTriggerDeltaEntry ::= SEQUENCE {
mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER,
mteTriggerDeltaDiscontinuityIDWildcard TruthValue,
mteTriggerDeltaDiscontinuityIDType INTEGER
}
MteTriggerDeltaEntry ::= SEQUENCE {
mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER,
mteTriggerDeltaDiscontinuityIDWildcard TruthValue,
mteTriggerDeltaDiscontinuityIDType INTEGER
}
sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 }
sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 }
mteTriggerDeltaDiscontinuityID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS current DESCRIPTION "The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or DateAndTime object that indicates a discontinuity in the value at mteTriggerValueID.
mteTriggerDeltaDiscontinuityID对象类型语法对象标识符MAX-ACCESS读写状态当前描述“表示mteTriggerValueID处的值不连续的时间标记、时间戳或DateAndTime对象的对象标识符（OID）。
The OID may be for a leaf object (e.g. sysUpTime.0) or may be wildcarded to match mteTriggerValueID.
OID可以用于叶对象（例如sysUpTime.0），也可以是通配符以匹配mteTriggerValueID。
This object supports normal checking for a discontinuity in a counter. Note that if this object does not point to sysUpTime discontinuity checking MUST still check sysUpTime for an overall discontinuity.
此对象支持对计数器中的不连续性进行常规检查。请注意，如果此对象未指向sysUpTime不连续性检查，则仍必须检查sysUpTime是否存在整体不连续性。
If the object identified is not accessible the sample attempt is in error, with the error code as from an SNMP request.
如果标识的对象不可访问，则示例尝试出错，错误代码来自SNMP请求。
Bad object identifiers or a mismatch between truncating the
identifier and the value of mteDeltaDiscontinuityIDWildcard
result in operation as one would expect when providing the
wrong identifier to a Get operation. The Get will fail or get
the wrong object. If the value syntax of those objects is not
usable, that results in an error that terminates the sample
with a 'badType' error code."
DEFVAL { sysUpTimeInstance }
::= { mteTriggerDeltaEntry 1 }
Bad object identifiers or a mismatch between truncating the
identifier and the value of mteDeltaDiscontinuityIDWildcard
result in operation as one would expect when providing the
wrong identifier to a Get operation. The Get will fail or get
the wrong object. If the value syntax of those objects is not
usable, that results in an error that terminates the sample
with a 'badType' error code."
DEFVAL { sysUpTimeInstance }
::= { mteTriggerDeltaEntry 1 }
mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Control for whether mteTriggerDeltaDiscontinuityID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard. Note that the value of this object will be the same as that of the corresponding instance of mteTriggerValueIDWildcard when the corresponding
mteTriggerDeltaDiscontinuityIDWildcard对象类型语法TruthValue MAX-ACCESS读写状态当前说明控制mteTriggerDeltaDiscontinuityID是完全指定还是通配符，其中“true”表示通配符。请注意，当相应的
mteTriggerSampleType is 'deltaValue'."
DEFVAL { false }
::= { mteTriggerDeltaEntry 2 }
mteTriggerSampleType is 'deltaValue'."
DEFVAL { false }
::= { mteTriggerDeltaEntry 2 }
mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE
SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value 'timeTicks' indicates the
mteTriggerDeltaDiscontinuityID of this row is of syntax
TimeTicks. The value 'timeStamp' indicates syntax TimeStamp.
The value 'dateAndTime' indicates syntax DateAndTime."
DEFVAL { timeTicks }
::= { mteTriggerDeltaEntry 3 }
mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE
SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value 'timeTicks' indicates the
mteTriggerDeltaDiscontinuityID of this row is of syntax
TimeTicks. The value 'timeStamp' indicates syntax TimeStamp.
The value 'dateAndTime' indicates syntax DateAndTime."
DEFVAL { timeTicks }
::= { mteTriggerDeltaEntry 3 }
-- -- Trigger Existence Table --
----触发器存在表--
mteTriggerExistenceTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerExistenceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information for existence
triggers."
::= { mteTrigger 4 }
mteTriggerExistenceTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerExistenceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information for existence
triggers."
::= { mteTrigger 4 }
mteTriggerExistenceEntry OBJECT-TYPE
SYNTAX MteTriggerExistenceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single existence trigger. Entries
automatically exist in this this table for each mteTriggerEntry
that has 'existence' set in mteTriggerTest."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerExistenceTable 1 }
mteTriggerExistenceEntry OBJECT-TYPE
SYNTAX MteTriggerExistenceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single existence trigger. Entries
automatically exist in this this table for each mteTriggerEntry
that has 'existence' set in mteTriggerTest."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerExistenceTable 1 }
MteTriggerExistenceEntry ::= SEQUENCE {
mteTriggerExistenceTest BITS,
mteTriggerExistenceStartup BITS,
mteTriggerExistenceObjectsOwner SnmpAdminString,
mteTriggerExistenceObjects SnmpAdminString,
mteTriggerExistenceEventOwner SnmpAdminString,
mteTriggerExistenceEvent SnmpAdminString
}
MteTriggerExistenceEntry ::= SEQUENCE {
mteTriggerExistenceTest BITS,
mteTriggerExistenceStartup BITS,
mteTriggerExistenceObjectsOwner SnmpAdminString,
mteTriggerExistenceObjects SnmpAdminString,
mteTriggerExistenceEventOwner SnmpAdminString,
mteTriggerExistenceEvent SnmpAdminString
}
mteTriggerExistenceTest OBJECT-TYPE SYNTAX BITS { present(0), absent(1), changed(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The type of existence test to perform. The trigger fires when the object at mteTriggerValueID is seen to go from present to absent, from absent to present, or to have it's value changed, depending on which tests are selected:
mteTriggerExistenceTest对象类型语法位{存在（0），不存在（1），已更改（2）}最大访问读写状态当前描述“要执行的存在性测试的类型。当mteTriggerValueID处的对象从存在变为不存在、从不存在变为存在或其值发生变化时，触发，具体取决于选择的测试：
present(0) - when this test is selected, the trigger fires when the mteTriggerValueID object goes from absent to present.
存在（0）-选择此测试时，当mteTriggerValueID对象从不存在变为存在时触发。
absent(1) - when this test is selected, the trigger fires when the mteTriggerValueID object goes from present to absent. changed(2) - when this test is selected, the trigger fires the mteTriggerValueID object value changes.
缺席（1）-选择此测试时，当mteTriggerValueID对象从存在变为不存在时触发。更改（2）-选择此测试时，触发器触发mteTriggerValueID对象值更改。
Once the trigger has fired for either presence or absence it
will not fire again for that state until the object has been
to the other state. "
DEFVAL { { present, absent } }
::= { mteTriggerExistenceEntry 1 }
Once the trigger has fired for either presence or absence it
will not fire again for that state until the object has been
to the other state. "
DEFVAL { { present, absent } }
::= { mteTriggerExistenceEntry 1 }
mteTriggerExistenceStartup OBJECT-TYPE
SYNTAX BITS { present(0), absent(1) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Control for whether an event may be triggered when this entry
is first set to 'active' and the test specified by
mteTriggerExistenceTest is true. Setting an option causes
that trigger to fire when its test is true."
DEFVAL { { present, absent } }
::= { mteTriggerExistenceEntry 2 }
mteTriggerExistenceStartup OBJECT-TYPE
SYNTAX BITS { present(0), absent(1) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Control for whether an event may be triggered when this entry
is first set to 'active' and the test specified by
mteTriggerExistenceTest is true. Setting an option causes
that trigger to fire when its test is true."
DEFVAL { { present, absent } }
::= { mteTriggerExistenceEntry 2 }
mteTriggerExistenceObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerExistenceObjects, the mteOwner of a
group of objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteTriggerExistenceEntry 3 }
mteTriggerExistenceObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerExistenceObjects, the mteOwner of a
group of objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteTriggerExistenceEntry 3 }
mteTriggerExistenceObjects OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32))
MTETriggerExistenceObject对象类型语法SnmpAdminString（大小（0..32））
MAX-ACCESS read-write STATUS current DESCRIPTION "The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger for this test.
MAX-ACCESS读写状态当前描述“mteObjectsTable中一组对象的mteObjectsName。这些对象将被添加到为此测试触发此触发器而产生的任何通知中。
A list of objects may also be added based on the overall trigger, the event or other settings in mteTriggerTest.
还可以根据mteTriggerTest中的整体触发器、事件或其他设置添加对象列表。
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteTriggerExistenceEntry 4 }
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteTriggerExistenceEntry 4 }
mteTriggerExistenceEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerExistenceEvent, the mteOwner of an event
entry from the mteEventTable."
DEFVAL { ''H }
::= { mteTriggerExistenceEntry 5 }
mteTriggerExistenceEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerExistenceEvent, the mteOwner of an event
entry from the mteEventTable."
DEFVAL { ''H }
::= { mteTriggerExistenceEntry 5 }
mteTriggerExistenceEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'existence' and this trigger fires. A length of 0 indicates no
event."
DEFVAL { ''H }
::= { mteTriggerExistenceEntry 6 }
mteTriggerExistenceEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'existence' and this trigger fires. A length of 0 indicates no
event."
DEFVAL { ''H }
::= { mteTriggerExistenceEntry 6 }
-- -- Trigger Boolean Table --
----触发器布尔表--
mteTriggerBooleanTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerBooleanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information for boolean
triggers."
::= { mteTrigger 5 }
mteTriggerBooleanTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerBooleanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information for boolean
triggers."
::= { mteTrigger 5 }
mteTriggerBooleanEntry OBJECT-TYPE
SYNTAX MteTriggerBooleanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single boolean trigger. Entries
automatically exist in this this table for each mteTriggerEntry
that has 'boolean' set in mteTriggerTest."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerBooleanTable 1 }
mteTriggerBooleanEntry OBJECT-TYPE
SYNTAX MteTriggerBooleanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single boolean trigger. Entries
automatically exist in this this table for each mteTriggerEntry
that has 'boolean' set in mteTriggerTest."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerBooleanTable 1 }
MteTriggerBooleanEntry ::= SEQUENCE {
mteTriggerBooleanComparison INTEGER,
mteTriggerBooleanValue Integer32,
mteTriggerBooleanStartup TruthValue,
mteTriggerBooleanObjectsOwner SnmpAdminString,
mteTriggerBooleanObjects SnmpAdminString,
mteTriggerBooleanEventOwner SnmpAdminString,
mteTriggerBooleanEvent SnmpAdminString
}
MteTriggerBooleanEntry ::= SEQUENCE {
mteTriggerBooleanComparison INTEGER,
mteTriggerBooleanValue Integer32,
mteTriggerBooleanStartup TruthValue,
mteTriggerBooleanObjectsOwner SnmpAdminString,
mteTriggerBooleanObjects SnmpAdminString,
mteTriggerBooleanEventOwner SnmpAdminString,
mteTriggerBooleanEvent SnmpAdminString
}
mteTriggerBooleanComparison OBJECT-TYPE SYNTAX INTEGER { unequal(1), equal(2), less(3), lessOrEqual(4), greater(5), greaterOrEqual(6) } MAX-ACCESS read-write STATUS current DESCRIPTION "The type of boolean comparison to perform.
mteTriggerBooleanComparison对象类型语法整数{不等（1）、相等（2）、小于（3）、lessOrEqual（4）、大于（5）、greaterequal（6）}MAX-ACCESS读写状态当前描述“要执行的布尔比较的类型。
The value at mteTriggerValueID is compared to
mteTriggerBooleanValue, so for example if
mteTriggerBooleanComparison is 'less' the result would be true
if the value at mteTriggerValueID is less than the value of
mteTriggerBooleanValue."
DEFVAL { unequal }
::= { mteTriggerBooleanEntry 1 }
The value at mteTriggerValueID is compared to
mteTriggerBooleanValue, so for example if
mteTriggerBooleanComparison is 'less' the result would be true
if the value at mteTriggerValueID is less than the value of
mteTriggerBooleanValue."
DEFVAL { unequal }
::= { mteTriggerBooleanEntry 1 }
mteTriggerBooleanValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value to use for the test specified by
mteTriggerBooleanTest."
DEFVAL { 0 }
::= { mteTriggerBooleanEntry 2 }
mteTriggerBooleanValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value to use for the test specified by
mteTriggerBooleanTest."
DEFVAL { 0 }
::= { mteTriggerBooleanEntry 2 }
mteTriggerBooleanStartup OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Control for whether an event may be triggered when this entry
is first set to 'active' or a new instance of the object at
mteTriggerValueID is found and the test specified by
mteTriggerBooleanComparison is true. In that case an event is
triggered if mteTriggerBooleanStartup is 'true'."
DEFVAL { true }
::= { mteTriggerBooleanEntry 3 }
mteTriggerBooleanStartup OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Control for whether an event may be triggered when this entry
is first set to 'active' or a new instance of the object at
mteTriggerValueID is found and the test specified by
mteTriggerBooleanComparison is true. In that case an event is
triggered if mteTriggerBooleanStartup is 'true'."
DEFVAL { true }
::= { mteTriggerBooleanEntry 3 }
mteTriggerBooleanObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerBooleanObjects, the mteOwner of a group
of objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteTriggerBooleanEntry 4 }
mteTriggerBooleanObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerBooleanObjects, the mteOwner of a group
of objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteTriggerBooleanEntry 4 }
mteTriggerBooleanObjects OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger for this test.
mteTriggerBooleanObjects对象类型语法SNMPAdministring（大小（0..32））MAX-ACCESS读写状态当前描述“mteObjectsTable中一组对象的mteObjectsName。这些对象将添加到为此测试触发此触发器所产生的任何通知中。
A list of objects may also be added based on the overall trigger, the event or other settings in mteTriggerTest.
还可以根据mteTriggerTest中的整体触发器、事件或其他设置添加对象列表。
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteTriggerBooleanEntry 5 }
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteTriggerBooleanEntry 5 }
mteTriggerBooleanEventOwner OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "To go with mteTriggerBooleanEvent, the mteOwner of an event entry from mteEventTable." DEFVAL { ''H }
mteTriggerBooleanEventOwner对象类型语法SnmpAdminString（大小（0..32））MAX-ACCESS读写状态当前描述“与mteTriggerBooleanEvent一起使用，mteEventTable中事件项的mteOwner。”deffal{“H}
::= { mteTriggerBooleanEntry 6 }
::= { mteTriggerBooleanEntry 6 }
mteTriggerBooleanEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'boolean' and this trigger fires. A length of 0 indicates no
event."
DEFVAL { ''H }
::= { mteTriggerBooleanEntry 7 }
mteTriggerBooleanEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'boolean' and this trigger fires. A length of 0 indicates no
event."
DEFVAL { ''H }
::= { mteTriggerBooleanEntry 7 }
-- -- Trigger Threshold Table --
----触发阈值表--
mteTriggerThresholdTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerThresholdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information for threshold
triggers."
::= { mteTrigger 6 }
mteTriggerThresholdTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerThresholdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event trigger information for threshold
triggers."
::= { mteTrigger 6 }
mteTriggerThresholdEntry OBJECT-TYPE
SYNTAX MteTriggerThresholdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single threshold trigger. Entries
automatically exist in this table for each mteTriggerEntry
that has 'threshold' set in mteTriggerTest."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerThresholdTable 1 }
mteTriggerThresholdEntry OBJECT-TYPE
SYNTAX MteTriggerThresholdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single threshold trigger. Entries
automatically exist in this table for each mteTriggerEntry
that has 'threshold' set in mteTriggerTest."
INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerThresholdTable 1 }
MteTriggerThresholdEntry ::= SEQUENCE {
mteTriggerThresholdStartup INTEGER,
mteTriggerThresholdRising Integer32,
mteTriggerThresholdFalling Integer32,
mteTriggerThresholdDeltaRising Integer32,
mteTriggerThresholdDeltaFalling Integer32,
mteTriggerThresholdObjectsOwner SnmpAdminString,
mteTriggerThresholdObjects SnmpAdminString,
mteTriggerThresholdRisingEventOwner SnmpAdminString,
mteTriggerThresholdRisingEvent SnmpAdminString,
mteTriggerThresholdFallingEventOwner SnmpAdminString,
MteTriggerThresholdEntry ::= SEQUENCE {
mteTriggerThresholdStartup INTEGER,
mteTriggerThresholdRising Integer32,
mteTriggerThresholdFalling Integer32,
mteTriggerThresholdDeltaRising Integer32,
mteTriggerThresholdDeltaFalling Integer32,
mteTriggerThresholdObjectsOwner SnmpAdminString,
mteTriggerThresholdObjects SnmpAdminString,
mteTriggerThresholdRisingEventOwner SnmpAdminString,
mteTriggerThresholdRisingEvent SnmpAdminString,
mteTriggerThresholdFallingEventOwner SnmpAdminString,
mteTriggerThresholdFallingEvent SnmpAdminString, mteTriggerThresholdDeltaRisingEventOwner SnmpAdminString, mteTriggerThresholdDeltaRisingEvent SnmpAdminString, mteTriggerThresholdDeltaFallingEventOwner SnmpAdminString, mteTriggerThresholdDeltaFallingEvent SnmpAdminString }
mteTriggerThresholdDeltaRisingEvent SNMPAdministring，mteTriggerThresholdDeltaRisingEvent SNMPAdministring，mteTriggerThresholdDeltaFallingEvent所有者SNMPAdministring，mteTriggerThresholdDeltaFallingEvent SNMPAdministring}
mteTriggerThresholdStartup OBJECT-TYPE
SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The event that may be triggered when this entry is first
set to 'active' and a new instance of the object at
mteTriggerValueID is found. If the first sample after this
instance becomes active is greater than or equal to
mteTriggerThresholdRising and mteTriggerThresholdStartup is
equal to 'rising' or 'risingOrFalling', then one
mteTriggerThresholdRisingEvent is triggered for that instance.
If the first sample after this entry becomes active is less
than or equal to mteTriggerThresholdFalling and
mteTriggerThresholdStartup is equal to 'falling' or
'risingOrFalling', then one mteTriggerThresholdRisingEvent is
triggered for that instance."
DEFVAL { risingOrFalling }
::= { mteTriggerThresholdEntry 1 }
mteTriggerThresholdStartup OBJECT-TYPE
SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The event that may be triggered when this entry is first
set to 'active' and a new instance of the object at
mteTriggerValueID is found. If the first sample after this
instance becomes active is greater than or equal to
mteTriggerThresholdRising and mteTriggerThresholdStartup is
equal to 'rising' or 'risingOrFalling', then one
mteTriggerThresholdRisingEvent is triggered for that instance.
If the first sample after this entry becomes active is less
than or equal to mteTriggerThresholdFalling and
mteTriggerThresholdStartup is equal to 'falling' or
'risingOrFalling', then one mteTriggerThresholdRisingEvent is
triggered for that instance."
DEFVAL { risingOrFalling }
::= { mteTriggerThresholdEntry 1 }
mteTriggerThresholdRising OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "A threshold value to check against if mteTriggerType is 'threshold'.
mteTriggerThresholdRising对象类型语法整数32 MAX-ACCESS读写状态当前描述“检查mteTriggerType是否为‘阈值’的阈值”。
When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, one mteTriggerThresholdRisingEvent is triggered. That event is also triggered if the first sample after this entry becomes active is greater than or equal to this threshold and mteTriggerThresholdStartup is equal to 'rising' or 'risingOrFalling'.
当当前采样值大于或等于此阈值，且上次采样间隔的值小于此阈值时，将触发一个mteTriggerThresholdRisingEvent。如果此条目变为活动状态后的第一个样本大于或等于此阈值，并且mteTriggerThresholdStartup等于“上升”或“上升”或“下降”，则也会触发该事件。
After a rising event is generated, another such event is not triggered until the sampled value falls below this threshold and reaches mteTriggerThresholdFalling." DEFVAL { 0 }
生成上升事件后，直到采样值低于此阈值并达到mteTriggerThresholdFalling。“DEFVAL{0}
::= { mteTriggerThresholdEntry 2 }
::= { mteTriggerThresholdEntry 2 }
mteTriggerThresholdFalling OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "A threshold value to check against if mteTriggerType is 'threshold'.
mteTriggerThresholdFalling对象类型语法整数32 MAX-ACCESS读写状态当前描述“检查mteTriggerType是否为‘阈值’的阈值”。
When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, one mteTriggerThresholdFallingEvent is triggered. That event is also triggered if the first sample after this entry becomes active is less than or equal to this threshold and mteTriggerThresholdStartup is equal to 'falling' or 'risingOrFalling'.
当当前采样值小于或等于此阈值，且上一个采样间隔的值大于此阈值时，将触发一个mteTriggerThresholdFallingEvent。如果此条目变为活动状态后的第一个样本小于或等于此阈值，并且mteTriggerThresholdStartup等于“下降”或“上升”或“下降”，则也会触发该事件。
After a falling event is generated, another such event is not
triggered until the sampled value rises above this threshold
and reaches mteTriggerThresholdRising."
DEFVAL { 0 }
::= { mteTriggerThresholdEntry 3 }
After a falling event is generated, another such event is not
triggered until the sampled value rises above this threshold
and reaches mteTriggerThresholdRising."
DEFVAL { 0 }
::= { mteTriggerThresholdEntry 3 }
mteTriggerThresholdDeltaRising OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "A threshold value to check against if mteTriggerType is 'threshold'.
mteTriggerThresholdDeltaRising对象类型语法整数32 MAX-ACCESS读写状态当前描述“检查mteTriggerType是否为‘阈值’的阈值”。
When the delta value (difference) between the current sampled value (value(n)) and the previous sampled value (value(n-1)) is greater than or equal to this threshold, and the delta value calculated at the last sampling interval (i.e. value(n-1) - value(n-2)) was less than this threshold, one mteTriggerThresholdDeltaRisingEvent is triggered. That event is also triggered if the first delta value calculated after this entry becomes active, i.e. value(2) - value(1), where value(1) is the first sample taken of that instance, is greater than or equal to this threshold.
当当前采样值（值（n））和上一个采样值（值（n-1））之间的增量值（差）大于或等于此阈值，并且在最后一个采样间隔（即值（n-1）-值（n-2））计算的增量值小于此阈值时，触发一个mttTriggerThresholdDeltarIsingEvent。如果此条目激活后计算的第一个增量值（即值（2）-值（1）（其中值（1）是该实例的第一个采样）大于或等于此阈值，则也会触发该事件。
After a rising event is generated, another such event is not triggered until the delta value falls below this threshold and reaches mteTriggerThresholdDeltaFalling." DEFVAL { 0 }
生成上升事件后，直到增量值低于此阈值并达到mteTriggerThresholdDeltaFalling。“DEFVAL{0}
::= { mteTriggerThresholdEntry 4 }
::= { mteTriggerThresholdEntry 4 }
mteTriggerThresholdDeltaFalling OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "A threshold value to check against if mteTriggerType is 'threshold'.
mteTriggerThresholdDeltaFalling对象类型语法整数32 MAX-ACCESS读写状态当前描述“检查mteTriggerType是否为“阈值”的阈值”。
When the delta value (difference) between the current sampled value (value(n)) and the previous sampled value (value(n-1)) is less than or equal to this threshold, and the delta value calculated at the last sampling interval (i.e. value(n-1) - value(n-2)) was greater than this threshold, one mteTriggerThresholdDeltaFallingEvent is triggered. That event is also triggered if the first delta value calculated after this entry becomes active, i.e. value(2) - value(1), where value(1) is the first sample taken of that instance, is less than or equal to this threshold.
当当前采样值（值（n））和上一个采样值（值（n-1））之间的增量值（差）小于或等于此阈值，并且在最后一个采样间隔（即值（n-1）-值（n-2））计算的增量值大于此阈值时，将触发一个mttTriggerThresholdDeltaFallingEvent。如果此条目激活后计算的第一个增量值（即值（2）-值（1）（其中值（1）是该实例的第一个样本）小于或等于此阈值，则也会触发该事件。
After a falling event is generated, another such event is not
triggered until the delta value falls below this threshold and
reaches mteTriggerThresholdDeltaRising."
DEFVAL { 0 }
::= { mteTriggerThresholdEntry 5 }
After a falling event is generated, another such event is not
triggered until the delta value falls below this threshold and
reaches mteTriggerThresholdDeltaRising."
DEFVAL { 0 }
::= { mteTriggerThresholdEntry 5 }
mteTriggerThresholdObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdObjects, the mteOwner of a group
of objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 6 }
mteTriggerThresholdObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdObjects, the mteOwner of a group
of objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 6 }
mteTriggerThresholdObjects OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger for this test.
mteTriggerThresholdObjects对象类型语法SNMPAdministring（大小（0..32））MAX-ACCESS读写状态当前描述“mteObjectsTable中一组对象的mteObjectsName。这些对象将添加到为此测试触发此触发器所产生的任何通知中。
A list of objects may also be added based on the overall
还可以根据总体布局添加对象列表
trigger, the event or other settings in mteTriggerTest.
触发器、事件或mteTriggerTest中的其他设置。
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 7 }
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 7 }
mteTriggerThresholdRisingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdRisingEvent, the mteOwner of an
event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 8 }
mteTriggerThresholdRisingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdRisingEvent, the mteOwner of an
event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 8 }
mteTriggerThresholdRisingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdRising. A length of 0 indicates no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 9 }
mteTriggerThresholdRisingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdRising. A length of 0 indicates no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 9 }
mteTriggerThresholdFallingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdFallingEvent, the mteOwner of an
event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 10 }
mteTriggerThresholdFallingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdFallingEvent, the mteOwner of an
event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 10 }
mteTriggerThresholdFallingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdFalling. A length of 0 indicates no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 11 }
mteTriggerThresholdFallingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdFalling. A length of 0 indicates no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 11 }
mteTriggerThresholdDeltaRisingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner
of an event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 12 }
mteTriggerThresholdDeltaRisingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner
of an event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 12 }
mteTriggerThresholdDeltaRisingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdDeltaRising. A length of 0 indicates
no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 13 }
mteTriggerThresholdDeltaRisingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdDeltaRising. A length of 0 indicates
no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 13 }
mteTriggerThresholdDeltaFallingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner
of an event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 14 }
mteTriggerThresholdDeltaFallingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner
of an event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 14 }
mteTriggerThresholdDeltaFallingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdDeltaFalling. A length of 0 indicates
no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 15 }
mteTriggerThresholdDeltaFallingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdDeltaFalling. A length of 0 indicates
no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 15 }
-- -- Objects Table --
----对象表--
mteObjectsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteObjectsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that can be added to notifications based
on the trigger, trigger test, or event, as pointed to by
entries in those tables."
::= { mteObjects 1 }
mteObjectsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteObjectsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that can be added to notifications based
on the trigger, trigger test, or event, as pointed to by
entries in those tables."
::= { mteObjects 1 }
mteObjectsEntry OBJECT-TYPE SYNTAX MteObjectsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A group of objects. Applications create and delete entries using mteObjectsEntryStatus.
mteObjectsEntry对象类型语法mteObjectsEntry MAX-ACCESS不可访问状态当前描述“一组对象。应用程序使用mteObjectsEntryStatus创建和删除条目。
When adding objects to a notification they are added in the
lexical order of their index in this table. Those associated
with a trigger come first, then trigger test, then event."
INDEX { mteOwner, mteObjectsName, mteObjectsIndex }
::= { mteObjectsTable 1 }
When adding objects to a notification they are added in the
lexical order of their index in this table. Those associated
with a trigger come first, then trigger test, then event."
INDEX { mteOwner, mteObjectsName, mteObjectsIndex }
::= { mteObjectsTable 1 }
MteObjectsEntry ::= SEQUENCE {
mteObjectsName SnmpAdminString,
mteObjectsIndex Unsigned32,
mteObjectsID OBJECT IDENTIFIER,
mteObjectsIDWildcard TruthValue,
mteObjectsEntryStatus RowStatus
}
MteObjectsEntry ::= SEQUENCE {
mteObjectsName SnmpAdminString,
mteObjectsIndex Unsigned32,
mteObjectsID OBJECT IDENTIFIER,
mteObjectsIDWildcard TruthValue,
mteObjectsEntryStatus RowStatus
}
mteObjectsName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A locally-unique, administratively assigned name for a group
of objects."
::= { mteObjectsEntry 1 }
mteObjectsName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A locally-unique, administratively assigned name for a group
of objects."
::= { mteObjectsEntry 1 }
mteObjectsIndex OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An arbitrary integer for the purpose of identifying individual objects within a mteObjectsName group.
mteObjectsIndex对象类型语法Unsigned32（1..4294967295）MAX-ACCESS不可访问状态当前描述“用于标识mteObjectsName组中单个对象的任意整数。
Objects within a group are placed in the notification in the numerical order of this index.
组中的对象按此索引的数字顺序放置在通知中。
Groups are placed in the notification in the order of the selections for overall trigger, trigger test, and event. Within trigger test they are in the same order as the numerical values of the bits defined for mteTriggerTest.
组按总体触发器、触发器测试和事件的选择顺序放置在通知中。在触发器测试中，它们的顺序与为mteTriggerTest定义的位的数值相同。
Bad object identifiers or a mismatch between truncating the
identifier and the value of mteDeltaDiscontinuityIDWildcard
result in operation as one would expect when providing the
wrong identifier to a Get operation. The Get will fail or get
the wrong object. If the object is not available it is omitted
from the notification."
::= { mteObjectsEntry 2 }
Bad object identifiers or a mismatch between truncating the
identifier and the value of mteDeltaDiscontinuityIDWildcard
result in operation as one would expect when providing the
wrong identifier to a Get operation. The Get will fail or get
the wrong object. If the object is not available it is omitted
from the notification."
::= { mteObjectsEntry 2 }
mteObjectsID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The object identifier of a MIB object to add to a Notification that results from the firing of a trigger.
mteObjectsID对象类型语法对象标识符MAX-ACCESS read create STATUS current DESCRIPTION“要添加到触发触发器后的通知中的MIB对象的对象标识符。
This may be wildcarded by truncating all or part of the instance portion, in which case the instance portion of the OID for obtaining this object will be the same as that used in obtaining the mteTriggerValueID that fired. If such wildcarding is applied, mteObjectsIDWildcard must be 'true' and if not it must be 'false'.
这可以通过截断全部或部分实例部分进行通配符，在这种情况下，用于获取此对象的OID实例部分将与用于获取触发的mteTriggerValueID的实例部分相同。如果应用了此类通配符，则mteObjectsIDWildcard必须为“true”，否则必须为“false”。
Each instance that fills the wildcard is independent of any
additional instances, that is, wildcarded objects operate
as if there were a separate table entry for each instance
that fills the wildcard without having to actually predict
all possible instances ahead of time."
DEFVAL { zeroDotZero }
::= { mteObjectsEntry 3 }
Each instance that fills the wildcard is independent of any
additional instances, that is, wildcarded objects operate
as if there were a separate table entry for each instance
that fills the wildcard without having to actually predict
all possible instances ahead of time."
DEFVAL { zeroDotZero }
::= { mteObjectsEntry 3 }
mteObjectsIDWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control for whether mteObjectsID is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard."
DEFVAL { false }
::= { mteObjectsEntry 4 }
mteObjectsIDWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control for whether mteObjectsID is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard."
DEFVAL { false }
::= { mteObjectsEntry 4 }
mteObjectsEntryStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The control that allows creation and deletion of entries.
Once made active an entry MAY not be modified except to
delete it."
::= { mteObjectsEntry 5 }
mteObjectsEntryStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The control that allows creation and deletion of entries.
Once made active an entry MAY not be modified except to
delete it."
::= { mteObjectsEntry 5 }
-- -- Event Section --
----活动部分--
-- Counters
--计数器
mteEventFailures OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an attempt to invoke an event
has failed. This counts individually for each
attempt in a group of targets or each attempt for a
wildcarded trigger object."
::= { mteEvent 1 }
mteEventFailures OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times an attempt to invoke an event
has failed. This counts individually for each
attempt in a group of targets or each attempt for a
wildcarded trigger object."
::= { mteEvent 1 }
-- -- Event Table --
----事件表--
mteEventTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event action information."
::= { mteEvent 2 }
mteEventTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event action information."
::= { mteEvent 2 }
mteEventEntry OBJECT-TYPE
SYNTAX MteEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single event. Applications create and
delete entries using mteEventEntryStatus."
INDEX { mteOwner, IMPLIED mteEventName }
::= { mteEventTable 1 }
mteEventEntry OBJECT-TYPE
SYNTAX MteEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single event. Applications create and
delete entries using mteEventEntryStatus."
INDEX { mteOwner, IMPLIED mteEventName }
::= { mteEventTable 1 }
MteEventEntry ::= SEQUENCE {
mteEventName SnmpAdminString,
mteEventComment SnmpAdminString,
mteEventActions BITS,
mteEventEnabled TruthValue,
mteEventEntryStatus RowStatus
}
MteEventEntry ::= SEQUENCE {
mteEventName SnmpAdminString,
mteEventComment SnmpAdminString,
mteEventActions BITS,
mteEventEnabled TruthValue,
mteEventEntryStatus RowStatus
}
mteEventName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A locally-unique, administratively assigned name for the
event."
::= { mteEventEntry 1 }
mteEventName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A locally-unique, administratively assigned name for the
event."
::= { mteEventEntry 1 }
mteEventComment OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A description of the event's function and use."
DEFVAL { ''H }
::= { mteEventEntry 2 }
mteEventComment OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A description of the event's function and use."
DEFVAL { ''H }
::= { mteEventEntry 2 }
mteEventActions OBJECT-TYPE SYNTAX BITS { notification(0), set(1) } MAX-ACCESS read-create STATUS current DESCRIPTION "The actions to perform when this event occurs.
mteEventActions对象类型语法位{notification（0），set（1）}MAX-ACCESS read create STATUS current DESCRIPTION“发生此事件时要执行的操作。
For 'notification', Traps and/or Informs are sent according to the configuration in the SNMP Notification MIB.
对于“通知”，根据SNMP通知MIB中的配置发送陷阱和/或通知。
For 'set', an SNMP Set operation is performed according to
control values in this entry."
DEFVAL { {} } -- No bits set.
::= { mteEventEntry 3 }
For 'set', an SNMP Set operation is performed according to
control values in this entry."
DEFVAL { {} } -- No bits set.
::= { mteEventEntry 3 }
mteEventEnabled OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "A control to allow an event to be configured but not used. When the value is 'false' the event does not execute even if
MTEEventenEnabled对象类型语法TruthValue MAX-ACCESS read create STATUS current DESCRIPTION“允许配置但不使用事件的控件。当值为“false”时，即使
triggered."
DEFVAL { false }
::= { mteEventEntry 4 }
triggered."
DEFVAL { false }
::= { mteEventEntry 4 }
mteEventEntryStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The control that allows creation and deletion of entries.
Once made active an entry MAY not be modified except to
delete it."
::= { mteEventEntry 5 }
mteEventEntryStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The control that allows creation and deletion of entries.
Once made active an entry MAY not be modified except to
delete it."
::= { mteEventEntry 5 }
-- -- Event Notification Table --
----事件通知表--
mteEventNotificationTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteEventNotificationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of information about notifications to be sent as a
consequence of management events."
::= { mteEvent 3 }
mteEventNotificationTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteEventNotificationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of information about notifications to be sent as a
consequence of management events."
::= { mteEvent 3 }
mteEventNotificationEntry OBJECT-TYPE
SYNTAX MteEventNotificationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single event's notification. Entries
automatically exist in this this table for each mteEventEntry
that has 'notification' set in mteEventActions."
INDEX { mteOwner, IMPLIED mteEventName }
::= { mteEventNotificationTable 1 }
mteEventNotificationEntry OBJECT-TYPE
SYNTAX MteEventNotificationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a single event's notification. Entries
automatically exist in this this table for each mteEventEntry
that has 'notification' set in mteEventActions."
INDEX { mteOwner, IMPLIED mteEventName }
::= { mteEventNotificationTable 1 }
MteEventNotificationEntry ::= SEQUENCE {
mteEventNotification OBJECT IDENTIFIER,
mteEventNotificationObjectsOwner SnmpAdminString,
mteEventNotificationObjects SnmpAdminString
}
MteEventNotificationEntry ::= SEQUENCE {
mteEventNotification OBJECT IDENTIFIER,
mteEventNotificationObjectsOwner SnmpAdminString,
mteEventNotificationObjects SnmpAdminString
}
mteEventNotification OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS current
mteEventNotification对象类型语法对象标识符最大访问读写状态当前
DESCRIPTION
"The object identifier from the NOTIFICATION-TYPE for the
notification to use if metEventActions has 'notification' set."
DEFVAL { zeroDotZero }
::= { mteEventNotificationEntry 1 }
DESCRIPTION
"The object identifier from the NOTIFICATION-TYPE for the
notification to use if metEventActions has 'notification' set."
DEFVAL { zeroDotZero }
::= { mteEventNotificationEntry 1 }
mteEventNotificationObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteEventNotificationObjects, the mteOwner of a
group of objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteEventNotificationEntry 2 }
mteEventNotificationObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteEventNotificationObjects, the mteOwner of a
group of objects from mteObjectsTable."
DEFVAL { ''H }
::= { mteEventNotificationEntry 2 }
mteEventNotificationObjects OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "The mteObjectsName of a group of objects from mteObjectsTable if mteEventActions has 'notification' set. These objects are to be added to any Notification generated by this event.
mteEventNotificationObjects对象类型语法SNMPAdministring（大小（0..32））MAX-ACCESS读写状态当前描述“如果mteEventActions设置了“通知”，则mteObjectsTable中一组对象的mteObjectsName。这些对象将添加到此事件生成的任何通知中。
Objects may also be added based on the trigger that stimulated the event.
还可以根据触发事件的触发器添加对象。
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteEventNotificationEntry 3 }
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteEventNotificationEntry 3 }
-- -- Event Set Table --
----事件集表--
mteEventSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteEventSetEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event action information."
::= { mteEvent 4 }
mteEventSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteEventSetEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of management event action information."
::= { mteEvent 4 }
mteEventSetEntry OBJECT-TYPE SYNTAX MteEventSetEntry MAX-ACCESS not-accessible
mteEventSetEntry对象类型语法mteEventSetEntry MAX-ACCESS不可访问
STATUS current
DESCRIPTION
"Information about a single event's set option. Entries
automatically exist in this this table for each mteEventEntry
that has 'set' set in mteEventActions."
INDEX { mteOwner, IMPLIED mteEventName }
::= { mteEventSetTable 1 }
STATUS current
DESCRIPTION
"Information about a single event's set option. Entries
automatically exist in this this table for each mteEventEntry
that has 'set' set in mteEventActions."
INDEX { mteOwner, IMPLIED mteEventName }
::= { mteEventSetTable 1 }
MteEventSetEntry ::= SEQUENCE {
mteEventSetObject OBJECT IDENTIFIER,
mteEventSetObjectWildcard TruthValue,
mteEventSetValue Integer32,
mteEventSetTargetTag SnmpTagValue,
mteEventSetContextName SnmpAdminString,
mteEventSetContextNameWildcard TruthValue
}
MteEventSetEntry ::= SEQUENCE {
mteEventSetObject OBJECT IDENTIFIER,
mteEventSetObjectWildcard TruthValue,
mteEventSetValue Integer32,
mteEventSetTargetTag SnmpTagValue,
mteEventSetContextName SnmpAdminString,
mteEventSetContextNameWildcard TruthValue
}
mteEventSetObject OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS current DESCRIPTION "The object identifier from the MIB object to set if mteEventActions has 'set' set.
mteEventSetObject对象类型语法对象标识符MAX-ACCESS读写状态当前描述“如果mteEventActions已设置“set”，则MIB对象中要设置的对象标识符。
This object identifier may be wildcarded by leaving sub-identifiers off the end, in which case nteEventSetObjectWildCard must be 'true'.
可以通过将子标识符保留在末尾来对该对象标识符进行通配符，在这种情况下，NTEventSetObjectWildcard必须为“true”。
If mteEventSetObject is wildcarded the instance used to set the object to which it points is the same as the instance from the value of mteTriggerValueID that triggered the event.
如果mteEventSetObject为通配符，则用于设置其指向的对象的实例与触发事件的mteTriggerValueID值中的实例相同。
Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time.
填充通配符的每个实例都独立于任何其他实例，也就是说，通配符对象的操作就像每个实例都有一个单独的表条目填充通配符一样，而不必提前实际预测所有可能的实例。
Bad object identifiers or a mismatch between truncating the
identifier and the value of mteSetObjectWildcard
result in operation as one would expect when providing the
wrong identifier to a Set operation. The Set will fail or set
the wrong object. If the value syntax of the destination
object is not correct, the Set fails with the normal SNMP
error code."
DEFVAL { zeroDotZero }
::= { mteEventSetEntry 1 }
Bad object identifiers or a mismatch between truncating the
identifier and the value of mteSetObjectWildcard
result in operation as one would expect when providing the
wrong identifier to a Set operation. The Set will fail or set
the wrong object. If the value syntax of the destination
object is not correct, the Set fails with the normal SNMP
error code."
DEFVAL { zeroDotZero }
::= { mteEventSetEntry 1 }
mteEventSetObjectWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Control over whether mteEventSetObject is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard
if mteEventActions has 'set' set."
DEFVAL { false }
::= { mteEventSetEntry 2 }
mteEventSetObjectWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Control over whether mteEventSetObject is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard
if mteEventActions has 'set' set."
DEFVAL { false }
::= { mteEventSetEntry 2 }
mteEventSetValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value to which to set the object at mteEventSetObject
if mteEventActions has 'set' set."
DEFVAL { 0 }
::= { mteEventSetEntry 3 }
mteEventSetValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value to which to set the object at mteEventSetObject
if mteEventActions has 'set' set."
DEFVAL { 0 }
::= { mteEventSetEntry 3 }
mteEventSetTargetTag OBJECT-TYPE SYNTAX SnmpTagValue MAX-ACCESS read-write STATUS current DESCRIPTION "The tag for the target(s) at which to set the object at mteEventSetObject to mteEventSetValue if mteEventActions has 'set' set.
mteEventSetTargetTag对象类型语法SnmpTagValue MAX-ACCESS读写状态当前描述“如果mteEventActions已设置“set”，则要将mteEventSetObject设置为mteEventSetValue的目标的标记。
Systems limited to self management MAY reject a non-zero length for the value of this object.
仅限于自我管理的系统可能会拒绝此对象值的非零长度。
A length of 0 indicates the local system. In this case, access to the objects indicated by mteEventSetObject is under the security credentials of the requester that set mteTriggerEntryStatus to 'active'. Those credentials are the input parameters for isAccessAllowed from the Architecture for Describing SNMP Management Frameworks.
长度为0表示本地系统。在这种情况下，对mteEventSetObject指示的对象的访问是在将mtetriggentrystatus设置为“活动”的请求者的安全凭据下进行的。这些凭据是从用于描述SNMP管理框架的体系结构中允许的ISACCESS的输入参数。
Otherwise access rights are checked according to the security
parameters resulting from the tag."
DEFVAL { ''H }
::= { mteEventSetEntry 4 }
Otherwise access rights are checked according to the security
parameters resulting from the tag."
DEFVAL { ''H }
::= { mteEventSetEntry 4 }
mteEventSetContextName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write
mteEventSetContextName对象类型语法SNMPAdministring MAX-ACCESS读写
STATUS current DESCRIPTION "The management context in which to set mteEventObjectID. if mteEventActions has 'set' set.
STATUS current DESCRIPTION“要在其中设置mteEventObjectID的管理上下文。如果mteEventActions已设置“set”。
This may be wildcarded by leaving characters off the end. To indicate such wildcarding mteEventSetContextNameWildcard must be 'true'.
这可以通过在末尾保留字符来进行通配符。要指示此类通配符，mteEventSetContextNameWildcard必须为“true”。
If this context name is wildcarded the value used to complete
the wildcarding of mteTriggerContextName will be appended."
DEFVAL { ''H }
::= { mteEventSetEntry 5 }
If this context name is wildcarded the value used to complete
the wildcarding of mteTriggerContextName will be appended."
DEFVAL { ''H }
::= { mteEventSetEntry 5 }
mteEventSetContextNameWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Control for whether mteEventSetContextName is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard
if mteEventActions has 'set' set."
DEFVAL { false }
::= { mteEventSetEntry 6 }
mteEventSetContextNameWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Control for whether mteEventSetContextName is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard
if mteEventActions has 'set' set."
DEFVAL { false }
::= { mteEventSetEntry 6 }
-- -- Notifications --
----通知--
dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::=
{ dismanEventMIB 2 }
dismanEventMIBNotifications OBJECT IDENTIFIER ::=
{ dismanEventMIBNotificationPrefix 0 }
dismanEventMIBNotificationObjects OBJECT IDENTIFIER
::= { dismanEventMIBNotificationPrefix 1 }
dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::=
{ dismanEventMIB 2 }
dismanEventMIBNotifications OBJECT IDENTIFIER ::=
{ dismanEventMIBNotificationPrefix 0 }
dismanEventMIBNotificationObjects OBJECT IDENTIFIER
::= { dismanEventMIBNotificationPrefix 1 }
-- -- Notification Objects --
----通知对象--
mteHotTrigger OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The name of the trigger causing the notification."
::= { dismanEventMIBNotificationObjects 1 }
mteHotTrigger OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The name of the trigger causing the notification."
::= { dismanEventMIBNotificationObjects 1 }
mteHotTargetName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The SNMP Target MIB's snmpTargetAddrName related to the
notification."
::= { dismanEventMIBNotificationObjects 2 }
mteHotTargetName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The SNMP Target MIB's snmpTargetAddrName related to the
notification."
::= { dismanEventMIBNotificationObjects 2 }
mteHotContextName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The context name related to the notification. This MUST be as
fully-qualified as possible, including filling in wildcard
information determined in processing."
::= { dismanEventMIBNotificationObjects 3 }
mteHotContextName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The context name related to the notification. This MUST be as
fully-qualified as possible, including filling in wildcard
information determined in processing."
::= { dismanEventMIBNotificationObjects 3 }
mteHotOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The object identifier of the destination object related to the notification. This MUST be as fully-qualified as possible, including filling in wildcard information determined in processing.
mteHotOID对象类型语法对象标识符MAX-ACCESS可用于通知状态当前描述“与通知相关的目标对象的对象标识符。这必须尽可能完全限定，包括填写在处理过程中确定的通配符信息。
For a trigger-related notification this is from mteTriggerValueID.
对于与触发器相关的通知，这来自mteTriggerValueID。
For a set failure this is from mteEventSetObject."
::= { dismanEventMIBNotificationObjects 4 }
For a set failure this is from mteEventSetObject."
::= { dismanEventMIBNotificationObjects 4 }
mteHotValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The value of the object at mteTriggerValueID when a
trigger fired."
::= { dismanEventMIBNotificationObjects 5 }
mteHotValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The value of the object at mteTriggerValueID when a
trigger fired."
::= { dismanEventMIBNotificationObjects 5 }
mteFailedReason OBJECT-TYPE SYNTAX FailureReason MAX-ACCESS accessible-for-notify STATUS current
mteFailedReason对象类型语法故障原因MAX-ACCESS可访问当前通知状态
DESCRIPTION
"The reason for the failure of an attempt to check for a
trigger condition or set an object in response to an event."
::= { dismanEventMIBNotificationObjects 6 }
DESCRIPTION
"The reason for the failure of an attempt to check for a
trigger condition or set an object in response to an event."
::= { dismanEventMIBNotificationObjects 6 }
-- -- Notifications --
----通知--
mteTriggerFired NOTIFICATION-TYPE
OBJECTS { mteHotTrigger,
mteHotTargetName,
mteHotContextName,
mteHotOID,
mteHotValue }
STATUS current
DESCRIPTION
"Notification that the trigger indicated by the object
instances has fired, for triggers with mteTriggerType
'boolean' or 'existence'."
::= { dismanEventMIBNotifications 1 }
mteTriggerFired NOTIFICATION-TYPE
OBJECTS { mteHotTrigger,
mteHotTargetName,
mteHotContextName,
mteHotOID,
mteHotValue }
STATUS current
DESCRIPTION
"Notification that the trigger indicated by the object
instances has fired, for triggers with mteTriggerType
'boolean' or 'existence'."
::= { dismanEventMIBNotifications 1 }
mteTriggerRising NOTIFICATION-TYPE
OBJECTS { mteHotTrigger,
mteHotTargetName,
mteHotContextName,
mteHotOID,
mteHotValue }
STATUS current
DESCRIPTION
"Notification that the rising threshold was met for triggers
with mteTriggerType 'threshold'."
::= { dismanEventMIBNotifications 2 }
mteTriggerRising NOTIFICATION-TYPE
OBJECTS { mteHotTrigger,
mteHotTargetName,
mteHotContextName,
mteHotOID,
mteHotValue }
STATUS current
DESCRIPTION
"Notification that the rising threshold was met for triggers
with mteTriggerType 'threshold'."
::= { dismanEventMIBNotifications 2 }
mteTriggerFalling NOTIFICATION-TYPE
OBJECTS { mteHotTrigger,
mteHotTargetName,
mteHotContextName,
mteHotOID,
mteHotValue }
STATUS current
DESCRIPTION
"Notification that the falling threshold was met for triggers
with mteTriggerType 'threshold'."
::= { dismanEventMIBNotifications 3 }
mteTriggerFalling NOTIFICATION-TYPE
OBJECTS { mteHotTrigger,
mteHotTargetName,
mteHotContextName,
mteHotOID,
mteHotValue }
STATUS current
DESCRIPTION
"Notification that the falling threshold was met for triggers
with mteTriggerType 'threshold'."
::= { dismanEventMIBNotifications 3 }
mteTriggerFailure NOTIFICATION-TYPE OBJECTS { mteHotTrigger,
MTETrigger失败通知类型对象{mteHotTrigger，
mteHotTargetName, mteHotContextName, mteHotOID, mteFailedReason } STATUS current DESCRIPTION "Notification that an attempt to check a trigger has failed.
mteHotTargetName、mteHotContextName、mteHotOID、mteFailedReason}状态当前描述“尝试检查触发器失败的通知。
The network manager must enable this notification only with
a certain fear and trembling, as it can easily crowd out more
important information. It should be used only to help diagnose
a problem that has appeared in the error counters and can not
be found otherwise."
::= { dismanEventMIBNotifications 4 }
The network manager must enable this notification only with
a certain fear and trembling, as it can easily crowd out more
important information. It should be used only to help diagnose
a problem that has appeared in the error counters and can not
be found otherwise."
::= { dismanEventMIBNotifications 4 }
mteEventSetFailure NOTIFICATION-TYPE OBJECTS { mteHotTrigger, mteHotTargetName, mteHotContextName, mteHotOID, mteFailedReason } STATUS current DESCRIPTION "Notification that an attempt to do a set in response to an event has failed.
mteEventSetFailure NOTIFICATION-TYPE对象{mteHotTrigger、mteHotTargetName、mteHotContextName、mteHotOID、mteFailedReason}状态当前描述“尝试执行集合以响应事件失败的通知”。
The network manager must enable this notification only with
a certain fear and trembling, as it can easily crowd out more
important information. It should be used only to help diagnose
a problem that has appeared in the error counters and can not
be found otherwise."
::= { dismanEventMIBNotifications 5 }
The network manager must enable this notification only with
a certain fear and trembling, as it can easily crowd out more
important information. It should be used only to help diagnose
a problem that has appeared in the error counters and can not
be found otherwise."
::= { dismanEventMIBNotifications 5 }
-- -- Conformance --
----一致性--
dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 }
dismanEventMIBCompliances OBJECT IDENTIFIER ::=
{ dismanEventMIBConformance 1 }
dismanEventMIBGroups OBJECT IDENTIFIER ::=
{ dismanEventMIBConformance 2 }
dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 }
dismanEventMIBCompliances OBJECT IDENTIFIER ::=
{ dismanEventMIBConformance 1 }
dismanEventMIBGroups OBJECT IDENTIFIER ::=
{ dismanEventMIBConformance 2 }
-- Compliance
--顺从
dismanEventMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION
拆卸MIB合规模块-合规状态当前描述
"The compliance statement for entities which implement
the Event MIB."
MODULE -- this module
MANDATORY-GROUPS {
dismanEventResourceGroup,
dismanEventTriggerGroup,
dismanEventObjectsGroup,
dismanEventEventGroup,
dismanEventNotificationObjectGroup,
dismanEventNotificationGroup
}
"The compliance statement for entities which implement
the Event MIB."
MODULE -- this module
MANDATORY-GROUPS {
dismanEventResourceGroup,
dismanEventTriggerGroup,
dismanEventObjectsGroup,
dismanEventEventGroup,
dismanEventNotificationObjectGroup,
dismanEventNotificationGroup
}
OBJECT mteTriggerTargetTag MIN-ACCESS read-only DESCRIPTION "Write access is not required, thus limiting monitoring to the local system or pre-configured remote systems."
对象mteTriggerTargetTag MIN-ACCESS只读说明“不需要写访问，因此将监视限制在本地系统或预配置的远程系统。”
OBJECT mteEventSetTargetTag MIN-ACCESS read-only DESCRIPTION "Write access is not required, thus limiting setting to the local system or pre-configured remote systems."
对象mteEventSetTargetTag MIN-ACCESS只读说明“不需要写访问，因此将设置限制为本地系统或预配置的远程系统。”
OBJECT mteTriggerValueIDWildcard MIN-ACCESS read-only DESCRIPTION "Write access is not required, thus allowing the system not to implement wildcarding."
对象mteTriggerValueIDWildcard MIN-ACCESS只读描述“不需要写访问，因此允许系统不实现通配符。”
OBJECT mteTriggerContextNameWildcard MIN-ACCESS read-only DESCRIPTION "Write access is not required, thus allowing the system not to implement wildcarding."
对象mteTriggerContextNameWildcard MIN-ACCESS只读描述“不需要写访问，因此允许系统不实现通配符。”
OBJECT mteObjectsIDWildcard MIN-ACCESS read-only DESCRIPTION "Write access is not required, thus allowing the system not to implement wildcarding."
对象mteObjectsIDWildcard MIN-ACCESS只读说明“不需要写访问，因此允许系统不实现通配符。”
OBJECT mteEventSetContextNameWildcard MIN-ACCESS read-only DESCRIPTION
对象MTEEventSetContextName通配符最小访问只读说明
"Write access is not required, thus allowing the system not to implement wildcarding."
不需要写访问权限，因此允许系统不执行通配符
::= { dismanEventMIBCompliances 1 }
::= { dismanEventMIBCompliances 1 }
-- Units of Conformance
--一致性单位
dismanEventResourceGroup OBJECT-GROUP
OBJECTS {
mteResourceSampleMinimum,
mteResourceSampleInstanceMaximum,
mteResourceSampleInstances,
mteResourceSampleInstancesHigh,
mteResourceSampleInstanceLacks
}
STATUS current
DESCRIPTION
"Event resource status and control objects."
::= { dismanEventMIBGroups 1 }
dismanEventResourceGroup OBJECT-GROUP
OBJECTS {
mteResourceSampleMinimum,
mteResourceSampleInstanceMaximum,
mteResourceSampleInstances,
mteResourceSampleInstancesHigh,
mteResourceSampleInstanceLacks
}
STATUS current
DESCRIPTION
"Event resource status and control objects."
::= { dismanEventMIBGroups 1 }
dismanEventTriggerGroup OBJECT-GROUP OBJECTS { mteTriggerFailures,
DemanEventTriggerGroup对象组对象{mteTriggerFailures，
mteTriggerComment, mteTriggerTest, mteTriggerSampleType, mteTriggerValueID, mteTriggerValueIDWildcard, mteTriggerTargetTag, mteTriggerContextName, mteTriggerContextNameWildcard, mteTriggerFrequency, mteTriggerObjectsOwner, mteTriggerObjects, mteTriggerEnabled, mteTriggerEntryStatus,
mteTriggerComment、mteTriggerTest、mteTriggerSampleType、mteTriggerValueID、mteTriggerValueID通配符、mteTriggerTargetTag、mteTriggerContextName、mteTriggerContextName通配符、mteTriggerFrequency、mteTriggerObjectsOwner、mteTriggerObjects、mteTriggerEnabled、mteTriggerEntryStatus、，
mteTriggerDeltaDiscontinuityID, mteTriggerDeltaDiscontinuityIDWildcard, mteTriggerDeltaDiscontinuityIDType, mteTriggerExistenceTest, mteTriggerExistenceStartup, mteTriggerExistenceObjectsOwner, mteTriggerExistenceObjects, mteTriggerExistenceEventOwner, mteTriggerExistenceEvent,
mteTriggerDeltaDiscontinuityID，MTETriggerDeltaDiscontinuityIdCard，mteTriggerDeltaDiscontinuityIDType，mteTriggerExistenceTest，mteTriggerExistenceStartup，MTETriggerExistenceObject Sowner，MTETriggerExistenceObject，mteTriggerExistenceEvent，
mteTriggerBooleanComparison, mteTriggerBooleanValue, mteTriggerBooleanStartup, mteTriggerBooleanObjectsOwner, mteTriggerBooleanObjects, mteTriggerBooleanEventOwner, mteTriggerBooleanEvent,
mteTriggerBooleanComparison、mteTriggerBooleanValue、mteTriggerBooleanStartup、mteTriggerBooleanObjectsOwner、mteTriggerBooleanObjects、mteTriggerBooleanEventOwner、mteTriggerBooleanEvent、，
mteTriggerThresholdStartup,
mteTriggerThresholdObjectsOwner,
mteTriggerThresholdObjects,
mteTriggerThresholdRising,
mteTriggerThresholdFalling,
mteTriggerThresholdDeltaRising,
mteTriggerThresholdDeltaFalling,
mteTriggerThresholdRisingEventOwner,
mteTriggerThresholdRisingEvent,
mteTriggerThresholdFallingEventOwner,
mteTriggerThresholdFallingEvent,
mteTriggerThresholdDeltaRisingEventOwner,
mteTriggerThresholdDeltaRisingEvent,
mteTriggerThresholdDeltaFallingEventOwner,
mteTriggerThresholdDeltaFallingEvent
}
STATUS current
DESCRIPTION
"Event triggers."
::= { dismanEventMIBGroups 2 }
mteTriggerThresholdStartup,
mteTriggerThresholdObjectsOwner,
mteTriggerThresholdObjects,
mteTriggerThresholdRising,
mteTriggerThresholdFalling,
mteTriggerThresholdDeltaRising,
mteTriggerThresholdDeltaFalling,
mteTriggerThresholdRisingEventOwner,
mteTriggerThresholdRisingEvent,
mteTriggerThresholdFallingEventOwner,
mteTriggerThresholdFallingEvent,
mteTriggerThresholdDeltaRisingEventOwner,
mteTriggerThresholdDeltaRisingEvent,
mteTriggerThresholdDeltaFallingEventOwner,
mteTriggerThresholdDeltaFallingEvent
}
STATUS current
DESCRIPTION
"Event triggers."
::= { dismanEventMIBGroups 2 }
dismanEventObjectsGroup OBJECT-GROUP
OBJECTS {
mteObjectsID,
mteObjectsIDWildcard,
mteObjectsEntryStatus
}
STATUS current
DESCRIPTION
"Supplemental objects."
::= { dismanEventMIBGroups 3 }
dismanEventObjectsGroup OBJECT-GROUP
OBJECTS {
mteObjectsID,
mteObjectsIDWildcard,
mteObjectsEntryStatus
}
STATUS current
DESCRIPTION
"Supplemental objects."
::= { dismanEventMIBGroups 3 }
dismanEventEventGroup OBJECT-GROUP OBJECTS { mteEventFailures,
DisamNeventGroup对象组对象{mteEventFailures，
mteEventComment, mteEventActions, mteEventEnabled, mteEventEntryStatus,
mteEventComment、mteEventActions、mteEventEnabled、mteEventEntryStatus、，
mteEventNotification, mteEventNotificationObjectsOwner, mteEventNotificationObjects,
mteEventNotification，mteEventNotification对象Sowner，mteEventNotification对象，
mteEventSetObject,
mteEventSetObjectWildcard,
mteEventSetValue,
mteEventSetTargetTag,
mteEventSetContextName,
mteEventSetContextNameWildcard
}
STATUS current
DESCRIPTION
"Events."
::= { dismanEventMIBGroups 4 }
mteEventSetObject,
mteEventSetObjectWildcard,
mteEventSetValue,
mteEventSetTargetTag,
mteEventSetContextName,
mteEventSetContextNameWildcard
}
STATUS current
DESCRIPTION
"Events."
::= { dismanEventMIBGroups 4 }
dismanEventNotificationObjectGroup OBJECT-GROUP
OBJECTS {
mteHotTrigger,
mteHotTargetName,
mteHotContextName,
mteHotOID,
mteHotValue,
mteFailedReason
}
STATUS current
DESCRIPTION
"Notification objects."
::= { dismanEventMIBGroups 5 }
dismanEventNotificationObjectGroup OBJECT-GROUP
OBJECTS {
mteHotTrigger,
mteHotTargetName,
mteHotContextName,
mteHotOID,
mteHotValue,
mteFailedReason
}
STATUS current
DESCRIPTION
"Notification objects."
::= { dismanEventMIBGroups 5 }
dismanEventNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
mteTriggerFired,
mteTriggerRising,
mteTriggerFalling,
mteTriggerFailure,
mteEventSetFailure
}
STATUS current
DESCRIPTION
"Notifications."
::= { dismanEventMIBGroups 6 }
dismanEventNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
mteTriggerFired,
mteTriggerRising,
mteTriggerFalling,
mteTriggerFailure,
mteEventSetFailure
}
STATUS current
DESCRIPTION
"Notifications."
::= { dismanEventMIBGroups 6 }
END
终止
The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards- related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
This MIB contains considerable contributions from the RMON MIB, the Distributed Management Design Team (Andy Bierman, Maria Greene, Bob Stewart, and Steve Waldbusser), the Distributed Management Working Group, and colleagues at Cisco.
此MIB包含来自RMON MIB、分布式管理设计团队（Andy Bierman、Maria Greene、Bob Stewart和Steve Waldbusser）、分布式管理工作组和Cisco同事的大量贡献。
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[RFC2571]Harrington，D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1155]Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[RFC1212]Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[RFC1215] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[RFC1215]Rose，M.，“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1157]Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[RFC1901]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC1906]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[RFC2572]Case，J.，Harrington D.，Presohn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2574]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版基于用户的安全模型（USM）”，RFC 2574，1999年4月。
[RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1905]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[RFC2573]Levi，D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC 2573，1999年4月。
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2575]Wijnen，B.，Presohn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 2575，1999年4月。
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999.
[RFC2570]Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准网络管理框架第3版简介”，RFC 25701999年4月。
[RFC1903] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Coexistence between Version 1 and version 2 of the Internet-standard Network Management Framework", RFC 1903, January 1996.
[RFC1903]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“互联网标准网络管理框架第1版和第2版之间的共存”，RFC 1903，1996年1月。
[RFC2981] Stewart, B., "Event MIB", RFC 2981, October 2000.
[RFC2981]Stewart，B.，“事件MIB”，RFC 29812000年10月。
[RFC1757] Waldbusser, S., "Remote Network Monitoring Management Information Base", RFC 1757, February 1995.
[RFC1757]Waldbusser，S.，“远程网络监控管理信息库”，RFC1757，1995年2月。
[RFC1451] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Manager-to- Manager Management Information Base", RFC 1451, April 1993.
[RFC1451]Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“经理对经理管理信息库”，RFC 14511993年4月。
[RFC2982] Stewart, B., "Distributed Management Expression MIB", RFC 2982, October 2000.
[RFC2982]Stewart，B.，“分布式管理表达式MIB”，RFC 29822000年10月。
[LOG-MIB] Stewart, B., "Notification Log MIB", Work in Progress.
[LOG-MIB]Stewart，B.，“通知日志MIB”，正在进行的工作。
Security issues are discussed in the Security section and in the DESCRIPTION clauses of relevant objects.
安全性部分和相关对象的描述条款中讨论了安全性问题。
Bob Stewart Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 U.S.A.
Bob Stewart Cisco Systems，Inc.美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134-1706。
Ramanathan Kavasseri Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 U.S.A.
美国加利福尼亚州圣何塞西塔斯曼大道170号拉马纳森·卡瓦塞里思科系统公司，邮编95134-1706。
Phone: +1 408 527 2446
EMail: ramk@cisco.com
Phone: +1 408 527 2446
EMail: ramk@cisco.com
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。