RFC2456 日本語訳

Network Working Group                                     B. Clouston
Request for Comments: 2456                              Cisco Systems
Category: Standards Track                                    B. Moore
                                                      IBM Corporation
                                                        November 1998

Cloustonがコメントのために要求するワーキンググループB.をネットワークでつないでください: 2456年のシスコシステムズカテゴリ: 標準化過程B.ムーアIBM社の1998年11月

                     Definitions of Managed Objects
                             for APPN TRAPS

APPN罠のための管理オブジェクトの定義

Status of this Memo

この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.

このドキュメントは、インターネットコミュニティにインターネット標準化過程プロトコルを指定して、改良のために議論と提案を要求します。 このプロトコルの標準化状態と状態への「インターネット公式プロトコル標準」(STD1)の現行版を参照してください。 このメモの分配は無制限です。

Copyright Notice

版権情報

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

Copyright(C)インターネット協会(1998)。 All rights reserved。

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 defines objects for receiving notifications from
   network devices with APPN (Advanced Peer-to-Peer Network) and DLUR
   (Dependent LU Requester) capabilities.  This memo identifies
   notifications for the APPN and DLUR architecture.

ネットワーク管理プロトコルがインターネットコミュニティにある状態で、このメモは使用のために、Management Information基地の一部(MIB)を定義します。 特に、それは、APPN(高度なPeer-to-Peerネットワーク)とDLUR(依存するLU Requester)能力でネットワーク装置から通知を受け取るために物を定義します。 このメモはAPPNとDLUR構造のための通知を特定します。

Table of Contents

目次

   1.     Introduction  ...........................................  2
   2.     The SNMP Network Management Framework  ..................  2
   3.     Overview  ...............................................  3
   3.1      APPN TRAP MIB structure  ..............................  5
   4.     Definitions  ............................................  6
   5.     Security Considerations  ................................ 17
   6.     Intellectual Property  .................................. 17
   7.     Acknowledgments  ........................................ 18
   8.     References  ............................................. 18
   9.     Authors' Addresses  ..................................... 20
   10.    Full Copyright Statement  ............................... 21

1. 序論… 2 2. SNMPネットワークマネージメント枠組み… 2 3. 概観… 3 3.1 APPN TRAP MIB構造… 5 4. 定義… 6 5. セキュリティ問題… 17 6. 知的所有権… 17 7. 承認… 18 8. 参照… 18 9. 作者のアドレス… 20 10. 完全な著作権宣言文… 21

Clouston & Moore            Standards Track                     [Page 1]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[1ページ]RFC2456APPNはMIB1998年11月に捕らえます。

1.  Introduction

1. 序論

   This document is a product of the SNA NAU Services MIB Working Group.
   It defines a MIB module for notifications for devices with Advanced
   Peer-to-Peer Networking (APPN) and Dependent LU Requester (DLUR)
   capabilities.

このドキュメントはSNA NAU Services MIB作業部会の製品です。 それはAdvanced Peerから同輩へのNetworking(APPN)とDependent LU Requester(DLUR)能力で装置のための通知のための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 [13].

キーワード“MUST"、「必須NOT」が「必要です」、“SHALL"、「」、“SHOULD"、「「推薦され」て、「5月」の、そして、「任意」のNOTはRFC2119[13]で説明されるように本書では解釈されることであるべきですか?

2.  The SNMP Network Management Framework

2. SNMPネットワークマネージメント枠組み

   The SNMP Management Framework presently consists of five major
   components:

SNMP Management Frameworkは現在、5個の主要コンポーネントから成ります:

   o    An overall architecture, described in RFC 2271 [1].

o RFC2271[1]で説明された総合的な構造。

   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 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
        second version, called SMIv2, is described in RFC 1902 [5], RFC
        1903 [6] and RFC 1904 [7].

o 物を説明して、命名するためのメカニズムと管理の目的のための出来事。 Management情報(SMI)のこのStructureの最初のバージョンは、STD16、RFC1155[2]、STD16、RFC1212[3]、およびRFC1215[4]でSMIv1と呼ばれて、説明されます。 SMIv2と呼ばれる第2バージョンはRFC1902[5]、RFC1903[6]、およびRFC1904[7]で説明されます。

   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 [8]. A second version of the SNMP
        message protocol, which is not an Internet standards track
        protocol, is called SNMPv2c and described in RFC 1901 [9] and
        RFC 1906 [10]. The third version of the message protocol is
        called SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and
        RFC 2274 [12].

o 経営情報を移すためのメッセージプロトコル。 SNMPメッセージプロトコルの最初のバージョンは、STD15、RFC1157[8]でSNMPv1と呼ばれて、説明されます。 SNMPメッセージプロトコルの第2のバージョンは、RFC1901[9]とRFC1906[10]でSNMPv2cと呼ばれて、説明されます。(プロトコルはインターネット標準化過程プロトコルではありません)。 メッセージプロトコルの第3バージョンは、RFC1906[10]、RFC2272[11]、およびRFC2274[12]でSNMPv3と呼ばれて、説明されます。

   o    Protocol operations for accessing management information. The
        first set of protocol operations and associated PDU formats is
        described in STD 15, RFC 1157 [8]. A second set of protocol
        operations and associated PDU formats is described in RFC 1905
        [13].

o 経営情報にアクセスするための操作について議定書の中で述べてください。 プロトコル操作と関連PDU形式の第一セットはSTD15、RFC1157[8]で説明されます。 2番目のセットのプロトコル操作と関連PDU形式はRFC1905[13]で説明されます。

   o    A set of fundamental applications described in RFC 2273 [14] and
        the view-based access control mechanism described in RFC 2275
        [15].

o 1セットの基礎的応用はRFCで2273[14]について説明しました、そして、視点ベースのアクセス管理機構はRFCで2275[15]について説明しました。

   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.

管理オブジェクトはManagement Information基地と呼ばれた仮想情報店かMIBを通してアクセスされます。 MIBの物は、SMIで定義されたメカニズムを使用することで定義されます。

Clouston & Moore            Standards Track                     [Page 2]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[2ページ]RFC2456APPNはMIB1998年11月に捕らえます。

   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.

このメモはSMIv2に対応であるMIBモジュールを指定します。 適切な翻訳でSMIv1に従うMIBは生産できます。 どんな翻訳も可能でないので(Counter64の使用)、結果として起こる翻訳されたMIBは物か出来事が省略されるところで意味的に同等でなければなりません。 SMIv2の何らかのマシンの読み込み可能な情報が翻訳の過程の間、SMIv1の原文の記述に変換されるでしょう。 しかしながら、マシンの読み込み可能な情報のこの損失がMIBの意味論を変えると考えられません。

3.  Overview

3. 概観

   This document identifies the set of objects for reporting the status
   of devices with APPN and DLUR capabilities via notifications.

このドキュメントは、APPNとDLUR能力で通知で装置の状態を報告するために物のセットを特定します。

   See the SNANAU APPN MIB [18] and SNANAU DLUR MIB [19] for the objects
   for monitoring the configuration and active characteristics of the
   devices with APPN and DLUR capabilities. Many objects contained in
   the notifications of this MIB are imported from the APPN and DLUR
   MIBs.  Implementors of this MIB must also implement the APPN MIB.
   Implementations that support the appnTrapMibDlurConfGroup and the
   appnTrapMibDlurNotifGroup must also implement the DLUR MIB.

APPNとDLUR能力で装置の構成とアクティブな特性をモニターするための物のためにSNANAU APPN MIB[18]とSNANAU DLUR MIB[19]を見てください。 APPNとDLUR MIBsからこのMIBの通知に含まれた多くの物を輸入します。 また、このMIBの作成者はAPPN MIBを実行しなければなりません。 また、appnTrapMibDlurConfGroupとappnTrapMibDlurNotifGroupを支持する実現はDLUR MIBを実行しなければなりません。

   The SNANAU APPN MIB allows a management station to collect the
   network topology of an APPN network (the network nodes (NNs) in the
   network and all of transmission groups (TGs) between the network
   nodes) from an APPN device.  It also allows the management station to
   collect the local topology (TGs to end stations, and locally defined
   ports and link stations) from an APPN device.  While the SNANAU APPN
   MIB has an efficient way to poll the APPN device for updates to the
   network topology, using flow reduction sequence numbers (FRSNs) as a
   table index; it does not have a mechanism to poll the local topology
   tables (appnLocalTgTable, appnPortTable, and appnLsTable) for status
   changes.

SNANAU APPN MIBは管理局にAPPN装置からAPPNネットワーク(ネットワーク・ノードの間のトランスミッショングループ(TGs)のネットワークとすべてのネットワーク・ノード(NNs))のネットワーク形態を集めさせます。 また、それで、管理局はAPPN装置から地方のトポロジー(ステーションを終わらせて、局所的にポートを定義して、ステーションをリンクするTGs)を集めることができます。 SNANAU APPN MIBにはアップデートのためのAPPN装置にネットワーク形態に投票する効率的な方法がある間、テーブルインデックスとして流れ減少一連番号(FRSNs)を使用すること。 それには、状態変化のために、地方のトポロジーテーブル(appnLocalTgTable、appnPortTable、およびappnLsTable)に投票するメカニズムがありません。

   This MIB provides a mechanism for an APPN device to send
   notifications to inform the management station of status changes to
   rows of these tables. Status changes include operational state
   changes, and for TGs also include control-point to control-point
   (CP-CP) session state changes.  A notification is defined for each
   type of status change for each table.

このMIBは、APPN装置がこれらのテーブルの列への状態変化の管理局を知らせるために通告を送るためにメカニズムを提供します。 状態変化は、制御点(CP-CP)セッション州の変化に操作上の州の変化を含めて、TGsのためにも制御点を含めます。 通知は各テーブルのためのそれぞれのタイプの状態変化のために定義されます。

   The port and link operational state objects have intermediate states.
   Notifications are only sent for transition to active or inactive
   state.

ポートとリンクには、中間的州があります操作上の州が、反対する。 アクティブであるか不活発な状態への変遷のために通知を送るだけです。

Clouston & Moore            Standards Track                     [Page 3]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[3ページ]RFC2456APPNはMIB1998年11月に捕らえます。

   Notifications are only sent for row creation if the state is active
   or operational.  This is done to avoid sending a notification as the
   row is created with an inactive initial state, followed by another
   notification as the resource is activated.

状態がアクティブであるか、または操作上である場合にだけ、列の創造のために通知を送ります。 リソースが活性であるので別の通知が不活発な初期状態のあとに続いていて列が作成されるので通知書を送るのを避けるためにこれをします。

   Notifications are only sent for row deletion if the last state was
   active or operational.  In most cases, a resource must be deactivated
   before it can be deleted, and the deactivation will cause a
   notification to be sent.  There is no need for a second notification
   to be sent for the row deletion, except for the case where the
   deletion occurred without deactivation.  In this case, the state of
   the object in the notification will indicate an inactve state, since
   a deleted resource can no longer be active.

最後の状態がアクティブであるか、または操作上であった場合にだけ、列の削除のために通知を送ります。 多くの場合、それを削除できる前にリソースを非活性化しなければなりません、そして、非活性化で、通知を送るでしょう。 2番目の通知が列の削除のために送られる必要は全くありません、削除が非活性化なしで起こったケースを除いて。 この場合、通知における物の州はinactve状態を示すでしょう、削除されたリソースがもうアクティブであるはずがないので。

   The purpose of the appnLocalTgCpCpStateChangeTrap notification is to
   identify the loss or recovery of CP-CP sessions on a TG while the TG
   remains operational.  Thus this notification is only sent if there is
   a change to an appnLocalTgCpCpSession object, but not a change to the
   appnLocalTgOperational object.  This notification is never sent for
   the creation or deletion of a row in the appnLocalTgTable.

appnLocalTgCpCpStateChangeTrap通知の目的はTGが操作上のままで残っている間、TGにおけるCP-CPセッションの損失か回復を特定することです。 したがって、appnLocalTgOperational物への変化ではなく、appnLocalTgCpCpSession物への変化がある場合にだけ、この通知を送ります。 appnLocalTgTableでの列の創造か削除のためにこの通知を決して送りません。

   Each notification always contains an object which is a count of the
   number of times the status of a row in table has changed since the
   APPN node was last reinitialized.  This enables a management station
   to detect that it has missed a notification, if it does not get the
   notifications in numerical sequence.  If the notifications are not in
   sequence, the management station should retrieve the entire table to
   get the correct status for all rows.

各通知はいつもAPPNノードが最後に再初期化されて以来テーブルの列の状態が変えている回数のカウントである物を含んでいます。 これは検出する管理局を可能にします。数字の系列における通知を得ないなら、それは通知を逃しました。 系列に通知がないなら、管理局は、正しい状態をすべての列に得るために全体のテーブルを検索するはずです。

   Similarly, the SNANAU DLUR MIB provides a mechanism for retrieving
   the configuration and status of dependent LU server (DLUS) sessions
   on a device with DLUR capabilities.  This MIB defines a notification
   for a DLUR-DLUS session state change of a row in the dlurDlusTable,
   in the manner described above.  A notification is only sent for a
   session state transition to active or inactive.  As with the above
   notifications, it is only sent on row creation if the initial state
   is active; and on row deletion is the last state was active, in which
   case the notification indicates that the state is now inactive.

同様に、SNANAU DLUR MIBはDLUR能力で装置の依存するLUサーバ(DLUS)セッションの構成と状態を検索するのにメカニズムを提供します。 このMIBはdlurDlusTableにおける、列のDLUR-DLUSセッション州の変化のための通知を定義します、上で説明された方法で。 セッション状態遷移のためにアクティブであるか不活発に通知を送るだけです。 上記の通知のように、初期状態が活動的である場合にだけ、列の創造にそれを送ります。 そして、列では、削除は最後の状態が活動的であった、その場合、通知が状態が現在不活発であることを示すということです。

   The SNANAU APPN MIB also provides a mechanism for a management
   station to collect traffic statistics on intermediate sessions,
   primarily for accounting purposes.  However, when the session is
   terminated, all statistics from the last poll until the session
   termination time are lost, since the row for that session is deleted
   from the appnIsInTable.  This MIB defines a notification so that the
   session's final statistics can be sent to a management station.  If
   the notification is not delivered, the final session statistics are
   lost.  If this is a concern, polling of the appnIsInTable in the APPN

また、管理局が中間的セッションにおける交通統計を集めるように、SNANAU APPN MIBはメカニズムを提供します、主として会計目的のために。 しかしながら、セッションが終えられるとき、最後の終了時間のセッションまでの投票からのすべての統計が無くなります、そのセッションのための列がappnIsInTableから削除されるので。 このMIBは、セッションの最終的な統計を管理局に送ることができるように通知を定義します。 通知が提供されないなら、最終的なセッション統計は無くなっています。 これが関心、APPNのappnIsInTableの世論調査であるなら

Clouston & Moore            Standards Track                     [Page 4]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[4ページ]RFC2456APPNはMIB1998年11月に捕らえます。

   MIB should be increased to more likely reduce the time between the
   last poll and the session termination, thereby reducing the amount of
   data lost.

MIBがおそらく、最後の投票とセッション終了の間で時間を短縮するために増加されているべきである、その結果、データ量を減少させるのは損をしました。

   Highlights of the management functions supported by the APPN TRAP MIB
   module include the following:

APPN TRAP MIBモジュールで支持された管理機能に関するハイライトは以下を含んでいます:

   o    A notification for an APPN local TG operational state change.

o APPNの地方のTG操作上の州の変化のための通知。

   o    A notification for an APPN local TG CP-CP session state change.

o APPNの地方のTG CP-CPセッション州の変化のための通知。

   o    A notification for an APPN port operational state change.

o APPNのための通知は操作上の州の変化を移植します。

   o    A notification for an APPN link station operational state
        change.

o APPNリンクステーション操作上の州の変化のための通知。

   o    A notification for a DLUR-DLUS session state change.

o DLUR-DLUSセッション州の変化のための通知。

   o    A notification for reporting final APPN intermediate session
        statistics.

o 最終的なAPPN中間的セッション統計を報告するための通知。

   This MIB module does not support:

このMIBモジュールは以下を支持しません。

   o    Objects to query the configuration or status of APPN nodes on
        demand.

o オンデマンドのAPPNノードの構成か状態について質問する物。

   o    Notifications for changes to local topology tables not related
        to status.

o 地方のトポロジーテーブルへの変化のための通知は状態に関連しませんでした。

3.1.  APPN TRAP MIB Structure

3.1. APPN罠MIB構造

   The APPN TRAP MIB module contains a group of notifications, and a
   group of supporting objects.

APPN TRAP MIBモジュールは通知のグループ、およびサポート物のグループを含みます。

   The group of notifications consists of the following notifications:

通知のグループは以下の通知から成ります:

   1) appnIsrAccountingDataTrap

1) appnIsrAccountingDataTrap

   This notification is generated by an APPN device when an intermediate
   session is terminating, to report the final accounting statistics of
   the session.

中間的セッションがセッションの最終的な会計統計を報告するために終わっているとき、この通知はAPPN装置で発生します。

   2) appnLocalTgOperStateChangeTrap

2) appnLocalTgOperStateChangeTrap

   This notification identifies a change to the appnLocalTgOperational
   object in a row of the SNANAU APPN MIB appnLocalTgTable.

この通知は並びSNANAU APPN MIB appnLocalTgTableのappnLocalTgOperational物への変化を特定します。

Clouston & Moore            Standards Track                     [Page 5]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[5ページ]RFC2456APPNはMIB1998年11月に捕らえます。

   3) appnLocalTgCpCpStateChangeTrap

3) appnLocalTgCpCpStateChangeTrap

   This notification identifies a change to the appnLocalTgCpCpSession
   object in a row of the SNANAU APPN MIB appnLocalTgTable.

この通知は並びSNANAU APPN MIB appnLocalTgTableのappnLocalTgCpCpSession物への変化を特定します。

   4) appnPortOperStateChangeTrap

4) appnPortOperStateChangeTrap

   This notification identifies a change to the appnPortOperState object
   in a row of the SNANAU APPN MIB appnPortTable.

この通知は並びSNANAU APPN MIB appnPortTableのappnPortOperState物への変化を特定します。

   5) appnLsOperStateChangeTrap

5) appnLsOperStateChangeTrap

   This notification identifies a change to the appnLsOperState object
   in a row of the SNANAU APPN MIB appnLsTable.

この通知は並びSNANAU APPN MIB appnLsTableのappnLsOperState物への変化を特定します。

   6) dlurDlusStateChangeTrap

6) dlurDlusStateChangeTrap

   This notification identifies a change to the dlurDlusSessnStatus
   object in a row of the SNANAU DLUR MIB dlurDlusTable.

この通知は並びSNANAU DLUR MIB dlurDlusTableのdlurDlusSessnStatus物への変化を特定します。

   The group of supporting objects contains the appnTrapControl object,
   which controls whether the APPN device generates each type of
   notification.  Note that generation of the appnIsrAccountingDataTrap
   is not controlled by this object; instead it is controlled by the
   appnIsInGlobalCtrAdminStatus object in the SNANAU APPN MIB.

サポート物のグループはappnTrapControl物を含みます。(それは、APPN装置がそれぞれのタイプに関する通知を発生させるかどうかを制御します)。 appnIsrAccountingDataTrapの世代がこの物によって制御されないことに注意してください。 代わりに、それはSNANAU APPN MIBのappnIsInGlobalCtrAdminStatus物によって制御されます。

   Although APPN notification generation could be controlled solely by
   entries in the snmpNotificationMIB, RFC 2273 [9], the appnTrapControl
   object exists in this MIB so that implementations are not required to
   implement RFC 2273 to control generation of APPN notifications.  For
   a notification to be generated and sent as a TRAP or INFORM, the
   notification type must first be enabled by the appnTrapControl
   object.  It must also not be disabled by an snmpNotificationMIB
   entry.  The destination of notifications is not within the scope of
   this MIB.

唯一snmpNotificationMIBのエントリーでAPPN通知世代を制御できるでしょうが、RFC2273[9]、appnTrapControl物がこのMIBに存在しているので、実現はAPPN通知の世代を制御するためにRFC2273を実行するのに必要ではありません。 TRAPかINFORMとして通知を発生して、送るために、最初に、appnTrapControl物で通知タイプを可能にしなければなりません。 また、snmpNotificationMIBエントリーでそれを無能にしてはいけません。 このMIBの範囲の中に通知の目的地がありません。

   Also contained in this group are objects for the TG, port, link, and
   DLUR-DLUS session notifications to indicate the number of times each
   of the tables has had a status change of a row since the APPN node
   was last reinitialized.

また、このグループに含まれているのは、TG、ポート、リンク、およびAPPNノードが最後に再初期化されて以来それぞれテーブルの回数には列の状態変化があるのを示すDLUR-DLUSセッション通知のための物です。

4.  Definitions

4. 定義

APPN-TRAP-MIB DEFINITIONS ::= BEGIN

APPN罠MIB定義:、:= 始まってください。

IMPORTS

輸入

        Counter32, OBJECT-TYPE, MODULE-IDENTITY,

Counter32、オブジェクト・タイプ、モジュールアイデンティティ

Clouston & Moore            Standards Track                     [Page 6]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[6ページ]RFC2456APPNはMIB1998年11月に捕らえます。

        NOTIFICATION-TYPE
                FROM SNMPv2-SMI

SNMPv2-SMIからの通知タイプ

        MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
                FROM SNMPv2-CONF

SNMPv2-CONFからのモジュールコンプライアンス、物グループ、通知グループ

        appnMIB, appnIsInP2SFmdPius, appnIsInS2PFmdPius,
        appnIsInP2SNonFmdPius, appnIsInS2PNonFmdPius,
        appnIsInP2SFmdBytes, appnIsInS2PFmdBytes,
        appnIsInP2SNonFmdBytes, appnIsInS2PNonFmdBytes,
        appnIsInSessUpTime, appnObjects,
        appnLocalTgOperational, appnLocalTgCpCpSession,
        appnPortOperState, appnLsOperState,
        appnCompliances, appnGroups
                 FROM APPN-MIB

APPN-MIBからのappnMIB、appnIsInP2SFmdPius、appnIsInS2PFmdPius、appnIsInP2SNonFmdPius、appnIsInS2PNonFmdPius、appnIsInP2SFmdBytes、appnIsInS2PFmdBytes、appnIsInP2SNonFmdBytes、appnIsInS2PNonFmdBytes、appnIsInSessUpTime、appnObjects、appnLocalTgOperational、appnLocalTgCpCpSession、appnPortOperState、appnLsOperState、appnCompliances、appnGroups

        dlurDlusSessnStatus
                 FROM APPN-DLUR-MIB;

APPN-DLUR-MIBからのdlurDlusSessnStatus。

appnTrapMIB MODULE-IDENTITY
        LAST-UPDATED  "9808310000Z" -- August 31, 1998
        ORGANIZATION  "IETF SNA NAU MIB WG / AIW APPN MIBs SIG"
        CONTACT-INFO

appnTrapMIBモジュールアイデンティティ最終更新日の"9808310000Z"--1998年8月31日組織「IETF SNAノーMIB WG / AIW APPN MIBs SIG」コンタクトインフォメーション

                "
                        Bob Clouston
                        Cisco Systems
                        7025 Kit Creek Road
                        P.O. Box 14987
                        Research Triangle Park, NC 27709, USA
                        Tel:    1 919 472 2333
                        E-mail: clouston@cisco.com

「7025年のボブCloustonシスコシステムズキットクリーク道路私書箱14987リサーチトライアングル公園、NC 27709、米国Tel:」 1 2333年の919 472メール: clouston@cisco.com

                        Bob Moore
                        IBM Corporation
                        4205 S. Miami Boulevard
                        BRQA/501
                        P.O. Box 12195
                        Research Triangle Park, NC 27709, USA
                        Tel:    1 919 254 4436
                        E-mail: remoore@us.ibm.com
                "
      DESCRIPTION
                "This MIB module defines notifications to be generated by
                network devices with APPN capabilities.  It presupposes
                support for the APPN MIB.  It also presupposes
                support for the DLUR MIB for implementations
                that support the DLUR-related groups."

4205秒間マイアミ並木街BRQA/501私書箱12195リサーチトライアングル公園、NC 27709、ボブムーアIBM社の米国Tel: 1 4436年の919 254メール: remoore@us.ibm.com 、「記述、「このMIBモジュールはAPPN能力があるネットワーク装置によって発生されるように通知を定義します」。 それはAPPN MIBのサポートを予想します。 「また、DLUR関連のグループを支持する実現のためにDLUR MIBのサポートを予想します。」

Clouston & Moore            Standards Track                     [Page 7]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[7ページ]RFC2456APPNはMIB1998年11月に捕らえます。

::= { appnMIB 0 }

::= appnMIB0

-- *********************************************************************
-- Notifications
-- *********************************************************************

-- ********************************************************************* -- 通知

appnIsrAccountingDataTrap NOTIFICATION-TYPE
      OBJECTS  {
                appnIsInP2SFmdPius,
                appnIsInS2PFmdPius,
                appnIsInP2SNonFmdPius,
                appnIsInS2PNonFmdPius,
                appnIsInP2SFmdBytes,
                appnIsInS2PFmdBytes,
                appnIsInP2SNonFmdBytes,
                appnIsInS2PNonFmdBytes,
                appnIsInSessUpTime
               }
      STATUS current
      DESCRIPTION
          "When it has been enabled, this notification is generated by an
          APPN node whenever an ISR session passing through the node is
          taken down, regardless of whether the session went down
          normally or abnormally.  Its purpose is to allow a management
          application (primarily an accounting application) that is
          monitoring the ISR counts to receive the final values of these
          counts, so that the application can properly account for the
          amounts the counts were incremented since the last time the
          application polled them.  The appnIsInSessUpTime object
          provides the total amount of time that the session was active.

appnIsrAccountingDataTrap NOTIFICATION-TYPE OBJECTS、appnIsInP2SFmdPius、appnIsInS2PFmdPius、appnIsInP2SNonFmdPius、appnIsInS2PNonFmdPius、appnIsInP2SFmdBytes、appnIsInS2PFmdBytes、appnIsInP2SNonFmdBytes、appnIsInS2PNonFmdBytes、appnIsInSessUpTime、「それは可能にされて、ノードを通り抜けるISRセッションが降ろされるときはいつも、セッションが通常か異常に落ちたかどうかにかかわらずこの通知はAPPNノードで発生する」STATUSの現在の記述。 目的が管理アプリケーション(主として会計アプリケーション)を許容することであり、すなわち、これらのカウントの検査値を受けるためにISRカウントをモニターして、アプリケーションが最後の時間それらに投票したので、カウントはアプリケーションが適切に量を説明できるように、増加されました。 appnIsInSessUpTime物はセッションが活発であったことの時間、合計を提供します。

          This notification is not a substitute for polling the ISR
          counts.  In particular, the count values reported in this
          notification cannot be assumed to be the complete totals for
          the life of the session, since they may have wrapped while the
          session was up.

この通知はISRカウントに投票する代用品ではありません。 特に、そうするかもしれなくて以来のセッションの人生のための完全な合計であるとセッションが終わりましたが、包装されて、この通知で報告されたカウント値を思うことができません。

          The session to which the objects in this notification apply is
          identified by the fully qualified CP name and PCID that make up
          the table index.  An instance of this notification will contain
          exactly one instance of each of its objects, and these objects
          will all belong to the same conceptual row of the
          appnIsInTable.

この通知における物が適用されるセッションは完全に適切なCP名とテーブルインデックスを補うPCIDによって特定されます。 この通知の例はまさにそれぞれの物の1つの例を含むでしょう、そして、これらの物はすべて、appnIsInTableの同じ概念的な列に属すでしょう。

          Generation of this notification is controlled by the same
          object in the APPN MIB, appnIsInGlobeCtrAdminStatus, that
          controls whether the count objects themselves are being
          incremented."

「この通知の世代はAPPN MIB、カウント物自体が増加されているかどうかを制御するappnIsInGlobeCtrAdminStatusの同じ物によって制御されます。」

Clouston & Moore            Standards Track                     [Page 8]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[8ページ]RFC2456APPNはMIB1998年11月に捕らえます。

      ::= { appnTrapMIB 1 }

::= appnTrapMIB1

appnLocalTgOperStateChangeTrap NOTIFICATION-TYPE
      OBJECTS  {
                appnLocalTgTableChanges,
                appnLocalTgOperational
               }
      STATUS current
      DESCRIPTION
          "When it has been enabled, this notification makes it possible
          for an APPN topology application to get asynchronous
          notifications of local TG operational state changes,
          and thus to reduce the frequency with which it polls
          for these changes.

appnLocalTgOperStateChangeTrap NOTIFICATION-TYPE OBJECTS、appnLocalTgTableChanges、appnLocalTgOperational、「それは可能にされて、この通知はAPPNトポロジーアプリケーションが地方のTG操作上の州の変化の非同期な通知を得て、その結果、それがこれらの変化に投票する頻度を減少させるのを可能にする」STATUSの現在の記述。

          This notification is sent whenever there is a change to
          the appnLocalTgOperational object in a row of the
          appnLocalTgTable.  This notification is only sent for row
          creation if the row is created with a value of 'true' for
          appnLocalTgOperational.  This notification is only sent for
          row deletion if the last value of appnLocalTgOperational was
          'true'.  In this case, the value of appnLocalTgOperational
          in the notification shall be 'false', since the deletion of
          a row indicates that the TG is no longer operational.

appnLocalTgOperational物への変化が並んであるときはいつも、appnLocalTgTableについてこの通知を送ります。 appnLocalTgOperationalに'本当'の値で列を作成する場合にだけ、列の創造のためにこの通知を送ります。 appnLocalTgOperationalの最終値が'本当であった'場合にだけ、列の削除のためにこの通知を送ります。 この場合、通知における、appnLocalTgOperationalの値は'誤るでしょう'、列の削除が、TGがもう操作上でないことを示すので。

          The notification is more than a simple 'poll me now' indication.
          It carries both a count of local TG topology changes, and the
          current operational state itself.  The count of changes allows an
          application to detect lost notifications, either when polling
          or upon receiving a subsequent notification, at which point it
          knows it must retrieve the entire appnLocalTgTable again.
          This is the same count as used in the appnLocalCpCpStateChangeTrap.
          A lost notification could indicate a local TG CP-CP session state
          change or an operational state change.

通知は'今、私に投票してください'という簡単な指示以上です。 それは地方のTGトポロジー変化のカウントと現在の操作上の状態自体の両方を運びます。 投票するとき、アプリケーションが変化のカウントで無くなっている通知を検出できなければなりませんか、またはその後の通知を受け取るとき、それがどのポイントでそれを知っているかが再び全体のappnLocalTgTableを検索しなければなりません。 これはappnLocalCpCpStateChangeTrapで使用されるように同じカウントです。 無くなっている通知は地方のTG CP-CPセッション州の変化か操作上の州の変化を示すかもしれません。

          Generation of this notification is controlled by the
          appnTrapControl object."

「この通知の世代はappnTrapControl物によって制御されます。」

      ::= { appnTrapMIB 2 }

::= appnTrapMIB2

appnLocalTgCpCpChangeTrap NOTIFICATION-TYPE
      OBJECTS  {
                appnLocalTgTableChanges,
                appnLocalTgCpCpSession
               }
      STATUS current
      DESCRIPTION
          "When it has been enabled, this notification makes it possible

appnLocalTgCpCpChangeTrap NOTIFICATION-TYPE OBJECTS、appnLocalTgTableChanges、appnLocalTgCpCpSession、「それは可能にされて、この通知はそれを可能にする」STATUSの現在の記述

Clouston & Moore            Standards Track                     [Page 9]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[9ページ]RFC2456APPNはMIB1998年11月に捕らえます。

          for an APPN topology application to get asynchronous
          notifications of local TG control-point to control-point (CP-CP)
          session state changes, and thus to reduce the
          frequency with which it polls for these changes.

APPNトポロジーアプリケーションが制御点(CP-CP)セッション州の変化に地方のTG制御点の非同期な通知を得て、その結果、それがこれらの変化に投票する頻度を減少させるために。

          This notification is sent whenever there is a change to
          the appnLocalTgCpCpSession object but NOT the
          appnLocalTgOperational object in a row of the appnLocalTgTable.
          This notification is never sent for appnLocalTgTable row
          creation or deletion.

appnLocalTgOperational物ではなく、appnLocalTgCpCpSession物への変化が並んであるときはいつも、appnLocalTgTableについてこの通知を送ります。 appnLocalTgTable列の創造か削除のためにこの通知を決して送りません。

          The notification is more than a simple 'poll me now' indication.
          It carries both a count of local TG topology changes, and the
          current CP-CP session state itself.  The count of changes allows
          an application to detect lost notifications, either when polling
          or upon receiving a subsequent notification, at which point it
          knows it must retrieve the entire appnLocalTgTable again.  This
          is the same count as used in the appnLocalTgOperStateChangeTrap.
          A lost notification could indicate a local TG CP-CP session
          state change or an operational state change.

通知は'今、私に投票してください'という簡単な指示以上です。 それは地方のTGトポロジー変化のカウントと現在のCP-CPセッション状態自体の両方を運びます。 投票するとき、アプリケーションが変化のカウントで無くなっている通知を検出できなければなりませんか、またはその後の通知を受け取るとき、それがどのポイントでそれを知っているかが再び全体のappnLocalTgTableを検索しなければなりません。 これはappnLocalTgOperStateChangeTrapで使用されるように同じカウントです。 無くなっている通知は地方のTG CP-CPセッション州の変化か操作上の州の変化を示すかもしれません。

          Generation of this notification is controlled by the
          appnTrapControl object."

「この通知の世代はappnTrapControl物によって制御されます。」

      ::= { appnTrapMIB 3 }

::= appnTrapMIB3

appnPortOperStateChangeTrap NOTIFICATION-TYPE
      OBJECTS  {
                appnPortTableChanges,
                appnPortOperState
               }

appnPortOperStateChangeTrap通知タイプ物appnPortTableChanges、appnPortOperState

      STATUS current
      DESCRIPTION
          "When it has been enabled, this notification makes it possible
          for an APPN topology application to get asynchronous
          notifications of port operational state changes, and thus to
          reduce the frequency with which it polls for these changes.
          This notification is only sent when a appnPortOperState has
          transitioned to a value of 'active' or 'inactive'.

「それは可能にされて、この通知はAPPNトポロジーアプリケーションが操作上の州が変えるポートの非同期な通知を得て、その結果、それがこれらの変化に投票する頻度を減少させるのを可能にする」STATUSの現在の記述。 appnPortOperStateが'アクティブである'か'不活発'の値に移行したときだけ、この通知を送ります。

          This notification is sent whenever there is a appnPortOperState
          object transition to 'inactive' or 'active' state in the
          appnPortTable.  This notification is only sent for row creation
          if the row is created with a value of 'active' for
          appnPortOperState.  This notification is only sent for
          row deletion if the last value of appnPortOperState was
          'active'.  In this case, the value of appnPortOperState

'不活発である'か'アクティブな'状態へのappnPortOperState物の変遷がappnPortTableにあるときはいつも、この通知を送ります。 appnPortOperStateに'アクティブ'の値で列を作成する場合にだけ、列の創造のためにこの通知を送ります。 appnPortOperStateの最終値が'アクティブであった'場合にだけ、列の削除のためにこの通知を送ります。 この場合appnPortOperStateの値

Clouston & Moore            Standards Track                    [Page 10]

RFC 2456                     APPN TRAPS MIB                November 1998

Cloustonとムーア標準化過程[10ページ]RFC2456APPNはMIB1998年11月に捕らえます。

          in the notification shall be 'inactive', since the deletion of
          a row indicates that the port is no longer active.

通知に、列の削除が、ポートがもうアクティブでないことを示して、'不活発'があるものとします。

          The notification is more than a simple 'poll me now' indication.
          It carries both a count of port table changes, and the
          operational state itself.  The count of changes allows an
          application to detect lost notifications, either when polling
          or upon receiving a subsequent notification, at which point
          it knows it must retrieve the entire appnPortTable again.

通知は'今、私に投票してください'という簡単な指示以上です。 それはポートテーブル変化のカウントと操作上の状態自体の両方を運びます。 投票するとき、アプリケーションが変化のカウントで無くなっている通知を検出できなければなりませんか、またはその後の通知を受け取るとき、それがどのポイントでそれを知っているかが再び全体のappnPortTableを検索しなければなりません。

          Generation of this notification is controlled by the
          appnTrapControl object."

「この通知の世代はappnTrapControl物によって制御されます。」

      ::= { appnTrapMIB 4 }

::= appnTrapMIB4

appnLsOperStateChangeTrap NOTIFICATION-TYPE
      OBJECTS  {
                appnLsTableChanges,
                appnLsOperState
               }
      STATUS current
      DESCRIPTION
          "When it has been enabled, this notification makes it possible
          for an APPN topology application to get asynchronous
          notifications of link station operational state changes, and
          thus to reduce the frequency with which it polls for these
          changes.  This notification is only sent when a appnLsOperState
          has transitioned to a value of 'active' or 'inactive'.

appnLsOperStateChangeTrap NOTIFICATION-TYPE OBJECTS、appnLsTableChanges、appnLsOperState、「それは可能にされて、この通知はAPPNトポロジーアプリケーションが操作上の州が変えるリンクステーションの非同期な通知を得て、その結果、それがこれらの変化に投票する頻度を減少させるのを可能にする」STATUSの現在の記述。 appnLsOperStateが'アクティブである'か'不活発'の値に移行したときだけ、この通知を送ります。

          This notification is sent whenever there is a appnLsOperState
          object transition to 'inactive' or 'active' state in the
          appnLsTable.  This notification is only sent for row creation
          if the row is created with a value of 'active' for
          appnLsOperState.  This notification is only sent for
          row deletion if the last value of appnLsOperState was
          'active'.  In this case, the value of appnLsOperState
          in the notification shall be 'inactive', since the deletion of
          a row indicates that the link station is no longer active.

This notification is sent whenever there is a appnLsOperState object transition to 'inactive' or 'active' state in the appnLsTable. This notification is only sent for row creation if the row is created with a value of 'active' for appnLsOperState. This notification is only sent for row deletion if the last value of appnLsOperState was 'active'. In this case, the value of appnLsOperState in the notification shall be 'inactive', since the deletion of a row indicates that the link station is no longer active.

          The notification is more than a simple 'poll me now' indication.
          It carries both a count of link station table changes, and the
          operational state itself.  The count of changes allows an
          application to detect lost notifications, either when polling
          or upon receiving a subsequent notification, at which point it
          knows it must retrieve the entire appnLsTable again.

The notification is more than a simple 'poll me now' indication. It carries both a count of link station table changes, and the operational state itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire appnLsTable again.

          Generation of this notification is controlled by the
          appnTrapControl object."

Generation of this notification is controlled by the appnTrapControl object."

Clouston & Moore            Standards Track                    [Page 11]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 11]  RFC 2456 APPN TRAPS MIB November 1998

      ::= { appnTrapMIB 5 }

::= { appnTrapMIB 5 }

dlurDlusStateChangeTrap NOTIFICATION-TYPE
      OBJECTS  {
                dlurDlusTableChanges,
                dlurDlusSessnStatus
               }
      STATUS current
      DESCRIPTION
          "When it has been enabled, this notification makes it possible
          for an APPN topology application to get asynchronous
          notifications of DLUR-DLUS session changes, and thus to reduce
          the frequency with which it polls for these changes.

dlurDlusStateChangeTrap NOTIFICATION-TYPE OBJECTS { dlurDlusTableChanges, dlurDlusSessnStatus } STATUS current DESCRIPTION "When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of DLUR-DLUS session changes, and thus to reduce the frequency with which it polls for these changes.

          This notification is sent whenever there is a dlurDlusSessnStatus
          object transition to 'inactive' or 'active' state in the
          dlurDlusTable.  This notification is only sent for row creation
          if the row is created with a value of 'active' for
          dlurDlusSessnStatus.  This notification is only sent for
          row deletion if the last value of dlurDlusSessnStatus was
          'active'.  In this case, the value of dlurDlusSessnStatus
          in the notification shall be 'inactive', since the deletion of
          a row indicates that the session is no longer active.

This notification is sent whenever there is a dlurDlusSessnStatus object transition to 'inactive' or 'active' state in the dlurDlusTable. This notification is only sent for row creation if the row is created with a value of 'active' for dlurDlusSessnStatus. This notification is only sent for row deletion if the last value of dlurDlusSessnStatus was 'active'. In this case, the value of dlurDlusSessnStatus in the notification shall be 'inactive', since the deletion of a row indicates that the session is no longer active.

          The notification is more than a simple 'poll me now' indication.
          It carries both a count of DLUR-DLUS table changes, and the
          session status itself.  The count of changes allows an
          application to detect lost notifications, either when polling
          or upon receiving a subsequent notification, at which point it
          knows it must retrieve the entire dlurDlusTable again.

The notification is more than a simple 'poll me now' indication. It carries both a count of DLUR-DLUS table changes, and the session status itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire dlurDlusTable again.

          Generation of this notification is controlled by the
          appnTrapControl object."

Generation of this notification is controlled by the appnTrapControl object."

      ::= { appnTrapMIB 6 }

::= { appnTrapMIB 6 }

-- *********************************************************************
-- Supporting Objects
-- *********************************************************************

-- ********************************************************************* -- Supporting Objects -- *********************************************************************

appnTrapObjects              OBJECT IDENTIFIER ::= { appnObjects 7 }

appnTrapObjects OBJECT IDENTIFIER ::= { appnObjects 7 }

appnTrapControl OBJECT-TYPE

appnTrapControl OBJECT-TYPE

      SYNTAX BITS {
                   appnLocalTgOperStateChangeTrap(0),
                   appnLocalTgCpCpChangeTrap(1),
                   appnPortOperStateChangeTrap(2),

SYNTAX BITS { appnLocalTgOperStateChangeTrap(0), appnLocalTgCpCpChangeTrap(1), appnPortOperStateChangeTrap(2),

Clouston & Moore            Standards Track                    [Page 12]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 12]  RFC 2456 APPN TRAPS MIB November 1998

                   appnLsOperStateChangeTrap(3),
                   dlurDlusStateChangeTrap(4)
                   -- add other notification types here
                  }
      MAX-ACCESS read-write
      STATUS current
      DESCRIPTION
          "An object to turn APPN notification generation on and off.
          Setting a notification type's bit to 1 enables generation of
          notifications of that type, subject to further filtering
          resulting from entries in the snmpNotificationMIB.  Setting
          this bit to 0 disables generation of notifications of that
          type.

appnLsOperStateChangeTrap(3), dlurDlusStateChangeTrap(4) -- add other notification types here } MAX-ACCESS read-write STATUS current DESCRIPTION "An object to turn APPN notification generation on and off. Setting a notification type's bit to 1 enables generation of notifications of that type, subject to further filtering resulting from entries in the snmpNotificationMIB. Setting this bit to 0 disables generation of notifications of that type.

          Note that generation of the appnIsrAccountingDataTrap is
          controlled by the appnIsInGlobeCtrAdminStatus object in
          the APPN MIB:  if counts of intermediate session traffic
          are being kept at all, then the notification is also enabled."

Note that generation of the appnIsrAccountingDataTrap is controlled by the appnIsInGlobeCtrAdminStatus object in the APPN MIB: if counts of intermediate session traffic are being kept at all, then the notification is also enabled."

      ::= { appnTrapObjects 1 }

::= { appnTrapObjects 1 }

appnLocalTgTableChanges OBJECT-TYPE
      SYNTAX Counter32
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "A count of the number of times a row in the appnLocalTgTable
          has changed status since the APPN node was last reinitialized.
          This counter is incremented whenever a condition is detected
          that would cause a appnLocalTgOperStateChangeTrap or
          appnLocalTgCpCpChangeTrap notification to be sent, whether
          or not those notifications are enabled."

appnLocalTgTableChanges OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of times a row in the appnLocalTgTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a appnLocalTgOperStateChangeTrap or appnLocalTgCpCpChangeTrap notification to be sent, whether or not those notifications are enabled."

      ::= { appnTrapObjects 2 }

::= { appnTrapObjects 2 }

appnPortTableChanges OBJECT-TYPE
      SYNTAX Counter32
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "A count of the number of times a row in the appnPortTable
          has changed status since the APPN node was last reinitialized.
          This counter is incremented whenever a condition is detected
          that would cause a appnPortOperStateChangeTrap notification
          to be sent, whether or not this notification is enabled."

appnPortTableChanges OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of times a row in the appnPortTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a appnPortOperStateChangeTrap notification to be sent, whether or not this notification is enabled."

      ::= { appnTrapObjects 3 }

::= { appnTrapObjects 3 }

Clouston & Moore            Standards Track                    [Page 13]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 13]  RFC 2456 APPN TRAPS MIB November 1998

appnLsTableChanges OBJECT-TYPE
      SYNTAX Counter32
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "A count of the number of times a row in the appnLsTable
          has changed status since the APPN node was last reinitialized.
          This counter is incremented whenever a condition is detected
          that would cause a appnLsOperStateChangeTrap notification
          to be sent, whether or not this notification is enabled."

appnLsTableChanges OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of times a row in the appnLsTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a appnLsOperStateChangeTrap notification to be sent, whether or not this notification is enabled."

      ::= { appnTrapObjects 4 }

::= { appnTrapObjects 4 }

dlurDlusTableChanges OBJECT-TYPE
      SYNTAX Counter32
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "A count of the number of times a row in the dlurDlusTable
          has changed status since the APPN node was last reinitialized.
          This counter is incremented whenever a condition is detected
          that would cause a dlurDlusStateChangeTrap notification
          to be sent, whether or not this notification is enabled."

dlurDlusTableChanges OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of times a row in the dlurDlusTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a dlurDlusStateChangeTrap notification to be sent, whether or not this notification is enabled."

      ::= { appnTrapObjects 5 }

::= { appnTrapObjects 5 }

-- *********************************************************************
-- Conformance information
-- *********************************************************************

-- ********************************************************************* -- Conformance information -- *********************************************************************

-- Tie into the conformance structure in the APPN MIB:
-- appnConformance       OBJECT IDENTIFIER ::= {appnMIB 3 }
--
-- appnCompliances       OBJECT IDENTIFIER ::= {appnConformance 1 }
-- appnGroups            OBJECT IDENTIFIER ::= {appnConformance 2 }

-- Tie into the conformance structure in the APPN MIB: -- appnConformance OBJECT IDENTIFIER ::= {appnMIB 3 } -- -- appnCompliances OBJECT IDENTIFIER ::= {appnConformance 1 } -- appnGroups OBJECT IDENTIFIER ::= {appnConformance 2 }

-- Compliance statement
appnTrapMibCompliance  MODULE-COMPLIANCE
       STATUS  current
       DESCRIPTION
           "The compliance statement for the SNMP entities that
           implement the APPN-TRAP-MIB."

-- Compliance statement appnTrapMibCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for the SNMP entities that implement the APPN-TRAP-MIB."

       MODULE  -- this module

MODULE -- this module

--     Conditionally mandatory groups
           GROUP appnTrapMibIsrNotifGroup
           DESCRIPTION

-- Conditionally mandatory groups GROUP appnTrapMibIsrNotifGroup DESCRIPTION

Clouston & Moore            Standards Track                    [Page 14]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 14]  RFC 2456 APPN TRAPS MIB November 1998

               "This group is mandatory for APPN nodes supporting
               reporting of final ISR counter values via notifications."

"This group is mandatory for APPN nodes supporting reporting of final ISR counter values via notifications."

           GROUP appnTrapMibTopoConfGroup
           DESCRIPTION
               "This group is mandatory for APPN nodes supporting
               polling reduction for local topology."

GROUP appnTrapMibTopoConfGroup DESCRIPTION "This group is mandatory for APPN nodes supporting polling reduction for local topology."

           GROUP appnTrapMibTopoNotifGroup
           DESCRIPTION
               "This group is mandatory for APPN nodes supporting
               polling reduction for local topology."

GROUP appnTrapMibTopoNotifGroup DESCRIPTION "This group is mandatory for APPN nodes supporting polling reduction for local topology."

           GROUP appnTrapMibDlurConfGroup
           DESCRIPTION
               "This group is mandatory for APPN nodes supporting
               polling reduction for the dlurDlusTable."

GROUP appnTrapMibDlurConfGroup DESCRIPTION "This group is mandatory for APPN nodes supporting polling reduction for the dlurDlusTable."

           GROUP appnTrapMibDlurNotifGroup
           DESCRIPTION
               "This group is mandatory for APPN nodes supporting
               polling reduction for the dlurDlusTable."

GROUP appnTrapMibDlurNotifGroup DESCRIPTION "This group is mandatory for APPN nodes supporting polling reduction for the dlurDlusTable."

           OBJECT appnTrapControl
               MIN-ACCESS  read-only
               DESCRIPTION
                   "An agent is not required to support a set to
                   this object."

OBJECT appnTrapControl MIN-ACCESS read-only DESCRIPTION "An agent is not required to support a set to this object."

       ::= {appnCompliances 2 }

::= {appnCompliances 2 }

-- Units of conformance
appnTrapMibIsrNotifGroup    NOTIFICATION-GROUP
        NOTIFICATIONS {
                       appnIsrAccountingDataTrap
                      }
        STATUS  current
        DESCRIPTION
            "A notification for reporting the final values of the
            APPN MIB's ISR counters."

-- Units of conformance appnTrapMibIsrNotifGroup NOTIFICATION-GROUP NOTIFICATIONS { appnIsrAccountingDataTrap } STATUS current DESCRIPTION "A notification for reporting the final values of the APPN MIB's ISR counters."

        ::= { appnGroups 21 }

::= { appnGroups 21 }

appnTrapMibTopoConfGroup  OBJECT-GROUP
        OBJECTS  {
                  appnTrapControl,
                  appnLocalTgTableChanges,
                  appnPortTableChanges,

appnTrapMibTopoConfGroup OBJECT-GROUP OBJECTS { appnTrapControl, appnLocalTgTableChanges, appnPortTableChanges,

Clouston & Moore            Standards Track                    [Page 15]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 15]  RFC 2456 APPN TRAPS MIB November 1998

                  appnLsTableChanges
                 }
        STATUS  current
        DESCRIPTION
            "A collection of objects for reducing the polling
            associated with the local topology tables in the
            APPN MIB.  Nodes that implement this group SHALL
            also implement the appnTrapMibTopoNotifGroup."

appnLsTableChanges } STATUS current DESCRIPTION "A collection of objects for reducing the polling associated with the local topology tables in the APPN MIB. Nodes that implement this group SHALL also implement the appnTrapMibTopoNotifGroup."

        ::= { appnGroups 22 }

::= { appnGroups 22 }

appnTrapMibTopoNotifGroup    NOTIFICATION-GROUP
        NOTIFICATIONS {
                       appnLocalTgOperStateChangeTrap,
                       appnLocalTgCpCpChangeTrap,
                       appnPortOperStateChangeTrap,
                       appnLsOperStateChangeTrap

appnTrapMibTopoNotifGroup NOTIFICATION-GROUP NOTIFICATIONS { appnLocalTgOperStateChangeTrap, appnLocalTgCpCpChangeTrap, appnPortOperStateChangeTrap, appnLsOperStateChangeTrap

                      }
        STATUS  current
        DESCRIPTION
            "A collection of notifications for reducing the polling
            associated with the local topology tables in the
            APPN MIB.  Nodes that implement this group SHALL
            also implement the appnTrapMibTopoConfGroup."

} STATUS current DESCRIPTION "A collection of notifications for reducing the polling associated with the local topology tables in the APPN MIB. Nodes that implement this group SHALL also implement the appnTrapMibTopoConfGroup."

        ::= { appnGroups 23 }

::= { appnGroups 23 }

appnTrapMibDlurConfGroup  OBJECT-GROUP
        OBJECTS  {
                  appnTrapControl,
                  dlurDlusTableChanges
                 }
        STATUS  current
        DESCRIPTION
            "A collection of objects for reducing the polling
            associated with the dlurDlusTable in the DLUR
            MIB.  Nodes that implement this group SHALL also
            implement the appnTrapMibDlurNotifGroup."

appnTrapMibDlurConfGroup OBJECT-GROUP OBJECTS { appnTrapControl, dlurDlusTableChanges } STATUS current DESCRIPTION "A collection of objects for reducing the polling associated with the dlurDlusTable in the DLUR MIB. Nodes that implement this group SHALL also implement the appnTrapMibDlurNotifGroup."

        ::= { appnGroups 24 }

::= { appnGroups 24 }

appnTrapMibDlurNotifGroup    NOTIFICATION-GROUP
        NOTIFICATIONS {
                       dlurDlusStateChangeTrap
                      }
        STATUS  current
        DESCRIPTION

appnTrapMibDlurNotifGroup NOTIFICATION-GROUP NOTIFICATIONS { dlurDlusStateChangeTrap } STATUS current DESCRIPTION

Clouston & Moore            Standards Track                    [Page 16]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 16]  RFC 2456 APPN TRAPS MIB November 1998

            "A notification for reducing the polling associated
            with the dlurDlusTable in the DLUR MIB.  Nodes that
            implement this group SHALL also implement the
            appnTrapMibDlurConfGroup."

"A notification for reducing the polling associated with the dlurDlusTable in the DLUR MIB. Nodes that implement this group SHALL also implement the appnTrapMibDlurConfGroup."

        ::= { appnGroups 25 }

::= { appnGroups 25 }

END

END

5.  Security Considerations

5. Security Considerations

   Certain management information defined in this MIB may be considered
   sensitive in some network environments.  Therefore, authentication of
   received SNMP requests and controlled access to management
   information SHOULD be employed in such environments.  An
   authentication protocol is defined in [12].  A protocol for access
   control is defined in [15].

Certain management information defined in this MIB may be considered sensitive in some network environments. Therefore, authentication of received SNMP requests and controlled access to management information SHOULD be employed in such environments. An authentication protocol is defined in [12]. A protocol for access control is defined in [15].

   None of the read-only objects in the APPN TRAP MIB reports a
   password, user data, or anything else that is particularly sensitive.
   Some enterprises view their network configuration itself, as well as
   information about network usage and performance, as corporate assets;
   such enterprises may wish to restrict SNMP access to most of the
   objects in the MIB.

None of the read-only objects in the APPN TRAP MIB reports a password, user data, or anything else that is particularly sensitive. Some enterprises view their network configuration itself, as well as information about network usage and performance, as corporate assets; such enterprises may wish to restrict SNMP access to most of the objects in the MIB.

   There is one read-write object in the APPN TRAP MIB, appnTrapControl.
   This object controls the generation of the notifications defined in
   the APPN TRAP MIB.

There is one read-write object in the APPN TRAP MIB, appnTrapControl. This object controls the generation of the notifications defined in the APPN TRAP MIB.

6.  Intellectual Property

6. Intellectual Property

   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 [16].  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 implementers or users of this specification can
   be obtained from the IETF Secretariat.

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 [16]. 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 implementers or users of this specification can be obtained from the IETF Secretariat.

Clouston & Moore            Standards Track                    [Page 17]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 17]  RFC 2456 APPN TRAPS MIB November 1998

   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.

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.

7.  Acknowledgments

7. Acknowledgments

   This MIB module is the product of the IETF SNA NAU MIB WG and the AIW
   APPN/HPR MIBs SIG.

This MIB module is the product of the IETF SNA NAU MIB WG and the AIW APPN/HPR MIBs SIG.

8.  References

8. References

   [1]  Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
        Describing SNMP Management Frameworks", RFC 2271, Cabletron
        Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
        January 1998.

[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2271, Cabletron Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.

   [2]  Rose, M., and K. McCloghrie, "Structure and Identification of
        Management Information for TCP/IP-based Internets", STD 16, RFC
        1155, May 1990.

[2] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.

   [3]  Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
        RFC 1212, March 1991.

[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.

   [4]  Rose, M., "A Convention for Defining Traps for use with the
        SNMP", RFC 1215, March 1991.

[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.

   [5]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Structure of Management Information for Version 2 of the Simple
        Network Management Protocol (SNMPv2)", RFC 1902, January 1996.

[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.

   [6]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
        Conventions for Version 2 of the Simple Network Management
        Protocol (SNMPv2)", RFC 1903, January 1996.

[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.

   [7]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Conformance Statements for Version 2 of the Simple Network
        Management Protocol (SNMPv2)", RFC 1904, January 1996.

[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.

   [8]  Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
        Network Management Protocol", STD 15, RFC 1157, May 1990.

[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.

   [9]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Introduction to Community-based SNMPv2", RFC 1901, January
        1996.

[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.

Clouston & Moore            Standards Track                    [Page 18]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 18]  RFC 2456 APPN TRAPS MIB November 1998

   [10] 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.

[10] 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.

   [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
        Processing and Dispatching for the Simple Network Management
        Protocol (SNMP)", RFC 2272, January 1998.

[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2272, January 1998.

   [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
        for version 3 of the Simple Network Management Protocol
        (SNMPv3)", RFC 2274, January 1998.

[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2274, January 1998.

   [13] 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.

[13] 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.

   [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
        2273, January 1998.

[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2273, January 1998.

   [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
         Control Model (VACM) for the Simple Network Management Protocol
         (SNMP)", RFC 2275, January 1998

[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2275, January 1998

   [16] Hovey, R., and S. Bradner, "The Organizations Involved in the
        IETF Standards Process", BCP 11, RFC 2028, October 1996.

[16] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996.

   [17] Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

[17] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.

   [18] Clouston, B., and B. Moore, "Definition of Managed Objects for
        APPN", RFC 2455, November 1998.

[18] Clouston, B., and B. Moore, "Definition of Managed Objects for APPN", RFC 2455, November 1998.

   [19] Clouston, B., and B. Moore, "Definitions of Managed Objects for
        DLUR", RFC 2232, November 1997.

[19] Clouston, B., and B. Moore, "Definitions of Managed Objects for DLUR", RFC 2232, November 1997.

Clouston & Moore            Standards Track                    [Page 19]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 19]  RFC 2456 APPN TRAPS MIB November 1998

9.  Authors' Addresses

9. Authors' Addresses

   Bob Clouston
   Cisco Systems
   7025 Kit Creek Road
   P.O. Box 14987
   Research Triangle Park, NC 27709, USA

Bob Clouston Cisco Systems 7025 Kit Creek Road P.O. Box 14987 Research Triangle Park, NC 27709, USA

   Phone: +1 919 472 2333
   EMail: clouston@cisco.com

Phone: +1 919 472 2333 EMail: clouston@cisco.com

   Robert Moore
   Dept. BRQA/Bldg. 501/G114
   IBM Corporation
   P.O.Box 12195
   3039 Cornwallis
   Research Triangle Park, NC 27709, USA

Robert Moore Dept. BRQA/Bldg. 501/G114 IBM Corporation P.O.Box 12195 3039 Cornwallis Research Triangle Park, NC 27709, USA

   Phone: +1 919 254 4436
   EMail: remoore@us.ibm.com

Phone: +1 919 254 4436 EMail: remoore@us.ibm.com

Clouston & Moore            Standards Track                    [Page 20]

RFC 2456                     APPN TRAPS MIB                November 1998

Clouston & Moore Standards Track [Page 20]  RFC 2456 APPN TRAPS MIB November 1998

10.  Full Copyright Statement

10. Full Copyright Statement

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

Copyright (C) The Internet Society (1998). All Rights Reserved.

   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.

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.

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.

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.

Clouston & Moore            Standards Track                    [Page 21]

Clouston & Moore Standards Track [Page 21]