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
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）の一部を定義します。特に、管理および監視する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.
この文書のキーワード "MUST"、 "MUST NOT"、 "REQUIRED"、、、、 "べきではない" "べきである" "ないもの" "ものとし"、 "推奨"、 "MAY"、および "OPTIONAL" はあります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
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 Management Frameworkは現在、5つの主要コンポーネントから構成されています。
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メッセージプロトコルの第2のバージョンは、SNMPv2cのと呼ばれ、RFC 1901 [RFC1901]及びRFC 1906 [RFC1906]に記載されています。メッセージプロトコルのバージョン3は、RFC 2572 [RFC2572]及びRFC 2574 [RFC2574]、[RFC1906]のSNMPv3と呼ばれ、RFC 1906年に記載されています。
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プロトコル操作。プロトコル操作と関連PDU形式の第一セットは、STD 15、RFC 1157 [RFC1157]に記載されています。プロトコル操作と関連PDU形式の第2のセットは、RFC 1905 [RFC1905]に記載されています。
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 Management Frameworkへの、より詳細な紹介は、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には翻訳（Counter64のの使用）が可能ではないので、オブジェクトまたはイベントが省略されている場合を除いて、意味的に等価でなければなりません。 SMIv2のいくつかの機械読み取り可能な情報には、翻訳プロセスの間、SMIv1の原文の記述に変換されます。しかし、機械読み取り可能な情報のこの損失がMIBの意味論を変えると考えられません。有意義MIBのでSMIv1バージョンを使用して、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イベントがトリガに応じて、SNMP通知を送信するRMONのコンセプトを維持し、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のマネージャ・ツー・マネージャMIB [RFC1451]の後継とアップデートです。
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 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はうまく監視するためのブールオブジェクトの予想源である分散管理式MIB [RFC2982]、によって補完されます。イベントのワイルドカードとデルタサンプル能力と表現MIBの間にかなりの重複があることに注意してください。慎重に計画された実装がうまく重なった機能を提供するために、共通のコードを使用することがあります。
The MIB has four sections: triggers, objects, events, and notifications. Triggers define the conditions that lead to events. Events may cause notifications.
トリガ、オブジェクト、イベント、および通知：MIBには4つのセクションがあります。イベントにつながる条件を定義トリガします。イベントは、通知を引き起こす可能性があります。
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 } |
+---------------------------+ +---------------------------+
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オブジェクトを監視し、分散管理アプリケーションのための計測です。最も単純な形式では、このアプリケーションは、RMONプローブはRMONのアラームとイベントの操作によって暗黙の機能を果たすと同じように、個々の、ローカルMIBオブジェクトを監視します。さらに、アプリケーションがリモートオブジェクトとオブジェクトのワイルドカードのグループを監視することができます。
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.
リモート監視は通常のSNMPベースの管理アプリケーションとしてリモートシステムを選択してアクセスするために、管理対象MIB [RFC2573]のタグサービスを使用しています。ローカル監視は、アクセス制御のアプリケーションを含むリモート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.
ワイルドカードは、アプリケーションが普通のSNMPベース管理アプリケーションのように、切り捨てられたオブジェクト識別子によって暗黙ゼロ以上のインスタンスを見つけるために、GetNextのタイプの動作を使用するべきであることを示します。ワイルドカードの各インスタンスは、それが別のエントリであるかのように、それがワイルドカードオブジェクトのインスタンスは、互いに独立しているで処理されます。例えば、ワイルドカードオブジェクトは、イベントをトリガすることができる、別のワイルドカードオブジェクトの設定をもたらします。トリガ機能を満たしインスタンスは、設定された機能を実行するために使用されます。このすべてが独立して、ワイルドカードを埋める可能性のある追加のインスタンスの代わりをします。
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]に記載または通知ログMIB [rfcNotificationLogMIB]に記載されているように、ログに向かうようにPDUを通知として送信されるべきである問題です。実際の通知には、通常は失われませんが、通知ログ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.
この1つは、イベントを設定する際に設定された値の持続性のための明示的なコントロールを持っていない、ほとんどの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管理フレームワークを記述するためのアーキテクチャからisAccessAllowedへの入力として必要なパラメータです。ローカルターゲットタグを使用せずにローカルオブジェクトにアクセスすると、システムは、（概念的には）それがセキュリティに違反しないことを確実にするための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自体のセキュリティ管理者がアクセス制御のプロビジョニングを容易にするために、インデックスは、「所有者インデックス」として使用されています。そのような初期のインデックスはれるSnmpAdminStringの構文を有し、セキュリティポリシーに従って、VACMで定義され、したがって自明のsecurityNameまたはグループ名にマッピングすることができます。
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を構成するためには、所有者インデックス部分、及びvacmViewTreeFamilyMask「ワイルドカード」欄サブ識別子を含むvacmViewTreeFamilySubtreeの値vacmViewTreeFamilyTableのエントリを作成します。より複雑な構成が可能です。
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
輸入MODULE-IDENTITY、OBJECT-TYPE、Integer32の、Unsigned32の、NOTIFICATION-TYPE、Counter32の、Gauge32、MIB-2のzeroDotZeroのSNMPv2-SMIテキストの表記法、RowStatusのFROM、のTruthValueのSNMPv2-TC FROM
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM 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
。dismanEventMIBのMODULE-IDENTITY LAST-UPDATED "200010160000Z" - 2000年10月16日ORGANIZATION "IETF分散管理ワーキンググループ" CONTACT-INFO「ラマナサンKavasseriシスコシステムズ、株式会社170西タスマン・ドライブ、サンノゼCA 95134-1706電話：+1 408 526 4527 Eメール：ramk@cisco.com」DESCRIPTION 『ネットワーク管理用にイベントトリガーおよびアクションを定義するためのMIBモジュール』。 - 改訂履歴
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 }
-- 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 }
-- -- Textual Conventions --
- - テキストの表記法 -
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 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より大きい番号の第2のグループは、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"
以下のようないくつかのローカルリソースをlocalResourceLackメモリ不足またはSNMP要求への応答がsampleOverrunに別のサンプルの試みを期待できないとしてとして検索対象のデータの構文をbadTypeないNORESPONSE mteResourceSampleInstanceMaximumは、宛先アドレスに取得することはできませんbadDestination認識されていないドメイン名またはそれ以外の場合は、無効な宛先アドレスdestinationUnreachableを超え前回のいずれかが完了する前に発生しました」
SYNTAX INTEGER { localResourceLack(-1), badDestination(-2), destinationUnreachable(-3), noResponse(-4), badType(-5), sampleOverrun(-6),
SYNTAX INTEGER {localResourceLack（-1）、badDestination（-2）、destinationUnreachable（-3）、NORESPONSE（-4）、badType（-5）、sampleOverrun（-6）
noError(0),
NOERROR（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）、読み取り専用（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）} -
-- 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のOBJECT-TYPE構文Integer32（1 2147483647）UNITS「秒」MAX-ACCESS読み取りと書き込みステータス現在の説明「このシステムが受け入れる最小mteTriggerFrequency。システムは、一定の影響を軽減するために、この最小値の大きい値を使用することができますサンプリング。より大きなサンプリングシステムサンプルあまり間隔及びより少ないオーバーヘッドを受けるためには、このオブジェクトは、それが設定された後に作成されたすべてのトリガーのためのそのようなより低いオーバーヘッドを適用する方法を提供します。
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.
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のOBJECT-TYPE構文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.
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 }
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 }
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 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 }
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
}
mteOwner OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION
mteOwner OBJECT-TYPE SYNTAXれるSnmpAdminString（SIZE（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 }
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 }
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 OBJECT-TYPE構文BITS {存在（0）、ブール値（1）、閾値（2）} MAX-ACCESSはリード作成ステータス現在の説明「トリガーテストの種類が実行する。 'ブール' および 'しきい値' 試験のために、 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.
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.
「ブール」のために、特定のテストはmteTriggerBooleanTestによって選択されるように。テスト結果は、トリガー火trueの場合。トリガーは値が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 }
mteTriggerSampleType OBJECT-TYPE SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The type of sampling to perform.
mteTriggerSampleTypeのOBJECT-TYPE SYNTAX INTEGER {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.
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」は意味があるために2つのサンプルを必要とするのmteTriggerValueIDでオブジェクトが最初に存在することが判明した後、第二及び後続のサンプルまでこうしてテストには使用できません。これは、2つのサンプル間の差です。符号なしの値の場合には、符号なし算術演算に基づいて、常にポジティブです。符号付きの値のためには、正または負とすることができます。
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 }
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 OBJECT-TYPE構文オブジェクト識別子MAX-ACCESSはリード作成しますステータス現在の説明「トリガーが発動すべきかどうかを確認するためにサンプリングする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 if they exist. If such wildcarding is applied,
mteTriggerValueIDWildcard must be 'true' and if not it must
be '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.
悪いオブジェクト識別子またはGETまたはGETNEXT操作に間違った識別子を提供する際に予想されるように動作して識別子とmteTriggerValueIDWildcard結果の値を切り捨てるの間のミスマッチ。取得に失敗したり、間違ったオブジェクトを取得します。それは混乱した結果の識別子と、おそらく多くの意図しないオブジェクトの最初の部分を過ぎて実行されるまで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 }
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 OBJECT-TYPE構文SnmpTagValue MAX-ACCESSリード作成ステータス現在の説明「トリガーチェックの状態を取得するための標的（単数または複数）のためのタグ。
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.
Otherwise access rights are checked according to the security 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のOBJECT-TYPE SYNTAXれるSnmpAdminString MAX-ACCESS読み取りと書き込みステータス現在の説明の「の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'.
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 }
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のOBJECT-TYPE構文Unsigned32 UNITSの "秒" MAX-ACCESSはリード作成しますステータス現在
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.
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'.
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 }
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 OBJECT-TYPE SYNTAXれるSnmpAdminString（SIZE（0 32））MAX-ACCESSリード作成ステータス現在の説明「オブジェクトのグループのからのmteObjectsTable mteObjectsName。これらのオブジェクトは、この焼成に起因する任意の通知に追加されます引き金。
A list of objects may also be added based on the event or on
the value of mteTriggerTest.
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 }
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 }
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
}
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 OBJECT-TYPE構文オブジェクト識別子MAX-ACCESS読み取りと書き込みステータス現在の説明「時間刻み、タイムスタンプ、またはのmteTriggerValueIDの値の不連続を示すのDateAndTimeオブジェクトのオブジェクト識別子（OID）。
The OID may be for a leaf object (e.g. sysUpTime.0) or may
be wildcarded to match 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 }
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 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 }
-- -- 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 }
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
} 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:
present(0) - when this test is selected, the trigger fires
when the mteTriggerValueID object goes from absent to present.
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 }
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 }
mteTriggerExistenceObjects OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32))
mteTriggerExistenceObjects 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.
A list of objects may also be added based on the overall
trigger, the event or other settings in mteTriggerTest.
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 }
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 }
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
}
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のOBJECT-TYPE SYNTAX INTEGER {不等（1）、等しい（2）、以下（3）、lessOrEqual（4）、大きい（5）、greaterOrEqual（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 }
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 }
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 OBJECT-TYPE SYNTAXれるSnmpAdminString（SIZE（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.
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 OBJECT-TYPE SYNTAXれるSnmpAdminString（SIZE（0 32））MAX-ACCESS読み取りと書き込みステータス現在の説明 "mteTriggerBooleanEvent、のmteEventTable mteOwnerイベントエントリのからので行くことに。" DEFVAL { '' H}
::= { 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 }
-- -- 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 }
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, mteTriggerThresholdFallingEvent SnmpAdminString,
mteTriggerThresholdDeltaRisingEventOwner SnmpAdminString,
mteTriggerThresholdDeltaRisingEvent SnmpAdminString,
mteTriggerThresholdDeltaFallingEventOwner SnmpAdminString,
mteTriggerThresholdDeltaFallingEvent SnmpAdminString
}
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 OBJECT-TYPE構文Integer32 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'.
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 }
mteTriggerThresholdFalling OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "A threshold value to check against if mteTriggerType is 'threshold'.
mteTriggerThresholdFalling OBJECT-TYPE構文Integer32 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'.
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 OBJECT-TYPE構文Integer32 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.
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 }
mteTriggerThresholdDeltaFalling OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "A threshold value to check against if mteTriggerType is 'threshold'.
mteTriggerThresholdDeltaFalling OBJECT-TYPE構文Integer32 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.
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 }
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 OBJECT-TYPE SYNTAXれるSnmpAdminString（SIZE（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 }
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 }
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 }
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 }
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 }
--
-- 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 }
mteObjectsEntry OBJECT-TYPE SYNTAX MteObjectsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A group of objects. Applications create and delete entries using mteObjectsEntryStatus.
mteObjectsEntryのOBJECT-TYPE SYNTAX 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 }
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 }
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のOBJECT-TYPE構文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 }
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 OBJECT-TYPE構文オブジェクト識別子MAX-ACCESSは、トリガーの発砲した結果の通知に追加するステータス現在の説明は「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'.
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 }
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 }
-- -- 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 }
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
}
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 }
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 OBJECT-TYPE構文BITS {通知（0）、（1）設定} MAX-ACCESSリード作成ステータス現在の説明「このイベントが発生したときにアクションを実行します。
For 'notification', Traps and/or Informs are sent according
to the configuration in the SNMP Notification MIB.
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 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 }
-- -- 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 }
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
}
mteEventNotification OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS current
mteEventNotification OBJECT-TYPE構文オブジェクト識別子MAX-ACCESS読み取りと書き込みステータス現在の
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 }
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 OBJECT-TYPE SYNTAXれるSnmpAdminString（SIZE（0 32））MAX-ACCESS読み取りと書き込みステータス現在の説明「オブジェクトのグループのからのmteObjectsTable mteObjectsName mteEventActionsセット 『通知』を有する場合、これらのオブジェクトは任意に追加されますこのイベントによって生成される通知。
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 }
-- -- 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 }
mteEventSetEntry OBJECT-TYPE SYNTAX MteEventSetEntry MAX-ACCESS not-accessible
mteEventSetEntryのOBJECT-TYPE SYNTAX 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 }
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 OBJECT-TYPE構文オブジェクト識別子MAX-ACCESS読み取りと書き込みステータス現在の説明「MIBオブジェクトからオブジェクト識別子はmteEventActionsを 『セット』している場合に設定を設定します。
This object identifier may be wildcarded by leaving
sub-identifiers off the end, in which case
nteEventSetObjectWildCard must be '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 }
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 }
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 OBJECT-TYPE構文SnmpTagValue MAX-ACCESS読み取りと書き込みステータス現在の説明「mteEventActionsセット 『セット』している場合mteEventSetValueにmteEventSetObjectにオブジェクトを設定するために標的（単数または複数）のタグ。
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によって示されるオブジェクトへのアクセスは、「アクティブ」にmteTriggerEntryStatus設定要求元のセキュリティ資格情報です。これらの資格情報は、SNMP管理フレームワークを記述するためのアーキテクチャからisAccessAllowedの入力パラメータです。
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のOBJECT-TYPE SYNTAXれるSnmpAdminString MAX-ACCESSの読み取りと書き込み
STATUS current
DESCRIPTION
"The management context in which to set mteEventObjectID.
if mteEventActions has 'set' set.
This may be wildcarded by leaving characters off the end. To
indicate such wildcarding mteEventSetContextNameWildcard must
be 'true'.
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 }
-- -- Notifications --
- - お知らせ -
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 }
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 }
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 OBJECT-TYPE構文オブジェクト識別子MAX-ACCESSアクセス可能のため、通知ステータス現在の説明「通知に関連先オブジェクトのオブジェクト識別子。これは、処理で決定されたワイルドカード情報を入力など、できるだけ完全修飾でなければなりません。
For a trigger-related notification this is from
mteTriggerValueID.
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 }
mteFailedReason OBJECT-TYPE SYNTAX FailureReason MAX-ACCESS accessible-for-notify STATUS current
mteFailedReasonのOBJECT-TYPE SYNTAX FailureReason MAX-ACCESSアクセス可能-FOR-通知STATUSの現在
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 }
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 }
mteTriggerFailure NOTIFICATION-TYPE OBJECTS { mteHotTrigger,
mteTriggerFailure NOTIFICATION-TYPEオブジェクト{mteHotTrigger、
mteHotTargetName,
mteHotContextName,
mteHotOID,
mteFailedReason }
STATUS current
DESCRIPTION
"Notification that an attempt to check a trigger has failed.
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 }
-- -- Conformance --
- - 適合 -
dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 }
dismanEventMIBCompliances OBJECT IDENTIFIER ::=
{ dismanEventMIBConformance 1 }
dismanEventMIBGroups OBJECT IDENTIFIER ::=
{ dismanEventMIBConformance 2 }
-- Compliance
- コンプライアンス
dismanEventMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION
dismanEventMIBCompliance MODULE-COMPLIANCEステータス現在の説明
"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."
OBJECT mteEventSetTargetTag MIN-ACCESS read-only DESCRIPTION "Write access is not required, thus limiting setting to the local system or pre-configured remote systems."
OBJECT mteEventSetTargetTag MIN-ACCESS読み取り専用説明「書き込みアクセスので、ローカルシステムまたは事前設定されたリモートシステムに設定する制限し、必要とされていません。」
OBJECT mteTriggerValueIDWildcard MIN-ACCESS read-only DESCRIPTION "Write access is not required, thus allowing the system not to implement wildcarding."
OBJECT mteTriggerValueIDWildcard MIN-ACCESS読み取り専用説明「書き込みアクセスので、ワイルドカードを実装しないシステムをできるように、必要とされていません。」
OBJECT mteTriggerContextNameWildcard MIN-ACCESS read-only DESCRIPTION "Write access is not required, thus allowing the system not to implement wildcarding."
OBJECT mteTriggerContextNameWildcard MIN-ACCESS読み取り専用説明「書き込みアクセスので、ワイルドカードを実装しないシステムをできるように、必要とされていません。」
OBJECT mteObjectsIDWildcard MIN-ACCESS read-only DESCRIPTION "Write access is not required, thus allowing the system not to implement wildcarding."
OBJECT mteObjectsIDWildcard MIN-ACCESS読み取り専用説明「書き込みアクセスので、ワイルドカードを実装しないシステムをできるように、必要とされていません。」
OBJECT mteEventSetContextNameWildcard MIN-ACCESS read-only DESCRIPTION
OBJECT mteEventSetContextNameWildcard MIN-ACCESS読み取り専用説明
"Write access is not required, thus allowing
the system not to implement wildcarding."
::= { 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 }
dismanEventTriggerGroup OBJECT-GROUP OBJECTS { mteTriggerFailures,
dismanEventTriggerGroupオブジェクト・グループオブジェクト{mteTriggerFailures、
mteTriggerComment,
mteTriggerTest,
mteTriggerSampleType,
mteTriggerValueID,
mteTriggerValueIDWildcard,
mteTriggerTargetTag,
mteTriggerContextName,
mteTriggerContextNameWildcard,
mteTriggerFrequency,
mteTriggerObjectsOwner,
mteTriggerObjects,
mteTriggerEnabled,
mteTriggerEntryStatus,
mteTriggerDeltaDiscontinuityID, mteTriggerDeltaDiscontinuityIDWildcard, mteTriggerDeltaDiscontinuityIDType, mteTriggerExistenceTest, mteTriggerExistenceStartup, mteTriggerExistenceObjectsOwner, mteTriggerExistenceObjects, mteTriggerExistenceEventOwner, mteTriggerExistenceEvent, mteTriggerBooleanComparison, mteTriggerBooleanValue, mteTriggerBooleanStartup, mteTriggerBooleanObjectsOwner, mteTriggerBooleanObjects, mteTriggerBooleanEventOwner, mteTriggerBooleanEvent,
mteTriggerDeltaDiscontinuityID、mteTriggerDeltaDiscontinuityIDWildcard、mteTriggerDeltaDiscontinuityIDType、mteTriggerExistenceTest、mteTriggerExistenceStartup、mteTriggerExistenceObjectsOwner、mteTriggerExistenceObjects、mteTriggerExistenceEventOwner、mteTriggerExistenceEvent、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 }
dismanEventObjectsGroup OBJECT-GROUP
OBJECTS {
mteObjectsID,
mteObjectsIDWildcard,
mteObjectsEntryStatus
}
STATUS current
DESCRIPTION
"Supplemental objects."
::= { dismanEventMIBGroups 3 }
dismanEventEventGroup OBJECT-GROUP OBJECTS { mteEventFailures,
dismanEventEventGroupオブジェクト・グループオブジェクト{mteEventFailures、
mteEventComment,
mteEventActions,
mteEventEnabled,
mteEventEntryStatus, mteEventNotification,
mteEventNotificationObjectsOwner,
mteEventNotificationObjects,
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 }
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は、そのような権限下で、ライセンスがたりないかもしれない可能性があるためにどの本書または程度に記載されている技術の実装や使用に関係すると主張される可能性があります任意の知的財産やその他の権利の有効性または範囲に関していかなる位置を取りません利用可能。また、そうした権利を特定するために取り組んできたことを表していないん。スタンダードトラックとstandards-関連文書の権利に関する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、分散管理設計チーム（アンディBierman、マリア・グリーン、ボブ・スチュワート、およびスティーブWaldbusser）、分散管理ワーキンググループ、およびシスコの同僚からかなりの貢献が含まれています。
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[RFC2571]ハリントン、D.、Presuhnと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]ローズ、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]ローズ、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]ローズ、M.、 "SNMPとの使用のためのDefining Trapsのための条約"、RFC 1215、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.、パーキンス、D.、Schoenwaelder、J.、ケース、J.、ローズ、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.、パーキンス、D.、Schoenwaelder、J.、ケース、J.、ローズ、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.、パーキンス、D.、Schoenwaelder、J.、ケース、J.、ローズ、M.およびS. Waldbusser、 "SMIv2のための適合性宣言"、STD 58、RFC 2580、1999年4月。
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1157]ケース、J.、ヒョードル、M.、Schoffstall、M.、およびJ.デーヴィン、 "簡単なネットワーク管理プロトコル"、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]ケース、J.、McCloghrie、K.、ローズ、M.およびS. Waldbusser、 "コミュニティベースのSNMPv2の概要"、RFC 1901、1996年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]ケース、J.、McCloghrie、K.、ローズ、M.、およびS. Waldbusser、RFC 1906 "簡易ネットワーク管理プロトコル（SNMPv2）のバージョン2のための交通マッピング"、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]ケース、J.、ハリントンD.、Presuhn 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.
、RFC 2574、1999年4月 "簡易ネットワーク管理プロトコル（SNMPv3の）のバージョン3のためのユーザベースセキュリティモデル（USM）" [RFC2574]ブルーメンソール、U.とB. Wijnenの、。
[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]ケース、J.、McCloghrie、K.、ローズ、M.、およびS. Waldbusser、 "簡易ネットワーク管理プロトコルのバージョン2のためのプロトコル操作（SNMPv2の）"、RFC 1905、1996年1月。
[RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[RFC2573]レビ、D.、マイヤー、P.とB.スチュワート、 "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.、Presuhn、R.とK. McCloghrie、 "簡易ネットワーク管理プロトコルのためのビューベースアクセス制御モデル（VACM）（SNMP）"、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]ケース、J.、マンディ、R.、パーテイン、D.とB.スチュワート、 "インターネット標準ネットワーク管理フレームワークのバージョン3への序論"、RFC 2570、1999年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]ケース、J.、McCloghrie、K.、ローズ、M.、およびS. Waldbusser、RFC 1903 "バージョン1およびインターネット標準ネットワーク管理フレームワークのバージョン2の間の共存"、1996年1月。
[RFC2981] Stewart, B., "Event MIB", RFC 2981, October 2000.
[RFC2981]スチュワート、B.、 "イベントMIB"、RFC 2981、2000年10月。
[RFC1757] Waldbusser, S., "Remote Network Monitoring Management Information Base", RFC 1757, February 1995.
[RFC1757] Waldbusser、S.、 "管理情報ベースのリモートネットワーク監視"、RFC 1757、1995年2月。
[RFC1451] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Manager-to- Manager Management Information Base", RFC 1451, April 1993.
[RFC1451]ケース、J.、McCloghrie、K.、ローズ、M.、およびS. Waldbusser、 "マネージャー・ツー・マネージャーの管理情報ベース"、RFC 1451、1993年4月。
[RFC2982] Stewart, B., "Distributed Management Expression MIB", RFC 2982, October 2000.
[RFC2982]スチュワート、B.、 "分散管理式のMIB"、RFC 2982、2000年10月。
[LOG-MIB] Stewart, B., "Notification Log MIB", Work in Progress.
[LOG-MIB]スチュワート、B.、 "通知ログMIB"、ProgressのWork。
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.
ボブスチュワートシスコシステムズ、株式会社170西タスマン・ドライブサンノゼ、CA 95134-1706 U.S.A.
Ramanathan Kavasseri Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 U.S.A.
ラマナサンKavasseriシスコシステムズ、株式会社170西タスマン・ドライブサンノゼ、CA 95134-1706 U.S.A.
Phone: +1 408 527 2446 EMail: ramk@cisco.com
電話：+1 408 527 2446 Eメール：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 Editor機能のための基金は現在、インターネット協会によって提供されます。